
From d.raft@rocketmail.com  Mon Apr  1 03:52:50 2013
Return-Path: <d.raft@rocketmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 481DE21F88EF for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 03:52:50 -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.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X+KH1Gf2SaxC for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 03:52:49 -0700 (PDT)
Received: from nm1-vm0.bullet.mail.ird.yahoo.com (nm1-vm0.bullet.mail.ird.yahoo.com [77.238.189.95]) by ietfa.amsl.com (Postfix) with SMTP id 416CE21F88E8 for <ietf@ietf.org>; Mon,  1 Apr 2013 03:52:49 -0700 (PDT)
Received: from [212.82.105.245] by nm1.bullet.mail.ird.yahoo.com with NNFMP; 01 Apr 2013 10:52:48 -0000
Received: from [212.82.108.252] by tm17.bullet.mail.ird.yahoo.com with NNFMP; 01 Apr 2013 10:52:48 -0000
Received: from [127.0.0.1] by omp1017.mail.ird.yahoo.com with NNFMP; 01 Apr 2013 10:52:48 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 286391.55812.bm@omp1017.mail.ird.yahoo.com
Received: (qmail 23708 invoked by uid 60001); 1 Apr 2013 10:52:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rocketmail.com; s=s1024; t=1364813568; bh=HbKbfaA14z+5rJ/3eecrlYPAexvYEJl3VXSkj5oVwf0=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Haf8jBOVyRAMzux3WNGVR6DX4fMR3+kR1ZYV8h3AGo4JslKHvFlIeFTyJiQYG8jtJpn/rJMkspi1fIKZgi+yho2a9jfSGxiZBxGkB/HQxL9/3drFTcZQ0DT9wuo0Lh6tQ8ecuiNIXF1EcZrWDshxQaQr2PN+12grjPioocxaSjc=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rocketmail.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=4Nk9gar8YpitK7K8lzjiV/07Zj6FwllTubMcclRc6NGZD6cCMgGWZKIdAlcUvboF9H3USHAAzgjZavAntb4/tuOWsbH2juPH2enWJtOKAYF5FPxkp9LZYio5D7e/c9Q/fWEwOFOreqaa8IQN9TEaq77TyEj+cGJtMZDfBb2D2ro=;
X-YMail-OSG: O222UEUVM1nQTTG.PLp8IQpa4FeDcyAXFoRXHBNoQv0ct.H vVQNmu0gi0a8iPnA4e0Zdqz9WT_NZG8b3V2tjXKkQWHyH0.NipAF3Y1QbsOp Ozq3IOd7ZniKBYkdhYOUz9n.0CgBEQIDdoo2UNUfZhuZVtQvVJsNw47g2wGL Y6UaVy9oNiqYfv2xH7k9s0kEKyuO6KKFJNcOfJyU5kaKOlzKTfKYS30f7swF XDPFM8ZlnYjkqhMI.JseUC_DwUzbfFFkyq0aRtv612zk87RpCFdAvG4HBPGI G76DIC7MVvDKpxt5pGdBdfsQf.Fyj7AlRfzTnFCdVloyuBjC1atMlZhctMG1 YPBU9GTp.QOvmVdAOhhdD5WIEfEAN.0QyhupQNkdUPuXiRWZkpWMW7xwbWn. YVQsL0nU8k9eZQ.lhwIL3VGFlRuC.JhBUqYa6qb1rcWtygJnFcli6Jfl.Np8 0rVYY9SUAvU.EPDU0whyw0ysitl6uRrnrDFvaohkzs9ocAkNigWYK62vMZ9i LvDz71yAujaD_DdIR5w--
Received: from [84.137.55.166] by web172405.mail.ir2.yahoo.com via HTTP; Mon, 01 Apr 2013 11:52:48 BST
X-Rocket-MIMEInfo: 002.001, U1RFQU06IEJPRiBwcm9wb3NhbCBmb3IgQmVybGluCgpZb3UgbWF5IGhhdmUgbm90aWNlZCBhIHJlY2VudCB0cmVuZCBpbiB0aGUgSUVURiB0b3dhcmRzIHZlcnkKbGlnaHR3ZWlnaHQgcHJvdG9jb2xzIGZvciB0aGUgSW50ZXJuZXQgb2YgRXZlcnl0aGluZy4KaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtZHJhZnQtZHJhZnQgaXMgdGhlIG1vc3QgZnVsbHkKZGV2ZWxvcGVkIHByb3Bvc2FsIG9uIHRoZSB0YWJsZSB0b2RheS4gwqBJdCBpcyBleHRyZW1lbHkgbGlnaHR3ZWlnaHQgYnkKc2ltcGx5IHUBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.139.530
Message-ID: <1364813568.23297.YahooMailNeo@web172405.mail.ir2.yahoo.com>
Date: Mon, 1 Apr 2013 11:52:48 +0100 (BST)
From: Daniel Raft <d.raft@rocketmail.com>
Subject: STEAM: BOF proposal for Berlin
To: "ietf@ietf.org" <ietf@ietf.org>
MIME-Version: 1.0
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
Reply-To: Daniel Raft <d.raft@rocketmail.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: Mon, 01 Apr 2013 10:54:37 -0000

STEAM: BOF proposal for Berlin=0A=0AYou may have noticed a recent trend in =
the IETF towards very=0Alightweight protocols for the Internet of Everythin=
g.=0Ahttp://tools.ietf.org/html/draft-draft-draft is the most fully=0Adevel=
oped proposal on the table today. =A0It is extremely lightweight by=0Asimpl=
y using UDP and nothing else.=0A=0ARecently, however, that draft has been c=
riticized for lack of=0Acongestion control. =A0And rightly so, because the =
only way to have=0Acongestion control is to use TCP. =A0And, TCP is all you=
 need.=0ABut then, clearly, there aren't enough RFCs about TCP yet [RFC4627=
].=0AA new WG will therefore develop "Secure TCP Extensions for Application=
=0Aand Management" (STEAM).=0A=0AAgain, TCP is all you need, but it hasn't =
been used for Provisioning=0Avery much yet. =A0The main objective of the ne=
w WG is therefore an=0Ainformational document for "Secure Provisioning for =
Applications and=0AManagement using TCP Reimagined as an Attractive Protoco=
l", SPAM-TRAP.=0A=0AWe aren't quite sure yet whether STEAM will be in the S=
ecurity,=0ATransport, Application, or Management Areas, or whether it shoul=
d have=0Aits own area (EVG for Internet of Everything). =A0We will use the =
BOF in=0ABerlin to figure out, and to set up the new EVG area in the IETF, =
and=0Ato restyle the IETF to "Internet of Everything Task Force".=0A=0AOne =
other field that STEAM will be working in is IETF process innovation.=0A(We=
 also figure you can't post to the IETF mailing list without=0Aincluding at=
 least one process improvement suggestion. =A0So we make two.)=0A=0A1) You =
might notice there is no R in STEAM. =A0This is because we have=0Ato increa=
se collaboration within a diverse IETF.=0AThe RTG area already has the ROLL=
 working group, which has been very=0Ainnovative in getting routing protoco=
ls to standards track RFC before=0Athere is even a glimpse of security, app=
licability or management.=0ADoing standardization in smoke-filled backrooms=
 is unhealthy, and=0ASTEAM has many of the properties needed for a replacem=
ent process.=0AWe don't want to spill the beans just yet, but can already s=
ay the=0Aprocess innovation will be named in honor of the two WGs, STEAM/RO=
LL.=0A=0A2) Finally, preparing for the global deployment of the=0AInternet-=
Enabled Smart Grid (IESG), and to further increase diversity,=0Awe probably=
 want to enable the use of steam-powered typewriters for=0AIETF work.=0AThe=
 STEAM WG will enhance the RFC format and process to allow direct=0Apublish=
ing from typewritten sheets and scanned printouts of Word=0Adocuments.=0A=
=0ASee you at the STEAM BOF in Berlin,=0A=0ADaniel Raft=0A

From tony@att.com  Mon Apr  1 04:56:31 2013
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 CE7FB21F8904 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 04:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.306
X-Spam-Level: 
X-Spam-Status: No, score=-105.306 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M4MISYMy35cK for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 04:56:31 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 155E221F8501 for <ietf@ietf.org>; Mon,  1 Apr 2013 04:56:26 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 9e579515.0.48752.00-448.125027.nbfkord-smmo07.seg.att.com (envelope-from <tony@att.com>);  Mon, 01 Apr 2013 11:56:26 +0000 (UTC)
X-MXL-Hash: 515975ea5f683071-35a6d26d974943c0466488f087bf3dbefa99c76d
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r31BuPJU007541 for <ietf@ietf.org>; Mon, 1 Apr 2013 07:56:25 -0400
Received: from alpi133.aldc.att.com (alpi133.aldc.att.com [130.8.217.3]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r31BuMBS007526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 1 Apr 2013 07:56:22 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi133.aldc.att.com (RSA Interceptor) for <ietf@ietf.org>; Mon, 1 Apr 2013 12:56:02 +0100
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r31Bu2Fr011603 for <ietf@ietf.org>; Mon, 1 Apr 2013 07:56:02 -0400
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r31Bu0vS011454 for <ietf@ietf.org>; Mon, 1 Apr 2013 07:56:01 -0400
Received: from [135.70.85.31] (vpn-135-70-85-31.vpn.swst.att.com[135.70.85.31]) by maillennium.att.com (mailgw1) with ESMTP id <20130401115414gw1000m5bhe> (Authid: tony); Mon, 1 Apr 2013 11:54:18 +0000
X-Originating-IP: [135.70.85.31]
Message-ID: <515975CA.3020705@att.com>
Date: Mon, 01 Apr 2013 07:55:54 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: STEAM: BOF proposal for Berlin
References: <1364813568.23297.YahooMailNeo@web172405.mail.ir2.yahoo.com>
In-Reply-To: <1364813568.23297.YahooMailNeo@web172405.mail.ir2.yahoo.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative; boundary="------------070106020900000206040508"
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.20.145]
X-AnalysisOut: [v=2.0 cv=b8UFFK6x c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=2JTH1Lu9lAgA:10 a=z55uD49gxukA:10 a=YefzbA8-rNkA:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=Ihg0Ow4T]
X-AnalysisOut: [XQ8A:10 a=YHMznWbcv_g9Zg1EhCoA:9 a=wPNLvfGTeEIA:10 a=CjxXg]
X-AnalysisOut: [O3LAAAA:8 a=-ZmwPChtLEMeUH3IiS4A:9 a=_W_S_7VecoQA:10 a=4sY]
X-AnalysisOut: [vWJcaNgE9AyJ-: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, 01 Apr 2013 11:56:31 -0000

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

I'm thinking the enhanced RFC format proposed below should be dubbed
STEAM/PUNC.

    Tony Hansen

On 4/1/2013 6:52 AM, Daniel Raft wrote:
> STEAM: BOF proposal for Berlin
> ...
> 2) Finally, preparing for the global deployment of the
> Internet-Enabled Smart Grid (IESG), and to further increase diversity,
> we probably want to enable the use of steam-powered typewriters for
> IETF work.
> The STEAM WG will enhance the RFC format and process to allow direct
> publishing from typewritten sheets and scanned printouts of Word
> documents.


--------------070106020900000206040508
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">
    <link href="chrome://translator/skin/floatingPanel.css"
      type="text/css" rel="stylesheet">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    I'm thinking the enhanced RFC format proposed below should be dubbed
    STEAM/PUNC.<br>
    <br>
    &nbsp;&nbsp;&nbsp; Tony Hansen<br>
    <br>
    <div class="moz-cite-prefix">On 4/1/2013 6:52 AM, Daniel Raft wrote:<br>
    </div>
    <blockquote
      cite="mid:1364813568.23297.YahooMailNeo@web172405.mail.ir2.yahoo.com"
      type="cite">
      <pre wrap="">STEAM: BOF proposal for Berlin
...
2) Finally, preparing for the global deployment of the
Internet-Enabled Smart Grid (IESG), and to further increase diversity,
we probably want to enable the use of steam-powered typewriters for
IETF work.
The STEAM WG will enhance the RFC format and process to allow direct
publishing from typewritten sheets and scanned printouts of Word
documents.
</pre>
    </blockquote>
    <br>
    <div style="bottom: auto; left: 494px; right: auto; top: 27px;"
      class="translator-theme-default" id="translator-floating-panel">
      <div title="Click to translate"
        id="translator-floating-panel-button"></div>
    </div>
  </body>
</html>

--------------070106020900000206040508--

From susielu25@gmail.com  Sun Mar 31 22:12:52 2013
Return-Path: <susielu25@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 5BB6621F85D9 for <ietf@ietfa.amsl.com>; Sun, 31 Mar 2013 22:12:51 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pF6aSycw1JOE for <ietf@ietfa.amsl.com>; Sun, 31 Mar 2013 22:12:49 -0700 (PDT)
Received: from mail-ia0-x236.google.com (mail-ia0-x236.google.com [IPv6:2607:f8b0:4001:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 3D03C21F84E3 for <ietf@ietf.org>; Sun, 31 Mar 2013 22:12:47 -0700 (PDT)
Received: by mail-ia0-f182.google.com with SMTP id u8so1631612iag.13 for <ietf@ietf.org>; Sun, 31 Mar 2013 22:12:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=wV7VGqUvXHCQZr0TkPZvKHkDJxmducZIWNVZffsAMn0=; b=l0Tv1oMrh6b20MI6eBuMSLqKMDT3A2vH3UmwGYSi9lPxmxLxBLRYC++df7TzL2B58F 4w6cM1EVLTd3kp9iriDTB3hz0PmgwFmfvcVFAsOaV4syUXrlUT6LBxPWu3gs6781fODj VHSSE/puHM2pDGnIiAv7O8beXZUxR0+PPxuzZ2ZYFJb4G2B5iQPSF6hYlG8WpISqzZfI R6VA5bF9vFKTBwMJLAuFKvLwiKve+q9eURWCbo+h8YsE9WGxOzIgFpFwHAIQDRXHO2+Y GXuM+kAscQ4pyK4HnhVVsIz9FNYjch+Rzue1CNRZf68CVIczSvOzXo4W++CRo7KoRfRe i4SA==
MIME-Version: 1.0
X-Received: by 10.50.92.4 with SMTP id ci4mr2860437igb.95.1364793167127; Sun, 31 Mar 2013 22:12:47 -0700 (PDT)
Received: by 10.50.112.71 with HTTP; Sun, 31 Mar 2013 22:12:47 -0700 (PDT)
Date: Mon, 1 Apr 2013 13:12:47 +0800
Message-ID: <CADVOzF5vf1w8eVvWzzJ8E3MZRYETuK9QUbkX51Kpz99wEiD+gg@mail.gmail.com>
Subject: Re:The Interconnection and Interoperability of Different Cloud-office Applications (IDCOA) with the HTML File Format draft-guo-idoca-with-the-html-file-format-00
From: Susie Lu <susielu25@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=e89a8f3bb247eb29de04d945ab40
X-Mailman-Approved-At: Mon, 01 Apr 2013 07:05:33 -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: Mon, 01 Apr 2013 05:12:52 -0000

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

Zhun : What are your I-D about? As I know , native office applications
based on XML. Then you draft are about some product ,such as Google Docs,
Microsoft Office 365, IBM Docs ,Zoho,ThinkFree,Cisco WebEx,Evernote...?



Susie

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

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:13px=
">Zhun : What are your I-D about? As I know , native office applications ba=
sed on XML. Then you draft are about some product ,such as Google Docs, Mic=
rosoft Office 365, IBM Docs ,Zoho,ThinkFree,Cisco WebEx,Evernote...?=A0</sp=
an><div>
<span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span></di=
v><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></sp=
an></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><=
br>
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">Susie</span></div></div>

--e89a8f3bb247eb29de04d945ab40--

From piyush@ditenity.com  Fri Mar 29 09:17:16 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8568A21F94F0 for <ietf@ietfa.amsl.com>; Fri, 29 Mar 2013 09:17:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.716
X-Spam-Level: 
X-Spam-Status: No, score=-2.716 tagged_above=-999 required=5 tests=[AWL=0.883,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZeyDvBq93fe for <ietf@ietfa.amsl.com>; Fri, 29 Mar 2013 09:17:16 -0700 (PDT)
Received: from mail-gh0-f175.google.com (mail-gh0-f175.google.com [209.85.160.175]) by ietfa.amsl.com (Postfix) with ESMTP id 980C721F94F2 for <ietf@ietf.org>; Fri, 29 Mar 2013 09:17:14 -0700 (PDT)
Received: by mail-gh0-f175.google.com with SMTP id f1so44406ghb.34 for <ietf@ietf.org>; Fri, 29 Mar 2013 09:17:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=+5PVVpAaAZ2cB0uKcFCPuLcPGzfXbN/K61uOX/TlPvs=; b=JhkKfbdg2oZycBKCZH+IwLnRtXIRpmlCaOsFqFxzjacLkRqb5Im3VutXAAJK4mdSDT +osNXxtwjArC/ajMHNN/c/FXQ54B8xg4NxVBzFcNy61ev4o93mCGoaRjrGLKXlYrQrva rcy1sTXTEFRhi2twtnRoKG7mzKIjaAeOLc4mDAzDBrck8hEm3aFz4lgUDhvTbAY0Qn7u gKnK1xVSP5RaycePDfn6FAu64IVrkwFel8Pl9kF42/I+pxK2ZdB6ly1TqViye25PymmF Ohx/mkWut7ypJKC9ToqnSJaXJBnL3HdiAnqFvKNTpny/jDwHftEKXdUZw6GDO/5Bot4K I8wg==
X-Received: by 10.236.222.69 with SMTP id s65mr749951yhp.59.1364573833856; Fri, 29 Mar 2013 09:17:13 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id f70sm1732504yhi.12.2013.03.29.09.17.11 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 29 Mar 2013 09:17:13 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Stefan Santesson'" <stefan@aaa-sec.com>, "'Black, David'" <david.black@emc.com>, <sts@aaa-sec.com>, <mmyers@fastq.com>, <ambarish@gmail.com>, <slava.galperin@gmail.com>, <cadams@eecs.uottawa.ca>, <gen-art@ietf.org>
References: <8D3D17ACE214DC429325B2B98F3AE71293D366B6@MX15A.corp.emc.com> <CD79DA61.5EF8B%stefan@aaa-sec.com>
In-Reply-To: <CD79DA61.5EF8B%stefan@aaa-sec.com>
Subject: RE: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
Date: Fri, 29 Mar 2013 09:17:08 -0700
Message-ID: <00fc01ce2c98$ddc41770$994c4650$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQGpRT9g4u5Gd5W5MBiHHaGDqUWdEpkGo+sQ
Content-Language: en-us
X-Gm-Message-State: ALoCoQnwLkUlR5rIOgtmh6KZs9MRPXCNEPAMgu5eIAKlpvWonDJx2IhmkUqFKxDObA4dmRaY4RSJ
X-Mailman-Approved-At: Mon, 01 Apr 2013 07:05:45 -0700
Cc: pkix@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, 29 Mar 2013 16:17:16 -0000

' "revoked" status is still optional in this context in order to maintain
backwards compatibility with deployments of RFC 2560.'

I fail to understand this statement about backward compatibility.
 How does "revoked" being "optional/required breaks backward compatibility?
The only reason cited in the WG discussions to use revoked for "not-issued"
was that any other approach would break backward compatibility with legacy
clients. And now the draft says that revoked is optional because making it
required won't be backward compatible.

And it gives the impression that best course of action for 2560bis
responders is to start issuing revoked for "not-issued", which is far from
the originally stated goal to provide a way for CAs to be able to return
revoked for such serial numbers.

-Piyush

> -----Original Message-----
> From: pkix-bounces@ietf.org [mailto:pkix-bounces@ietf.org] On Behalf Of
> Stefan Santesson
> Sent: Thursday, March 28, 2013 3:34 AM
> To: Black, David; sts@aaa-sec.com; mmyers@fastq.com;
> ambarish@gmail.com; slava.galperin@gmail.com; cadams@eecs.uottawa.ca;
> gen-art@ietf.org
> Cc: pkix@ietf.org; ietf@ietf.org
> Subject: Re: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
> 
> I have given this a go by expanding the note as follows:
> 
> NOTE: The "revoked" state for known non-issued certificate serial
>          numbers is allowed in order to reduce the risk of relying
>          parties using CRLs as a fall back mechanism, which would be
>          considerably higher if an "unknown" response was returned. The
>          "revoked" status is still optional in this context in order to
>          maintain backwards compatibility with deployments of RFC 2560.
>          For example, the responder may not have any knowledge about
>          whether a requested serial number has been assigned to any
>          issued certificate, or the responder may provide pre produced
>          responses in accordance with RFC 5019 and, for that reason, is
>          not capable of providing a signed response for all non-issued
>          certificate serial numbers.
> 
> 
> Does this solve you issue.
> I think this is as far as dare to go without risking a heated debate.
> 
> /Stefan
> 
> 
> On 3/27/13 5:08 PM, "Black, David" <david.black@emc.com> wrote:
> 
> >Stefan,
> >
> >> Is this important enough to do that?
> >
> >IMHO, yes - the "running code" aspects of existing responder
> >behavior/limitations are definitely important enough for an RFC like
> >this that revises a protocol spec, and the alternatives to "revoked"
> >feel like an important complement to those aspects (discussion what to
> >do instead when responder behavior/limitations are encountered).
> >
> >I appreciate the level of work that may be involved in capturing this,
> >as I've had my share of contentious discussions in WGs that I chair -
> >FWIW, I'm currently chairing my 4th and 5th WGs.  OTOH, when a WG has
> >put that much time/effort into reaching a (compromise) decision, it
> >really is valuable to record why the decision was reached to avoid
> >recovering that ground in the future and (specific to this situation)
> >to give implementers some more context/information on how the protocol
> >is likely to work in practice.
> >
> >Thanks,
> >--David
> >
> >> -----Original Message-----
> >> From: Stefan Santesson [mailto:stefan@aaa-sec.com]
> >> Sent: Wednesday, March 27, 2013 11:38 AM
> >> To: Black, David; sts@aaa-sec.com; mmyers@fastq.com;
> >> ambarish@gmail.com; slava.galperin@gmail.com;
> cadams@eecs.uottawa.ca;
> >> gen-art@ietf.org
> >> Cc: pkix@ietf.org; Sean Turner; ietf@ietf.org
> >> Subject: Re: Gen-ART review of draft-ietf-pkix-rfc2560bis-15
> >>
> >> I could.
> >>
> >> My worry is just that this is such a contentious subject and it took
> >>us x  hundreds of emails to reach this state, that if I add more
> >>explanations,  people will start disagreeing with it and that we end
> >>up in a long debate  on how to correctly express this.
> >>
> >> Is this important enough to do that?
> >>
> >> /Stefan
> >>
> >>
> >> On 3/27/13 3:30 PM, "Black, David" <david.black@emc.com> wrote:
> >>
> >> >Hi Stefan,
> >> >
> >> >> Does this answer your question?
> >> >
> >> >Yes, please add some of that explanation to the next version of the
> >>draft
> >> >;-).
> >> >Coverage of existing responder behavior/limitations (important
> >> >"running code"
> >> >concerns, IMHO) and alternatives to using "revoked" ("have a number
> >> >of tools to prevent the client from accepting a bad certificate")
> >> >seem
> >>particularly
> >> >relevant.
> >> >
> >> >Thanks,
> >> >--David
> >> >
> >> >> -----Original Message-----
> >> >> From: Stefan Santesson [mailto:stefan@aaa-sec.com]
> >> >> Sent: Wednesday, March 27, 2013 7:44 AM
> >> >> To: Black, David; sts@aaa-sec.com; mmyers@fastq.com;
> >>ambarish@gmail.com;
> >> >> slava.galperin@gmail.com; cadams@eecs.uottawa.ca; gen-
> art@ietf.org
> >> >> Cc: pkix@ietf.org; Sean Turner; ietf@ietf.org
> >> >> Subject: Re: Gen-ART review of draft-ietf-pkix-rfc2560bis-15
> >> >>
> >> >> Hi David,
> >> >>
> >> >> Yes I missed to respond to that aspect.
> >> >>
> >> >> This is a bit complicated, but we have a large legacy to take into
> >> >>account  where some responders implements just RFC 2560, while
> some
> >> >>deliver  pre-generated responses according to RFC 5019
> >> >>(Light-weight OCSP). LW  responders are not capable of producing a
> >> >>signed response at the
> >>time of
> >> >> responding and in case such responder finds a request for a
> >>certificate
> >> >> where no pre-produced response exists, it will reply with an
> >> >>unsigned  error response "unauthorized", which also is a legitimate
> >> >>way to respond.
> >> >> So the actual OCSP responder may actually know that the
> >> >>certificate
> >>was
> >> >> never issued, but since it delivers pre-produced responder through
> >> >>a CDN,  it can not provide a revoked response in real time.
> >> >>
> >> >> So the major aim with the current writing is to declare that the
> >>revoked
> >> >> response is a MAY because there are other valid alternatives.
> >> >>
> >> >> We also want to avoid putting down a SHOULD respond revoked if a
> >> >> certificate is known to be not-issued, because that would require
> >> >> us
> >>to
> >> >> define what "known to be non-issued" actually means. And that
> >> >> could
> >>be
> >> >> quite tricky as OCSP responders by no means are required to have
> >> >> this knowledge.
> >> >>
> >> >> The OCSP responder simply have a number of tools to prevent the
> >>client
> >> >> from accepting a bad certificate.
> >> >> This update of OCSP simply allows responders to use the "revoked"
> >> >>response
> >> >> as a preventive measure, without mandating it.
> >> >>
> >> >> This is also related to activities in the CA Browser Forum where
> >> >>they put  down requirements on responders complying with CAB rules
> >> >>to not
> >>respond
> >> >> "good" to certificates that were never issued.
> >> >> With this update in OCSP, they can now mandate in their policies
> >> >>both the  fact that their responders MUST know if a certificate was
> >> >>never
> >>issued
> >> >>and
> >> >> MUST respond "revoked".
> >> >>
> >> >> So we allow other communities to raise the bar even if the base
> >>standard
> >> >> defines the response as optional.
> >> >>
> >> >> In theory we could possibly say that responding revoked is
> >> >> optional,
> >>but
> >> >> if you choose between revoked and unknown then you SHOULD
> favour
> >>revoked
> >> >> over unknown. But such nested requirements just feels bad and
> >>impossible
> >> >> to test compliance against. I'd much rather just leave it
> >> >> optional. I think the Note gives a clear recommendation on this
> >> >> and the rationale without spelling it out as a requirement.
> >> >>
> >> >> Does this answer your question?
> >> >>
> >> >>
> >> >> On 3/27/13 12:51 AM, "Black, David" <david.black@emc.com> wrote:
> >> >>
> >> >> >Hi Stefan,
> >> >> >
> >> >> >This looks good - thank you for the prompt response.
> >> >> >
> >> >> >It looks like my speculation on item [1] was wrong, so could you
> >> >>respond
> >> >> >to the question below, please?:
> >> >> >
> >> >> >> >[1] Section 2.2:
> >> >> >> >
> >> >> >> >       NOTE: The "revoked" state for known non-issued
> >>certificate serial
> >> >> >> >               numbers is allowed in order to reduce the risk
> >> >> >> > of
> >>relying
> >> >> >> >               parties using CRLs as a fall back mechanism,
> >>which would be
> >> >> >> >               considerably higher if an "unknown" response
> >> >> >> > was
> >>returned.
> >> >> >> >
> >> >> >> >Given this explanation, I'm surprised that the use of "revoked"
> >> >> >>instead of
> >> >> >> >"unknown" for a known non-issued certificate is a "MAY"
> >>requirement
> >> >>and
> >> >> >> >not a "SHOULD" requirement.  Why is that the case?
> >> >> >
> >> >> >--------------
> >> >> >
> >> >> >Beyond that, the proposed actions (or proposed non-actions) on
> >> >> >items [2]-[5] are fine with me, Sean's taken care of the author
> >> >> >permissions item
> >>from
> >> >> >idnits, and I assume someone has or will check the ASN.1 .
> >> >> >
> >> >> >Thanks,
> >> >> >--David
> >> >> >
> >> >> >> -----Original Message-----
> >> >> >> From: Stefan Santesson [mailto:stefan@aaa-sec.com]
> >> >> >> Sent: Monday, March 25, 2013 10:21 PM
> >> >> >> To: Black, David; sts@aaa-sec.com; mmyers@fastq.com;
> >> >>ambarish@gmail.com;
> >> >> >> slava.galperin@gmail.com; cadams@eecs.uottawa.ca;
> >> >> >> gen-art@ietf.org
> >> >> >> Cc: pkix@ietf.org; Sean Turner; ietf@ietf.org
> >> >> >> Subject: Re: Gen-ART review of draft-ietf-pkix-rfc2560bis-15
> >> >> >>
> >> >> >> Hi David,
> >> >> >>
> >> >> >> Thanks for the review.
> >> >> >> My reply in line.
> >> >> >>
> >> >> >> On 3/26/13 1:25 AM, "Black, David" <david.black@emc.com> wrote:
> >> >> >>
> >> >> >> >Authors,
> >> >> >> >
> >> >> >> >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-pkix-rfc2560bis-15
> >> >> >> >Reviewer: David L. Black
> >> >> >> >Review Date: March 25, 2013
> >> >> >> >IETF LC End Date: March 27, 2013
> >> >> >> >
> >> >> >> >Summary:
> >> >> >> >This draft is on the right track but has open issues,
> >> >> >> >described
> >>in
> >> >>the
> >> >> >> >review.
> >> >> >> >
> >> >> >> >This draft updates the OCSP protocol for obtaining certificate
> >> >>status
> >> >> >> >with some minor extensions.
> >> >> >> >
> >> >> >> >Because this is a "bis" draft, I reviewed the diffs against
> >> >> >> >RFC
> >> >>2560.
> >> >> >> >
> >> >> >> >I did not check the ASN.1.  I also did not see a writeup for
> >> >> >> >this
> >> >>draft
> >> >> >> >in the data tracker, and so will rely on the document shepherd
> >> >> >> >to ensure that the ASN.1 has been checked when the writeup is
> >>prepared.
> >> >> >> >
> >> >> >> >I found five open issues, all of which are minor, plus one
> >> >> >> >idnits
> >> >>item
> >> >> >> >that is probably ok, but should be double-checked.
> >> >> >> >
> >> >> >> >Minor issues:
> >> >> >> >
> >> >> >> >[1] Section 2.2:
> >> >> >> >
> >> >> >> >       NOTE: The "revoked" state for known non-issued
> >>certificate serial
> >> >> >> >               numbers is allowed in order to reduce the risk
> >> >> >> > of
> >>relying
> >> >> >> >               parties using CRLs as a fall back mechanism,
> >>which would be
> >> >> >> >               considerably higher if an "unknown" response
> >> >> >> > was
> >>returned.
> >> >> >> >
> >> >> >> >Given this explanation, I'm surprised that the use of "revoked"
> >> >> >>instead of
> >> >> >> >"unknown" for a known non-issued certificate is a "MAY"
> >>requirement
> >> >>and
> >> >> >> >not a "SHOULD" requirement.  Why is that the case?
> >> >> >> >
> >> >> >> >It appears that the reason is that the use of "revoked" in
> >> >> >> >this
> >> >> >>situation
> >> >> >> >may be dangerous when serial numbers can be predicted for
> >> >>certificates
> >> >> >> >that
> >> >> >> >will be issued in the future.  If that's what's going on, this
> >> >>concern
> >> >> >>is
> >> >> >> >already explained in the security considerations section, but
> >> >> >> >it
> >> >>should
> >> >> >> >also be mentioned here for completeness.
> >> >> >>
> >> >> >> No, this is not the main reason. The main reason is the one
> >> >> >> stated
> >> >>as a
> >> >> >> Note: in this section:
> >> >> >>
> >> >> >> NOTE: The "revoked" state for known non-issued certificate
> >> >> >>serial numbers  is allowed in order to reduce the risk of
> >> >> >>relying parties using
> >>CRLs
> >> >>as
> >> >> >>a
> >> >> >> fall back mechanism, which would be considerably higher if an
> >> >>"unknown"
> >> >> >> response was returned.
> >> >> >>
> >> >> >>
> >> >> >> >
> >> >> >> >[2] Section 4.2.2.2:
> >> >> >> >
> >> >> >> >       The key that signs a certificate's status information
> >>need not be
> >> >>the
> >> >> >> >       same key that signed the certificate. It is necessary
> >>however to
> >> >> >> >       ensure that the entity signing this information is
> >>authorized to
> >> do
> >> >> >> >       so.  Therefore, a certificate's issuer MAY either sign
> >>the OCSP
> >> >> >> >       responses itself or it MAY explicitly designate this
> >>authority to
> >> >> >> >       another entity.
> >> >> >> >
> >> >> >> >The two instances of "MAY" in the above text were both "MUST"
> >> >> >> >in
> >>RFC
> >> >> >>2560.
> >> >> >> >
> >> >> >> >The RFC 2560 text construction of "MUST" or "MUST" is a bit
> >> >> >> >odd,
> >>but
> >> >> >>the two
> >> >> >> >"MAY"s in this draft are even worse, as they allow "MAY do
> >>something
> >> >> >>else
> >> >> >> >entirely", despite being enclosed in an either-or construct.
> >> >> >> >I
> >> >> >>strongly
> >> >> >> >suspect that the latter was not intended, so the following
> >> >> >> >would
> >>be
> >> >> >> >clearer:
> >> >> >> >
> >> >> >> >       The key that signs a certificate's status information
> >>need not be
> >> >>the
> >> >> >> >       same key that signed the certificate. It is necessary
> >>however to
> >> >> >> >       ensure that the entity signing this information is
> >>authorized to
> >> do
> >> >> >> >       so.  Therefore, a certificate's issuer MUST do one of
> >> >> >> > the
> >> >>following:
> >> >> >> >               - sign the OCSP responses itself, or
> >> >> >> >               - explicitly designate this authority to
> >> >> >> > another
> >>entity.
> >> >> >>
> >> >> >>
> >> >> >> I Agree. I will adopt your text.
> >> >> >>
> >> >> >> >
> >> >> >> >[3] Section 4.3:
> >> >> >> >
> >> >> >> >Is the "SHOULD" requirement still appropriate for the DSA with
> >>SHA-1
> >> >> >>combo
> >> >> >> >(vs. a "MAY" requirement)?  This requirement was a "MUST" in
> >> >> >> >RFC
> >> >>2560,
> >> >> >>but
> >> >> >> >I wonder about actual usage of DSA in practice.
> >> >> >>
> >> >> >> The change in algorithm requirements was provided by RFC 6277,
> >> >> >>and further  refined in this draft in accordance with requests
> >> >> >>from Sean
> >>Turner.
> >> >> >>
> >> >> >> >
> >> >> >> >[4] Section 5, last paragraph:
> >> >> >> >
> >> >> >> >       Responding a "revoked" state to certificate that has
> >>never been
> >> >> >> >       issued may enable someone to obtain a revocation
> >> >> >> > response
> >>for a
> >> >> >> >       certificate that is not yet issued, but soon will be
> >>issued, if
> >> the
> >> >> >> >       CA issues certificates using sequential certificate
> >>serial number
> >> >> >> >       assignment.
> >> >> >> >
> >> >> >> >The above text after starting with the "if" is too narrow - it
> >> >>should
> >> >> >>say:
> >> >> >> >
> >> >> >> >       if the certificate serial number of the certificate that
> >> >> >> >       will be issued can be predicted or guessed by the
> >>requester.
> >> >> >> >       Such prediction is easy for a CA that issues certificates
> >> >> >> >       using sequential certificate serial number assignment.
> >> >> >> >
> >> >> >> >There's also a nit in original text - its first line should be:
> >> >> >> >
> >> >> >> >       Responding with a "revoked" state for a certificate
> >> >> >> > that
> >>has never
> >> >> >>been
> >> >> >>
> >> >> >> Good suggestions. I will update accordingly.
> >> >> >>
> >> >> >> >
> >> >> >> >[5] Section 5.1.1:
> >> >> >> >
> >> >> >> >       In archival applications it is quite possible that an
> >> >> >> > OCSP
> >> >>responder
> >> >> >> >       might be asked to report the validity of a certificate
> >> >> >> > on
> >>a date
> >> in
> >> >> >> >       the distant past. Such a certificate might employ a
> >>signing method
> >> >> >> >       that is no longer considered acceptably secure. In such
> >> >> >> >       circumstances the responder MUST NOT generate a
> >> >> >> > signature
> >>using a
> >> >> >> >       signing mechanism that is not considered acceptably
> >>secure.
> >> >> >> >
> >> >> >> >This could use an additional warning that certificate archival
> >> >>should
> >> >> >> >not rely solely on signatures in archived certificates for
> >>ensuring
> >> >>the
> >> >> >> >validity and integrity of the archived certificates because
> >> >> >> >the
> >> >> >>signature
> >> >> >> >algorithm(s) may transition to no longer being considered
> >>acceptably
> >> >> >> >secure at some point after the certificates are archived.
> >> >> >>
> >> >> >> This note if I remember correctly is imported from RFC 6277,
> >>which is
> >> >> >> incorporated into this document. The reason behind the text is
> >>only
> >> >>to
> >> >> >> avoid usages of insecure algorithms.
> >> >> >> Historical validation is a real can of worms that I really
> >> >> >> would
> >> >>like to
> >> >> >> keep a tight lid on. I really want to avoid doing
> >> >> >> recommendations
> >>in
> >> >> >>this
> >> >> >> space as it may trigger a whole flood of things that could be
> >>equally
> >> >> >> important to say about this subject.
> >> >> >>
> >> >> >> >
> >> >> >> >Nits:
> >> >> >> >
> >> >> >> >idnits 2.12.15 said:
> >> >> >> >
> >> >> >> >  -- The document seems to lack a disclaimer for pre-RFC5378
> >>work,
> >> >>but
> >> >> >>may
> >> >> >> >     have content which was first submitted before 10 November
> >>2008.
> >> >> >>If
> >> >> >> >you
> >> >> >> >     have contacted all the original authors and they are all
> >> >>willing
> >> >> >>to
> >> >> >> >grant
> >> >> >> >     the BCP78 rights to the IETF Trust, then this is fine,
> >> >> >> >and
> >>you
> >> >>can
> >> >> >> >ignore
> >> >> >> >     this comment.  If not, you may need to add the
> >> >> >> >pre-RFC5378 disclaimer.
> >> >> >> >     (See the Legal Provisions document at
> >> >> >> >     http://trustee.ietf.org/license-info for more
> >> >> >> >information.)
> >> >> >> >
> >> >> >> >This looks like it's ok because all the authors of RFC 2560
> >> >> >> >are
> >>also
> >> >> >> >authors of
> >> >> >> >this draft, but it should be double-checked.
> >> >> >>
> >> >> >>
> >> >> >> I defer this one to Sean. I think he has this one under control.
> >> >> >>
> >> >> >>
> >> >> >> Thanks again for the review.
> >> >> >>
> >> >> >> /Stefan
> >> >> >>
> >> >> >>
> >> >> >> >
> >> >> >> >Thanks,
> >> >> >> >--David
> >> >> >> >----------------------------------------------------
> >> >> >> >David L. Black, Distinguished Engineer EMC Corporation, 176
> >> >> >> >South St., Hopkinton, MA  01748
> >> >> >> >+1 (508) 293-7953             FAX: +1 (508) 293-7786
> >> >> >> >david.black@emc.com        Mobile: +1 (978) 394-7754
> >> >> >> >----------------------------------------------------
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >
> >> >>
> >> >>
> >> >
> >>
> >>
> >
> 
> 
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix


From stefan@aaa-sec.com  Fri Mar 29 09:37:14 2013
Return-Path: <stefan@aaa-sec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C53C921F93B8 for <ietf@ietfa.amsl.com>; Fri, 29 Mar 2013 09:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.171
X-Spam-Level: 
X-Spam-Status: No, score=-102.171 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, HELO_EQ_SE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dwXDQgHEEyol for <ietf@ietfa.amsl.com>; Fri, 29 Mar 2013 09:37:14 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by ietfa.amsl.com (Postfix) with ESMTP id 321B121F91AA for <ietf@ietf.org>; Fri, 29 Mar 2013 09:37:14 -0700 (PDT)
Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id 0C2B51F07DC6 for <ietf@ietf.org>; Fri, 29 Mar 2013 17:37:13 +0100 (CET)
X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se
Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id D3Blq2i2phgH for <ietf@ietf.org>; Fri, 29 Mar 2013 17:37:12 +0100 (CET)
Received: from s327.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id B6D601F07DBE for <ietf@ietf.org>; Fri, 29 Mar 2013 17:37:12 +0100 (CET)
Received: (qmail 51098 invoked from network); 29 Mar 2013 16:37:12 -0000
Received: from 81-232-51-61-no39.business.telia.com (HELO [192.168.0.104]) (stefan@fiddler.nu@[81.232.51.61]) (envelope-sender <stefan@aaa-sec.com>) by s327.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <piyush@ditenity.com>; 29 Mar 2013 16:37:12 -0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Fri, 29 Mar 2013 17:37:10 +0100
Subject: Re: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
From: Stefan Santesson <stefan@aaa-sec.com>
To: Piyush Jain <piyush@ditenity.com>, "'Black, David'" <david.black@emc.com>, <sts@aaa-sec.com>, <mmyers@fastq.com>, <ambarish@gmail.com>, <slava.galperin@gmail.com>, <cadams@eecs.uottawa.ca>, <gen-art@ietf.org>
Message-ID: <CD7B80C0.5F100%stefan@aaa-sec.com>
Thread-Topic: [pkix] Gen-ART review of draft-ietf-pkix-rfc2560bis-15
In-Reply-To: <00fc01ce2c98$ddc41770$994c4650$@ditenity.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Mon, 01 Apr 2013 07:05:44 -0700
Cc: pkix@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, 29 Mar 2013 16:37:14 -0000

On 3/29/13 5:17 PM, "Piyush Jain" <piyush@ditenity.com> wrote:

>' "revoked" status is still optional in this context in order to maintain
>backwards compatibility with deployments of RFC 2560.'
>
>I fail to understand this statement about backward compatibility.
>How does "revoked" being "optional/required breaks backward compatibility?
>The only reason cited in the WG discussions to use revoked for
>"not-issued"
>was that any other approach would break backward compatibility with legacy
>clients. And now the draft says that revoked is optional because making it
>required won't be backward compatible.

Yes. Making it required would prohibit other valid ways to respond to this
situation that is allowed by RFC 2560 and RFC 5019.
Such as responding "good" or responding with "unauthorized" error.

>
>And it gives the impression that best course of action for 2560bis
>responders is to start issuing revoked for "not-issued", which is far from
>the originally stated goal to provide a way for CAs to be able to return
>revoked for such serial numbers.

The latter is what optional means.

/Stefan



From david.black@emc.com  Fri Mar 29 15:59:25 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 174C521F8C83; Fri, 29 Mar 2013 15:59:25 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81jpheRAwxZY; Fri, 29 Mar 2013 15:59:24 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id ABF3F21F8B61; Fri, 29 Mar 2013 15:59:20 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2TMxGPG020843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Mar 2013 18:59:16 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 29 Mar 2013 18:58:57 -0400
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r2TMwuvS027472; Fri, 29 Mar 2013 18:58:57 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Fri, 29 Mar 2013 18:58:56 -0400
From: "Black, David" <david.black@emc.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Ted Lemon <Ted.Lemon@nominum.com>
Date: Fri, 29 Mar 2013 18:58:55 -0400
Subject: RE: [savi] Gen-ART review of draft-ietf-savi-threat-scope-06
Thread-Topic: [savi] Gen-ART review of draft-ietf-savi-threat-scope-06
Thread-Index: Ac4szVjS9UAHr94bQtuYWuQh61daWAAAsYBA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293D36C5C@MX15A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E055F69357F@MX14A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.com> <8D23D4052ABE7A4490E77B1A012B63077511F644@mbx-01.win.nominum.com> <8D3D17ACE214DC429325B2B98F3AE71293D36520@MX15A.corp.emc.com> <51531EA4.4030504@joelhalpern.com> <8D3D17ACE214DC429325B2B98F3AE71293D366C6@MX15A.corp.emc.com> <5153222E.30202@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B6307751243D6@mbx-01.win.nominum.com> <515610B0.2050204@joelhalpern.com>
In-Reply-To: <515610B0.2050204@joelhalpern.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-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 01 Apr 2013 07:05:45 -0700
Cc: "McPherson, Danny" <dmcpherson@verisign.com>, "savi@ietf.org" <savi@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "joel.halpern@ericsson.com" <joel.halpern@ericsson.com>, "Black, David" <david.black@emc.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, 29 Mar 2013 22:59:25 -0000

Joel,

Yes, I think you do have the right end of the question, and that new text l=
ooks
ok, as the previous sentence introduces the gratuitous ARP.

To summarize, we've decided to address two of the three concerns from the r=
eview
of -06.  The third concern that will not be addressed is:=20

> a) the alternative of statically allowing all source addresses through al=
l
>	teamed/aggregated links (decouples SAVI state from link teaming/aggregati=
on
>	state) should also be mentioned,

I'm satisfied with this outcome.

Thanks,
--David

> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: Friday, March 29, 2013 6:08 PM
> To: Ted Lemon
> Cc: Black, David; McPherson, Danny; savi@ietf.org; ietf@ietf.org; gen-
> art@ietf.org; Jean-Michel Combes; joel.halpern@ericsson.com
> Subject: Re: [savi] Gen-ART review of draft-ietf-savi-threat-scope-06
>=20
> I have a draft version with this correction.
> David, would adding:
>            When such a move
>            is done without changing the MAC address, the SAVI switches
>            will need to update their state.  While the ARP may be
>            helpful,
>            traffic detection, switch based neighbor solicitation,
>            interaction with orchestration system, or other means may be
>            used.
> to the end of 5.2.3 address your concern?  I am not sure whether I have
> the right end of the question here, given that SAVI can not create new
> protocol.
>=20
> Yours,
> Joel
>=20
> On 3/27/2013 10:56 PM, Ted Lemon wrote:
> > On Mar 27, 2013, at 12:45 PM, Joel Halpern Direct
> <jmh.direct@joelhalpern.com> wrote:
> >
> >> Then it will be done.  I will wait for the AD to decide what other cha=
nges
> are needed, and then will either make this change or include it in an RFC
> Editor note.
> >
> >> Old:
> >>    If the bridging topologies which connects the switches changes, or
> >>    if LACP [IEEE802.3ad] changes which links are used to deliver
> >>    traffic, the switch may need to move the SAVI state to a different
> >>    port, are the state may need to be moved or reestablished on a
> >>    different switch.
> >> New:
> >>    If the bridging topologies which connects the switches changes, or
> >>    if LACP [IEEE802.3ad], VRRP, or other link management
> >>    operations, change which links are used to deliver
> >>    traffic, the switch may need to move the SAVI state to a different
> >>    port, are the state may need to be moved or reestablished on a
> >>    different switch.
> >
> > I think you probably meant "or", not "are", in the second word of the
> second-to-last line of the new text.
> >
> > As far as I am concerned, given that David is happy with your recent ch=
ange,
> I'm happy with it too.   However, since you are asking, if you were willi=
ng to
> also accommodate David's other request (see below) by adding some text to=
 the
> document in section 5, that would be an added bonus:
> >
> >> A paragraph has been added to 5.2.3 to address all three of the above
> concerns.   I guess that's ok, but I would have liked to see some text
> pointing out that a MAC move can be detected by the switches and used to
> update SAVI state about which port(s) a MAC is accessed through.
> >
> > So if you can do this, it would be much appreciated; if you can't do it=
, I
> think the document is valuable enough to move forward without this additi=
onal
> work.
> >
> >


From wjhns1@hardakers.net  Mon Apr  1 07:12:46 2013
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 D317A11E80A2 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 07:12:46 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lvp0Ot3xKhLU for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 07:12:46 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id 46BEE11E80AD for <ietf@ietf.org>; Mon,  1 Apr 2013 07:12:46 -0700 (PDT)
Received: from localhost (wjh.hardakers.net [IPv6:2001:470:1f00:187:f2de:f1ff:fee6:e6e8]) by mail.hardakers.net (Postfix) with ESMTPSA id 6D14720061; Mon,  1 Apr 2013 07:12:45 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Tony Hansen <tony@att.com>
Subject: Re: STEAM: BOF proposal for Berlin
References: <1364813568.23297.YahooMailNeo@web172405.mail.ir2.yahoo.com> <515975CA.3020705@att.com>
Date: Mon, 01 Apr 2013 07:12:45 -0700
In-Reply-To: <515975CA.3020705@att.com> (Tony Hansen's message of "Mon, 01 Apr 2013 07:55:54 -0400")
Message-ID: <0l62069w6a.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
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, 01 Apr 2013 14:12:47 -0000

Tony Hansen <tony@att.com> writes:

> I'm thinking the enhanced RFC format proposed below should be dubbed
> STEAM/PUNC.

And anyone that participates in said work would be "STEAMed".
-- 
Wes Hardaker
SPARTA, Inc.

From drafts1962@yahoo.co.uk  Mon Apr  1 06:38:35 2013
Return-Path: <drafts1962@yahoo.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 92D1021E803F for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 06:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.69
X-Spam-Level: 
X-Spam-Status: No, score=-0.69 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_ILLEGAL_IP=1.908]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kb71gxCSYuDu for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 06:38:34 -0700 (PDT)
Received: from nm3.bullet.mail.ird.yahoo.com (nm3.bullet.mail.ird.yahoo.com [77.238.189.60]) by ietfa.amsl.com (Postfix) with SMTP id 0DE7621E803A for <ietf@ietf.org>; Mon,  1 Apr 2013 06:38:30 -0700 (PDT)
Received: from [77.238.189.230] by nm3.bullet.mail.ird.yahoo.com with NNFMP; 01 Apr 2013 13:38:30 -0000
Received: from [212.82.108.245] by tm11.bullet.mail.ird.yahoo.com with NNFMP; 01 Apr 2013 13:38:30 -0000
Received: from [127.0.0.1] by omp1010.mail.ird.yahoo.com with NNFMP; 01 Apr 2013 13:38:30 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 197600.89939.bm@omp1010.mail.ird.yahoo.com
Received: (qmail 57531 invoked by uid 60001); 1 Apr 2013 13:38:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s1024; t=1364823510; bh=6dmaPiIIqLXcCk+0TNO+I1pT5aZDeIfRWemGGk+wJcU=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type; b=v1vkOp4I+O+0qEhmB3EyiTSbjb5pA8D2MGABUkz3nSM6EbZ5D+CkJD+5bY4afXXFfryunMpm2psZoYRBOL7Rus7ggr1XTh1BAtdEXI30h/p+O0lYCkDx+yRqj+kk8SmfXih2mMRDpT9f4itqhfCQ/7m/Dop+apFzjCeC0jHxuTE=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type; b=jcxYxCmQ9CSorY0Sg/y8bPWuDYfgqZzQCd0LNBdSOkmbh6eqz7Q78K0EVX/wpQkW1BlUrqXaHnuoRj3rV64sq8UorAhvttzvpwVAXIPFwR1Lmpi5lRHQm4wIqb1/+wJrMMA4FIATis7bY8WD9uD/ve2nlkC7zGuTsQ+HHzk8KII=;
X-YMail-OSG: yKU6s74VM1mOx.pSSR7Ge8_9EBjBS5za1qyLjl2fM7SPPKU S68pclxcPb5iddH7ZpIXbHY2Ya1G7dxE6D2.Hctjy.Ec4pT.EwmRYQvf2Yod XOLj4F_eN_9ftI3euPaiU1Qbc.TmaAfGVwpTKUM3Oj14pzw7o2rRdy2x39GJ yzDo23wXAU7m2sSf4QboYuYCFOB4Yd0zblHvk5f_IM2.ehgriLbspDj4LsGP 4PHXvmIzIb._.xCNmDirTVZND9gSV5Ur_iFQFBN_vk9DvDRlnZEuCN9FUM9s JARU_.2qjTymEDipdV6w0uqlpQRRJyhqF247kB5_Oth5H0LOY2AT89Xwhd6L ES8alNCG8u4nevQKzullMXmkwIEt841kIEF9KxwlecT.l_6kZZgfQlaxx6cj fNKYS_7aSaYAIj4PsOnAhoEVsmpscKYH9G58.kCURqiH0eVe1QdVeNd2fvna EJsWU8P58x6pq1S2vqGde5UIfNnjp1HT4sMj261FWfGUhZDmBLCF_EQ--
Received: from [2.101.188.34] by web172001.mail.ir2.yahoo.com via HTTP; Mon, 01 Apr 2013 14:38:30 BST
X-Rocket-MIMEInfo: 002.001, PiBTVEVBTTogQk9GIHByb3Bvc2FsIGZvciBCZXJsaW4KPgo.IFlvdSBtYXkgaGF2ZSBub3RpY2VkIGEgcmVjZW50IHRyZW5kIGluIHRoZSBJRVRGIHRvd2FyZHMgdmVyeQo.IGxpZ2h0d2VpZ2h0IHByb3RvY29scyBmb3IgdGhlIEludGVybmV0IG9mIEV2ZXJ5dGhpbmcuID4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtZHJhZnQtZHJhZnQgaXMgdGhlIG1vc3QgZnVsbHkKPiBkZXZlbG9wZWQgcHJvcG9zYWwgb24gdGhlIHRhYmxlIHRvZGF5LiDCoEl0IGlzIGV4dHJlbWVseSBsaWdodHdlaWdodCABMAEBAQE-
X-Mailer: YahooMailWebService/0.8.139.530
Message-ID: <1364823510.43204.YahooMailNeo@web172001.mail.ir2.yahoo.com>
Date: Mon, 1 Apr 2013 14:38:30 +0100 (BST)
From: Diana Raft <drafts1962@yahoo.co.uk>
Subject: Re: STEAM: BOF proposal for Berlin
To: "ietf@ietf.org" <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1242719849-850698416-1364823510=:43204"
X-Mailman-Approved-At: Mon, 01 Apr 2013 08:40:35 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Diana Raft <drafts1962@yahoo.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, 01 Apr 2013 14:54:34 -0000

--1242719849-850698416-1364823510=:43204
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

> STEAM: BOF proposal for Berlin=0A>=0A> You may have noticed a recent tren=
d in the IETF towards very=0A> lightweight protocols for the Internet of Ev=
erything. > http://tools.ietf.org/html/draft-draft-draft is the most fully=
=0A> developed proposal on the table today. =A0It is extremely lightweight =
by=0A> simply using UDP and nothing else.=0A>=0A> Recently, however, that d=
raft has been criticized for lack of=0A> congestion control. =A0And rightly=
 so, because the only way to have=0A> congestion control is to use TCP. =A0=
=0A=0AIs efficiency problem, did not you read draft-draft-draft ?=0A=0A> An=
d, TCP is all you need.=0A> But then, clearly, there aren't enough RFCs abo=
ut TCP yet [RFC4627].=0A> A new WG will therefore develop "Secure TCP Exten=
sions for Application=0A> and Management" (STEAM).=0A>=0A> Again, TCP is al=
l you need, but it hasn't been used for Provisioning=0A> very much yet=0A=
=0AToo complicated Daniel, you always attack my ideas since we twin babies =
together and now you attack even on our birthday.=0A=0AD.Raft (Ms)=0A
--1242719849-850698416-1364823510=:43204
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt"><pre wrap=3D"">&gt; S=
TEAM: BOF proposal for Berlin=0A&gt;=0A&gt; You may have noticed a recent t=
rend in the IETF towards very=0A&gt; lightweight protocols for the Internet=
 of Everything.=0A<a class=3D"moz-txt-link-freetext" href=3D"http://tools.i=
etf.org/html/draft-draft-draft">&gt; http://tools.ietf.org/html/draft-draft=
-draft</a> is the most fully=0A&gt; developed proposal on the table today. =
&nbsp;It is extremely lightweight by=0A&gt; simply using UDP and nothing el=
se.=0A&gt;=0A&gt; Recently, however, that draft has been criticized for lac=
k of=0A&gt; congestion control. &nbsp;And rightly so, because the only way =
to have=0A&gt; congestion control is to use TCP. &nbsp;<br><br>Is efficienc=
y problem, did not you read draft-draft-draft ?<br><br>&gt; And, TCP is all=
 you need.=0A&gt; But then, clearly, there aren't enough RFCs about TCP yet=
 [RFC4627].=0A&gt; A new WG will therefore develop "Secure TCP Extensions f=
or Application=0A&gt; and Management" (STEAM).=0A&gt;=0A&gt; Again, TCP is =
all you need, but it hasn't been used for Provisioning=0A&gt; very much yet=
<br><br>Too complicated Daniel, you always attack my ideas since we twin ba=
bies together and now you attack even on our birthday.<br>   <br>   D.Raft =
(Ms)<br></pre></div></body></html>
--1242719849-850698416-1364823510=:43204--

From Ted.Lemon@nominum.com  Mon Apr  1 08:55:48 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460DA21F8CE2 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 08:55:48 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kfi52DIkKSeZ for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 08:55:47 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id B924B21F8CDF for <ietf@ietf.org>; Mon,  1 Apr 2013 08:55:47 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKUVmuA0OjJbNWBYeqSEEapTUIwuEsij9v@postini.com; Mon, 01 Apr 2013 08:55:47 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5320B1B8239 for <ietf@ietf.org>; Mon,  1 Apr 2013 08:55:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4938F19005C; Mon,  1 Apr 2013 08:55:47 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Mon, 1 Apr 2013 08:55:47 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Diana Raft <drafts1962@yahoo.co.uk>
Subject: Re: STEAM: BOF proposal for Berlin
Thread-Topic: STEAM: BOF proposal for Berlin
Thread-Index: AQHOLu9b9ujB0MHNB0+Duk60QoQffJjB+jmA
Date: Mon, 1 Apr 2013 15:55:47 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077512B86C@mbx-01.win.nominum.com>
References: <1364823510.43204.YahooMailNeo@web172001.mail.ir2.yahoo.com>
In-Reply-To: <1364823510.43204.YahooMailNeo@web172001.mail.ir2.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5261627BF493BC47902D6CFF2628FD7B@nominum.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, 01 Apr 2013 15:55:48 -0000

I thought the DRAFT proposal was very interesting, but it includes RFC2119 =
for a single throw-away bit of normative language.   Port 9?   Please!   Yo=
u already excluded port 9 with the language in the later paragraph on port =
allocation.   So it's blatantly obvious that you are referencing RFC2119 ju=
st to make your draft look cool.

Please take that paragraph out.   Let the proposal stand on its merits.


From swb@internet2.edu  Mon Apr  1 08:57:41 2013
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 2E9CC21F8EBB for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 08:57:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21aHxnN4epQ1 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 08:57:40 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by ietfa.amsl.com (Postfix) with ESMTP id A3D5621F8CEC for <ietf@ietf.org>; Mon,  1 Apr 2013 08:57:40 -0700 (PDT)
Received: from mail140-ch1-R.bigfish.com (10.43.68.232) by CH1EHSOBE001.bigfish.com (10.43.70.51) with Microsoft SMTP Server id 14.1.225.23; Mon, 1 Apr 2013 15:57:40 +0000
Received: from mail140-ch1 (localhost [127.0.0.1])	by mail140-ch1-R.bigfish.com (Postfix) with ESMTP id C8E8A3600E6; Mon,  1 Apr 2013 15:57:39 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.232.165; KIP:(null); UIP:(null); IPV:NLI; H:BLUPRD0810HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 10
X-BigFish: S10(zzda00hdc73hzz1f42h1fc6h1d77h1ee6h1de0h1202h1e76h1d1ah1d2ah1082kzzz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1b1cn1b1bi1155h)
Received: from mail140-ch1 (localhost.localdomain [127.0.0.1]) by mail140-ch1 (MessageSwitch) id 1364831857122796_26160; Mon,  1 Apr 2013 15:57:37 +0000 (UTC)
Received: from CH1EHSMHS017.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.243])	by mail140-ch1.bigfish.com (Postfix) with ESMTP id 11B491A0068;	Mon,  1 Apr 2013 15:57:37 +0000 (UTC)
Received: from BLUPRD0810HT003.namprd08.prod.outlook.com (157.56.232.165) by CH1EHSMHS017.bigfish.com (10.43.70.17) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 1 Apr 2013 15:57:33 +0000
Received: from swbi2mbp.local (67.241.75.185) by pod51019.outlook.com (10.255.125.38) with Microsoft SMTP Server (TLS) id 14.16.287.8; Mon, 1 Apr 2013 15:57:31 +0000
Message-ID: <5159AE69.2050708@internet2.edu>
Date: Mon, 1 Apr 2013 11:57:29 -0400
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: STEAM: BOF proposal for Berlin
References: <1364823510.43204.YahooMailNeo@web172001.mail.ir2.yahoo.com> <8D23D4052ABE7A4490E77B1A012B63077512B86C@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077512B86C@mbx-01.win.nominum.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [67.241.75.185]
X-OriginatorOrg: internet2.edu
Cc: "ietf@ietf.org" <ietf@ietf.org>, Diana Raft <drafts1962@yahoo.co.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: Mon, 01 Apr 2013 15:57:41 -0000

PORT 9 FROM OUTER SPACE


From thierry.moreau@connotech.com  Mon Apr  1 10:11:59 2013
Return-Path: <thierry.moreau@connotech.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2D311E80D1 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 10:11:59 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdHa5Xi-dB32 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 10:11:58 -0700 (PDT)
Received: from mail.connotech.com (connotech.com [76.10.176.241]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD1911E80AE for <ietf@ietf.org>; Mon,  1 Apr 2013 10:11:58 -0700 (PDT)
Received: from [192.168.1.200] (SUDOKU.CONNOTECH-INTERNAL.COM [192.168.1.200]) by mail.connotech.com (Postfix) with ESMTPA id 555D7317B3 for <ietf@ietf.org>; Mon,  1 Apr 2013 13:11:57 -0400 (EDT)
Message-ID: <5159BFDD.60400@connotech.com>
Date: Mon, 01 Apr 2013 13:11:57 -0400
From: Thierry Moreau <thierry.moreau@connotech.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20090608)
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: STEAM: BOF proposal for Berlin
References: <1364813568.23297.YahooMailNeo@web172405.mail.ir2.yahoo.com>
In-Reply-To: <1364813568.23297.YahooMailNeo@web172405.mail.ir2.yahoo.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: Mon, 01 Apr 2013 17:11:59 -0000

Dear Daniel, IETFers:

With regard to security, I'm afraid the proposed scope of work is 
covered to a large extent by a breakthrough patent application titled 
"Defending the namespace" for which the abstract reads:

"This invention is about an global entity oriented declarative 
authentication and security system that can be used in the present and 
future internet based distributed applications and services. An entity 
here refers to an unique object (most likely to be physical or human) or 
aspect that can hardly be duplicated. The system provides both 
authentication and security (A & S). It can be used in areas comprising 
one to one or one to many (OR or AND) content publication or 
distribution so that maximum granularity of access control is made 
possible. Examples comprise 1) A & S in messaging or communication (one 
to one). 2) A & S in publication or distribution or information sharing 
(one to many(OR)). 3) Secured document escrowing (one to many(AND)). 4) 
Declarative just in time A & S for web-services. 5) Copyright protection 
for digital products. 6) Digital cash. 7) Internet based electronic 
voting system. 8) Witnessed digital legal papers. 9) Support large scale 
virtualized virtual private network and its applications. 10) etc."

The reference is the US patent application publication 20040255137.

If the BOF proceeds, at least this will deserve an IPR disclosure.

- Thierry

Daniel Raft wrote:
> STEAM: BOF proposal for Berlin
> 
> You may have noticed a recent trend in the IETF towards very
> lightweight protocols for the Internet of Everything.
> http://tools.ietf.org/html/draft-draft-draft is the most fully
> developed proposal on the table today.  It is extremely lightweight by
> simply using UDP and nothing else.
> 
> Recently, however, that draft has been criticized for lack of
> congestion control.  And rightly so, because the only way to have
> congestion control is to use TCP.  And, TCP is all you need.
> But then, clearly, there aren't enough RFCs about TCP yet [RFC4627].
> A new WG will therefore develop "Secure TCP Extensions for Application
> and Management" (STEAM).
> 
> Again, TCP is all you need, but it hasn't been used for Provisioning
> very much yet.  The main objective of the new WG is therefore an
> informational document for "Secure Provisioning for Applications and
> Management using TCP Reimagined as an Attractive Protocol", SPAM-TRAP.
> 
> We aren't quite sure yet whether STEAM will be in the Security,
> Transport, Application, or Management Areas, or whether it should have
> its own area (EVG for Internet of Everything).  We will use the BOF in
> Berlin to figure out, and to set up the new EVG area in the IETF, and
> to restyle the IETF to "Internet of Everything Task Force".
> 
> One other field that STEAM will be working in is IETF process innovation.
> (We also figure you can't post to the IETF mailing list without
> including at least one process improvement suggestion.  So we make two.)
> 
> 1) You might notice there is no R in STEAM.  This is because we have
> to increase collaboration within a diverse IETF.
> The RTG area already has the ROLL working group, which has been very
> innovative in getting routing protocols to standards track RFC before
> there is even a glimpse of security, applicability or management.
> Doing standardization in smoke-filled backrooms is unhealthy, and
> STEAM has many of the properties needed for a replacement process.
> We don't want to spill the beans just yet, but can already say the
> process innovation will be named in honor of the two WGs, STEAM/ROLL.
> 
> 2) Finally, preparing for the global deployment of the
> Internet-Enabled Smart Grid (IESG), and to further increase diversity,
> we probably want to enable the use of steam-powered typewriters for
> IETF work.
> The STEAM WG will enhance the RFC format and process to allow direct
> publishing from typewritten sheets and scanned printouts of Word
> documents.
> 
> See you at the STEAM BOF in Berlin,
> 
> Daniel Raft
> 
> 


From fgont@si6networks.com  Mon Apr  1 10:59:49 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CAE81F0D1E for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 10:59:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.393
X-Spam-Level: 
X-Spam-Status: No, score=-0.393 tagged_above=-999 required=5 tests=[AWL=2.163,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M22ipfKYLMTX for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 10:59:48 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4F01F0D21 for <ietf@ietf.org>; Mon,  1 Apr 2013 10:59:48 -0700 (PDT)
Received: from [186.134.3.135] (helo=[192.168.123.121]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UMj1A-0003a1-Lw; Mon, 01 Apr 2013 19:59:41 +0200
Message-ID: <51598243.2020109@si6networks.com>
Date: Mon, 01 Apr 2013 09:49:07 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130330230305.0bce91a8@resistor.net>
X-Enigmail-Version: 1.4.6
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: Mon, 01 Apr 2013 17:59:49 -0000

SM,

On 03/31/2013 06:29 AM, SM wrote:
>> 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-04-12. Exceptionally, comments may be
> 
> From Section 6:
> 
>   "In general, the possible mitigations boil down to enforcing on native
>    IPv6 and IPv6 transition/co-existence traffic the same security
>    policies currently enforced for IPv4 traffic, and/or blocking the
>    aforementioned traffic when it is deemed as undesirable."
> 
> My reading of the mitigation is that it comes down to block everything
> IPv6.  The draft seems to treat every network as a military operation
> network.

Please re-read the above paragraph -- you missed the part that says
"...the same security policies".



> In the Section 1:
> 
>   "Native IPv6 support could also possibly lead to VPN traffic leakages
>    when hosts employ VPN software that not only does not support IPv6,
>    but that does nothing about IPv6 traffic.
>    [I-D.ietf-opsec-vpn-leakages] describes this issue, along with
>    possible mitigations."
> 
> I don't understand the relationship between the above and "IPv4-only"
> networks.

Those issues are not present when your network employs v4-only.



> From Section 2:
> 
>  "This means that even if a network is expected to be IPv4-only,
>   much of its infrastructure is nevertheless likely to be
>   IPv6 enabled."
> 
> What is an IPv4-only network?

A network were none of the devices connected to it implement v6.



>   "[CORE2007] is a security advisory about a buffer overflow which
>    could be remotely-exploited by leveraging link-local IPv6
>    connectivity that is enabled by default."
> 
> How is this attack mitigated within the context of the draft?

The reference is meant to illustrate that that even if you think your
network only employs IPv4 (and hence forget about the v6 support), you
could be hit by that.



>   "Additionally, unless appropriate measures are taken, an attacker with
>    access to an 'IPv4-only' local network could impersonate a local
>    router and cause local hosts to enable their 'non-link-local' IPv6
>    connectivity (e.g. by sending Router Advertisement messages),
>    possibly circumventing security controls that were enforced only on
>    IPv4 communications."
> 
> Where is the mitigation for this?

For attacks that employ link-local connectivity, it bolds down to packet
filtering (either by a personal firewall at the host, or by filtering v6
at layer-2) -- this is discussed in the I-D.



> From Section 4:
> 
>   "IPv6 deployments in the Internet are continually increasing"
> 
> I am no longer worried about IPv6 deployment as the OPSEC working group
> has a plan to stop that. :-)
> 
>   'Upstream filtering of transition technologies or situations
>    where a mis-configured node attempts to "provide" native IPv6
>    service on a given network without proper upstream IPv6 connectivity
>    may result in hosts attempting to reach remote nodes via IPv6, and
>    depending on the absence or presence and specific implementation
>    details of "Happy Eyeballs" [RFC6555], there might be a non-trivial
>    timeout period before the host falls back to IPv4 [Huston2010a]
>   [Huston2012].'
> 
> I don't see what "Happy Eyeballs" has to do with operational security.

Happy Eyeballs has to do with what you do when you drop packets. If you
silently drop them, the host may have rely on timeouts rather than
having a positive indication that a packet has been dropped.



>   "For this reason, networks attempting to prevent IPv6 traffic from
>    traversing their devices should consider configuring their local
>    recursive DNS servers to respond to queries for AAAA DNS records with
>    a DNS RCODE of 3 (NXDOMAIN) [RFC1035] or to silently ignore such
>    queries, and should even consider filtering AAAA records at the
>    network ingress point to prevent the internal hosts from attempting
>    their own DNS resolution."
> 
> The above breaks DNS in an attempt to remove everything IPv6 related
> from the network.

Could you please elaborate?



> The title of the draft is "Security Implications of IPv6 on IPv4
> Networks".  The Abstract mentions "IPv4-only" networks.  The
> Introduction Section mentions "networks that are assumed to be
> IPv4-only".

Please see the quotes when we say "'IPv4-only' networks" -- in practice,
there's no such a thing, and you should think v6 security even if you
think/want to run an IPv4-only network.


> I don't understand what this draft is about.

This one I cannot do much about. :-)

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From fgont@si6networks.com  Mon Apr  1 10:59:51 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD161F0D26; Mon,  1 Apr 2013 10:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.474
X-Spam-Level: 
X-Spam-Status: No, score=-1.474 tagged_above=-999 required=5 tests=[AWL=1.081,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxYYQn2uIUui; Mon,  1 Apr 2013 10:59:50 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 7216C1F0D22; Mon,  1 Apr 2013 10:59:50 -0700 (PDT)
Received: from [186.134.3.135] (helo=[192.168.123.121]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UMj1H-0003a4-4e; Mon, 01 Apr 2013 19:59:48 +0200
Message-ID: <515985E1.1000404@si6networks.com>
Date: Mon, 01 Apr 2013 10:04:33 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [OPSEC] Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <51559943.1010703@gmail.com>
In-Reply-To: <51559943.1010703@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: opsec@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, 01 Apr 2013 17:59:51 -0000

Brian,

On 03/29/2013 10:38 AM, Brian E Carpenter wrote:
> 
> My minimal request for this draft is for my name to be removed from
> the Acknowledgements, as I do not think that my comments have been
> acted on.

That has been my intent, and I sent a note before publishing one of the
latest revs to double-check that (not sure if I missed your respond, or
you didn't respond).


> In fact, I think that in its current state, this document is harmful
> to IPv6 deployment. It in effect encourage sites to fence themselves
> into an IPv4-only world. Particularly, it explicitly suggests a
> default/deny approach to IPv6-in-IPv4 tunnels, which would prevent
> the typical "baby steps" first approach to IPv6 deployment.

Sites that implement any kind of security policy employ a "default deny
policy" (for the simple reason that it's safer to open holes than
explicitly close them). The bottom-line is that if your site enforces
any kind of security policy, you should make an explicit decision
regarding what you do with v6, rather than being unaware that it's there
in your network.



> I would like to see the document convey a positive message, suggesting
> that an IPv4 site first decides which IPv6 deployment mechanism it
> will use, and then configures security appropriately (to allow that
> mechanism and block all others).

There's an operational gap here: in many cases, operators have no tools
to enforce security policies on such tunneled traffic.

Besides, when thinking about v6, enterprise networks and the like should
be doing native IPv6 (in which case v6 security controls would be
enforced throughout the network), rather than having each node go their
own way.


> A specific aspect of this is that if a site provides one well-managed
> 6in4 tunnel mechanism, all tunneled IPv6 packets will pass through
> well-defined points where security mechanisms may be applied.

In which case you'd be "enforcing IPv6 security controls", which is
entirely in-line ith what this document is saying.


> We shouldn't imply that not having an IPv6 plan and blocking all IPv6
> by default is a sound strategy.

It's not, and I don't think we're implying that. However, I'd note that
some people are in the position of blocking traffic, or not doing
anything about it. Check for IPv6 support in different security
products, and you might get depressed.

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From wesley.george@twcable.com  Mon Apr  1 11:00:02 2013
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 E2F3321E80A5 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 11:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.463
X-Spam-Level: 
X-Spam-Status: No, score=-1.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Spx3fqXZiiq for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 11:00:02 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 565771F0D12 for <ietf@ietf.org>; Mon,  1 Apr 2013 11:00:01 -0700 (PDT)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.87,387,1363147200"; d="scan'208";a="51632691"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 01 Apr 2013 13:59:33 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Mon, 1 Apr 2013 13:59:41 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 1 Apr 2013 13:59:40 -0400
Subject: RE: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
Thread-Topic: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
Thread-Index: Ac4t8quX1YyVTuRUS42wTRk1oa0NUABDMpdA
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923042CFA4019@PRVPEXVS15.corp.twcable.com>
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130330230305.0bce91a8@resistor.net>
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, 01 Apr 2013 18:00:03 -0000

Since I was the one that provided some of this text and raised the issues i=
t's addressing, I'll take a crack  at responding at a couple of your concer=
ns below.

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> SM
>
>    'Upstream filtering of transition technologies or situations
>     where a mis-configured node attempts to "provide" native IPv6
>     service on a given network without proper upstream IPv6 connectivity
>     may result in hosts attempting to reach remote nodes via IPv6, and
>     depending on the absence or presence and specific implementation
>     details of "Happy Eyeballs" [RFC6555], there might be a non-trivial
>     timeout period before the host falls back to IPv4 [Huston2010a]
>    [Huston2012].'
>
> I don't see what "Happy Eyeballs" has to do with operational security.
[WEG] It doesn't. This is a second-order effect, but IMO an important one. =
If one is attempting to prevent IPv6 from being used on a network in an eff=
ort to "secure" it from IPv6-related vulnerabilities, one must consider the=
 fact that there are multiple IPv6 transition technologies specifically des=
igned to enable IPv6 access on a network that is otherwise without IPv6 con=
nectivity, some that can be used without any coordination from the upstream=
 network admins. It might even "helpfully" try to share its IPv6 service wi=
th other hosts on the network (rogue RAs...). The act of preventing those t=
ransition technologies from passing traffic (by doing things like blocking =
protocol 41, for example) may create IPv6 connectivity that is broken or ot=
herwise impaired, where an end host believes that it has IPv6 connectivity =
via a transition technology when it fact it does not because its transition=
 mechanism is being blocked upstream. Happy Eyeballs attempts to fix this b=
y ensuring that fallbacks to IPv4 happen more rapidly and IPv4 is preferred=
 when issues are detected with IPv6 connectivity. However, it's inappropria=
te to rely on pervasive implementation of Happy Eyeballs as the sole soluti=
on to prevent end host impacts, since the end user may not know that IPv6 i=
s actively being disabled on this network, or that their IPv6 implementatio=
n is otherwise broken. This is a problem that continues to get worse the mo=
re dual-stack content becomes available.
>
>    "For this reason, networks attempting to prevent IPv6 traffic from
>     traversing their devices should consider configuring their local
>     recursive DNS servers to respond to queries for AAAA DNS records
> with
>     a DNS RCODE of 3 (NXDOMAIN) [RFC1035] or to silently ignore such
>     queries, and should even consider filtering AAAA records at the
>     network ingress point to prevent the internal hosts from attempting
>     their own DNS resolution."
>
> The above breaks DNS in an attempt to remove everything IPv6 related
> from the network.
>
[WEG] On a network with the stated goal of providing/allowing no IPv6 conne=
ctivity, AAAA records are effectively useless. Preventing hosts from receiv=
ing AAAA records in order to prevent them from attempting to connect to an =
IPv6 address and failing is not broken DNS.

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 rjsparks@nostrum.com  Mon Apr  1 13:47:03 2013
Return-Path: <rjsparks@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 03DFE21F8BBD; Mon,  1 Apr 2013 13:47:03 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KoB5gfQCQLQV; Mon,  1 Apr 2013 13:47:02 -0700 (PDT)
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 DC81821F8738; Mon,  1 Apr 2013 13:47:01 -0700 (PDT)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r31KkoSQ072419 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Mon, 1 Apr 2013 15:47:01 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5159F239.1060001@nostrum.com>
Date: Mon, 01 Apr 2013 15:46:49 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: 6renum@ietf.org, draft-ietf-6renum-gap-analysis@tools.ietf.org
Subject: Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: gen-art@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, 01 Apr 2013 20:47:03 -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-6renum-gap-analysis-05.txt
Reviewer: Robert Sparks
Review Date: April 1, 2013
IETF LC End Date: April 10,2013
IESG Telechat date: Not yet scheduled for a telechat

Summary: This document is not ready for publication as an Informational RFC.
          It may be on the right track, but there issues both in substance
          and form that need to be addressed.

Major issues:

The document doesn't provide what its title and abstract claim it will 
provide.
For instance, the abstract claims a gap analysis is presented following 
a renumbering
event procedure summary, but neither appear in the draft. There are a 
few places
in the text that say "this is a gap", but usually it's not clear what 
"this" means.

The stated intent is to identify missing capabilities (gaps) and the work
needed to provide them. The document should lay these out very clearly. 
As the
document is currently written, it is difficult to pull out a simple list of
identified gaps. While addressing that, it would help more to provide some
sense of the relative importance of addressing each of the gaps identified.

There are several significant issues with clarity. I will point to the most
difficult in a section below.

----------------------
Minor issues:

The document currently references draft-chown-v6ops-renumber-thinkabout 
several times.
That document is long expired (2006). It would be better to simply 
restate what is
important from that document here and reference it only once in the 
acknowlegements
rather than send the reader off to read it.

RFC4076 seems to say very similar things to this document. Should it 
have been referenced?

Section 5.3 punts discussion of static addresses off to RFC 6866. That 
document was scoped
only to Enterprise Networks. The scope of this document is larger. Are 
there gaps because
of that difference in scope that were missed? Would it make sense to 
summarize any gaps
RFC 6866 identified that are relevant to this document here?

Should section 8 belong to some other document? It looks like 
operational renumbering
advice/considerations, but doesn't seem to be exploring renumbering 
gaps, except for
the very short section 8.2 which says "we need a better mechanism" 
without much explanation.


----------------------
Text needing clarity (more than nits):

Section 4.1, second paragraph: The first sentence needs to be 
simplified. Something like
"Delegation routers may need to renumber themselves with new delegated 
prefixes" perhaps.
The second sentence speaks of "the router renumbering issue" as if it's 
clear which particular
issue you're actually talking about. Is there a gap here? If so, 
consider replacing the entire
paragraph with an explicit description of the gap.

Section 5.1, first bullet, 2nd paragraph: The third sentence (starting 
"In ND protocol,")
makes no sense. The fourth sentence is also hard to parse.

Section 5.1, first bullet. The list below "the impact of ambiguous M/O 
flags" says things like
"there is no standard" and "it is unspecified". I think you are trying 
to say that there is
ambiguity in what's written, not that nothing's written. This entire 
list would benefit from
being recast in terms of what needs to be done (what are the gaps?).

Section 5.2, last paragraph. It's not clear what you are trying to say 
here. Is it simply
that the natural pressures in an ISP make it more likely that an ISP 
would choose to use
DNS names as part of configuration than an enterprise would? If so, can 
you list what some
of those pressures are? What gap is this discussion trying to identify?

Section 6.1, first paragraph, first sentence (starting "For DNS records 
update") - this sentence
does not parse. What is it trying to say, and what's the gap you are 
trying to point to?

Section 6.3, 6th paragraph. "So there's a big gap for configuration 
aggregation" is
unclear. Is it that configuration isn't stored in one place, or that it 
can't be
found through one place, or something different?

Section 7.1 second bullet. Taking this partial quote from RFC4192 
destroyed the meaning
of the sentence. The original sentence said "The suggestion applies" - 
this misquote says
"reducing the delay applies". There's no benefit to quoting 4192 
directly - say what you
mean and reference 4192.


----------------------
Nits/editorial comments:

There are a few sentences ending with "etc." in the document. Please 
consider deleting the
word from the list - it doesn't help each sentence make its point.

Introduction: "Future efforts may be achieved in the future." doesn't 
add anything
to the document. I suggest deleting the sentence.

Section 3.2: Consider deleting "basically" from "an IPAM is basically used"

Section 5.1: draft-ietf-dhc-host-gen-id is no longer new (and it 
definitely will not be
new a few years after this is published as an RFC. Please remove "the 
new IETF DHC WG
document" from the sentence it appears in.

Section 5.1: This sentence "Using these flags, the two separated address 
configuration
modes are somehow correlated." is not clear. ("somehow" isn't going to 
help the reader
in any case). Are you trying to say "This flags provide some degree of 
correlation in
the use of these separate configuration protocols"? Could you rewrite 
this explicitly
identifying gaps?

Section 5.1: Please delete "mainly" from "flags mainly includes"

Section 5.2 (and other places): Is it really the case that router 
operators have to
resort to restarting routers in order to pick up configuration changes 
these days?
RFC2072 pointed to that, and in 1997 it may have been more routine to 
restart, but
for modern systems, that action is more extreme. Surely for something as 
basic as
a cache-clear, restarts are vanishingly rare.

Section 5.3: Instead of "the static address issue" could you say 
"discussing the
problems associated with renumbering hosts with static addresses"?

Section 6, first paragraph: It's not clear what "the entries in the 
site" means.
What's a site and what are entries in this case.  I suggest "then any 
configuration
or data store containing the previous number must be updated." as a 
replacement, and
then say "Some examples include:" and list DNS records and ACLs. 
Consider pointing
forward to the section on DNS Authority listed under "Gaps considered 
unsolvable".
Note that some of those ACLS are going to be on machines under control 
by another
authority, having the same problem you point to for DNS.

Section 6.1: What do you mean by "the major DNS systems". Do you mean 
the major
implementations like BIND?

Section 6.2, first paragraph. This suffers from the ambiguity of the word
"records". You meant it as a verb (DNS writes something down) instead of
a noun (the DNS system contains DNS records). I suggest rewriting this
paragraph to avoid the ambiguity. "While DNS entries contain addresses" -
"Hosts are configured with" - "hosts must update these addreses"

Section 6.2 second paragraph. Please be more clear what you mean by
"DNS lifetimes". You are not trying to refer to the time-to-live of
a DNS record. Rather, you are trying to say how long a bit of configuration
obtained through DHCP should be considered relevant. If there's a gap
(a need for more protocol), please be explicit. You will proabably want
to engage the DHC working group if you are thinking about asking that
DHCP tell you how long DNS server configuration value is good for if you
are really trying to decouple it from the lease time. (Is that what
you're suggesting? If not, then what's the problem?)

Section 6.3, second bullet, second sub-bullet: What does "the entries" mean?
Please be specific. Do you mean "configured addresses or prefixes" or 
something
else? Or is this intended to extend to updating things like DNS zone files?
As written, it is vague.

Section 6.3, last sentence. "It is a big gap currently." What specifically
is the big gap. Is it a lack of a standard protocol for updating 
configurations
so that there won't be some many vendor-private protocols deployed?
Please consider replacing "It" with something explicit.

Seciton 7.1: The first bullet does not parse. If I guess its meaning 
correctly
(that it would be benificial to tell hosts that local DNS has been 
updated and
they may want to make fresh queries), please be careful with the 
wording. The
hosts don't know which names are likely to resolve locally.

Section 7.1, third bullet - This isn't obviously about notification. Why 
is it
in this section? What's the gap this is trying to identify?

Section 7.2 - how is this section helping the document? What are the gaps?

Section 7.3 - again, how is this section helping the document acheive 
its goal?
Would anyone working to close gaps do anything differently if this 
section were
deleted?

Section 9.4 - what is it about these that make them gaps, much less 
unsolvable gaps.
Is this discussion in the wrong section of the document?

Section 10 - The sentence starting "In the LAN" doesn't parse. Did you mean
"may be needed to"?

Section 10, last paragraph: This sentence doesn't make sense. It would 
make more
sense if you replaced "blocking access" with "protecting", but it would 
be even
better to expand the discussion and explain what you mean by interruption.


From sm@resistor.net  Mon Apr  1 14:24:50 2013
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 A858011E80F4 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:24:50 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jsEFtl06XiRn for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:24:49 -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 A2FAD11E80E2 for <ietf@ietf.org>; Mon,  1 Apr 2013 14:24:49 -0700 (PDT)
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 r31LOgiM002668; Mon, 1 Apr 2013 14:24:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1364851487; bh=7UkiGtGbVG9eJN+jffo4E0vLEwm7Z7moOUKNNsBMZzw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=46zasMWA0EXiLhqdJ8OR++povsJwRvLuiSqi9Vo32LhLi3ntVLl8Kpl2YGv3MPXri Tmgf3Bjx5c+KvhLnnpasfK8/0w1rUyyON01JmSZjjPsjJWJQ5BgDjadjEdIWZ7T6q6 rqNj+MqdVbN+kgKhCOy36OaSuToWz8FV3+bNyHMQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1364851487; i=@resistor.net; bh=7UkiGtGbVG9eJN+jffo4E0vLEwm7Z7moOUKNNsBMZzw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iRYM/eZmd4nU7MkTparn7uvvNEiTKVcwppwwXW02vKmZVO3BOtP604Aa48psKospX jf80vxH/PUMDTWFCeiocPL/gH+QUZBO0SbTe7KMvIVa37c4y8YufV2kGcQbJUl5vbO u1MrALxfE0WOfanKwEc09n0VVkxDUzhUOcRBKpAU=
Message-Id: <6.2.5.6.2.20130401124437.0a5a1190@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 01 Apr 2013 13:49:15 -0700
To: Fernando Gont <fgont@si6networks.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
In-Reply-To: <51598243.2020109@si6networks.com>
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net> <51598243.2020109@si6networks.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: Mon, 01 Apr 2013 21:24:50 -0000

Hi Fernando,
At 05:49 01-04-2013, Fernando Gont wrote:
>Please re-read the above paragraph -- you missed the part that says
>"...the same security policies".

I saw that. :-)  I commented on Section 6 first as it's only when I 
reached that part of the document that I saw the trade-off between 
blocking IPv6 traffic and security.

>Those issues are not present when your network employs v4-only.

What's missing is some text in the Introduction section explaining 
that the draft is discussing about IPv4 networks (what is mentioned above).

>A network were none of the devices connected to it implement v6.

If that is the case some of the attacks would not be possible.  The 
scenario the draft discusses about is when there are devices which 
have IPv6 support.  The draft could have an explanation about IPv4 
networks (see previous comment) and then follow it with the first 
sentence of Section 1.  It can then go into a discussion of the 
threats and how to mitigate them.

 From Section 1:

   "filtering IPv6 traffic (whether native or transition/co-existence)
    to mitigate IPv6 security implications on IPv4 networks should
   (generally) only be considered as a temporary measure until IPv6
   is deployed."

It's not a temporary measure in the sense that there is an assumption 
that the network should be IPv4 only.  If the network is to support 
IPv4 and IPv6, filtering of IPv6 traffic is not recommended then.

>The reference is meant to illustrate that that even if you think your
>network only employs IPv4 (and hence forget about the v6 support), you
>could be hit by that.

Ok.

>For attacks that employ link-local connectivity, it bolds down to packet
>filtering (either by a personal firewall at the host, or by filtering v6
>at layer-2) -- this is discussed in the I-D.

I don't see anything about that in the draft.  There is a mention of 
filtering at Layer 2 and Layer 3.

>Happy Eyeballs has to do with what you do when you drop packets. If you
>silently drop them, the host may have rely on timeouts rather than
>having a positive indication that a packet has been dropped.

This is a browser issue.  I'll comment further in another message.

>Could you please elaborate?

The text about DNS (Section 4) is about DNS replies.  What I meant 
was that the draft recommends changing the answer for a (DNS) AAAA 
query in an attempt to stop IPv6 traffic.  It's ok to block IPv6 
traffic as it's an IPv4-only network.  I don't think that it is ok to 
tamper with DNS replies (in this case you are covered by local policy 
and you can do that).

>Please see the quotes when we say "'IPv4-only' networks" -- in practice,
>there's no such a thing, and you should think v6 security even if you
>think/want to run an IPv4-only network.

It might help to reword the Abstract and the Introduction Section so 
that the purpose of the document is clear.  I agree that it is good 
to think IPv6 security even if I want an IPv4-only network.

>This one I cannot do much about. :-)

:-)

Regards,
-sm 


From sm@resistor.net  Mon Apr  1 14:24:54 2013
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 C938121E80C3 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:24:53 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lguB3xU745uG for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:24:52 -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 C3EF711E80F5 for <ietf@ietf.org>; Mon,  1 Apr 2013 14:24:52 -0700 (PDT)
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 r31LOgiO002668; Mon, 1 Apr 2013 14:24:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1364851492; bh=8R7+C3/GKrFU5h0+lMjy/SoqDbsNA1T91B6fW24MlUA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=IVjskLz4boG1VhuTtYN2FV2Bc0v1ZF86KXfEBfJ83uHkQMBBre3+tWrrA3yVeuk7m VVoDASlzsDpdb6+HMzfGZqov6WCGis7sU+REUlcq8dYA+/8Irz9/KvC8siQk/JHLTj H4Z+tEGQxWpvuv+KE14lAoICnQkCR2NXPQm0gQEI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1364851492; i=@resistor.net; bh=8R7+C3/GKrFU5h0+lMjy/SoqDbsNA1T91B6fW24MlUA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TyPyitWIKdFaRmy0+di7ooKDRWumXBOEtchJgyufwOUtxSY4jHUtRrcm26QB76PIY 4iuUvhJKAsdCuwP4xF7uDIWbNrMBZq2JjU5TdYgkslJmu7pmXpjrkVM+JkWbXYyxzG greyeNbAXRg1XtV9/AjMGAyy1FtUcRaMc2/jlLwM=
Message-Id: <6.2.5.6.2.20130401134936.0a5a1420@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 01 Apr 2013 14:14:29 -0700
To: "George, Wes" <wesley.george@twcable.com>
From: SM <sm@resistor.net>
Subject: RE: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923042CFA4019@PRVPEXVS15.corp .twcable.com>
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923042CFA4019@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: Mon, 01 Apr 2013 21:24:54 -0000

At 10:59 01-04-2013, George, Wes wrote:
>Since I was the one that provided some of this text and raised the 
>issues it's addressing, I'll take a crack  at responding at a couple 
>of your concerns below.

Ok.

>[WEG] It doesn't. This is a second-order effect, but IMO an 
>important one. If one is attempting to prevent IPv6 from being used 
>on a network in an effort to "secure" it from IPv6-related 
>vulnerabilities, one must consider the fact that there are multiple 
>IPv6 transition technologies specifically designed to enable IPv6 
>access on a network that is otherwise without IPv6 connectivity, 
>some that can be used without any coordination from the upstream 
>network admins. It might even "helpfully" try to share its IPv6 
>service with other hosts on the network (rogue RAs...). The act of 
>preventing those transition technologies from passing traffic (by 
>doing things like blocking protocol 41, for example) may create IPv6 
>connectivity that is broken or otherwise impaired, where an end host 
>believes that it has IPv6 connectivity via a transition technology 
>when it fact it does not because its transition mechanism is being 
>blocked upstream. Happy Eyeballs attempts to fix this by ensuring 
>that fallbacks to IPv4 happen more rapidly and IPv4 is preferred 
>when issues are detected with IPv6 connectivity. However, it's 
>inappropriate to rely on pervasive implementation of Happy Eyeballs 
>as the sole solution to prevent end host impacts, since the end user 
>may not know that IPv6 is actively being disabled on this network, 
>or that their IPv6 implementation is otherwise broken. This is a 
>problem that continues to get worse the more dual-stack content 
>becomes available.

I agree with the last sentence.  Happy Eyeballs is about the 
HTTP.  There are other applications protocols too. :-)  In the 
context of the draft you have an IPv4 network and you want the 
devices or applications to be IPv4-only.  I see that as configuring 
the applications (there is a browser option for IPv4 only 
access).  There isn't any mis-configured node as the document 
intentionally argues for blocking IPv6 traffic and IPv6 transition 
technologies.

>[WEG] On a network with the stated goal of providing/allowing no 
>IPv6 connectivity, AAAA records are effectively useless. Preventing 
>hosts from receiving AAAA records in order to

Yes.

>  prevent them from attempting to connect to an IPv6 address and 
> failing is not broken DNS.

If there isn't any IPv6 connectivity it is useless to query for AAAA 
RRs as the host is not going to establish an IPv6 
connection.  Instead of looking at the problem from that angle the 
proposal uses a "middlebox" (not the correct term) to change 
things.  Once it becomes best practice to tamper with DNS there is 
one more problem to solve as you can no longer rely on DNS working 
according to specifications.

Regards,
-sm 


From fgont@si6networks.com  Mon Apr  1 14:33:53 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B76321E80D6 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level: 
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[AWL=0.557,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nxhoPhl6-2Ff for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:33:51 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 5DBD421E80A0 for <ietf@ietf.org>; Mon,  1 Apr 2013 14:33:51 -0700 (PDT)
Received: from [186.134.3.135] (helo=[192.168.123.121]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UMmMI-0000Th-JH; Mon, 01 Apr 2013 23:33:42 +0200
Message-ID: <5159FD2A.90305@si6networks.com>
Date: Mon, 01 Apr 2013 18:33:30 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923042CFA4019@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20130401134936.0a5a1420@resistor.net>
In-Reply-To: <6.2.5.6.2.20130401134936.0a5a1420@resistor.net>
X-Enigmail-Version: 1.4.6
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: Mon, 01 Apr 2013 21:33:53 -0000

On 04/01/2013 06:14 PM, SM wrote:
>>  prevent them from attempting to connect to an IPv6 address and
>> failing is not broken DNS.
> 
> If there isn't any IPv6 connectivity it is useless to query for AAAA RRs
> as the host is not going to establish an IPv6 connection.  Instead of
> looking at the problem from that angle the proposal uses a "middlebox"
> (not the correct term) to change things.  Once it becomes best practice
> to tamper with DNS there is one more problem to solve as you can no
> longer rely on DNS working according to specifications.

Welcome to the real world:  That cat has been out of the box for years
(no matter whether you consider that a problem, or a feature).

FWIW, my TP-LINK router does that, even if I don't want it to.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From rjsparks@nostrum.com  Mon Apr  1 14:41:40 2013
Return-Path: <rjsparks@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 95D261F0D1E for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:41:40 -0700 (PDT)
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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDQ4mmFkwfjz for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:41:39 -0700 (PDT)
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 47EA21F0D1D for <ietf@ietf.org>; Mon,  1 Apr 2013 14:41:39 -0700 (PDT)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r31LfYj3078508 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Mon, 1 Apr 2013 16:41:34 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5159FF0E.9080202@nostrum.com>
Date: Mon, 01 Apr 2013 16:41:34 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch? (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu> <6.2.5.6.2.20130328111022.0ceeb7d8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130328111022.0ceeb7d8@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: Burger Eric <eburger@cs.georgetown.edu>, 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, 01 Apr 2013 21:41:40 -0000

On 3/28/13 1:17 PM, SM wrote:
> Hi Eric,
> At 05:13 28-03-2013, Burger Eric wrote:
>> Rather than guessing all of the bad things that could happen, I would 
>> offer it would be better to say what we mean, like:
>>         The IMAP interface MUST NOT provide any IMAP facilities that 
>> modify the underlying message and message metadata, such as mailbox, 
>> flags, marking for deletion, etc. If the client is authenticated and 
>> authorized, the IMAP interface MUST provide per-user marking of the 
>> underlying message as read or flagged.
>
> The IMAP interface is a front-end to the read-only mailboxes 
> (archive).  It's easier to do what is mentioned above.
I'm taking more or less that approach in my working copy (I'll be 
posting -06 soon).
>
>> Something to ponder:
>> I use the IMAP interface once, mark a bunch of things as read, and 
>> then decide never to use the IMAP interface ever again. How long does 
>> the server need to keep my (per-user) marking metadata? E.g., besides 
>> CPU and I/O issues, there is a potentially unbounded storage problem 
>> as well. It is unbounded because in IMAP I can assign any kind of 
>> label (marking) to a message, even ones I make up.
>>
>> One thought for an approach to a solution:
>> 1. per-user markings expire after X time units (six months?)
>> 2. per-user markings may take up at most X storage units (512KB?)
>
> I would go for both.
Instead, I propose that we make it possible to notice an abuser and turn 
off access (this is what -06 will contain).

I don't believe we could come to a consensus on an automatic expiry of 
state - there are use cases I can think of where any short
expiration (like 6-months) would be infuriating.

If keeping this state for normal use turns out to be too expensive for 
us, then we will have learned something, and can start talking about 
future IMAP work in general to help systems mitigate that expense.
>
>> Per-user metadata can be incredibly useful - I might label things by 
>> project, work group, draft, mumble, or foo. I would not want to limit 
>> the labels to red or green. However, we need some predictable limit 
>> as well.
>
> Yes.
>
> Regards,
> -sm


From hartmans@mit.edu  Mon Apr  1 16:49:42 2013
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 3019811E8115 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 16:49:42 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Bhit-jLwNr7 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 16:49:41 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 98B8011E80F8 for <ietf@ietf.org>; Mon,  1 Apr 2013 16:49:41 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 7CA042033A; Mon,  1 Apr 2013 19:48:32 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id A14324497; Mon,  1 Apr 2013 19:49:37 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch?
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu> <6.2.5.6.2.20130328111022.0ceeb7d8@resistor.net> <5159FF0E.9080202@nostrum.com>
Date: Mon, 01 Apr 2013 19:49:37 -0400
In-Reply-To: <5159FF0E.9080202@nostrum.com> (Robert Sparks's message of "Mon,  01 Apr 2013 16:41:34 -0500")
Message-ID: <tsl38v9q0a6.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>, Burger Eric <eburger@cs.georgetown.edu>, 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, 01 Apr 2013 23:49:42 -0000

May I suggest that the specific details of this be left to the
implementation effort.  What is easy to implement in this area depends
significantly on what platform (and here I mean more imap libraries and
imap server technology than say python vs ruby vs .net vs C) A simple
requirement like the implementation should consider how to handle abuse
of message marking.

From abdussalambaryun@gmail.com  Mon Apr  1 17:45:44 2013
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 B293F21F8B16 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 17:45:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YZeSRJNs7IDr for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 17:45:44 -0700 (PDT)
Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2894B21F8B15 for <ietf@ietf.org>; Mon,  1 Apr 2013 17:45:44 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id kl13so1568932pab.18 for <ietf@ietf.org>; Mon, 01 Apr 2013 17:45:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ybyWwyCCK5PXDaSNOu45DkCoI8gsfcFM2LVfueWlh/w=; b=t+9MAAGGI8b2Te/qYKF/6bsK8rTtld4kCM//W7I/MLAmfa2FQKhsrWHMnmAdKDUh0C jO+CqZpKwlm38wURTBBUgV6esD3/e7SaVB+wDOLbkNUyWrM67ozk62xdaTg+w8DggqwX bPbaCIbHE95HDNuk1pZGQhntXKQ8Pluy0LHlZ+sN3/pXDN2ovbXh4gi3+RWZXcZeE679 eb9vrciSJuoi10cxw20J+7m52Od+o10qwD4c9qBJ+vXMy6W8GoYBCCtCKh18Wyr/3U18 fQSpJI4Pm18kje0VevII6h9qF6RP0GQJ9ZrAnT8Gw4TpFENNacMI2om+OK8J01JV4QVx 2D1g==
MIME-Version: 1.0
X-Received: by 10.68.189.234 with SMTP id gl10mr76649pbc.93.1364863543648; Mon, 01 Apr 2013 17:45:43 -0700 (PDT)
Received: by 10.68.33.132 with HTTP; Mon, 1 Apr 2013 17:45:43 -0700 (PDT)
In-Reply-To: <20130401215830.710ADB1E007@rfc-editor.org>
References: <20130401215830.710ADB1E007@rfc-editor.org>
Date: Tue, 2 Apr 2013 02:45:43 +0200
Message-ID: <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: bob.hinden@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, 02 Apr 2013 00:45:44 -0000

RFC6921>It is well known that as we approach the speed of light, time
slows down.
AB> I know that time slows for something when it is in speed of light,
but communication is not something moving. If the packet is in speed
of light we may reduce the comm-delay but never less than zero. The
communication times don't change if at least one communicator is not
moving in light speed.

My comment is that I think this RFC is not logical, and I don't
understand its recommendations. There is no way that a packet can be
received before send, packet-time never changes communicators-time
while the positions of both Tx and Rx are semi-fixed (change is
relative to communicators' times not their signal). I think the
communication-times may change when the communicators are at/above
speed of light not the signal/packet. Is my physics correct?

AB

On 4/1/13, rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org> wrote:
> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 6921
>
>         Title:      Design Considerations for Faster-Than-Light (FTL)
>                     Communication
>         Author:     R. Hinden
>         Status:     Informational
>         Stream:     Independent
>         Date:       1 April 2013
>         Mailbox:    bob.hinden@gmail.com
>         Pages:      7
>         Characters: 15100
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-hinden-FTL-design-considerations-00.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc6921.txt
>
> We are approaching the time when we will be able to communicate
> faster than the speed of light.  It is well known that as we approach
> the speed of light, time slows down.  Logically, it is reasonable to
> assume that as we go faster than the speed of light, time will
> reverse.  The major consequence of this for Internet protocols is
> that packets will arrive before they are sent.  This will have a
> major impact on the way we design Internet protocols.  This paper
> outlines some of the issues and suggests some directions for
> additional analysis of these issues.
>
>
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   http://www.ietf.org/mailman/listinfo/ietf-announce
>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
>

From abdussalambaryun@gmail.com  Mon Apr  1 17:49:47 2013
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 63D3B21F8F9F for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 17:49:47 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rX6v+iHQWqDT for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 17:49:46 -0700 (PDT)
Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) by ietfa.amsl.com (Postfix) with ESMTP id B836721F8B27 for <ietf@ietf.org>; Mon,  1 Apr 2013 17:49:46 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id kp14so1562199pab.22 for <ietf@ietf.org>; Mon, 01 Apr 2013 17:49:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Ifk3RCCqzYw/vrelZvQVFqJcMSgP4Mk/II0TVK5W5WE=; b=NsltZErgiBQ/wtlYzVoBI+MW4ibpl0B/ioo4zVj1yVoWKAk1o+KGSB0WR+wSm4LTuP L8+whSsjmk2roiaTZU7T9ULza0FMWUfQjeHB1SY1CMgzhktM/Hz43anQ/bFGZEmnytmN BF3GK0+7yqLq/jc4zukiDoMrg1KVNA/BvCiWjBp1Av6LzjxHSLYKgvwlXGyhg3KCtzJx VSlD/Qmy+0gntpzBEOjWZQjID5tDGfWqgerqFa5HcI9nTcGq/twefyouTcxvmVZYZ+/c gGJrZRLWi+qS4WB0IdciVHrGB4y+z3V/DCBSZ0G5Uzf37ni/PaYjjhDDH31lb30Pl8IF /RlQ==
MIME-Version: 1.0
X-Received: by 10.68.237.100 with SMTP id vb4mr21279910pbc.202.1364863786528;  Mon, 01 Apr 2013 17:49:46 -0700 (PDT)
Received: by 10.68.33.132 with HTTP; Mon, 1 Apr 2013 17:49:46 -0700 (PDT)
In-Reply-To: <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>
Date: Tue, 2 Apr 2013 02:49:46 +0200
Message-ID: <CADnDZ89Eu_FvyUOF30tTAyJm8FJdN39ZBx9HSux2t4HHFtxaiA@mail.gmail.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: bob.hinden@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, 02 Apr 2013 00:49:47 -0000

Delete
>The communication times don't change if at least one communicator is not
> moving in light speed.

AB> I meant the communication times MAY change if at least one
communicator is moving in light speed.


On 4/2/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> RFC6921>It is well known that as we approach the speed of light, time
> slows down.
> AB> I know that time slows for something when it is in speed of light,
> but communication is not something moving. If the packet is in speed
> of light we may reduce the comm-delay but never less than zero. The
> communication times don't change if at least one communicator is not
> moving in light speed.
>
> My comment is that I think this RFC is not logical, and I don't
> understand its recommendations. There is no way that a packet can be
> received before send, packet-time never changes communicators-time
> while the positions of both Tx and Rx are semi-fixed (change is
> relative to communicators' times not their signal). I think the
> communication-times may change when the communicators are at/above
> speed of light not the signal/packet. Is my physics correct?
>
> AB
>
> On 4/1/13, rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org> wrote:
>> A new Request for Comments is now available in online RFC libraries.
>>
>>
>>         RFC 6921
>>
>>         Title:      Design Considerations for Faster-Than-Light (FTL)
>>                     Communication
>>         Author:     R. Hinden
>>         Status:     Informational
>>         Stream:     Independent
>>         Date:       1 April 2013
>>         Mailbox:    bob.hinden@gmail.com
>>         Pages:      7
>>         Characters: 15100
>>         Updates/Obsoletes/SeeAlso:   None
>>
>>         I-D Tag:    draft-hinden-FTL-design-considerations-00.txt
>>
>>         URL:        http://www.rfc-editor.org/rfc/rfc6921.txt
>>
>> We are approaching the time when we will be able to communicate
>> faster than the speed of light.  It is well known that as we approach
>> the speed of light, time slows down.  Logically, it is reasonable to
>> assume that as we go faster than the speed of light, time will
>> reverse.  The major consequence of this for Internet protocols is
>> that packets will arrive before they are sent.  This will have a
>> major impact on the way we design Internet protocols.  This paper
>> outlines some of the issues and suggests some directions for
>> additional analysis of these issues.
>>
>>
>> INFORMATIONAL: This memo provides information for the Internet community.
>> It does not specify an Internet standard of any kind. Distribution of
>> this memo is unlimited.
>>
>> This announcement is sent to the IETF-Announce and rfc-dist lists.
>> To subscribe or unsubscribe, see
>>   http://www.ietf.org/mailman/listinfo/ietf-announce
>>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>
>> For searching the RFC series, see
>> http://www.rfc-editor.org/rfcsearch.html.
>> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
>>
>> Requests for special distribution should be addressed to either the
>> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
>> specifically noted otherwise on the RFC itself, all RFCs are for
>> unlimited distribution.
>>
>>
>> The RFC Editor Team
>> Association Management Solutions, LLC
>>
>>
>>
>

From sm@resistor.net  Mon Apr  1 19:05:08 2013
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 C6BC321F9005 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 19:05:08 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DL3Fmk15JSg1 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 19:05:08 -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 0F3B121F9003 for <ietf@ietf.org>; Mon,  1 Apr 2013 19:05:07 -0700 (PDT)
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 r32252oK011524 for <ietf@ietf.org>; Mon, 1 Apr 2013 19:05:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1364868307; bh=h6YB6ezMrF3O2tGbSXoC7nqwihnwNqZ+asLCUBMIRz4=; h=Date:To:From:Subject:In-Reply-To:References; b=l1N4eGXBwgzVm05q07Xp4ruIhngnMSBR9qlrFpit4P6TkXON3vW7wSca7gEs/Ipql rvfw492u8pPD5fum5kTabip6U/S9CDIUGMNvZ4dVX1Tz+aNcazT/zQ6r2Ui+xocvLy aUl/S0ESmoB/G+466+pbVsAASZvXIVoNXRNI25ac=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1364868307; i=@resistor.net; bh=h6YB6ezMrF3O2tGbSXoC7nqwihnwNqZ+asLCUBMIRz4=; h=Date:To:From:Subject:In-Reply-To:References; b=uFWSC/rEM1DrkePgrVhsqHfgICkv9kSLXZflCvwAfAoN3GaNQPGcXD2/UHB7wK/wk uQl4i0VxFmHxJCJJ9qEbeU0Gk3anpX3RNwb6gCgg2mFz2LV/yedzdjbcZR8Nd+dkxb V+bDaJ5+iSvU/fvQXEz2CKyY3q9TxnlnJZn4m50E=
Message-Id: <6.2.5.6.2.20130401181647.0a702300@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 01 Apr 2013 18:49:14 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
In-Reply-To: <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.g mail.com>
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.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: Tue, 02 Apr 2013 02:05:08 -0000

The words in this message are to be interpreted as described in RFC 6919.

Here are some considerations for Faster-Than-Light Communication (see 
RFC 6921).

  *  Bring value when you send a message.  Do not seek value.

     Value-seeking questions such as, "What are you doing tonight?" make people
     sound too needy and also fail to inspire any emotion in the person whom
     they are communicating with.

  *  Avoid sending too many messages.

     This is meant to keep someone who is interested in a person from sounding
     too desperate or like they have no reason to live other than to 
send messages.

  *  Keep it simple, stupid.

     The whole point of communicating with a person is to make the 
person get the
     point without being long-winded, which can be boring.

Regards,
-sm


From jari.arkko@piuha.net  Mon Apr  1 22:11:40 2013
Return-Path: <jari.arkko@piuha.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 19D9E21F983E for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 22:11:40 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJSFccLgI+-u for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 22:11:39 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id D34A621F983C for <ietf@ietf.org>; Mon,  1 Apr 2013 22:11:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2B5672CC4A; Tue,  2 Apr 2013 08:11:38 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeK_16j-zjJl; Tue,  2 Apr 2013 08:11:37 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 2353D2CC55; Tue,  2 Apr 2013 08:11:37 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: team to look at diversity
Date: Tue, 2 Apr 2013 07:06:10 +0200
Message-Id: <E41A7C0D-470D-4480-824F-2AA8CFAB3677@piuha.net>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Apr 2013 05:11:40 -0000

I have an update relating to the diversity discussions we've had on the =
list and at IETF-86. I promised that I'd set up a design team. I have =
found two people to lead such a design team: Kathleen Moriarty and =
Suresh Krishnan. Thank you volunteering to lead this!

Please contact them if you are interested in contributing to the work. I =
have given them an open assignment, with a desire to get advice on what =
steps we could take to increase participation in various aspects of the =
IETF, hoping for some initial advice before the next IETF. The leaders =
will determine how they want to run the team and who to select to it, =
but the writeup below is my input for setting the stage and some scope =
for the work. The design team will present their recommendations to the =
community, and engage in the discussion. Recommendations with community =
support will be taken forward. The creation of this team should not stop =
other efforts or proposals from going forward. For instance, there is an =
independent effort in looking at improvements in mentoring.

Jari Arkko

-----
For the purposes of this team, we think of diversity as something that =
covers international participation, different cultures, gender, age, =
organisational background, and so on. While the IETF has become a very =
international organisation (with participants from 60 countries working =
on documents, for instance), there are many aspects of diversity where =
we could do much better. Overall participation is concentrated in some =
areas of the world, with little participation from Africa and South =
America, for instance. Similarly, while the IETF has some very active =
female participants and leadership members, the numbers are very small. =
Much of the work in the IETF is driven by large networking companies, =
yet academia and small companies would have more to give, and =
operational experience from additional operators would be similarly =
appreciated. Importantly, these disparities appear most prominently in =
our leadership, where institutional and structural issues can lead to =
even less diversity along all of the above mentioned axes than in our =
general population. All organisations benefit from a healthy influx of =
new participants at all levels, and in the IETF we need that to balance =
our well-established topics and participants, to build the next =
generation technologies, experts, and leaders.

These issues are of course related to general engineering and industry =
issues, and are a source of discussions in other similar organisations. =
But we should not attempt to show how we match or do not match the =
general patterns. We should rather just make the observation that =
additional diversity would be beneficial to IETF and improve its =
results.

The diversity team is a design team tasked with understanding the issues =
we are facing, drawing in experience from other organizations affected =
by similar issues, identifying obstacles to us having the widest breadth =
of talented participants and leaders, and making practical =
recommendations that could help us improve the situation. It is =
understood that many improvements may only take effect long-term, such =
as drawing in more participants from areas of the world where the IETF =
has traditionally not had much participation. Nevertheless, a set of =
actionable steps would be useful.

The diversity team is not charged with evaluating the particulars of =
current or past Nominations Committee (Nomcom) decisions, and any =
discussion of ongoing NomCom activities is out of scope. The NomCom is =
expected to continue to do its utmost to recruit and appoint a top-notch =
and well-rounded set of people to our leadership. The diversity team =
will make recommendations on actions we can take going forward, both to =
increase diversity of IETF as a whole, and to help future NomComs (and =
other bodies selecting people) address issues of diversity in our =
leadership.

From yangkun2005@gmail.com  Mon Apr  1 22:47:05 2013
Return-Path: <yangkun2005@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 5256721F9863 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 22:47:05 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVcUeaNsG88B for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 22:47:05 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id E3E6A21F9861 for <ietf@ietf.org>; Mon,  1 Apr 2013 22:47:04 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id ef5so47613obb.13 for <ietf@ietf.org>; Mon, 01 Apr 2013 22:47:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=txf5TxYNS3rVkMI1Wj4KmUmF3Oml6w0bNaB2pRInK+c=; b=ArWqdM6b+d1QpWp+Lfb2hMv36rJbSysUGGME0nDTt9lVvygPUQCn8YxNZ5ZE3GZxP9 vbBKTW7aZAIsxi2kpjQgki4e0bF4rWyumVJIMEuxHUb95/OoHT2IPAmDfpIF7y54FUwP msMbZrOdliNfui8BD/2Rmco0JGphxBijPjAOJ1e2SXWss+V9EnldqYO794wUD0l/BVnP F8ftI5tinmOty1PEb1sRSClhckhQEElpfgkk5PPHGQpzvemwT/KB2rp3o34mvdogEgrQ CHrMt0TjG5yKKTXu2cept5uTl30YhBMJbRjfoM2pvoVr0+A5GZMYonK6aGPb86nUVaB2 8npw==
MIME-Version: 1.0
X-Received: by 10.60.63.73 with SMTP id e9mr2769779oes.87.1364881624474; Mon, 01 Apr 2013 22:47:04 -0700 (PDT)
Received: by 10.182.12.36 with HTTP; Mon, 1 Apr 2013 22:47:04 -0700 (PDT)
Date: Tue, 2 Apr 2013 13:47:04 +0800
Message-ID: <CAAby8wRoebOF+wDR0Z=p6Rfza23fvWh3niCvoicPd2=aYuHOVg@mail.gmail.com>
Subject: Re: draft-guo-idoca-with-the-html-file-format-00
From: Kun Yang <yangkun2005@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a11c21d1a6378d604d95a4440
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Apr 2013 05:47:05 -0000

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

Dear Mr. Guo,

This I-D is a good idea. It is the first time I hear about the idea of
IDOCA (Interconnection and Interoperability of Cloud-Office Application)
with the html file format. If this idea comes true, it will be beneficial
to all cloud-office user. However, the problem of security will arise with
the interconnection and the interoperability, but the solution for it is
not specific in this I-D. Maybe deeper discusses need to be made.

Kun

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

<div dir=3D"ltr">Dear Mr. Guo,<div><br></div><div style>This I-D is a good =
idea. It is the first time I hear about the idea of IDOCA (Interconnection =
and Interoperability of Cloud-Office Application) with the html file format=
. If this idea comes true, it will be beneficial to all cloud-office user. =
However, the problem of security will arise with the interconnection and th=
e interoperability, but the solution for it is not specific in this I-D. Ma=
ybe deeper discusses need to be made.</div>
<div style><br></div><div style>Kun</div><div style><br></div><div style><b=
r></div></div>

--001a11c21d1a6378d604d95a4440--

From cabo@tzi.org  Mon Apr  1 23:10:04 2013
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 780E521F8D6E for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 23:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pRnw0kgSokQg for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 23:10:03 -0700 (PDT)
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 072AF21F9855 for <ietf@ietf.org>; Mon,  1 Apr 2013 23:09:59 -0700 (PDT)
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.4/8.14.4) with ESMTP id r3269vKe018871; Tue, 2 Apr 2013 08:09:57 +0200 (CEST)
Received: from [192.168.217.105] (p54894F4F.dip.t-dialin.net [84.137.79.79]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id CDDC83BC3; Tue,  2 Apr 2013 08:09:56 +0200 (CEST)
Subject: Re: team to look at diversity
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <E41A7C0D-470D-4480-824F-2AA8CFAB3677@piuha.net>
Date: Tue, 2 Apr 2013 08:09:55 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C001659D-B342-4D84-9361-D617AF33BE4B@tzi.org>
References: <E41A7C0D-470D-4480-824F-2AA8CFAB3677@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org 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: Tue, 02 Apr 2013 06:10:04 -0000

Jari,

this is great news.  A design team approach may be able to collect
information and generate ideas and actionable points in a way that
works much better than ranting on the IETF list.

The most important insight is that diversity is not a "problem" that
can be "fixed" by some set of measures, but a process that needs to be
ongoing.

Of course, that process can still be supported by specific measures,
and you have to have a diverse view to find out what might work.

I would like to pick two items here.  Both are not going to help for
all dimensions of diversity, or "fix the diversity problem", but it's
the small steps that will make a difference.  My items are:

-- Reducing situations that are perceived as hostile by members of
   specific groups.

-- Working on incentive structures that are useful for diverse groups.

Re hostility: I think most of us like to think they know what this
means for gender, ethnicity (but we sure can still get a lot better in
acting on that knowledge, and in increasing consciousness).  We are
not always very good at accommodating people with limited command of
the English language (yesterday's "Diana Raft" thing was great comic
relief here) -- keeping the process efficient is one thing, being
insensitive clods another.  Some groups think they know it all and
dismiss input from other groups in an aggressive way (folks:
"academic" is not a pejorative!).  I don't even know what other people
might perceive as hostile; that would be good input for the design
team.

Re incentives: Just an example that I happen to know about: academia
has a need for authorship recognition -- but that need is regularly
dismissed by people that come from different groups (in a way that
feels like utter contempt, back to the hostility point).  What can we
improve with respect to the incentive structures for other groups,
say, people from operators or from small businesses?  Again, something
that people from the various groups could contribute their thoughts
about toward the design team.

I'm not trying to make the design team the "diversity ombudsman", but
providing a somewhat sensitive and possibly confidential atmosphere
for offering thoughts like these might help.

Gr=FC=DFe, Carsten


From susielu25@gmail.com  Mon Apr  1 23:36:24 2013
Return-Path: <susielu25@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 9218A21F9879 for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 23:36:24 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ytuicz0im65S for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 23:36:24 -0700 (PDT)
Received: from mail-ia0-x22f.google.com (mail-ia0-x22f.google.com [IPv6:2607:f8b0:4001:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id B32B321F986B for <ietf@ietf.org>; Mon,  1 Apr 2013 23:36:23 -0700 (PDT)
Received: by mail-ia0-f175.google.com with SMTP id e16so65788iaa.20 for <ietf@ietf.org>; Mon, 01 Apr 2013 23:36:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=QZHjjW8zlPiYFDBIEy4up+fRibY2vwP67CVm8lqYfcQ=; b=dbrEfz2aAtCXIdLOdTNmlxeeSM8M7vWcIV9S7lbP2Nf+xQyUaXRiRWORjG9UtvewVO W2bMWL3KZg1Q9+jNQpElODSwABxovG8Zxz3wou9BYYv6uvhCOo/kSAGrRB9xXgdc2PMH UTE84Naut74ceeAISpTnGQBCOQKTQe8+23V07iXk8N/GF3WYAIAGQjx9lEmc1t3DumCr e5hAM8eBw/iqKEjrUHT/NP5/6yA+m/vj2E1ZiB9i5dPiwz1V+N8PG6ndWEd/biIn1nD+ UMErr0FcsyOJJcYR3sVBwam2vkxJhGPFUIDeZGbbL7uiFDi/0rlR85rkk2IepjuPMB4r LNHQ==
MIME-Version: 1.0
X-Received: by 10.50.33.139 with SMTP id r11mr4670981igi.63.1364884583309; Mon, 01 Apr 2013 23:36:23 -0700 (PDT)
Received: by 10.50.112.71 with HTTP; Mon, 1 Apr 2013 23:36:23 -0700 (PDT)
In-Reply-To: <CAAby8wRoebOF+wDR0Z=p6Rfza23fvWh3niCvoicPd2=aYuHOVg@mail.gmail.com>
References: <CAAby8wRoebOF+wDR0Z=p6Rfza23fvWh3niCvoicPd2=aYuHOVg@mail.gmail.com>
Date: Tue, 2 Apr 2013 14:36:23 +0800
Message-ID: <CADVOzF5rWr2=bnSTyG8jKpkUdU=SQFD=_z+PO061vCZW4+kEaA@mail.gmail.com>
Subject: Re: draft-guo-idoca-with-the-html-file-format-00
From: Susie Lu <susielu25@gmail.com>
To: Kun Yang <yangkun2005@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04462dd6bf6a5604d95af47d
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, 02 Apr 2013 06:36:24 -0000

--f46d04462dd6bf6a5604d95af47d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Yes=EF=BC=8CI think this idea very goog too, But how to make various softwa=
re
vendors agree to do so ?Especially in larger companies ,such as google
docs, office365,why they to do so ?where they do the interest in this=EF=BC=
=9FAnd
finally the implementation of the technology is who is going to achieve?


Susie


On Tue, Apr 2, 2013 at 1:47 PM, Kun Yang <yangkun2005@gmail.com> wrote:

> Dear Mr. Guo,
>
> This I-D is a good idea. It is the first time I hear about the idea of
> IDOCA (Interconnection and Interoperability of Cloud-Office Application)
> with the html file format. If this idea comes true, it will be beneficial
> to all cloud-office user. However, the problem of security will arise wit=
h
> the interconnection and the interoperability, but the solution for it is
> not specific in this I-D. Maybe deeper discusses need to be made.
>
> Kun
>
>
>

--f46d04462dd6bf6a5604d95af47d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yes=EF=BC=8CI think this idea very goog too, But how to ma=
ke various software vendors agree to do so ?Especially in larger companies =
,such as google docs, office365,why they to do so ?where they do the intere=
st in this=EF=BC=9FAnd finally the implementation of the technology is who =
is going to achieve?<div>
<br></div><div><br></div><div style>Susie</div></div><div class=3D"gmail_ex=
tra"><br><br><div class=3D"gmail_quote">On Tue, Apr 2, 2013 at 1:47 PM, Kun=
 Yang <span dir=3D"ltr">&lt;<a href=3D"mailto:yangkun2005@gmail.com" target=
=3D"_blank">yangkun2005@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"><div dir=3D"ltr">Dear Mr. Guo,<div><br></div=
><div>This I-D is a good idea. It is the first time I hear about the idea o=
f IDOCA (Interconnection and Interoperability of Cloud-Office Application) =
with the html file format. If this idea comes true, it will be beneficial t=
o all cloud-office user. However, the problem of security will arise with t=
he interconnection and the interoperability, but the solution for it is not=
 specific in this I-D. Maybe deeper discusses need to be made.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div><div>Kun</div><div><br></div><div><br></div></font></span></=
div>
</blockquote></div><br></div>

--f46d04462dd6bf6a5604d95af47d--

From brian.e.carpenter@gmail.com  Tue Apr  2 02:45:28 2013
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 D4EC921F9858; Tue,  2 Apr 2013 02:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.48
X-Spam-Level: 
X-Spam-Status: No, score=-101.48 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IP_ADDR=1.119, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 72pC3uAcsPxg; Tue,  2 Apr 2013 02:45:28 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id AA1B821F9850; Tue,  2 Apr 2013 02:45:27 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id c10so2972609wiw.0 for <multiple recipients>; Tue, 02 Apr 2013 02:45:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XRgv9LTx9/KXB2UTkDmdxcNEuuw5ZUIgIC8IDRIYeoo=; b=XsF5aKFPjXREIU7Niaa4faHdNrUi7SqZNTqKb3G+p6oUKWNNq4CNBK5KAMrCLr61wJ gOEPzWOLp/SSkn19NaPNuT5NpPuOGHUZYJLcLJHMBfi84I6sIpVSP3nvUnDtai2j29Yj 4DZFqOk9bus7El+wewaUxyVvWXhB1RLOxukZHfWYad1iHxA+cPcg/Mb3EON8OMfc0b6k B+B625JeriNCnv0c2uRYiIwDmdxLJuMHuPP0oLouftjCmnrwALhBMY9O2hLzImzSjsv8 3dAqZE2WtXG5JrZ6N6rNHaodvdjxJv9DLjtiA2B09hqyA4mYPvOVqHtK/HTUmaUvnaXF G5Bw==
X-Received: by 10.194.220.70 with SMTP id pu6mr20384298wjc.27.1364895923349; Tue, 02 Apr 2013 02:45:23 -0700 (PDT)
Received: from [128.232.110.128] (c128.al.cl.cam.ac.uk. [128.232.110.128]) by mx.google.com with ESMTPS id er1sm17900398wib.5.2013.04.02.02.45.21 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 02:45:22 -0700 (PDT)
Message-ID: <515AA8B4.5020707@gmail.com>
Date: Tue, 02 Apr 2013 10:45:24 +0100
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: Fernando Gont <fgont@si6networks.com>
Subject: Re: [OPSEC] Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <51559943.1010703@gmail.com> <515985E1.1000404@si6networks.com>
In-Reply-To: <515985E1.1000404@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: opsec@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, 02 Apr 2013 09:45:28 -0000

Fernando,

Rather than repeating myself, I'll suggest a change to the Introduction
that would (IMHO) improve the message:

OLD:

1.  Introduction

   Most general-purpose operating systems implement and enable native
   IPv6 [RFC2460] support and a number of transition/co-existence
   technologies by default.  For cases in which the corresponding
   devices are deployed on networks that are assumed to be IPv4-only,

NEW:

1.  Introduction

   Most general-purpose operating systems implement and enable native
   IPv6 [RFC2460] support and a number of transition/co-existence
   technologies by default [RFC6434]. Support of IPv6 by all nodes is
   intended to become best current practice [RFC6540]. As a result,
   networks will need to plan for and deploy IPv6 and its security
   mechanisms. Some enterprise networks might, however, choose to delay
   active use of IPv6. For networks that are assumed to be IPv4-only,

It would be nice to refer to draft-ietf-v6ops-enterprise-incremental-ipv6
but I think that is too far from RFC publication to be very useful.

Regards
   Brian

On 01/04/2013 14:04, Fernando Gont wrote:
> Brian,
> 
> On 03/29/2013 10:38 AM, Brian E Carpenter wrote:
>> My minimal request for this draft is for my name to be removed from
>> the Acknowledgements, as I do not think that my comments have been
>> acted on.
> 
> That has been my intent, and I sent a note before publishing one of the
> latest revs to double-check that (not sure if I missed your respond, or
> you didn't respond).
> 
> 
>> In fact, I think that in its current state, this document is harmful
>> to IPv6 deployment. It in effect encourage sites to fence themselves
>> into an IPv4-only world. Particularly, it explicitly suggests a
>> default/deny approach to IPv6-in-IPv4 tunnels, which would prevent
>> the typical "baby steps" first approach to IPv6 deployment.
> 
> Sites that implement any kind of security policy employ a "default deny
> policy" (for the simple reason that it's safer to open holes than
> explicitly close them). The bottom-line is that if your site enforces
> any kind of security policy, you should make an explicit decision
> regarding what you do with v6, rather than being unaware that it's there
> in your network.
> 
> 
> 
>> I would like to see the document convey a positive message, suggesting
>> that an IPv4 site first decides which IPv6 deployment mechanism it
>> will use, and then configures security appropriately (to allow that
>> mechanism and block all others).
> 
> There's an operational gap here: in many cases, operators have no tools
> to enforce security policies on such tunneled traffic.
> 
> Besides, when thinking about v6, enterprise networks and the like should
> be doing native IPv6 (in which case v6 security controls would be
> enforced throughout the network), rather than having each node go their
> own way.
> 
> 
>> A specific aspect of this is that if a site provides one well-managed
>> 6in4 tunnel mechanism, all tunneled IPv6 packets will pass through
>> well-defined points where security mechanisms may be applied.
> 
> In which case you'd be "enforcing IPv6 security controls", which is
> entirely in-line ith what this document is saying.
> 
> 
>> We shouldn't imply that not having an IPv6 plan and blocking all IPv6
>> by default is a sound strategy.
> 
> It's not, and I don't think we're implying that. However, I'd note that
> some people are in the position of blocking traffic, or not doing
> anything about it. Check for IPv6 support in different security
> products, and you might get depressed.
> 
> Cheers,

From brian.e.carpenter@gmail.com  Tue Apr  2 02:58:44 2013
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 D910121F97A6; Tue,  2 Apr 2013 02:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.48
X-Spam-Level: 
X-Spam-Status: No, score=-101.48 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IP_ADDR=1.119, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yt7JYDKMwFsg; Tue,  2 Apr 2013 02:58:44 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E07AC21F9776; Tue,  2 Apr 2013 02:58:14 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id u12so179306wey.33 for <multiple recipients>; Tue, 02 Apr 2013 02:58:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=sn/5PJyrWKgXR2Yr614/5IZ0Wx5Bb9oYiO+TYeHmQnI=; b=VEpnfDuuQD/pYpfOM3xOejxmcSNxgJmp5ZDwGKmB8/MKXKWnCsuLPJ3Wp7aZ9iKgOq b85yhPcDJtRn/36G2l8iY/gQUFMrmpl1oyTSOzMd+09kKGqBL+fCMcV2z1eKtgMP8hIa xmBmz/mUDQqn0RMV/E7QxYhaivRytXZLJcpSi0qZ6ZCOUS8aLNdC9FItXb53YM0OaEww DqjNsm0MYPBI8VERhmwmS3sgXaOXKDtOGB8Dhu86H4lFRgMZ5dZQxdFDs1MJsRijNQPx TiiFyW37jA/duxSBTgjlNH4QtfcODtQNySBqI/ICyCzQSGN+3nFy5O6sgQp0r/Ap4Wh3 Wa2A==
X-Received: by 10.194.89.169 with SMTP id bp9mr20469780wjb.57.1364896691847; Tue, 02 Apr 2013 02:58:11 -0700 (PDT)
Received: from [128.232.110.128] (c128.al.cl.cam.ac.uk. [128.232.110.128]) by mx.google.com with ESMTPS id bk1sm1494604wib.2.2013.04.02.02.58.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 02:58:11 -0700 (PDT)
Message-ID: <515AABB5.5050202@gmail.com>
Date: Tue, 02 Apr 2013 10:58:13 +0100
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: "Liubing (Leo)" <leo.liubing@huawei.com>
Subject: Re: [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
References: <5159F239.1060001@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Apr 2013 09:58:45 -0000

Just picking a couple of points for further comment:

On 02/04/2013 08:46, Liubing (Leo) wrote:
> Hi, Robert
...

>> -----Original Message-----
>> From: Robert Sparks [mailto:rjsparks@nostrum.com]

...
>> The document currently references
>> draft-chown-v6ops-renumber-thinkabout
>> several times.
>> That document is long expired (2006). It would be better to simply
>> restate what is
>> important from that document here and reference it only once in the
>> acknowlegements
>> rather than send the reader off to read it.
> 
> [Bing] draft-chown-v6ops-renumber-thinkabout is an important input for the gap analysis. Although the draft is expired, most of the content are still valid. 
> draft-chown is a more comprehensive analysis, while the gap draft is focusing on gaps in enterprise renumbering. So it might not easy to abstract several points as important from draft-chown to this draft. We actually encourage people to read it.

Robert is right, though, sending people to a long-expired draft is a bad idea.
Of course we have to acknowledge it, but maybe we should pull some of its text
into an Appendix.

Tim Chown, any opinion?

>> RFC4076 seems to say very similar things to this document. Should it
>> have been referenced?
> 
> [Bing] RFC4076 is a more specific case of stateless-DHCPv6 [RFC3736], which might not be common usage in enterprise. But sure we can consider reference it. 

Yes, and check if it identifies any gaps that we should mention.

Bing: we should also add a reference to RFC 4085 "Embedding Globally-Routable
Internet Addresses Considered Harmful" which I missed for RFC 6866.

>> Section 5.3 punts discussion of static addresses off to RFC 6866. That
>> document was scoped
>> only to Enterprise Networks. The scope of this document is larger. 

As Bing said, the *intended* scope is enterprise networks. We should
add that in the Abstract and Introduction. Indeed, many of the points
are more general.

Thanks again Robert!

   Brian

From l.wood@surrey.ac.uk  Tue Apr  2 03:45:14 2013
Return-Path: <l.wood@surrey.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 5EB8B21F983B for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 03:45:14 -0700 (PDT)
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, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vq4Gyd8gSxhi for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 03:45:13 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.171]) by ietfa.amsl.com (Postfix) with ESMTP id CB69D21F9838 for <ietf@ietf.org>; Tue,  2 Apr 2013 03:45:12 -0700 (PDT)
Received: from [195.245.230.131:6430] by server-11.bemta-3.messagelabs.com id 2F/1A-01263-7B6BA515; Tue, 02 Apr 2013 10:45:11 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-78.messagelabs.com!1364899506!30511879!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24701 invoked from network); 2 Apr 2013 10:45:07 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-8.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 2 Apr 2013 10:45:07 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Tue, 2 Apr 2013 11:45:05 +0100
From: <l.wood@surrey.ac.uk>
To: <ietf@ietf.org>
Date: Tue, 2 Apr 2013 11:41:56 +0100
Subject: RE: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Topic: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Index: Ac4vO4kU43hGqxe9SAWNjxYLGbXItAAUylZM
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E55@EXMB01CMS.surrey.ac.uk>
References: <20130401215830.710ADB1E007@rfc-editor.org>, <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>
In-Reply-To: <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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, 02 Apr 2013 10:45:14 -0000

Kids! Remember, if we're not bright enough to do physics, we can always do =
engineering, the slow younger brother of physics! But if engineering is too=
 difficult, there's always computer science, where terms like "bandwidth" m=
ean what we want them to mean. And if even that's too hard, there's always =
the arts-and-crafts knitted-my-own-shawl-or-at-least-drew-an-okay-pattern-f=
or-it trade of 'Internet Engineering', and writing RFCs.

And we can achieve that RFC goal easily by getting in the back door with an=
 April 1 RFC! Every April 1 there's a reminder and inspiration to us all!

Lloyd Wood
http://sat-net.com/L.Wood/

Time's arrow is written --------&gt;

From stbryant@cisco.com  Tue Apr  2 06:10:15 2013
Return-Path: <stbryant@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 4F8B621F8E6C; Tue,  2 Apr 2013 06:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ve1zmxJqhLC5; Tue,  2 Apr 2013 06:10:14 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6DECB21F8DCF; Tue,  2 Apr 2013 06:10:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8390; q=dns/txt; s=iport; t=1364908213; x=1366117813; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=ucMRQTIov8h8Imb+zvKxGOz9WBKT2GGs97RW6f7sYfQ=; b=QYhI0xnL/UnQrykKVyv9r9vOImhEjXj1j3JRmG+PdCaGdQ48Zq9zSbeB r5nsLSiK8B0OXJgiKAgpXB/o7Ecxi6aY8s/PdelwfygvKq3jFb6JlewA+ zuBLNadESOYtaGPL5y45xhrKAh55+WwClluynYLOHycHFbYl8A4bEvVVk Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFANTXWlGQ/khR/2dsb2JhbABDgzuIfrZFgQMWdIIfAQEBBGcSEAsOBgQJJQ8CRgYBDAEHAQEQiAAMsTOQEI8ZEQeDQAOWa5ELgww
X-IronPort-AV: E=Sophos;i="4.87,393,1363132800"; d="scan'208,217";a="81688324"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 02 Apr 2013 13:10:11 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r32DA93Z015621 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Apr 2013 13:10:10 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r32DA8j9011028; Tue, 2 Apr 2013 14:10:08 +0100 (BST)
Message-ID: <515AD8B1.20503@cisco.com>
Date: Tue, 02 Apr 2013 14:10:09 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>, Richard Barnes <rlb@ipv.sx>
Subject: Re: Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-05
References: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com>
In-Reply-To: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com>
Content-Type: multipart/alternative; boundary="------------060801070601050309000207"
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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, 02 Apr 2013 13:10:15 -0000

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

Resending due to Richards change of address.

Stewart

On 11/02/2013 23:45, Richard Barnes wrote:
> I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, pleaseseehttp://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>
> Please wait for direction from your document shepherd or AD before posting a new version of the draft.
>
> Document: draft-ietf-mpls-tp-ethernet-addressing-05
> Reviewer: Richard Barnes
> Review Date: 2013-02-11
> IETF LC End Date: 2013-02-18
> IESG Telechat date: TBD
>
> Summary:  Ready, with a couple of minor questions / clarifications.
>
> Comment:
>
> The document is mostly very clearly written.  (Thanks!)  It would have helped me understand if it could have been clarified up front that the mechanism in this document is intended for "pure Ethernet" MPLS-TP (without assumptions about layer 3+).  The current introduction says as much, but in a negative way, in terms of ARP or ND not being available.
>
> I have some minor unease about the distinction that this document makes between point-to-point and multipoint links.  The document correctly notes that a point-to-point link might become multipoint without either end being aware.  I would have thought this would argue for using GAP in all cases, but instead the document carries on with addressing the point-to-point case separately..
>
Richard

It is always difficult when writing a simple draft dealing with a small
component of a larger technology to know how much tutorial to include,
but I believe the point about operation in the absence IP would be well 
known
to anyone implementing this. In particular we assume that anyone
implementing the draft would have read the required references called
up in the first paragraph of the Introduction:


" The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of protocol
functions that meet the requirements [RFC5654] for the application of
MPLS to the construction and operation of packet-switched transport
networks. The MPLS-TP data plane consists of those MPLS-TP functions
concerned with the encapsulation and forwarding of MPLS-TP packets
and is described in [RFC5960]."

RFC5654 says:

"   36  It MUST be possible to operate and configure the MPLS-TP data
        plane without any IP forwarding capability in the MPLS-TP data
        plane.  That is, the data plane only operates on the MPLS label."
Thus I think that the text is complete as it stands and requires no
further clarification for anyone that needs to consider the technology
it describes.


With regard to your second point, the issue that we are have, is that
there are a number of deployment scenarios where the operator knows
that the link is Pt-Pt, and there is a reluctance by that community to
use anything other than NMS configuration. That has lead them
to use Ethernet broadcast addressing which allows the crafts to
change h/w without the need for reconfiguration by the NMS.
Against that background moving them onto the use of a Ethernet m/c
address is a step forward. To require using the GAP to that
community would illustrate that the IETF is out of touch with
their needs and methods of network operation.

Hopefully this additional background, which I believe is well
known to the MPLS-TP community to which this draft is directed,
satisfies your concern on the latter point.

- Stewart



-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------060801070601050309000207
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">Resending due to Richards change of
      address.<br>
      <br>
      Stewart<br>
      <br>
      On 11/02/2013 23:45, Richard Barnes wrote:<br>
    </div>
    <blockquote cite="mid:BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com"
      type="cite">
      <pre wrap="">I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, pleaseseehttp://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

Please wait for direction from your document shepherd or AD before posting a new version of the draft.

Document: draft-ietf-mpls-tp-ethernet-addressing-05
Reviewer: Richard Barnes
Review Date: 2013-02-11
IETF LC End Date: 2013-02-18
IESG Telechat date: TBD

Summary:  Ready, with a couple of minor questions / clarifications.

Comment:

The document is mostly very clearly written.  (Thanks!)  It would have helped me understand if it could have been clarified up front that the mechanism in this document is intended for "pure Ethernet" MPLS-TP (without assumptions about layer 3+).  The current introduction says as much, but in a negative way, in terms of ARP or ND not being available.

I have some minor unease about the distinction that this document makes between point-to-point and multipoint links.  The document correctly notes that a point-to-point link might become multipoint without either end being aware.  I would have thought this would argue for using GAP in all cases, but instead the document carries on with addressing the point-to-point case separately..

</pre>
    </blockquote>
    Richard<br>
    <br>
    It is always difficult when writing a simple draft dealing with a
    small<br>
    component of a larger technology to know how much tutorial to
    include,<br>
    but I believe the point about operation in the absence IP would be
    well known<br>
    to anyone implementing this. In particular we assume that anyone<br>
    implementing the draft would have read the required references
    called<br>
    up in the first paragraph of the Introduction:<br>
    <br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    " The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of
    protocol <br>
    functions that meet the requirements [RFC5654] for the application
    of <br>
    MPLS to the construction and operation of packet-switched transport
    <br>
    networks. The MPLS-TP data plane consists of those MPLS-TP functions
    <br>
    concerned with the encapsulation and forwarding of MPLS-TP packets <br>
    and is described in [RFC5960]."<br>
    <pre>RFC5654 says:

<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">"   36  It MUST be possible to operate and configure the MPLS-TP data
       plane without any IP forwarding capability in the MPLS-TP data
       plane.  That is, the data plane only operates on the MPLS label."
Thus I think that the text is complete as it stands and requires no 
further clarification for anyone that needs to consider the technology
it describes.


With regard to your second point, the issue that we are have, is that
there are a number of deployment scenarios where the operator knows
that the link is Pt-Pt, and there is a reluctance by that community to
use anything other than NMS configuration. That has lead them
to use Ethernet broadcast addressing which allows the crafts to 
change h/w without the need for reconfiguration by the NMS. 
Against that background moving them onto the use of a Ethernet m/c 
address is a step forward. To require using the GAP to that 
community would illustrate that the IETF is out of touch with 
their needs and methods of network operation.

Hopefully this additional background, which I believe is well
known to the MPLS-TP community to which this draft is directed,
satisfies your concern on the latter point.

- Stewart
</pre>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------060801070601050309000207--

From Ted.Lemon@nominum.com  Tue Apr  2 06:31:52 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7464B21F86EB for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 06:31:52 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z01u814qIj97 for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 06:31:51 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 2D42F21F86E6 for <ietf@ietf.org>; Tue,  2 Apr 2013 06:31:51 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUVrdxrBv334NY8/K/2uD7HgEkdQE/uNs@postini.com; Tue, 02 Apr 2013 06:31:51 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AAA4F1B807D for <ietf@ietf.org>; Tue,  2 Apr 2013 06:31:50 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A18B819005C; Tue,  2 Apr 2013 06:31:50 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 2 Apr 2013 06:31:44 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Topic: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Index: AQHOLzt6xZKHzVrsMkmbs2sZy6JPWpjDNEUAgAAvcIA=
Date: Tue, 2 Apr 2013 13:31:43 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077512D113@mbx-01.win.nominum.com>
References: <20130401215830.710ADB1E007@rfc-editor.org>, <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <290E20B455C66743BE178C5C84F12408223F494E55@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E55@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EFFA1BECD5C4FF4AA58F7B53F2C27152@nominum.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: Tue, 02 Apr 2013 13:31:52 -0000

On Apr 2, 2013, at 6:41 AM, l.wood@surrey.ac.uk wrote:
> Kids! Remember, if we're not bright enough to do physics, we can always d=
o engineering, the slow younger brother of physics!

Is your point that if we do an engineering solution, that will slow things =
down enough that we won't have packet ordering problems?


From rlb@ipv.sx  Tue Apr  2 07:28:32 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5649A21F883A for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 07:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.703
X-Spam-Level: 
X-Spam-Status: No, score=-0.703 tagged_above=-999 required=5 tests=[AWL=-0.278, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yuezjjhI9vfU for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 07:28:32 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 3D57121F88CA for <ietf@ietf.org>; Tue,  2 Apr 2013 07:28:31 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id wc20so414938obb.15 for <ietf@ietf.org>; Tue, 02 Apr 2013 07:28:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=Py5BtG+/OD8W6ctWwYFaI1ZL16k20NpCtwq1QJ1i52c=; b=ACabh+qQ/j+B5zck6D8Rlf0xs3jeERD68j8dGkCmDi9DOQtgAMqpjUd+Lk9LB3VHx7 ZW5ymtuUCh82AdYn8x8sVx0a4yzQS/+gJ7Wvz+yyq8gwkUXXWDGZKoNR3FgRdCgruDtG Ar15vnxR9Yb6RnQPIDHgTSiEflV7ZdIOcLiKgoV5ie34ri2u6ZOo/2LFTvE0HG/84w1p ZptBeHAIe+v4XFtMM2uLBooxVbiP5dm3/LTUh38VEB8qg2/vVkIDqYLATXg3KsXstDQX Epq1QUxHqfAgjPjxTRk0Ei1WS/kdBYdaRCMAxt9DXNu1dwRInKZvKs5zs3LZvUGF9LLD 45YQ==
MIME-Version: 1.0
X-Received: by 10.60.30.131 with SMTP id s3mr5744629oeh.106.1364912910401; Tue, 02 Apr 2013 07:28:30 -0700 (PDT)
Received: by 10.60.160.201 with HTTP; Tue, 2 Apr 2013 07:28:30 -0700 (PDT)
X-Originating-IP: [192.1.51.16]
In-Reply-To: <515AD8B1.20503@cisco.com>
References: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com> <515AD8B1.20503@cisco.com>
Date: Tue, 2 Apr 2013 10:28:30 -0400
Message-ID: <CAL02cgTExcoC+fMYVs0KT==yx1vZgaK5Tc8Dij3vhiR9Os3YkQ@mail.gmail.com>
Subject: Re: Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-05
From: Richard Barnes <rlb@ipv.sx>
To: stbryant@cisco.com
Content-Type: multipart/alternative; boundary=e89a8ff1c0362c94ca04d9618d64
X-Gm-Message-State: ALoCoQnJeNwir/5bWTE+WUWTFczc+yY9y/492WKL3rQ9gnGHhhc1oHRJxpfQvKcZtiFjTzNaxReY
Cc: Richard Barnes <rbarnes@bbn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org, "ietf@ietf.org" <ietf@ietf.org>, The 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: Tue, 02 Apr 2013 14:28:32 -0000

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

Thanks for following up, and for the re-send.  Just to be clear, I do not
mean these as blocking points.

On the former point, I might just suggest a minor edit to the introduction:
OLD: "This document specifies the options for determination and selection
of next-hop Ethernet MAC addressing under these circumstances."
NEW: "This document specifies the options for determination and selection
of next-hop Ethernet MAC addressing when MPLS-TP is used in a "pure
Ethernet" manner, without any IP forwarding capability."

On the latter point, I can understand the desire to make the simple case
simple, and the text at the end of Section 2 sends a clear warning. It does
seems like GAP would also allow autoconfiguration without further NMS
interaction.  (Unless the NMS is configuring per-Ethernet-address policies,
e.g., "forward packets with this label to 00:11:22:33:44:55". Is that the
case?)




On Tue, Apr 2, 2013 at 9:10 AM, Stewart Bryant <stbryant@cisco.com> wrote:

>  Resending due to Richards change of address.
>
> Stewart
>
>
> On 11/02/2013 23:45, Richard Barnes wrote:
>
> I have been selected as the General Area Review Team (Gen-ART) reviewer f=
or this draft (for background on Gen-ART, pleaseseehttp://www.alvestrand.no=
/ietf/gen/art/gen-art-FAQ.html).
>
> Please wait for direction from your document shepherd or AD before postin=
g a new version of the draft.
>
> Document: draft-ietf-mpls-tp-ethernet-
> addressing-05
> Reviewer: Richard Barnes
> Review Date: 2013-02-11
> IETF LC End Date: 2013-02-18
> IESG Telechat date: TBD
>
> Summary:  Ready, with a couple of minor questions / clarifications.
>
> Comment:
>
> The document is mostly very clearly written.  (Thanks!)  It would have he=
lped me understand if it could have been clarified up front that the mechan=
ism in this document is intended for "pure Ethernet" MPLS-TP (without assum=
ptions about layer 3+).  The current introduction says as much, but in a ne=
gative way, in terms of ARP or ND not being available.
>
> I have some minor unease about the distinction that this document makes b=
etween point-to-point and multipoint links.  The document correctly notes t=
hat a point-to-point link might become multipoint without either end being =
aware.  I would have thought this would argue for using GAP in all cases, b=
ut instead the document carries on with addressing the point-to-point case =
separately..
>
>
>  Richard
>
> It is always difficult when writing a simple draft dealing with a small
> component of a larger technology to know how much tutorial to include,
> but I believe the point about operation in the absence IP would be well
> known
> to anyone implementing this. In particular we assume that anyone
> implementing the draft would have read the required references called
> up in the first paragraph of the Introduction:
>
>
> " The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of protocol
> functions that meet the requirements [RFC5654] for the application of
> MPLS to the construction and operation of packet-switched transport
> networks. The MPLS-TP data plane consists of those MPLS-TP functions
> concerned with the encapsulation and forwarding of MPLS-TP packets
> and is described in [RFC5960]."
>
> RFC5654 says:
>
> "   36  It MUST be possible to operate and configure the MPLS-TP data
>        plane without any IP forwarding capability in the MPLS-TP data
>        plane.  That is, the data plane only operates on the MPLS label."
> Thus I think that the text is complete as it stands and requires no
> further clarification for anyone that needs to consider the technology
> it describes.
>
>
> With regard to your second point, the issue that we are have, is that
> there are a number of deployment scenarios where the operator knows
> that the link is Pt-Pt, and there is a reluctance by that community to
> use anything other than NMS configuration. That has lead them
> to use Ethernet broadcast addressing which allows the crafts to
> change h/w without the need for reconfiguration by the NMS.
> Against that background moving them onto the use of a Ethernet m/c
> address is a step forward. To require using the GAP to that
> community would illustrate that the IETF is out of touch with
> their needs and methods of network operation.
>
> Hopefully this additional background, which I believe is well
> known to the MPLS-TP community to which this draft is directed,
> satisfies your concern on the latter point.
>
> - Stewart
>
>
>
> --
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>

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

Thanks for following up, and for the re-send. =A0Just to be clear, I do not=
 mean these as blocking points.<div><br></div><div>On the former point, I m=
ight just suggest a minor edit to the introduction:</div><div>OLD: &quot;Th=
is document specifies the options for determination and selection of next-h=
op Ethernet MAC addressing under these circumstances.&quot;</div>
<div>NEW: &quot;This document specifies the options for determination and s=
election of next-hop Ethernet MAC addressing when MPLS-TP is used in a &quo=
t;pure Ethernet&quot; manner, without any IP forwarding capability.&quot;</=
div>
<div><br></div><div>On the latter point, I can understand the desire to mak=
e the simple case simple, and the text at the end of Section 2 sends a clea=
r warning. It does seems like GAP would also allow autoconfiguration withou=
t further NMS interaction. =A0(Unless the NMS is configuring per-Ethernet-a=
ddress policies, e.g., &quot;forward packets with this label to 00:11:22:33=
:44:55&quot;. Is that the case?) =A0</div>
<div><br></div><div><br><br><br><div class=3D"gmail_quote">On Tue, Apr 2, 2=
013 at 9:10 AM, Stewart Bryant <span dir=3D"ltr">&lt;<a href=3D"mailto:stbr=
yant@cisco.com" target=3D"_blank">stbryant@cisco.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div>Resending due to Richards change of
      address.<br>
      <br>
      Stewart<div class=3D"im"><br>
      <br>
      On 11/02/2013 23:45, Richard Barnes wrote:<br>
    </div></div>
    <blockquote type=3D"cite">
      <pre><div><div class=3D"h5">I have been selected as the General Area =
Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, p=
leaseseehttp://<a href=3D"http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ=
.html" target=3D"_blank">www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html</a=
>).

Please wait for direction from your document shepherd or AD before posting =
a new version of the draft.

Document: draft-ietf-mpls-tp-ethernet-</div></div>addressing-05
Reviewer: Richard Barnes
Review Date: 2013-02-11
IETF LC End Date: 2013-02-18
IESG Telechat date: TBD

Summary:  Ready, with a couple of minor questions / clarifications.

Comment:

The document is mostly very clearly written.  (Thanks!)  It would have help=
ed me understand if it could have been clarified up front that the mechanis=
m in this document is intended for &quot;pure Ethernet&quot; MPLS-TP (witho=
ut assumptions about layer 3+).  The current introduction says as much, but=
 in a negative way, in terms of ARP or ND not being available.

I have some minor unease about the distinction that this document makes bet=
ween point-to-point and multipoint links.  The document correctly notes tha=
t a point-to-point link might become multipoint without either end being aw=
are.  I would have thought this would argue for using GAP in all cases, but=
 instead the document carries on with addressing the point-to-point case se=
parately..

</pre>
    </blockquote><div><div class=3D"h5">
    Richard<br>
    <br>
    It is always difficult when writing a simple draft dealing with a
    small<br>
    component of a larger technology to know how much tutorial to
    include,<br>
    but I believe the point about operation in the absence IP would be
    well known<br>
    to anyone implementing this. In particular we assume that anyone<br>
    implementing the draft would have read the required references
    called<br>
    up in the first paragraph of the Introduction:<br>
    <br>
    <br>
   =20
    &quot; The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of
    protocol <br>
    functions that meet the requirements [RFC5654] for the application
    of <br>
    MPLS to the construction and operation of packet-switched transport
    <br>
    networks. The MPLS-TP data plane consists of those MPLS-TP functions
    <br>
    concerned with the encapsulation and forwarding of MPLS-TP packets <br>
    and is described in [RFC5960].&quot;<br>
    <pre>RFC5654 says:

&quot;   36  It MUST be possible to operate and configure the MPLS-TP data
       plane without any IP forwarding capability in the MPLS-TP data
       plane.  That is, the data plane only operates on the MPLS label.&quo=
t;
Thus I think that the text is complete as it stands and requires no=20
further clarification for anyone that needs to consider the technology
it describes.


With regard to your second point, the issue that we are have, is that
there are a number of deployment scenarios where the operator knows
that the link is Pt-Pt, and there is a reluctance by that community to
use anything other than NMS configuration. That has lead them
to use Ethernet broadcast addressing which allows the crafts to=20
change h/w without the need for reconfiguration by the NMS.=20
Against that background moving them onto the use of a Ethernet m/c=20
address is a step forward. To require using the GAP to that=20
community would illustrate that the IETF is out of touch with=20
their needs and methods of network operation.

Hopefully this additional background, which I believe is well
known to the MPLS-TP community to which this draft is directed,
satisfies your concern on the latter point.

- Stewart
</pre>
    <br>
    <br>
    </div></div><span class=3D"HOEnZb"><font color=3D"#888888"><pre cols=3D=
"72">--=20
For corporate legal information go to:

<a href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.ht=
ml" target=3D"_blank">http://www.cisco.com/web/about/doing_business/legal/c=
ri/index.html</a>

</pre>
  </font></span></div>

</blockquote></div><br></div>

--e89a8ff1c0362c94ca04d9618d64--

From kaduk@mit.edu  Mon Apr  1 10:01:12 2013
Return-Path: <kaduk@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 A9A7311E80CC; Mon,  1 Apr 2013 10:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28l6HrMA6vCq; Mon,  1 Apr 2013 10:01:12 -0700 (PDT)
Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by ietfa.amsl.com (Postfix) with ESMTP id CAE1411E80AE; Mon,  1 Apr 2013 10:01:10 -0700 (PDT)
X-AuditID: 12074425-b7fec6d000007584-37-5159bd558297
Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id CD.E9.30084.55DB9515; Mon,  1 Apr 2013 13:01:09 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id r31H19Wr015051;  Mon, 1 Apr 2013 13:01:09 -0400
Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r31H17fJ016511 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Apr 2013 13:01:08 -0400
Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r31H17tr006109; Mon, 1 Apr 2013 13:01:07 -0400 (EDT)
Date: Mon, 1 Apr 2013 13:01:06 -0400 (EDT)
From: Benjamin Kaduk <kaduk@MIT.EDU>
To: ietf@ietf.org
Subject: Re: [nfsv4] Last Call: <draft-ietf-nfsv4-rfc3530bis-25.txt> (Network File System	(NFS) Version 4 Protocol) to Proposed Standard
In-Reply-To: <20130319142244.19905.39903.idtracker@ietfa.amsl.com>
Message-ID: <alpine.GSO.1.10.1303312327530.9389@multics.mit.edu>
References: <20130319142244.19905.39903.idtracker@ietfa.amsl.com>
User-Agent: Alpine 1.10 (GSO 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKIsWRmVeSWpSXmKPExsUixCmqrRu6NzLQ4PN9c4tnG+ezWHxY+JDF gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZG74/YSn4zFNxeN9D5gbGY1xdjBwcEgImEl3rmLoY OYFMMYkL99azdTFycQgJ7GOU6PjxjBEkISSwgVHiR4cwROIgk8SBBWeZIBL1Ej/ubGMGsVkE tCRmnW8Fs9kEVCRmvtnIBrJAREBQ4uBjSxCTWUBYYt9RJ5AxwgJdjBKNa2ayg5RzCjhJ/O+9 BzaSV8BBYuPOLqi9jhL7zh5hA7FFBXQkVu+fwgJRIyhxcuYTMJtZwFLi39pfrBMYBWchSc1C klrAyLSKUTYlt0o3NzEzpzg1Wbc4OTEvL7VI10IvN7NELzWldBMjKDTZXVR3ME44pHSIUYCD UYmH12FOZKAQa2JZcWXuIUZJDiYlUd5Tu4FCfEn5KZUZicUZ8UWlOanFhxglOJiVRHhXZALl eFMSK6tSi/JhUtIcLErivDdSbvoLCaQnlqRmp6YWpBbBZGU4OJQkeOfuAWoULEpNT61Iy8wp QUgzcXCCDOcBGr4DpIa3uCAxtzgzHSJ/ilFRSpy3AyQhAJLIKM2D64WljleM4kCvCPOuAKni AaYduO5XQIOZgAYvuxUOMrgkESEl1cAocGWr1QXzX9zysnwditJpu5Nnxr+axckXn3k+ZKbk N4Xv2y7Zn9oe8frB7TjFi+9NM803MvwW/sSw5piR2pN7yz99ZKj8ILCISVTtQewLrcdCQbe2 v6q78UHsy0efhqJ1Ou8bFY8pP2tinKr4mFPUe0nXlhPa89b9mhFhsDhW5MLMrXc8L7c+UWIp zkg01GIuKk4EACl6mS/4AgAA
X-Mailman-Approved-At: Tue, 02 Apr 2013 08:31:16 -0700
Cc: secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Apr 2013 17:01:12 -0000

I have not yet completed a full review of this (320-page) document, and I 
worry that I may not finish before the deadline, so I am bringing this 
concern to your attention now.

Section 3.2.1.1 of this document ("Kerberos V5 as a security triple") 
seems to indicate that it is mandatory for a conformant NFSv4 
implementation to implement the Kerberos V5 GSS-API mechanism and a few 
"security triples" (mechanism,quality of protection,service).  All of the 
mandatory-to-implement security triples use the DES-MAC-MD5 algorithm. 
The draft goes on to indicate that clients should engage in security 
negotiation (section 3.3) to determine what security to use for bulk 
operation, and that since kerberos-v5 under RPCSEC_GSS is mandatory, the 
negotiation will be performed using that security provider.  The actual 
mechanism resulting from the negotiation may be different (or may be the 
same), but this single-DES mechanism seems to be required to be used to 
protect the negotiation step.

Given that the kerberos working group has published RFC 6649 (Deprecate 
DES, RC4-HMAC-EXP, and Other Weak Cryptographic Algorithms in Kerberos) 
and single-DES is known to be critically vulnerable to brute-force 
attacks, I have grave concern about the IETF publishing new standards 
documents that mandate the implementation of single-DES and do not specify 
strong cryptographic algorithms.  I feel that to do so would be misleading 
implementors into believing that single-DES is sufficient and other 
mechanisms need not be implemented, when in reality this is not true.

Sincerely,

Ben Kaduk
MIT Kerberos Consortium

From eburger@cs.georgetown.edu  Mon Apr  1 14:58:21 2013
Return-Path: <eburger@cs.georgetown.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 58E0111E80FA for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:58:21 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P1wW3De1o0yi for <ietf@ietfa.amsl.com>; Mon,  1 Apr 2013 14:58:20 -0700 (PDT)
Received: from karma.cs.georgetown.edu (karma.cs.georgetown.edu [141.161.20.3]) by ietfa.amsl.com (Postfix) with ESMTP id 4712211E80F9 for <ietf@ietf.org>; Mon,  1 Apr 2013 14:58:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by karma.cs.georgetown.edu (Postfix) with ESMTP id 8FF6B4397E; Mon,  1 Apr 2013 17:58:19 -0400 (EDT)
X-Virus-Scanned: by amavisd-new at cs.georgetown.edu
Received: from karma.cs.georgetown.edu ([127.0.0.1]) by localhost (karma.cs.georgetown.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wVknFN04GiNL; Mon,  1 Apr 2013 17:58:17 -0400 (EDT)
Received: from [192.168.15.177] (ip68-100-199-8.dc.dc.cox.net [68.100.199.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by karma.cs.georgetown.edu (Postfix) with ESMTP id 2C8A143557; Mon,  1 Apr 2013 17:58:17 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch? (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
From: Burger Eric <eburger@cs.georgetown.edu>
In-Reply-To: <5159FF0E.9080202@nostrum.com>
Date: Mon, 1 Apr 2013 17:58:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6F96AAC-4584-40CD-A369-FCF6B1EFBFD3@cs.georgetown.edu>
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu> <6.2.5.6.2.20130328111022.0ceeb7d8@resistor.net> <5159FF0E.9080202@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1503)
X-Mailman-Approved-At: Tue, 02 Apr 2013 08:31:16 -0700
Cc: "ietf@ietf.org 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, 01 Apr 2013 21:58:21 -0000

Fine with me.

On Apr 1, 2013, at 5:41 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

> On 3/28/13 1:17 PM, SM wrote:
>> Hi Eric,
>> At 05:13 28-03-2013, Burger Eric wrote:
>>> Rather than guessing all of the bad things that could happen, I =
would offer it would be better to say what we mean, like:
>>>        The IMAP interface MUST NOT provide any IMAP facilities that =
modify the underlying message and message metadata, such as mailbox, =
flags, marking for deletion, etc. If the client is authenticated and =
authorized, the IMAP interface MUST provide per-user marking of the =
underlying message as read or flagged.
>>=20
>> The IMAP interface is a front-end to the read-only mailboxes =
(archive).  It's easier to do what is mentioned above.
> I'm taking more or less that approach in my working copy (I'll be =
posting -06 soon).
>>=20
>>> Something to ponder:
>>> I use the IMAP interface once, mark a bunch of things as read, and =
then decide never to use the IMAP interface ever again. How long does =
the server need to keep my (per-user) marking metadata? E.g., besides =
CPU and I/O issues, there is a potentially unbounded storage problem as =
well. It is unbounded because in IMAP I can assign any kind of label =
(marking) to a message, even ones I make up.
>>>=20
>>> One thought for an approach to a solution:
>>> 1. per-user markings expire after X time units (six months?)
>>> 2. per-user markings may take up at most X storage units (512KB?)
>>=20
>> I would go for both.
> Instead, I propose that we make it possible to notice an abuser and =
turn off access (this is what -06 will contain).
>=20
> I don't believe we could come to a consensus on an automatic expiry of =
state - there are use cases I can think of where any short
> expiration (like 6-months) would be infuriating.
>=20
> If keeping this state for normal use turns out to be too expensive for =
us, then we will have learned something, and can start talking about =
future IMAP work in general to help systems mitigate that expense.
>>=20
>>> Per-user metadata can be incredibly useful - I might label things by =
project, work group, draft, mumble, or foo. I would not want to limit =
the labels to red or green. However, we need some predictable limit as =
well.
>>=20
>> Yes.
>>=20
>> Regards,
>> -sm
>=20


From lufang@cisco.com  Mon Apr  1 18:05:30 2013
Return-Path: <lufang@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 64E4411E811A; Mon,  1 Apr 2013 18:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.846
X-Spam-Level: 
X-Spam-Status: No, score=-8.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id COllLp47q31a; Mon,  1 Apr 2013 18:05:29 -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 1665011E80F8; Mon,  1 Apr 2013 18:05:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12295; q=dns/txt; s=iport; t=1364864729; x=1366074329; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=FPyWT/s0hLgu4xm9JXKcQjXk/PAzMb0bdYobFBuoTDE=; b=eb59mU5XpNZIlTjUAlvzgaM29Xte96HQZOkfsJri2JWXGtqXW3KweZxr n37LH2f8b7JEz5SvjciZqoisX2lPvMpn0ModiZC5Z9tgQmbUcVWzuyQrp gL+hD4p2671aO/59yEtG02g9W+P44kLqkumcYkkug8XGi9ngkR/tCiaFJ E=;
X-Files: default[4].xml : 3222
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAI8tWlGtJXG8/2dsb2JhbABDgzuDILwhDXEWdIIfAQEBBAEBAWsLDAYBCBEDAQIBCiIEJQsdCAIEAQ0FCAaIBgyTS5p+BoJCj3aNeYEHIAYLBwaCIThhA49FiEWPbIMLgWo+
X-IronPort-AV: E=Sophos;i="4.87,390,1363132800";  d="xml'?rels'?scan'72,48,208";a="193830200"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-5.cisco.com with ESMTP; 02 Apr 2013 01:05:28 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3215SVI029451 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Apr 2013 01:05:28 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.17]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.004; Mon, 1 Apr 2013 20:05:27 -0500
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: Russ Housley <housley@vigilsec.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt>
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt>
Thread-Index: AQHOLz4pe+S4mct/bEWgHAuKWl97qA==
Date: Tue, 2 Apr 2013 01:05:27 +0000
Message-ID: <0DB8F45437AB844CBB5102F807A0AD93102CB212@xmb-rcd-x03.cisco.com>
In-Reply-To: <A7D6179B-4760-4B3B-8547-769DADAA4243@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.131.12.86]
Content-Type: multipart/mixed; boundary="_002_0DB8F45437AB844CBB5102F807A0AD93102CB212xmbrcdx03ciscoc_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 02 Apr 2013 08:31:16 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Apr 2013 01:05:30 -0000

--_002_0DB8F45437AB844CBB5102F807A0AD93102CB212xmbrcdx03ciscoc_
Content-Type: text/plain; charset="euc-kr"
Content-ID: <2ABE71F1A2CCC3498D35A3B97E6A0B1A@emea.cisco.com>
Content-Transfer-Encoding: base64

SGkgUnVzcywNCg0KVGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzLCB2ZXJ5IGdvb2QgcG9pbnRzLg0K
U29ycnkgZm9yIHRoZSBkZWxheSBpbiByZXBseWluZywgSSB3YXMgb3V0IG9mIG9mZmljZS4NCg0K
IA0KVGhlIGZvbGxvd2luZyBpcyBteSBwcm9wb3NlZCB0ZXh0IGZvciByZXBsYWNpbmcgdGhlIGN1
cnJlbnQgZmlyc3QNCnBhcmFncmFwaCBvZiBzZWN0aW9uIDEuMi4NCg0KIA0KVHJhZGl0aW9uYWwg
dHJhbnNwb3J0IHRlY2hub2xvZ2llcyBpbmNsdWRlIFNPTkVUL1NESCwgVERNLCBhbmQgQVRNLiBU
aGVyZQ0KaXMgYSB0cmFuc2l0aW9uIGF3YXkgZnJvbSB0aGVzZSB0cmFuc3BvcnQgdGVjaG5vbG9n
aWVzIHRvIG5ldyBwYWNrZXQNCnRlY2hub2xvZ2llcy4NCkluIGFkZGl0aW9uIHRvIHRoZSBldmVy
IGluY3JlYXNpbmcgZGVtYW5kIGZvciBiYW5kd2lkdGgsIHRoZSBwYWNrZXQNCnRlY2hub2xvZ2ll
cyBvZmZlciB0aGVzZSBrZXkgYWR2YW50YWdlczoNCg0KIA0KQmFuZHdpZHRoIGVmZmljaWVuY3k6
IFRyYW5zcG9ydCB0ZWNobm9sb2dpZXMgc3VwcG9ydHMgZml4ZWQgQmFuZHdpZHRoDQpvbmx5LCBu
byBwYWNrZXQgc3RhdGlzdGljYWwgbXVsdGlwbGV4aW5nLCBiYW5kd2lkdGggaXMgcmVzZXJ2ZWQg
aW4NCnRyYW5zcG9ydA0Kd2hldGhlciB1c2VkIG9yIG5vdCBieSBjbGllbnRzLiBQYWNrZXQgdGVj
aG5vbG9naWVzIHN1cHBvcnQgc3RhdGlzdGljYWwNCm11bHRpcGxleGluZywNCnRoaXMgaXMgdGhl
IG1vc3QgaW1wb3J0YW50IG1vdGl2YXRpb24gZm9yIHRoZSB0cmFuc2l0aW9uIGZyb20gdHJhZGl0
aW9uYWwNCnRyYW5zcG9ydCB0ZWNobm9sb2dpZXMgdG8gcGFja2V0IHRlY2hub2xvZ2llcy4gVGhl
IHByb2xpZmVyYXRpb24gb2YgbmV3DQpkaXN0cmlidXRlZCBhcHBsaWNhdGlvbnMgd2hpY2ggY29t
bXVuaWNhdGUgd2l0aCBzZXJ2ZXJzIG92ZXIgdGhlIG5ldHdvcmsNCmluIGENCmJ1cnN0eSBmYXNo
aW9uIGhhcyBiZWVuIGRyaXZpbmcgdGhlIGFkb3B0aW9uIG9mIHBhY2tldCB0cmFuc3BvcnQNCnRl
Y2huaXF1ZXMsIHNpbmNlDQptdWx0aXBsZXhpbmcgb2YgYnVyc3R5IHNvdXJjZXMgaXMgZmFyIG1v
cmUgZWZmaWNpZW50IG92ZXIgdHJhZGl0aW9uYWwNCmNpcmN1aXQtYmFzZWQNClRETSB0ZWNobm9s
b2dpZXMuDQoNCiANCkZsZXhpYmxlIGRhdGEgcmF0ZSBjb25uZWN0aW9uczogVHJhZGl0aW9uYWwg
dHJhbnNwb3J0IGNvbm5lY3Rpb24NCmdyYW51bGFyaXR5DQppcyBsaW1pdGVkIHRvIHRoZSByaWdp
ZCBQREggb3IgU09ORVQgaGllcmFyY2h5IChlLmcuLCBEUzEsIERTMywgT0MzLCBPQzEyLA0KZXRj
LikuDQpQYWNrZXQgdGVjaG5vbG9naWVzIHN1cHBvcnQgZmxleGlibGUgZGF0YSByYXRlIGNvbm5l
Y3Rpb25zLiBUaGUgc3VwcG9ydCBvZg0KZmluZXIgZGF0YSByYXRlIGdyYW51bGFyaXR5IGlzIGlt
cG9ydGFudCBmb3IgdG9kYXmp9nMgd2lyZWxpbmUgYW5kIHdpcmVsZXNzDQpzZXJ2aWNlcyBhbmQg
YXBwbGljYXRpb25zLg0KDQogDQpRb1Mgc3VwcG9ydDogV2hpbGUgdHJhZGl0aW9uYWwgdHJhbnNw
b3J0LCBzdWNoIGFzIFRETSB0cmFuc3BvcnQgaGFzDQp2ZXJ5IGxpbWl0ZWQgUW9TIHN1cHBvcnQs
IHBhY2tldCB0cmFuc3BvcnQgY2FuIHByb3ZpZGUgbmVlZGVkIFFvUw0KdHJlYXRtZW50IGZvcg0K
SVBUViwgVm9pY2UgYW5kIFZpZGVvIG92ZXIgSVAgYXBwbGljYXRpb25zLg0KDQogDQpUaGUgcm9v
dCBjYXVzZSBmb3IgdHJhbnNwb3J0IG1vdmluZyB0byBwYWNrZXQgdHJhbnNwb3J0IGlzIHRoZSBz
aGlmdA0Kb2YgYXBwbGljYXRpb24gZnJvbSBURE0gdG8gcGFja2V0LiBGb3IgZXhhbXBsZSwgVm9p
Y2UgVERNIHRvIFZvSVA7IFZpZGVvIHRvDQpWaWRlbyBvdmVyIElQOyBURE0gYWNjZXNzIGxpbmVz
IHRvIEV0aGVybmV0OyBURE0gVlBOcyB0byBJUCBWUE5zIGFuZA0KRXRoZXJuZXQNClZQTnMuIElu
IGFkZGl0aW9uLCBuZXR3b3JrIGNvbnZlcmdlbmNlIGFuZCB0ZWNobm9sb2d5IHJlZnJlc2hlcyBk
ZW1hbmQgZm9yDQpjb21tb24gYW5kIGZsZXhpYmxlIGluZnJhc3RydWN0dXJlIHRoYXQgcHJvdmlk
ZXMgbXVsdGlwbGUgc2VydmljZXMuDQoNCiANClRoYW5rcywNCkx1eXVhbg0KDQoNCg0KLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFJ1c3MgSG91c2xleSA8aG91c2xleUB2aWdpbHNl
Yy5jb20+DQpEYXRlOiBTYXR1cmRheSwgTWFyY2ggMjMsIDIwMTMgMzoxNiBQTQ0KVG86ICJpZXRm
QGlldGYub3JnIiA8aWV0ZkBpZXRmLm9yZz4NCkNjOiAibXBsc0BpZXRmLm9yZyIgPG1wbHNAaWV0
Zi5vcmc+DQpTdWJqZWN0OiBSZTogW21wbHNdIExhc3QNCkNhbGw6CTxkcmFmdC1pZXRmLW1wbHMt
dHAtdXNlLWNhc2VzLWFuZC1kZXNpZ24tMDYudHh0Pg0KDQo+SSB3b25kZXIgaWYgdGhlIGRpcmVj
dGlvbiBvZiBTZWN0aW9uIDEuMiBjYW4gYmUgcmV2aXNlZCB0byBtYWtlIGl0IG1vcmUNCj5vZiBh
biBlbmdpbmVlcmluZyBkb2N1bWVudC4NCj4NCj5JdCBjdXJyZW50bHkgc2F5czoNCj4NCj4gICBJ
biByZWNlbnQgeWVhcnMsIHRoZSB1cmdlbmN5IGZvciBtb3ZpbmcgZnJvbSB0cmFkaXRpb25hbCB0
cmFuc3BvcnQNCj4gICB0ZWNobm9sb2dpZXMsIHN1Y2ggYXMgU09ORVQvU0RILCBURE0sIGFuZCBB
VE0sIHRvIG5ldyBwYWNrZXQNCj4gICB0ZWNobm9sb2dpZXMgaGFzIGJlZW4gcmlzaW5nLiBUaGlz
IGlzIGxhcmdlbHkgZHVlIHRvIHRoZSBmYXN0IGdyb3dpbmcNCj4gICBkZW1hbmQgZm9yIGJhbmR3
aWR0aCwgd2hpY2ggaGFzIGJlZW4gZnVlbGVkIGJ5IHRoZSBmb2xsb3dpbmcgZmFjdG9yczoNCj4g
ICAuLi4NCj4NCj5QbGVhc2UgY29uc2lkZXIgYW4gYXBwcm9hY2ggdGhhdCBkZXNjcmliZXMgdGhl
IHRoZSByZWFzb25zIGJlaGluZCB0aGUNCj50cmFuc2l0aW9uIGZyb20gdGhlIG5ldHdvcmsgb3Bl
cmF0b3IgYW5kIG5ldHdvcmsgdXNlciBwZXJzcGVjdGl2ZXM6DQo+DQo+ICAgVHJhZGl0aW9uYWwg
dHJhbnNwb3J0IHRlY2hub2xvZ2llcyBpbmNsdWRlIFNPTkVUL1NESCwgVERNLCBhbmQgQVRNLg0K
PiAgIFRoZXJlIGlzIGEgdHJhbnNpdGlvbiBhd2F5IGZyb20gdGhlc2UgdHJhbnNwb3J0IHRlY2hu
b2xvZ2llcyB0byBuZXcNCj4gICBwYWNrZXQgdGVjaG5vbG9naWVzLiBJbiBhZGRpdGlvbiB0byB0
aGUgZXZlciBpbmNyZWFzaW5nIGRlbWFuZCBmb3INCj4gICBiYW5kd2lkdGgsIHRoZSBwYWNrZXQg
dGVjaG5vbG9naWVzIG9mZmVyIHRoZXNlIGFkdmFudGFnZXM6DQo+ICAgLi4uDQo+DQo+VGhlIGZh
Y3QgdGhhdCBJUCBuZXR3b3JrcyBhcmUgYmVpbmcgdXNlZCBmb3IgbmV3IGFwcGxpY2F0aW9ucyBh
bmQgdGhhdA0KPnRoZSBsZWdhY3kgZGV2aWNlcyBhcmUgZ2V0dGluZyBvbGQgZG9lcyBub3QgbW90
aXZhdGUgdGhlIHRyYW5zaXRpb24gdG8NCj5wYWNrZXQgdGVjaG5vbG9naWVzLiAgVGhlIGFkdmFu
dGFnZXMgdGhhdCBwYWNrZXQgdGVjaG5vbG9naWVzIG9mZmVyIGZvcg0KPnRoZXNlIG5ldyBhcHBs
aWNhdGlvbnMgaXMgdGhlIHRoaW5nIHRoYXQgbmVlZHMgdG8gYmUgaGlnaGxpZ2h0ZWQgaGVyZSwN
Cj5ldmVuIGlmIGl0IGlzIGp1c3QgYSBsaXN0IG9mIGJ1bGxldHMuDQo+DQo+SXQgc2VlbXMgbGlr
ZSB0aGUgb25seSBzZW50ZW5jZSB0aGF0IGFkZHJlc3NlcyB0aGlzIHBvaW50IGluIFNlY3Rpb24g
MS4yDQo+aXM6ICJJdCBzdHJlYW1saW5lcyB0aGUgb3BlcmF0aW9uLCByZWR1Y2VzIHRoZSBvdmVy
YWxsIGNvbXBsZXhpdHksIGFuZA0KPmltcHJvdmVzIGVuZC10by1lbmQgY29udmVyZ2VuY2UuIg0K
Pg0KPlRoYW5rcywNCj4gIFJ1c3MNCj4NCj5PbiBKYW4gMjgsIDIwMTMsIGF0IDM6MDEgUE0sIFRo
ZSBJRVNHIHdyb3RlOg0KPg0KPj4gVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9t
IHRoZSBNdWx0aXByb3RvY29sIExhYmVsIFN3aXRjaGluZw0KPj5XRw0KPj4gKG1wbHMpIHRvIGNv
bnNpZGVyIHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6DQo+PiAtICdNUExTLVRQIEFwcGxpY2FiaWxp
dHk7IFVzZSBDYXNlcyBhbmQgRGVzaWduJw0KPj4gIDxkcmFmdC1pZXRmLW1wbHMtdHAtdXNlLWNh
c2VzLWFuZC1kZXNpZ24tMDYudHh0PiBhcyBJbmZvcm1hdGlvbmFsIFJGQw0KPj4gDQo+PiBUaGUg
SUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBhbmQg
c29saWNpdHMNCj4+IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVhc2Ugc2VuZCBz
dWJzdGFudGl2ZSBjb21tZW50cyB0byB0aGUNCj4+IGlldGZAaWV0Zi5vcmcgbWFpbGluZyBsaXN0
cyBieSAyMDEzLTAyLTExLiBFeGNlcHRpb25hbGx5LCBjb21tZW50cyBtYXkNCj4+YmUNCj4+IHNl
bnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNlIHJldGFp
biB0aGUNCj4+IGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFsbG93IGF1dG9tYXRl
ZCBzb3J0aW5nLg0KPj4gDQo+PiBBYnN0cmFjdA0KPj4gDQo+PiAgIFRoaXMgZG9jdW1lbnQgcHJv
dmlkZXMgYXBwbGljYWJpbGl0eSwgdXNlIGNhc2Ugc3R1ZGllcyBhbmQgbmV0d29yaw0KPj4gICBk
ZXNpZ24gY29uc2lkZXJhdGlvbnMgZm9yIHRoZSBNdWx0aXByb3RvY29sIExhYmVsIFN3aXRjaGlu
ZyBUcmFuc3BvcnQNCj4+ICAgUHJvZmlsZSAoTVBMUy1UUCkuIFRoZSB1c2UgY2FzZXMgaW5jbHVk
ZSBNZXRybyBFdGhlcm5ldCBhY2Nlc3MgYW5kDQo+PiAgIGFnZ3JlZ2F0aW9uIHRyYW5zcG9ydCwg
TW9iaWxlIGJhY2toYXVsLCBhbmQgcGFja2V0IG9wdGljYWwgdHJhbnNwb3J0Lg0KPj4gDQo+PiBU
aGUgZmlsZSBjYW4gYmUgb2J0YWluZWQgdmlhDQo+PiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZG9jL2RyYWZ0LWlldGYtbXBscy10cC11c2UtY2FzZXMtYW5kLWRlc2lnbi8NCj4+IA0KPj4g
SUVTRyBkaXNjdXNzaW9uIGNhbiBiZSB0cmFja2VkIHZpYQ0KPj4gDQo+Pmh0dHA6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1tcGxzLXRwLXVzZS1jYXNlcy1hbmQtZGVzaWdu
L2INCj4+YWxsb3QvDQo+PiANCj4+IA0KPj4gTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4g
c3VibWl0dGVkIGRpcmVjdGx5IG9uIHRoaXMgSS1ELg0KPg0KPl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+bXBscyBtYWlsaW5nIGxpc3QNCj5tcGxzQGll
dGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQoNCg==

--_002_0DB8F45437AB844CBB5102F807A0AD93102CB212xmbrcdx03ciscoc_
Content-Type: application/xml; name="default[4].xml"
Content-Description: default[4].xml
Content-Disposition: attachment; filename="default[4].xml"; size=3222;
	creation-date="Tue, 02 Apr 2013 01:05:27 GMT";
	modification-date="Tue, 02 Apr 2013 01:05:27 GMT"
Content-ID: <7C3E371EA94B6A438481022DB9CCAD88@emea.cisco.com>
Content-Transfer-Encoding: base64

UEsDBBQABgAIAAAAIQCb6HBP/AAAABwCAAATAAAAW0NvbnRlbnRfVHlwZXNdLnhtbKyRy2rDMBBF
94X+g9C22HK6KKXYzqKPXR+L9AMGeWyL2CMhTULy9x07LpQSAoVuBNLMvffMqFwfxkHtMSbnqdKr
vNAKyfrGUVfpz81Ldq9VYqAGBk9Y6SMmva6vr8rNMWBSoqZU6Z45PBiTbI8jpNwHJKm0Po7Aco2d
CWC30KG5LYo7Yz0xEmc8eei6fMIWdgOr54M8n0hErtXjqW+KqjSEMDgLLKBmqpqzuohDuiDcU/OL
LlvIclHO5ql3Id0sCe+ymugaVB8Q+Q1G4TAsQ+LP8xVIRov5ZeYz0b5tncXG290o68hn48XsTwCr
/4n+zjTz39ZfAAAA//8DAFBLAwQUAAYACAAAACEApdan58AAAAA2AQAACwAAAF9yZWxzLy5yZWxz
hI/PasMwDIfvhb2D0X1R0sMYJXYvpZBDL6N9AOEof2giG9sb69tPxwYKuwiEpO/3qT3+rov54ZTn
IBaaqgbD4kM/y2jhdj2/f4LJhaSnJQhbeHCGo3vbtV+8UNGjPM0xG6VItjCVEg+I2U+8Uq5CZNHJ
ENJKRds0YiR/p5FxX9cfmJ4Z4DZM0/UWUtc3YK6PqMn/s8MwzJ5PwX+vLOVFBG43lExp5GKhqC/j
U72QqGWq1B7Qtbj51v0BAAD//wMAUEsDBBQABgAIAAAAIQBreZYWgwAAAIoAAAAcAAAAdGhlbWUv
dGhlbWUvdGhlbWVNYW5hZ2VyLnhtbAzMTQrDIBBA4X2hd5DZN2O7KEVissuuu/YAQ5waQceg0p/b
1+XjgzfO3xTVm0sNWSycBw2KZc0uiLfwfCynG6jaSBzFLGzhxxXm6XgYybSNE99JyHNRfSPVkIWt
td0g1rUr1SHvLN1euSRqPYtHV+jT9yniResrJgoCOP0BAAD//wMAUEsDBBQABgAIAAAAIQAhWqKE
IQcAANsdAAAWAAAAdGhlbWUvdGhlbWUvdGhlbWUxLnhtbOxZT28bRRS/I/EdRnsvsRMnTaI6VezY
DbRpo9gt6nG8O/ZOM7uzmhkn8Q21RyQkREEcqMSNAwIqtRKX8mkCRVCkfgXezOyud+Jxk5QAFTSH
1jv7e2/e+70/82evXD1KGDogQlKeNoP6e7UAkTTkEU1HzeB2v3tpNUBS4TTCjKekGUyIDK5uvPvO
FbyuYpIQBPKpXMfNIFYqW19YkCEMY/kez0gK74ZcJFjBoxgtRAIfgt6ELSzWaisLCaZpgFKcgNpb
wyENCeprlcFGobzD4DFVUg+ETPS0auJIGGy0X9cIOZFtJtABZs0A5on4YZ8cqQAxLBW8aAY18xcs
bFxZwOu5EFNzZCtyXfOXy+UC0f6imVOMBuWk9W5j7fJWqd8AmJrFdTqddqde6jMAHIbgqbWlqrPR
Xa23Cp0VkP05q7tdW641XHxF/9KMzWutVmt5LbfFKjUg+7Mxg1+trTQ2Fx28AVn88gy+0dpst1cc
vAFZ/MoMvnt5baXh4g0oZjTdn0HrgHa7ufYSMuRs2wtfBfhqLYdPUZANZXbpKYY8VfNyLcH3uOgC
QAMZVjRFapKRIQ4hi9uY0YGgegK8TnDljR0K5cyQngvJUNBMNYMPMgwVMdX38tl3L589Qcf3nx7f
//H4wYPj+z9YRY7UNk5HVakX33z6x6OP0O9Pvn7x8HM/Xlbxv3z/8c8/feYHQvlMzXn+xeNfnz5+
/uUnv3370APfFHhQhfdpQiS6SQ7RHk/AMcOKazkZiPNJ9GNMqxKb6UjiFOtZPPo7KnbQNyeYYQ+u
RVwG7whoHz7gtfE9x+BeLMYqj7fj2fU4cYA7nLMWF14Wruu5KjT3x+nIP7kYV3F7GB/45m7j1Ilv
Z5xB36Q+le2YOGbuMpwqPCIpUUi/4/uEePi6S6nD6w4NBZd8qNBdilqYeinp04GTTVOhbZpAXCY+
AyHeDjc7d1CLM5/XW+TARUJVYOYxvk+YQ+M1PFY48ans44RVCb+BVewzsjcRYRXXkQoiPSKMo05E
pPTJ3BLgbyXo16F1+MO+wyaJixSK7vt03sCcV5FbfL8d4yTzYXs0javY9+U+pChGu1z54DvcrRD9
DHHA6dxw36HECffp3eA2HTkmTRNEvxkLTyyvEe7kb2/ChpiYVgNN3enVCU1f1bgT6Nu54xfXuKFV
Pv/qkcfuN7VlbwIJvprZPtGo5+FOtuc2FxF987vzFh6nuwQKYnaJetuc3zbn4D/fnOfV88W35GkX
hgatt0x2o2223cncXfeQMtZTE0ZuSLPxlrD2RF0Y1HLmxEnKU1gWw09dyTCBgxsJbGSQ4OpDquJe
jDPYtNcDrWQkc9UjiTIu4bBohr26NR42/soeNZf1IcR2DonVDo/s8JIeLs4apRpj1cgcaIuJlrSC
s062dDlXCr69zmR1bdSZZ6sb00xTdGYrXdYUm0M5UF66BoMlm7CpQbAVApZX4Myvp4bDDmYk0rzb
GBVhMVH4e0KUe20diXFEbIic4QqbdRO7IoVm/NPu2Rw5H5sla0Da6UaYtJifP2ckuVAwJRkET1YT
S6u1xVJ02AzWlheXAxTirBkM4ZgLP5MMgib1NhCzEdwVhUrYrD21Fk2RTj1e82dVHW4u5hSMU8aZ
kGoLy9jG0LzKQ8VSPZO1f3G5oZPtYhzwNJOzWbG0Cinyr1kBoXZDS4ZDEqpqsCsjmjv7mHdCPlZE
9OLoEA3YWOxhCD9wqv2JqITbClPQ+gGu1jTb5pXbW/NOU73QMjg7jlkW47xb6quZouIs3PST0gbz
VDEPfPPabpw7vyu64i/KlWoa/89c0csBXB4sRToCIdzsCox0pTQDLlTMoQtlMQ27AtZ90zsgW+B6
Fl4D+XC/bP4X5ED/b2vO6jBlDWdAtUdHSFBYTlQsCNmFtmSy7xRl9XzpsSpZrshkVMVcmVmzB+SA
sL7ugSu6BwcohlQ33SRvAwZ3Mv/c57yCBiO9R6nWm9PJyqXT1sA/vXGxxQxOndhL6Pwt+C9NLFf3
6epn5Y14sUZWHdEvprukRlEVzuK3tpZP9ZomnGUBrqy1tmPNeLy4XBgHUZz1GAbL/UwGV0BI/wPr
HxUhsx8r9ILa53vQWxF8e7D8IcjqS7qrQQbpBml/DWDfYwdtMmlVltp856NZKxbrC96olvOeIFtb
dpZ4n5PschPlTufU4kWSnTPscG3H5lINkT1ZojA0LM4hJjDmK1f1QxQf3INAb8GV/5jZT1MygydT
B9muMNk14NEk/8mkXXBt1ukzjEaydI8MEY2OivNHyYQtIft5pNgiG7QW04lWCi75Dg2uYI7Xona1
LIUXTxcuJczM0LJLYXOX5lMAH8fyxq2PdoC3TdZ6rYurYIqlf4WyMxjvp8x78jkrZfag+MpAvQZl
6ujVlOVMAXmziQefNwWGo1fP9F9YdGymm5Td+BMAAP//AwBQSwMEFAAGAAgAAAAhAA3RkJ+2AAAA
GwEAACcAAAB0aGVtZS90aGVtZS9fcmVscy90aGVtZU1hbmFnZXIueG1sLnJlbHOEj00KwjAUhPeC
dwhvb9O6EJEm3YjQrdQDhOQ1DTY/JFHs7Q2uLAguh2G+mWm7l53JE2My3jFoqhoIOumVcZrBbbjs
jkBSFk6J2TtksGCCjm837RVnkUsoTSYkUiguMZhyDidKk5zQilT5gK44o49W5CKjpkHIu9BI93V9
oPGbAXzFJL1iEHvVABmWUJr/s/04GolnLx8WXf5RQXPZhQUoosbM4CObqkwEylu6usTfAAAA//8D
AFBLAQItABQABgAIAAAAIQCb6HBP/AAAABwCAAATAAAAAAAAAAAAAAAAAAAAAABbQ29udGVudF9U
eXBlc10ueG1sUEsBAi0AFAAGAAgAAAAhAKXWp+fAAAAANgEAAAsAAAAAAAAAAAAAAAAALQEAAF9y
ZWxzLy5yZWxzUEsBAi0AFAAGAAgAAAAhAGt5lhaDAAAAigAAABwAAAAAAAAAAAAAAAAAFgIAAHRo
ZW1lL3RoZW1lL3RoZW1lTWFuYWdlci54bWxQSwECLQAUAAYACAAAACEAIVqihCEHAADbHQAAFgAA
AAAAAAAAAAAAAADTAgAAdGhlbWUvdGhlbWUvdGhlbWUxLnhtbFBLAQItABQABgAIAAAAIQAN0ZCf
tgAAABsBAAAnAAAAAAAAAAAAAAAAACgKAAB0aGVtZS90aGVtZS9fcmVscy90aGVtZU1hbmFnZXIu
eG1sLnJlbHNQSwUGAAAAAAUABQBdAQAAIwsAAAAA

--_002_0DB8F45437AB844CBB5102F807A0AD93102CB212xmbrcdx03ciscoc_--

From leo.liubing@huawei.com  Tue Apr  2 00:46:48 2013
Return-Path: <leo.liubing@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 A553D21F985C; Tue,  2 Apr 2013 00:46:48 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J0eBt83nWuZs; Tue,  2 Apr 2013 00:46:47 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D362121F985B; Tue,  2 Apr 2013 00:46:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARI19611; Tue, 02 Apr 2013 07:46:44 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 2 Apr 2013 08:46:32 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 2 Apr 2013 15:46:41 +0800
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.42]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Tue, 2 Apr 2013 15:46:34 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Robert Sparks <rjsparks@nostrum.com>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "renum@ietf.org" <renum@ietf.org>
Subject: RE: Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
Thread-Topic: Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
Thread-Index: AQHOLxocMFWfMeFT5EmCEaSFUOUemZjCTHqg
Date: Tue, 2 Apr 2013 07:46:33 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>
References: <5159F239.1060001@nostrum.com>
In-Reply-To: <5159F239.1060001@nostrum.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Tue, 02 Apr 2013 08:31:16 -0700
Cc: "gen-art@ietf.org" <gen-art@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: Tue, 02 Apr 2013 07:46:48 -0000

Hi, Robert

Thanks a lot for your careful and detailed review. It is very helpful to re=
fine the draft.
Please see replies inline.=20

> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> Sent: Tuesday, April 02, 2013 4:47 AM
> To: 6renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
> Cc: gen-art@ietf.org; ietf@ietf.org
> Subject: Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
>=20
> 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-6renum-gap-analysis-05.txt
> Reviewer: Robert Sparks
> Review Date: April 1, 2013
> IETF LC End Date: April 10,2013
> IESG Telechat date: Not yet scheduled for a telechat
>=20
> Summary: This document is not ready for publication as an Informational
> RFC.
>           It may be on the right track, but there issues both in substanc=
e
>           and form that need to be addressed.
>=20
> Major issues:
>=20
> The document doesn't provide what its title and abstract claim it will
> provide.
> For instance, the abstract claims a gap analysis is presented following
> a renumbering
> event procedure summary, but neither appear in the draft.=20

[Bing] In fact the subtitles have the implication of a renumbering event pr=
ocedure summary. But it is indeed not explicit in the main texts. We'll add=
 some texts to represent it explicitly in the next version.

> There are a few places
> in the text that say "this is a gap", but usually it's not clear what
> "this" means.

[Bing] We'll make them more clear in the next version.=20
=20
> The stated intent is to identify missing capabilities (gaps) and the work
> needed to provide them. The document should lay these out very clearly.
> As the document is currently written, it is difficult to pull out a simpl=
e list of
> identified gaps.=20

[Bing] A good suggestion. We once had a summary subtitle in previous versio=
ns, but we deleted it since we thought it might be a little redundancy.=20
Now we can add it back, it could be helpful for the readers.

> While addressing that, it would help more to provide some
> sense of the relative importance of addressing each of the gaps identifie=
d.

[Bing] We used to divide the gaps into "solvable" and "unsolvable". Some im=
portant gaps might be unsolvable; while some of the solvable ones might not=
 be so important. We'll consider to reflex the two dimensions in the next v=
ersion.

> There are several significant issues with clarity. I will point to the mo=
st
> difficult in a section below.
>=20
> ----------------------
> Minor issues:
>=20
> The document currently references
> draft-chown-v6ops-renumber-thinkabout
> several times.
> That document is long expired (2006). It would be better to simply
> restate what is
> important from that document here and reference it only once in the
> acknowlegements
> rather than send the reader off to read it.

[Bing] draft-chown-v6ops-renumber-thinkabout is an important input for the =
gap analysis. Although the draft is expired, most of the content are still =
valid.=20
draft-chown is a more comprehensive analysis, while the gap draft is focusi=
ng on gaps in enterprise renumbering. So it might not easy to abstract seve=
ral points as important from draft-chown to this draft. We actually encoura=
ge people to read it.

> RFC4076 seems to say very similar things to this document. Should it
> have been referenced?

[Bing] RFC4076 is a more specific case of stateless-DHCPv6 [RFC3736], which=
 might not be common usage in enterprise. But sure we can consider referenc=
e it.=20

> Section 5.3 punts discussion of static addresses off to RFC 6866. That
> document was scoped
> only to Enterprise Networks. The scope of this document is larger. Are
> there gaps because
> of that difference in scope that were missed? Would it make sense to
> summarize any gaps
> RFC 6866 identified that are relevant to this document here?

[Bing] This document scope is also for enterprise (it is the 6renum WG scop=
e). In fact the RFC6866 is a sub-document of this draft. We considered stat=
ic address problem is an important topic that need a separated document to =
describe. We can consider add a brief summary there.

> Should section 8 belong to some other document? It looks like
> operational renumbering
> advice/considerations, but doesn't seem to be exploring renumbering
> gaps, except for
> the very short section 8.2 which says "we need a better mechanism"
> without much explanation.

[Bing] The multicast and mobility in section 8 were considered as important=
 standalone topics that need to be addressed.=20
Since multicast is complex, we need more texts to describe the problem than=
 describing the gaps directly. But we can make the gaps more clear.

> ----------------------
> Text needing clarity (more than nits):

[Bing] We'll also deal with the following clarity and nits comments in the =
next version. Thanks for the careful review.

Best regards,
Bing


> Section 4.1, second paragraph: The first sentence needs to be
> simplified. Something like
> "Delegation routers may need to renumber themselves with new delegated
> prefixes" perhaps.
> The second sentence speaks of "the router renumbering issue" as if it's
> clear which particular
> issue you're actually talking about. Is there a gap here? If so,
> consider replacing the entire
> paragraph with an explicit description of the gap.
>=20
> Section 5.1, first bullet, 2nd paragraph: The third sentence (starting
> "In ND protocol,")
> makes no sense. The fourth sentence is also hard to parse.
>=20
> Section 5.1, first bullet. The list below "the impact of ambiguous M/O
> flags" says things like
> "there is no standard" and "it is unspecified". I think you are trying
> to say that there is
> ambiguity in what's written, not that nothing's written. This entire
> list would benefit from
> being recast in terms of what needs to be done (what are the gaps?).
>=20
> Section 5.2, last paragraph. It's not clear what you are trying to say
> here. Is it simply
> that the natural pressures in an ISP make it more likely that an ISP
> would choose to use
> DNS names as part of configuration than an enterprise would? If so, can
> you list what some
> of those pressures are? What gap is this discussion trying to identify?
>=20
> Section 6.1, first paragraph, first sentence (starting "For DNS records
> update") - this sentence
> does not parse. What is it trying to say, and what's the gap you are
> trying to point to?
>=20
> Section 6.3, 6th paragraph. "So there's a big gap for configuration
> aggregation" is
> unclear. Is it that configuration isn't stored in one place, or that it
> can't be
> found through one place, or something different?
>=20
> Section 7.1 second bullet. Taking this partial quote from RFC4192
> destroyed the meaning
> of the sentence. The original sentence said "The suggestion applies" -
> this misquote says
> "reducing the delay applies". There's no benefit to quoting 4192
> directly - say what you
> mean and reference 4192.
>=20
>=20
> ----------------------
> Nits/editorial comments:
>=20
> There are a few sentences ending with "etc." in the document. Please
> consider deleting the
> word from the list - it doesn't help each sentence make its point.
>=20
> Introduction: "Future efforts may be achieved in the future." doesn't
> add anything
> to the document. I suggest deleting the sentence.
>=20
> Section 3.2: Consider deleting "basically" from "an IPAM is basically use=
d"
>=20
> Section 5.1: draft-ietf-dhc-host-gen-id is no longer new (and it
> definitely will not be
> new a few years after this is published as an RFC. Please remove "the
> new IETF DHC WG
> document" from the sentence it appears in.
>=20
> Section 5.1: This sentence "Using these flags, the two separated address
> configuration
> modes are somehow correlated." is not clear. ("somehow" isn't going to
> help the reader
> in any case). Are you trying to say "This flags provide some degree of
> correlation in
> the use of these separate configuration protocols"? Could you rewrite
> this explicitly
> identifying gaps?
>=20
> Section 5.1: Please delete "mainly" from "flags mainly includes"
>=20
> Section 5.2 (and other places): Is it really the case that router
> operators have to
> resort to restarting routers in order to pick up configuration changes
> these days?
> RFC2072 pointed to that, and in 1997 it may have been more routine to
> restart, but
> for modern systems, that action is more extreme. Surely for something as
> basic as
> a cache-clear, restarts are vanishingly rare.
>=20
> Section 5.3: Instead of "the static address issue" could you say
> "discussing the
> problems associated with renumbering hosts with static addresses"?
>=20
> Section 6, first paragraph: It's not clear what "the entries in the
> site" means.
> What's a site and what are entries in this case.  I suggest "then any
> configuration
> or data store containing the previous number must be updated." as a
> replacement, and
> then say "Some examples include:" and list DNS records and ACLs.
> Consider pointing
> forward to the section on DNS Authority listed under "Gaps considered
> unsolvable".
> Note that some of those ACLS are going to be on machines under control
> by another
> authority, having the same problem you point to for DNS.
>=20
> Section 6.1: What do you mean by "the major DNS systems". Do you mean
> the major
> implementations like BIND?
>=20
> Section 6.2, first paragraph. This suffers from the ambiguity of the word
> "records". You meant it as a verb (DNS writes something down) instead of
> a noun (the DNS system contains DNS records). I suggest rewriting this
> paragraph to avoid the ambiguity. "While DNS entries contain addresses" -
> "Hosts are configured with" - "hosts must update these addreses"
>=20
> Section 6.2 second paragraph. Please be more clear what you mean by
> "DNS lifetimes". You are not trying to refer to the time-to-live of
> a DNS record. Rather, you are trying to say how long a bit of configurati=
on
> obtained through DHCP should be considered relevant. If there's a gap
> (a need for more protocol), please be explicit. You will proabably want
> to engage the DHC working group if you are thinking about asking that
> DHCP tell you how long DNS server configuration value is good for if you
> are really trying to decouple it from the lease time. (Is that what
> you're suggesting? If not, then what's the problem?)
>=20
> Section 6.3, second bullet, second sub-bullet: What does "the entries" me=
an?
> Please be specific. Do you mean "configured addresses or prefixes" or
> something
> else? Or is this intended to extend to updating things like DNS zone file=
s?
> As written, it is vague.
>=20
> Section 6.3, last sentence. "It is a big gap currently." What specificall=
y
> is the big gap. Is it a lack of a standard protocol for updating
> configurations
> so that there won't be some many vendor-private protocols deployed?
> Please consider replacing "It" with something explicit.
>=20
> Seciton 7.1: The first bullet does not parse. If I guess its meaning
> correctly
> (that it would be benificial to tell hosts that local DNS has been
> updated and
> they may want to make fresh queries), please be careful with the
> wording. The
> hosts don't know which names are likely to resolve locally.
>=20
> Section 7.1, third bullet - This isn't obviously about notification. Why
> is it
> in this section? What's the gap this is trying to identify?
>=20
> Section 7.2 - how is this section helping the document? What are the gaps=
?
>=20
> Section 7.3 - again, how is this section helping the document acheive
> its goal?
> Would anyone working to close gaps do anything differently if this
> section were
> deleted?
>=20
> Section 9.4 - what is it about these that make them gaps, much less
> unsolvable gaps.
> Is this discussion in the wrong section of the document?
>=20
> Section 10 - The sentence starting "In the LAN" doesn't parse. Did you me=
an
> "may be needed to"?
>=20
> Section 10, last paragraph: This sentence doesn't make sense. It would
> make more
> sense if you replaced "blocking access" with "protecting", but it would
> be even
> better to expand the discussion and explain what you mean by interruption=
.


From eburger@cs.georgetown.edu  Tue Apr  2 03:47:07 2013
Return-Path: <eburger@cs.georgetown.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 40A8D21F984B for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 03:47:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level: 
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R-UBqwAihOk8 for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 03:47:06 -0700 (PDT)
Received: from karma.cs.georgetown.edu (karma.cs.georgetown.edu [141.161.20.3]) by ietfa.amsl.com (Postfix) with ESMTP id 61E1621F984A for <ietf@ietf.org>; Tue,  2 Apr 2013 03:47:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by karma.cs.georgetown.edu (Postfix) with ESMTP id E1F7043C7D; Tue,  2 Apr 2013 06:47:05 -0400 (EDT)
X-Virus-Scanned: by amavisd-new at cs.georgetown.edu
Received: from karma.cs.georgetown.edu ([127.0.0.1]) by localhost (karma.cs.georgetown.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o9IU1faDqsa0; Tue,  2 Apr 2013 06:47:02 -0400 (EDT)
Received: from karma.cs.georgetown.edu (151.sub-174-227-192.myvzw.com [174.227.192.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by karma.cs.georgetown.edu (Postfix) with ESMTP id 0DB7943C49; Tue,  2 Apr 2013 06:47:01 -0400 (EDT)
Message-ID: <247dcccd-588d-4853-ad44-910b1a8c63c0@blur>
From: "Eric Burger" <eburger@cs.georgetown.edu>
To: alexey.melnikov@isode.com
Date: Tue, 2 Apr 2013 06:47:18 -0400
X-Mailer: Motorola android mail 1.0
MIME-Version: 1.0
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch=?UTF-8?B?PyAgICAgICAgIA==?= (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
X-Priority: 3
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu> <515AAACD.90003@isode.com>
In-Reply-To: <515AAACD.90003@isode.com>
Content-Type: multipart/alternative; boundary="Motorola-A-Mail-NfWEbRqmY3WwCO8y"
X-Mailman-Approved-At: Tue, 02 Apr 2013 08:31:16 -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: Tue, 02 Apr 2013 10:47:07 -0000

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

Works for me.

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

-----Original message-----
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Burger Eric <eburger@cs.georgetown.edu>
Cc: Robert Sparks <rjsparks@nostrum.com>, ietf@ietf.org
Sent: Tue, Apr 2, 2013 09:53:39 GMT+00:00
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch?           
(was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)

Hi Eric,
I am sorry if I sound pedantic below, but I think your suggestion can be 
misinterpreted and thus needs improving:

On 28/03/2013 12:13, Burger Eric wrote:
> Rather than guessing all of the bad things that could happen, I would  
offer it would be better to say what we mean, like:
> 	The IMAP interface MUST NOT provide any IMAP facilities that modify the  
underlying message and message metadata, such as mailbox, flags, marking for  
deletion, etc. If the client is authenticated and authorized, the IMAP  
interface MUST provide per-user marking of the underlying message as read or  
flagged.
One way to implement this is in an IMAP server is to always fail 
commands for modifying message metadata. Another way of implementing 
this is to allow them, but ignore (don't persist) results. Both ways 
were used in the past and they have different effect on IMAP clients. I 
hope the requirement is intended to allow for either.

Another thing to consider is that for IMAP servers that implement IMAP 
ACL, the easiest way to meet the intended requirement is by not allowing 
unauthorized users to access some commands on a mailbox. Again, a 
possible reading of your suggested text is that that is not allowed.

So, my suggestion is to change "MUST NOT provide any IMAP facilities 
..." to "MUST disallow any IMAP facilities ...".



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

PGh0bWw+PGhlYWQ+PHN0eWxlIHR5cGU9InRleHQvY3NzIj5ib2R5IHt3b3JkLXdyYXA6IGJyZWFr
LXdvcmQ7IGJhY2tncm91bmQtY29sb3I6I2ZmZmZmZjt9PC9zdHlsZT48L2hlYWQ+PGJvZHk+PGRp
diBzdHlsZT0iZm9udC1mYW1pbHk6IHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTZweCI+V29ya3Mg
Zm9yIG1lLjxicj48YnI+LS08YnI+U2VudCBmcm9tIG15IG1vYmlsZSBkZXZpY2UuIFRoYW5rcyBi
ZSB0byBsZW1vbmFkZSEgPGEgaHJlZj0iaHR0cDovL3d3dy5zdGFuZGFyZHN0cmFjay5jb20vaWV0
Zi9sZW1vbmFkZS8iPmh0dHA6Ly93d3cuc3RhbmRhcmRzdHJhY2suY29tL2lldGYvbGVtb25hZGUv
PC9hPjwvZGl2Pjxicj48YnI+LS0tLS1PcmlnaW5hbCBtZXNzYWdlLS0tLS08YnI+PGJsb2NrcXVv
dGUgc3R5bGU9IjsgYm9yZGVyLWxlZnQ6IDJweCBzb2xpZCByZ2IoMTYsIDE2LCAyNTUpOyBtYXJn
aW4tbGVmdDogNXB4OyBwYWRkaW5nLWxlZnQ6IDVweDsiPjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5
OiBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHgiPjxiPkZyb206IDwvYj5BbGV4ZXkgTWVsbmlr
b3YgJmx0O2FsZXhleS5tZWxuaWtvdkBpc29kZS5jb20mZ3Q7PGI+PGJyPlRvOiA8L2I+QnVyZ2Vy
IEVyaWMgJmx0O2VidXJnZXJAY3MuZ2VvcmdldG93bi5lZHUmZ3Q7PGI+PGJyPkNjOiA8L2I+Um9i
ZXJ0IFNwYXJrcyAmbHQ7cmpzcGFya3NAbm9zdHJ1bS5jb20mZ3Q7LCBpZXRmQGlldGYub3JnPGI+
PGJyPlNlbnQ6IDwvYj5UdWUsIEFwciAyLCAyMDEzIDA5OjUzOjM5IEdNVCswMDowMDxiPjxicj5T
dWJqZWN0OiA8L2I+UmU6IE1pc3NpbmcgcmVxdWlyZW1lbnQgaW4gZHJhZnQtc3BhcmtzLWdlbmFy
ZWEtaW1hcGFyY2g/ICAgICAgICAgICh3YXMgUmU6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiAt
IGRyYWZ0LXNwYXJrcy1nZW5hcmVhLWltYXBhcmNoLTA1LnR4dCk8YnI+PGJyPjwvZGl2PkhpIEVy
aWMsPGJyPkkgYW0gc29ycnkgaWYgSSBzb3VuZCBwZWRhbnRpYyBiZWxvdywgYnV0IEkgdGhpbmsg
eW91ciBzdWdnZXN0aW9uIGNhbiBiZSA8YnI+bWlzaW50ZXJwcmV0ZWQgYW5kIHRodXMgbmVlZHMg
aW1wcm92aW5nOjxicj48YnI+T24gMjgvMDMvMjAxMyAxMjoxMywgQnVyZ2VyIEVyaWMgd3JvdGU6
PGJyPj4gUmF0aGVyIHRoYW4gZ3Vlc3NpbmcgYWxsIG9mIHRoZSBiYWQgdGhpbmdzIHRoYXQgY291
bGQgaGFwcGVuLCBJIHdvdWxkIG9mZmVyIGl0IHdvdWxkIGJlIGJldHRlciB0byBzYXkgd2hhdCB3
ZSBtZWFuLCBsaWtlOjxicj4+IAlUaGUgSU1BUCBpbnRlcmZhY2UgTVVTVCBOT1QgcHJvdmlkZSBh
bnkgSU1BUCBmYWNpbGl0aWVzIHRoYXQgbW9kaWZ5IHRoZSB1bmRlcmx5aW5nIG1lc3NhZ2UgYW5k
IG1lc3NhZ2UgbWV0YWRhdGEsIHN1Y2ggYXMgbWFpbGJveCwgZmxhZ3MsIG1hcmtpbmcgZm9yIGRl
bGV0aW9uLCBldGMuIElmIHRoZSBjbGllbnQgaXMgYXV0aGVudGljYXRlZCBhbmQgYXV0aG9yaXpl
ZCwgdGhlIElNQVAgaW50ZXJmYWNlIE1VU1QgcHJvdmlkZSBwZXItdXNlciBtYXJraW5nIG9mIHRo
ZSB1bmRlcmx5aW5nIG1lc3NhZ2UgYXMgcmVhZCBvciBmbGFnZ2VkLjxicj5PbmUgd2F5IHRvIGlt
cGxlbWVudCB0aGlzIGlzIGluIGFuIElNQVAgc2VydmVyIGlzIHRvIGFsd2F5cyBmYWlsIDxicj5j
b21tYW5kcyBmb3IgbW9kaWZ5aW5nIG1lc3NhZ2UgbWV0YWRhdGEuIEFub3RoZXIgd2F5IG9mIGlt
cGxlbWVudGluZyA8YnI+dGhpcyBpcyB0byBhbGxvdyB0aGVtLCBidXQgaWdub3JlIChkb24ndCBw
ZXJzaXN0KSByZXN1bHRzLiBCb3RoIHdheXMgPGJyPndlcmUgdXNlZCBpbiB0aGUgcGFzdCBhbmQg
dGhleSBoYXZlIGRpZmZlcmVudCBlZmZlY3Qgb24gSU1BUCBjbGllbnRzLiBJIDxicj5ob3BlIHRo
ZSByZXF1aXJlbWVudCBpcyBpbnRlbmRlZCB0byBhbGxvdyBmb3IgZWl0aGVyLjxicj48YnI+QW5v
dGhlciB0aGluZyB0byBjb25zaWRlciBpcyB0aGF0IGZvciBJTUFQIHNlcnZlcnMgdGhhdCBpbXBs
ZW1lbnQgSU1BUCA8YnI+QUNMLCB0aGUgZWFzaWVzdCB3YXkgdG8gbWVldCB0aGUgaW50ZW5kZWQg
cmVxdWlyZW1lbnQgaXMgYnkgbm90IGFsbG93aW5nIDxicj51bmF1dGhvcml6ZWQgdXNlcnMgdG8g
YWNjZXNzIHNvbWUgY29tbWFuZHMgb24gYSBtYWlsYm94LiBBZ2FpbiwgYSA8YnI+cG9zc2libGUg
cmVhZGluZyBvZiB5b3VyIHN1Z2dlc3RlZCB0ZXh0IGlzIHRoYXQgdGhhdCBpcyBub3QgYWxsb3dl
ZC48YnI+PGJyPlNvLCBteSBzdWdnZXN0aW9uIGlzIHRvIGNoYW5nZSAiTVVTVCBOT1QgcHJvdmlk
ZSBhbnkgSU1BUCBmYWNpbGl0aWVzIDxicj4uLi4iIHRvICJNVVNUIGRpc2FsbG93IGFueSBJTUFQ
IGZhY2lsaXRpZXMgLi4uIi48YnI+PGJyPjwvYmxvY2txdW90ZT48L2JvZHk+PC9odG1sPg0K


--Motorola-A-Mail-NfWEbRqmY3WwCO8y--

From paul.doolan@nsn.com  Tue Apr  2 05:00:08 2013
Return-Path: <paul.doolan@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 A3A0B21F9777; Tue,  2 Apr 2013 05:00:08 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vyrr2vaXMhmI; Tue,  2 Apr 2013 05:00:07 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 634D521F9756; Tue,  2 Apr 2013 05:00:07 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r32C02gC022611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 2 Apr 2013 14:00:03 +0200
Received: from SGSIHTC002.nsn-intra.net ([10.159.225.19]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r32BwVug015124 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Apr 2013 14:00:01 +0200
Received: from SGSIHTC004.nsn-intra.net (10.159.225.21) by SGSIHTC002.nsn-intra.net (10.159.225.19) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 2 Apr 2013 19:58:34 +0800
Received: from SGSIMBX001.nsn-intra.net ([169.254.1.109]) by SGSIHTC004.nsn-intra.net ([10.159.225.21]) with mapi id 14.03.0123.003; Tue, 2 Apr 2013 19:58:34 +0800
From: "Doolan, Paul (NSN - US/Irving)" <paul.doolan@nsn.com>
To: "ext Luyuan Fang (lufang)" <lufang@cisco.com>, Russ Housley <housley@vigilsec.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt>
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt>
Thread-Index: AQHOLz41gpocwnlmdkCids41O+SOypjC0o8w
Date: Tue, 2 Apr 2013 11:58:33 +0000
Message-ID: <0D9D63ECB53A1449B376D2196ADC34159B2D43@SGSIMBX001.nsn-intra.net>
References: <A7D6179B-4760-4B3B-8547-769DADAA4243@vigilsec.com> <0DB8F45437AB844CBB5102F807A0AD93102CB212@xmb-rcd-x03.cisco.com>
In-Reply-To: <0DB8F45437AB844CBB5102F807A0AD93102CB212@xmb-rcd-x03.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.159.42.121]
X-TM-AS-Product-Ver: SMEX-10.0.0.4238-6.000.1038-15056.000
X-TM-AS-Result: No--9.880300-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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: 6332
X-purgate-ID: 151667::1364904003-000077CC-F50D59F9/0-0/0-0
X-Mailman-Approved-At: Tue, 02 Apr 2013 08:31:16 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Apr 2013 12:00:08 -0000

Hi Luyuan,

You wrote (in part):

......since multiplexing of bursty sources is far more efficient over tradi=
tional circuit-based
TDM technologies.

Which is not true and probably not what you meant.=20

A better formulation might be "since packet multiplexing of traffic from bu=
rsty sources provides more efficient use of bandwidth than traditional circ=
uit-based TDM technologies".

To be honest however, I'd cut the traditional and use only TDM (since some =
'circuit' based technologies also offer packet multiplexing) so I'd reduce =
it to:

A better formulation might be "since packet multiplexing of traffic from bu=
rsty sources provides more efficient use of bandwidth than TDM technologies=
".


cheers,
pd


-----Original Message-----
From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of ext=
 Luyuan Fang (lufang)
Sent: Monday, April 01, 2013 9:05 PM
To: Russ Housley; ietf@ietf.org
Cc: mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.=
txt>

Hi Russ,

Thanks for your comments, very good points.
Sorry for the delay in replying, I was out of office.

=20
The following is my proposed text for replacing the current first
paragraph of section 1.2.

=20
Traditional transport technologies include SONET/SDH, TDM, and ATM. There
is a transition away from these transport technologies to new packet
technologies.
In addition to the ever increasing demand for bandwidth, the packet
technologies offer these key advantages:

=20
Bandwidth efficiency: Transport technologies supports fixed Bandwidth
only, no packet statistical multiplexing, bandwidth is reserved in
transport
whether used or not by clients. Packet technologies support statistical
multiplexing,
this is the most important motivation for the transition from traditional
transport technologies to packet technologies. The proliferation of new
distributed applications which communicate with servers over the network
in a
bursty fashion has been driving the adoption of packet transport
techniques, since
multiplexing of bursty sources is far more efficient over traditional
circuit-based
TDM technologies.

=20
Flexible data rate connections: Traditional transport connection
granularity
is limited to the rigid PDH or SONET hierarchy (e.g., DS1, DS3, OC3, OC12,
etc.).
Packet technologies support flexible data rate connections. The support of
finer data rate granularity is important for today=B9s wireline and wireles=
s
services and applications.

=20
QoS support: While traditional transport, such as TDM transport has
very limited QoS support, packet transport can provide needed QoS
treatment for
IPTV, Voice and Video over IP applications.

=20
The root cause for transport moving to packet transport is the shift
of application from TDM to packet. For example, Voice TDM to VoIP; Video to
Video over IP; TDM access lines to Ethernet; TDM VPNs to IP VPNs and
Ethernet
VPNs. In addition, network convergence and technology refreshes demand for
common and flexible infrastructure that provides multiple services.

=20
Thanks,
Luyuan



-----Original Message-----
From: Russ Housley <housley@vigilsec.com>
Date: Saturday, March 23, 2013 3:16 PM
To: "ietf@ietf.org" <ietf@ietf.org>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Last
Call:	<draft-ietf-mpls-tp-use-cases-and-design-06.txt>

>I wonder if the direction of Section 1.2 can be revised to make it more
>of an engineering document.
>
>It currently says:
>
>   In recent years, the urgency for moving from traditional transport
>   technologies, such as SONET/SDH, TDM, and ATM, to new packet
>   technologies has been rising. This is largely due to the fast growing
>   demand for bandwidth, which has been fueled by the following factors:
>   ...
>
>Please consider an approach that describes the the reasons behind the
>transition from the network operator and network user perspectives:
>
>   Traditional transport technologies include SONET/SDH, TDM, and ATM.
>   There is a transition away from these transport technologies to new
>   packet technologies. In addition to the ever increasing demand for
>   bandwidth, the packet technologies offer these advantages:
>   ...
>
>The fact that IP networks are being used for new applications and that
>the legacy devices are getting old does not motivate the transition to
>packet technologies.  The advantages that packet technologies offer for
>these new applications is the thing that needs to be highlighted here,
>even if it is just a list of bullets.
>
>It seems like the only sentence that addresses this point in Section 1.2
>is: "It streamlines the operation, reduces the overall complexity, and
>improves end-to-end convergence."
>
>Thanks,
>  Russ
>
>On Jan 28, 2013, at 3:01 PM, The IESG wrote:
>
>> The IESG has received a request from the Multiprotocol Label Switching
>>WG
>> (mpls) to consider the following document:
>> - 'MPLS-TP Applicability; Use Cases and Design'
>>  <draft-ietf-mpls-tp-use-cases-and-design-06.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 2013-02-11. 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
>>   This document provides applicability, use case studies and network
>>   design considerations for the Multiprotocol Label Switching Transport
>>   Profile (MPLS-TP). The use cases include Metro Ethernet access and
>>   aggregation transport, Mobile backhaul, and packet optical transport.
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-use-cases-and-design/
>>=20
>> IESG discussion can be tracked via
>>=20
>>http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-use-cases-and-design/b
>>allot/
>>=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


From leo.liubing@huawei.com  Tue Apr  2 05:36:36 2013
Return-Path: <leo.liubing@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 150B521F976B; Tue,  2 Apr 2013 05:36:36 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dQUq1fovwMPC; Tue,  2 Apr 2013 05:36:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 608A421F9767; Tue,  2 Apr 2013 05:36:34 -0700 (PDT)
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 APZ64617; Tue, 02 Apr 2013 12:36:33 +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.7; Tue, 2 Apr 2013 13:36:01 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 2 Apr 2013 13:36:09 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.42]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Tue, 2 Apr 2013 20:36:05 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
Thread-Topic: [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
Thread-Index: AQHOLxocMFWfMeFT5EmCEaSFUOUemZjCTHqg///gYoCAALD3MA==
Date: Tue, 2 Apr 2013 12:36:05 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED729@nkgeml506-mbx.china.huawei.com>
References: <5159F239.1060001@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com> <515AABB5.5050202@gmail.com>
In-Reply-To: <515AABB5.5050202@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Tue, 02 Apr 2013 08:31:16 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Apr 2013 12:36:36 -0000

SGksIEJyaWFuDQoNCj4gPj4gVGhlIGRvY3VtZW50IGN1cnJlbnRseSByZWZlcmVuY2VzDQo+ID4+
IGRyYWZ0LWNob3duLXY2b3BzLXJlbnVtYmVyLXRoaW5rYWJvdXQNCj4gPj4gc2V2ZXJhbCB0aW1l
cy4NCj4gPj4gVGhhdCBkb2N1bWVudCBpcyBsb25nIGV4cGlyZWQgKDIwMDYpLiBJdCB3b3VsZCBi
ZSBiZXR0ZXIgdG8gc2ltcGx5DQo+ID4+IHJlc3RhdGUgd2hhdCBpcw0KPiA+PiBpbXBvcnRhbnQg
ZnJvbSB0aGF0IGRvY3VtZW50IGhlcmUgYW5kIHJlZmVyZW5jZSBpdCBvbmx5IG9uY2UgaW4gdGhl
DQo+ID4+IGFja25vd2xlZ2VtZW50cw0KPiA+PiByYXRoZXIgdGhhbiBzZW5kIHRoZSByZWFkZXIg
b2ZmIHRvIHJlYWQgaXQuDQo+ID4NCj4gPiBbQmluZ10gZHJhZnQtY2hvd24tdjZvcHMtcmVudW1i
ZXItdGhpbmthYm91dCBpcyBhbiBpbXBvcnRhbnQgaW5wdXQgZm9yDQo+IHRoZSBnYXAgYW5hbHlz
aXMuIEFsdGhvdWdoIHRoZSBkcmFmdCBpcyBleHBpcmVkLCBtb3N0IG9mIHRoZSBjb250ZW50IGFy
ZSBzdGlsbA0KPiB2YWxpZC4NCj4gPiBkcmFmdC1jaG93biBpcyBhIG1vcmUgY29tcHJlaGVuc2l2
ZSBhbmFseXNpcywgd2hpbGUgdGhlIGdhcCBkcmFmdCBpcw0KPiBmb2N1c2luZyBvbiBnYXBzIGlu
IGVudGVycHJpc2UgcmVudW1iZXJpbmcuIFNvIGl0IG1pZ2h0IG5vdCBlYXN5IHRvIGFic3RyYWN0
DQo+IHNldmVyYWwgcG9pbnRzIGFzIGltcG9ydGFudCBmcm9tIGRyYWZ0LWNob3duIHRvIHRoaXMg
ZHJhZnQuIFdlIGFjdHVhbGx5DQo+IGVuY291cmFnZSBwZW9wbGUgdG8gcmVhZCBpdC4NCj4gDQo+
IFJvYmVydCBpcyByaWdodCwgdGhvdWdoLCBzZW5kaW5nIHBlb3BsZSB0byBhIGxvbmctZXhwaXJl
ZCBkcmFmdCBpcyBhIGJhZCBpZGVhLg0KPiBPZiBjb3Vyc2Ugd2UgaGF2ZSB0byBhY2tub3dsZWRn
ZSBpdCwgYnV0IG1heWJlIHdlIHNob3VsZCBwdWxsIHNvbWUgb2YgaXRzDQo+IHRleHQNCj4gaW50
byBhbiBBcHBlbmRpeC4NCj4gDQo+IFRpbSBDaG93biwgYW55IG9waW5pb24/DQoNCltCaW5nXSBP
aywgdGhlbiB3ZSBjYW4gaGVhciBzb21lIG9waW5pb25zIGZyb20gVGltLg0KDQo+IA0KPiA+PiBS
RkM0MDc2IHNlZW1zIHRvIHNheSB2ZXJ5IHNpbWlsYXIgdGhpbmdzIHRvIHRoaXMgZG9jdW1lbnQu
IFNob3VsZCBpdA0KPiA+PiBoYXZlIGJlZW4gcmVmZXJlbmNlZD8NCj4gPg0KPiA+IFtCaW5nXSBS
RkM0MDc2IGlzIGEgbW9yZSBzcGVjaWZpYyBjYXNlIG9mIHN0YXRlbGVzcy1ESENQdjYgW1JGQzM3
MzZdLA0KPiB3aGljaCBtaWdodCBub3QgYmUgY29tbW9uIHVzYWdlIGluIGVudGVycHJpc2UuIEJ1
dCBzdXJlIHdlIGNhbiBjb25zaWRlcg0KPiByZWZlcmVuY2UgaXQuDQo+IA0KPiBZZXMsIGFuZCBj
aGVjayBpZiBpdCBpZGVudGlmaWVzIGFueSBnYXBzIHRoYXQgd2Ugc2hvdWxkIG1lbnRpb24uDQo+
IA0KPiBCaW5nOiB3ZSBzaG91bGQgYWxzbyBhZGQgYSByZWZlcmVuY2UgdG8gUkZDIDQwODUgIkVt
YmVkZGluZw0KPiBHbG9iYWxseS1Sb3V0YWJsZQ0KPiBJbnRlcm5ldCBBZGRyZXNzZXMgQ29uc2lk
ZXJlZCBIYXJtZnVsIiB3aGljaCBJIG1pc3NlZCBmb3IgUkZDIDY4NjYuDQoNCltCaW5nXSBHb3Qg
aXQuIEknbGwgYWRkIGl0IGluIHRoZSBuZXh0IHZlcnNpb24uDQoNCj4gPj4gU2VjdGlvbiA1LjMg
cHVudHMgZGlzY3Vzc2lvbiBvZiBzdGF0aWMgYWRkcmVzc2VzIG9mZiB0byBSRkMgNjg2Ni4gVGhh
dA0KPiA+PiBkb2N1bWVudCB3YXMgc2NvcGVkDQo+ID4+IG9ubHkgdG8gRW50ZXJwcmlzZSBOZXR3
b3Jrcy4gVGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQgaXMgbGFyZ2VyLg0KPiANCj4gQXMgQmlu
ZyBzYWlkLCB0aGUgKmludGVuZGVkKiBzY29wZSBpcyBlbnRlcnByaXNlIG5ldHdvcmtzLiBXZSBz
aG91bGQNCj4gYWRkIHRoYXQgaW4gdGhlIEFic3RyYWN0IGFuZCBJbnRyb2R1Y3Rpb24uIEluZGVl
ZCwgbWFueSBvZiB0aGUgcG9pbnRzDQo+IGFyZSBtb3JlIGdlbmVyYWwuDQoNCltCaW5nXSBPSy4g
VGhhbmtzLg0KDQo+IFRoYW5rcyBhZ2FpbiBSb2JlcnQhDQo+IA0KPiAgICBCcmlhbg0K

From lufang@cisco.com  Tue Apr  2 05:46:17 2013
Return-Path: <lufang@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 40E8321F978D; Tue,  2 Apr 2013 05:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.846
X-Spam-Level: 
X-Spam-Status: No, score=-8.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RKDYmmUCKGOW; Tue,  2 Apr 2013 05:46:16 -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 51E4621F978C; Tue,  2 Apr 2013 05:46:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9398; q=dns/txt; s=iport; t=1364906774; x=1366116374; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=aYWAoLw7Z9Galx9QK5qGK8gyVfVKWtRUAJTH8kQGKFc=; b=bY25OYe3DIm96I7joRjmSdMKiI0qe/uELBof4IEGi9/83mkYlLyM0/AL d9IMveetJlgZVqH7px9fWKUV9lxT4kX/vEz1gWxHyIj5tSTOcBvFV3wFC JIdTFCvZdDP+YZcE3+x4WEDKgJzGeKMx8r9Rk0XhofEgq9jsewikqJShB Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAJPSWlGtJV2d/2dsb2JhbABDgzuDILwkDXcWdIIfAQEBBAEBATE6CwwGAQgRAwEBAQEEBh0FBCULFAkIAgQBDQUIiAwMk16afgaCQpAQgR2MVYEFAgYgCwcCAgKCIThhA5gKj2yDC4FqPg
X-IronPort-AV: E=Sophos;i="4.87,393,1363132800"; d="scan'208";a="194076017"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 02 Apr 2013 12:46:13 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r32CkDf6018299 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 2 Apr 2013 12:46:13 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.17]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Tue, 2 Apr 2013 07:46:13 -0500
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: "Doolan, Paul (NSN - US/Irving)" <paul.doolan@nsn.com>, Russ Housley <housley@vigilsec.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt>
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-use-cases-and-design-06.txt>
Thread-Index: AQHOLz4pe+S4mct/bEWgHAuKWl97qJjDKCGA///KQAA=
Date: Tue, 2 Apr 2013 12:46:12 +0000
Message-ID: <0DB8F45437AB844CBB5102F807A0AD93102CB82D@xmb-rcd-x03.cisco.com>
In-Reply-To: <0D9D63ECB53A1449B376D2196ADC34159B2D43@SGSIMBX001.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.21.92.107]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <C31E7A43632BB042BB2D8A589C04212B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 02 Apr 2013 08:31:16 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Apr 2013 12:46:17 -0000

V29ya3MgZm9yIG1lLiBUaGFua3MsIFBhdWwuDQpMdXl1YW4NCg0KLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCkZyb206IDxEb29sYW4+LCAiUGF1bCAgIChOU04gLSBVUy9JcnZpbmcpIiA8cGF1
bC5kb29sYW5AbnNuLmNvbT4NCkRhdGU6IFR1ZXNkYXksIEFwcmlsIDIsIDIwMTMgNzo1OCBBTQ0K
VG86IEx1eXVhbiBGYW5nIDxsdWZhbmdAY2lzY28uY29tPiwgUnVzcyBIb3VzbGV5IDxob3VzbGV5
QHZpZ2lsc2VjLmNvbT4sDQoiaWV0ZkBpZXRmLm9yZyIgPGlldGZAaWV0Zi5vcmc+DQpDYzogIm1w
bHNAaWV0Zi5vcmciIDxtcGxzQGlldGYub3JnPg0KU3ViamVjdDogUkU6IFttcGxzXSBMYXN0IENh
bGw6DQo8ZHJhZnQtaWV0Zi1tcGxzLXRwLXVzZS1jYXNlcy1hbmQtZGVzaWduLTA2LnR4dD4NCg0K
PkhpIEx1eXVhbiwNCj4NCj5Zb3Ugd3JvdGUgKGluIHBhcnQpOg0KPg0KPi4uLi4uLnNpbmNlIG11
bHRpcGxleGluZyBvZiBidXJzdHkgc291cmNlcyBpcyBmYXIgbW9yZSBlZmZpY2llbnQgb3Zlcg0K
PnRyYWRpdGlvbmFsIGNpcmN1aXQtYmFzZWQNCj5URE0gdGVjaG5vbG9naWVzLg0KPg0KPldoaWNo
IGlzIG5vdCB0cnVlIGFuZCBwcm9iYWJseSBub3Qgd2hhdCB5b3UgbWVhbnQuDQo+DQo+QSBiZXR0
ZXIgZm9ybXVsYXRpb24gbWlnaHQgYmUgInNpbmNlIHBhY2tldCBtdWx0aXBsZXhpbmcgb2YgdHJh
ZmZpYyBmcm9tDQo+YnVyc3R5IHNvdXJjZXMgcHJvdmlkZXMgbW9yZSBlZmZpY2llbnQgdXNlIG9m
IGJhbmR3aWR0aCB0aGFuIHRyYWRpdGlvbmFsDQo+Y2lyY3VpdC1iYXNlZCBURE0gdGVjaG5vbG9n
aWVzIi4NCj4NCj5UbyBiZSBob25lc3QgaG93ZXZlciwgSSdkIGN1dCB0aGUgdHJhZGl0aW9uYWwg
YW5kIHVzZSBvbmx5IFRETSAoc2luY2UNCj5zb21lICdjaXJjdWl0JyBiYXNlZCB0ZWNobm9sb2dp
ZXMgYWxzbyBvZmZlciBwYWNrZXQgbXVsdGlwbGV4aW5nKSBzbyBJJ2QNCj5yZWR1Y2UgaXQgdG86
DQo+DQo+QSBiZXR0ZXIgZm9ybXVsYXRpb24gbWlnaHQgYmUgInNpbmNlIHBhY2tldCBtdWx0aXBs
ZXhpbmcgb2YgdHJhZmZpYyBmcm9tDQo+YnVyc3R5IHNvdXJjZXMgcHJvdmlkZXMgbW9yZSBlZmZp
Y2llbnQgdXNlIG9mIGJhbmR3aWR0aCB0aGFuIFRETQ0KPnRlY2hub2xvZ2llcyIuDQo+DQo+DQo+
Y2hlZXJzLA0KPnBkDQo+DQo+DQo+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBt
cGxzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzptcGxzLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJl
aGFsZiBPZg0KPmV4dCBMdXl1YW4gRmFuZyAobHVmYW5nKQ0KPlNlbnQ6IE1vbmRheSwgQXByaWwg
MDEsIDIwMTMgOTowNSBQTQ0KPlRvOiBSdXNzIEhvdXNsZXk7IGlldGZAaWV0Zi5vcmcNCj5DYzog
bXBsc0BpZXRmLm9yZw0KPlN1YmplY3Q6IFJlOiBbbXBsc10gTGFzdCBDYWxsOg0KPjxkcmFmdC1p
ZXRmLW1wbHMtdHAtdXNlLWNhc2VzLWFuZC1kZXNpZ24tMDYudHh0Pg0KPg0KPkhpIFJ1c3MsDQo+
DQo+VGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzLCB2ZXJ5IGdvb2QgcG9pbnRzLg0KPlNvcnJ5IGZv
ciB0aGUgZGVsYXkgaW4gcmVwbHlpbmcsIEkgd2FzIG91dCBvZiBvZmZpY2UuDQo+DQo+IA0KPlRo
ZSBmb2xsb3dpbmcgaXMgbXkgcHJvcG9zZWQgdGV4dCBmb3IgcmVwbGFjaW5nIHRoZSBjdXJyZW50
IGZpcnN0DQo+cGFyYWdyYXBoIG9mIHNlY3Rpb24gMS4yLg0KPg0KPiANCj5UcmFkaXRpb25hbCB0
cmFuc3BvcnQgdGVjaG5vbG9naWVzIGluY2x1ZGUgU09ORVQvU0RILCBURE0sIGFuZCBBVE0uIFRo
ZXJlDQo+aXMgYSB0cmFuc2l0aW9uIGF3YXkgZnJvbSB0aGVzZSB0cmFuc3BvcnQgdGVjaG5vbG9n
aWVzIHRvIG5ldyBwYWNrZXQNCj50ZWNobm9sb2dpZXMuDQo+SW4gYWRkaXRpb24gdG8gdGhlIGV2
ZXIgaW5jcmVhc2luZyBkZW1hbmQgZm9yIGJhbmR3aWR0aCwgdGhlIHBhY2tldA0KPnRlY2hub2xv
Z2llcyBvZmZlciB0aGVzZSBrZXkgYWR2YW50YWdlczoNCj4NCj4gDQo+QmFuZHdpZHRoIGVmZmlj
aWVuY3k6IFRyYW5zcG9ydCB0ZWNobm9sb2dpZXMgc3VwcG9ydHMgZml4ZWQgQmFuZHdpZHRoDQo+
b25seSwgbm8gcGFja2V0IHN0YXRpc3RpY2FsIG11bHRpcGxleGluZywgYmFuZHdpZHRoIGlzIHJl
c2VydmVkIGluDQo+dHJhbnNwb3J0DQo+d2hldGhlciB1c2VkIG9yIG5vdCBieSBjbGllbnRzLiBQ
YWNrZXQgdGVjaG5vbG9naWVzIHN1cHBvcnQgc3RhdGlzdGljYWwNCj5tdWx0aXBsZXhpbmcsDQo+
dGhpcyBpcyB0aGUgbW9zdCBpbXBvcnRhbnQgbW90aXZhdGlvbiBmb3IgdGhlIHRyYW5zaXRpb24g
ZnJvbSB0cmFkaXRpb25hbA0KPnRyYW5zcG9ydCB0ZWNobm9sb2dpZXMgdG8gcGFja2V0IHRlY2hu
b2xvZ2llcy4gVGhlIHByb2xpZmVyYXRpb24gb2YgbmV3DQo+ZGlzdHJpYnV0ZWQgYXBwbGljYXRp
b25zIHdoaWNoIGNvbW11bmljYXRlIHdpdGggc2VydmVycyBvdmVyIHRoZSBuZXR3b3JrDQo+aW4g
YQ0KPmJ1cnN0eSBmYXNoaW9uIGhhcyBiZWVuIGRyaXZpbmcgdGhlIGFkb3B0aW9uIG9mIHBhY2tl
dCB0cmFuc3BvcnQNCj50ZWNobmlxdWVzLCBzaW5jZQ0KPm11bHRpcGxleGluZyBvZiBidXJzdHkg
c291cmNlcyBpcyBmYXIgbW9yZSBlZmZpY2llbnQgb3ZlciB0cmFkaXRpb25hbA0KPmNpcmN1aXQt
YmFzZWQNCj5URE0gdGVjaG5vbG9naWVzLg0KPg0KPiANCj5GbGV4aWJsZSBkYXRhIHJhdGUgY29u
bmVjdGlvbnM6IFRyYWRpdGlvbmFsIHRyYW5zcG9ydCBjb25uZWN0aW9uDQo+Z3JhbnVsYXJpdHkN
Cj5pcyBsaW1pdGVkIHRvIHRoZSByaWdpZCBQREggb3IgU09ORVQgaGllcmFyY2h5IChlLmcuLCBE
UzEsIERTMywgT0MzLCBPQzEyLA0KPmV0Yy4pLg0KPlBhY2tldCB0ZWNobm9sb2dpZXMgc3VwcG9y
dCBmbGV4aWJsZSBkYXRhIHJhdGUgY29ubmVjdGlvbnMuIFRoZSBzdXBwb3J0IG9mDQo+ZmluZXIg
ZGF0YSByYXRlIGdyYW51bGFyaXR5IGlzIGltcG9ydGFudCBmb3IgdG9kYXmp9nMgd2lyZWxpbmUg
YW5kIHdpcmVsZXNzDQo+c2VydmljZXMgYW5kIGFwcGxpY2F0aW9ucy4NCj4NCj4gDQo+UW9TIHN1
cHBvcnQ6IFdoaWxlIHRyYWRpdGlvbmFsIHRyYW5zcG9ydCwgc3VjaCBhcyBURE0gdHJhbnNwb3J0
IGhhcw0KPnZlcnkgbGltaXRlZCBRb1Mgc3VwcG9ydCwgcGFja2V0IHRyYW5zcG9ydCBjYW4gcHJv
dmlkZSBuZWVkZWQgUW9TDQo+dHJlYXRtZW50IGZvcg0KPklQVFYsIFZvaWNlIGFuZCBWaWRlbyBv
dmVyIElQIGFwcGxpY2F0aW9ucy4NCj4NCj4gDQo+VGhlIHJvb3QgY2F1c2UgZm9yIHRyYW5zcG9y
dCBtb3ZpbmcgdG8gcGFja2V0IHRyYW5zcG9ydCBpcyB0aGUgc2hpZnQNCj5vZiBhcHBsaWNhdGlv
biBmcm9tIFRETSB0byBwYWNrZXQuIEZvciBleGFtcGxlLCBWb2ljZSBURE0gdG8gVm9JUDsgVmlk
ZW8NCj50bw0KPlZpZGVvIG92ZXIgSVA7IFRETSBhY2Nlc3MgbGluZXMgdG8gRXRoZXJuZXQ7IFRE
TSBWUE5zIHRvIElQIFZQTnMgYW5kDQo+RXRoZXJuZXQNCj5WUE5zLiBJbiBhZGRpdGlvbiwgbmV0
d29yayBjb252ZXJnZW5jZSBhbmQgdGVjaG5vbG9neSByZWZyZXNoZXMgZGVtYW5kIGZvcg0KPmNv
bW1vbiBhbmQgZmxleGlibGUgaW5mcmFzdHJ1Y3R1cmUgdGhhdCBwcm92aWRlcyBtdWx0aXBsZSBz
ZXJ2aWNlcy4NCj4NCj4gDQo+VGhhbmtzLA0KPkx1eXVhbg0KPg0KPg0KPg0KPi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogUnVzcyBIb3VzbGV5IDxob3VzbGV5QHZpZ2lsc2VjLmNv
bT4NCj5EYXRlOiBTYXR1cmRheSwgTWFyY2ggMjMsIDIwMTMgMzoxNiBQTQ0KPlRvOiAiaWV0ZkBp
ZXRmLm9yZyIgPGlldGZAaWV0Zi5vcmc+DQo+Q2M6ICJtcGxzQGlldGYub3JnIiA8bXBsc0BpZXRm
Lm9yZz4NCj5TdWJqZWN0OiBSZTogW21wbHNdIExhc3QNCj5DYWxsOgk8ZHJhZnQtaWV0Zi1tcGxz
LXRwLXVzZS1jYXNlcy1hbmQtZGVzaWduLTA2LnR4dD4NCj4NCj4+SSB3b25kZXIgaWYgdGhlIGRp
cmVjdGlvbiBvZiBTZWN0aW9uIDEuMiBjYW4gYmUgcmV2aXNlZCB0byBtYWtlIGl0IG1vcmUNCj4+
b2YgYW4gZW5naW5lZXJpbmcgZG9jdW1lbnQuDQo+Pg0KPj5JdCBjdXJyZW50bHkgc2F5czoNCj4+
DQo+PiAgIEluIHJlY2VudCB5ZWFycywgdGhlIHVyZ2VuY3kgZm9yIG1vdmluZyBmcm9tIHRyYWRp
dGlvbmFsIHRyYW5zcG9ydA0KPj4gICB0ZWNobm9sb2dpZXMsIHN1Y2ggYXMgU09ORVQvU0RILCBU
RE0sIGFuZCBBVE0sIHRvIG5ldyBwYWNrZXQNCj4+ICAgdGVjaG5vbG9naWVzIGhhcyBiZWVuIHJp
c2luZy4gVGhpcyBpcyBsYXJnZWx5IGR1ZSB0byB0aGUgZmFzdCBncm93aW5nDQo+PiAgIGRlbWFu
ZCBmb3IgYmFuZHdpZHRoLCB3aGljaCBoYXMgYmVlbiBmdWVsZWQgYnkgdGhlIGZvbGxvd2luZyBm
YWN0b3JzOg0KPj4gICAuLi4NCj4+DQo+PlBsZWFzZSBjb25zaWRlciBhbiBhcHByb2FjaCB0aGF0
IGRlc2NyaWJlcyB0aGUgdGhlIHJlYXNvbnMgYmVoaW5kIHRoZQ0KPj50cmFuc2l0aW9uIGZyb20g
dGhlIG5ldHdvcmsgb3BlcmF0b3IgYW5kIG5ldHdvcmsgdXNlciBwZXJzcGVjdGl2ZXM6DQo+Pg0K
Pj4gICBUcmFkaXRpb25hbCB0cmFuc3BvcnQgdGVjaG5vbG9naWVzIGluY2x1ZGUgU09ORVQvU0RI
LCBURE0sIGFuZCBBVE0uDQo+PiAgIFRoZXJlIGlzIGEgdHJhbnNpdGlvbiBhd2F5IGZyb20gdGhl
c2UgdHJhbnNwb3J0IHRlY2hub2xvZ2llcyB0byBuZXcNCj4+ICAgcGFja2V0IHRlY2hub2xvZ2ll
cy4gSW4gYWRkaXRpb24gdG8gdGhlIGV2ZXIgaW5jcmVhc2luZyBkZW1hbmQgZm9yDQo+PiAgIGJh
bmR3aWR0aCwgdGhlIHBhY2tldCB0ZWNobm9sb2dpZXMgb2ZmZXIgdGhlc2UgYWR2YW50YWdlczoN
Cj4+ICAgLi4uDQo+Pg0KPj5UaGUgZmFjdCB0aGF0IElQIG5ldHdvcmtzIGFyZSBiZWluZyB1c2Vk
IGZvciBuZXcgYXBwbGljYXRpb25zIGFuZCB0aGF0DQo+PnRoZSBsZWdhY3kgZGV2aWNlcyBhcmUg
Z2V0dGluZyBvbGQgZG9lcyBub3QgbW90aXZhdGUgdGhlIHRyYW5zaXRpb24gdG8NCj4+cGFja2V0
IHRlY2hub2xvZ2llcy4gIFRoZSBhZHZhbnRhZ2VzIHRoYXQgcGFja2V0IHRlY2hub2xvZ2llcyBv
ZmZlciBmb3INCj4+dGhlc2UgbmV3IGFwcGxpY2F0aW9ucyBpcyB0aGUgdGhpbmcgdGhhdCBuZWVk
cyB0byBiZSBoaWdobGlnaHRlZCBoZXJlLA0KPj5ldmVuIGlmIGl0IGlzIGp1c3QgYSBsaXN0IG9m
IGJ1bGxldHMuDQo+Pg0KPj5JdCBzZWVtcyBsaWtlIHRoZSBvbmx5IHNlbnRlbmNlIHRoYXQgYWRk
cmVzc2VzIHRoaXMgcG9pbnQgaW4gU2VjdGlvbiAxLjINCj4+aXM6ICJJdCBzdHJlYW1saW5lcyB0
aGUgb3BlcmF0aW9uLCByZWR1Y2VzIHRoZSBvdmVyYWxsIGNvbXBsZXhpdHksIGFuZA0KPj5pbXBy
b3ZlcyBlbmQtdG8tZW5kIGNvbnZlcmdlbmNlLiINCj4+DQo+PlRoYW5rcywNCj4+ICBSdXNzDQo+
Pg0KPj5PbiBKYW4gMjgsIDIwMTMsIGF0IDM6MDEgUE0sIFRoZSBJRVNHIHdyb3RlOg0KPj4NCj4+
PiBUaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20gdGhlIE11bHRpcHJvdG9jb2wg
TGFiZWwgU3dpdGNoaW5nDQo+Pj5XRw0KPj4+IChtcGxzKSB0byBjb25zaWRlciB0aGUgZm9sbG93
aW5nIGRvY3VtZW50Og0KPj4+IC0gJ01QTFMtVFAgQXBwbGljYWJpbGl0eTsgVXNlIENhc2VzIGFu
ZCBEZXNpZ24nDQo+Pj4gIDxkcmFmdC1pZXRmLW1wbHMtdHAtdXNlLWNhc2VzLWFuZC1kZXNpZ24t
MDYudHh0PiBhcyBJbmZvcm1hdGlvbmFsIFJGQw0KPj4+IA0KPj4+IFRoZSBJRVNHIHBsYW5zIHRv
IG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4dCBmZXcgd2Vla3MsIGFuZCBzb2xpY2l0cw0KPj4+
IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVhc2Ugc2VuZCBzdWJzdGFudGl2ZSBj
b21tZW50cyB0byB0aGUNCj4+PiBpZXRmQGlldGYub3JnIG1haWxpbmcgbGlzdHMgYnkgMjAxMy0w
Mi0xMS4gRXhjZXB0aW9uYWxseSwgY29tbWVudHMgbWF5DQo+Pj5iZQ0KPj4+IHNlbnQgdG8gaWVz
Z0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNlIHJldGFpbiB0aGUNCj4+
PiBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGlu
Zy4NCj4+PiANCj4+PiBBYnN0cmFjdA0KPj4+IA0KPj4+ICAgVGhpcyBkb2N1bWVudCBwcm92aWRl
cyBhcHBsaWNhYmlsaXR5LCB1c2UgY2FzZSBzdHVkaWVzIGFuZCBuZXR3b3JrDQo+Pj4gICBkZXNp
Z24gY29uc2lkZXJhdGlvbnMgZm9yIHRoZSBNdWx0aXByb3RvY29sIExhYmVsIFN3aXRjaGluZyBU
cmFuc3BvcnQNCj4+PiAgIFByb2ZpbGUgKE1QTFMtVFApLiBUaGUgdXNlIGNhc2VzIGluY2x1ZGUg
TWV0cm8gRXRoZXJuZXQgYWNjZXNzIGFuZA0KPj4+ICAgYWdncmVnYXRpb24gdHJhbnNwb3J0LCBN
b2JpbGUgYmFja2hhdWwsIGFuZCBwYWNrZXQgb3B0aWNhbCB0cmFuc3BvcnQuDQo+Pj4gDQo+Pj4g
VGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYQ0KPj4+IA0KPj4+aHR0cDovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW1wbHMtdHAtdXNlLWNhc2VzLWFuZC1kZXNpZ24vDQo+
Pj4gDQo+Pj4gSUVTRyBkaXNjdXNzaW9uIGNhbiBiZSB0cmFja2VkIHZpYQ0KPj4+IA0KPj4+aHR0
cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW1wbHMtdHAtdXNlLWNhc2Vz
LWFuZC1kZXNpZ24vDQo+Pj5iDQo+Pj5hbGxvdC8NCj4+PiANCj4+PiANCj4+PiBObyBJUFIgZGVj
bGFyYXRpb25zIGhhdmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+Pg0K
Pj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj5tcGxz
IG1haWxpbmcgbGlzdA0KPj5tcGxzQGlldGYub3JnDQo+Pmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vbXBscw0KPg0KDQo=

From bob.hinden@gmail.com  Tue Apr  2 09:20:05 2013
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 5413F21F8D03 for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 09:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.952
X-Spam-Level: 
X-Spam-Status: No, score=-99.952 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F9EngHYUtl2w for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 09:20:03 -0700 (PDT)
Received: from mail-bk0-x22c.google.com (mail-bk0-x22c.google.com [IPv6:2a00:1450:4008:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 5D55F21F8CF7 for <ietf@ietf.org>; Tue,  2 Apr 2013 09:20:01 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jk13so313543bkc.31 for <ietf@ietf.org>; Tue, 02 Apr 2013 09:20:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=uSlu50KzaST5xySVFtMfY1LuO02jhOGfDrjQLk37o7A=; b=LX8awiikKo2aOf8TkxQPVtssuhk8xD5NK/PrVvQPUvaA4WzHlxonOXRUpuFyqItZNF ADHJ3w/DPd09uhntdZEg72saAZc/Nu0vQPYHRyXZjahdkZQnEWsNuMT8fAaF1Ely9Hmj 0vM0GHIfob8tke5rAiZQYst5Dc2KfRk2h1NVCjjXv9/c7b1SUzCCILWj3Mju0L3EFjME ETTtkrzkyU+Ee489+1lNoEJpmW0pLcdTzxtEwF+04iPG4yIeDrnYeSV/StqFKnS8g6ZX Em98dQPMUiBamCrznhQakz6I0IKaHuZ7uw0v27pPQSBOPN4/Wikpg7wZLDxaL0Q7pE71 Ynfw==
X-Received: by 10.205.108.72 with SMTP id eb8mr7153520bkc.111.1364919600446; Tue, 02 Apr 2013 09:20:00 -0700 (PDT)
Received: from [10.0.0.35] (c-24-130-151-138.hsd1.ca.comcast.net. [24.130.151.138]) by mx.google.com with ESMTPS id n1sm895637bkv.14.2013.04.02.09.19.56 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 09:19:59 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>
Date: Tue, 2 Apr 2013 09:19:52 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com>
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: Bob Hinden <bob.hinden@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: Tue, 02 Apr 2013 16:20:05 -0000

AB,

On Apr 1, 2013, at 5:45 PM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> RFC6921>It is well known that as we approach the speed of light, time
> slows down.
> AB> I know that time slows for something when it is in speed of light,
> but communication is not something moving. If the packet is in speed
> of light we may reduce the comm-delay but never less than zero. The
> communication times don't change if at least one communicator is not
> moving in light speed.
>=20
> My comment is that I think this RFC is not logical, and I don't
> understand its recommendations. There is no way that a packet can be
> received before send, packet-time never changes communicators-time
> while the positions of both Tx and Rx are semi-fixed (change is
> relative to communicators' times not their signal). I think the
> communication-times may change when the communicators are at/above
> speed of light not the signal/packet. Is my physics correct?

Only time will tell.

Bob




From stig@venaas.com  Tue Apr  2 10:24:58 2013
Return-Path: <stig@venaas.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69CC021F8A0C; Tue,  2 Apr 2013 10:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dh7uvGymbpT4; Tue,  2 Apr 2013 10:24:58 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id C5EED21F89E2; Tue,  2 Apr 2013 10:24:57 -0700 (PDT)
Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 61D568012; Tue,  2 Apr 2013 19:24:55 +0200 (CEST)
Message-ID: <515B140C.3060707@venaas.com>
Date: Tue, 02 Apr 2013 10:23:24 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
References: <5159F239.1060001@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com> <515AABB5.5050202@gmail.com>
In-Reply-To: <515AABB5.5050202@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "Liubing \(Leo\)" <leo.liubing@huawei.com>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Apr 2013 17:24:58 -0000

On 4/2/2013 2:58 AM, Brian E Carpenter wrote:
> Just picking a couple of points for further comment:
>
> On 02/04/2013 08:46, Liubing (Leo) wrote:
>> Hi, Robert
> ...
>
>>> -----Original Message-----
>>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>
> ...
>>> The document currently references
>>> draft-chown-v6ops-renumber-thinkabout
>>> several times.
>>> That document is long expired (2006). It would be better to simply
>>> restate what is
>>> important from that document here and reference it only once in the
>>> acknowlegements
>>> rather than send the reader off to read it.
>>
>> [Bing] draft-chown-v6ops-renumber-thinkabout is an important input for the gap analysis. Although the draft is expired, most of the content are still valid.
>> draft-chown is a more comprehensive analysis, while the gap draft is focusing on gaps in enterprise renumbering. So it might not easy to abstract several points as important from draft-chown to this draft. We actually encourage people to read it.
>
> Robert is right, though, sending people to a long-expired draft is a bad idea.
> Of course we have to acknowledge it, but maybe we should pull some of its text
> into an Appendix.
>
> Tim Chown, any opinion?

I still think that old draft is fairly good, and a shame to let it all
just die. But there is no chance of getting that out as an RFC I guess?

Stig

>
>>> RFC4076 seems to say very similar things to this document. Should it
>>> have been referenced?
>>
>> [Bing] RFC4076 is a more specific case of stateless-DHCPv6 [RFC3736], which might not be common usage in enterprise. But sure we can consider reference it.
>
> Yes, and check if it identifies any gaps that we should mention.
>
> Bing: we should also add a reference to RFC 4085 "Embedding Globally-Routable
> Internet Addresses Considered Harmful" which I missed for RFC 6866.
>
>>> Section 5.3 punts discussion of static addresses off to RFC 6866. That
>>> document was scoped
>>> only to Enterprise Networks. The scope of this document is larger.
>
> As Bing said, the *intended* scope is enterprise networks. We should
> add that in the Abstract and Introduction. Indeed, many of the points
> are more general.
>
> Thanks again Robert!
>
>     Brian
>


From fgont@si6networks.com  Tue Apr  2 18:17:41 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 909CA21F87C5 for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 18:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.153
X-Spam-Level: 
X-Spam-Status: No, score=-2.153 tagged_above=-999 required=5 tests=[AWL=0.446,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6PGmw3ewA+D7 for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 18:17:41 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0E0DF21E803A for <ietf@ietf.org>; Tue,  2 Apr 2013 18:17:32 -0700 (PDT)
Received: from [186.134.38.231] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UNCKK-0000UT-MO; Wed, 03 Apr 2013 03:17:25 +0200
Message-ID: <515B6A04.9080400@si6networks.com>
Date: Tue, 02 Apr 2013 20:30:12 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923042CFA4019@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20130401134936.0a5a1420@resistor.net>
In-Reply-To: <6.2.5.6.2.20130401134936.0a5a1420@resistor.net>
X-Enigmail-Version: 1.4.6
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, 03 Apr 2013 01:17:41 -0000

On 04/01/2013 06:14 PM, SM wrote:
>> with IPv6 connectivity. However, it's inappropriate to rely on
>> pervasive implementation of Happy Eyeballs as the sole solution to
>> prevent end host impacts, since the end user may not know that IPv6 is
>> actively being disabled on this network, or that their IPv6
>> implementation is otherwise broken. This is a problem that continues
>> to get worse the more dual-stack content becomes available.
> 
> I agree with the last sentence.  Happy Eyeballs is about the HTTP. 
> There are other applications protocols too. :-) 

Happy eyeballs is about HTTP. But part of the approach predates "Happy
Eyeballs" -- please see RFC5461.

Signaling hosts when packets are being dropped allows for a more
informed decision/reaction on the host-side.

Removing the AAAA records when you're not going to allow such
connectivity reduces the potential problem (at the end of the day, this
is kind of the whitelisting approach that has been applied to the
general case by content providers -- with the caveat that in this case
you positively know that such connectivity is not present).

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From Ted.Lemon@nominum.com  Tue Apr  2 18:25:11 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1539721F86C5 for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 18:25:11 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hOlj6Htru9iR for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 18:25:10 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id 8126821F86B7 for <ietf@ietf.org>; Tue,  2 Apr 2013 18:25:10 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUVuE9uJOz55KkzUWrPlIUcPaccCnPTm5@postini.com; Tue, 02 Apr 2013 18:25:10 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BF8051B8707 for <ietf@ietf.org>; Tue,  2 Apr 2013 18:25:09 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B6FA719005C; Tue,  2 Apr 2013 18:25:09 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 2 Apr 2013 18:25:09 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt>	(Security Implications of IPv6 on IPv4 Networks) to Informational RFC
Thread-Topic: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt>	(Security Implications of IPv6 on IPv4 Networks) to Informational RFC
Thread-Index: AQHOMAkP2n4gvj4/EE+x1APPHRWvsJjEKW+A
Date: Wed, 3 Apr 2013 01:25:09 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077512E746@mbx-01.win.nominum.com>
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923042CFA4019@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20130401134936.0a5a1420@resistor.net> <515B6A04.9080400@si6networks.com>
In-Reply-To: <515B6A04.9080400@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <4ADE700A4B16D34AB9DE2F0D0632BB6A@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SM <sm@resistor.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: Wed, 03 Apr 2013 01:25:11 -0000

On Apr 2, 2013, at 7:30 PM, Fernando Gont <fgont@si6networks.com> wrote:
>> I agree with the last sentence.  Happy Eyeballs is about the HTTP.=20
>> There are other applications protocols too. :-)=20
>=20
> Happy eyeballs is about HTTP. But part of the approach predates "Happy
> Eyeballs" -- please see RFC5461.

It's certainly true that we usually talk about Happy Eyeballs in the contex=
t of HTTP, but I use it for ssh as well, and I think it's applicable across=
 a broad range of application protocols.   It is not applicable to _every_ =
protocol, but that's as strong a qualification as I'd put on it=97saying it=
's only applicable to HTTP is not correct.


From sm@resistor.net  Tue Apr  2 21:28:55 2013
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 658FA21F8651 for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 21:28:55 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDVlLDzE1061 for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 21:28:54 -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 AFA9721F8633 for <ietf@ietf.org>; Tue,  2 Apr 2013 21:28:54 -0700 (PDT)
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 r334Sl71009013; Tue, 2 Apr 2013 21:28:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1364963333; bh=K+LPKbW1oDjOqiHkwO+/h9JjL1PvzKvGFXIZPSwIYn0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=L9Rqg1DEIJgPAFfbCP+TTuCvd89jd36uyXkXWVaq9qrtwSjxDl4FYn//74zLXWW6u j262R6DfjI55TM1PQJp71gRfxK2c9XSSsCOBwQyvRpSNaQczLv1GsoUN3BlIOqJ2VX JdUK181TjlD97u6oFnpNEZ6ek1SUKXTT1ibBlxvY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1364963333; i=@resistor.net; bh=K+LPKbW1oDjOqiHkwO+/h9JjL1PvzKvGFXIZPSwIYn0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dh/HamC9RhVrQiaPzH3IBLKGC3txp97qGk7vC0zhlDqOO+XHzXYmXgucHNRuyiKI4 NI97t+0w01mh87xejdwe4GqVvHBl3t9fo1TlDwtx6MvoAh7JKwGHVY3Bq/ViBPKUOI BzscnPrEEIz6qTQksydTPug4AMSpJAKdKE6WTCCM=
Message-Id: <6.2.5.6.2.20130402203714.0cd15e78@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 02 Apr 2013 21:08:33 -0700
To: Fernando Gont <fgont@si6networks.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
In-Reply-To: <515B6A04.9080400@si6networks.com>
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923042CFA4019@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20130401134936.0a5a1420@resistor.net> <515B6A04.9080400@si6networks.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: Wed, 03 Apr 2013 04:28:55 -0000

Hi Fernando,
At 16:30 02-04-2013, Fernando Gont wrote:
>Happy eyeballs is about HTTP. But part of the approach predates "Happy
>Eyeballs" -- please see RFC5461.

Ok.

>Removing the AAAA records when you're not going to allow such
>connectivity reduces the potential problem (at the end of the day, this
>is kind of the whitelisting approach that has been applied to the
>general case by content providers -- with the caveat that in this case
>you positively know that such connectivity is not present).

Here's an extract from RFC 4924:

   'In particular, the DNSSEC protocol described in "Protocol
    Modifications for the DNS Security Extensions" [RFC4035] has been
    designed to verify that DNS information has not been modified between
    the moment they have been published on an authoritative server and
    the moment the validation takes place.  Since that verification can
    take place at the application level, any modification by a recursive
    forwarder or other intermediary will cause validation failures,
    disabling the improved security that DNSSEC is intended to provide.'

I am ok with resolving the problem of the day.  If I am of the 
opinion that it may cause problems in the long run I'll mention 
it.  I am not inclined to do anything more than that.

Regards,
-sm 


From doug.mtview@gmail.com  Tue Apr  2 21:29:25 2013
Return-Path: <doug.mtview@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 BAFAD21E805D for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 21:29:25 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TsmlvAGufYfc for <ietf@ietfa.amsl.com>; Tue,  2 Apr 2013 21:29:24 -0700 (PDT)
Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7A521E804E for <ietf@ietf.org>; Tue,  2 Apr 2013 21:29:24 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rp8so626358pbb.19 for <ietf@ietf.org>; Tue, 02 Apr 2013 21:29:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:message-id:references:to:x-mailer; bh=2+mcOT+NFYjwrn+lAjMrNR7w60cIqpEDPx8h5LXq4x0=; b=mocSXCqhdL0JnU7i2InNegDwq1X9yCvUhz1I2cL5yfnUfHwdQ7s8LRlWyB9SQ3I386 Mw/r6cNon/FLAs28lwxco4SXGaXz/iyh2fRnVEIOatMplinEG0OGn6VdiO5YJqAbjVQc EgRQEWnv05nfhFllUGnPCLcHCngdNQwfY25XLBGA1m195WQoau/3rzLlZxrCgrqiL5IZ /sm0Ihayq2osmbDxQHciHiON7mD98t1qN0pbDUvRjcJ7uSnuPI/lhW88s1ZvO2zDAY41 3Cwmk1RTVrT7UP1bWIg979z/iW1V+6eqfVR8aOCq/AiIWbPz6IW1Vs/zfPDlYmfJTfEq DQWw==
X-Received: by 10.68.134.5 with SMTP id pg5mr143610pbb.161.1364963363443; Tue, 02 Apr 2013 21:29:23 -0700 (PDT)
Received: from [192.168.1.186] (c-24-4-157-244.hsd1.ca.comcast.net. [24.4.157.244]) by mx.google.com with ESMTPS id ky10sm5087502pab.23.2013.04.02.21.29.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 02 Apr 2013 21:29:22 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_FC795D4F-8CD2-4B2D-B8D3-075338B46145"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Sufficient email authentication requirements for IPv6
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0BFF8A84@tk5ex14mbxc272.redmond.corp.microsoft.com>
Date: Tue, 2 Apr 2013 21:29:17 -0700
Message-Id: <0426C738-B041-4075-AF9D-6EEAC31F37CD@gmail.com>
References: <CANB+R+WfeBu49YdsENwkJMZnu7zAHaNGSqOfkcmJOW7X5TOg9A@mail.gmail.com> <5154C9E0.7060408@isdg.net> <357617C8-766E-4CCF-A733-E032103211E1@gmail.com> <C91E67751B1EFF41B857DE2FE1F68ABA0BFF8A84@tk5ex14mbxc272.redmond.corp.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1503)
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: Wed, 03 Apr 2013 04:29:26 -0000

--Apple-Mail=_FC795D4F-8CD2-4B2D-B8D3-075338B46145
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Mar 30, 2013, at 11:26 PM, Christian Huitema <huitema@microsoft.com> =
wrote:

>> IPv6 makes publishing IP address reputations impractical.  Since IP =
address reputation has been a primary method for identifying abusive =
sources with IPv4, imposing ineffective and flaky > replacement =
strategies has an effect of deterring IPv6 use.=20
>=20
> In practice, the /64 prefix of the IPv6 address has very much the same =
"administrative" properties as the /32 value of the IPv4 address. It =
should be fairly straightforward to update a reputation system to manage =
the /64 prefixes of IPv6. This seems somewhat more practical than trying =
to change the behavior of mail agent if their connectivity happens to =
use IPv6.

Dear Christian,

The announced prefix space currently represents more than 4 million =
times the entire IPv4 address space.  This means the /64 prefix space =
can not be considered comparable to IPv4 address space.  Go to =
http://bgp.potaroo.net/v6/as2.0/ and look for Total address space =
advertised (/64 equiv).  The number of announced prefixes over /64s =
currently shows 18,206,079,529,779,202.

Much of the IPv4 has already had Reverse DNS PTR records traversed =
scanning for hints about whether any specific address appears to =
represent dynamically assigned access.  This guesswork allows about 1/3 =
of the IPv4 space to be ignored by blocking them from sending public =
(port 25) SMTP messages.

Reverse DNS PTR records offers a costly means to differentiate =
residential and non-residential access when done on a realtime basis.  A =
significant benefit of a comprehensive reputation mapping of the entire =
IPv4 address space is that any reverse naming exceptions are =
incorporated into the reputation values which also eliminates dependence =
on reverse DNS performance.

In IPv6, there can not be any pre-mapping.  This places reverse PTR =
review at the mercy of the even more broken IPv6 reverse zone =
provisioning.  Any mis-configuration of the reverse name space, which is =
common for IPv4 from residential systems, greatly increases the =
resources consumed by the growing proportion of sessions emitted by =
compromised systems.  Few expect reverse PTRs and hostnames to match, =
but to offer names not hinting at being for a dynamic assignment.  =
Greatly increased delays caused by DNS misconfiguration, along with a =
need to handle a larger number of sessions, will make testing reverse =
PTR records highly resource prohibitive and problematic for IPv6.

In the end, Reverse PTRs can be assigned any name and thus can not serve =
as a basis to assess accountability.  Once a conclusion is reached that =
only AUTHENTICATED initiating domains offer a means to fairly establish =
a basis for acceptance, use of reverse PTR records becomes far far less =
attractive.  The ability to authenticate forward domains initiating =
messages improves security and is better suited for a future of more =
mobile and dynamic infrastructure.

Many email domains will find themselves obligated to authorize IPv4 =
outbound servers using SPF.  Return-Path mail parameters locating =
authorization reduces backscatter abuse at the cost of reduced delivery =
integrity.  However this parameter's relationship over mail's entire =
path is too fragile to serve as a basis for acceptance.  Since DKIM =
allows any message to be relayed by design, it can not offer a means to =
mitigate abuse when any marginal domain must be accepted, as for domains =
considered too big to block.

In addition, problems related to DKIM header field spoofing permitted =
when signatures are still considered valid, along with a growing range =
of dangerous email content that references compromised i-frames, makes =
responding to new threats a growing problem.  IPv6 pushes this problem =
further over the edge without the introduction of the initiating domains =
having been authenticated.  IPv6 addresses can not serve this function, =
and there is progress being made in respect to use of DANE and the like.

Regards,
Douglas Otis

--Apple-Mail=_FC795D4F-8CD2-4B2D-B8D3-075338B46145
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><font face=3D"Monaco">On Mar 30, 2013, at 11:26 PM, =
Christian Huitema &lt;<a =
href=3D"mailto:huitema@microsoft.com">huitema@microsoft.com</a>&gt; =
wrote:</font></div><font face=3D"Monaco"><br =
class=3D"Apple-interchange-newline"></font><blockquote =
type=3D"cite"><blockquote type=3D"cite"><font face=3D"Monaco">IPv6 makes =
publishing IP address reputations impractical. &nbsp;Since IP address =
reputation has been a primary method for identifying abusive sources =
with IPv4, imposing ineffective and flaky &gt; replacement strategies =
has an effect of deterring IPv6 use. <br></font></blockquote><font =
face=3D"Monaco"><br>In practice, the /64 prefix of the IPv6 address has =
very much the same "administrative" properties as the /32 value of the =
IPv4 address. It should be fairly straightforward to update a reputation =
system to manage the /64 prefixes of IPv6. This seems somewhat more =
practical than trying to change the behavior of mail agent if their =
connectivity happens to use IPv6.<br></font></blockquote></div><font =
face=3D"Monaco"><br></font><div><font face=3D"Monaco">Dear =
Christian,</font></div><div><font =
face=3D"Monaco"><br></font></div><div><font face=3D"Monaco">The =
announced prefix space currently represents more than 4 million times =
the entire IPv4 address space. &nbsp;This means the /64 prefix space can =
not be considered comparable to IPv4 address space. &nbsp;Go to&nbsp;<a =
href=3D"http://bgp.potaroo.net/v6/as2.0/">http://bgp.potaroo.net/v6/as2.0/=
</a>&nbsp;and look for Total address space advertised (/64 equiv). =
&nbsp;The number of announced prefixes over /64s currently shows&nbsp;<a =
href=3D"http://bgp.potaroo.net/v6/as2.0/bgp-total-space.txt" =
target=3D"text">18,206,079,529,779,202</a>.</font></div><div><font =
face=3D"Monaco"><br></font></div><div><font face=3D"Monaco">Much of the =
IPv4 has already had Reverse DNS PTR records traversed scanning for =
hints about whether any specific address appears to represent =
dynamically assigned access. &nbsp;This guesswork allows about 1/3 of =
the IPv4 space to be ignored by blocking them from sending public (port =
25) SMTP messages.</font></div><div><font =
face=3D"Monaco"><br></font></div><div><font face=3D"Monaco">Reverse DNS =
PTR records offers a costly means to differentiate residential and =
non-residential access when done on a realtime basis. &nbsp;A =
significant benefit of a comprehensive reputation mapping of the entire =
IPv4 address space is that any reverse naming exceptions are =
incorporated into the reputation values which also eliminates dependence =
on reverse DNS performance.<br><br>In IPv6, there can not be any =
pre-mapping. &nbsp;This places reverse PTR review at the mercy of the =
even more broken IPv6 reverse zone provisioning. &nbsp;Any =
mis-configuration of the reverse name space, which is common for IPv4 =
from residential systems, greatly increases the resources consumed by =
the growing proportion of sessions emitted by compromised systems. =
&nbsp;Few expect reverse PTRs and hostnames to match, but to offer names =
not hinting at being for a dynamic assignment. &nbsp;Greatly increased =
delays caused by DNS misconfiguration, along with a need to handle a =
larger number of sessions, will make testing reverse PTR records highly =
resource prohibitive and problematic for IPv6.<br><br>In the end, =
Reverse PTRs can be assigned any name and thus can not serve as a basis =
to assess accountability. &nbsp;Once a conclusion is reached that only =
AUTHENTICATED initiating domains offer a means to fairly establish a =
basis for acceptance, use of reverse PTR records becomes far far less =
attractive. &nbsp;The ability to authenticate forward domains initiating =
messages improves security and is better suited for a future of more =
mobile and dynamic infrastructure.</font></div><div><font =
face=3D"Monaco"><br></font></div><div><font face=3D"Monaco">Many email =
domains will find themselves obligated to authorize IPv4 outbound =
servers using SPF. &nbsp;Return-Path mail parameters locating =
authorization reduces backscatter abuse at the cost of reduced delivery =
integrity. &nbsp;However this parameter's relationship over mail's =
entire path is too fragile to serve as a basis for acceptance. =
&nbsp;Since DKIM allows any message to be relayed by design, it can not =
offer a means to mitigate abuse when any marginal domain must be =
accepted, as for domains considered too big to =
block.</font></div><div><font face=3D"Monaco"><br></font></div><div><font =
face=3D"Monaco">In addition, problems related to DKIM header field =
spoofing permitted when signatures are still considered valid, along =
with a growing range of dangerous email content that references =
compromised i-frames, makes responding to new threats a growing problem. =
&nbsp;IPv6 pushes this problem further over the edge without the =
introduction of the initiating domains having been authenticated. =
&nbsp;IPv6 addresses can not serve this function, and there is progress =
being made in respect to use of DANE and the =
like.</font></div><div><font face=3D"Monaco"><br></font></div><div><font =
face=3D"Monaco">Regards,</font></div><div><font face=3D"Monaco">Douglas =
Otis<br></font></div></body></html>=

--Apple-Mail=_FC795D4F-8CD2-4B2D-B8D3-075338B46145--

From fgont@si6networks.com  Wed Apr  3 00:04:21 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68E5921F85C3 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 00:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCDZ+kKWOgIC for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 00:04:21 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id EB25C21F85D9 for <ietf@ietf.org>; Wed,  3 Apr 2013 00:04:20 -0700 (PDT)
Received: from [2001:5c0:1000:a::d6b] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UNHjr-0000xS-7C; Wed, 03 Apr 2013 09:04:08 +0200
Message-ID: <515B9CD2.1030402@si6networks.com>
Date: Wed, 03 Apr 2013 00:06:58 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130330230305.0bce91a8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923042CFA4019@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20130401134936.0a5a1420@resistor.net> <515B6A04.9080400@si6networks.com> <8D23D4052ABE7A4490E77B1A012B63077512E746@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077512E746@mbx-01.win.nominum.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: SM <sm@resistor.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: Wed, 03 Apr 2013 07:04:21 -0000

On 04/02/2013 10:25 PM, Ted Lemon wrote:
> On Apr 2, 2013, at 7:30 PM, Fernando Gont <fgont@si6networks.com> wrote:
>>> I agree with the last sentence.  Happy Eyeballs is about the HTTP. 
>>> There are other applications protocols too. :-) 
>>
>> Happy eyeballs is about HTTP. But part of the approach predates "Happy
>> Eyeballs" -- please see RFC5461.
> 
> It's certainly true that we usually talk about Happy Eyeballs in the context of HTTP, but I use it for ssh as well, and I think it's applicable across a broad range of application protocols.   It is not applicable to _every_ protocol, but that's as strong a qualification as I'd put on it—saying it's only applicable to HTTP is not correct.
> 

Exactly. For instance, I seem to recall benefiting of RFC5461 for ssh in
NetBSD long before the first version of the Happy Eyeballs I-D was
published.

As noted in RFC5461, the approach is useful for any protocol -- but for
obvious reasons the benefits become evident for interactive protocols
such as HTTP, SSH, telnet, and the like...

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From alexey.melnikov@isode.com  Wed Apr  3 06:04:03 2013
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F8E921F8B08 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 06:04:03 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y2a2PRN5SMz0 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 06:04:02 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id A334221F8B07 for <ietf@ietf.org>; Wed,  3 Apr 2013 06:04:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1364896417; d=isode.com; s=selector; i=@isode.com; bh=2vvvhqI+ZdMl7YscE2/kSHpt3ORQ7oiu6U5/GV8uk7g=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=p2oJPmyvnRPIp1KoqfcPfX1ujlP6AfmeqSOKr4JsDG99jrHg/pUrNXlX4Fq3kaP8E41qoS +l9s4dkxLYJDy3oM7gBjLEo2PXvcPpDhY6dfw++5B4MQrU8OYx5QqygAcFz4iG1FiFHOQ9 7oXHIDuUBWDUbe+H37aycHo+Pn87TX8=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <UVqqoAA4j5an@statler.isode.com>; Tue, 2 Apr 2013 10:53:37 +0100
Message-ID: <515AAACD.90003@isode.com>
Date: Tue, 02 Apr 2013 10:54:21 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: Burger Eric <eburger@cs.georgetown.edu>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch?  (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu>
In-Reply-To: <CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu>
MIME-Version: 1.0
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: Wed, 03 Apr 2013 13:04:03 -0000

Hi Eric,
I am sorry if I sound pedantic below, but I think your suggestion can be 
misinterpreted and thus needs improving:

On 28/03/2013 12:13, Burger Eric wrote:
> Rather than guessing all of the bad things that could happen, I would offer it would be better to say what we mean, like:
> 	The IMAP interface MUST NOT provide any IMAP facilities that modify the underlying message and message metadata, such as mailbox, flags, marking for deletion, etc. If the client is authenticated and authorized, the IMAP interface MUST provide per-user marking of the underlying message as read or flagged.
One way to implement this is in an IMAP server is to always fail 
commands for modifying message metadata. Another way of implementing 
this is to allow them, but ignore (don't persist) results. Both ways 
were used in the past and they have different effect on IMAP clients. I 
hope the requirement is intended to allow for either.

Another thing to consider is that for IMAP servers that implement IMAP 
ACL, the easiest way to meet the intended requirement is by not allowing 
unauthorized users to access some commands on a mailbox. Again, a 
possible reading of your suggested text is that that is not allowed.

So, my suggestion is to change "MUST NOT provide any IMAP facilities 
..." to "MUST disallow any IMAP facilities ...".


From alexey.melnikov@isode.com  Wed Apr  3 06:11:27 2013
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD9821F8A54 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 06:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SfLSsQer5tff for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 06:11:24 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 755B321F8648 for <ietf@ietf.org>; Wed,  3 Apr 2013 06:11:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1364837957; d=isode.com; s=selector; i=@isode.com; bh=kGNK14+byUTa/deW2BGy+Rp24+66hcyfTG3t74/bu8o=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=dLIf3GAW7VF/zsLYKLHcnmNzZI3gJvQFuxfN665m082IE1zPeG4DGdNXK4UBQQJ6a4HoQK a6gMs/A0hHksRrnROFDzoX135OQrAPLw2J+tLKnR3Yli3/0Xfw/uEo0hWIRa2mLlZjmp9Z M1aFmpjJfSyaHLmD1w/NYTE9BbdiBG0=;
Received: from [188.29.0.198] (188.29.0.198.threembb.co.uk [188.29.0.198])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <UVnGRAA4j5g6@statler.isode.com>; Mon, 1 Apr 2013 18:39:17 +0100
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com>
In-Reply-To: <5153571C.9070800@nostrum.com>
Message-Id: <6E194773-03C8-4A88-8002-C9E4C8657E98@isode.com>
X-Mailer: iPad Mail (9B206)
From: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch?  (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
Date: Mon, 1 Apr 2013 18:41:12 +0100
To: Robert Sparks <rjsparks@nostrum.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
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: Wed, 03 Apr 2013 13:11:27 -0000

On 27 Mar 2013, at 20:31, Robert Sparks <rjsparks@nostrum.com> wrote:

> While looking at it, I noticed we don't explicitly say that this IMAP inte=
rface MUST NOT
> allow messages in the archive to be deleted

I would actually allow administrative users to delete messages (e.g. spam), b=
ut such actions should be recorded in logs. Other users shouldn't be allowed=
 to do that.

> or moved to other mailboxes, and MUST NOT
> allow messages to be inserted. I plan to add those as requirements in the n=
ext version.

This is fine with me.


From rjsparks@nostrum.com  Wed Apr  3 07:46:33 2013
Return-Path: <rjsparks@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 E8E7621F8D85 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 07:46:33 -0700 (PDT)
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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 38EZQQwC9PQW for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 07:46:33 -0700 (PDT)
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 2606621F8BBB for <ietf@ietf.org>; Wed,  3 Apr 2013 07:46:33 -0700 (PDT)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r33EkUlO062604 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Wed, 3 Apr 2013 09:46:31 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <515C40C8.1000106@nostrum.com>
Date: Wed, 03 Apr 2013 09:46:32 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch?
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu> <6.2.5.6.2.20130328111022.0ceeb7d8@resistor.net> <5159FF0E.9080202@nostrum.com> <tsl38v9q0a6.fsf@mit.edu>
In-Reply-To: <tsl38v9q0a6.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: SM <sm@resistor.net>, Burger Eric <eburger@cs.georgetown.edu>, 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, 03 Apr 2013 14:46:34 -0000

On 4/1/13 6:49 PM, Sam Hartman wrote:
> May I suggest that the specific details of this be left to the
> implementation effort.  What is easy to implement in this area depends
> significantly on what platform (and here I mean more imap libraries and
> imap server technology than say python vs ruby vs .net vs C) A simple
> requirement like the implementation should consider how to handle abuse
> of message marking.
Sam - I agree, and was taking a very similar approach in my working copy 
already.
Let me know if you think -06 has it right.

RjS

From rjsparks@nostrum.com  Wed Apr  3 07:46:36 2013
Return-Path: <rjsparks@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 9D6AF21F8E66 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 07:46:36 -0700 (PDT)
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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oJnxRnz4r-DV for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 07:46:36 -0700 (PDT)
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 D3A8221F8E4C for <ietf@ietf.org>; Wed,  3 Apr 2013 07:46:35 -0700 (PDT)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r33EkY84062608 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Wed, 3 Apr 2013 09:46:34 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <515C40CC.6050404@nostrum.com>
Date: Wed, 03 Apr 2013 09:46:36 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch? (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu> <515AAACD.90003@isode.com>
In-Reply-To: <515AAACD.90003@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: Burger Eric <eburger@cs.georgetown.edu>, 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, 03 Apr 2013 14:46:36 -0000

On 4/2/13 4:54 AM, Alexey Melnikov wrote:
> Hi Eric,
> I am sorry if I sound pedantic below, but I think your suggestion can 
> be misinterpreted and thus needs improving:
>
> On 28/03/2013 12:13, Burger Eric wrote:
>> Rather than guessing all of the bad things that could happen, I would 
>> offer it would be better to say what we mean, like:
>>     The IMAP interface MUST NOT provide any IMAP facilities that 
>> modify the underlying message and message metadata, such as mailbox, 
>> flags, marking for deletion, etc. If the client is authenticated and 
>> authorized, the IMAP interface MUST provide per-user marking of the 
>> underlying message as read or flagged.
> One way to implement this is in an IMAP server is to always fail 
> commands for modifying message metadata. Another way of implementing 
> this is to allow them, but ignore (don't persist) results. Both ways 
> were used in the past and they have different effect on IMAP clients. 
> I hope the requirement is intended to allow for either.
>
> Another thing to consider is that for IMAP servers that implement IMAP 
> ACL, the easiest way to meet the intended requirement is by not 
> allowing unauthorized users to access some commands on a mailbox. 
> Again, a possible reading of your suggested text is that that is not 
> allowed.
>
> So, my suggestion is to change "MUST NOT provide any IMAP facilities 
> ..." to "MUST disallow any IMAP facilities ...".
I think I found a way to say this that strikes a good balance in -06. 
Let me know what you think.


From presnick@qti.qualcomm.com  Wed Apr  3 08:53:45 2013
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 65E2021F8ECC for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 08:53:45 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QU-uTWoN8jbJ for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 08:53:44 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id C376521F8EC7 for <ietf@ietf.org>; Wed,  3 Apr 2013 08:53:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1365004424; x=1396540424; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=fXn8FuVfErAjb7s67ktAyk7wU71hLhj4F+zdRhrm+jA=; b=QE3LTDgTZBdpCg6bzDUVnmc3iLoMOiRWTuWaXe/Y3XhXBmXrVQ6xlR7n Ldqk8RXJOpVRmzG49jjnbrZV60Trp/0yuXDEWWNhzWNmmNHcZxGYEXRSU flgMKcp3qps3AlFNNeC+UDM8KFz7AFkPV90gaabpj4ZOgK1k/JCscqkQ9 c=;
X-IronPort-AV: E=Sophos;i="4.87,402,1363158000"; d="scan'208";a="33523317"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth02.qualcomm.com with ESMTP; 03 Apr 2013 08:53:43 -0700
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Apr 2013 08:53:43 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 3 Apr 2013 08:53:43 -0700
Message-ID: <515C5084.8040701@qti.qualcomm.com>
Date: Wed, 3 Apr 2013 10:53:40 -0500
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: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch? (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com>	<5153571C.9070800@nostrum.com>	<CBA0E06E-C59D-43C4-BD13-6DD5AB7AF1B7@cs.georgetown.edu>	<515AAACD.90003@isode.com> <515C40CC.6050404@nostrum.com>
In-Reply-To: <515C40CC.6050404@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Burger Eric <eburger@cs.georgetown.edu>, 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, 03 Apr 2013 15:53:45 -0000

On 4/3/13 9:46 AM, Robert Sparks wrote:
> I think I found a way to say this that strikes a good balance in -06. 
> Let me know what you think.

Excellent. Ship it.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From housley@vigilsec.com  Wed Apr  3 09:10:28 2013
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 248DA21F8E67 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 09:10:28 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxRRJEiE0nEq for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 09:10:27 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 4534321F8E04 for <ietf@ietf.org>; Wed,  3 Apr 2013 09:10:27 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 34BC39A4103; Wed,  3 Apr 2013 12:10:52 -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 g4VGjaVMlMXi; Wed,  3 Apr 2013 12:09:41 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id CEB9E9A410B; Wed,  3 Apr 2013 12:10:49 -0400 (EDT)
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch? (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6E194773-03C8-4A88-8002-C9E4C8657E98@isode.com>
Date: Wed, 3 Apr 2013 12:10:24 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <692E7C28-FF9E-4F3A-8369-4CB2836BFB7E@vigilsec.com>
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <6E194773-03C8-4A88-8002-C9E4C8657E98@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.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: Wed, 03 Apr 2013 16:10:28 -0000

Alexey:

Of course we want to be able to delete spam, but this is being used to =
access an archive, so only the administrator should be able to delete =
the spam.

Russ


On Apr 1, 2013, at 1:41 PM, Alexey Melnikov wrote:

> On 27 Mar 2013, at 20:31, Robert Sparks <rjsparks@nostrum.com> wrote:
>=20
>> While looking at it, I noticed we don't explicitly say that this IMAP =
interface MUST NOT
>> allow messages in the archive to be deleted
>=20
> I would actually allow administrative users to delete messages (e.g. =
spam), but such actions should be recorded in logs. Other users =
shouldn't be allowed to do that.
>=20
>> or moved to other mailboxes, and MUST NOT
>> allow messages to be inserted. I plan to add those as requirements in =
the next version.
>=20
> This is fine with me.
>=20


From dhc@dcrocker.net  Wed Apr  3 09:22:21 2013
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 AB98121F8ED6 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 09:22:21 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bIQ6S-Knvz9t for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 09:22:21 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 153A121F8ECA for <ietf@ietf.org>; Wed,  3 Apr 2013 09:22:21 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r33GMKKW029980 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 3 Apr 2013 09:22:20 -0700
Message-ID: <515C573A.7000109@dcrocker.net>
Date: Wed, 03 Apr 2013 09:22:18 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch? (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <6E194773-03C8-4A88-8002-C9E4C8657E98@isode.com> <692E7C28-FF9E-4F3A-8369-4CB2836BFB7E@vigilsec.com>
In-Reply-To: <692E7C28-FF9E-4F3A-8369-4CB2836BFB7E@vigilsec.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, 03 Apr 2013 09:22:20 -0700 (PDT)
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, 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: Wed, 03 Apr 2013 16:22:21 -0000

On 4/3/2013 9:10 AM, Russ Housley wrote:
> Alexey:
>
> Of course we want to be able to delete spam, but this is being used
> to access an archive, so only the administrator should be able to
> delete the spam.
>
> Russ
>
>
> On Apr 1, 2013, at 1:41 PM, Alexey Melnikov wrote:
>
>> On 27 Mar 2013, at 20:31, Robert Sparks <rjsparks@nostrum.com>
>> wrote:
>>> While looking at it, I noticed we don't explicitly say that this
>>> IMAP interface MUST NOT allow messages in the archive to be
>>> deleted
>>
>> I would actually allow administrative users to delete messages
>> (e.g. spam), but such actions should be recorded in logs. Other
>> users shouldn't be allowed to do that.


I'm  confused Russ.  Isn't that exactly what Alexey recommends, here?

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From housley@vigilsec.com  Wed Apr  3 09:23:59 2013
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 066F621F8E71 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 09:23:59 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xRZHe5OymiIZ for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 09:23:58 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id BF64B21F8AC2 for <ietf@ietf.org>; Wed,  3 Apr 2013 09:23:57 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 04FE39A410B; Wed,  3 Apr 2013 12:24:03 -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 d2Mh-f43aigU; Wed,  3 Apr 2013 12:23:49 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 0B21F9A4103; Wed,  3 Apr 2013 12:24:02 -0400 (EDT)
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch? (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <515C573A.7000109@dcrocker.net>
Date: Wed, 3 Apr 2013 12:23:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CCD7F13-7972-43B2-9B7D-451CBA4E5FB3@vigilsec.com>
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <6E194773-03C8-4A88-8002-C9E4C8657E98@isode.com> <692E7C28-FF9E-4F3A-8369-4CB2836BFB7E@vigilsec.com> <515C573A.7000109@dcrocker.net>
To: Dave Crocker <dcrocker@bbiw.net>, Alexey Melnikov <alexey.melnikov@isode.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: Wed, 03 Apr 2013 16:23:59 -0000

Dave:

>> Alexey:
>>=20
>> Of course we want to be able to delete spam, but this is being used
>> to access an archive, so only the administrator should be able to
>> delete the spam.
>>=20
>> Russ
>>=20
>>=20
>> On Apr 1, 2013, at 1:41 PM, Alexey Melnikov wrote:
>>=20
>>> On 27 Mar 2013, at 20:31, Robert Sparks <rjsparks@nostrum.com>
>>> wrote:
>>>> While looking at it, I noticed we don't explicitly say that this
>>>> IMAP interface MUST NOT allow messages in the archive to be
>>>> deleted
>>>=20
>>> I would actually allow administrative users to delete messages
>>> (e.g. spam), but such actions should be recorded in logs. Other
>>> users shouldn't be allowed to do that.
>=20
>=20
> I'm  confused Russ.  Isn't that exactly what Alexey recommends, here?

The administrator does not have to use the IMAP interface.  They could =
use a different interface.

Russ


From dhc@dcrocker.net  Wed Apr  3 09:44:44 2013
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 2F57921F8F07 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 09:44:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKUJ0VB4Vcim for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 09:44:43 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD5D21F8BE8 for <ietf@ietf.org>; Wed,  3 Apr 2013 09:44:43 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r33Gig74030427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 3 Apr 2013 09:44:43 -0700
Message-ID: <515C5C79.8040606@dcrocker.net>
Date: Wed, 03 Apr 2013 09:44:41 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Missing requirement in draft-sparks-genarea-imaparch? (was Re: New Version Notification - draft-sparks-genarea-imaparch-05.txt)
References: <20130326204553.17292.36013.idtracker@ietfa.amsl.com> <5153571C.9070800@nostrum.com> <6E194773-03C8-4A88-8002-C9E4C8657E98@isode.com> <692E7C28-FF9E-4F3A-8369-4CB2836BFB7E@vigilsec.com> <515C573A.7000109@dcrocker.net> <2CCD7F13-7972-43B2-9B7D-451CBA4E5FB3@vigilsec.com>
In-Reply-To: <2CCD7F13-7972-43B2-9B7D-451CBA4E5FB3@vigilsec.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, 03 Apr 2013 09:44:43 -0700 (PDT)
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, 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: Wed, 03 Apr 2013 16:44:44 -0000

On 4/3/2013 9:23 AM, Russ Housley wrote:
>>> Of course we want to be able to delete spam, but this is being used
>>> to access an archive, so only the administrator should be able to
>>> delete the spam.
...
>>> On Apr 1, 2013, at 1:41 PM, Alexey Melnikov wrote:
>>>
>>>> On 27 Mar 2013, at 20:31, Robert Sparks <rjsparks@nostrum.com>
>>>> wrote:
>>>>> While looking at it, I noticed we don't explicitly say that this
>>>>> IMAP interface MUST NOT allow messages in the archive to be
>>>>> deleted
>>>>
>>>> I would actually allow administrative users to delete messages
>>>> (e.g. spam), but such actions should be recorded in logs. Other
>>>> users shouldn't be allowed to do that.
>>
>> I'm  confused Russ.  Isn't that exactly what Alexey recommends, here?
>
> The administrator does not have to use the IMAP interface.  They could use a different interface.


Your previous note specified /who/ should have the capability; this 
matches what Alexey said.

Your note now refers to /how/ and appears to mean that you believe they 
should not be allowed to exercise that capability via IMAP.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dean.willis@softarmor.com  Wed Apr  3 15:16:29 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4BC921F8FDB for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 15:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.973
X-Spam-Level: 
X-Spam-Status: No, score=-98.973 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_CPE=0.979, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6tb6wSfPotwx for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 15:16:29 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3C88C21F8FAB for <ietf@ietf.org>; Wed,  3 Apr 2013 15:16:29 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id bn7so2301675ieb.37 for <ietf@ietf.org>; Wed, 03 Apr 2013 15:16:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=HfPsqVkVvlSMZ6qGPI+tboZagC9tf6UsmCjXDHHuPUQ=; b=XcH0MQYebl8ZtlQRZI4U7QWllzKj6/fQZ4HYRIvUSvN9xvWBxJOmIgzkmoVAauQsCZ qbGSr9/5lC4tRhW48nGH7nlufC3XddeLLkdYHe8Zx6sxN+YemGOXS0YTZcQyEoTJaz1G JQrop4vSE950N+9d152QEXA0vOqA4dX5aF2tQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received: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=HfPsqVkVvlSMZ6qGPI+tboZagC9tf6UsmCjXDHHuPUQ=; b=CcPxKnBowwn6rBZ49w0GkExIpZE1LbLSim0NMszYr1dJoARsiuxPHmplr7N+peU3Fz oxzj1YLnLoxlvCYiF77JeGEJqwzpiImdqbYmEWPg4xxGmkoHLho+h93tik7moR5rxaAg y/P9Lzbk5L/srn9fg6wAiGH146M/9iC1bqH16qMnoV7R5tXwrO9WLGxEGspNlIdIxBV3 d+wUQvSgfviS3Qq4Olc0sDhrIgzOs2e6qAqtWypv1SDpA4xzIrLj+qnXMOm+PIFtpw0s atiSsTutjI8xPa+JXWtxKfbx281Xs9bUBfKEe90RDpGw/z0tN3meAcoLxLekCJhbv+Uo IRWg==
X-Received: by 10.50.178.212 with SMTP id da20mr2295591igc.13.1365027388784; Wed, 03 Apr 2013 15:16:28 -0700 (PDT)
Received: from [192.168.2.104] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPS id wn10sm10607872igb.2.2013.04.03.15.16.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Apr 2013 15:16:27 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Sufficient email authentication requirements for IPv6
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <7EC291A080112791E237A211@JcK-HP8200.jck.com>
Date: Wed, 3 Apr 2013 17:16:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF4F3AFB-1299-4FEE-82F3-CABECA73A20F@softarmor.com>
References: <10229F86C86EB444898E629583FD417172798E19@PACDCEXMB06.cable.comcast.com> <7EC291A080112791E237A211@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQk1C56fFzwVyb3qzwm4YuZCZ+fLdtRj7pk3Nvcidh34t/75n4ph7tVtIF+7OfneSD7Z2oNF
Cc: ietf@ietf.org, John Levine <johnl@taugh.com>, "Walker, Severin" <Severin_Walker@Cable.Comcast.com>, "O'Reirdan, Michael" <Michael_OReirdan@Cable.Comcast.com>, "Rosenwald, Jordan" <Jordan_Rosenwald@cable.comcast.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: Wed, 03 Apr 2013 22:16:29 -0000

On Mar 30, 2013, at 10:43 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
>=20
> It sometimes feels as if anti-spam efforts are trending in the
> direction of its being acceptable to accidentally discard a few
> dozen legitimate messages if doing so allows blocking a few
> thousand unsolicited/undesired ones.   I hope we never consider
> that a good tradeoff but, if we do, the decisions should at
> least be made openly and with some degree of community
> consensus. =20

The trend in the market (meaning "young people") is that it seems to be =
preferable to discard ALL email messages just to avoid getting a few =
SPAM.

That's a large part of why they use closed-group systems like Facebook =
and Twitter in preference to email.

Subsequent filtering/blocking and "automatic" mailing lists (like "the =
list of everybody who is interested in me and that I haven't explicitly =
blocked") and the other big part of the appeal of closed-group systems.=20=


I've tried to imagine using Facebook-like system for IETF work, and it =
is strangely compelling ...

--
Dean=

From Ted.Lemon@nominum.com  Wed Apr  3 17:01:30 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAD7521F8FFB for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 17:01:30 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dK8kYXkAY1n7 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 17:01:30 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 62CBB21F8F11 for <ietf@ietf.org>; Wed,  3 Apr 2013 17:01:30 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUVzC2tAsCZdcgE2DddLWlHC5O9xpsP1r@postini.com; Wed, 03 Apr 2013 17:01:30 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id EDFB1108A8B for <ietf@ietf.org>; Wed,  3 Apr 2013 17:01:29 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id E687119005D; Wed,  3 Apr 2013 17:01:29 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 3 Apr 2013 17:01:30 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: Sufficient email authentication requirements for IPv6
Thread-Topic: Sufficient email authentication requirements for IPv6
Thread-Index: AQHOMLjhCIU+G9h+/0KzwfMupRPUXZjFowMA
Date: Thu, 4 Apr 2013 00:01:28 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775130890@mbx-01.win.nominum.com>
References: <10229F86C86EB444898E629583FD417172798E19@PACDCEXMB06.cable.comcast.com> <7EC291A080112791E237A211@JcK-HP8200.jck.com> <AF4F3AFB-1299-4FEE-82F3-CABECA73A20F@softarmor.com>
In-Reply-To: <AF4F3AFB-1299-4FEE-82F3-CABECA73A20F@softarmor.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2BB5979426CE504B9B6958164117C026@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, "O'Reirdan, Michael" <Michael_OReirdan@Cable.Comcast.com>, John C Klensin <john-ietf@jck.com>, "Walker, Severin" <Severin_Walker@Cable.Comcast.com>, "Rosenwald, Jordan" <Jordan_Rosenwald@cable.comcast.com>, John Levine <johnl@taugh.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, 04 Apr 2013 00:01:31 -0000

On Apr 3, 2013, at 6:16 PM, Dean Willis <dean.willis@softarmor.com> wrote:
> I've tried to imagine using Facebook-like system for IETF work, and it is=
 strangely compelling ...

It would, however, be nice if it were peer-to-peer rather than monolithic.


From dougb@dougbarton.us  Wed Apr  3 18:30:43 2013
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 D765F21F8F25 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 18:30:43 -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=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2xDTNuDVUXSU for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 18:30:42 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id DC1AB21F8F13 for <ietf@ietf.org>; Wed,  3 Apr 2013 18:30:42 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:4910:bd04:5b3f:5d14] (unknown [IPv6:2001:470:d:5e7:4910:bd04:5b3f:5d14]) by dougbarton.us (Postfix) with ESMTPSA id 51CC022B8D for <ietf@ietf.org>; Thu,  4 Apr 2013 01:30:42 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1365039042; bh=q7Hw+ySTbdWcUDTNCLZJQjD+zFxA3FBwv67ka4bOebw=; h=Date:From:To:Subject:References:In-Reply-To; b=hljBXUjIbofcajV6+ZLsgiRidz5aDI7qqI2a2Wiqcjsbba3Xsi7iJTMBoha6Qm5WD TFAadezUi1XDxZw0a51Eiew0hljRFRmX8wUdSd8jpSim9tBM0Ob+17d1n6PEmJArj/ iNHsqvy0tAvBEf1eETtsqTi/OGZrYRhPDcfhe6PI=
Message-ID: <515CD7C1.8050107@dougbarton.us>
Date: Wed, 03 Apr 2013 18:30:41 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sufficient email authentication requirements for IPv6
References: <10229F86C86EB444898E629583FD417172798E19@PACDCEXMB06.cable.comcast.com> <7EC291A080112791E237A211@JcK-HP8200.jck.com> <AF4F3AFB-1299-4FEE-82F3-CABECA73A20F@softarmor.com> <8D23D4052ABE7A4490E77B1A012B630775130890@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775130890@mbx-01.win.nominum.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
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: Thu, 04 Apr 2013 01:30:44 -0000

On 04/03/2013 05:01 PM, Ted Lemon wrote:
> On Apr 3, 2013, at 6:16 PM, Dean Willis <dean.willis@softarmor.com> wrote:
>> I've tried to imagine using Facebook-like system for IETF work, and it is strangely compelling ...
>
> It would, however, be nice if it were peer-to-peer rather than monolithic.

XMPP (aka Jabber) already has such a system.

Doug


From Tom.Haynes@netapp.com  Wed Apr  3 21:14:57 2013
Return-Path: <Tom.Haynes@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 52D1711E80A5; Wed,  3 Apr 2013 21:14:57 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jAkkJbe6Is58; Wed,  3 Apr 2013 21:14:55 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id BAA6021F8A4F; Wed,  3 Apr 2013 21:14:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,405,1363158000"; d="scan'208";a="36922071"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 03 Apr 2013 21:14:55 -0700
Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r344EtB7008861; Wed, 3 Apr 2013 21:14:55 -0700 (PDT)
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.175]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.02.0342.003; Wed, 3 Apr 2013 21:14:54 -0700
From: "Haynes, Tom" <Tom.Haynes@netapp.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Subject: Re: [nfsv4] Last Call: <draft-ietf-nfsv4-rfc3530bis-25.txt> (Network	File System	(NFS) Version 4 Protocol) to Proposed Standard
Thread-Topic: [nfsv4] Last Call: <draft-ietf-nfsv4-rfc3530bis-25.txt> (Network	File System	(NFS) Version 4 Protocol) to Proposed Standard
Thread-Index: AQHOJK1Hk1lo2vsfCEaGISRIWfn6TZjCIP0AgAPg6QA=
Date: Thu, 4 Apr 2013 04:14:54 +0000
Message-ID: <830AD203-2C2A-428F-A952-08B8F5A727E9@netapp.com>
References: <20130319142244.19905.39903.idtracker@ietfa.amsl.com> <alpine.GSO.1.10.1303312327530.9389@multics.mit.edu>
In-Reply-To: <alpine.GSO.1.10.1303312327530.9389@multics.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.118]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4F13949B2D100146887AC8DB4086D04F@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, nfsv4 list <nfsv4@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Apr 2013 04:14:57 -0000

On Apr 1, 2013, at 10:01 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:

> I have not yet completed a full review of this (320-page) document, and I=
 worry that I may not finish before the deadline, so I am bringing this con=
cern to your attention now.
>=20
> Section 3.2.1.1 of this document ("Kerberos V5 as a security triple") see=
ms to indicate that it is mandatory for a conformant NFSv4 implementation t=
o implement the Kerberos V5 GSS-API mechanism and a few "security triples" =
(mechanism,quality of protection,service).  All of the mandatory-to-impleme=
nt security triples use the DES-MAC-MD5 algorithm. The draft goes on to ind=
icate that clients should engage in security negotiation (section 3.3) to d=
etermine what security to use for bulk operation, and that since kerberos-v=
5 under RPCSEC_GSS is mandatory, the negotiation will be performed using th=
at security provider.  The actual mechanism resulting from the negotiation =
may be different (or may be the same), but this single-DES mechanism seems =
to be required to be used to protect the negotiation step.
>=20
> Given that the kerberos working group has published RFC 6649 (Deprecate D=
ES, RC4-HMAC-EXP, and Other Weak Cryptographic Algorithms in Kerberos) and =
single-DES is known to be critically vulnerable to brute-force attacks, I h=
ave grave concern about the IETF publishing new standards documents that ma=
ndate the implementation of single-DES and do not specify strong cryptograp=
hic algorithms.  I feel that to do so would be misleading implementors into=
 believing that single-DES is sufficient and other mechanisms need not be i=
mplemented, when in reality this is not true.
>=20
> Sincerely,
>=20
> Ben Kaduk
> MIT Kerberos Consortium


Hi Ben,

Thanks for pointing this out - the last work on Kerberos for this bis
was done before RFC 6649 was published.

While I can propose that we modify the text to point to take RFC 6649
into consideration and to deprecate DES for Kerberos in NFSv4
implementations, this will in no way invalidate the use of DES in shipping
implementations based solely on RFC 3530.

We did have the following in RFC 3530:

   Users and implementors are warned that 56 bit DES is no longer
   considered state of the art in terms of resistance to brute force
   attacks.  Once a revision to [RFC1964] is available that adds support
   for AES, implementors are urged to incorporate AES into their NFSv4
   over Kerberos V5 protocol stacks, and users are similarly urged to
   migrate to the use of AES.

And in RFC 5661, we have this wording:

   At the time NFSv4.1 was specified, the Advanced Encryption Standard
   (AES) with HMAC-SHA1 was a REQUIRED algorithm set for Kerberos V5.
   In contrast, when NFSv4.0 was specified, weaker algorithm sets were
   REQUIRED for Kerberos V5, and were REQUIRED in the NFSv4.0
   specification, because the Kerberos V5 specification at the time did
   not specify stronger algorithms.  The NFSv4.1 specification does not
   specify REQUIRED algorithms for Kerberos V5, and instead, the
   implementor is expected to track the evolution of the Kerberos V5
   standard if and when stronger algorithms are specified.

And instead of referencing RFC 1964, it instead references:

   [5]   Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos Version
         5 Generic Security Service Application Program Interface (GSS-
         API) Mechanism Version 2", RFC 4121, July 2005.

My proposal is that we adopt the language from RFC 5661:

   At the time of this document, the Advanced Encryption Standard
   (AES) with HMAC-SHA1 was a REQUIRED algorithm set for Kerberos V5.
   In contrast, when NFSv4.0 was first specified, weaker algorithm sets wer=
e
   REQUIRED for Kerberos V5, and were REQUIRED in the NFSv4.0
   specification, because the Kerberos V5 specification at the time did
   not specify stronger algorithms.  The NFSv4.0 specification no longer
   specifies REQUIRED algorithms for Kerberos V5, and instead, the
   implementor is expected to track the evolution of the Kerberos V5
   standard if and when stronger algorithms are specified.

In essence, the proposal is to replace Section 3.2 in 3530bis with
that of Section 2.2.1 of 5661. You would not see DES in the new
content.

Does this alleviate your concern?

Thanks,
Tom=

From nico@cryptonector.com  Wed Apr  3 14:07:13 2013
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5635A21F8F21; Wed,  3 Apr 2013 14:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Tgn4sNuCTjT; Wed,  3 Apr 2013 14:07:12 -0700 (PDT)
Received: from homiemail-a30.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id B05C021F8F10; Wed,  3 Apr 2013 14:07:12 -0700 (PDT)
Received: from homiemail-a30.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a30.g.dreamhost.com (Postfix) with ESMTP id 6CFA021DE6A; Wed,  3 Apr 2013 14:07:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=BbKACLYqkV8M3QhUNqi/ C8xXqRI=; b=FJ7r+MMapQUDgNWLHc86aK7YqtbRYE1XiJUuYI3rTDTtcRhzZVMP k1Xybx95hfBEl5ClHLGV6K5oOrEFmlkHnDI8mPFhDJHkYinloafIxwzFyb23ZBGq tLHe+RqBaUcFhj1i5E1gakQe2NvxR7Ij4oriP8VzqUeZtqfx8vvhzno=
Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a30.g.dreamhost.com (Postfix) with ESMTPSA id E275521DE58;  Wed,  3 Apr 2013 14:07:11 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id p43so1547518wea.10 for <multiple recipients>; Wed, 03 Apr 2013 14:07:10 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.77.226 with SMTP id v2mr24814528wiw.33.1365023230434; Wed, 03 Apr 2013 14:07:10 -0700 (PDT)
Received: by 10.217.105.195 with HTTP; Wed, 3 Apr 2013 14:07:10 -0700 (PDT)
In-Reply-To: <alpine.GSO.1.10.1303312327530.9389@multics.mit.edu>
References: <20130319142244.19905.39903.idtracker@ietfa.amsl.com> <alpine.GSO.1.10.1303312327530.9389@multics.mit.edu>
Date: Wed, 3 Apr 2013 16:07:10 -0500
Message-ID: <CAK3OfOidT3dX6DiD54sVFYON0ROKF6J1TeGsntxj2XGe5txWnA@mail.gmail.com>
Subject: Re: [secdir] [nfsv4] Last Call: <draft-ietf-nfsv4-rfc3530bis-25.txt> (Network File System (NFS) Version 4 Protocol) to Proposed Standard
From: Nico Williams <nico@cryptonector.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Thu, 04 Apr 2013 08:15:13 -0700
Cc: ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Apr 2013 21:07:13 -0000

On Mon, Apr 1, 2013 at 12:01 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> Section 3.2.1.1 of this document ("Kerberos V5 as a security triple") seems
> to indicate that it is mandatory for a conformant NFSv4 implementation to
> implement the Kerberos V5 GSS-API mechanism and a few "security triples"
> (mechanism,quality of protection,service).  All of the
> mandatory-to-implement security triples use the DES-MAC-MD5 algorithm. The
> draft goes on to indicate that clients should engage in security negotiation
> (section 3.3) to determine what security to use for bulk operation, and that
> since kerberos-v5 under RPCSEC_GSS is mandatory, the negotiation will be
> performed using that security provider.  The actual mechanism resulting from
> the negotiation may be different (or may be the same), but this single-DES
> mechanism seems to be required to be used to protect the negotiation step.

Oh, well, this is just outdated text.  And indeed, the GSS-API's
notion of "qop" (quality of protection) is broken: it's used in the
wrong place (per-msg token functions).  The GSS qop brokenness is why
this text persists.

OLD:
   1 == number of pseudo flavor
   2 == name of pseudo flavor
   3 == mechanism's OID
   4 == mechanism's algorithm(s)
   5 == RPCSEC_GSS service

   1      2     3                    4             5
   --------------------------------------------------------------------
   390003 krb5  1.2.840.113554.1.2.2 DES MAC MD5   rpc_gss_svc_none
   390004 krb5i 1.2.840.113554.1.2.2 DES MAC MD5   rpc_gss_svc_integrity
   390005 krb5p 1.2.840.113554.1.2.2 DES MAC MD5   rpc_gss_svc_privacy
                                     for integrity,
                                     and 56 bit DES
                                     for privacy.

NEW:
   1 == number of pseudo flavor
   2 == name of pseudo flavor
   3 == mechanism's OID
   4 == qop
   5 == RPCSEC_GSS service

   1      2     3                    4             5
   --------------------------------------------------------------------
   390003 krb5  1.2.840.113554.1.2.2 0   rpc_gss_svc_none
   390004 krb5i 1.2.840.113554.1.2.2 0   rpc_gss_svc_integrity
   390005 krb5p 1.2.840.113554.1.2.2 0   rpc_gss_svc_privacy

KITTEN WG should undertake an extension to replace the broken qop concept.

Nico
--

From david.black@emc.com  Wed Apr  3 10:04:42 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 716C221F8F56; Wed,  3 Apr 2013 10:04:42 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPdFAoY03Sjy; Wed,  3 Apr 2013 10:04:40 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6899321F8F40; Wed,  3 Apr 2013 10:04:38 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r33H4Xe3026469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Apr 2013 13:04:33 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 3 Apr 2013 13:04:14 -0400
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r33H4ALW029953; Wed, 3 Apr 2013 13:04:10 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Wed, 3 Apr 2013 13:04:09 -0400
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "McPherson, Danny" <dmcpherson@verisign.com>, Fred Baker <fred@cisco.com>, "joel.halpern@ericsson.com" <joel.halpern@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Wed, 3 Apr 2013 13:04:08 -0400
Subject: RE: Gen-ART review of draft-ietf-savi-threat-scope-07
Thread-Topic: Gen-ART review of draft-ietf-savi-threat-scope-07
Thread-Index: AcwRKxLMGPOwf18pRUizv8st+VLKC4QxHuTAAbSUPlA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293D371CF@MX15A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E055F69357F@MX14A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 04 Apr 2013 08:15:49 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, "savi@ietf.org" <savi@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Apr 2013 17:04:42 -0000

The -07 version of this draft resolves all of the issues raised by the Gen-=
ART
review of the -06 version.  Discussion of the review with the authors has
resulted in a common understanding that there is no need for additional tex=
t
on statically allowing all source addresses through all links in a set of
teamed/aggregated links - that's at best "nice to have" for this draft, but
not essential.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Monday, March 25, 2013 9:04 PM
> To: McPherson, Danny; Fred Baker; joel.halpern@ericsson.com; gen-art@ietf=
.org
> Cc: Jean-Michel Combes; Ted Lemon; savi@ietf.org; Black, David; ietf@ietf=
.org
> Subject: Gen-ART review of draft-ietf-savi-threat-scope-06
>=20
> I have been selected as the General Area Review Team (Gen-ART) reviewer
> for this draft (for background on Gen-ART, please see
> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>=20
> Please wait for direction from your document shepherd or
> AD before posting a new version of the draft.
>=20
> Document: draft-ietf-savi-threat-scope-06
> Reviewer: David L. Black
> Review Date: March 27, 2013
> IESG Telechat Date: (if known)
>=20
> Summary: This draft is on the right track, but has open issues, described=
 in
> the review.
>=20
> Looking at the original Gen-ART review of the -05 draft and checking the =
diffs
> between -05 and -06, the issues raised by that review have only been part=
ially
> addressed:
>=20
> > There is no discussion of link teaming or aggregation (e.g., via LACP);=
 this
> > may affect source address validation functionality by requiring the sam=
e
> > validation checks on all aggregated ports.  An important case to discus=
s
> > is where the aggregated host links are connected to ports on different
> > switches (e.g., in an active/passive configuration).
>=20
> This is partially addressed on 4.1.2 (new section in -06), but only in te=
rms
> of moving validation state when something like LACP reconfigures.  This h=
as a
> couple of shortcomings:
> a) the alternative of statically  allowing all source addresses through a=
ll
> 	teamed/aggregated links (decouples SAVI state from link
> teaming/aggregation
> 	state) should also be mentioned, and
> b) the new text implies that LACP is the only way to cause this situation=
 -
> it's
> 	not, so LACP should be used as an example.  VRRP is another example.
>=20
> > (1) Some of the software switch implementations are single instance swi=
tches
> > whose implementation is distributed across multiple physical servers.  =
This
> > results in concerns similar to the link aggregation discussion above.
>=20
> I don't think this has been addressed, but the notion of single-instance
> switches
> could be added to the generalization of the new text in 4.1.2.
>=20
> > (2) Live migration of virtual machines among physical servers causes
> > relocation of MAC addresses across switch ports.  A so-called "gratuito=
us
> ARP"
> > is often used to inform the network of the MAC address move; port-based
> > source address validation information needs to move in response to such
> ARPs.
> >
> > (3) MAC address relocation is also used as a failure recovery technique=
; the
> > surviving hardware element (e.g., host in a cluster) takes over the MAC
> > addresses of the failed hardware; like the previous case, a "gratuitous=
 ARP"
> > is a common means of informing the network that the MAC address has mov=
ed,
> > and source address validation information needs to move in response to =
it.
> >
> > Minor issues:
> >
> > There doesn't seem to be much discussion of dynamic network reconfigura=
tion,
> > which may change traffic egress points.  VRRP may be a useful example t=
o
> > discuss beyond the typical routing protocol updates to forwarding table=
s.
>=20
> A paragraph has been added to 5.2.3 to address all three of the above
> concerns.
> I guess that's ok, but I would have liked to see some text pointing out t=
hat a
> MAC move can be detected by the switches and used to update SAVI state ab=
out
> which port(s) a MAC is accessed through.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Friday, May 13, 2011 1:03 AM
> > To: McPherson, Danny; Fred Baker; joel.halpern@ericsson.com; gen-
> art@ietf.org
> > Cc: Black, David; Christian Vogt; Jean-Michel Combes; Jari Arkko;
> > savi@ietf.org
> > Subject: Gen-ART review of draft-ietf-savi-threat-scope-05
> >
> > 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-savi-threat-scope-05
> > Reviewer: David L. Black
> > Review Date: 12 May 2011
> > IETF LC End Date: 18 May 2011
> >
> > Summary: This draft is on the right track, but has open issues, describ=
ed in
> > the review.
> >
> > This draft discusses the threats and deployment environment for IP sour=
ce
> > address validation with particular attention to finer-grain validation =
that
> > could be used within a network to validate IP addresses closer to the
> sources
> > of network traffic than ingress to an ISP's network.
> >
> > Major issues:
> >
> > There is no discussion of link teaming or aggregation (e.g., via LACP);=
 this
> > may affect source address validation functionality by requiring the sam=
e
> > validation checks on all aggregated ports.  An important case to discus=
s
> > is where the aggregated host links are connected to ports on different
> > switches
> > (e.g., in an active/passive configuration).
> >
> > The discussion of multi-instance hosts in section 5.2.3 is incomplete
> > in several important aspects:
> >
> > (1) Some of the software switch implementations are single instance swi=
tches
> > whose implementation is distributed across multiple physical servers.  =
This
> > results in concerns similar to the link aggregation discussion above.
> >
> > (2) Live migration of virtual machines among physical servers causes
> > relocation of MAC addresses across switch ports.  A so-called "gratuito=
us
> ARP"
> > is often used to inform the network of the MAC address move; port-based
> > source address validation information needs to move in response to such
> ARPs.
> >
> > (3) MAC address relocation is also used as a failure recovery technique=
; the
> > surviving hardware element (e.g., host in a cluster) takes over the MAC
> > addresses of the failed hardware; like the previous case, a "gratuitous=
 ARP"
> > is a common means of informing the network that the MAC address has mov=
ed,
> > and source address validation information needs to move in response to =
it.
> >
> > Minor issues:
> >
> > There doesn't seem to be much discussion of dynamic network reconfigura=
tion,
> > which may change traffic egress points.  VRRP may be a useful example t=
o
> > discuss beyond the typical routing protocol updates to forwarding table=
s.
> >
> > Nits/editorial comments:
> >
> > idnits 2.12.11 ran clean.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >


From hsantos@santronics.com  Wed Apr  3 18:01:42 2013
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEEB21F9310 for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 18:01:42 -0700 (PDT)
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, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E3j6+Mr6Nl0U for <ietf@ietfa.amsl.com>; Wed,  3 Apr 2013 18:01:41 -0700 (PDT)
Received: from mail.santronics.com (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3D0CB21F9305 for <ietf@ietf.org>; Wed,  3 Apr 2013 18:01:40 -0700 (PDT)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1823; t=1365037293; h=Received:Received: Message-ID:From:To:Subject:Date:Organization:List-ID; bh=T74aldC VZwwpMOTjY87velIa6BE=; b=oMErP1sqMFe1YDEooKL0abRonDA1x86sxvhS6N2 reKJe6k3Z+exA9j9DB8Mquy/GD9ZVLCgqjdFNqr8vy+PdC7o08xjFcyeTnXe8iap T4kYImu9OQlqIG6EJuP/5Z4UmuoICuAwK2zIT2fuo9eqEmkp6UoNJkFylKreglLd 7O/U=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 03 Apr 2013 20:01:33 -0500
Received: from hdev1 ([99.121.4.27]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3831003710.47452.4916; Wed, 03 Apr 2013 20:01:32 -0500
Message-ID: <000801ce30d0$a5bde720$0201a8c0@hdev1>
From: "Hector Santos" <hsantos@santronics.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>, "Dean Willis" <dean.willis@softarmor.com>
References: <10229F86C86EB444898E629583FD417172798E19@PACDCEXMB06.cable.comcast.com><7EC291A080112791E237A211@JcK-HP8200.jck.com><AF4F3AFB-1299-4FEE-82F3-CABECA73A20F@softarmor.com> <8D23D4052ABE7A4490E77B1A012B630775130890@mbx-01.win.nominum.com>
Subject: Re: Sufficient email authentication requirements for IPv6
Date: Wed, 3 Apr 2013 21:06:32 -0400
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.3790.1830
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
X-Mailman-Approved-At: Thu, 04 Apr 2013 08:15:49 -0700
Cc: ietf@ietf.org, "O'Reirdan, Michael" <Michael_OReirdan@Cable.Comcast.com>, John C Klensin <john-ietf@jck.com>, "Walker, Severin" <Severin_Walker@Cable.Comcast.com>, "Rosenwald, Jordan" <Jordan_Rosenwald@cable.comcast.com>, John Levine <johnl@taugh.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, 04 Apr 2013 01:01:42 -0000

I would suggest it is always both.  The trend was back to centralization, 
but as the devices become more powerful, distributed (offloading, P2P, P2B) 
methods are considered again.  A constant battle of having a terminal vs 
frontend gui client

Facebook itself seems to be reverting to traditional groupware 
communications methods.  Just last week or so, they just added a REPLY 
button and the display now has the "tree" like threads layouts now.  They do 
beta testing Live too!   Its all strangely done, and you can tell they are 
still learning the email/group communications curve. Its not in all 
renderings also. The mobile version does not show this real estate (screen) 
consuming trait.    At some point, it has to be single source again (if only 
to start saving money).

The IETF can benefit greatly in putting up some servers to host some online 
communications methods. I believe it should also offer its own membership 
and provide IETF.ORG email accounts as well. :)

--
Hector Santos, CTO/CEO
Santronics Software, Inc.
http://www.santronics.com

----- Original Message ----- 
From: "Ted Lemon" <Ted.Lemon@nominum.com>
To: "Dean Willis" <dean.willis@softarmor.com>
Cc: <ietf@ietf.org>; "O'Reirdan,Michael" 
<Michael_OReirdan@Cable.Comcast.com>; "John C Klensin" <john-ietf@jck.com>; 
"Walker,Severin" <Severin_Walker@Cable.Comcast.com>; "Rosenwald,Jordan" 
<Jordan_Rosenwald@cable.comcast.com>; "John Levine" <johnl@taugh.com>
Sent: Wednesday, April 03, 2013 8:01 PM
Subject: Re: Sufficient email authentication requirements for IPv6


On Apr 3, 2013, at 6:16 PM, Dean Willis <dean.willis@softarmor.com> wrote:
> I've tried to imagine using Facebook-like system for IETF work, and it is 
> strangely compelling ...

It would, however, be nice if it were peer-to-peer rather than monolithic.




From joelja@bogus.com  Thu Apr  4 09:55:45 2013
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 A0FF221F9404 for <ietf@ietfa.amsl.com>; Thu,  4 Apr 2013 09:55:45 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W7s3fhcYuWaS for <ietf@ietfa.amsl.com>; Thu,  4 Apr 2013 09:55:45 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 232B521F8BC0 for <ietf@ietf.org>; Thu,  4 Apr 2013 09:55:45 -0700 (PDT)
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 r34GtiY1097399 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 4 Apr 2013 16:55:44 GMT (envelope-from joelja@bogus.com)
Message-ID: <515DB08B.80201@bogus.com>
Date: Thu, 04 Apr 2013 09:55:39 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20100101 Thunderbird/20.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, Eric Burger <eburger@standardstrack.com>
Subject: Re: Less Corporate Diversity
References: <FB4D5027-9279-47DA-A122-91C65D1DB54D@standardstrack.com> <FF0C573C-DFC9-4241-8E97-1943A4831FAE@piuha.net>
In-Reply-To: <FF0C573C-DFC9-4241-8E97-1943A4831FAE@piuha.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, 04 Apr 2013 16:55:44 +0000 (UTC)
Cc: "ietf@ietf.org 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, 04 Apr 2013 16:55:45 -0000

this late  but I thought I'd comment on one part of it.

On 3/20/13 3:36 PM, Jari Arkko wrote:
> I think it is mostly market forces and historical reasons, and the development of the IETF to focus on more particular core aspects of the Internet (like routing) as opposed to what the small shops might work on.
>
> But I think we are missing a bit of the point in this discussion. I do not feel that we need to prove we are somehow "no worse" than industry average. The point is that *if* we had more diversity along many of the discussed lines, we'd be far better off. For instance, having people from multiple organisations provide input to a last would be preferable to just a few. Similarly with the other dimensions of diversity. When I talked to some of the ISOC fellows last week, I realised peering is very different on different continents.
Different doesn't generally mean good, in the peering case.

There are plenty of examples of monopoly PTTs or regulators engaging in 
behavior that impacts the usability of or availability of traffic 
exchange, there's all sorts of market failures, and there's deliberately 
uncompetitive practices from some of the participants. so when we look 
at the diversity of experience for network operators not all the 
diversity is a happy place.
>   Even if there may be less economic activity on networking on those continents, it would be good for us to understand the real situations around the world, as opposed to thinking the whole world is like where we live. Diversity = good in most cases, and increasing that goodness should be the goal.
>
> Jari
>
>


From jari.arkko@piuha.net  Thu Apr  4 10:22:24 2013
Return-Path: <jari.arkko@piuha.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 BFD4121F8F0E for <ietf@ietfa.amsl.com>; Thu,  4 Apr 2013 10:22:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id acP3z0xyvtcd for <ietf@ietfa.amsl.com>; Thu,  4 Apr 2013 10:22:24 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFE521F93EF for <ietf@ietf.org>; Thu,  4 Apr 2013 10:22:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7C25C2CC55; Thu,  4 Apr 2013 20:22:23 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BPCMjoDHpD-n; Thu,  4 Apr 2013 20:22:22 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id C6CAB2CC4A; Thu,  4 Apr 2013 20:22:22 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Less Corporate Diversity
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <515DB08B.80201@bogus.com>
Date: Thu, 4 Apr 2013 20:22:22 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <754BC5ED-B16E-4DA9-91E7-D0C1437BC38F@piuha.net>
References: <FB4D5027-9279-47DA-A122-91C65D1DB54D@standardstrack.com> <FF0C573C-DFC9-4241-8E97-1943A4831FAE@piuha.net> <515DB08B.80201@bogus.com>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, Eric Burger <eburger@standardstrack.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, 04 Apr 2013 17:22:25 -0000

Joel,

> Different doesn't generally mean good, in the peering case.
>=20
> There are plenty of examples of monopoly PTTs or regulators engaging =
in behavior that impacts the usability of or availability of traffic =
exchange, there's all sorts of market failures, and there's deliberately =
uncompetitive practices from some of the participants. so when we look =
at the diversity of experience for network operators not all the =
diversity is a happy place.

I agree, of course. And the Internet community needs to work on getting =
to a better situation where such breakage exists. (My point on the =
diversity thread was that it is good to understand what the situations =
are in the world, not that those situations themselves are necessarily =
always good=85)

Jari



From narten@us.ibm.com  Thu Apr  4 21:53:14 2013
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 3CAF721F96B8 for <ietf@ietfa.amsl.com>; Thu,  4 Apr 2013 21:53:14 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m4lwHZbJ2MaH for <ietf@ietfa.amsl.com>; Thu,  4 Apr 2013 21:53:13 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id AB2AE21F8BA4 for <ietf@ietf.org>; Thu,  4 Apr 2013 21:53:12 -0700 (PDT)
Received: from /spool/local by e7.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, 5 Apr 2013 00:53:11 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 5 Apr 2013 00:53:10 -0400
Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [9.56.227.237]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 577B738C801A for <ietf@ietf.org>; Fri,  5 Apr 2013 00:53:09 -0400 (EDT)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r354r9T0325294 for <ietf@ietf.org>; Fri, 5 Apr 2013 00:53:09 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r354r87P020572 for <ietf@ietf.org>; Fri, 5 Apr 2013 01:53:09 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r354r8hg020541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 5 Apr 2013 01:53:08 -0300
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 r354r7ja028771 for <ietf@ietf.org>; Fri, 5 Apr 2013 00:53:07 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r354r73Q028728 for ietf@ietf.org; Fri, 5 Apr 2013 00:53:07 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201304050453.r354r73Q028728@rotala.raleigh.ibm.com>
Date: Fri, 05 Apr 2013 00:53:06 -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-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13040504-5806-0000-0000-0000209BBC57
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Apr 2013 04:53:14 -0000

Total of 99 messages in the last 7 days.
 
script run at: Fri Apr  5 00:53:06 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.06% |    6 |  5.52% |    45474 | sm@resistor.net
  5.05% |    5 |  4.08% |    33620 | fgont@si6networks.com
  4.04% |    4 |  3.92% |    32357 | rjsparks@nostrum.com
  3.03% |    3 |  4.87% |    40120 | stbryant@cisco.com
  4.04% |    4 |  3.55% |    29304 | brian.e.carpenter@gmail.com
  3.03% |    3 |  4.16% |    34318 | doug.mtview@gmail.com
  3.03% |    3 |  4.14% |    34139 | david.black@emc.com
  4.04% |    4 |  2.95% |    24285 | ted.lemon@nominum.com
  4.04% |    4 |  2.93% |    24153 | dhc@dcrocker.net
  2.02% |    2 |  3.60% |    29693 | lufang@cisco.com
  3.03% |    3 |  2.23% |    18352 | dougb@dougbarton.us
  3.03% |    3 |  2.05% |    16875 | housley@vigilsec.com
  2.02% |    2 |  2.97% |    24450 | leo.liubing@huawei.com
  1.01% |    1 |  3.82% |    31525 | michael.scharf@alcatel-lucent.com
  1.01% |    1 |  3.17% |    26096 | piyush@ditenity.com
  2.02% |    2 |  2.08% |    17186 | eburger@cs.georgetown.edu
  2.02% |    2 |  2.02% |    16651 | abdussalambaryun@gmail.com
  2.02% |    2 |  1.84% |    15189 | mstjohns@comcast.net
  2.02% |    2 |  1.82% |    15024 | hsantos@isdg.net
  2.02% |    2 |  1.63% |    13472 | huitema@microsoft.com
  2.02% |    2 |  1.63% |    13447 | susielu25@gmail.com
  2.02% |    2 |  1.62% |    13386 | jari.arkko@piuha.net
  2.02% |    2 |  1.47% |    12151 | johnl@taugh.com
  2.02% |    2 |  1.43% |    11783 | swmike@swm.pp.se
  2.02% |    2 |  1.37% |    11282 | alexey.melnikov@isode.com
  1.01% |    1 |  1.90% |    15665 | rlb@ipv.sx
  1.01% |    1 |  1.40% |    11523 | paul.doolan@nsn.com
  1.01% |    1 |  1.26% |    10393 | scott.mansfield@ericsson.com
  1.01% |    1 |  1.20% |     9904 | mike5guo@gmail.com
  1.01% |    1 |  1.16% |     9571 | narten@us.ibm.com
  1.01% |    1 |  1.14% |     9362 | drafts1962@yahoo.co.uk
  1.01% |    1 |  1.12% |     9220 | d.raft@rocketmail.com
  1.01% |    1 |  1.11% |     9186 | tom.haynes@netapp.com
  1.01% |    1 |  1.11% |     9167 | wesley.george@twcable.com
  1.01% |    1 |  1.06% |     8737 | tony@att.com
  1.01% |    1 |  1.02% |     8429 | thierry.moreau@connotech.com
  1.01% |    1 |  0.96% |     7908 | john-ietf@jck.com
  1.01% |    1 |  0.95% |     7853 | jmh@joelhalpern.com
  1.01% |    1 |  0.89% |     7378 | nico@cryptonector.com
  1.01% |    1 |  0.87% |     7176 | kaduk@mit.edu
  1.01% |    1 |  0.85% |     7014 | dean.willis@softarmor.com
  1.01% |    1 |  0.84% |     6896 | david.kessens@nsn.com
  1.01% |    1 |  0.83% |     6879 | jason_livingood@cable.comcast.com
  1.01% |    1 |  0.83% |     6873 | hsantos@santronics.com
  1.01% |    1 |  0.81% |     6678 | cabo@tzi.org
  1.01% |    1 |  0.79% |     6540 | stefan@aaa-sec.com
  1.01% |    1 |  0.78% |     6462 | stig@venaas.com
  1.01% |    1 |  0.75% |     6214 | bob.hinden@gmail.com
  1.01% |    1 |  0.74% |     6122 | jcurran@istaff.org
  1.01% |    1 |  0.74% |     6066 | swb@internet2.edu
  1.01% |    1 |  0.73% |     5981 | joelja@bogus.com
  1.01% |    1 |  0.70% |     5764 | yangkun2005@gmail.com
  1.01% |    1 |  0.68% |     5607 | l.wood@surrey.ac.uk
  1.01% |    1 |  0.66% |     5461 | presnick@qti.qualcomm.com
  1.01% |    1 |  0.65% |     5367 | hartmans-ietf@mit.edu
  1.01% |    1 |  0.57% |     4666 | wjhns1@hardakers.net
--------+------+--------+----------+------------------------
100.00% |   99 |100.00% |   824394 | Total


From shimshamshimmy@gmail.com  Fri Apr  5 00:24:06 2013
Return-Path: <shimshamshimmy@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 850AD21F96D1 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 00:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Level: 
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SUBJ_ALL_CAPS=2.077]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WqSZrf2tQIj0 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 00:24:05 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC6A21F96CF for <ietf@ietf.org>; Fri,  5 Apr 2013 00:24:05 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id c10so277382wiw.14 for <ietf@ietf.org>; Fri, 05 Apr 2013 00:24:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=m27JiO+JeSWDYuDGcIXRcbItj3mrVd9TmQtq3W1UHyI=; b=fwVeokqq25mk3bo3Pfnh+3sKm3fqdz3hQTYCPnLNeoWWbxFOUUerEg93VgnPp6HUo1 u0c6Guo0IN7luZMG+Yfo1SsKY7D4ushMYFC0btAAJ6YhABPo18QJPcVYXlGopKjP64RK jE0rwSzUXS2Xudn5Gn8o+1uUpz3to58XfX6Z94GaSMtb0vfKs+U2E5WOyb5us4J4x5WE 4w+ktNBhVsp9XxjrNvPkdMM+QUcn2btyhBbkHsUAwDbnEb+4v3YnCngF8mF2KZ5Ow6PK ffwC8hiQXsttkX7MHKEOBfyKSWqyQKUGdO/NyVYykpfkObk8gbjOTTaBy4GjAMBKLKwV fRRA==
X-Received: by 10.194.81.40 with SMTP id w8mr14205475wjx.14.1365146644388; Fri, 05 Apr 2013 00:24:04 -0700 (PDT)
MIME-Version: 1.0
Sender: shimshamshimmy@gmail.com
Received: by 10.194.124.204 with HTTP; Fri, 5 Apr 2013 00:23:44 -0700 (PDT)
From: Jun Murai <jun@wide.ad.jp>
Date: Fri, 5 Apr 2013 16:23:44 +0900
X-Google-Sender-Auth: Vgnp4t4ZuskKp2bUwiy2E8J7i1I
Message-ID: <CA+k18nVMnS-cbqR0KMzggRW1p9MGQdBWB+Nq29NkDn=MXZ_X8w@mail.gmail.com>
Subject: CALL FOR CANDIDATES FOR ITOJUN SERVICE AWARD
To: "ietf@ietf. org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bb04364ce26f904d997f88e
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Apr 2013 07:24:06 -0000

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

Dear IETFers,

The Itojun Service Award is presented every year to an individual or a
group who has made outstanding contributions in service to the IPv6
community.   The deadline for nominations for this year's award is 12
July 2013.  The award will be presented at the 88th meeting of the
IETF to be held in November 2013 in Vancouver, Canada.

About the Award

The Itojun Service Award, established by the friends of Dr. Jun-ichiro
"Itojun" Hagino and administered by the Internet Society (ISOC),
recognises and commemorates the extraordinary dedication of Itojun to
IPv6 development.  The award includes a presentation crystal, a
US$3,000 honorarium, and a travel grant.

The award is named after Dr. Jun-ichiro "Itojun" Hagino, who passed
away in 2007, aged just 37.  Itojun worked as a Senior Researcher at
Internet Initiative Japan Inc. (IIJ), was a member of the board of the
Widely Integrated Distributed Environment (WIDE) project, and from
1998 to 2006 served on the groundbreaking KAME project in Japan as the
"IPv6 samurai". He was also a member of the Internet Architecture
Board (IAB) from 2003 to 2005.

The award is focused on pragmatic technical contributions, especially
related to development or operation of IPv6 networking, keeping with
the spirit of servicing the Internet.  With respect to the spirit, the
selection committee seeks contributors to the Internet as a whole;
open source developers are a common example of such contributors,
although this is not a requirement for expected nominees.  While the
committee primarily considers practical contributions such as software
development or network operation, higher level efforts that help those
direct contributions will also be appreciated in this regard.

Nominees' contribution should be substantial, but could be immature or
ongoing; this award aims to encourage the contributor to continue
their efforts, rather than only recognizing well established work.
Finally, contributions of a group of individuals will be accepted as
deployment work is often done by teams or organizations, not just a
single outstanding individual.

For additional information on the award, please visit
http://www.isoc.org/awards/itojun/

Award Nomination Procedure

Neither the nominee nor nominator needs to be a member of ISOC.
Nominate via email to <itojun-award at elists.isoc.org> and include the
following details:
1. Name and Email address of nominee (in case of a group nominee,
 names and Email addresses of representative persons of that group)
2. CV/Bio of nominee (in case of a group nominee, a summary of the
 group's achievements)
3. Statement of recommendation including specific acts, works,
 contributions, and other criteria that would show the nominee to
 fit the standard set by Itojun.  Please include corroborating
 references with their name, email address, and telephone
 number. Conclude with your affiliation, postal address, and
 telephone number as well as the postal address, telephone and fax
 number of the nominee.

Thank you in advance for your support,

Jun Murai
Itojun Service Award Selection Committee

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

<div dir=3D"ltr">Dear IETFers,<br><br>
The Itojun Service Award is presented every year to an individual or a<br>
group who has made outstanding contributions in service to the IPv6<br>
community. =A0 The deadline for nominations for this year&#39;s award is 12=
<br>
July 2013. =A0The award will be presented at the 88th meeting of the<br>
IETF to be held in November 2013 in Vancouver, Canada.<br>
<br>
About the Award<br>
<br>
The Itojun Service Award, established by the friends of Dr. Jun-ichiro<br>
&quot;Itojun&quot; Hagino and administered by the Internet Society (ISOC),<=
br>
recognises and commemorates the extraordinary dedication of Itojun to<br>
IPv6 development. =A0The award includes a presentation crystal, a<br>
US$3,000 honorarium, and a travel grant.<br>
<br>
The award is named after Dr. Jun-ichiro &quot;Itojun&quot; Hagino, who pass=
ed<br>
away in 2007, aged just 37. =A0Itojun worked as a Senior Researcher at<br>
Internet Initiative Japan Inc. (IIJ), was a member of the board of the<br>
Widely Integrated Distributed Environment (WIDE) project, and from<br>
1998 to 2006 served on the groundbreaking KAME project in Japan as the<br>
&quot;IPv6 samurai&quot;. He was also a member of the Internet Architecture=
<br>
Board (IAB) from 2003 to 2005.<br>
<br>
The award is focused on pragmatic technical contributions, especially<br>
related to development or operation of IPv6 networking, keeping with<br>
the spirit of servicing the Internet. =A0With respect to the spirit, the<br=
>
selection committee seeks contributors to the Internet as a whole;<br>
open source developers are a common example of such contributors,<br>
although this is not a requirement for expected nominees. =A0While the<br>
committee primarily considers practical contributions such as software<br>
development or network operation, higher level efforts that help those<br>
direct contributions will also be appreciated in this regard.<br>
<br>
Nominees&#39; contribution should be substantial, but could be immature or<=
br>
ongoing; this award aims to encourage the contributor to continue<br>
their efforts, rather than only recognizing well established work.<br>
Finally, contributions of a group of individuals will be accepted as<br>
deployment work is often done by teams or organizations, not just a<br>
single outstanding individual.<br>
<br>
For additional information on the award, please visit<br>
<a href=3D"http://www.isoc.org/awards/itojun/" target=3D"_blank">http://www=
.isoc.org/awards/itojun/</a><br>
<br>
Award Nomination Procedure<br>
<br>
Neither the nominee nor nominator needs to be a member of ISOC.<br>
Nominate via email to &lt;itojun-award at <a href=3D"http://elists.isoc.org=
" target=3D"_blank">elists.isoc.org</a>&gt; and include the<br>
following details:<br>
1. Name and Email address of nominee (in case of a group nominee,<br>
=A0names and Email addresses of representative persons of that group)<br>
2. CV/Bio of nominee (in case of a group nominee, a summary of the<br>
=A0group&#39;s achievements)<br>
3. Statement of recommendation including specific acts, works,<br>
=A0contributions, and other criteria that would show the nominee to<br>
=A0fit the standard set by Itojun. =A0Please include corroborating<br>
=A0references with their name, email address, and telephone<br>
=A0number. Conclude with your affiliation, postal address, and<br>
=A0telephone number as well as the postal address, telephone and fax<br>
=A0number of the nominee.<br>
<br>
Thank you in advance for your support,<br>
<br>
Jun Murai<br>
Itojun Service Award Selection Committee</div>

--047d7bb04364ce26f904d997f88e--

From loa@pi.nu  Fri Apr  5 01:47:50 2013
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 DB5B821F971B for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 01:47:50 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EmO4ix9mjAry for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 01:47:50 -0700 (PDT)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id 1344B21F9718 for <ietf@ietf.org>; Fri,  5 Apr 2013 01:47:49 -0700 (PDT)
Received: from [192.168.10.102] (unknown [121.54.51.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id A938D7FE07; Fri,  5 Apr 2013 10:47:44 +0200 (CEST)
Message-ID: <515E8FA9.1030901@pi.nu>
Date: Fri, 05 Apr 2013 10:47:37 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com>
In-Reply-To: <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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, 05 Apr 2013 08:47:51 -0000

Bob,

thinking about this and assuming that the FTL Communication are deployed
in a not too far distant future, wouldn't we have started to receive
packets that was sent in the future already now?

/Loa


On 2013-04-02 18:19, Bob Hinden wrote:
> AB,
>
> On Apr 1, 2013, at 5:45 PM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
>
>> RFC6921>It is well known that as we approach the speed of light, time
>> slows down.
>> AB> I know that time slows for something when it is in speed of light,
>> but communication is not something moving. If the packet is in speed
>> of light we may reduce the comm-delay but never less than zero. The
>> communication times don't change if at least one communicator is not
>> moving in light speed.
>>
>> My comment is that I think this RFC is not logical, and I don't
>> understand its recommendations. There is no way that a packet can be
>> received before send, packet-time never changes communicators-time
>> while the positions of both Tx and Rx are semi-fixed (change is
>> relative to communicators' times not their signal). I think the
>> communication-times may change when the communicators are at/above
>> speed of light not the signal/packet. Is my physics correct?
>
> Only time will tell.
>
> Bob
>
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From dave@cridland.net  Fri Apr  5 02:03:39 2013
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 D71A221F8614 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0JXLdlE+lVmu for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:03:39 -0700 (PDT)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 25D9A21F85EB for <ietf@ietf.org>; Fri,  5 Apr 2013 02:03:39 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id wp18so2774500obc.28 for <ietf@ietf.org>; Fri, 05 Apr 2013 02:03:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=YYObUTys7T+INvZbMb9MfuB8kYOV7dx5oe8crjXkrsQ=; b=FelqGUKzYbvNCx3Ozo6N0IfWtZ2GoOKx6LhxLtbTl9fOPQzI22fvICdmqZDR1Dz4j3 yTsg3b7JX4d4gwod0GTu4VGw0AqP74HDfu9nQlRBhzEqSt1hoNoxFl71qUEn1nfD+Z0b Ee6z6i6MMt9+F7XCrkJaJcHhN3sc2CDkPtgC8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=YYObUTys7T+INvZbMb9MfuB8kYOV7dx5oe8crjXkrsQ=; b=gR0pI7SbqsAgvv1P8djsezWd0ZfMJJXb0azbj4h57pdq3MMAOQ5x6mUyFXExHxNeJo UEo34II93/aRFbNJGaMnXvDFbgf70xqdzdHz/3QZjuUrQb3KoJuhjP0a5IAPNT0Cwtdx Fe13Lfr4isJ8Oi8dEs1kEB9EhpmROu3JNKIAjMlmBgO4LtCYVk+PrsvekAc3Fch51afX kwu1HNORcK1uz5FxpjbKn+UsFOqea73Sro8nLhhSzgH1X5guA5mGC6XvfgIxPwKuXgvP K7f+CqWXVAcuJvzW7RPHyOwybT53E6o+2Lzt+Z2heZUclV0hk/wXRXLmOYGYMaDJ5MN/ ejgw==
MIME-Version: 1.0
X-Received: by 10.182.114.97 with SMTP id jf1mr7355518obb.31.1365152618646; Fri, 05 Apr 2013 02:03:38 -0700 (PDT)
Received: by 10.60.22.105 with HTTP; Fri, 5 Apr 2013 02:03:38 -0700 (PDT)
Received: by 10.60.22.105 with HTTP; Fri, 5 Apr 2013 02:03:38 -0700 (PDT)
In-Reply-To: <515E8FA9.1030901@pi.nu>
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com> <515E8FA9.1030901@pi.nu>
Date: Fri, 5 Apr 2013 10:03:38 +0100
Message-ID: <CAKHUCzypTVZc8nmzDXPSM+RRPcJ7Rv+ngGkhE9shYH6V4c1nzQ@mail.gmail.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
From: Dave Cridland <dave@cridland.net>
To: Loa Andersson <loa@pi.nu>
Content-Type: multipart/alternative; boundary=f46d0444edf1e63f8f04d9995c46
X-Gm-Message-State: ALoCoQncCxApf5HxuVJWB08yOf3arJPYfzI+MP6Us69kwxf9KU4XRzF5UNMXV+GXRHSUko5WncB/
Cc: Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org 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: Fri, 05 Apr 2013 09:03:40 -0000

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

On 5 Apr 2013 09:47, "Loa Andersson" <loa@pi.nu> wrote:
>
> Bob,
>
> thinking about this and assuming that the FTL Communication are deployed
> in a not too far distant future, wouldn't we have started to receive
> packets that was sent in the future already now?
>

Indeed, and this tells us that publication of this was important, since
we'll need to be in a position to handle the issues that will occur much
sooner than deployment, and for that matter development of the technology.

--f46d0444edf1e63f8f04d9995c46
Content-Type: text/html; charset=ISO-8859-1

<p dir="ltr"><br>
On 5 Apr 2013 09:47, &quot;Loa Andersson&quot; &lt;<a href="mailto:loa@pi.nu">loa@pi.nu</a>&gt; wrote:<br>
&gt;<br>
&gt; Bob,<br>
&gt;<br>
&gt; thinking about this and assuming that the FTL Communication are deployed<br>
&gt; in a not too far distant future, wouldn&#39;t we have started to receive<br>
&gt; packets that was sent in the future already now?<br>
&gt;</p>
<p dir="ltr">Indeed, and this tells us that publication of this was important, since we&#39;ll need to be in a position to handle the issues that will occur much sooner than deployment, and for that matter development of the technology.</p>


--f46d0444edf1e63f8f04d9995c46--

From brian.e.carpenter@gmail.com  Fri Apr  5 02:11:06 2013
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 5F4FD21F96CD for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:11:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.776
X-Spam-Level: 
X-Spam-Status: No, score=-101.776 tagged_above=-999 required=5 tests=[AWL=-1.824, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGzXJbiBwLCP for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:11:05 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 5058021F96DA for <ietf@ietf.org>; Fri,  5 Apr 2013 02:11:05 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id z53so2846778wey.9 for <ietf@ietf.org>; Fri, 05 Apr 2013 02:11:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ao4gh0ju4qA/EkpyJIIPZ4OrlYFswOdc5+Yq02YOjQM=; b=MS8S0e3aoS0G6UFvPjNd/p+MHVzxaguRpYlKVtMiEJmOszG6FAQTNV5qrzaOxhkZxi lS5GVeZEe4+OSaxCpWv64EnROt67ci5VgoFIQrd2bbpzRtefKB0WyExAX4uQ/COHabVv 2O7nIQEtFpg/ts8loV1BTwNgPTQe/YxF4MmP+PNo7xoklNNv/Fol4EBTh7WKrycCX+/M an10s5KFCpdn3F2IHgnr9+0jQOfxzpF7TfKe9uh3ldhKJutr9hLaOiRO6VyeYWNW/sxS OW7csNbZ/Gp4bOSQVNBGVMoZ2OTA1zznaLvcxdkNkyGQDU/jvkBuu/1YSjHnN4Pbnv4E XZvQ==
X-Received: by 10.180.10.105 with SMTP id h9mr2600505wib.34.1365153064323; Fri, 05 Apr 2013 02:11:04 -0700 (PDT)
Received: from [192.168.1.65] (host-84-13-238-122.opaltelecom.net. [84.13.238.122]) by mx.google.com with ESMTPS id t7sm2406498wij.2.2013.04.05.02.11.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Apr 2013 02:11:03 -0700 (PDT)
Message-ID: <515E9530.10107@gmail.com>
Date: Fri, 05 Apr 2013 10:11:12 +0100
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: Dave Cridland <dave@cridland.net>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
References: <20130401215830.710ADB1E007@rfc-editor.org>	<CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>	<5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com>	<515E8FA9.1030901@pi.nu> <CAKHUCzypTVZc8nmzDXPSM+RRPcJ7Rv+ngGkhE9shYH6V4c1nzQ@mail.gmail.com>
In-Reply-To: <CAKHUCzypTVZc8nmzDXPSM+RRPcJ7Rv+ngGkhE9shYH6V4c1nzQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org 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: Fri, 05 Apr 2013 09:11:06 -0000

On 05/04/2013 10:03, Dave Cridland wrote:
> On 5 Apr 2013 09:47, "Loa Andersson" <loa@pi.nu> wrote:
>> Bob,
>>
>> thinking about this and assuming that the FTL Communication are deployed
>> in a not too far distant future, wouldn't we have started to receive
>> packets that was sent in the future already now?
>>
> 
> Indeed, and this tells us that publication of this was important, since
> we'll need to be in a position to handle the issues that will occur much
> sooner than deployment, and for that matter development of the technology.

If the announcement of the RFC had arrived on March 31st, that would have
demonstrated running code.

From adrian@olddog.co.uk  Fri Apr  5 02:12:19 2013
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 5B00C21F96CF for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LON4h87ie5CX for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:12:17 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id A505F21F96EE for <ietf@ietf.org>; Fri,  5 Apr 2013 02:12:15 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r359CCpl019879;  Fri, 5 Apr 2013 10:12:12 +0100
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 r359CBD6019865 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 5 Apr 2013 10:12:11 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Dave Cridland'" <dave@cridland.net>, "'Loa Andersson'" <loa@pi.nu>
References: <20130401215830.710ADB1E007@rfc-editor.org>	<CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>	<5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com>	<515E8FA9.1030901@pi.nu> <CAKHUCzypTVZc8nmzDXPSM+RRPcJ7Rv+ngGkhE9shYH6V4c1nzQ@mail.gmail.com>
In-Reply-To: <CAKHUCzypTVZc8nmzDXPSM+RRPcJ7Rv+ngGkhE9shYH6V4c1nzQ@mail.gmail.com>
Subject: RE: RFC 6921 on Design Considerations for Faster-Than-Light (FTL)	Communication
Date: Fri, 5 Apr 2013 10:12:10 +0100
Message-ID: <01de01ce31dd$a7b36b50$f71a41f0$@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: AQGFuNdULLCi9P3OTG4bbR+Jd8l5gwGyYXzxAlhbCXMCJCX7sQEtTeHxmR1nefA=
Content-Language: en-gb
Cc: 'Bob Hinden' <bob.hinden@gmail.com>, 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: Fri, 05 Apr 2013 09:12:19 -0000

So instead of asking the community "do you have an intention to implement and
deploy?" we should ask "have you already been going to have implemented and
deployed yet?"

>> thinking about this and assuming that the FTL Communication are
>> deployed in a not too far distant future, wouldn't we have started
>> to receive packets that was sent in the future already now?
>
> Indeed, and this tells us that publication of this was important,
> since we'll need to be in a position to handle the issues that will
> occur much sooner than deployment, and for that matter
> development of the technology.


From loa@pi.nu  Fri Apr  5 02:40:39 2013
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 7ADAA21F9712 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:40:39 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k+1aaqyfle3M for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:40:39 -0700 (PDT)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id ECE9321F9708 for <ietf@ietf.org>; Fri,  5 Apr 2013 02:40:38 -0700 (PDT)
Received: from [192.168.1.101] (unknown [121.54.51.84]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id A2606823B5; Fri,  5 Apr 2013 11:40:34 +0200 (CEST)
Message-ID: <515E9C0D.80400@pi.nu>
Date: Fri, 05 Apr 2013 11:40:29 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
References: <20130401215830.710ADB1E007@rfc-editor.org>	<CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com>	<5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com>	<515E8FA9.1030901@pi.nu> <CAKHUCzypTVZc8nmzDXPSM+RRPcJ7Rv+ngGkhE9shYH6V4c1nzQ@mail.gmail.com> <515E9530.10107@gmail.com>
In-Reply-To: <515E9530.10107@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org 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: Fri, 05 Apr 2013 09:40:39 -0000

On 2013-04-05 11:11, Brian E Carpenter wrote:
> On 05/04/2013 10:03, Dave Cridland wrote:
>> On 5 Apr 2013 09:47, "Loa Andersson" <loa@pi.nu> wrote:
>>> Bob,
>>>
>>> thinking about this and assuming that the FTL Communication are deployed
>>> in a not too far distant future, wouldn't we have started to receive
>>> packets that was sent in the future already now?
>>>
>>
>> Indeed, and this tells us that publication of this was important, since
>> we'll need to be in a position to handle the issues that will occur much
>> sooner than deployment, and for that matter development of the technology.
>
> If the announcement of the RFC had arrived on March 31st, that would have
> demonstrated running code.
>

Are you sure that this was not published April 1, 2014 or even 2015??

/Loa

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From abdussalambaryun@gmail.com  Fri Apr  5 02:45:43 2013
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 19EFB21F96FF for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.016
X-Spam-Level: 
X-Spam-Status: No, score=-3.016 tagged_above=-999 required=5 tests=[AWL=-0.417, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IGZZj12G2SwK for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 02:45:41 -0700 (PDT)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5286921F93D6 for <ietf@ietf.org>; Fri,  5 Apr 2013 02:45:34 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id 5so1931222pdd.3 for <ietf@ietf.org>; Fri, 05 Apr 2013 02:45:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=FxztLrBLhcpQMuJoNIs/OpVl1PYW9zDqKxOwy7dq6dI=; b=Au1vHu7+ZkW3fWQl5plCpmpLmLRgH215/h79uXK54rWI/yUyMxQBMtC5DS3VVdaSTX CDe3Dh2rTeq3FrdUpOvZhUshAAJ7rX68uJSvF/LwEDJi6rbeBkkwtxljoF4Tqb1wxJaq xqC0WXuuKl8N830iP97p0H0ba/SOlx4Z3H+TZqboC8f/irxRRnUnq7fA9cUmcbd/zxnQ tyXvW8UdTTb2Ft1rxj9B0q4MwztPG3Eme0WQg7wIDYDk9j+K7MWtVdaopHSAR8RuXOHS nMsS1gTnQOGyE7WaTiOIhNM25NWgxl/rdO33dD5LXuDvaPN9C2xCcbqk+2WC2jOSolPY wc0Q==
MIME-Version: 1.0
X-Received: by 10.66.222.228 with SMTP id qp4mr14268318pac.113.1365155134080;  Fri, 05 Apr 2013 02:45:34 -0700 (PDT)
Received: by 10.68.33.132 with HTTP; Fri, 5 Apr 2013 02:45:34 -0700 (PDT)
Date: Fri, 5 Apr 2013 11:45:34 +0200
Message-ID: <CADnDZ892i8BZLE4iC4ozf6ZQbJ8_GUgZXSngjQ1DUNDEd1hx+w@mail.gmail.com>
Subject: Re: Less Corporate Diversity
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <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: Fri, 05 Apr 2013 09:45:43 -0000

>>The point is that *if* we had more diversity along many of the discussed =
lines, we'd be far better off. For instance, having people from multiple or=
ganisations provide input to a last would be preferable to just a few. Simi=
larly with the other dimensions of diversity. When I talked to some of the =
ISOC fellows last week, I realised peering is very different on different c=
ontinents.

> Different doesn't generally mean good, in the peering case.

I think different is good and bad news (who is responsible?), but
mostly good to be detected, and hopefully corrected. It is bad for
IETF to loose participation just because experience levels or peering
are different.

>
> There are plenty of examples of monopoly PTTs or regulators engaging
> in behavior that impacts the usability of or availability of traffic
> exchange, there's all sorts of market failures, and there's
> deliberately uncompetitive practices from some of the participants. so
> when we look at the diversity of experience for network operators not
> all the diversity is a happy place.

All diverse participants are good for IETF even if majority were
uncompetitive, because no one is competitive to future experience. In
history some scholars tried to confense the majority of their theories
but were only understood in future because different minds. Some
countries are in past experience and some are in present and some may
be in future, but the IETF it is for all countries and it needs to
make fast communication between future and past, or make availability
for past components to communicate with future and verse versa,

May be the solution can be if participants got into *faster speed of
light* [RFC6921] [1] to make all countries participation in IETF
received at right times or at the similar level of experience, that
will make communicating with the IETF experiences easier,

[1] http://www.ietf.org/mail-archive/web/ietf/current/msg78376.html

AB

From mcr@sandelman.ca  Fri Apr  5 06:59:05 2013
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 9C4BD21F978F for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 06:59:05 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5N8c+1AvB6Y3 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 06:59:05 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id D9A3F21F9763 for <ietf@ietf.org>; Fri,  5 Apr 2013 06:59:04 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 007B82016D for <ietf@ietf.org>; Fri,  5 Apr 2013 10:08:25 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id B6736A9936; Fri,  5 Apr 2013 09:58:46 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9FFC3B9395 for <ietf@ietf.org>; Fri,  5 Apr 2013 09:58:46 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf <ietf@ietf.org>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
In-Reply-To: <515E8FA9.1030901@pi.nu>
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com> <515E8FA9.1030901@pi.nu>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 05 Apr 2013 09:58:46 -0400
Message-ID: <8473.1365170326@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: Fri, 05 Apr 2013 13:59:05 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Loa" =3D=3D Loa Andersson <loa@pi.nu> writes:
    Loa> thinking about this and assuming that the FTL Communication are de=
ployed
    Loa> in a not too far distant future, wouldn't we have started to recei=
ve
    Loa> packets that was sent in the future already now?

I for one, have always found these Crocker brothers suspicious: always
seem to have been at the key points in Internet future history.
I think that they are in fact a single person.=20=20
One is going forward in time, and the other one backwards.=20
(Which is which, is still open to debate)

So I claim that we  will have been receiving packets from the future for
some time now.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUV7YloqHRg3pndX9AQIGcgP/cu8onILgS6mFgdMWXrQ7fuIFOLb3yiGi
MUp6G2K4R8RZFdiCo4gLKz1p+waH610kvRbDDXVFS1EdmMlDXm72M0BxIpeaduYd
KeSgkmIg8CB5fV5kBoNKQBW4s4PqXZ/8bLFqJZ9NM6HyQ+QeKGlYHQf8f6P44Y4h
d2Q35dNuUyg=
=KvlZ
-----END PGP SIGNATURE-----
--=-=-=--

From steve@shinkuro.com  Fri Apr  5 07:08:08 2013
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 102C221F97D1 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 07:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.073
X-Spam-Level: 
X-Spam-Status: No, score=-0.073 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129, MIME_QP_LONG_LINE=1.396, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2W0P4V3AcTdj for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 07:08:07 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id EB11421F97D0 for <ietf@ietf.org>; Fri,  5 Apr 2013 07:08:06 -0700 (PDT)
Received: from dummy.name; Fri, 05 Apr 2013 14:08:05 +0000
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com> <515E8FA9.1030901@pi.nu> <8473.1365170326@sandelman.ca>
In-Reply-To: <8473.1365170326@sandelman.ca>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset=us-ascii
Message-Id: <6B23735D-7769-482C-B619-C2BBF63966B7@shinkuro.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (9B206)
From: Steve Crocker <steve@shinkuro.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Date: Fri, 5 Apr 2013 22:09:10 +0800
To: Michael Richardson <mcr+ietf@sandelman.ca>
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, 05 Apr 2013 14:08:08 -0000

I too have always found at least one of the Crocker brothers {suspicious, sm=
art, funny, irrelevant, prescient, handsome, annoying, etc.}. I've never bee=
n able to tell which is which :)

Sent from my iPad

On Apr 5, 2013, at 9:58 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote=
:

>=20
>>>>>> "Loa" =3D=3D Loa Andersson <loa@pi.nu> writes:
>    Loa> thinking about this and assuming that the FTL Communication are de=
ployed
>    Loa> in a not too far distant future, wouldn't we have started to recei=
ve
>    Loa> packets that was sent in the future already now?
>=20
> I for one, have always found these Crocker brothers suspicious: always
> seem to have been at the key points in Internet future history.
> I think that they are in fact a single person. =20
> One is going forward in time, and the other one backwards.=20
> (Which is which, is still open to debate)
>=20
> So I claim that we  will have been receiving packets from the future for
> some time now.
>=20
> --=20
> ]               Never tell me the odds!                 | ipv6 mesh networ=
ks [=20
> ]   Michael Richardson, Sandelman Software Works        | network architec=
t  [=20
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails =
   [=20
>   =20

From john@jck.com  Fri Apr  5 07:26:38 2013
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 CFF4821F97B0 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 07:26:38 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8OgIf80ucuev for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 07:26:37 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E3E8621F97AE for <ietf@ietf.org>; Fri,  5 Apr 2013 07:26:36 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1UO7b7-000K0Z-CT; Fri, 05 Apr 2013 10:26:33 -0400
Date: Fri, 05 Apr 2013 10:26:21 -0400
From: John C Klensin <john@jck.com>
To: Dave Cridland <dave@cridland.net>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL)	Communication
Message-ID: <79788B90225DE753A94F3A6F@JcK-HP8200.jck.com>
In-Reply-To: <CAKHUCzypTVZc8nmzDXPSM+RRPcJ7Rv+ngGkhE9shYH6V4c1nzQ@mail.gmail.com>
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com> <515E8FA9.1030901@pi.nu> <CAKHUCzypTVZc8nmzDXPSM+RRPcJ7Rv+ngGkhE9shYH6V4c1nzQ@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
Cc: "ietf@ietf.org 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: Fri, 05 Apr 2013 14:26:38 -0000

--On Friday, April 05, 2013 10:03 +0100 Dave Cridland
<dave@cridland.net> wrote:

>...
> Indeed, and this tells us that publication of this was
> important, since we'll need to be in a position to handle the
> issues that will occur much sooner than deployment, and for
> that matter development of the technology.
>...

Don't we already have demonstrations of this in the number of
systems that are deployed before being developed?

   john


From spencer@wonderhamster.org  Fri Apr  5 07:29:39 2013
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 5B0F321F976D for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 07:29:39 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lDVGWOYeVvb8 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 07:29:38 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id C9C4121F9701 for <ietf@ietf.org>; Fri,  5 Apr 2013 07:29:38 -0700 (PDT)
Received: from [192.168.1.79] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net [99.108.174.213]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0LmbFL-1Uwu683iSZ-00ZXjs; Fri, 05 Apr 2013 10:29:37 -0400
Message-ID: <515EDFC9.1010509@wonderhamster.org>
Date: Fri, 05 Apr 2013 09:29:29 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com> <515E8FA9.1030901@pi.nu> <8473.1365170326@sandelman.ca> <6B23735D-7769-482C-B619-C2BBF63966B7@shinkuro.com>
In-Reply-To: <6B23735D-7769-482C-B619-C2BBF63966B7@shinkuro.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:EBeu9G7AiGava189qunisGugVd7lk2EceHuaKnL+Hej qt3Mb2JsC3UTtHXqxDXgU60Cx50uSQ1ItkZCXZC69+ALFzEu6r xIGKIn6zHrQtyQB8cyfSq3AXCBXI0tRo5ygCe5jXAmGuK3XXYY ziiZPFKwcmepHX2GizATBBhJXDnuJTGi0TfKSWx/AchcVL2rHd 1AN6sGNxS47hlXz5Nly1HjM4VnfQO08uRyOCbti4tDQONIzvRD 2w5aL2dH1Pzgz1HzGe3oY+4MLtI6fZMok6JAX4xVPefvFT0k71 y1CmIeTjEglZ/CnbubRXOgWXW59td7xq6QsypuIcZLFRliP0DI 0H2sQXhCwf+/Y9TOCmtD3AOKg6ME5dW+xbZEMQEQ0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Apr 2013 14:29:39 -0000

On 4/5/2013 9:09 AM, Steve Crocker wrote:
> I too have always found at least one of the Crocker brothers {suspicious, smart, funny, irrelevant, prescient, handsome, annoying, etc.}. I've never been able to tell which is which :)

There are days when I'm really glad to be part of this community ...

Spencer

From Ted.Lemon@nominum.com  Fri Apr  5 07:35:29 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48FEE21F97CD for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 07:35:29 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tMqamBP6t3Eh for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 07:35:28 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id BAEC721F97CA for <ietf@ietf.org>; Fri,  5 Apr 2013 07:35:28 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUV7hMLlkbvRtz4rTDFf00RRjBWnyRmHC@postini.com; Fri, 05 Apr 2013 07:35:28 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5AA251081B2 for <ietf@ietf.org>; Fri,  5 Apr 2013 07:35:28 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 5494819005D; Fri,  5 Apr 2013 07:35:28 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 5 Apr 2013 07:35:28 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Topic: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Index: AQHOLzt6xZKHzVrsMkmbs2sZy6JPWpjDkrAAgAQ4o4CAAFbwAIAAAucAgAAFroCAAAGtgA==
Date: Fri, 5 Apr 2013 14:35:27 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077513334B@mbx-01.win.nominum.com>
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com> <515E8FA9.1030901@pi.nu> <8473.1365170326@sandelman.ca> <6B23735D-7769-482C-B619-C2BBF63966B7@shinkuro.com> <515EDFC9.1010509@wonderhamster.org>
In-Reply-To: <515EDFC9.1010509@wonderhamster.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <A4409EB974C9DE4F8118532B412C9D36@nominum.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, 05 Apr 2013 14:35:29 -0000

On Apr 5, 2013, at 10:29 AM, Spencer Dawkins <spencer@wonderhamster.org> wr=
ote:
> There are days when I'm really glad to be part of this community ...

Yes, but the question is, is this such a day?   :)


From nico@cryptonector.com  Thu Apr  4 09:41:29 2013
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96BBE21F8D1C; Thu,  4 Apr 2013 09:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjV3wGuTjSKO; Thu,  4 Apr 2013 09:41:29 -0700 (PDT)
Received: from homiemail-a67.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id 1A70C21F8D14; Thu,  4 Apr 2013 09:41:29 -0700 (PDT)
Received: from homiemail-a67.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTP id BA3BB27BC056;  Thu,  4 Apr 2013 09:41:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=ZimHsvHYRfFbFV8Ovqco Egeb7ZM=; b=mVN5YBUMoc9xNTTMOwwlNiHYLaXgVDDHntKZAvzWk7iKH+c+hww6 u7FRwN+l2I04b1HwwqprioJBDDYHx6lgzimoJSMGxkiCPBnJER+Bg3yRC8rGrFFf 2RE3TWAzk/r7XgHoj3brkbu6zTxTeLMB9iamiUK9+5tZ8q+BDe4TvMA=
Received: from mail-we0-f171.google.com (mail-we0-f171.google.com [74.125.82.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTPSA id AF79327BC075; Thu,  4 Apr 2013 09:41:23 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id d46so2235529wer.30 for <multiple recipients>; Thu, 04 Apr 2013 09:41:21 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.158.161 with SMTP id wv1mr10890652wjb.38.1365093681860;  Thu, 04 Apr 2013 09:41:21 -0700 (PDT)
Received: by 10.217.105.195 with HTTP; Thu, 4 Apr 2013 09:41:21 -0700 (PDT)
In-Reply-To: <CAK3OfOidT3dX6DiD54sVFYON0ROKF6J1TeGsntxj2XGe5txWnA@mail.gmail.com>
References: <20130319142244.19905.39903.idtracker@ietfa.amsl.com> <alpine.GSO.1.10.1303312327530.9389@multics.mit.edu> <CAK3OfOidT3dX6DiD54sVFYON0ROKF6J1TeGsntxj2XGe5txWnA@mail.gmail.com>
Date: Thu, 4 Apr 2013 11:41:21 -0500
Message-ID: <CAK3OfOjrWi+4sLGcnBcgCHnNMFK=90cuBS-1Q8bt=Q48GKozCA@mail.gmail.com>
Subject: Re: [secdir] [nfsv4] Last Call: <draft-ietf-nfsv4-rfc3530bis-25.txt> (Network File System (NFS) Version 4 Protocol) to Proposed Standard
From: Nico Williams <nico@cryptonector.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Fri, 05 Apr 2013 08:35:57 -0700
Cc: ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Apr 2013 16:41:29 -0000

On Wed, Apr 3, 2013 at 4:07 PM, Nico Williams <nico@cryptonector.com> wrote:
> Oh, well, this is just outdated text.  And indeed, the GSS-API's
> notion of "qop" (quality of protection) is broken: it's used in the
> wrong place (per-msg token functions).  The GSS qop brokenness is why
> this text persists.
>
> OLD:
...
> NEW:
...

Actually, I should also propose some text explaining why qop is a
busted concept and what qop 0 means ("default").

Nico
--

From kaduk@mit.edu  Thu Apr  4 10:36:16 2013
Return-Path: <kaduk@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 D064121F93CC; Thu,  4 Apr 2013 10:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.854
X-Spam-Level: 
X-Spam-Status: No, score=-2.854 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CTN4PWpYu8e5; Thu,  4 Apr 2013 10:36:16 -0700 (PDT)
Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by ietfa.amsl.com (Postfix) with ESMTP id 99D4C21F93C7; Thu,  4 Apr 2013 10:36:15 -0700 (PDT)
X-AuditID: 1209190e-b7f266d0000008cb-4d-515dba0e507c
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 58.16.02251.E0ABD515; Thu,  4 Apr 2013 13:36:14 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id r34HaC0k009503;  Thu, 4 Apr 2013 13:36:13 -0400
Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r34Ha9GV029365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 4 Apr 2013 13:36:11 -0400
Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r34Ha8KQ027661; Thu, 4 Apr 2013 13:36:08 -0400 (EDT)
Date: Thu, 4 Apr 2013 13:36:08 -0400 (EDT)
From: Benjamin Kaduk <kaduk@MIT.EDU>
To: "Haynes, Tom" <Tom.Haynes@netapp.com>, Nico Williams <nico@cryptonector.com>
Subject: Re: [nfsv4] Last Call: <draft-ietf-nfsv4-rfc3530bis-25.txt> (Network File System	(NFS) Version 4 Protocol) to Proposed Standard
In-Reply-To: <830AD203-2C2A-428F-A952-08B8F5A727E9@netapp.com>
Message-ID: <alpine.GSO.1.10.1304041234320.9389@multics.mit.edu>
References: <20130319142244.19905.39903.idtracker@ietfa.amsl.com> <alpine.GSO.1.10.1303312327530.9389@multics.mit.edu> <830AD203-2C2A-428F-A952-08B8F5A727E9@netapp.com>
User-Agent: Alpine 1.10 (GSO 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmleLIzCtJLcpLzFFi42IRYrdT1+XbFRto0HZAzeLZxvksFrPfP2K1 OHXtCJvFh4UPWSxOHTnN4sDq8fLUOUaPJUt+MnnM+PSFLYA5issmJTUnsyy1SN8ugSvjxoWX LAXPDCq2d05lbmDsV+ti5OSQEDCRWNi1nR3CFpO4cG89WxcjF4eQwD5Gib/X9jBDOBsYJT49 fQTlHGSS+ND3kRWkRUigXuLrlYVsIDaLgJbE175uRhCbTUBFYuabjWBxEYFIifOt+5lAbGaB PIknd+eDrRAW6GKUaFwzE2w3p4CdRMfR+ywgNq+Ag8TlmdtZIbatYJR4dHE9WEJUQEdi9f4p UEWCEidnPmGBmGop8W/tL9YJjIKzkKRmIUktYGRaxSibklulm5uYmVOcmqxbnJyYl5dapGus l5tZopeaUrqJERTWnJJ8Oxi/HlQ6xCjAwajEw5vRFxsoxJpYVlyZe4hRkoNJSZT36UagEF9S fkplRmJxRnxRaU5q8SFGCQ5mJRHepZuAcrwpiZVVqUX5MClpDhYlcd4rKTf9hQTSE0tSs1NT C1KLYLIyHBxKErzHdgA1ChalpqdWpGXmlCCkmTg4QYbzAA1n3QkyvLggMbc4Mx0if4pRUUqc dzNIswBIIqM0D64XlnZeMYoDvSLM2wtSxQNMWXDdr4AGMwENnno3GmRwSSJCSqqB0a+Iazbr 0tVX9/0+OOmxQgTrlkVhjhb21ka7HqXy/J2xcZYz58yYP1G/JWqe26ueOzCV5XnF5kAB/jev KvTUG3dkqD90EN4eZLb5OEfCPecd2xwLFVyCPY44TI6wPvkpZDqL4rWZJbfVF8tV1qWbr9vl Zpbz2pxDs9zpTPfUCb1C8ZdWPvoXocRSnJFoqMVcVJwIACpS8msWAwAA
X-Mailman-Approved-At: Fri, 05 Apr 2013 08:35:57 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, nfsv4 list <nfsv4@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Apr 2013 17:36:17 -0000

Hi Tom, Nico,

On Thu, 4 Apr 2013, Haynes, Tom wrote:

>
> On Apr 1, 2013, at 10:01 AM, Benjamin Kaduk <kaduk@mit.edu> wrote:
>
[snip.  Single-DES is weak and deprecated]
>
>
> Hi Ben,
>
> Thanks for pointing this out - the last work on Kerberos for this bis
> was done before RFC 6649 was published.

It did look like the Kerberos portions of the document had not been 
touched since the previous revision; RFC 6649 was probably later in coming 
than it should have been.

> While I can propose that we modify the text to point to take RFC 6649
> into consideration and to deprecate DES for Kerberos in NFSv4
> implementations, this will in no way invalidate the use of DES in shipping
> implementations based solely on RFC 3530.

Understood.  The DES-migration process has been and continues to be a long 
process; on the Kerberos side we're mostly done, but applications still 
need to adapt.  (I'm working on updates for AFS, which had DES baked into 
it pretty thoroughly.)  Thus, part of the work of the Kerberos folks is to 
actively encourage people to migrate away from DES -- though there's not 
much we can do about old standards still being used, new standards should 
encourage migration.  In this vein, my preference would be for this 
document to actively mention migration away from DES, though I understand 
that this is a stronger sentiment than is strictly speaking necessary.

Part of my concern stems from the fact that there are existing NFSv4 
implementations which remain DES-only, and I would like this document to 
strongly encourage those implementations to add support for strong crypto.

> We did have the following in RFC 3530:
>
>   Users and implementors are warned that 56 bit DES is no longer
>   considered state of the art in terms of resistance to brute force
>   attacks.  Once a revision to [RFC1964] is available that adds support
>   for AES, implementors are urged to incorporate AES into their NFSv4
>   over Kerberos V5 protocol stacks, and users are similarly urged to
>   migrate to the use of AES.
>
> And in RFC 5661, we have this wording:
>
>   At the time NFSv4.1 was specified, the Advanced Encryption Standard
>   (AES) with HMAC-SHA1 was a REQUIRED algorithm set for Kerberos V5.
>   In contrast, when NFSv4.0 was specified, weaker algorithm sets were
>   REQUIRED for Kerberos V5, and were REQUIRED in the NFSv4.0
>   specification, because the Kerberos V5 specification at the time did
>   not specify stronger algorithms.  The NFSv4.1 specification does not
>   specify REQUIRED algorithms for Kerberos V5, and instead, the
>   implementor is expected to track the evolution of the Kerberos V5
>   standard if and when stronger algorithms are specified.
>
> And instead of referencing RFC 1964, it instead references:
>
>   [5]   Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos Version
>         5 Generic Security Service Application Program Interface (GSS-
>         API) Mechanism Version 2", RFC 4121, July 2005.
>
> My proposal is that we adopt the language from RFC 5661:
>
>   At the time of this document, the Advanced Encryption Standard
>   (AES) with HMAC-SHA1 was a REQUIRED algorithm set for Kerberos V5.
>   In contrast, when NFSv4.0 was first specified, weaker algorithm sets were
>   REQUIRED for Kerberos V5, and were REQUIRED in the NFSv4.0
>   specification, because the Kerberos V5 specification at the time did
>   not specify stronger algorithms.  The NFSv4.0 specification no longer
>   specifies REQUIRED algorithms for Kerberos V5, and instead, the
>   implementor is expected to track the evolution of the Kerberos V5
>   standard if and when stronger algorithms are specified.
>
> In essence, the proposal is to replace Section 3.2 in 3530bis with
> that of Section 2.2.1 of 5661. You would not see DES in the new
> content.
>
> Does this alleviate your concern?

The quoted text would be a big improvement, but does not seem like a 
complete solution -- the table would need to be updated to remove the 
algorithm column, probably as per Nico's suggestion.  It also seems like 
section 2.2.1.1.1.2.1.1 of RFC 5661 is still applicable:

    When deploying NFSv4.1, the strength of the security achieved depends
    on the existing Kerberos V5 infrastructure.  The algorithms of
    Kerberos V5 are not directly exposed to or selectable by the client
    or server, so there is some due diligence required by the user of
    NFSv4.1 to ensure that security is acceptable where needed.

This would be a good place to reference RFC 6649 and/or mention that 
modern Kerberos implementations disable weak algorithms by default, as 
part of the "active encouragement" that I would prefer.


On Wed, 3 Apr 2013, Nico Williams wrote:

> Oh, well, this is just outdated text.  And indeed, the GSS-API's
> notion of "qop" (quality of protection) is broken: it's used in the
> wrong place (per-msg token functions).  The GSS qop brokenness is why
> this text persists.
>
[snip]
>
> NEW:
>   1 == number of pseudo flavor
>   2 == name of pseudo flavor
>   3 == mechanism's OID
>   4 == qop
>   5 == RPCSEC_GSS service
>
>   1      2     3                    4             5
>   --------------------------------------------------------------------
>   390003 krb5  1.2.840.113554.1.2.2 0   rpc_gss_svc_none
>   390004 krb5i 1.2.840.113554.1.2.2 0   rpc_gss_svc_integrity
>   390005 krb5p 1.2.840.113554.1.2.2 0   rpc_gss_svc_privacy
>
> Actually, I should also propose some text explaining why qop is a
> busted concept and what qop 0 means ("default").

The table in RFC 5661 also includes columns for whether the flavor is 
mandatory for clients and servers, but it looks like they are now always 
mandatory and those columns are not needed.

In combination with Tom's proposed changes, this table should work well.
Agreed that some text about what qop 0 means is needed.


> KITTEN WG should undertake an extension to replace the broken qop concept.

I worry that such an undertaking would degenerate into a full GSS-API 
rewrite, but regardless that's out of scope for the current discussion.


Thanks for the updates,

Ben

From nico@cryptonector.com  Thu Apr  4 11:50:57 2013
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA8221F8D40; Thu,  4 Apr 2013 11:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8IbXi2z0CAHp; Thu,  4 Apr 2013 11:50:57 -0700 (PDT)
Received: from homiemail-a86.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id 26DD021F8D1C; Thu,  4 Apr 2013 11:50:57 -0700 (PDT)
Received: from homiemail-a86.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTP id 7811C36007C; Thu,  4 Apr 2013 11:50:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=yQzikiiRZQ28Q3cggg6w 9L1F3vo=; b=ierx04cCAY+sR7zonCafRR8tVZ/qyhYrxB0+J/hydq5+ah/RQtnK JeedkF9zAiNu8VFNP/RUJAvxDCBhfObbDP93gvJxSouSdoDks73MQ5eeEEg28yWW KmSzhw+RH5Yr2Se28aSnlp98Cx+ElabWZBSGMkjTAj3YMoNU5+VpYbI=
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a86.g.dreamhost.com (Postfix) with ESMTPSA id 1C25F360014;  Thu,  4 Apr 2013 11:50:52 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id k13so3130431wgh.5 for <multiple recipients>; Thu, 04 Apr 2013 11:50:51 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.11.70 with SMTP id o6mr11523044wjb.29.1365101451215; Thu, 04 Apr 2013 11:50:51 -0700 (PDT)
Received: by 10.217.105.195 with HTTP; Thu, 4 Apr 2013 11:50:51 -0700 (PDT)
In-Reply-To: <alpine.GSO.1.10.1304041234320.9389@multics.mit.edu>
References: <20130319142244.19905.39903.idtracker@ietfa.amsl.com> <alpine.GSO.1.10.1303312327530.9389@multics.mit.edu> <830AD203-2C2A-428F-A952-08B8F5A727E9@netapp.com> <alpine.GSO.1.10.1304041234320.9389@multics.mit.edu>
Date: Thu, 4 Apr 2013 13:50:51 -0500
Message-ID: <CAK3OfOgmO+zqNEwyzcgnVYiGBvPbq3Ka5BxNPFp-f0K-1uLhLw@mail.gmail.com>
Subject: Re: [nfsv4] Last Call: <draft-ietf-nfsv4-rfc3530bis-25.txt> (Network File System (NFS) Version 4 Protocol) to Proposed Standard
From: Nico Williams <nico@cryptonector.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Fri, 05 Apr 2013 08:35:57 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, nfsv4 list <nfsv4@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Apr 2013 18:50:57 -0000

On Thu, Apr 4, 2013 at 12:36 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> In combination with Tom's proposed changes, this table should work well.

I agree.

> Agreed that some text about what qop 0 means is needed.

I yes.  Indeed, maybe we should even remove the qop column and state
that we always use qop 0 unless otherwise stated (and we'll not state
otherwise).

>> KITTEN WG should undertake an extension to replace the broken qop concept.
>
> I worry that such an undertaking would degenerate into a full GSS-API
> rewrite, but regardless that's out of scope for the current discussion.

I don't think so.  We've discussed it [since] on IRC, and it's not
relevant here so I'll not burden the cc'ed with it.  I'll bring
something to KITTEN WG about this *after* the interim meeting that's
coming up, but NFSv4 WG should not wait for it.

Nico
--

From bob.hinden@gmail.com  Fri Apr  5 09:42:22 2013
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 8CECB21F9802 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 09:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.952
X-Spam-Level: 
X-Spam-Status: No, score=-99.952 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8FgD5Th2RE3 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 09:42:22 -0700 (PDT)
Received: from mail-bk0-x235.google.com (mail-bk0-x235.google.com [IPv6:2a00:1450:4008:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id E293321F97F8 for <ietf@ietf.org>; Fri,  5 Apr 2013 09:42:21 -0700 (PDT)
Received: by mail-bk0-f53.google.com with SMTP id e19so2225982bku.12 for <ietf@ietf.org>; Fri, 05 Apr 2013 09:42:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=NNj/wqU9SrTrx+5mUXqRtirgF2CLSgEPc/3Ml+WQnhE=; b=ftSDiAWKpryXGUkOYt/Qg8IE+rDIbJvtVXX3tXoEQN7TORfEpjOc96DTJckdfNu1a9 yxuo+/+FIjw5RymEwLNT0TAO/+5EDNCpShVxSuW8qPWH/HQpIFjf3vNHTAmLKhukVEiq iExSv0iqLTRJUQ/JtIv5DW3rZvD/4GT3dfwlBeiEaRJOdV8lZfd9P3l+QVc76DAnV3wm oVDUH/jHIaFw8EFQLCT9yJNhJMVO+mXSG8R64Wg8yIosa2ZushMEI/W516ozEcQliwrK oivbteJNz7YHo2R0luQKj6hVXaWbpMiguFRPvgfojwYLly6wp9p54LHNNCgprUh3z6Fu +Fhg==
X-Received: by 10.205.123.138 with SMTP id gk10mr7192967bkc.49.1365180140971;  Fri, 05 Apr 2013 09:42:20 -0700 (PDT)
Received: from [10.0.0.35] (c-24-130-151-138.hsd1.ca.comcast.net. [24.130.151.138]) by mx.google.com with ESMTPS id u4sm8700335bkz.20.2013.04.05.09.42.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Apr 2013 09:42:19 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <515E8FA9.1030901@pi.nu>
Date: Fri, 5 Apr 2013 09:42:15 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <AF86DE0B-19E0-4307-9D04-49FFBD06EF56@gmail.com>
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com> <515E8FA9.1030901@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1503)
Cc: Bob Hinden <bob.hinden@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: Fri, 05 Apr 2013 16:42:22 -0000

Loa,

On Apr 5, 2013, at 1:47 AM, Loa Andersson <loa@pi.nu> wrote:

> Bob,
> 
> thinking about this and assuming that the FTL Communication are deployed
> in a not too far distant future, wouldn't we have started to receive
> packets that was sent in the future already now?

See Section 5.  It may be already be happening...

Bob



From wbeebee@cisco.com  Fri Apr  5 10:12:48 2013
Return-Path: <wbeebee@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 4438E21F97EB for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 10:12:48 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lii5ui+DJx3P for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 10:12:47 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 92A4921F97EA for <ietf@ietf.org>; Fri,  5 Apr 2013 10:12:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=814; q=dns/txt; s=iport; t=1365181967; x=1366391567; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=rai2WukVCWRKd+WeAAZJFExR2Bmb1qrYp+HA36wiQEc=; b=GwhSsW8GENkzJXfJCEcetMkcYfCz0IVxSJepepX++N4LcpvfmezsTaop fuXyj60JXtaz1Tz7wDOPvG5Vb3pgzPgdjSo7aL/eTxtxsEYLTuEuuMf4b qr1X3t3aRK9/6K/mQ23sNSXo3ppnpzJZS0aqSkcez6MOU6nmhyJg9OIUO A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjkFAMoFX1GtJV2c/2dsb2JhbABLgwaDGL4/gQ0WdIIhAQQ6PxIBCCIUQiUCBAENBQgMiADBYY5qMQeCX2EDp3uDC4FqBTk
X-IronPort-AV: E=Sophos;i="4.87,415,1363132800"; d="scan'208";a="195542562"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP; 05 Apr 2013 17:12:35 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r35HCYPt022885 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 5 Apr 2013 17:12:34 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.192]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Fri, 5 Apr 2013 12:12:34 -0500
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'Dave Cridland'" <dave@cridland.net>, "'Loa Andersson'" <loa@pi.nu>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Topic: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Index: AQHOMiDD8cENHTet70KJzG3FvVNA/g==
Date: Fri, 5 Apr 2013 17:12:34 +0000
Message-ID: <9515564336C5B442A00021645539CFCC28A0AC7A@xmb-rcd-x08.cisco.com>
In-Reply-To: <01de01ce31dd$a7b36b50$f71a41f0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [10.131.71.105]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0063666424650042A39FC00EC99D5CD3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'Bob Hinden' <bob.hinden@gmail.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, 05 Apr 2013 17:12:48 -0000

Or use the FTL to predict the company stock price so that you get rich
without
implementing anything.

- Wes

On 4/5/13 5:12 AM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

>So instead of asking the community "do you have an intention to implement
>and
>deploy?" we should ask "have you already been going to have implemented
>and
>deployed yet?"
>
>>> thinking about this and assuming that the FTL Communication are
>>> deployed in a not too far distant future, wouldn't we have started
>>> to receive packets that was sent in the future already now?
>>
>> Indeed, and this tells us that publication of this was important,
>> since we'll need to be in a position to handle the issues that will
>> occur much sooner than deployment, and for that matter
>> development of the technology.
>


From dhc@dcrocker.net  Fri Apr  5 10:48:01 2013
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 27F6E21F9871 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 10:48:01 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oc+ciUBeX2AS for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 10:48:00 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7C27C21F9868 for <ietf@ietf.org>; Fri,  5 Apr 2013 10:48:00 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r35HlxGX017967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 5 Apr 2013 10:48:00 -0700
Message-ID: <515F0E4B.3070107@dcrocker.net>
Date: Fri, 05 Apr 2013 10:47:55 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
References: <20130401215830.710ADB1E007@rfc-editor.org> <CADnDZ88CPZ0YTbZue-=Rs0UEEocEjf376Y4s1f9j6YLQfMYkog@mail.gmail.com> <5EF5988B-04A4-4944-81CF-CC93B546C9F5@gmail.com> <515E8FA9.1030901@pi.nu> <8473.1365170326@sandelman.ca>
In-Reply-To: <8473.1365170326@sandelman.ca>
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, 05 Apr 2013 10:48:00 -0700 (PDT)
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: Fri, 05 Apr 2013 17:48:01 -0000

On 4/5/2013 6:58 AM, Michael Richardson wrote:
> "Loa" == Loa Andersson <loa@pi.nu> writes:
>> thinking about this and assuming that the FTL Communication are
>> deployed Loa in a not too far distant future, wouldn't we have
>> started to receive Loapackets that was sent in the future already
>> now?
 >
> I for one, have always found these Crocker brothers suspicious:

wtf?  Is this some sort of demonstration that the IETF has its own
variation of Godwin's Law at work?



> I think that they are in fact a single person.

> On 4/5/2013 7:09 AM, Steve Crocker wrote:> I too have always found at
> least one of the Crocker brothers {suspicious, smart, funny,
> irrelevant, prescient, handsome, annoying, etc.}. I've never been
> able to tell which is which :)

I usually can.


But given the context, I'm reminded of a brief exchange I had many years 
ago with Steve:

      I'd just read Azimov's "The Last Question"[*] which was about 
Azimov's ultimate computer, Multivac, taking eons to consider the 
question "can entropy be reversed?"  The story is a series of snapshots, 
with that generation's version of Multivac always concluding that it 
doesn't yet have enough information but it will continue to consider 
this interesting question.  At the end, with humanity long gone and it's 
own existence continuing only for considering the question it uses its 
last metaphysical ounce of energy, to say/think/whatever: Let there be 
light!

     Steve said he didn't like that ending.  Instead, he said, he'd have 
had the computer say/think/whatever: No.

d/

[*] http://en.wikipedia.org/wiki/The_Last_Question
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From housley@vigilsec.com  Fri Apr  5 11:14:55 2013
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 267B121F988A for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 11:14:55 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xwlgqdEBF3mq for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 11:14:54 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 992E821F986A for <ietf@ietf.org>; Fri,  5 Apr 2013 11:14:54 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 35B7CF2406D for <ietf@ietf.org>; Fri,  5 Apr 2013 14:14: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 Dy1QBIDARGXk for <ietf@ietf.org>; Fri,  5 Apr 2013 14:14:51 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 7378DF2406F for <ietf@ietf.org>; Fri,  5 Apr 2013 14:14:53 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: (Former) IETF Chair Interview
Date: Fri, 5 Apr 2013 14:14:51 -0400
Message-Id: <6C8D03FE-1228-4E7C-BAF3-ACCB6FD7BED7@vigilsec.com>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
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, 05 Apr 2013 18:14:55 -0000

This was recorded in January 2013, when I was the IETF Chair.  It was =
not released until March 20th, when I was no longer IETF Chair

It is 15 minutes.  It is not aimed at a technical crowd.

Russ=

From housley@vigilsec.com  Fri Apr  5 11:17:51 2013
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 54A6921F989C for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 11:17:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ONU5VI2zVOQo for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 11:17:50 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id B941C21F9898 for <ietf@ietf.org>; Fri,  5 Apr 2013 11:17:50 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 03507F2406D for <ietf@ietf.org>; Fri,  5 Apr 2013 14:17:53 -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 PqhNLwyorIaB for <ietf@ietf.org>; Fri,  5 Apr 2013 14:17:49 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id EFBF4F2406B for <ietf@ietf.org>; Fri,  5 Apr 2013 14:17:51 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
Subject: Re: (Former) IETF Chair Interview
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6C8D03FE-1228-4E7C-BAF3-ACCB6FD7BED7@vigilsec.com>
Date: Fri, 5 Apr 2013 14:17:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9042284C-5B76-4FAF-93BD-1A2D4B8E746A@vigilsec.com>
References: <6C8D03FE-1228-4E7C-BAF3-ACCB6FD7BED7@vigilsec.com>
To: IETF <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, 05 Apr 2013 18:17:51 -0000

http://www.youtube.com/watch?v=3DCH65RbOSrZ8


On Apr 5, 2013, at 2:14 PM, Russ Housley wrote:

> This was recorded in January 2013, when I was the IETF Chair.  It was =
not released until March 20th, when I was no longer IETF Chair
>=20
> It is 15 minutes.  It is not aimed at a technical crowd.
>=20
> Russ


From yaronf.ietf@gmail.com  Fri Apr  5 13:27:31 2013
Return-Path: <yaronf.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 0DB4821F98F3 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 13:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.891
X-Spam-Level: 
X-Spam-Status: No, score=-101.891 tagged_above=-999 required=5 tests=[AWL=1.708, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VROiBsn4YLyq for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 13:27:30 -0700 (PDT)
Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) by ietfa.amsl.com (Postfix) with ESMTP id 4E89621F98ED for <ietf@ietf.org>; Fri,  5 Apr 2013 13:27:30 -0700 (PDT)
Received: by mail-ee0-f43.google.com with SMTP id e50so1505903eek.30 for <ietf@ietf.org>; Fri, 05 Apr 2013 13:27:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-forwarded-message-id:content-type :content-transfer-encoding; bh=GbR5Q9gTdViOt9m1lYPL60TI5tmfgN9TG1FSz4XZ2dY=; b=m+tS0418Ct8rYNBC+nqW9MCvt1146qY/3cP2xLIYoJ+ZhigC9mE/TV//91MvAuFhrJ ZhyisNeSb9IHbLC+sxvepPzEndO7hMSpIq1olD71u0ynZNWKgEu4IVOdxAXnteQzw6kK qc36f5MehjCrBMjfGw+xqIxIUUA/qdyNNNA8z6HJm4+WSYCP7B2WF5A3iT9Y2zv59CTM Fi0SrFBVPTO6VkPs5djEZIOrzFvz8Q5jSNxsMKlLpVOWszs5BhhrOWrOtr9epaRO+wSM KrgKAvw098rzkcQ48axbuZTjjprfP/rDOb2PuLky7spLrqNZ3OB1CPVQsoGoQvF231OG 7OMA==
X-Received: by 10.15.21.1 with SMTP id c1mr22529429eeu.36.1365193649405; Fri, 05 Apr 2013 13:27:29 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-181-109-111.red.bezeqint.net. [79.181.109.111]) by mx.google.com with ESMTPS id cd3sm7632150eeb.6.2013.04.05.13.27.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 05 Apr 2013 13:27:28 -0700 (PDT)
Message-ID: <515F33AD.60508@gmail.com>
Date: Fri, 05 Apr 2013 23:27:25 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: draft-sheffer-running-code-03 published
References: <20130405194251.19607.86337.idtracker@ietfa.amsl.com>
In-Reply-To: <20130405194251.19607.86337.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20130405194251.19607.86337.idtracker@ietfa.amsl.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: Fri, 05 Apr 2013 20:27:31 -0000

Hi,

we have just published a new revision of this draft, defining a new, 
optional Implementation Status section to be included in Internet 
Drafts: http://tools.ietf.org/html/draft-sheffer-running-code-03

We believe this document is almost ready for IETF last call; in fact 
this idea has already been adopted by a few I-D authors. Any comments 
would be appreciated.

Thanks,
	Yaron

From dave@cridland.net  Fri Apr  5 13:59:54 2013
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 F1DFC21F98D7 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 13:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Co4p2bMIQwrk for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 13:59:53 -0700 (PDT)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id CA60421F98D6 for <ietf@ietf.org>; Fri,  5 Apr 2013 13:59:53 -0700 (PDT)
Received: by mail-ob0-f177.google.com with SMTP id uz6so4150930obc.36 for <ietf@ietf.org>; Fri, 05 Apr 2013 13:59:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=32tjj+vsQIGjrHD/Qwb5nbyu1SQYFKWomsi3GH0JFio=; b=M69AN+BJ6XXg21g3rwyS5C7yRzz6FJrtogaEmrsSOpWVA12fqT/FCCNozGR8z/TCQ2 5tcTnvIC0laGmPeXmauoosHtQTP7O2Cm4APtcx3bQIqtoUt1jwJVa9/5yrAeZn7GqFK9 CoDKbsSE+iFdoVxvEhBPVaSOdZ0yYwTbLudPI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=32tjj+vsQIGjrHD/Qwb5nbyu1SQYFKWomsi3GH0JFio=; b=H1fwijgGVwjRyKda4fekVf4Cw4Gj6lzjjcupNqF4vFcvJsTm4HRkDGsoaXb2umgOSd 71vmyKD7FXTbxw8s+RYB0lPcna6b1zlJQ4tBpHLOVhofd7wjfl3bEi16vvRmBTq5eODn edJQiUN78f//rdPCtxT3uAK95kokC//6T4x2PmNKf00xGRFU9shFybsiHKq6/Q8Htk8s vWv6t4TKmWzDzYipW4atB0OirPmQniivM2ZbBkVTbd4oOHf1AwKbfGyiIXpCj5j9Qs0O csCNw31tgQ/edYdpskQT67NmW5/zDQ9lfDf783MdrjQwRh/FBNY2eoU3+fiAe5sjdxO4 DvZw==
MIME-Version: 1.0
X-Received: by 10.182.157.104 with SMTP id wl8mr9317425obb.79.1365195593354; Fri, 05 Apr 2013 13:59:53 -0700 (PDT)
Received: by 10.60.22.105 with HTTP; Fri, 5 Apr 2013 13:59:53 -0700 (PDT)
In-Reply-To: <9515564336C5B442A00021645539CFCC28A0AC7A@xmb-rcd-x08.cisco.com>
References: <01de01ce31dd$a7b36b50$f71a41f0$@olddog.co.uk> <9515564336C5B442A00021645539CFCC28A0AC7A@xmb-rcd-x08.cisco.com>
Date: Fri, 5 Apr 2013 21:59:53 +0100
Message-ID: <CAKHUCzzUXPoXjJ3PfU2aXe08hL65EdeNzch9vLXLuLPyWoFAnw@mail.gmail.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
From: Dave Cridland <dave@cridland.net>
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
Content-Type: multipart/alternative; boundary=f46d044281a064485404d9a35e3b
X-Gm-Message-State: ALoCoQma73mkqOIgpIZj4LyML1WcXoNUmkj860LIFQI4kY5qpj2Kx67ew/cjvkZaaFEP9wYTMYLj
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Bob Hinden <bob.hinden@gmail.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, 05 Apr 2013 20:59:55 -0000

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

Actually, getting rich without implementing anything seems to happen quite
often enough these days - it's called acquisition.


On Fri, Apr 5, 2013 at 6:12 PM, Wes Beebee (wbeebee) <wbeebee@cisco.com>wrote:

> Or use the FTL to predict the company stock price so that you get rich
> without
> implementing anything.
>
> - Wes
>
> On 4/5/13 5:12 AM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>
> >So instead of asking the community "do you have an intention to implement
> >and
> >deploy?" we should ask "have you already been going to have implemented
> >and
> >deployed yet?"
> >
> >>> thinking about this and assuming that the FTL Communication are
> >>> deployed in a not too far distant future, wouldn't we have started
> >>> to receive packets that was sent in the future already now?
> >>
> >> Indeed, and this tells us that publication of this was important,
> >> since we'll need to be in a position to handle the issues that will
> >> occur much sooner than deployment, and for that matter
> >> development of the technology.
> >
>
>

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

<div dir=3D"ltr">Actually, getting rich without implementing anything seems=
 to happen quite often enough these days - it&#39;s called acquisition.</di=
v><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Apr=
 5, 2013 at 6:12 PM, Wes Beebee (wbeebee) <span dir=3D"ltr">&lt;<a href=3D"=
mailto:wbeebee@cisco.com" target=3D"_blank">wbeebee@cisco.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">Or use the FTL to predict the company stock =
price so that you get rich<br>
without<br>
implementing anything.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
- Wes<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On 4/5/13 5:12 AM, &quot;Adrian Farrel&quot; &lt;<a href=3D"mailto:adrian@o=
lddog.co.uk">adrian@olddog.co.uk</a>&gt; wrote:<br>
<br>
&gt;So instead of asking the community &quot;do you have an intention to im=
plement<br>
&gt;and<br>
&gt;deploy?&quot; we should ask &quot;have you already been going to have i=
mplemented<br>
&gt;and<br>
&gt;deployed yet?&quot;<br>
&gt;<br>
&gt;&gt;&gt; thinking about this and assuming that the FTL Communication ar=
e<br>
&gt;&gt;&gt; deployed in a not too far distant future, wouldn&#39;t we have=
 started<br>
&gt;&gt;&gt; to receive packets that was sent in the future already now?<br=
>
&gt;&gt;<br>
&gt;&gt; Indeed, and this tells us that publication of this was important,<=
br>
&gt;&gt; since we&#39;ll need to be in a position to handle the issues that=
 will<br>
&gt;&gt; occur much sooner than deployment, and for that matter<br>
&gt;&gt; development of the technology.<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div>

--f46d044281a064485404d9a35e3b--

From jmpolk@cisco.com  Fri Apr  5 16:13:08 2013
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 8727A21F98A4 for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 16:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.166
X-Spam-Level: 
X-Spam-Status: No, score=-110.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3U9bN99o2ew for <ietf@ietfa.amsl.com>; Fri,  5 Apr 2013 16:13:07 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id CCC3F21F9050 for <ietf@ietf.org>; Fri,  5 Apr 2013 16:13:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1200; q=dns/txt; s=iport; t=1365203587; x=1366413187; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=A7UarMH4zs22X+3kFsGJezoqPmnuCw0+kx+l1OuxrpM=; b=SV5/lEwR+hh51DjW0Be0H77Id143tuONCb/S3tovFW6Pao8p8HvI2oA6 pCHn8z7wm+rOGHtbQD85h2XjKE+o/PVGvDJBpZNinTAYwueBy5j6d98EQ 8u4DhKVcPwGIgdyQ+RMwSBN/QBYGJUT7K49qCNjSiOTuJX74EQbEcU+8y s=;
X-IronPort-AV: E=Sophos;i="4.87,418,1363132800"; d="scan'208";a="195606833"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP; 05 Apr 2013 23:13:06 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r35ND6kL027589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Apr 2013 23:13:06 GMT
Message-Id: <201304052313.r35ND6kL027589@rcdn-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 05 Apr 2013 18:11:57 -0500
To: Dave Cridland <dave@cridland.net>, "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
From: James Polk <jmpolk@cisco.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
In-Reply-To: <CAKHUCzzUXPoXjJ3PfU2aXe08hL65EdeNzch9vLXLuLPyWoFAnw@mail.g mail.com>
References: <01de01ce31dd$a7b36b50$f71a41f0$@olddog.co.uk> <9515564336C5B442A00021645539CFCC28A0AC7A@xmb-rcd-x08.cisco.com> <CAKHUCzzUXPoXjJ3PfU2aXe08hL65EdeNzch9vLXLuLPyWoFAnw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, Bob Hinden <bob.hinden@gmail.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, 05 Apr 2013 23:13:08 -0000

At 03:59 PM 4/5/2013, Dave Cridland wrote:
>Actually, getting rich without implementing anything seems to happen 
>quite often enough these days - it's called acquisition.

or be a Kardashian



>On Fri, Apr 5, 2013 at 6:12 PM, Wes Beebee (wbeebee) 
><<mailto:wbeebee@cisco.com>wbeebee@cisco.com> wrote:
>Or use the FTL to predict the company stock price so that you get rich
>without
>implementing anything.
>
>- Wes
>
>On 4/5/13 5:12 AM, "Adrian Farrel" 
><<mailto:adrian@olddog.co.uk>adrian@olddog.co.uk> wrote:
>
> >So instead of asking the community "do you have an intention to implement
> >and
> >deploy?" we should ask "have you already been going to have implemented
> >and
> >deployed yet?"
> >
> >>> thinking about this and assuming that the FTL Communication are
> >>> deployed in a not too far distant future, wouldn't we have started
> >>> to receive packets that was sent in the future already now?
> >>
> >> Indeed, and this tells us that publication of this was important,
> >> since we'll need to be in a position to handle the issues that will
> >> occur much sooner than deployment, and for that matter
> >> development of the technology.
> >
>


From peter@akayla.com  Fri Apr  5 16:55:06 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F0F21F990A; Fri,  5 Apr 2013 16:55:06 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qFTRGISOl25s; Fri,  5 Apr 2013 16:55:05 -0700 (PDT)
Received: from p3plsmtpa09-06.prod.phx3.secureserver.net (p3plsmtpa09-06.prod.phx3.secureserver.net [173.201.193.235]) by ietfa.amsl.com (Postfix) with ESMTP id C052921F9907; Fri,  5 Apr 2013 16:55:05 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-06.prod.phx3.secureserver.net with  id LPv41l0031huGat01Pv4RV; Fri, 05 Apr 2013 16:55:05 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-intarea-nat-reveal-analysis.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-intarea-nat-reveal-analysis-06
Date: Fri, 5 Apr 2013 16:56:18 -0700
Message-ID: <030101ce3259$2b900520$82b00f60$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac4yVqRs/Mt47fa6QWSvsgPU2PDQHw==
Content-Language: en-us
Cc: gen-art@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, 05 Apr 2013 23:55:06 -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-intarea-nat-reveal-analysis-06
Reviewer: Peter Yee
Review Date: Apr-5-2013
IETF LC End Date: Mar-8-2013
IESG Telechat date: Apr-11-2013

This draft is basically ready for publication, but has nits that should =
be fixed before publication. [Ready with nits]

It addresses most of the issues raised in my review of the -05 version.  =
Two items from that review that I'm
revisiting are noted below with text from the original review and =
responses from one of the authors (Med).
We agreed that those two revisited items could be addressed in a =
subsequent revision; they are just
recorded here for ease of reference.

Major issues:

Minor issues:

Nits:

[Old]

>>Section 3.1, 5th paragraph: I don't quite follow what's being said =
here.
>>Is the point that the address-sharing function should reveal the same=20
>>HOST_ID for any given host regardless of what layer or mechanism that=20
>>HOST_ID is being conveyed across?  How does this relate to=20
>>interference between HOST_IDs?

>Med: The point is: when several layers are used to inject a host_id, =
the device should check the same subset of information is revealed. For =
instance, there should not be conflict, etc.

Then perhaps you could reword so that "should reveal subsets of the same =
information" becomes "should reveal the same subsets of information at =
each layer"?

>>Section 4.9.2, 4th bullet item, 2nd sentence: Delete "heavy and" =
unless you want to=20
>>explain what heavy means.

>Med: Establishing agreements with the owner of the address sharing =
function and owners of servers is heavy. This is already mentioned in =
the text.

Perhaps you could replace "heavy" with "burdensome".

[New]

In the references, there seem to be an excess of commas in a couple of =
places.   Look for the string ", ," (comma space comma) and you'll see =
what I mean.  The document titles start with an extra comma and end with =
one.

Also in the references, for RFC 1413, put a space between the "M." and =
the "C." in Mike St. Johns' initials.



From ron.even.tlv@gmail.com  Sat Apr  6 00:10:09 2013
Return-Path: <ron.even.tlv@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 0D73A21F93C7; Sat,  6 Apr 2013 00:10:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.181
X-Spam-Level: 
X-Spam-Status: No, score=-2.181 tagged_above=-999 required=5 tests=[AWL=1.417,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iv2mvnvshxKT; Sat,  6 Apr 2013 00:10:07 -0700 (PDT)
Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com [74.125.83.43]) by ietfa.amsl.com (Postfix) with ESMTP id 34B5921F938E; Sat,  6 Apr 2013 00:10:07 -0700 (PDT)
Received: by mail-ee0-f43.google.com with SMTP id e50so1651953eek.16 for <multiple recipients>; Sat, 06 Apr 2013 00:10:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=Zu49OIjZ+HeCQPPngKG0z4uEQqcXLMfItX9GcU11EUQ=; b=JRuzEMV7OlwXYy2EaAFJl6+09r7CpqrmpJuop+5NKQozPEU2HtpXaiyuiboiGXM4hw LAqSX1GKX/3NYE/mMqfRLP1I8B0rkIai2goGpDXAe2IIh5Ps6TYtZHEZWPaSkSqFajiO FkgKqoL9LMX9XojTbg4EKTM+HauYFx6unpWSUCGysgn13QfWPPTd+097L82xaSjmtGGd No9CDjuHzjUGjLr23VvzZ6jrGo/dO5mstu3Sz0kUYbzfSboY6oPoDSb+l13sarxIS1UG Q/k52wvCCQ8LKK0a4Gl47KjyifZFD/Hdmaqq9YO5t2K9TSYN5X9KKqp3+GTrU50Zjq5M iqBw==
X-Received: by 10.14.39.5 with SMTP id c5mr18035664eeb.27.1365232206108; Sat, 06 Apr 2013 00:10:06 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPS id s47sm19329822eeg.8.2013.04.06.00.10.03 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 06 Apr 2013 00:10:05 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets.all@ietf.tools.org>, <ietf@ietf.org>
Subject: Gen-ART LC review of draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03
Date: Sat, 6 Apr 2013 10:09:38 +0300
Message-ID: <01f201ce3295$b5a1aa70$20e4ff50$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01F3_01CE32AE.DAEFCCD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac4ylbNrszEEef+vS7Gk5rMUmr+arQ==
Content-Language: en-us
Cc: gen-art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Apr 2013 07:10:09 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01F3_01CE32AE.DAEFCCD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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-opsec-ipv6-implications-on-ipv4-nets-03

Reviewer: Roni Even

Review Date:2013-4-6

IETF LC End Date: 2013-4-12

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Informational RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	I found this draft very informational but I was wondering if it will
be better to have in the introduction and the abstract a sentence that will
mention the target audience for this draft.

 


------=_NextPart_000_01F3_01CE32AE.DAEFCCD0
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-microsoft-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=3DGenerator 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:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:551036080;
	mso-list-type:hybrid;
	mso-list-template-ids:-1333356038 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;4&#8211;6<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-4&#8211;12<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>I found =
this draft very informational but I was wondering if it will be better =
to have in the introduction and the abstract a sentence that will =
mention the target audience for this draft.<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_01F3_01CE32AE.DAEFCCD0--


From brian.e.carpenter@gmail.com  Sat Apr  6 00:21:21 2013
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 71BDC21F97C0 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 00:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.921
X-Spam-Level: 
X-Spam-Status: No, score=-98.921 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2AvcPmF88U3M for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 00:21:16 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF2821F96D7 for <ietf@ietf.org>; Sat,  6 Apr 2013 00:21:15 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id hj8so1208739wib.8 for <ietf@ietf.org>; Sat, 06 Apr 2013 00:21:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hG+Sa9Ft2umcE/8E64YwrfIyk3y+URve13P10cBdyaw=; b=th3i9Qek0c2FgaAi1DbrSrKNwSoHnaZlbpgs+Qj9ZC7/e3vB+mkA0rQyXEvGhHyw3M GRZMj0CQHwYR0+PTG3LZUM1qRY5NO1Te2RSqYvbsf+JDafSKIJdFuG6C5FzN6saN1RKZ 7QemrPcoA4FpHM30lizsHPa1mpeTP5X/0G9sGDzQHQ+GumqliAF2O3VG7ygIJpkg0GJR yw6jEcX862zDgtEr1BVKurD7zq6SKW/TOJ2l7yBQJ7mMUzSl5bKhY1PCcdtef7gbIptl GA603QBCKg6rSbhhk1up6tthXsCnblxsLus7wxlQSohwdecoVZZdoazr1+fHPoHzqvxy cAKw==
X-Received: by 10.194.222.3 with SMTP id qi3mr21010316wjc.28.1365232874492; Sat, 06 Apr 2013 00:21:14 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-189-39.as13285.net. [2.101.189.39]) by mx.google.com with ESMTPS id ed6sm8566156wib.9.2013.04.06.00.21.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 06 Apr 2013 00:21:13 -0700 (PDT)
Message-ID: <515FCCF5.7060800@gmail.com>
Date: Sat, 06 Apr 2013 08:21:25 +0100
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: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
References: <9515564336C5B442A00021645539CFCC28A0AC7A@xmb-rcd-x08.cisco.com>
In-Reply-To: <9515564336C5B442A00021645539CFCC28A0AC7A@xmb-rcd-x08.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 'Bob Hinden' <bob.hinden@gmail.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: Sat, 06 Apr 2013 07:21:21 -0000

On 05/04/2013 18:12, Wes Beebee (wbeebee) wrote:
> Or use the FTL to predict the company stock price so that you get rich
> without implementing anything.

That's terrible for the IETF. It completely nullifies the NomCom
random selection process; all the suggestions in RFC 3797 seem
to be blown away by this.

   Brian

From ron.even.tlv@gmail.com  Sat Apr  6 03:44:18 2013
Return-Path: <ron.even.tlv@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 CB30D21F8C03; Sat,  6 Apr 2013 03:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.223
X-Spam-Level: 
X-Spam-Status: No, score=-0.223 tagged_above=-999 required=5 tests=[AWL=-0.894, BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, DYN_RDNS_SHORT_HELO_HTML=0.499, FH_HOST_EQ_D_D_D_D=0.765, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQwUZ5SDxBkn; Sat,  6 Apr 2013 03:44:18 -0700 (PDT)
Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABB021F8BEB; Sat,  6 Apr 2013 03:44:17 -0700 (PDT)
Received: by mail-ea0-f171.google.com with SMTP id b15so1659845eae.2 for <multiple recipients>; Sat, 06 Apr 2013 03:44:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=+Gk8IyAnvRf1MV1HS22URGBmAgw6AEvRgx7sP4GdSgI=; b=jQCCMcp5LZLq3PV1eIm90p3ScKOHi2XprZTvS4HjJPgRre44jZk/pEIno+oHPiajlP UsWZt3+f64aJoeYXSDxTEdMSi20n/gRdXGkD++faeuxQoVSW7pqANe6N8mrHWyWqz1Dy WCuTskTwHtJgx0ea4BzZcBOK3VdPobwFX+SLCbP3kDVrW+e6/yT96tEbz8iDhsWZbIjc HyzshO4jRc44ycmeEAUM29uPVjQJE6g2NVVXvDZiSWURfb0DxTr4a5w2Zajk42PL+a21 73jD370HcPx7/R6h2MuDI/jf00fXFtt2ojSKZxbIgKl9xCHYtttyYaOY4CQ6YG2ryF11 uYqg==
X-Received: by 10.14.39.5 with SMTP id c5mr19649797eeb.27.1365245056295; Sat, 06 Apr 2013 03:44:16 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPS id s47sm20232439eeg.8.2013.04.06.03.44.11 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 06 Apr 2013 03:44:15 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <ietf@ietf.org>, <draft-ietf-opsec-ipv6-implications-on-ipv4-nets.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03
Date: Sat, 6 Apr 2013 13:43:43 +0300
Message-ID: <020001ce32b3$a06aed60$e140c820$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0201_01CE32CC.C5B8C1A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac4ylbNrszEEef+vS7Gk5rMUmr+arQ==
Content-Language: en-us
Cc: gen-art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Apr 2013 10:44:19 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0201_01CE32CC.C5B8C1A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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-opsec-ipv6-implications-on-ipv4-nets-03

Reviewer: Roni Even

Review Date:2013-4-6

IETF LC End Date: 2013-4-12

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Informational RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	I found this draft very informational but I was wondering if it will
be better to have in the introduction and the abstract a sentence that will
mention the target audience for this draft.

 


------=_NextPart_000_0201_01CE32CC.C5B8C1A0
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-microsoft-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=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator 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:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:486477111;
	mso-list-template-ids:1580108680;}
@list l1
	{mso-list-id:551036080;
	mso-list-type:hybrid;
	mso-list-template-ids:-1333356038 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned =
Gen-ART reviewer for this draft. For background on Gen-ART, please see =
the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;4&#8211;6<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-4&#8211;12<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo3'>I found =
this draft very informational but I was wondering if it will be better =
to have in the introduction and the abstract a sentence that will =
mention the target audience for this draft.<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0201_01CE32CC.C5B8C1A0--


From Ted.Lemon@nominum.com  Sat Apr  6 04:50:11 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D30CD21F8DB4 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 04:50:09 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Wk6Up830-S4 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 04:50:08 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 4761721F8BF4 for <ietf@ietf.org>; Sat,  6 Apr 2013 04:50:08 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUWAL8HWuHx6FnjysXjjE5uBCGxxdbMDS@postini.com; Sat, 06 Apr 2013 04:50:08 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E59A31B8A0F for <ietf@ietf.org>; Sat,  6 Apr 2013 04:50:07 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id DD16319005D; Sat,  6 Apr 2013 04:50:07 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sat, 6 Apr 2013 04:50:08 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Topic: RFC 6921 on Design Considerations for Faster-Than-Light (FTL) Communication
Thread-Index: AQHOMiDTWHU5cmOm4kWXN3oO2Ji+I5jJP8iAgABLE4A=
Date: Sat, 6 Apr 2013 11:50:06 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775134B22@mbx-01.win.nominum.com>
References: <9515564336C5B442A00021645539CFCC28A0AC7A@xmb-rcd-x08.cisco.com> <515FCCF5.7060800@gmail.com>
In-Reply-To: <515FCCF5.7060800@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <028AA77442DE164998D3B156110FCFDE@nominum.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: Sat, 06 Apr 2013 11:50:12 -0000

On Apr 6, 2013, at 3:21 AM, Brian E Carpenter <brian.e.carpenter@gmail.com>=
 wrote:
> That's terrible for the IETF. It completely nullifies the NomCom
> random selection process; all the suggestions in RFC 3797 seem
> to be blown away by this.

This seems like exactly the sort of problem that Jari's cross-area draft is=
 intended to address.


From abdussalambaryun@gmail.com  Sat Apr  6 06:03:36 2013
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 137B221F8BF4 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 06:03:36 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wl1JHUd4zVPJ for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 06:03:34 -0700 (PDT)
Received: from mail-pb0-f50.google.com (mail-pb0-f50.google.com [209.85.160.50]) by ietfa.amsl.com (Postfix) with ESMTP id B73D621F8E69 for <ietf@ietf.org>; Sat,  6 Apr 2013 06:03:23 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id jt11so2456693pbb.37 for <ietf@ietf.org>; Sat, 06 Apr 2013 06:03:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=d5DhpRKAV6pLo2OPEkC4q7pnSPbrbjaBvlIRHcXesD0=; b=FKoPws2QKWtrwIjEBQYHAk2qnMdP5pe4LYn20+btJoJ0LW1nG0qa79gINo3Kc9iBNk ko/I8hY8a/eWri+etMcXZSKr9oru/CqtU85tT1jYKNneMDNMZUpJYu2eEDlhpfD7EdKF R1isU6xVndgup6CQImJxiyaqyXnYb28OEhkAk2SwV+sU76kmXPtsa7IiDLIOl+aHdEJj qrF+fX8DKNUkvprIYK9SmunbhelsXDp8RfHIu/YIHtjUwFvJ6HejBfoNNTRxS8vvwrtA CO+sPRn3ZVxV3lTlrHTPizr+JOR2tP10rZv5jCg5dQrnOrJCJmb7SRmc5lqk/UDIFtdh 5p9g==
MIME-Version: 1.0
X-Received: by 10.66.222.228 with SMTP id qp4mr20351148pac.113.1365253403508;  Sat, 06 Apr 2013 06:03:23 -0700 (PDT)
Received: by 10.68.33.132 with HTTP; Sat, 6 Apr 2013 06:03:23 -0700 (PDT)
Date: Sat, 6 Apr 2013 15:03:23 +0200
Message-ID: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
Subject: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
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: Sat, 06 Apr 2013 13:03:36 -0000

<Unclassified Message, but not Humorous>

Some participants like to send messages/documents as categoried or
classified, and may include in others uncategorised or unclassified.
That is a reasonable approach in reasonable organisations.

I see some RFCs as mentioned in [1], that they are humorous that
reflect a historic culture or a behavior that some may like to do in a
certain date (others may not like to do or be part of). If the date is
special then thoes RFCs SHOULD be *historical*.

I suggest/request that the IETF stops this humorous RFC publication or
try to categories them or distinguish them from our logical
work/efforts. I request if they are categorised as informational or
experimental then to be obsoleted. I recommend for future RFCs of that
type categories to be as *historical* not others (i.e. informational).

 If those RFCs are not categorising/distinguished as unclassified or
humorous, then all RFC may be affected. The reader may not be able to
distinguish thoes published documents by IETF (does an organisation
care about readers or users of its publications!). You may think to
create a new category name for such publication published on April for
that interested culture behavior.

[1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC

Regards
AB

From dave@cridland.net  Sat Apr  6 07:08:24 2013
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 E731F21F8E62 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 07:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rs0gqfeZs4CA for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 07:08:24 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4BF21F8E48 for <ietf@ietf.org>; Sat,  6 Apr 2013 07:08:19 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wm15so1909929obc.5 for <ietf@ietf.org>; Sat, 06 Apr 2013 07:08:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6nKPOHv0hrGbWnUoGppJXvbCCkyWGoNnJLx0t1CCUG4=; b=e4TJ+fv8UQSIjHPezhpm7r1/mDFvL1IcjD9gFqbFfd/jTlBwgFJQyVtjbbwfinwrrq U43YS6+0jkeHitCM8SB2GQQijbitkjDa8RTh7EtxArQfPnyFFRQ2uPuJseWuiAzx8ZZP 0Bfpzij2b1gvuXgMuPczvDESprqocu334UWPA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=6nKPOHv0hrGbWnUoGppJXvbCCkyWGoNnJLx0t1CCUG4=; b=Ai43Ti2OqIPuBG75+sVQxzhThK56f7k7Y+Cx9S0uEXYFScxPeaFcoQLtRYgtWXupNF LWtJpAYCU/p1s8MxzPL/enkxI5CS9xJdUDUDn1cuCqPpIpjb2rrXonjgepH07bO748fD CfQh8MaTxpe+Z5Jb9KOFtIz9ExJcL1gZIG6S50HQat3pWjM8mf/eaICNsg8TRHEw4j22 Pehed8coBcWkwHJy3H8kCS8WKqg8W/7diF6ksjLPfGiZe45ZgBQ2AS4u2lIV2WggiQO/ ToD2zZwb9530RlCV8HN7ERx8P9bRSOBx8nQxCYijCzu1UlVdVSd5NcjzGjeD5bW+g5CI 1omw==
MIME-Version: 1.0
X-Received: by 10.182.34.165 with SMTP id a5mr10723690obj.70.1365257298950; Sat, 06 Apr 2013 07:08:18 -0700 (PDT)
Received: by 10.60.22.105 with HTTP; Sat, 6 Apr 2013 07:08:18 -0700 (PDT)
Received: by 10.60.22.105 with HTTP; Sat, 6 Apr 2013 07:08:18 -0700 (PDT)
In-Reply-To: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
Date: Sat, 6 Apr 2013 15:08:18 +0100
Message-ID: <CAKHUCzwBpvDE6FtmcTWGOWydKFhgZtcnw_gU0PA4DhPjiTDPOg@mail.gmail.com>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
From: Dave Cridland <dave@cridland.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2229854f8d804d9b1bc57
X-Gm-Message-State: ALoCoQnbKAca6cFE98uxl/D4TZYZfCFtbFECSLUwETz4BZB/OpgjZSoD4dqifJHPJv+4K30sOBs7
Cc: "ietf@ietf.org 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: Sat, 06 Apr 2013 14:08:25 -0000

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

These aren't published by the IETF, but by the RFC editor directly. As
such, the IETF has little control.

Even if this were not so, I would be very much against discontinuing or
specially marking such documents. I appreciate Mark Crispin was always
proud that his randomly lose telnet extension was marked 'note date of
issue', but that should remain the only one.

Humour is an important part of IETF culture, and long may it remain so.
Actively working to remove support for humour would be a very bad thing,
and marking it joylessly would drain it of any value.
On 6 Apr 2013 14:03, "Abdussalam Baryun" <abdussalambaryun@gmail.com> wrote:

> <Unclassified Message, but not Humorous>
>
> Some participants like to send messages/documents as categoried or
> classified, and may include in others uncategorised or unclassified.
> That is a reasonable approach in reasonable organisations.
>
> I see some RFCs as mentioned in [1], that they are humorous that
> reflect a historic culture or a behavior that some may like to do in a
> certain date (others may not like to do or be part of). If the date is
> special then thoes RFCs SHOULD be *historical*.
>
> I suggest/request that the IETF stops this humorous RFC publication or
> try to categories them or distinguish them from our logical
> work/efforts. I request if they are categorised as informational or
> experimental then to be obsoleted. I recommend for future RFCs of that
> type categories to be as *historical* not others (i.e. informational).
>
>  If those RFCs are not categorising/distinguished as unclassified or
> humorous, then all RFC may be affected. The reader may not be able to
> distinguish thoes published documents by IETF (does an organisation
> care about readers or users of its publications!). You may think to
> create a new category name for such publication published on April for
> that interested culture behavior.
>
> [1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>
> Regards
> AB
>

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

<p dir=3D"ltr">These aren&#39;t published by the IETF, but by the RFC edito=
r directly. As such, the IETF has little control.</p>
<p dir=3D"ltr">Even if this were not so, I would be very much against disco=
ntinuing or specially marking such documents. I appreciate Mark Crispin was=
 always proud that his randomly lose telnet extension was marked &#39;note =
date of issue&#39;, but that should remain the only one.</p>

<p dir=3D"ltr">Humour is an important part of IETF culture, and long may it=
 remain so. Actively working to remove support for humour would be a very b=
ad thing, and marking it joylessly would drain it of any value.</p>
<div class=3D"gmail_quote">On 6 Apr 2013 14:03, &quot;Abdussalam Baryun&quo=
t; &lt;<a href=3D"mailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail=
.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
&lt;Unclassified Message, but not Humorous&gt;<br>
<br>
Some participants like to send messages/documents as categoried or<br>
classified, and may include in others uncategorised or unclassified.<br>
That is a reasonable approach in reasonable organisations.<br>
<br>
I see some RFCs as mentioned in [1], that they are humorous that<br>
reflect a historic culture or a behavior that some may like to do in a<br>
certain date (others may not like to do or be part of). If the date is<br>
special then thoes RFCs SHOULD be *historical*.<br>
<br>
I suggest/request that the IETF stops this humorous RFC publication or<br>
try to categories them or distinguish them from our logical<br>
work/efforts. I request if they are categorised as informational or<br>
experimental then to be obsoleted. I recommend for future RFCs of that<br>
type categories to be as *historical* not others (i.e. informational).<br>
<br>
=A0If those RFCs are not categorising/distinguished as unclassified or<br>
humorous, then all RFC may be affected. The reader may not be able to<br>
distinguish thoes published documents by IETF (does an organisation<br>
care about readers or users of its publications!). You may think to<br>
create a new category name for such publication published on April for<br>
that interested culture behavior.<br>
<br>
[1] <a href=3D"http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC" target=
=3D"_blank">http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC</a><br>
<br>
Regards<br>
AB<br>
</blockquote></div>

--001a11c2229854f8d804d9b1bc57--

From warren@kumari.net  Sat Apr  6 07:26:24 2013
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 5A81221F8C83 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 07:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0ZQaO2yoAIn for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 07:26:23 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F0321F8C7D for <ietf@ietf.org>; Sat,  6 Apr 2013 07:26:22 -0700 (PDT)
Received: from [172.26.9.33] (unknown [65.114.129.62]) by vimes.kumari.net (Postfix) with ESMTPSA id 88F081B4030C; Sat,  6 Apr 2013 10:26:21 -0400 (EDT)
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
In-Reply-To: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <577E2C0B-16F5-47D2-8D71-7A9D914ACF23@kumari.net>
X-Mailer: iPhone Mail (10B329)
From: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated April the first
Date: Sat, 6 Apr 2013 10:26:21 -0400
To: Abdussalam Baryun <abdussalambaryun@gmail.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: Sat, 06 Apr 2013 14:26:24 -0000

On Apr 6, 2013, at 9:03 AM, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:

> <Unclassified Message, but not Humorous>
>=20
> Some participants like to send messages/documents as categoried or
> classified, and may include in others uncategorised or unclassified.
> That is a reasonable approach in reasonable organisations.
>=20
> I see some RFCs as mentioned in [1], that they are humorous that
> reflect a historic culture or a behavior that some may like to do in a
> certain date (others may not like to do or be part of). If the date is
> special then thoes RFCs SHOULD be *historical*.
>=20
> I suggest/request that the IETF stops this humorous RFC publication or
> try to categories them or distinguish them from our logical
> work/efforts. I request if they are categorised as informational or
> experimental then to be obsoleted. I recommend for future RFCs of that
> type categories to be as *historical* not others (i.e. informational).
>=20

-very, very, very lots.

I understand you may have missed the fact that an RFC was an April 1st, and a=
re grumpy now, but that's no reason to ruin things for the rest of us...

Try hacking protocol, not policy -- then folk may listen more to your propos=
als on things.


W


> If those RFCs are not categorising/distinguished as unclassified or
> humorous, then all RFC may be affected. The reader may not be able to
> distinguish thoes published documents by IETF (does an organisation
> care about readers or users of its publications!). You may think to
> create a new category name for such publication published on April for
> that interested culture behavior.
>=20
> [1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>=20
> Regards
> AB
>=20

From barryleiba.mailing.lists@gmail.com  Sat Apr  6 07:41:49 2013
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 1B5F921F8A85 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 07:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.885
X-Spam-Level: 
X-Spam-Status: No, score=-102.885 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00IZBtivq5iv for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 07:41:48 -0700 (PDT)
Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3F37D21F8AF8 for <ietf@ietf.org>; Sat,  6 Apr 2013 07:41:43 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id ox1so4269500veb.21 for <ietf@ietf.org>; Sat, 06 Apr 2013 07:41:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=pyBKkeRwYVn5Vhqu56gRpPT6NdDbqHeBa9RdsitdYFU=; b=SZlpFZFye+BmVjmxZbnujoID6Em8ql/EUKV6+5lxo+GTBE/Y1WpO6lo94EFASIwDJn VXkTRm7wionbXxhkyATt4tQRUaHr4h1NIiA/9Fa48WZjGnMiuD1e/B1T5GfqKvzUV1KO nUVhYDh6KBFSAkXJzGU/rN31s/+jdLcBHQyk6OOWt4CFCgcDs3yl0hqtjn+D183pLU3C uYyFKHV245zs0fVNHvblz0UyWO6KO9sCsztGE95pDC5/ocSp7pn0DjZECR9byIDoz2Uv oVhRkHwrJaGj94Oc3x2nTmDQ/3dA6v3LgtFqkyt7tgaEcCjyUg65k113PfscBYhGYMmS kKfw==
MIME-Version: 1.0
X-Received: by 10.52.72.40 with SMTP id a8mr9605721vdv.20.1365259303424; Sat, 06 Apr 2013 07:41:43 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Sat, 6 Apr 2013 07:41:43 -0700 (PDT)
In-Reply-To: <515F33AD.60508@gmail.com>
References: <20130405194251.19607.86337.idtracker@ietfa.amsl.com> <515F33AD.60508@gmail.com>
Date: Sat, 6 Apr 2013 10:41:43 -0400
X-Google-Sender-Auth: 3WUNjINosj-XaMqWW0t4ybK13LU
Message-ID: <CAC4RtVCujgrb3=E6mKYycAcHjav8fJNXEO4Cp657VyKHTfrwsw@mail.gmail.com>
Subject: Re: draft-sheffer-running-code-03 published
From: Barry Leiba <barryleiba@computer.org>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion Mailing 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, 06 Apr 2013 14:41:49 -0000

> we have just published a new revision of this draft, defining a new,
> optional Implementation Status section to be included in Internet Drafts:
> http://tools.ietf.org/html/draft-sheffer-running-code-03

It does look mostly ready, though I think the primary addition in -03,
the recommended boilerplate, needs something.

As I said many times in response to Stephen's proposal, I vehemently
object to the idea that any "reward" is being given.  The point here
is that specs with implementations have some greater level of evidence
of solidity than those without, and we're considering that evidence in
our evaluations -- we not rewarding them for having it, but giving
them the consideration they deserve.

When the word "reward" was only in the abstract, it was less
bothersome; now you're proposing that it be echoed in the boilerplate
of the Implementation Status section of every document that does this.
 Please, no.

I suggest this change to the Abstract, Introduction, and Section 2.1:

OLD
   This will allow
   reviewers and working groups to assign due consideration to documents
   that have the benefit of running code and potentially reward the
   documented protocols by treating the documents with implementations
   preferentially.

NEW
   This will allow
   reviewers and working groups to assign due consideration to documents
   that have the benefit of running code, by considering the running code as
   evidence of valuable experimentation and feedback that has made the
   implemented protocols more mature.

END

And then a small point in 2.1:

   Authors are requested to add a note to the RFC Editor at the top of
   this section, advising the Editor to remove the entire section before
   publication, as well as the reference to [RFC Editor: replace by a
   reference to this document].

Why not include that directly in the recommended boilerplate?:

OLD
   The following boilerplate text is proposed to head the Implementation
   Status section:

      This section records the status of known implementations of the
      protocol defined by this specification at the time of posting of
      this Internet-Draft, and is based on a proposal described in [RFC
      Editor: replace by a reference to this document].  According to
      [RFC Editor: replace by a reference to this document], "this will
      allow reviewers and working groups to assign due consideration to
      documents that have the benefit of running code and potentially
      reward the documented protocols by treating the documents with
      implementations preferentially".  Furthermore, "It is up to the
      individual working groups to use this information as they see
      fit".

NEW
   The following boilerplate text is proposed to head the Implementation
   Status section:

      This section records the status of known implementations of the
      protocol defined by this specification at the time of posting of
      this Internet-Draft, and is based on a proposal described in
      [RFCXXXX].  According to [RFCXXXX], "This will allow reviewers
      and working groups to assign due consideration to documents that
      have the benefit of running code, by considering the running code
      as evidence of valuable experimentation and feedback that has
      made the implemented protocols more mature." Furthermore, "It is
      up to the individual working groups to use this information as they
      see fit".

      [RFC Editor: Please remove this entire section and the reference
      to RFCXXXX.]

   [RFC Editor: The "RFC Editor" note above is there as example text.
   Please do not take action on it, and leave it in the document. Instead,
   replace "RFCXXXX" by a reference to this document, and remove this
   note.]

END

Barry

From adrian@olddog.co.uk  Sat Apr  6 07:58:53 2013
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 661A021F8AAA for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 07:58:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.57
X-Spam-Level: 
X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ernxrUGwaF4Y for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 07:58:52 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9C821F8A68 for <ietf@ietf.org>; Sat,  6 Apr 2013 07:58:52 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r36Ewfk0028695;  Sat, 6 Apr 2013 15:58:41 +0100
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 r36EwYiS028650 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 6 Apr 2013 15:58:35 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Barry Leiba'" <barryleiba@computer.org>, "'Yaron Sheffer'" <yaronf.ietf@gmail.com>
References: <20130405194251.19607.86337.idtracker@ietfa.amsl.com>	<515F33AD.60508@gmail.com> <CAC4RtVCujgrb3=E6mKYycAcHjav8fJNXEO4Cp657VyKHTfrwsw@mail.gmail.com>
In-Reply-To: <CAC4RtVCujgrb3=E6mKYycAcHjav8fJNXEO4Cp657VyKHTfrwsw@mail.gmail.com>
Subject: RE: draft-sheffer-running-code-03 published
Date: Sat, 6 Apr 2013 15:58:33 +0100
Message-ID: <03a801ce32d7$3849ef50$a8ddcdf0$@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: AQKW9EKV9UmB4IRLyATi+JVTiEMQhgKTQyd0AhCy5eqXEqUTcA==
Content-Language: en-gb
Cc: 'IETF Discussion Mailing 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: Sat, 06 Apr 2013 14:58:53 -0000

Hi,

[snipping out some useful points]

We had considered what you suggest below, and indeed I typed it up in a recent
email to Yaron before deleting it again.

Yes, we could do what you suggest, but as you found, it requires a kind of
meta-note to the RFC Editor that starts to get messy and confusing.

If you feel strongly that something needs to be included in the boilerplate we
can look again. but since it is only suggested rather than mandated boilerplate,
maybe it is enough to ask for a note to be added rather than including the text
of the note in the boilerplate?

A

> And then a small point in 2.1:
> 
>    Authors are requested to add a note to the RFC Editor at the top of
>    this section, advising the Editor to remove the entire section before
>    publication, as well as the reference to [RFC Editor: replace by a
>    reference to this document].
> 
> Why not include that directly in the recommended boilerplate?:
> 
> OLD
>    The following boilerplate text is proposed to head the Implementation
>    Status section:
> 
>       This section records the status of known implementations of the
>       protocol defined by this specification at the time of posting of
>       this Internet-Draft, and is based on a proposal described in [RFC
>       Editor: replace by a reference to this document].  According to
>       [RFC Editor: replace by a reference to this document], "this will
>       allow reviewers and working groups to assign due consideration to
>       documents that have the benefit of running code and potentially
>       reward the documented protocols by treating the documents with
>       implementations preferentially".  Furthermore, "It is up to the
>       individual working groups to use this information as they see
>       fit".
> 
> NEW
>    The following boilerplate text is proposed to head the Implementation
>    Status section:
> 
>       This section records the status of known implementations of the
>       protocol defined by this specification at the time of posting of
>       this Internet-Draft, and is based on a proposal described in
>       [RFCXXXX].  According to [RFCXXXX], "This will allow reviewers
>       and working groups to assign due consideration to documents that
>       have the benefit of running code, by considering the running code
>       as evidence of valuable experimentation and feedback that has
>       made the implemented protocols more mature." Furthermore, "It is
>       up to the individual working groups to use this information as they
>       see fit".
> 
>       [RFC Editor: Please remove this entire section and the reference
>       to RFCXXXX.]
> 
>    [RFC Editor: The "RFC Editor" note above is there as example text.
>    Please do not take action on it, and leave it in the document. Instead,
>    replace "RFCXXXX" by a reference to this document, and remove this
>    note.]
> 
> END


From moore@network-heretics.com  Sat Apr  6 08:12:58 2013
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 1B47221F8EB2 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:12:58 -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=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DLN2k+gLl56G for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:12:57 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 74A0321F8EAE for <ietf@ietf.org>; Sat,  6 Apr 2013 08:12:57 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E5729209D6 for <ietf@ietf.org>; Sat,  6 Apr 2013 11:12:55 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 06 Apr 2013 11:12:55 -0400
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=oBzInwnJGOuqH0ShpFDy5q 8NCAA=; b=W0t3k2+w1sKdj+mSmmaXetJpJztIdNsY5R/DXRgUWU2NJRo/DwbL8n hmXfw9R4ptx6B7fjtERVrDEXS4U9IjrguSRU2h6lIV+FiISIic6ICYUONGDty5To qhkdq2CCDsfTzfJpmKkbp2IMlv/oArYxNIa7XW5+zQ4DDImMf/7LQ=
X-Sasl-enc: LdxXQ1II5fjcECHno0JdiHDdjNGtNm3uR5y+BRvosWI3 1365261175
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 576D52000A1; Sat,  6 Apr 2013 11:12:55 -0400 (EDT)
Message-ID: <51603B6F.7010204@network-heretics.com>
Date: Sat, 06 Apr 2013 11:12:47 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Less Corporate Diversity
References: <FB4D5027-9279-47DA-A122-91C65D1DB54D@standardstrack.com> <FF0C573C-DFC9-4241-8E97-1943A4831FAE@piuha.net> <CD8A2BFC24C51A24A71EBA5E@JcK-HP8200.jck.com> <514D1EB2.6070805@mrp.net>, <514D207E.60506@joelhalpern.com> <290E20B455C66743BE178C5C84F124081A49EEF29C@EXMB01CMS.surrey.ac.uk> <A4654596-9CA6-48D8-B876-96B1330522FC@gmail.com>
In-Reply-To: <A4654596-9CA6-48D8-B876-96B1330522FC@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: Sat, 06 Apr 2013 15:12:58 -0000

On 03/23/2013 02:27 AM, Bob Hinden wrote:
> To raise this discussion up a bit, I can think two other related reasons why there may be less corporate diversity in the IETF.
>
> The first is that it's possible to build applications and businesses that take advantage of the Internet without having to come to the IETF to standardize anything.  The work of the IETF (and related organizations like W3C, IEEE, etc.) have made this possible.  A success problem so to speak.
>
> The second is that it's very hard to make changes at the IP and transport layers and have them be deployed in scale given middle boxes.  Many organizations have stopped trying and focus on making things work on top of http.  This also doesn't require coming to the IETF.

Perhaps not, but the extensive proliferation of middle boxes is arguably 
due to various failures within IETF, such as the failure to promote 
end-to-end security or the failure to extend the Internet architecture 
to accommodate legitimate needs of networks.

Keith



From barryleiba@gmail.com  Sat Apr  6 08:16:55 2013
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 2769921F8EA6 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.834
X-Spam-Level: 
X-Spam-Status: No, score=-101.834 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXLQxdiIuT+u for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:16:54 -0700 (PDT)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5772E21F8E94 for <ietf@ietf.org>; Sat,  6 Apr 2013 08:16:54 -0700 (PDT)
Received: by mail-la0-f54.google.com with SMTP id gw10so4186698lab.41 for <ietf@ietf.org>; Sat, 06 Apr 2013 08:16:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=bUSSxQtfpa4BU7G+bOtMFiiAdznz6Tk8ZhSE37NV2DY=; b=MA3QOOpJ4xva7B0rzYyNg0kKbGUyJ27mcBZYk6Pb4NqU/QlBfGHKQl67ZR1B0yDMvu g5tmsHTPq92wxF6hVKvYQ5fTXnn3v7MM/Ba0er9eRafo+N0BfT3n8E/BNPzWZ8WexAtV cOI1vO/ukZSN18TxZN0kc7jSIMfbyDOQkr1lBzTB6SMAUfxZ15OVhCiCxTuwfCo6gNcU h/RFnJUultF/o/tFTKGPFS63Zz/zEXcX2718XKxkJ3SvWipmkTG2Rhs7woPKXAqQBtR9 xHvWQMEIOuNGFsVb4uQN0GC0UAi4jAY/wpoEBlJ1Mic7mjjVc2fjvlPfmj7cdsHEDe9s Zrdg==
MIME-Version: 1.0
X-Received: by 10.112.168.97 with SMTP id zv1mr8441324lbb.25.1365261413205; Sat, 06 Apr 2013 08:16:53 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.112.76.98 with HTTP; Sat, 6 Apr 2013 08:16:53 -0700 (PDT)
In-Reply-To: <03a801ce32d7$3849ef50$a8ddcdf0$@olddog.co.uk>
References: <20130405194251.19607.86337.idtracker@ietfa.amsl.com> <515F33AD.60508@gmail.com> <CAC4RtVCujgrb3=E6mKYycAcHjav8fJNXEO4Cp657VyKHTfrwsw@mail.gmail.com> <03a801ce32d7$3849ef50$a8ddcdf0$@olddog.co.uk>
Date: Sat, 6 Apr 2013 11:16:53 -0400
X-Google-Sender-Auth: bKefkiXuMi0BBvnLKU0F9k9BYa4
Message-ID: <CALaySJ++OK69ZrSzVtNbEZkSH87NgR=8Keqg0HS=3HGqSRcjXg@mail.gmail.com>
Subject: Re: draft-sheffer-running-code-03 published
From: Barry Leiba <barryleiba@computer.org>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, IETF Discussion Mailing 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, 06 Apr 2013 15:16:55 -0000

> Yes, we could do what you suggest, but as you found, it requires a kind of
> meta-note to the RFC Editor that starts to get messy and confusing.

I don't know: I don't think the meta-note is a problem.  Perhaps you
might pass it by Sandy and see if she thinks it's reasonable and
understandable.

> If you feel strongly that something needs to be included in the boilerplate we
> can look again. but since it is only suggested rather than mandated boilerplate,
> maybe it is enough to ask for a note to be added rather than including the text
> of the note in the boilerplate?

Sure, it's enough... though I really do think that if you're
recommending boilerplate, you should recommend complete boilerplate.

But, no, this isn't a "DISCUSS" level thing.  :-)

Barry

From stbryant@cisco.com  Sat Apr  6 08:39:53 2013
Return-Path: <stbryant@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 5F12321F8EBB for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:39:53 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wcL9e5V5POiB for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:39:52 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 400A521F8EC1 for <ietf@ietf.org>; Sat,  6 Apr 2013 08:39:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=309; q=dns/txt; s=iport; t=1365262791; x=1366472391; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=q3MRfqJIjstjVfVafTwmwhJfszVchUg0GeCM3f5KPYM=; b=QxqFr/5ItRxGls4IShYmB2+XNhjny/3xtelaSzNJJvuehDUYG9lUq/Xt +kdzHyYg0bHNTTWfd18hkLWTlAQ4xQu57U6Mxauf7DQoNcabb+vkBBFp0 TKN6Mk4WFG0PVeUqmdNYtooE307PINIipEop8pmcDxbSiwV633VIeN8pA w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApQFAGtBYFGtJV2Y/2dsb2JhbABRgwaDGb4+gQIWdIIfAQEBAwE6PxACAQg2ECERJQIEDgWIAgMJBrUTDYldjEmCHzMHgl9hA5UOgWCLcoUbgws
X-IronPort-AV: E=Sophos;i="4.87,421,1363132800"; d="scan'208";a="195769983"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-3.cisco.com with ESMTP; 06 Apr 2013 15:39:50 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r36Fdom0019088 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 6 Apr 2013 15:39:50 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Sat, 6 Apr 2013 10:39:50 -0500
From: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the	first
Thread-Topic: Comments for Humorous RFCs or uncategorised RFCs or dated April the	first
Thread-Index: AQHOMsc4lhhFwNDwuUuo9GxZDHFpapjJVGMQ
Date: Sat, 6 Apr 2013 15:39:49 +0000
Message-ID: <D16DEEF2-A3AB-4FA0-8950-749D575D8004@cisco.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
In-Reply-To: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
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: Sat, 06 Apr 2013 15:39:53 -0000

Sent from my iPad

On 6 Apr 2013, at 14:04, "Abdussalam Baryun" <abdussalambaryun@gmail.com> w=
rote:

>=20
> If the date is
> special then thoes RFCs SHOULD be *historical*.
>=20

Surely the correct requirement is :

If the date is special then those RFCs MUST be *hysterical*.

- Stewart





From hsantos@isdg.net  Sat Apr  6 08:53:20 2013
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 4D38321F8EC7 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.867
X-Spam-Level: 
X-Spam-Status: No, score=-100.867 tagged_above=-999 required=5 tests=[AWL=0.867, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H64xDxhz9Ymg for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:53:19 -0700 (PDT)
Received: from pop3.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 986E421F8BB6 for <ietf@ietf.org>; Sat,  6 Apr 2013 08:53:19 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1925; t=1365263588; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=A9boUG8 w8Df5Z1Evt06HULhnHlc=; b=tW8JAQ2h5vPZRwAIGlmG1MLqxJwyTFDzwxFFbgi dJcpQTPpIHdkrfLaQ7CbC1Pt/Ndd8w+kosxqo0bvLMkxW/Mjp9/IU4BzSA4jZGZH BS/bgSXK0Qz9PYrknEBA3BAc6kWZOY2QIRLsxA0tD0qu4V4KbEEjHCftt0BNZGgP 4ZdI=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 06 Apr 2013 10:53:08 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4057296264.676.5508; Sat, 06 Apr 2013 10:53:07 -0500
Message-ID: <516044AE.8080904@isdg.net>
Date: Sat, 06 Apr 2013 11:52:14 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
In-Reply-To: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Sat, 06 Apr 2013 15:53:20 -0000

Hi Abdusalam,

You should consider all APRIL 1 published I-D as "SPAM" and the 
electronic mail follow ups generated in the IETF list as more wasted 
bandwidth, time and spam.   We have too much time in our hands, boredom 
for many, and even more wasted time if we spend time reading it - so in 
that regard I agree with your concerns.  Who has time for all this?  Its 
already a challenge to decipher most of the postings and wondering if 
one is serious or not. Ignore April 1 publications. :)

--
HLS


On 4/6/2013 9:03 AM, Abdussalam Baryun wrote:
> <Unclassified Message, but not Humorous>
>
> Some participants like to send messages/documents as categoried or
> classified, and may include in others uncategorised or unclassified.
> That is a reasonable approach in reasonable organisations.
>
> I see some RFCs as mentioned in [1], that they are humorous that
> reflect a historic culture or a behavior that some may like to do in a
> certain date (others may not like to do or be part of). If the date is
> special then thoes RFCs SHOULD be *historical*.
>
> I suggest/request that the IETF stops this humorous RFC publication or
> try to categories them or distinguish them from our logical
> work/efforts. I request if they are categorised as informational or
> experimental then to be obsoleted. I recommend for future RFCs of that
> type categories to be as *historical* not others (i.e. informational).
>
>   If those RFCs are not categorising/distinguished as unclassified or
> humorous, then all RFC may be affected. The reader may not be able to
> distinguish thoes published documents by IETF (does an organisation
> care about readers or users of its publications!). You may think to
> create a new category name for such publication published on April for
> that interested culture behavior.
>
> [1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>
> Regards
> AB
>
>


From swb@internet2.edu  Sat Apr  6 08:57:36 2013
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 EFA0121F8EFD for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:57:36 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgC7yxilkHFv for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 08:57:36 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe004.messaging.microsoft.com [216.32.180.14]) by ietfa.amsl.com (Postfix) with ESMTP id 531B821F8ED4 for <ietf@ietf.org>; Sat,  6 Apr 2013 08:57:36 -0700 (PDT)
Received: from mail26-va3-R.bigfish.com (10.7.14.252) by VA3EHSOBE006.bigfish.com (10.7.40.26) with Microsoft SMTP Server id 14.1.225.23; Sat, 6 Apr 2013 15:57:35 +0000
Received: from mail26-va3 (localhost [127.0.0.1])	by mail26-va3-R.bigfish.com (Postfix) with ESMTP id 669382007A; Sat,  6 Apr 2013 15:57:35 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.237.5; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0811HT004.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 7
X-BigFish: S7(zzbb2dI98dI1432Izz1f42h1fc6h1d77h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1082kzzz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1b1cn1b1bi1155h)
Received: from mail26-va3 (localhost.localdomain [127.0.0.1]) by mail26-va3 (MessageSwitch) id 1365263853499559_30779; Sat,  6 Apr 2013 15:57:33 +0000 (UTC)
Received: from VA3EHSMHS006.bigfish.com (unknown [10.7.14.243])	by mail26-va3.bigfish.com (Postfix) with ESMTP id 6B42A3E0119; Sat,  6 Apr 2013 15:57:33 +0000 (UTC)
Received: from BY2PRD0811HT004.namprd08.prod.outlook.com (157.56.237.5) by VA3EHSMHS006.bigfish.com (10.7.99.16) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 6 Apr 2013 15:57:33 +0000
Received: from swbi2mbp.local (69.137.164.168) by pod51019.outlook.com (10.255.91.167) with Microsoft SMTP Server (TLS) id 14.16.287.8; Sat, 6 Apr 2013 15:57:32 +0000
Message-ID: <516045EC.3090900@internet2.edu>
Date: Sat, 6 Apr 2013 11:57:32 -0400
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hector Santos <hsantos@isdg.net>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net>
In-Reply-To: <516044AE.8080904@isdg.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [69.137.164.168]
X-OriginatorOrg: internet2.edu
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: Sat, 06 Apr 2013 15:57:37 -0000

On 04/06/13 11:52, Hector Santos allegedly wrote:
> Hi Abdusalam,
> 
> You should consider all APRIL 1 published I-D as "SPAM" and the
> electronic mail follow ups generated in the IETF list as more wasted
> bandwidth, time and spam.   We have too much time in our hands, boredom
> for many, and even more wasted time if we spend time reading it - so in
> that regard I agree with your concerns.  Who has time for all this?  Its
> already a challenge to decipher most of the postings and wondering if
> one is serious or not. Ignore April 1 publications. :)

It's called having a shared culture.  The IETF could even generate
friendship, if allowed.


From dwm@xpasc.com  Sat Apr  6 10:02:31 2013
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 84BF421F849C for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level: 
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xrvvLjgTHxdN for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:02:31 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 21D2421F8499 for <ietf@ietf.org>; Sat,  6 Apr 2013 10:02:30 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 780D440391 for <ietf@ietf.org>; Sat,  6 Apr 2013 17:02:30 +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 r36H2U9a002553 for <ietf@ietf.org>; Sat, 6 Apr 2013 10:02:30 -0700
Date: Sat, 6 Apr 2013 10:02:30 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf <ietf@ietf.org>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
In-Reply-To: <516045EC.3090900@internet2.edu>
Message-ID: <alpine.LRH.2.01.1304060949060.26119@egate.xpasc.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <516045EC.3090900@internet2.edu>
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, 06 Apr 2013 17:02:31 -0000

On Sat, 6 Apr 2013, Scott Brim wrote:

> On 04/06/13 11:52, Hector Santos allegedly wrote:
> > Hi Abdusalam,
> > 
> > You should consider all APRIL 1 published I-D as "SPAM" and the
> > electronic mail follow ups generated in the IETF list as more wasted
> > bandwidth, time and spam.   We have too much time in our hands, boredom
> > for many, and even more wasted time if we spend time reading it - so in
> > that regard I agree with your concerns.  Who has time for all this?  Its
> > already a challenge to decipher most of the postings and wondering if
> > one is serious or not. Ignore April 1 publications. :)
> 
> It's called having a shared culture.  The IETF could even generate
> friendship, if allowed.

The most effective way to join a well established group is to lurk long
enough to understand the social structure and operational norms of the
group before demanding that the group change to your norms. We don't need
to become a dour boring group to meet the diversity goals discussed in
other threads.

It is also about reading and understanding before responding in public.
Part of the fun of the April 1 RFC series is that they start by sounding
real for a couple sentences and the latest was better than most in
that regard.

From heas@shrubbery.net  Sat Apr  6 10:10:05 2013
Return-Path: <heas@shrubbery.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 4515121F8617 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.203
X-Spam-Level: 
X-Spam-Status: No, score=-5.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JGhCQHGDGAy3 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:10:04 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CAB321F8615 for <ietf@ietf.org>; Sat,  6 Apr 2013 10:10:04 -0700 (PDT)
Received: from [10.166.231.170] (140.sub-70-199-225.myvzw.com [70.199.225.140]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by guelah.shrubbery.net (Postfix) with ESMTPSA id 3A6BBA1D4; Sat,  6 Apr 2013 17:10:05 +0000 (UTC)
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <516044AE.8080904@isdg.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <907C9058-8EA4-483C-9C8C-3EEB15BDA8C4@shrubbery.net>
X-Mailer: iPhone Mail (10B329)
From: Heasley <heas@shrubbery.net>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
Date: Sat, 6 Apr 2013 10:10:03 -0700
To: Hector Santos <hsantos@isdg.net>
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: Sat, 06 Apr 2013 17:10:05 -0000

Am Apr 6, 2013 um 8:52 schrieb Hector Santos <hsantos@isdg.net>:

> Hi Abdusalam,
>=20
> You should consider all APRIL 1 published I-D as "SPAM" and the electronic=
 mail follow ups generated in the IETF list as more wasted bandwidth, time a=
nd spam.   We have too much time in our hands, boredom for many, and even mo=
re wasted time if we spend time reading it - so in that regard I agree with y=
our concerns.  Who has time for all this?  Its already a challenge to deciph=
er most of the postings and wondering if one is serious or not. Ignore April=
 1 publications. :)
>=20
It's called humor and fun; look it up.=20

> --
> HLS
>=20
>=20
> On 4/6/2013 9:03 AM, Abdussalam Baryun wrote:
>> <Unclassified Message, but not Humorous>
>>=20
>> Some participants like to send messages/documents as categoried or
>> classified, and may include in others uncategorised or unclassified.
>> That is a reasonable approach in reasonable organisations.
>>=20
>> I see some RFCs as mentioned in [1], that they are humorous that
>> reflect a historic culture or a behavior that some may like to do in a
>> certain date (others may not like to do or be part of). If the date is
>> special then thoes RFCs SHOULD be *historical*.
>>=20
>> I suggest/request that the IETF stops this humorous RFC publication or
>> try to categories them or distinguish them from our logical
>> work/efforts. I request if they are categorised as informational or
>> experimental then to be obsoleted. I recommend for future RFCs of that
>> type categories to be as *historical* not others (i.e. informational).
>>=20
>>  If those RFCs are not categorising/distinguished as unclassified or
>> humorous, then all RFC may be affected. The reader may not be able to
>> distinguish thoes published documents by IETF (does an organisation
>> care about readers or users of its publications!). You may think to
>> create a new category name for such publication published on April for
>> that interested culture behavior.
>>=20
>> [1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>>=20
>> Regards
>> AB
>>=20
>>=20

From abdussalambaryun@gmail.com  Sat Apr  6 10:12:26 2013
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 4D23821F8640 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.764
X-Spam-Level: 
X-Spam-Status: No, score=-2.764 tagged_above=-999 required=5 tests=[AWL=-0.480, BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H8rTfEqOyE3q for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:12:25 -0700 (PDT)
Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) by ietfa.amsl.com (Postfix) with ESMTP id D23E821F862A for <ietf@ietf.org>; Sat,  6 Apr 2013 10:12:25 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id 10so2486724pdi.29 for <ietf@ietf.org>; Sat, 06 Apr 2013 10:12:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=+9hK0PeGDWz1w7H0hra7Ko+RL9rWAfmcAHIWYSlKJ6Q=; b=XNP4Vw62BUOtoX1EuKIwYfgq/SIAnbzM6olqhSTv7vmtC8WtTPqWGyez91cnie1EcJ 1rpKubJ+t3sTIstYLngGfyItk6kR0TWdGq+DeBk3Et4RxIT32n281EbObnpPXzO9EgA/ ZBgokamv5Cdy6MwR0eXUQCwu4N1SrnpB88UvHWRD2x2XOZjx5LpIz1RGEKoXa0/7K5QF efUCrxcEpPwD1nVvDq61jnRKSTrnQMh4nEBDqHNW/PF2WFE/E53ZxREB45lzH6KFC3IW MhrRHMQgIm36wK8HIo0U3O2zFdBByRNa5RjLKnJlCBt2LkpskRJsyIH2llUMj5ugI6KC GOsA==
MIME-Version: 1.0
X-Received: by 10.66.184.14 with SMTP id eq14mr16783308pac.215.1365268345492;  Sat, 06 Apr 2013 10:12:25 -0700 (PDT)
Received: by 10.68.33.132 with HTTP; Sat, 6 Apr 2013 10:12:25 -0700 (PDT)
In-Reply-To: <CAKHUCzwBpvDE6FtmcTWGOWydKFhgZtcnw_gU0PA4DhPjiTDPOg@mail.gmail.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <CAKHUCzwBpvDE6FtmcTWGOWydKFhgZtcnw_gU0PA4DhPjiTDPOg@mail.gmail.com>
Date: Sat, 6 Apr 2013 19:12:25 +0200
Message-ID: <CADnDZ88nXw71kRyAoFBf4twLsP-EeY8o=R8BxuFWHt2dhTx0eg@mail.gmail.com>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org 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: Sat, 06 Apr 2013 17:12:26 -0000

The Mark Crispin RFC was not categorised as informational nor
experimental, so I was not against that old work that had few readers,
the problem is now new work and  millions of readers,

AB

On 4/6/13, Dave Cridland <dave@cridland.net> wrote:
> These aren't published by the IETF, but by the RFC editor directly. As
> such, the IETF has little control.
>
> Even if this were not so, I would be very much against discontinuing or
> specially marking such documents. I appreciate Mark Crispin was always
> proud that his randomly lose telnet extension was marked 'note date of
> issue', but that should remain the only one.
>
> Humour is an important part of IETF culture, and long may it remain so.
> Actively working to remove support for humour would be a very bad thing,
> and marking it joylessly would drain it of any value.
> On 6 Apr 2013 14:03, "Abdussalam Baryun" <abdussalambaryun@gmail.com>
> wrote:
>
>> <Unclassified Message, but not Humorous>
>>
>> Some participants like to send messages/documents as categoried or
>> classified, and may include in others uncategorised or unclassified.
>> That is a reasonable approach in reasonable organisations.
>>
>> I see some RFCs as mentioned in [1], that they are humorous that
>> reflect a historic culture or a behavior that some may like to do in a
>> certain date (others may not like to do or be part of). If the date is
>> special then thoes RFCs SHOULD be *historical*.
>>
>> I suggest/request that the IETF stops this humorous RFC publication or
>> try to categories them or distinguish them from our logical
>> work/efforts. I request if they are categorised as informational or
>> experimental then to be obsoleted. I recommend for future RFCs of that
>> type categories to be as *historical* not others (i.e. informational).
>>
>>  If those RFCs are not categorising/distinguished as unclassified or
>> humorous, then all RFC may be affected. The reader may not be able to
>> distinguish thoes published documents by IETF (does an organisation
>> care about readers or users of its publications!). You may think to
>> create a new category name for such publication published on April for
>> that interested culture behavior.
>>
>> [1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>>
>> Regards
>> AB
>>
>

From tjc@ecs.soton.ac.uk  Sat Apr  6 10:15:27 2013
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 09E7D21F8738 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:15:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNP0qXaP76cg for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:15:26 -0700 (PDT)
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 13F9D21F8700 for <ietf@ietf.org>; Sat,  6 Apr 2013 10:15:25 -0700 (PDT)
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 r36HFJYb005459; Sat, 6 Apr 2013 18:15:19 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r36HFJYb005459
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1365268519; bh=mqLvSCoqIdtw1azQlubotrva8Gg=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=OyipMzg14bySEq8G7ir70fbpoEj6vKAcRBXprhFIoCXphLZbpU7DW1j+MB6fO6GKN L9WhIHJ/OgygtPMuvJxmXFl+tecdcsdk/mBF8CYSqEHgo6GHVsMqzzZEbmSkxjOZMc TslSM+PzgpuekO+IvZqBtVRIBr9LFzy4/5Fq+nxY=
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 p35IFJ043062287641 ret-id none; Sat, 06 Apr 2013 18:15:19 +0100
Received: from [192.168.1.103] (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 r36HDulL009366 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 6 Apr 2013 18:13:58 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the	first
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <D16DEEF2-A3AB-4FA0-8950-749D575D8004@cisco.com>
Date: Sat, 6 Apr 2013 18:13:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|7bc3f95779d33d6ed39ad86bd6ebcdecp35IFJ03tjc|ecs.soton.ac.uk|0097FC23-054C-4B56-A9AC-37DB4C1712C7@ecs.soton.ac.uk>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <D16DEEF2-A3AB-4FA0-8950-749D575D8004@cisco.com> <0097FC23-054C-4B56-A9AC-37DB4C1712C7@ecs.soton.ac.uk>
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p35IFJ043062287600; tid=p35IFJ043062287641; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r36HFJYb005459
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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: Sat, 06 Apr 2013 17:15:27 -0000

On 6 Apr 2013, at 16:39, "Stewart Bryant (stbryant)" =
<stbryant@cisco.com> wrote:
>=20
> On 6 Apr 2013, at 14:04, "Abdussalam Baryun" =
<abdussalambaryun@gmail.com> wrote:
>=20
>>=20
>> If the date is
>> special then thoes RFCs SHOULD be *historical*.
>>=20
>=20
> Surely the correct requirement is :
>=20
> If the date is special then those RFCs MUST be *hysterical*.

'Like' :)

Tim=

From abdussalambaryun@gmail.com  Sat Apr  6 10:35:56 2013
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 CA01821F8617 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:35:56 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sJk8IMDPTxi7 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:35:56 -0700 (PDT)
Received: from mail-da0-x22a.google.com (mail-da0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 04AD721F8539 for <ietf@ietf.org>; Sat,  6 Apr 2013 10:35:55 -0700 (PDT)
Received: by mail-da0-f42.google.com with SMTP id n15so2003862dad.15 for <ietf@ietf.org>; Sat, 06 Apr 2013 10:35:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=j9/YqCu4+cZfr224QLI1dLdvmT7/BJcTBcKgrRlt28c=; b=k+OEJT8WjXMSYR7Chxyud35sgooS2FgozRhhrUu8NmU1SM9wBSqkt8U8NVK35TtS39 /MGq/nDqLuxQBjI4knX9Vu2rK8YH34N821fu0pwf6XgpmYjveP97hrsHY6Yr6QemEjew D+sY3jz+GRU/Q4t6funi/ff9JRF9kSRkG1zJcmBD+91TzxaQ14yt40/5oC1yl0Mkjfiw oUl5s69Dtrlewap538L1VPZ6RvVrZZ56xojxb1ws4/PCRhQrBiR/Ur8XNedTetCcw5tR 3EdYQt8LRs5Hv9n8qFZxRDYVH9Wi/lRsVvu5CLSPRB98rrIdVFMoXeS++Vg83ZIUeBnR ya3Q==
MIME-Version: 1.0
X-Received: by 10.66.75.193 with SMTP id e1mr21849756paw.202.1365269755547; Sat, 06 Apr 2013 10:35:55 -0700 (PDT)
Received: by 10.68.33.132 with HTTP; Sat, 6 Apr 2013 10:35:55 -0700 (PDT)
In-Reply-To: <516044AE.8080904@isdg.net>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net>
Date: Sat, 6 Apr 2013 19:35:55 +0200
Message-ID: <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Hector Santos <hsantos@isdg.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: Sat, 06 Apr 2013 17:35:56 -0000

Hi Hector,

When I read the RFC on 1 April 2013 (my first time experience) I
noticed something is wrong (with the system or with doc-content), but
the document does not refer to any joke. As if you receive a message
from someone you know, but you realise that you don't know why he/she
sending it. If it is the IETF culture, is this culture defined in any
RFC or draft? However, don't mind culture/fun but mind its relation to
classifications. My comments in line,

On 4/6/13, Hector Santos <hsantos@isdg.net> wrote:
> Hi Abdusalam,
>
> You should consider all APRIL 1 published I-D as "SPAM" and the
> electronic mail follow ups generated in the IETF list as more wasted
> bandwidth, time and spam.

the question is not that I SHOULD consider importance for the
published date, my question is : Does the IETF as an organisation
consider Content of its publications? is there something in IETF as
reference refering to such happy activity!!!, I am not sure. If yes
there is a reference then why the management forgot to categorise the
RFC as different from the serious work, do they just rely on the date
1 April.

> We have too much time in our hands, boredom
> for many, and even more wasted time if we spend time reading it - so in
> that regard I agree with your concerns.  Who has time for all this?  Its
> already a challenge to decipher most of the postings and wondering if
> one is serious or not. Ignore April 1 publications. :)

I never ignore any message/RFC I receive from IETF, IMO the IETF
SHOULD consider to categorise its messages sent or documents published
as any other publishers do for readers. However, I will follow your
advise, but just like to comment about any faulty RFC because it is in
the end a Request For Comment (RFC).

If the documents are calling/requesting a comment that was my
reply/comment as a reader,

<Just done my job and commented don't care if things change or not>

AB

>
> --
> HLS
>
>
> On 4/6/2013 9:03 AM, Abdussalam Baryun wrote:
>> <Unclassified Message, but not Humorous>
>>
>> Some participants like to send messages/documents as categoried or
>> classified, and may include in others uncategorised or unclassified.
>> That is a reasonable approach in reasonable organisations.
>>
>> I see some RFCs as mentioned in [1], that they are humorous that
>> reflect a historic culture or a behavior that some may like to do in a
>> certain date (others may not like to do or be part of). If the date is
>> special then thoes RFCs SHOULD be *historical*.
>>
>> I suggest/request that the IETF stops this humorous RFC publication or
>> try to categories them or distinguish them from our logical
>> work/efforts. I request if they are categorised as informational or
>> experimental then to be obsoleted. I recommend for future RFCs of that
>> type categories to be as *historical* not others (i.e. informational).
>>
>>   If those RFCs are not categorising/distinguished as unclassified or
>> humorous, then all RFC may be affected. The reader may not be able to
>> distinguish thoes published documents by IETF (does an organisation
>> care about readers or users of its publications!). You may think to
>> create a new category name for such publication published on April for
>> that interested culture behavior.
>>
>> [1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>>
>> Regards
>> AB
>>
>>
>
>

From melinda.shore@gmail.com  Sat Apr  6 10:38:28 2013
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 E9D9221F86B2 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.332
X-Spam-Level: 
X-Spam-Status: No, score=-1.332 tagged_above=-999 required=5 tests=[AWL=-2.268, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877,  RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PXL83hC8pnPq for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:38:27 -0700 (PDT)
Received: from mail-da0-x22a.google.com (mail-da0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D25C021F869C for <ietf@ietf.org>; Sat,  6 Apr 2013 10:38:27 -0700 (PDT)
Received: by mail-da0-f42.google.com with SMTP id n15so1996014dad.29 for <ietf@ietf.org>; Sat, 06 Apr 2013 10:38:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=b/o4elBqN5Ng+dWaiLv7OR6PXF2DJnJYcVpyEWy1Gdk=; b=NPfk7upvibL/iITh5s7mDDaj7e7Sa1Kj9dlSToYuJzfhNqsuINc0snMlg9Aqqh9xDh 3uTecCxyCf4WkVL12rrz0bD8S7aizr63QA22J/Qf4b6uM63+Y+0jJcwtgt5Fi5CQ1Xuo N4gECbi3+VYUOIDUswwPN8c/kXTlKNatwhT2Q6FMNpf/prGZG6vAYBkuGSpkpw6EWlOG TZMieMkjuITi+Nwq1E8V/OucQO6Yh58dW1Rl3w4/PqWLkxMqteXf+F/w6fCTlNJ0gjLw +yoEPVaSZdukDt7YwbNrqdrZYt9EHZ1Pc1ynQOmjtN4HqnA0cyXap3hLjlLSWVwdfkA3 X2ug==
X-Received: by 10.66.220.197 with SMTP id py5mr21779889pac.86.1365269907387; Sat, 06 Apr 2013 10:38:27 -0700 (PDT)
Received: from spandex.local (66-230-112-119-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.119]) by mx.google.com with ESMTPS id yr10sm21292194pab.6.2013.04.06.10.38.25 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 06 Apr 2013 10:38:26 -0700 (PDT)
Message-ID: <51605D8F.2090406@gmail.com>
Date: Sat, 06 Apr 2013 09:38:23 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com>
In-Reply-To: <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@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: Sat, 06 Apr 2013 17:38:29 -0000

On 4/6/13 9:35 AM, Abdussalam Baryun wrote:
> but just like to comment about any faulty RFC because it is in
> the end a Request For Comment (RFC).

Clearly the real solution would be to rename the series.

Melinda


From abdussalambaryun@gmail.com  Sat Apr  6 10:49:12 2013
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 A34F721F861B for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.873
X-Spam-Level: 
X-Spam-Status: No, score=-2.873 tagged_above=-999 required=5 tests=[AWL=-0.274, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I7n28z6saayf for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 10:49:12 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 3C4D821F8533 for <ietf@ietf.org>; Sat,  6 Apr 2013 10:49:12 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id 3so2498820pdj.27 for <ietf@ietf.org>; Sat, 06 Apr 2013 10:49:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=hT0nBpQRzMC1nMxvQScA4O3gSY4zXrpbjc/+5XbiGkw=; b=BMN2EMvRQU6Yy+UVElfeNj9dpWRnIVv3OPJJpHyLyPmzww1kqDfJIrWiToIzqK5qjL c8tqPRneyYKxKPKscMBQ2wGFxUx34plcFJ1aCfdaLliIzAC15wRL1k4PJSeWazt7jzdA 6FRdA6HDzVihQkdlRKt6A6Pr7UQZOCBPi0jHb32NBbHaWqMfGm3l3c0okfwFMaiTa2j8 rWo7Ws4/lT+Nb//lY04DapeglmP0pUOkAHj2GXsRvJJcPyLr8eAV/XueenUFdDx0+SS1 q7BGXQt7uwY4bmz84ABH4lrRMed3IxwiExKyu28yq9foxwQbZ+153lETzeyQ/nOODOHR 4NEg==
MIME-Version: 1.0
X-Received: by 10.66.144.5 with SMTP id si5mr18143691pab.6.1365270551838; Sat, 06 Apr 2013 10:49:11 -0700 (PDT)
Received: by 10.68.33.132 with HTTP; Sat, 6 Apr 2013 10:49:11 -0700 (PDT)
In-Reply-To: <577E2C0B-16F5-47D2-8D71-7A9D914ACF23@kumari.net>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <577E2C0B-16F5-47D2-8D71-7A9D914ACF23@kumari.net>
Date: Sat, 6 Apr 2013 19:49:11 +0200
Message-ID: <CADnDZ8_p=hp+yP5YTso72LO6MEuONxpdw-QBsTCtXn+v9eVpaw@mail.gmail.com>
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated April the first
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Warren Kumari <warren@kumari.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: Sat, 06 Apr 2013 17:49:12 -0000

On 4/6/13, Warren Kumari <warren@kumari.net> wrote:
> -very, very, very lots.
>
> I understand you may have missed the fact that an RFC was an April 1st, and
> are grumpy now, but that's no reason to ruin things for the rest of us...
>
> Try hacking protocol, not policy -- then folk may listen more to your
> proposals on things.

A message today may not be listened to but in future it may be listen
to. I just commented and replied to special publication RFC, does that
ruin things for you? do you/us own the policy. If IETF does not listen
to proposals on the list, then what is it about, do you mean folks
don't listen to only specific people's proposals? I think me or you
don't know how IETF works,

AB

From elwynd@dial.pipex.com  Sat Apr  6 13:26:09 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6024B21F89A6 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 13:26:09 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBZSUNuDZwY9 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 13:26:09 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id DD96F21F8521 for <ietf@ietf.org>; Sat,  6 Apr 2013 13:26:08 -0700 (PDT)
Received: from 247.254.187.81.in-addr.arpa ([81.187.254.247]) by a.painless.aa.net.uk with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1UOZgZ-0007Qv-0k; Sat, 06 Apr 2013 21:26:05 +0100
Date: Sat, 06 Apr 2013 21:26:04 +0100
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the	first
Message-ID: <4xe3ug28nhgoau4ssaiigfcj.1365279964452@email.android.com>
From: Elwyn Davies <elwynd@dial.pipex.com>
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-Spam-Score-a.painless.aa.net.uk: -4.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: Sat, 06 Apr 2013 20:26:09 -0000

UmlnaHQuLiB0aGV5IGFyZSBtaW5kIGV4cGFuZGluZyBkcnVncy4gIEVzc2VudGlhbCBmb3Iga2Vl
cGluZyB1cyBzYW5lLgoKL0Vsd3luCgpTZW50IGZyb20gbXkgQVNVUyBQYWQKCiJTdGV3YXJ0IEJy
eWFudCAoc3RicnlhbnQpIiA8c3RicnlhbnRAY2lzY28uY29tPiB3cm90ZToKCj4KPgo+U2VudCBm
cm9tIG15IGlQYWQKPgo+T24gNiBBcHIgMjAxMywgYXQgMTQ6MDQsICJBYmR1c3NhbGFtIEJhcnl1
biIgPGFiZHVzc2FsYW1iYXJ5dW5AZ21haWwuY29tPiB3cm90ZToKPgo+PiAKPj4gSWYgdGhlIGRh
dGUgaXMKPj4gc3BlY2lhbCB0aGVuIHRob2VzIFJGQ3MgU0hPVUxEIGJlICpoaXN0b3JpY2FsKi4K
Pj4gCj4KPlN1cmVseSB0aGUgY29ycmVjdCByZXF1aXJlbWVudCBpcyA6Cj4KPklmIHRoZSBkYXRl
IGlzIHNwZWNpYWwgdGhlbiB0aG9zZSBSRkNzIE1VU1QgYmUgKmh5c3RlcmljYWwqLgo+Cj4tIFN0
ZXdhcnQKPgo+Cj4KPgo=


From dave@cridland.net  Sat Apr  6 14:22:36 2013
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 A278D21F890D for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.81
X-Spam-Level: 
X-Spam-Status: No, score=-2.81 tagged_above=-999 required=5 tests=[AWL=0.166,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2iB5Q07zb9Dw for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:22:34 -0700 (PDT)
Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) by ietfa.amsl.com (Postfix) with ESMTP id 5441D21F8887 for <ietf@ietf.org>; Sat,  6 Apr 2013 14:22:34 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id l10so5052090oag.2 for <ietf@ietf.org>; Sat, 06 Apr 2013 14:22:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=uyW4v4LfZoOtZSEiai3emt4G2ju9TnY1+scHe7IIHH0=; b=ZJSQ2qLmmZog7r/ODM9/esgyhMC8v7L3jG4q+cmeKi2fJr42weQLJMsL1lbcmFAMd4 o5+cK/by5obk4wf6bsnnxi7e1D/1uk3M0NFFfILAgC6kUZerZqL4cDnj2v+flwEN3MhC D3EeybDXUYspvg0u+1rVRWIzqMB9ewkufspRk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=uyW4v4LfZoOtZSEiai3emt4G2ju9TnY1+scHe7IIHH0=; b=k0NuAMcNcnEMvc3RQSdxK4jW6BUgfeCEumH3Co5HpJhRmLC34mhOsv1cO3KfIoA4EE Qqn+a60eomLNOFklJ11vRHiWRt6Vw1/f9/aobC/NhZu6VIl1xdxHql7qqsrlr8Hc3BSx KLyb/6BsTg5y7/mLf1+WT3jUkYBGtw5jmUOXO3Ivb75Wjm07AmzocgJTotF5+H0jMTCA ahU8pJyTLN+4P0uEHEXGWLFlEiZDSSxt02SKSz3J6pjfMQucumYt1WFU5l21hfIqpwKM CwNZKEEsQDkKrbo+E094t3DHuuIGLjoiT4xg8SATEyRcay4iFl5EPgfYvEb8+bJB5boI H9/w==
MIME-Version: 1.0
X-Received: by 10.60.54.6 with SMTP id f6mr5045461oep.136.1365283350722; Sat, 06 Apr 2013 14:22:30 -0700 (PDT)
Received: by 10.60.22.105 with HTTP; Sat, 6 Apr 2013 14:22:30 -0700 (PDT)
Received: by 10.60.22.105 with HTTP; Sat, 6 Apr 2013 14:22:30 -0700 (PDT)
In-Reply-To: <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com>
Date: Sat, 6 Apr 2013 22:22:30 +0100
Message-ID: <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
From: Dave Cridland <dave@cridland.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=089e011763b9234af804d9b7cd8f
X-Gm-Message-State: ALoCoQkIAtRrZMVXzBhrNe7bBYUTguiYPcGMcxgCwDbf+7fTLPy0Om1UboW0mvVHvkHnJWKjT749
Cc: "ietf@ietf.org 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: Sat, 06 Apr 2013 21:22:36 -0000

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

The message below suggests you still think that every RFC is published by
the IETF.

It's not, and this one explicitly nuts that it is not an IETF RFC at the
top.
On 6 Apr 2013 18:35, "Abdussalam Baryun" <abdussalambaryun@gmail.com> wrote:

> Hi Hector,
>
> When I read the RFC on 1 April 2013 (my first time experience) I
> noticed something is wrong (with the system or with doc-content), but
> the document does not refer to any joke. As if you receive a message
> from someone you know, but you realise that you don't know why he/she
> sending it. If it is the IETF culture, is this culture defined in any
> RFC or draft? However, don't mind culture/fun but mind its relation to
> classifications. My comments in line,
>
> On 4/6/13, Hector Santos <hsantos@isdg.net> wrote:
> > Hi Abdusalam,
> >
> > You should consider all APRIL 1 published I-D as "SPAM" and the
> > electronic mail follow ups generated in the IETF list as more wasted
> > bandwidth, time and spam.
>
> the question is not that I SHOULD consider importance for the
> published date, my question is : Does the IETF as an organisation
> consider Content of its publications? is there something in IETF as
> reference refering to such happy activity!!!, I am not sure. If yes
> there is a reference then why the management forgot to categorise the
> RFC as different from the serious work, do they just rely on the date
> 1 April.
>
> > We have too much time in our hands, boredom
> > for many, and even more wasted time if we spend time reading it - so in
> > that regard I agree with your concerns.  Who has time for all this?  Its
> > already a challenge to decipher most of the postings and wondering if
> > one is serious or not. Ignore April 1 publications. :)
>
> I never ignore any message/RFC I receive from IETF, IMO the IETF
> SHOULD consider to categorise its messages sent or documents published
> as any other publishers do for readers. However, I will follow your
> advise, but just like to comment about any faulty RFC because it is in
> the end a Request For Comment (RFC).
>
> If the documents are calling/requesting a comment that was my
> reply/comment as a reader,
>
> <Just done my job and commented don't care if things change or not>
>
> AB
>
> >
> > --
> > HLS
> >
> >
> > On 4/6/2013 9:03 AM, Abdussalam Baryun wrote:
> >> <Unclassified Message, but not Humorous>
> >>
> >> Some participants like to send messages/documents as categoried or
> >> classified, and may include in others uncategorised or unclassified.
> >> That is a reasonable approach in reasonable organisations.
> >>
> >> I see some RFCs as mentioned in [1], that they are humorous that
> >> reflect a historic culture or a behavior that some may like to do in a
> >> certain date (others may not like to do or be part of). If the date is
> >> special then thoes RFCs SHOULD be *historical*.
> >>
> >> I suggest/request that the IETF stops this humorous RFC publication or
> >> try to categories them or distinguish them from our logical
> >> work/efforts. I request if they are categorised as informational or
> >> experimental then to be obsoleted. I recommend for future RFCs of that
> >> type categories to be as *historical* not others (i.e. informational).
> >>
> >>   If those RFCs are not categorising/distinguished as unclassified or
> >> humorous, then all RFC may be affected. The reader may not be able to
> >> distinguish thoes published documents by IETF (does an organisation
> >> care about readers or users of its publications!). You may think to
> >> create a new category name for such publication published on April for
> >> that interested culture behavior.
> >>
> >> [1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
> >>
> >> Regards
> >> AB
> >>
> >>
> >
> >
>

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

<p dir=3D"ltr">The message below suggests you still think that every RFC is=
 published by the IETF.</p>
<p dir=3D"ltr">It&#39;s not, and this one explicitly nuts that it is not an=
 IETF RFC at the top.</p>
<div class=3D"gmail_quote">On 6 Apr 2013 18:35, &quot;Abdussalam Baryun&quo=
t; &lt;<a href=3D"mailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail=
.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Hector,<br>
<br>
When I read the RFC on 1 April 2013 (my first time experience) I<br>
noticed something is wrong (with the system or with doc-content), but<br>
the document does not refer to any joke. As if you receive a message<br>
from someone you know, but you realise that you don&#39;t know why he/she<b=
r>
sending it. If it is the IETF culture, is this culture defined in any<br>
RFC or draft? However, don&#39;t mind culture/fun but mind its relation to<=
br>
classifications. My comments in line,<br>
<br>
On 4/6/13, Hector Santos &lt;<a href=3D"mailto:hsantos@isdg.net">hsantos@is=
dg.net</a>&gt; wrote:<br>
&gt; Hi Abdusalam,<br>
&gt;<br>
&gt; You should consider all APRIL 1 published I-D as &quot;SPAM&quot; and =
the<br>
&gt; electronic mail follow ups generated in the IETF list as more wasted<b=
r>
&gt; bandwidth, time and spam.<br>
<br>
the question is not that I SHOULD consider importance for the<br>
published date, my question is : Does the IETF as an organisation<br>
consider Content of its publications? is there something in IETF as<br>
reference refering to such happy activity!!!, I am not sure. If yes<br>
there is a reference then why the management forgot to categorise the<br>
RFC as different from the serious work, do they just rely on the date<br>
1 April.<br>
<br>
&gt; We have too much time in our hands, boredom<br>
&gt; for many, and even more wasted time if we spend time reading it - so i=
n<br>
&gt; that regard I agree with your concerns. =A0Who has time for all this? =
=A0Its<br>
&gt; already a challenge to decipher most of the postings and wondering if<=
br>
&gt; one is serious or not. Ignore April 1 publications. :)<br>
<br>
I never ignore any message/RFC I receive from IETF, IMO the IETF<br>
SHOULD consider to categorise its messages sent or documents published<br>
as any other publishers do for readers. However, I will follow your<br>
advise, but just like to comment about any faulty RFC because it is in<br>
the end a Request For Comment (RFC).<br>
<br>
If the documents are calling/requesting a comment that was my<br>
reply/comment as a reader,<br>
<br>
&lt;Just done my job and commented don&#39;t care if things change or not&g=
t;<br>
<br>
AB<br>
<br>
&gt;<br>
&gt; --<br>
&gt; HLS<br>
&gt;<br>
&gt;<br>
&gt; On 4/6/2013 9:03 AM, Abdussalam Baryun wrote:<br>
&gt;&gt; &lt;Unclassified Message, but not Humorous&gt;<br>
&gt;&gt;<br>
&gt;&gt; Some participants like to send messages/documents as categoried or=
<br>
&gt;&gt; classified, and may include in others uncategorised or unclassifie=
d.<br>
&gt;&gt; That is a reasonable approach in reasonable organisations.<br>
&gt;&gt;<br>
&gt;&gt; I see some RFCs as mentioned in [1], that they are humorous that<b=
r>
&gt;&gt; reflect a historic culture or a behavior that some may like to do =
in a<br>
&gt;&gt; certain date (others may not like to do or be part of). If the dat=
e is<br>
&gt;&gt; special then thoes RFCs SHOULD be *historical*.<br>
&gt;&gt;<br>
&gt;&gt; I suggest/request that the IETF stops this humorous RFC publicatio=
n or<br>
&gt;&gt; try to categories them or distinguish them from our logical<br>
&gt;&gt; work/efforts. I request if they are categorised as informational o=
r<br>
&gt;&gt; experimental then to be obsoleted. I recommend for future RFCs of =
that<br>
&gt;&gt; type categories to be as *historical* not others (i.e. information=
al).<br>
&gt;&gt;<br>
&gt;&gt; =A0 If those RFCs are not categorising/distinguished as unclassifi=
ed or<br>
&gt;&gt; humorous, then all RFC may be affected. The reader may not be able=
 to<br>
&gt;&gt; distinguish thoes published documents by IETF (does an organisatio=
n<br>
&gt;&gt; care about readers or users of its publications!). You may think t=
o<br>
&gt;&gt; create a new category name for such publication published on April=
 for<br>
&gt;&gt; that interested culture behavior.<br>
&gt;&gt;<br>
&gt;&gt; [1] <a href=3D"http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC=
" target=3D"_blank">http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC</a>=
<br>
&gt;&gt;<br>
&gt;&gt; Regards<br>
&gt;&gt; AB<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
</blockquote></div>

--089e011763b9234af804d9b7cd8f--

From ulrich@herberg.name  Sat Apr  6 14:33:17 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1516E21F87E4 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZGYnjDQ8apD for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:33:15 -0700 (PDT)
Received: from mail-ve0-f172.google.com (mail-ve0-f172.google.com [209.85.128.172]) by ietfa.amsl.com (Postfix) with ESMTP id B029F21F8887 for <ietf@ietf.org>; Sat,  6 Apr 2013 14:33:15 -0700 (PDT)
Received: by mail-ve0-f172.google.com with SMTP id oz10so4439033veb.17 for <ietf@ietf.org>; Sat, 06 Apr 2013 14:33:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ZrmZETg9hMn0Hn2bgdFu1EdK5aorkJoUr3CCV6fyZZY=; b=2GMkyZ2VDZHty6jS1GH6aZUwvduMpZXAR2gCHLZQ/0IZ/pfiBxFn0PhmVvOH8FBawR Qr5F0KuuthJrMhQWzy4bwXBNHhcMaYtEh9huBUe9nflK7HZ3WCRK2lKgc6M/+InV3SND xPqMk4GnEHXwatZqcb2ffX8I3P92uZmYjRkPg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=ZrmZETg9hMn0Hn2bgdFu1EdK5aorkJoUr3CCV6fyZZY=; b=KPrDKOpzngDyfuVUSl5WSQnOqME2FrpBuX8wWLv5KJQQc4ddf6TzQ1apiCkbK8KOXi 2ag2LzpWsaHXPAGgxlAxGdFcxWob13J/YO2xbiyd7dUjaRjNNjvUH6c6Smxpmc/xU/jz 8+hSjMTTX3f4g08OrTnTLLmiBqJHEPNgDaQ6jkGlixb2t1FFmavkJjwYMzjvagI/kBjX qCAbnwg9Qz3D2ipr36+3jy5BeCUVESAM/6vGTY8E4xRJwdydWG2WLq2ZM286+U/lH/nh axuC/u51c+3mEQqo5OWesGYA69Qe0A1+Rb4AcZaHTEBBUIwmnyBDfRx8M30udFT77QhJ anAg==
MIME-Version: 1.0
X-Received: by 10.220.224.77 with SMTP id in13mr11692584vcb.12.1365283995111;  Sat, 06 Apr 2013 14:33:15 -0700 (PDT)
Received: by 10.220.40.68 with HTTP; Sat, 6 Apr 2013 14:33:15 -0700 (PDT)
In-Reply-To: <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com> <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com>
Date: Sat, 6 Apr 2013 14:33:15 -0700
Message-ID: <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
From: Ulrich Herberg <ulrich@herberg.name>
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnP/bs7jx9m8hfzJY/YT58GrCj2ClaYpDpSARcPbRuwqBGxv4mZBKOJnW+MrOoXedHHBvCN
Cc: "ietf@ietf.org Discussion" <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: Sat, 06 Apr 2013 21:33:17 -0000

Indeed. The wikipedia entry is somewhat misleading though:
http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC

"Almost every April Fools' Day (1 April) since 1989, the Internet
Engineering Task Force has published one or more humorous Request for
Comments (RFC) documents,"

and then

"The IETF accepts submission of properly formatted April Fools' Day
RFCs from the general public, and considers them for publication in
the same year if received at least two weeks prior to April
1st.[2][3]"

Ulrich

On Sat, Apr 6, 2013 at 2:22 PM, Dave Cridland <dave@cridland.net> wrote:
> The message below suggests you still think that every RFC is published by
> the IETF.
>
> It's not, and this one explicitly nuts that it is not an IETF RFC at the
> top.
>
> On 6 Apr 2013 18:35, "Abdussalam Baryun" <abdussalambaryun@gmail.com> wrote:
>>
>> Hi Hector,
>>
>> When I read the RFC on 1 April 2013 (my first time experience) I
>> noticed something is wrong (with the system or with doc-content), but
>> the document does not refer to any joke. As if you receive a message
>> from someone you know, but you realise that you don't know why he/she
>> sending it. If it is the IETF culture, is this culture defined in any
>> RFC or draft? However, don't mind culture/fun but mind its relation to
>> classifications. My comments in line,
>>
>> On 4/6/13, Hector Santos <hsantos@isdg.net> wrote:
>> > Hi Abdusalam,
>> >
>> > You should consider all APRIL 1 published I-D as "SPAM" and the
>> > electronic mail follow ups generated in the IETF list as more wasted
>> > bandwidth, time and spam.
>>
>> the question is not that I SHOULD consider importance for the
>> published date, my question is : Does the IETF as an organisation
>> consider Content of its publications? is there something in IETF as
>> reference refering to such happy activity!!!, I am not sure. If yes
>> there is a reference then why the management forgot to categorise the
>> RFC as different from the serious work, do they just rely on the date
>> 1 April.
>>
>> > We have too much time in our hands, boredom
>> > for many, and even more wasted time if we spend time reading it - so in
>> > that regard I agree with your concerns.  Who has time for all this?  Its
>> > already a challenge to decipher most of the postings and wondering if
>> > one is serious or not. Ignore April 1 publications. :)
>>
>> I never ignore any message/RFC I receive from IETF, IMO the IETF
>> SHOULD consider to categorise its messages sent or documents published
>> as any other publishers do for readers. However, I will follow your
>> advise, but just like to comment about any faulty RFC because it is in
>> the end a Request For Comment (RFC).
>>
>> If the documents are calling/requesting a comment that was my
>> reply/comment as a reader,
>>
>> <Just done my job and commented don't care if things change or not>
>>
>> AB
>>
>> >
>> > --
>> > HLS
>> >
>> >
>> > On 4/6/2013 9:03 AM, Abdussalam Baryun wrote:
>> >> <Unclassified Message, but not Humorous>
>> >>
>> >> Some participants like to send messages/documents as categoried or
>> >> classified, and may include in others uncategorised or unclassified.
>> >> That is a reasonable approach in reasonable organisations.
>> >>
>> >> I see some RFCs as mentioned in [1], that they are humorous that
>> >> reflect a historic culture or a behavior that some may like to do in a
>> >> certain date (others may not like to do or be part of). If the date is
>> >> special then thoes RFCs SHOULD be *historical*.
>> >>
>> >> I suggest/request that the IETF stops this humorous RFC publication or
>> >> try to categories them or distinguish them from our logical
>> >> work/efforts. I request if they are categorised as informational or
>> >> experimental then to be obsoleted. I recommend for future RFCs of that
>> >> type categories to be as *historical* not others (i.e. informational).
>> >>
>> >>   If those RFCs are not categorising/distinguished as unclassified or
>> >> humorous, then all RFC may be affected. The reader may not be able to
>> >> distinguish thoes published documents by IETF (does an organisation
>> >> care about readers or users of its publications!). You may think to
>> >> create a new category name for such publication published on April for
>> >> that interested culture behavior.
>> >>
>> >> [1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>> >>
>> >> Regards
>> >> AB
>> >>
>> >>
>> >
>> >

From melinda.shore@gmail.com  Sat Apr  6 14:39:42 2013
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 58A7A21F8976 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.965
X-Spam-Level: 
X-Spam-Status: No, score=-1.965 tagged_above=-999 required=5 tests=[AWL=0.634,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PXxS5Sl092Dr for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:39:41 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id AB42C21F8967 for <ietf@ietf.org>; Sat,  6 Apr 2013 14:39:41 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id y10so2561280pdj.12 for <ietf@ietf.org>; Sat, 06 Apr 2013 14:39:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mkPfRIdheWkvYklL94MhptZOA6a9L+xnwqE+p1m36/Y=; b=jEv4wKww594lumetjkbuWp1Q+JPr3KnUIIQZ15KGo8IA/CWwib4YVyTusT++C9rMET ygTESElv9ipL49inhVYEIeglGw4cOYPOiR8Q3pyep8QTFut/L9es6LlUCYzyVpM4Nllc e31D2J1V5KG0gWW2pzOdtsW1hNA0xFlqfaog5j6Dp0GJ1MxInzwP2VLdJF8NWY9OY/4U N/3+6fWCVvaT3kG5Q/Cx8ZgJGNYVPbDXOdLe3tK/Gg5OlXCqvT+rV5enT7OR3NT8HWUf XcYzWYEvPxK+uFCps0q7JzraBuCrPq41J8w3q7rmsdvltiYWoQOOqDTo8f7/XEhN5ylF LZTw==
X-Received: by 10.67.10.228 with SMTP id ed4mr10015744pad.41.1365284381312; Sat, 06 Apr 2013 14:39:41 -0700 (PDT)
Received: from spandex.local (66-230-112-119-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.119]) by mx.google.com with ESMTPS id yr10sm22912218pab.6.2013.04.06.14.39.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 06 Apr 2013 14:39:40 -0700 (PDT)
Message-ID: <51609619.6050903@gmail.com>
Date: Sat, 06 Apr 2013 13:39:37 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com> <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com> <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com>
In-Reply-To: <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@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: Sat, 06 Apr 2013 21:39:42 -0000

On 4/6/13 1:33 PM, Ulrich Herberg wrote:
> Indeed. The wikipedia entry is somewhat misleading though:
> http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC

Fix it or ignore it.  Wikipedia is neither authoritative nor
reliable.

Melinda



From abdussalambaryun@gmail.com  Sat Apr  6 14:58:08 2013
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 7105821F8967 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level: 
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[AWL=-0.249, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uT1Q+Ov+pZDH for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:58:07 -0700 (PDT)
Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7A48221F85D6 for <ietf@ietf.org>; Sat,  6 Apr 2013 14:58:07 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id g10so2326811pdj.6 for <ietf@ietf.org>; Sat, 06 Apr 2013 14:58:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6txPZ/CTPnZB2Kndf2p2k5D5tD0gslcS+nFGhquraHs=; b=nZdgvTudj771lbSdlann8h5S0oH/wnp4RpdZ7xI+FkSr5bya2H9x0SUMB06g14rd1w 4eXjjICiF+DestJTwYyzD5wtWSe8WKfSaxdnRtZMc/h519CFOGLvN+m3uPITt3Q2S9Ky fHekVBqLrHWf2HenVv9XPZpir0BgCkNpViBMSKusS2icAJ65fzPTno6BNrJvdm957b2u Q0YVlBc5CR2jJ5ywBWeoZs7SwowO6czR0qEFVlXlEXFe+1nqDm/SaHfM/32xEYeP1PT0 fpo6XhnEOgZ8sRgFno5PDTELa0V4RTX7x0aAoMDi4Td/I3tGHh3KjHMHItR9ek3WytVc 9AIg==
MIME-Version: 1.0
X-Received: by 10.66.222.228 with SMTP id qp4mr23134052pac.113.1365285487014;  Sat, 06 Apr 2013 14:58:07 -0700 (PDT)
Received: by 10.68.33.132 with HTTP; Sat, 6 Apr 2013 14:58:06 -0700 (PDT)
In-Reply-To: <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com> <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com> <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com>
Date: Sat, 6 Apr 2013 23:58:06 +0200
Message-ID: <CADnDZ8_yo8E5_bN9DRw6M3Hq3FVUMdabACGvfq2EKQxGMeEOrw@mail.gmail.com>
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated April the first
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Ulrich Herberg <ulrich@herberg.name>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org 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: Sat, 06 Apr 2013 21:58:08 -0000

If we read each document in the world we know the answer; who owns the
copyright for these documents? so only owner can update it or to
change category name as per proposed,

AB

On 4/6/13, Ulrich Herberg <ulrich@herberg.name> wrote:
> Indeed. The wikipedia entry is somewhat misleading though:
> http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>
> "Almost every April Fools' Day (1 April) since 1989, the Internet
> Engineering Task Force has published one or more humorous Request for
> Comments (RFC) documents,"
>
> and then
>
> "The IETF accepts submission of properly formatted April Fools' Day
> RFCs from the general public, and considers them for publication in
> the same year if received at least two weeks prior to April
> 1st.[2][3]"
>
> Ulrich
>
> On Sat, Apr 6, 2013 at 2:22 PM, Dave Cridland <dave@cridland.net> wrote:
>> The message below suggests you still think that every RFC is published by
>> the IETF.
>>
>> It's not, and this one explicitly nuts that it is not an IETF RFC at the
>> top.
>>
>> On 6 Apr 2013 18:35, "Abdussalam Baryun" <abdussalambaryun@gmail.com>
>> wrote:
>>>
>>> Hi Hector,
>>>
>>> When I read the RFC on 1 April 2013 (my first time experience) I
>>> noticed something is wrong (with the system or with doc-content), but
>>> the document does not refer to any joke. As if you receive a message
>>> from someone you know, but you realise that you don't know why he/she
>>> sending it. If it is the IETF culture, is this culture defined in any
>>> RFC or draft? However, don't mind culture/fun but mind its relation to
>>> classifications. My comments in line,
>>>
>>> On 4/6/13, Hector Santos <hsantos@isdg.net> wrote:
>>> > Hi Abdusalam,
>>> >
>>> > You should consider all APRIL 1 published I-D as "SPAM" and the
>>> > electronic mail follow ups generated in the IETF list as more wasted
>>> > bandwidth, time and spam.
>>>
>>> the question is not that I SHOULD consider importance for the
>>> published date, my question is : Does the IETF as an organisation
>>> consider Content of its publications? is there something in IETF as
>>> reference refering to such happy activity!!!, I am not sure. If yes
>>> there is a reference then why the management forgot to categorise the
>>> RFC as different from the serious work, do they just rely on the date
>>> 1 April.
>>>
>>> > We have too much time in our hands, boredom
>>> > for many, and even more wasted time if we spend time reading it - so
>>> > in
>>> > that regard I agree with your concerns.  Who has time for all this?
>>> > Its
>>> > already a challenge to decipher most of the postings and wondering if
>>> > one is serious or not. Ignore April 1 publications. :)
>>>
>>> I never ignore any message/RFC I receive from IETF, IMO the IETF
>>> SHOULD consider to categorise its messages sent or documents published
>>> as any other publishers do for readers. However, I will follow your
>>> advise, but just like to comment about any faulty RFC because it is in
>>> the end a Request For Comment (RFC).
>>>
>>> If the documents are calling/requesting a comment that was my
>>> reply/comment as a reader,
>>>
>>> <Just done my job and commented don't care if things change or not>
>>>
>>> AB
>>>
>>> >
>>> > --
>>> > HLS
>>> >
>>> >
>>> > On 4/6/2013 9:03 AM, Abdussalam Baryun wrote:
>>> >> <Unclassified Message, but not Humorous>
>>> >>
>>> >> Some participants like to send messages/documents as categoried or
>>> >> classified, and may include in others uncategorised or unclassified.
>>> >> That is a reasonable approach in reasonable organisations.
>>> >>
>>> >> I see some RFCs as mentioned in [1], that they are humorous that
>>> >> reflect a historic culture or a behavior that some may like to do in
>>> >> a
>>> >> certain date (others may not like to do or be part of). If the date
>>> >> is
>>> >> special then thoes RFCs SHOULD be *historical*.
>>> >>
>>> >> I suggest/request that the IETF stops this humorous RFC publication
>>> >> or
>>> >> try to categories them or distinguish them from our logical
>>> >> work/efforts. I request if they are categorised as informational or
>>> >> experimental then to be obsoleted. I recommend for future RFCs of
>>> >> that
>>> >> type categories to be as *historical* not others (i.e.
>>> >> informational).
>>> >>
>>> >>   If those RFCs are not categorising/distinguished as unclassified or
>>> >> humorous, then all RFC may be affected. The reader may not be able to
>>> >> distinguish thoes published documents by IETF (does an organisation
>>> >> care about readers or users of its publications!). You may think to
>>> >> create a new category name for such publication published on April
>>> >> for
>>> >> that interested culture behavior.
>>> >>
>>> >> [1] http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>>> >>
>>> >> Regards
>>> >> AB
>>> >>
>>> >>
>>> >
>>> >
>

From ynir@checkpoint.com  Sat Apr  6 14:59:15 2013
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 A08CF21F861B for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:59:15 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96Tsp-pQqhcL for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 14:59:15 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id D0C4421F85F5 for <ietf@ietf.org>; Sat,  6 Apr 2013 14:59:14 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r36Lx7KX008825; Sun, 7 Apr 2013 00:59:07 +0300
X-CheckPoint: {51609879-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Sun, 7 Apr 2013 00:59:06 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Ulrich Herberg <ulrich@herberg.name>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
Thread-Topic: Comments for Humorous RFCs or uncategorised RFCs or dated April	the first
Thread-Index: AQHOMt71wZk0wMSj6UqCFaEVWTiTYZjJQlmAgAA/TgCAAAMBgIAABzcA
Date: Sat, 6 Apr 2013 21:59:05 +0000
Message-ID: <5463E929-0889-4C96-AC0E-28A37CFC4F4B@checkpoint.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com> <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com> <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com>
In-Reply-To: <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.76]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B908E22DE893034DB68EDDCB9563FC5C@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Abdussalam Baryun <abdussalambaryun@gmail.com>, "ietf@ietf.org 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: Sat, 06 Apr 2013 21:59:15 -0000

On Apr 7, 2013, at 12:33 AM, Ulrich Herberg <ulrich@herberg.name> wrote:

> Indeed. The wikipedia entry is somewhat misleading though:
> http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>=20
> "Almost every April Fools' Day (1 April) since 1989, the Internet
> Engineering Task Force has published one or more humorous Request for
> Comments (RFC) documents,"
>=20
> and then
>=20
> "The IETF accepts submission of properly formatted April Fools' Day
> RFCs from the general public, and considers them for publication in
> the same year if received at least two weeks prior to April
> 1st.[2][3]"

Fixed


From hsantos@isdg.net  Sat Apr  6 15:21:12 2013
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 882A821F8A27 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 15:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.272
X-Spam-Level: 
X-Spam-Status: No, score=-101.272 tagged_above=-999 required=5 tests=[AWL=0.405, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SXc4hXV35C1z for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 15:21:12 -0700 (PDT)
Received: from catinthebox.net (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B133321F89E1 for <ietf@ietf.org>; Sat,  6 Apr 2013 15:21:11 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1118; t=1365286866; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=bb/XqjF e2PqIkeCNryIDaTPNFfM=; b=pSbIdoZeMwlrJuo/YEo78JwksTRbza0rs3fFCaP rhVrLTKhinHSBLQ7FGiO6tdgyjm7SD28G0lITxe5M2mKjgdffk6PI01MIYUPLLwv 1+WN502fbMDtsy3i0tg8SzCwSOUGjj09xrpM3z/MnENsqI4lREfbGsYznfA1YCi2 +ggw=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 06 Apr 2013 17:21:06 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4080573844.676.2072; Sat, 06 Apr 2013 17:21:05 -0500
Message-ID: <51609F9B.6040703@isdg.net>
Date: Sat, 06 Apr 2013 18:20:11 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Scott Brim <swb@internet2.edu>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <516045EC.3090900@internet2.edu>
In-Reply-To: <516045EC.3090900@internet2.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 06 Apr 2013 22:21:12 -0000

On 4/6/2013 11:57 AM, Scott Brim wrote:
> On 04/06/13 11:52, Hector Santos allegedly wrote:
>> Hi Abdusalam,
>>
>> You should consider all APRIL 1 published I-D as "SPAM" and the
>> electronic mail follow ups generated in the IETF list as more wasted
>> bandwidth, time and spam.   We have too much time in our hands, boredom
>> for many, and even more wasted time if we spend time reading it - so in
>> that regard I agree with your concerns.  Who has time for all this?  Its
>> already a challenge to decipher most of the postings and wondering if
>> one is serious or not. Ignore April 1 publications. :)
>
> It's called having a shared culture.  The IETF could even generate
> friendship, if allowed.

Sure. I chose to ignore the April 1 I-Ds coming into a public newsgroup 
view of the IETF drafts [1].  There were a few, if just be the title of 
it, it seem like a joke, "draft-draft-draft" so you ignore it.  I can 
understand what Abdusalem was concern can occur - ignorance.

I don't have the time for it. I hope its not a diversity issue. :)

--
HLS

[1]news://news.winserver.com/ietf-drafts


From mrw@lilacglade.org  Sat Apr  6 22:35:57 2013
Return-Path: <mrw@lilacglade.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 E5C2221F8AE3 for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 22:35:57 -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.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wwwbv4uXORhh for <ietf@ietfa.amsl.com>; Sat,  6 Apr 2013 22:35:57 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 4BC5E21F87B7 for <ietf@ietf.org>; Sat,  6 Apr 2013 22:35:57 -0700 (PDT)
Received: from new-host-3.home (pool-71-184-79-25.bstnma.fios.verizon.net [71.184.79.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.painless-security.com (Postfix) with ESMTPSA id 8C7F720115; Sun,  7 Apr 2013 01:34:35 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_4DAAC1D7-C2A6-4685-8109-C2758EDBF473"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated April the first
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <CADnDZ8_yo8E5_bN9DRw6M3Hq3FVUMdabACGvfq2EKQxGMeEOrw@mail.gmail.com>
Date: Sun, 7 Apr 2013 01:35:57 -0400
Message-Id: <0722FBCE-8FC7-4B48-B189-0617216C5E37@lilacglade.org>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com> <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com> <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com> <CADnDZ8_yo8E5_bN9DRw6M3Hq3FVUMdabACGvfq2EKQxGMeEOrw@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org 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: Sun, 07 Apr 2013 05:35:58 -0000

--Apple-Mail=_4DAAC1D7-C2A6-4685-8109-C2758EDBF473
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Apr 6, 2013, at 5:58 PM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> If we read each document in the world we know the answer; who owns the
> copyright for these documents? so only owner can update it or to
> change category name as per proposed,
>=20

All of the (at least recent) RFCs have copyright notices in them.  In =
the case of RFC 6921, the copyright says:
   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.
Margaret


--Apple-Mail=_4DAAC1D7-C2A6-4685-8109-C2758EDBF473
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><div>On Apr 6, 2013, at 5:58 PM, Abdussalam Baryun &lt;<a href="mailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">If we read each document in the world we know the answer; who owns the<br>copyright for these documents? so only owner can update it or to<br>change category name as per proposed,<br><br></blockquote><div><br></div>All of the (at least recent) RFCs have copyright notices in them. &nbsp;In the case of RFC 6921, the copyright says:</div><div><pre style="word-wrap: break-word; white-space: pre-wrap; ">   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.</pre><div>Margaret</div><div><br></div></div></body></html>
--Apple-Mail=_4DAAC1D7-C2A6-4685-8109-C2758EDBF473--

From l.wood@surrey.ac.uk  Sun Apr  7 04:24:49 2013
Return-Path: <l.wood@surrey.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 6346221F8A4E for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 04:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[AWL=1.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thy7LBGtDmEE for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 04:24:47 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.119]) by ietfa.amsl.com (Postfix) with ESMTP id EDAFC21F877A for <ietf@ietf.org>; Sun,  7 Apr 2013 04:24:45 -0700 (PDT)
Received: from [193.109.255.147:4315] by server-15.bemta-14.messagelabs.com id 70/A5-14305-C7751615; Sun, 07 Apr 2013 11:24:44 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-3.tower-72.messagelabs.com!1365333884!7238179!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7354 invoked from network); 7 Apr 2013 11:24:44 -0000
Received: from unknown (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-3.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 7 Apr 2013 11:24:44 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Sun, 7 Apr 2013 12:24:44 +0100
From: <l.wood@surrey.ac.uk>
To: <elwynd@dial.pipex.com>, <stbryant@cisco.com>
Date: Sun, 7 Apr 2013 12:24:43 +0100
Subject: RE: Comments for Humorous RFCs or uncategorised RFCs or dated April the	first
Thread-Topic: Comments for Humorous RFCs or uncategorised RFCs or dated April	the	first
Thread-Index: Ac4zBQ4x6W+3VKHZQom6XIbP0JQljQAe9hH+
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E56@EXMB01CMS.surrey.ac.uk>
References: <4xe3ug28nhgoau4ssaiigfcj.1365279964452@email.android.com>
In-Reply-To: <4xe3ug28nhgoau4ssaiigfcj.1365279964452@email.android.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org, 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, 07 Apr 2013 11:24:49 -0000

All April 1 RFCs should not be categorised historical but=20
Category: CLASSIFIED TOP SECRET EYES ONLY NEED TO KNOW SIPRNET COBRA VATICA=
N FNORD KNITTING PATTERN
Distribution: Unlimited.

We should also start a December 25 series. With something on SOCKS.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Elwyn Davi=
es [elwynd@dial.pipex.com]
Sent: 06 April 2013 21:26
To: Stewart Bryant (stbryant)
Cc: ietf; Abdussalam Baryun
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated Apri=
l    the     first

Right.. they are mind expanding drugs.  Essential for keeping us sane.

/Elwyn

Sent from my ASUS Pad

"Stewart Bryant (stbryant)" <stbryant@cisco.com> wrote:

>
>
>Sent from my iPad
>
>On 6 Apr 2013, at 14:04, "Abdussalam Baryun" <abdussalambaryun@gmail.com> =
wrote:
>
>>
>> If the date is
>> special then thoes RFCs SHOULD be *historical*.
>>
>
>Surely the correct requirement is :
>
>If the date is special then those RFCs MUST be *hysterical*.
>
>- Stewart
>
>
>
>

From ynir@checkpoint.com  Sun Apr  7 04:59:37 2013
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 629A821F84D4 for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 04:59:37 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qpyuhDB+iXau for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 04:59:36 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 93FBF21F84D9 for <ietf@ietf.org>; Sun,  7 Apr 2013 04:59:33 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r37BxSvw014400 for <ietf@ietf.org>; Sun, 7 Apr 2013 14:59:32 +0300
X-CheckPoint: {51615D64-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Sun, 7 Apr 2013 14:59:30 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: ietf <ietf@ietf.org>
Subject: RE: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated	April the first
Thread-Topic: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated	April the first
Thread-Index: AQHOMtLCY/W/har6j0iUclYVgtQStJjJRiaAgAFgukA=
Date: Sun, 7 Apr 2013 11:59:30 +0000
Message-ID: <4613980CFC78314ABFD7F85CC3027721119FF4B7@IL-EX10.ad.checkpoint.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <577E2C0B-16F5-47D2-8D71-7A9D914ACF23@kumari.net> <CADnDZ8_p=hp+yP5YTso72LO6MEuONxpdw-QBsTCtXn+v9eVpaw@mail.gmail.com>
In-Reply-To: <CADnDZ8_p=hp+yP5YTso72LO6MEuONxpdw-QBsTCtXn+v9eVpaw@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.121]
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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Apr 2013 11:59:37 -0000

I mostly share the sentiment that this is just humor, so what's the harm.

That said, I did at one point have to exercise my diplomatic skills when I =
got forwarded a customer (nameless here for evermore) question about whethe=
r support for RFC 3514 was on our roadmap.

While the people on this list generally "get" the joke, not all readers of =
RFCs are part of this group. The recent RFC 6919 is full of in-jokes (or pe=
rhaps, in-roast?) that many outside the IETF will not get. Anyways, it is a=
n issue, but I think these are too much fun to do away with them.

Yoav

From cabo@tzi.org  Sun Apr  7 06:03:29 2013
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 3048221F8CD8; Sun,  7 Apr 2013 06:03:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.448
X-Spam-Level: 
X-Spam-Status: No, score=-105.448 tagged_above=-999 required=5 tests=[AWL=-0.688, BAYES_05=-1.11, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2uYw9M+YAVQ; Sun,  7 Apr 2013 06:03:26 -0700 (PDT)
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 EA71E21F8C45; Sun,  7 Apr 2013 06:03:25 -0700 (PDT)
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.4/8.14.4) with ESMTP id r37D3BaS023269; Sun, 7 Apr 2013 15:03:11 +0200 (CEST)
Received: from [192.168.217.105] (p54894EAC.dip.t-dialin.net [84.137.78.172]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 547D13B2B; Sun,  7 Apr 2013 15:03:10 +0200 (CEST)
Subject: Re: [core] tsv-dir review of draft-ietf-core-coap-14
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <2A886F9088894347A3BE0CC5B7A85F3E9AB12A6F16@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Date: Sun, 7 Apr 2013 15:03:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EAD87339-D57D-49CB-991D-564C3DFE8B97@tzi.org>
References: <2A886F9088894347A3BE0CC5B7A85F3E9AB12A6F16@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1503)
Cc: "core-chairs@tools.ietf.org" <core-chairs@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, The IESG <iesg@ietf.org>, "core@ietf.org" <core@ietf.org>, "tsv-dir@ietf.org" <tsv-dir@ietf.org>, "draft-ietf-core-coap@tools.ietf.org" <draft-ietf-core-coap@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Apr 2013 13:03:29 -0000

Michael,

thank you for this thoughtful and extensive review.

We have turned nine of the items below into eight tickets, #287 to
#294 (see in-line references below), that will be processed along with
the other IETF last-call tickets and turned into
draft-ietf-core-coap-15 in the next few days.

Below, please find a detailed discussion of the review comments.

Gr=FC=DFe, Carsten


        Review - good news:

        I have reviewed few selected aspects in draft-ietf-core-coap-09
        =
(http://www.ietf.org/mail-archive/web/core/current/msg03280.html). I
        confirm that those past concerns are sufficiently addressed by =
this
        document.

Thank you, that is good to know.

        Review - not so good news:

        * General: In a nutshell, this document proposes a rather =
lightwight
         protocol that provides a subset of TCP/HTTP transport.

The authors don't agree with this view at all.
CoAP is a application layer transfer protocol.
It provides very few transport features.
It is not very productive to compare it to TCP.
It can be used for certain applications that could theoretically also
be supported by HTTP over TCP, if the complexity of these protocols
didn't get in the way.
We sense very little danger that Web developers will run out and
abandon HTTP and TCP in droves when CoAP is published.

         In order to
         reduce message sizes and implementation complexity, the =
protocol
         sacrifies many TCP/HTTP features. But I really had a hard time
         figuring out what the protocol as defined in this document does
         *not* provide, in particular in the message layer. At first =
sight,
         the CoAP protocol as defined in this document lacks features =
such as:

         - Support for messages exceeding the path MTU

         - Byte stream transport with segmentation and reassembly

         - Flow control

         - Congestion control for non-confirmable messages (this must =
IMHO be
           fixed)

         Further typical TCP features are pretty much left to the
         implementation or to extensions which will make the protocol =
more
         complex (imho, as complex as TCP):

         - In-order delivery of unconfirmed messages (for confirmed =
messages,
           delivery seems to be in-order right now if the implementation
           indeed complies to the mandated limit of one out-standing
           transaction per destination, but any application requiring a =
data
           transfer of more than 1KB will need something better)

         - Strong protection against message duplication (in particular =
if
           some checks are disabled based on cross-layer assumptions, =
which
           is allowed by this spec)

         - Non-trivial transport features for multicast

         - Security and DoS protection (mostly out-of-scope of this =
review)

         These aspects are further detailed below with specific text
         references.

         =3D> I think that the document needs a disclaimer in Section 1 =
that
         explicitly explains what users cannot expect from the CoAP base
         protocol (say, compared to a light-weight HTTP/TCP =
implementation
         with HTTP compression and the absolute minimum set of TCP =
features).

Disagree.  That is not the job of a protocol specification.

RFC 2616 does not have a disclaimer that explains how it is inferior
to FTP, even though both can be used for related applications and FTP
clearly has a number of desirable features that HTTP lacks (some of
which were later defined in additional protocols on top of HTTP, e.g.,
WebDAV, and some that apparently weren't actually needed by HTTP users).

Creating such a section would already fail at the definition of the
protocol stack against which CoAP is to be compared to, as a
"light-weight HTTP/TCP implementation with HTTP compression" is
neither standardized nor even possible within the confines of the
constrained nodes addressed by CoAP.

Once written, such a section would almost immediately be dated as
implementers find new ways to solve old problems, and as additional
specifications are written (cf. WebDAV above).

        * General: The message layer, which basically provides a =
transport
         protocol service, is in parts only vaguely specified, and many
         transport-related protocol features can be overwriten by
         implementation or environment-specific settings, or by future
         extensions drafts. This makes it very difficult to review the
         protocol regarding completeness and robustness, such as =
atypical
         packet arrival patterns, reordering, and other corner cases =
that
         fundamentally matter for a transport protocol design. I believe =
that
         the protocol is simple enough that a full description of the =
state
         engine and event processing would be possible (like RFC 793 =
Section
         3.9. Event Processing). But without a rigourous specification, =
it is
         difficult to figure out what a CoAP implementation would do in =
many
         corner cases, and if interoperable implementations would =
interprete
         the spec in the same way.

As is apparent from interops, this was less of a problem for
implementers so far.  We have drafts that discuss implementation
approaches in LWIG, and these will be developed further.  I'm not a
big fan of an FDT requirement for an initial protocol specification,
this was part of what killed OSI.

          =3D> The following list of open issues is almost certainly
          incomplete; other TSV experts might identify further problems.

        * Section 4.2

             A CoAP endpoint that sent a Confirmable message MAY give up =
in
             attempting to obtain an ACK even before the MAX_RETRANSMIT
             counter value is reached: E.g., the application has =
canceled the
             request as it no longer needs a response, or there is some =
other
             indication that the CON message did arrive.  In particular, =
a
             CoAP request message may have elicited a separate response, =
in
             which case it is clear to the requester that only the ACK =
was
             lost and a retransmission of the request would serve no =
purpose.
             However, a responder MUST NOT in turn rely on this =
cross-layer
             behavior from a requester, i.e. it SHOULD retain the state =
to
             create the ACK for the request, if needed, even if a =
Confirmable
             response was already acknowledged by the requester.

         =3D> I think that this situation can also occur during an =
attack with
         spoofed addresses, i. e., it is not "clear" that the ACK was
         lost. In that case, retransmitting the request may even be the
         better alternative, in order to identify the attack. As already
         mentioned, state diagrams and a clear event handling would help =
to
         identify such corner cases (there may be more than this =
specific
         one). This would also simplify discussion when it is indeed =
save to
         release state information.

I don't understand the concern.  This is a comment on a common
implementation optimization.  There are multiple ways to counter an
attack, the preferable one of which is to use DTLS security.

        * Section 4.3

             At the CoAP level, there is no way for the sender to detect =
if a
             Non- confirmable message was received or not.  A sender MAY
             choose to transmit multiple copies of a Non-confirmable =
message
             within MAX_TRANSMIT_SPAN, or the network may duplicate the
             message in transit.

          =3D> This section lacks any guidance on how frequently
          non-confirmable messages may be sent. Section 4.7 mandates a
          maximum PROBING_RATE for congestion control. With the default
          parameters, MAX_TRANSMIT_SPAN is 45s, and PROBING_RATE is 1
          Byte/second, i. e., for messages larger than 45 Byte, the =
limit for
          multiple copies is given by MESSAGE_SIZE/PROBING_RATE, not by
          MAX_TRANSMIT_SPAN.

Indeed, a reference to 4.7 wouldn't hurt here. [#288] (Sending multiple
copies that are spaced more than MAX_TRANSMIT_SPAN may defeat the
duplicate detection.  Messages that benefit from saturation are often
short discovery requests, so extremely very low value we chose for
PROBING_RATE may not hurt in practice.)

        `* Section 4.5

          o A constrained server MAY even want to relax this requirement =
for
             certain non-idempotent requests if the application =
semantics
             make this trade-off favorable.  For example, if the result =
of a
             POST request is just the creation of some short-lived state =
at
             the server, it may be less expensive to incur this effort
             multiple times for a request than keeping track of whether =
a
             previous transmission of the same request already was =
processed.

         =3D> I think that this section must stronger state that both =
endpoints
         must agree on those modified semantics. Otherwise, it is not =
clear
         to me whether the client and server implementations would =
indeed be
         interoperable, in particular, if they are implemented =
independently
         and thus make different assumptions. The client here asked for
         reliable transfer, but the server actually ignores that =
requests for
         reliabile transfer, right?

It is the purview of the server how it implements its resources.  The
server can unilaterally decide that its resources don't need this
processing.  There is no interoperability concern with this.  The
keyword is "if the application semantics make this trade-off
favorable".  This kind of latitude may be unusual for a protocol
specification, but it is often what makes a constrained implementation
possible.

        * Section 4.6

              Message sizes are also of considerable importance to
              implementations on constrained nodes.  Many =
implementations
              will need to allocate a buffer for incoming messages.  If =
an
              implementation is too constrained to allow for allocating =
the
              above-mentioned upper bound, it could apply the following
              implementation strategy: Implementations receiving a =
datagram
              into a buffer that is too small are usually able to =
determine
              if the trailing portion of a datagram was discarded and to
              retrieve the initial portion.  So, if not all of the =
payload,
              at least the CoAP header and options are likely to fit =
within
              the buffer.  A server can thus fully interpret a request =
and
              return a 4.13 (Request Entity Too Large) response code if =
the
              payload was truncated.  A client sending an idempotent =
request
              and receiving a response larger than would fit in the =
buffer
              can repeat the request with a suitable value for the Block
              Option [I-D.ietf-core-block].

         =3D> This document must include a discussion on flow control, =
i. e.,
         what happens if the receiver's receive buffer is full or if an
         application stalls and does not consume data for longer time
         (exceeding the retransmission timeout).

         Explanation:

         For constrainted devices with small receive buffers and
         communication with more than one endpoint, it seems to me =
pretty
         likely that at some points in time no receive buffer is
         available. The protocol spec does not discuss what happens if =
the
         buffer is to small to process even the header, and what the =
behavior
         of the receiver should be (silently dropping the incoming =
message?

Yes.

         sending a RST? does the behavior depend on whether it is CON or
         NON?). I think that this spec must provide guidance how the =
protocol
         deals with buffer shortage.

That is an implementation concern.

         TCP's solution to this kind of situations is flow control by =
the
         receive window.

Actually, TCP's solution is dropping the SYN.

         In CoAP, there seems to be an implicit assumption
         that messages can either always be "somehow" processed by a =
receiver
         or savely be dropped. As long as the protocol allows only one
         outstanding transaction per destination, and allocates =
dedicated
         receive buffer for a full CoAP packet for each destination,
         out-of-my head this indeed seems to work without deadlocks =
because
         we basically have the alternating-bit-protocol. But in more =
complex
         situations with small buffer sizes (e. g., multiple
         transactions/applications sharing one buffer, or =
insequence-delivery
         for more than one transaction), I think that the protocol could =
run
         into deadlocks because it cannot prevent a sender from sending =
or
         retransmitting data into a receiver not having any receive =
buffer.

         I am not an expert on formal protocol verification, i. e., I =
cannot
         provide an exact specification for the minimum set of =
implementation
         requirements that savely prevents deadlock (also see my other
         remarks on state engine specification). But I am really =
concerned
         that the document does not even mention the terms "flow =
control",
         "buffer sizing", etc.

There is no way to define the CoAP protocol such that it prevents
implementers from painting themselves into a corner.

Again, I would expect much of this discussion to turn up in future
LWIG documents.  Work is being done one some of these issues in
draft-ietf-lwig-guidance, draft-kovatsch-lwig-class1-coap, and the
(currently expired) draft-castellani-lwig-coap-separate-responses.  In
Orlando, there was considerable energy between the authors of these
documents to get more documentation done; a first authors' draft is
already in the LWIG SVN and is actively being worked on.

        * Section 4.7

             In order not to cause congestion, Clients (including =
proxies)
             MUST strictly limit the number of simultaneous outstanding
             interactions that they maintain to a given server =
(including
             proxies) to NSTART.  An outstanding interaction is either a =
CON
             for which an ACK has not yet been received but is still =
expected
             (message layer) or a request for which neither a response =
nor an
             Acknowledgment message has yet been received but is still
             expected (which may both occur at the same time, counting =
as one
             outstanding interaction).  The default value of NSTART for =
this
             specification is 1.

         =3D> This section MUST clarify congestion control for =
non-confirmable
         messages. I miss a clear recommendation how frequently a sender =
is
         allowed to send non-confirmable messages if there is no other
         feedback. I think that a maximum data rate of PROBING_RATE =
would be
         reasonable and save, but I recall some discussion on other =
proposals
         (e. g., mandating a confirmable message every X non-confirmable
         messages, etc.).

That specific discussion would be part of the -observe extension.  The
base protocol is stuck at PROBING_RATE.

        * Section 4.8.2

                  o PROCESSING_DELAY is the time a node takes to turn =
around
                     a Confirmable message into an acknowledgement.  We
                     assume the node will attempt to send an ACK before
                     having the sender time out, so as a conservative
                     assumption we set it equal to ACK_TIMEOUT.

         =3D> I assume that the spec wants to say "a receiver MUST have =
sent an
         ACK after PROCESSING_DELAY"? I have not found that requirement
         elsewhere in the document. If it is not a MUST requirement, the
         calculations involving PROCESSING_DELAY seem to be not the =
worst
         case and are therefore not really useful for worst-case =
analysis.

The worst-case analysis is about as robust as that for TCP 2MSL.
There is absolutely no assurance in IP that data won't be in the
network longer than MSL (and I sure have measured latencies way
higher).  The analysis describes what we try to guard against, not the
absolute worst case.

But I agree that the discussion of when to piggy-back (5.2.1) could
include a mention of PROCESSING_DELAY. [#290]

        * Section 5.3.1

             A token is intended for use as a client-local identifier =
for
             differentiating between concurrent requests (see Section =
5.3);
             it could have been called a "request ID".

         =3D> Im my understanding, concurrent requests are not allowed =
by this
         spec, i. e., why does this document not recommend to use an =
empty
         token as long as NSTART=3D1? It apparently just wastes scace =
bandwidth
         if there is only one allowed request to a destination. As an
         editorial note, this reference to Section 5.3 is strange here; =
this
         is the only paragraph in the document where concurrent requests =
are
         mentioned.

Concurrent requests are allowed as long as there has been a return
message.  E.g., a client could send a CON GET, get an empty ACK
(resetting the outstanding count to zero), and then decide to do
another CON GET (and receive another empty ACK) before the response
CON for the first request arrives.  Which request does the response
reply to?

        * Section 5.3.2

             The exact rules for matching a response to a request are as
             follows:

             1.  The source endpoint of the response MUST be the same as =
the
                 destination endpoint of the original request.

             2.  In a piggy-backed response, both the Message ID of the
                 Confirmable request and the Acknowledgement, and the =
token
                 of the response and original request MUST match.  In a
                 separate response, just the token of the response and
                 original request MUST match.

             In case a message carrying a response is unexpected (the =
client
             is not waiting for a response from the identified endpoint, =
at
             the endpoint addressed, and/or with the given token), the
             response is rejected (Section 4.2, Section 4.3).

         =3D> To me, the CoAP message processing seems underspecified. =
What
         really happens if either the msg and token mismatch (two =
entirely
         different cases), i. e., what will the endpoint put into the =
RST
         message? Section 4.2 states "The Acknowledgement message MUST =
echo
         the Message ID of the Confirmable message, and MUST carry a =
response
         or be empty (see Section 5.2.1 and Section 5.2.2)."; based on =
text I
         cannot figure out what the response would be. For =
interoperability
         between implementations, this sort of events matter.

There is some discussion of rejecting messages in 4.2.
There is relatively little need for details here as there is no
connection state to maintain or fix up once a message has been rejected.

         =3D> Would it be allowed to send back a response both by a CON =
and a
         NON message, with the same token, but different message IDs? If =
so,
         how would the matching deal with this?

Yes.  This is one of the things that -observe might be doing.
(Note that a message can have more than one response.)

        * Section 5.3.2

          Implementation Note: A client that receives a response in a =
CON
             message may want to clean up the message state right after
             sending the ACK.  If that ACK is lost and the server =
retransmits
             the CON, the client may no longer have any state to =
correlate
             this response to, making the retransmission an unexpected
             message; the client may send a Reset message so it does not
             receive any more retransmissions.  This behavior is normal =
and
             not an indication of an error.  (Clients that are not
             aggressively optimized in their state memory usage will =
still
             have message state that will identify the second CON as a
             retransmission.  Clients that actually expect more messages =
from
             the server [I-D.ietf-core-observe] will have to keep state =
in
             any case.)

         =3D> I am confused by this sort of argument of removing state. =
This
         statement probably refers to Token state, since some kind of =
Message
         ID state has to be kept at least for MAX_LATENCY according to
         Section 4.8.2? Again, I'd expect the protocol specification to
         clearly state what the minimum requirements on keeping state =
are.

We try to minimize those minimum requirements.
The specific optimization described here has the unfortunate property
that a client may seem like it just has been rebooted.
We cannot disallow rebooting in the protocol.

        * Section 5.4 and Section 5.10

         =3D> The maximum size of these options, in particular if more =
than one
         is used at the same time, can easily exceed the IPv6 MTU of =
1280
         bytes. In other words, a single non-fragmented IP packet will =
not
         only have not enough space for payload if options are used, =
possibly
         a single packet will not even be sufficient to transport all
         required options? What does the CoAP base protocol do in that =
case?
         Discard that request/response and return an application error? =
Why
         does Section 5 not have any guidance on size/segmentation =
issues if
         options are (too) large?

There is a SHOULD about messages sizes in 4.6.

        * Section 8.1

          A multicast request is characterized by being transported in a =
CoAP
          message that is addressed to an IP multicast address instead =
of a
          CoAP endpoint.  Such multicast requests MUST be =
Non-confirmable.

         =3D> A normative statement on congestion control for *sending* =
to
         multicast addresses is missing. I think that a slow-speed =
network
         can get very easily congested by multicast messages, i. e., =
this
         matters for the main CoAP use cases. I believe that sending 1
         Byte/second is save for multicast destinations.

As the text you cite says, multicast requests are governed by NON rules.

It is indeed easy to congest a constrained node network using
multicast (if that is implemented at all, usually by flooding a
broadcast message).  Multicast application protocol specifications for
more powerful networks, such as RFC 6762 (which does not contain the
word "congestion" and only alludes to "rate-limiting"), have not even
tried to codify the limits of reasonableness here: it is nearly
impossible to give limits that aren't both ridiculously high for some
environments and too conservative for others.  Multicast congestion
control for wireless constrained node networks is significantly less
well understood because of the dynamics of the flooding protocols
used; it also has to contend with memory limits in the router nodes.

In summary, CoAP implementers are likely to be extremely careful about
using multicast.  And that is about the level of advice we could give
them: "Be very, very careful about using multicast".

        * Section 8.1

          When a server is aware that a request arrived via multicast, =
it
          MUST NOT return a RST in reply to NON.  If it is not aware, it =
MAY
          return a RST in reply to NON as usual.  Because such a Reset
          message will look identical to an RST for a unicast message =
from
          the sender, the sender MUST avoid using a Message ID that is =
also
          still active from this endpoint with any unicast endpoint that
          might receive the multicast message.

         =3D> Why is a RST forbidden by a MUST? I would understand the
         motivation for a SHOULD, but if a server is overloaded by =
multicast
         requests and runs out of processing resources for multicast
         requests, isn't there a need to tell the sender that it has to =
stop
         using this multicast group?

There is no flow control implication of RST, so I'm not quite sure I
understand the scenario.  Sending back an RST to a multicast is not
going to help an overloaded server (there are no retransmissions to be
curbed).
(The specific case discussed in the rest of that paragraph is that of
a server stuck with pre-3542 posix, so it is unaware that it just
received a multicast.  This is an ugly situation, and there is not
really that much that can be done to clean it up.)

        * Section 8.2

          When matching a response to a multicast request, only the =
token
          MUST match; the source endpoint of the response does not need =
to
          (and will not) be the same as the destination endpoint of the
          original request.

         =3D> So, the token is the only way to deal with packets that =
are
         duplicated in the network? Then, this section must IMHO expand
         further on how to select token IDs for multicast transfer. For =
use
         in multicast, Section 5.3.1. "The client SHOULD generate tokens =
in
         such a way that tokens currently in use for a given
         source/destination endpoint pair are unique." is not =
sufficient; the
         token must in addition be unique during MAX_LATENCY, right?

The text is about response matching, not about removing duplicates.
Duplicate removal will be done based on message-IDs.
That state (if duplicate removal is desired) indeed needs to live on.

        * Section 8.2

            If a server does decide to respond to a multicast request, =
it
            should not respond immediately.

         =3D> The spec leaves open if a server is allowed to respond =
with
         confirmed message. If a large number of servers respond, the =
ACK
         traffic for many CONs could be an issue, right? But if only NON =
is
         allowed, what happens if the server wants that its message is =
indeed
         delivered reliably to the requester?

5.2.3 says a NON SHOULD be answered by a NON.
Now: "if the server wants that its message is indeed delivered
reliably" -- why? there was no guarantee the requesting NON would have
reached it in the first place, so why is delivering the response now
so important?
But if it indeed is, that might be a good reason to send a CON.  The
ACK traffic will indeed confound the network load.  So, as with any
SHOULD, there should be a strong reason to depart from 5.2.3.

        * Section 8.2

          E.g., for a multicast request with link-local scope on an 2.4 =
GHz
          IEEE 802.15.4 (6LoWPAN) network, G could be (relatively
          conservatively) set to 100, S to 100 bytes, and the target =
rate to
          a conservative 8 kbit/s =3D 1 kB/s.  The resulting lower bound =
for
          the Leisure is 10 seconds.

         =3D> While I like the idea of randomizing the response time to =
avoid
         in-cast problems, according to Section 4.8, a conservative
         assumption about the allowed data rate in a potentially =
congested
         network is PROBING_RATE =3D 1 Byte/second. 1 kB/s might be =
realistic
         in a specific application scenario if the network does not have =
any
         other traffic, but the attribute "conservative" should not be =
used
         here, because reality with cross-traffic could be entirely
         different.

Indeed.   We should strike "conservative".  [#291]

        * Section 8.2

          If a CoAP endpoint does not have suitable data to compute a =
value
          for Leisure, it MAY resort to DEFAULT_LEISURE.

         =3D> With this vague specification of leisure time the client =
has no
         means to know whether *any* response will ever arrive. The =
servers
         could, for instance, err on the size of the group and just pick =
all
         a large random leasure time. I think it would make sense to =
define
         an upper limit on the leasure time, to allow some =
interpretation on
         the client side. If this upper limit significantly exceeds the =
rate
         PROBING_RATE, servers may just randomly decide not to reply, =
instead
         of waiting for a long time.

That is indeed a problem, but it strikes me as more of of a quality of
implementation problem.  (I don't understand the last sentence,
though.  How does a time limit exceed a rate?)

        * Section 8.2.2

          When a forward-proxy receives a request with a Proxy-Uri or =
URI
          constructed from Proxy-Scheme that indicates a multicast =
address,
          the proxy obtains a set of responses as described above and =
sends
          all responses (both cached-still-fresh and new) back to the
          original client.

          =3D> I don't understand from the document how this works. For
          instance, will these responses all have the same token?

Yes.

          How can a
          client process this if it expects only one response from the =
proxy?

Indeed, there is a problem if the authority contains indirection
(e.g., is a DNS name), and maps to a multicast address unbeknownst of
the client.

          My general impression is that the multicast mode of CoAP would
          require a more rigorous specification for being included in a =
PS
          document.

There is continuing discussion of this in draft-ietf-core-groupcomm.
The fundamental mechanism works well for the problem we are trying to
solve using multicast (local service discovery), but, as the text
says, e.g., multicasting through a proxy may need additional
mechanisms.

        * Section 9

          DTLS is not applicable to group keying (multicast =
communication);
          however, it may be a component in a future group key =
management
          protocol.

         =3D> I am not really familiar with DTLS. But communication to
         multicast addresses by CoAP cannot be secured by DTLS, right? =
If so,
         why is there not a big warning sign "DTLS is not available for
         multicast CoAP"?

This sentence is the warning sign.

In today's usage of CoAP, multicast is mainly used for discovery, and
that often takes place as a prerequisite to establishing security.
So there is no practical problem today.  But we want to be able to
secure multicast CoAP, so we are working on multicast extensions to
DTLS.  These will take some time.

        * Section 11

         =3D> This section IMHO lacks the description of two further =
attacks:

            (a) The equivalent of a SYN flooding attack on TCP would be
            sending complex queries with CON to a server. Given that the =
cost
            of a CON request is small, this attack can easily be
            executed. Also, if the server responds with CONs, it will =
have to
            allocate buffer and retransmission logic for each request, =
and it
            will likely run out of resources. A simple remedy is rate
            limiting as mentioned in Section 4.7; this counter-measure =
should
            be repeated here.

Yes. [#292]
(There is a whole set of battery depletion attacks that are hard to
guard against without some form of network segregation.)

            (b) A subtle attack with spoofed addresses could possibly =
exploit
            the lack of congestion control in CoAP. Due to NSTART=3D1, a =
tricky
            attacker could prevent a server to communicate with a =
legitime
            client, because only one transaction is allowed to one
            destination address. The attacker could try to always occupy =
this
            "slot".

Good point. [#293]

            Both attacks are due to the lack of a three-way handshake =
like in
            TCP.

Yes.  This is a design feature, and we are fully aware of its cost.
(The real answer, of course, is global deployment of BCP38.  But I
won't open that can of worms.)

        * Section 11

         =3D> This section IMHO needs a discussion on minimum =
requirements on
         how to select Message ID and Tokens. Both are a means to =
protect
         against "hijacking" of transactions / falsification of =
responses,
         but if an attacker can guess these values, an attacker can =
inject
         wrong data into a CoAP communication. Compare e.g. to a TCP =
receiver
         that carefully checks whether sequence numbers are valid, i.e.,
         within the receive window.

The Token length was chosen to be as big as it is to enable this kind
of protection, if desired.  More likely, we will simply use DTLS
security where that matters.  But a short discussion of this could be
added. [#294] Note that there is a recommendation that message-IDs are
allocated sequentially in draft-ietf-lwig-guidance; for a constrained
system, this may be the only way to keep enough message state for
reliable duplicate removal.

        Editorial nits:

        * Section 2.2

                    CoAP makes use of GET, PUT, POST and DELETE methods =
in a
                    similar manner to HTTP, with the semantics specified =
in
                    Section 5.8.  (Note that the detailed semantics of =
CoAP
                    methods are "almost, but not entirely unlike" those =
of
                    HTTP methods:

         =3D> s/unlike/like/ ?

Ah, sorry, that is an inside joke for Douglas Adams fans.
Reference added (SVN [1272]).

        * Section 3

             Following the header, token, and options, if any, comes the
             optional payload.  If present and of non-zero length, it is
             prefixed by a fixed, one-byte Payload Marker (0xFF) which
             indicates the end of options and the start of the payload.  =
The
             payload data extends from after the marker to the end of =
the UDP
             datagram, i.e., the Payload Length is calculated from the
             datagram size.  The absence of the Payload Marker denotes a
             zero-length payload.  The presence of a marker followed by =
a
             zero-length payload MUST be processed as a message format =
error.

          =3D> I think that the term "payload marker" is kind of =
dangerous; it
          would be better to use a term like "end-of-option option". =
When I
          first read this section, I wondered whether a CoAP =
implementation
          could just scan through the packet to find the begin of the =
payload
          by the first occence of 0xFF after the default CoAP
          header. However, this would require 0xFF to be masked in all
          options. Masking is realized in Section 3.1, but apparently =
not in
          Sections 3.2 and Section 5.4.

The payload marker is not by itself an option.  Also, it is only
present if there is payload.  Instead of changing the name, maybe we
should add a note that byte-wise scanning for 0xFF is not a viable
technique for finding the payload.  [#287]

        * Section 4.4

             The same Message ID MUST NOT be re-used (in communicating =
with
             the same endpoint) within the EXCHANGE_LIFETIME (Section =
4.8.2).

             Implementation Note: Several implementation strategies can =
be
                employed for generating Message IDs.  In the simplest =
case a
                CoAP endpoint generates Message IDs by keeping a single
                Message ID variable, which is changed each time a new
                Confirmable or Non- confirmable message is sent =
regardless of
                the destination address or port.  Endpoints dealing with
                large numbers of transactions could keep multiple =
Message ID
                variables, for example per prefix or destination =
address.
                The initial variable value should be randomized.

         =3D> Using a single Message ID variable IMHO is only possible =
if there
         is only a single message outstanding to any address, because =
the
         Message ID has to be kept for verifying responses. Which =
implies
         that even in the "simplest case" there is also one Message ID
         variable per address. I wonder whether the Implementation Note
         should be something of the sort "implementations will typically
         store Message IDs per destination, but they may use a single =
counter
         to ensure uniqueness among several destinations".

The state per outstanding request is separate from this.  Simple
implementations will have one counter and one (or a very small number
of) outstanding request, so they will indeed not keep per-destinations
state.

        * Section 4.6

                  header and options are likely to fit within the =
buffer.  A
                  server can thus fully interpret a request and return a =
4.13
                  (Request Entity Too Large) response code if the =
payload was
                  truncated.  A

          =3D> The syntax "4.13" is not introduced at this stage; it =
could make
          sense to add a brief sentence early in the document to explain =
the
          response code format

Or just a forward reference to 5.9.2.9. [#289]


        * Section 4.8

                Message transmission is controlled by the following
                parameters:

         =3D> At least DEFAULT_LEISURE is not defined in the text until =
this
         table (and it is not really self-explaining).

This is one of the places where I would expect curious readers to make
use of the search function of their display device...

        * Section 4.8.2

         =3D> The whole section on time values derived from transmission
         parameters is pretty hard to parse. Instead of organizing it
         according parameters, it would be better to highlight the =
subset of
         parameters that actually matter for an implementation, and what =
is
         exactly the event at the beginning and end of that duration.

I'd rather write an LWIG document with lots of more details about
these parameters than trying to shoe-horn all this information in here.
The specification is already heavy on implementation information.

        * Section 5.3.1

          The Token is used to match a response with a request.  The =
token
          value is a sequence of 0 to 8 bytes.

         =3D> While CoAP optimizes its protocol fields for single bits, =
the
         document does not comment at all on reasonable sizes for the
         token. At least some text mentioning the high overhead of a 4 =
or 8
         byte token compared to the rest of the CoAP headers could be =
useful.
         Possibly also addressing the security-size tradeoff.

Yes, see [_] above.


        * Section 5.10

         =3D> I don't understand why the Proxy-URI is longer than =
others, and
         why the length is 1034.

The reason this is much larger than the other options is that it might
be used for interfacing to HTTP, which tends to use much larger URIs =
than we
normally create in the CoAP world (say, for OAuth).
(The specific value of 1034 is a remnant of an earlier option
encoding, 1023 would do, too, but we never made that change.)


From johnl@iecc.com  Sun Apr  7 08:15:35 2013
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 0B74B21F86C9 for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 08:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.019
X-Spam-Level: 
X-Spam-Status: No, score=-111.019 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-3OoAMUaBVI for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 08:15:34 -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 23EBA21F861B for <ietf@ietf.org>; Sun,  7 Apr 2013 08:15:33 -0700 (PDT)
Received: (qmail 4813 invoked from network); 7 Apr 2013 15:15:33 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 7 Apr 2013 15:15:33 -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; s=51618d94.xn--btvx9d.k1304; i=johnl@user.iecc.com; bh=5pHyI0zyuf6vK6PjXo/CeuyYQWp70jRtnL3b/AcBl8M=; b=KQc/7nYk9lNpqzP6pULn1M18q4Z52TCH8+TSlA8692FCd874f5a7y94A0oPbJmdYTWJTvEf4eHBVINKBqr6NpxNAa8VA7c0G9PQXyYvil9aUefrIrTDzuCFQr3uSkF0aayr6426m2Zss+LKT2WlHz2uuF1en+EiscM9XN9oTLwE=
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; s=51618d94.xn--btvx9d.k1304; olt=johnl@user.iecc.com; bh=5pHyI0zyuf6vK6PjXo/CeuyYQWp70jRtnL3b/AcBl8M=; b=IHW8vKNmj38GsJ7vrCMd8zNE7tBh14Mzbo6kv11dcFLrsC+HHhCqWnlkgQFCQOs9oY27Srmqc4qISJl/bFSKWkxPqou+gx7uv06PB257Hc6WLPQRVkG2fsDQltwo6nkfqBEHDjFDUCc8oUYPUdxtqAKYYg1/ralZEzCXfgyuJJM=
Date: 7 Apr 2013 15:15:08 -0000
Message-ID: <20130407151508.75879.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated	April the first
In-Reply-To: <4613980CFC78314ABFD7F85CC3027721119FF4B7@IL-EX10.ad.checkpoint.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: Sun, 07 Apr 2013 15:15:35 -0000

>That said, I did at one point have to exercise my diplomatic skills when I got forwarded a customer (nameless
>here for evermore) question about whether support for RFC 3514 was on our roadmap.

Think of it as free market intelligence on your customer base.

Of course we've only had April 1 RFCs for 35 years now.  Who knows
what horrible problem they may yet cause that we haven't noticed yet.




From mansaxel@besserwisser.org  Sun Apr  7 08:41:23 2013
Return-Path: <mansaxel@besserwisser.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 0440021F8DA4 for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 08:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_55=0.6, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VXWKtM9x8S2r for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 08:41:22 -0700 (PDT)
Received: from jaja.besserwisser.org (primary.se [IPv6:2a01:298:4::53]) by ietfa.amsl.com (Postfix) with ESMTP id 70E7121F8DB2 for <ietf@ietf.org>; Sun,  7 Apr 2013 08:41:21 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 42AF79E5B; Sun,  7 Apr 2013 17:41:19 +0200 (CEST)
Date: Sun, 7 Apr 2013 17:41:19 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated	April the first
Message-ID: <20130407154119.GA1162@besserwisser.org>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <577E2C0B-16F5-47D2-8D71-7A9D914ACF23@kumari.net> <CADnDZ8_p=hp+yP5YTso72LO6MEuONxpdw-QBsTCtXn+v9eVpaw@mail.gmail.com> <4613980CFC78314ABFD7F85CC3027721119FF4B7@IL-EX10.ad.checkpoint.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv"
Content-Disposition: inline
In-Reply-To: <4613980CFC78314ABFD7F85CC3027721119FF4B7@IL-EX10.ad.checkpoint.com>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
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, 07 Apr 2013 15:41:23 -0000

--ZGiS0Q5IWpPtfppv
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: RE: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dat=
ed?April the first Date: Sun, Apr 07, 2013 at 11:59:30AM +0000 Quoting Yoav=
 Nir (ynir@checkpoint.com):
> I mostly share the sentiment that this is just humor, so what's the harm.
>=20
> That said, I did at one point have to exercise my diplomatic skills when =
I got forwarded a customer (nameless here for evermore) question about whet=
her support for RFC 3514 was on our roadmap.

On that subject, April 1 RFCen in call for tender, I'd argue that they
serve a purpose. If an April 1 RFC is included in MUST or SHOULD --
a clued supplier will have staff that get the joke and reply with "only
on April 1" or similar. A box-ticking "let's hope they don't test this"
lying bastard will just check it and pull their pants down in public.
=20
> While the people on this list generally "get" the joke, not all readers o=
f RFCs are part of this group. The recent RFC 6919 is full of in-jokes (or =
perhaps, in-roast?) that many outside the IETF will not get. Anyways, it is=
 an issue, but I think these are too much fun to do away with them.

I do not want code or devices from people that don't "get" it in my
network. The April 1 series are useful documents.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
So this is what it feels like to be potato salad

--ZGiS0Q5IWpPtfppv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlFhk58ACgkQ02/pMZDM1cW+5wCeNylgWNzFwsaTEZ7c1WfJczWR
cfcAn366Dml8AVbQtIA33XGdtG7+wuKu
=MlHQ
-----END PGP SIGNATURE-----

--ZGiS0Q5IWpPtfppv--

From braden@isi.edu  Sun Apr  7 11:28:02 2013
Return-Path: <braden@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 C5AB221F877A for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 11:28:02 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOlNpVm46mMP for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 11:28:02 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id D399C21F86BA for <ietf@ietf.org>; Sun,  7 Apr 2013 11:28:01 -0700 (PDT)
Received: from [192.168.1.6] (c1-vpn5.isi.edu [128.9.176.35]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r37IRKcV010615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 7 Apr 2013 11:27:20 -0700 (PDT)
Message-ID: <5161BA77.4040406@isi.edu>
Date: Sun, 07 Apr 2013 11:27:03 -0700
From: Bob Braden <braden@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated April the first
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <577E2C0B-16F5-47D2-8D71-7A9D914ACF23@kumari.net> <CADnDZ8_p=hp+yP5YTso72LO6MEuONxpdw-QBsTCtXn+v9eVpaw@mail.gmail.com> <4613980CFC78314ABFD7F85CC3027721119FF4B7@IL-EX10.ad.checkpoint.com> <20130407154119.GA1162@besserwisser.org>
In-Reply-To: <20130407154119.GA1162@besserwisser.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@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: Sun, 07 Apr 2013 18:28:02 -0000

On 4/7/2013 8:41 AM, Måns Nilsson wrote:
>
> I do not want code or devices from people that don't "get" it in my
> network. The April 1 series are useful documents.
>
Well said!

i believe that april 1 RFCs server several useful purposes. They remind 
us to
not take ourselves too seriously. They remind us that the Internet community
has at times a counter-cultural tinge, questioning the common wisdom --
  when the prevailing wisdom was virtual circuits, we chose datagrams,
  for example. April 1 RFCs remind us that it is a mistake to completely 
legislate
the rules of organization of the IETF; we need room for permitting well-
grounded exceptions, thereby fostering growth and innovation
.
April 1 RFCs originated in the subtle wit of Jon Postel, and Jon believed
that April 1 RFCs should be outside the process -- they should  just appear
mysteriously every April 1, without last calls,  IESG actions, etc. (Similar
magic happens with the assignment of RFC numbers, by the way.
When questioned how it happened that the update to RFC 822 got
the number 2822, Jon would say "just a coincidence".)

I must confess to falling for 6919, but I think this simply reflected
  my dismay over today's  waste of time and effor perfecting
IETF process rules. At first glance, I thought that
6919 was simply the next step down into the pit of fruitless
Bickering that is the IETF mailing list these days.  More attention
to the very real problems of the Internet would seem to be in
order. I was much heartened to realize that 6919 was a joke,
and that publication of that April 1 RFC demonstrated some
community consensus that things are getting out of hand.

Bob Braden




From ynir@checkpoint.com  Sun Apr  7 12:32:03 2013
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 5A3B521F863B for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 12:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.149
X-Spam-Level: 
X-Spam-Status: No, score=-10.149 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OmmsKF8FKaQv for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 12:32:02 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 76D2B21F84CC for <ietf@ietf.org>; Sun,  7 Apr 2013 12:32:02 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r37JVssT010809; Sun, 7 Apr 2013 22:31:58 +0300
X-CheckPoint: {5161C9A0-0-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Sun, 7 Apr 2013 22:31:54 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated	April the first
Thread-Topic: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated	April the first
Thread-Index: AQHOMtLCY/W/har6j0iUclYVgtQStJjJRiaAgAFgukCAAA3hgIAAQG8A
Date: Sun, 7 Apr 2013 19:31:54 +0000
Message-ID: <3784DE17-5026-4C32-AE57-76606CF05A28@checkpoint.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <577E2C0B-16F5-47D2-8D71-7A9D914ACF23@kumari.net> <CADnDZ8_p=hp+yP5YTso72LO6MEuONxpdw-QBsTCtXn+v9eVpaw@mail.gmail.com> <4613980CFC78314ABFD7F85CC3027721119FF4B7@IL-EX10.ad.checkpoint.com> <20130407154119.GA1162@besserwisser.org>
In-Reply-To: <20130407154119.GA1162@besserwisser.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.39]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DE40BDB935792F4BBB3723B320C95347@ad.checkpoint.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: Sun, 07 Apr 2013 19:32:03 -0000

On Apr 7, 2013, at 6:41 PM, M=E5ns Nilsson <mansaxel@besserwisser.org> wrot=
e:

> Subject: RE: [IETF] Comments for Humorous RFCs or uncategorised RFCs or d=
ated?April the first Date: Sun, Apr 07, 2013 at 11:59:30AM +0000 Quoting Yo=
av Nir (ynir@checkpoint.com):
>> I mostly share the sentiment that this is just humor, so what's the harm=
.
>>=20
>> That said, I did at one point have to exercise my diplomatic skills when=
 I got forwarded a customer (nameless here for evermore) question about whe=
ther support for RFC 3514 was on our roadmap.
>=20
> On that subject, April 1 RFCen in call for tender, I'd argue that they
> serve a purpose. If an April 1 RFC is included in MUST or SHOULD --
> a clued supplier will have staff that get the joke and reply with "only
> on April 1" or similar. A box-ticking "let's hope they don't test this"
> lying bastard will just check it and pull their pants down in public.

In this case I could tick that box without being a lying bastard. Just a so=
rt-of deceitful one. It is possible to configure the firewall to drop packe=
ts with the evil bit set. I still went with explaining the April 1 RFC conc=
ept.=

From mansaxel@besserwisser.org  Sun Apr  7 12:42:02 2013
Return-Path: <mansaxel@besserwisser.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 4626021F8AAA for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 12:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_55=0.6, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkDNlKOX4VEk for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 12:42:01 -0700 (PDT)
Received: from jaja.besserwisser.org (primary.se [IPv6:2a01:298:4::53]) by ietfa.amsl.com (Postfix) with ESMTP id 3E85321F8AA8 for <ietf@ietf.org>; Sun,  7 Apr 2013 12:41:57 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 33DCF9E5B; Sun,  7 Apr 2013 21:41:55 +0200 (CEST)
Date: Sun, 7 Apr 2013 21:41:55 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated	April the first
Message-ID: <20130407194154.GB1162@besserwisser.org>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <577E2C0B-16F5-47D2-8D71-7A9D914ACF23@kumari.net> <CADnDZ8_p=hp+yP5YTso72LO6MEuONxpdw-QBsTCtXn+v9eVpaw@mail.gmail.com> <4613980CFC78314ABFD7F85CC3027721119FF4B7@IL-EX10.ad.checkpoint.com> <20130407154119.GA1162@besserwisser.org> <3784DE17-5026-4C32-AE57-76606CF05A28@checkpoint.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PmA2V3Z32TCmWXqI"
Content-Disposition: inline
In-Reply-To: <3784DE17-5026-4C32-AE57-76606CF05A28@checkpoint.com>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
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, 07 Apr 2013 19:42:02 -0000

--PmA2V3Z32TCmWXqI
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dat=
ed?April the first Date: Sun, Apr 07, 2013 at 07:31:54PM +0000 Quoting Yoav=
 Nir (ynir@checkpoint.com):

> In this case I could tick that box without being a lying bastard. Just a =
sort-of deceitful one. It is possible to configure the firewall to drop pac=
kets with the evil bit set. I still went with explaining the April 1 RFC co=
ncept.

You pass.=20

I seem to be able to locate several implementations. Shall we initiate
work to elevate 3514 from Informational to Proposed Standard?

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
I hope the ``Eurythmics'' practice birth control ...

--PmA2V3Z32TCmWXqI
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlFhzAIACgkQ02/pMZDM1cW7UQCfUYvWpKDwe7GR9nVFeWEfWII9
qScAnRL18EveJ7A8+KfTemj1t2MzFd9N
=S4R3
-----END PGP SIGNATURE-----

--PmA2V3Z32TCmWXqI--

From superuser@gmail.com  Sun Apr  7 13:32:09 2013
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 DC41921F8EC3 for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 13:32:09 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6oYDHGGsmE8T for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 13:32:09 -0700 (PDT)
Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) by ietfa.amsl.com (Postfix) with ESMTP id 0DABD21F8A09 for <ietf@ietf.org>; Sun,  7 Apr 2013 13:32:08 -0700 (PDT)
Received: by mail-wg0-f53.google.com with SMTP id c11so5307870wgh.20 for <ietf@ietf.org>; Sun, 07 Apr 2013 13:32:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=EGDeFvu7830NiKyW6jiy4ny3PqIVngIE/awO+0MIk5A=; b=NCJMdoNhA1wUCz2nDckdWNDntFyKFt2BQ9nbuEx5Et5AO0K+XnwRHRjAmyESy7GC0t 8C5eEpD/Eof3vGPESfgbgU05UHGIVRchuzGIRtCpIrZgFRSnWqQsBlTOuvWZprPh2QEd YCHQW08PVztY8sk++Uliq2pf+mPzzw7JRYCSCFeGM2imwoDE699AGZ+M0quAGcR8HJBa TwAWocWZwuav+XwV58gHglmWs6qCdC39mniRWKNxj1ROG62sW0NBlV/mc+ou9qjWjka3 TLBjEU9rsGS3OYNfxvs1kbRs4l6wcoj61vcEwqXhwGY7U5+dw/vhnkzw9bgPTUWBbH1y pn3g==
MIME-Version: 1.0
X-Received: by 10.180.74.67 with SMTP id r3mr9046322wiv.14.1365366728212; Sun, 07 Apr 2013 13:32:08 -0700 (PDT)
Received: by 10.180.36.176 with HTTP; Sun, 7 Apr 2013 13:32:08 -0700 (PDT)
In-Reply-To: <51609619.6050903@gmail.com>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com> <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com> <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com> <51609619.6050903@gmail.com>
Date: Sun, 7 Apr 2013 13:32:08 -0700
Message-ID: <CAL0qLwbZ=HiidJqafAmy5RyQRdNpD+NpSKRkzyNLeWhbZpoTcg@mail.gmail.com>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0438914dd2cb4504d9cb36db
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, 07 Apr 2013 20:32:10 -0000

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

That this thread is still being pursued made me double-check that it is in
fact not still April 1st.


On Sat, Apr 6, 2013 at 2:39 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 4/6/13 1:33 PM, Ulrich Herberg wrote:
> > Indeed. The wikipedia entry is somewhat misleading though:
> > http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>
> Fix it or ignore it.  Wikipedia is neither authoritative nor
> reliable.
>
> Melinda
>
>
>

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

<div dir=3D"ltr">That this thread is still being pursued made me double-che=
ck that it is in fact not still April 1st.<br></div><div class=3D"gmail_ext=
ra"><br><br><div class=3D"gmail_quote">On Sat, Apr 6, 2013 at 2:39 PM, Meli=
nda 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"><div class=3D"im">On 4/6/13 1:33 PM, Ulrich =
Herberg wrote:<br>
&gt; Indeed. The wikipedia entry is somewhat misleading though:<br>
&gt; <a href=3D"http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC" target=
=3D"_blank">http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC</a><br>
<br>
</div>Fix it or ignore it. =A0Wikipedia is neither authoritative nor<br>
reliable.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Melinda<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--f46d0438914dd2cb4504d9cb36db--

From hsantos@isdg.net  Sun Apr  7 13:59:57 2013
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 881AB21F8D40 for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 13:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.568
X-Spam-Level: 
X-Spam-Status: No, score=-101.568 tagged_above=-999 required=5 tests=[AWL=0.431, BAYES_00=-2.599, J_CHICKENPOX_28=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p8QsIf7HAuiC for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 13:59:57 -0700 (PDT)
Received: from secure.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B363B21F8A55 for <ietf@ietf.org>; Sun,  7 Apr 2013 13:59:56 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1226; t=1365368388; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=gSUBUFU 0Xnm4C8gzzUyWzt1ElWw=; b=c19OBYrj4oRuC+pkbBhMke4lRMzmSmGC3p+jTfs uuBE09WpQ2tV/N05lrYa8dNRi+URMDyiiKzPLGFbmDlEMRXkjsGEPlXREdajiRCV Ly7dimzMv9uBIWzIH/tMkuSovyUo9+mwpV0MkKabGCMAFkQ7qgTsG5X1p/amKXgV pF/U=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 07 Apr 2013 16:59:48 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4162095006.1914.664; Sun, 07 Apr 2013 16:59:47 -0400
Message-ID: <5161DE0C.8060207@isdg.net>
Date: Sun, 07 Apr 2013 16:58:52 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Proposed solution  for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
References: <20130407151508.75879.qmail@joyce.lan>
In-Reply-To: <20130407151508.75879.qmail@joyce.lan>
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: Sun, 07 Apr 2013 20:59:57 -0000

This is one of those DPEP (Diversity Problem Entry Point) arising from 
globalization, April 1 HRC (Humor Recognition Culture) differences,  
IETF "stalization" and the growth of I-D submissions.   I suggest there 
is a direct correlation among these factors with the end goal efficacy 
of the submission.  Fortunately, there is a technical solution for this 
particular DPEP:

     if Date is April.1 then
          id.filename = "joke-"+id.filename.
     end if


A BCP can be written on when are the better days to submit an I-D. 
Clearly, the day with the lowest impact with a high ignorance factor 
would be April 1st submissions - its just bad marketing and bad 
judgement too, in my book, to submit anything intended to be real and 
serious on this day.

--
HLS


On 4/7/2013 11:15 AM, John Levine wrote:
>> That said, I did at one point have to exercise my diplomatic skills when I got forwarded a customer (nameless
>> here for evermore) question about whether support for RFC 3514 was on our roadmap.
> Think of it as free market intelligence on your customer base.
>
> Of course we've only had April 1 RFCs for 35 years now.  Who knows
> what horrible problem they may yet cause that we haven't noticed yet.
>
>
>



From ajs@anvilwalrusden.com  Sun Apr  7 15:32:49 2013
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 8D56C21F8F5B for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 15:32:49 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XkanmyLPjZtf for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 15:32:49 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id EF5CE21F8F33 for <ietf@ietf.org>; Sun,  7 Apr 2013 15:32:48 -0700 (PDT)
Received: from mx1.yitter.info (li440-116.members.linode.com [50.116.54.116]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E70478A031 for <ietf@ietf.org>; Sun,  7 Apr 2013 22:32:47 +0000 (UTC)
Date: Sun, 7 Apr 2013 18:32:45 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
Message-ID: <20130407223244.GG18639@mx1.yitter.info>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com> <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com> <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com> <51609619.6050903@gmail.com> <CAL0qLwbZ=HiidJqafAmy5RyQRdNpD+NpSKRkzyNLeWhbZpoTcg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL0qLwbZ=HiidJqafAmy5RyQRdNpD+NpSKRkzyNLeWhbZpoTcg@mail.gmail.com>
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: Sun, 07 Apr 2013 22:32:49 -0000

On Sun, Apr 07, 2013 at 01:32:08PM -0700, Murray S. Kucherawy wrote:
> That this thread is still being pursued made me double-check that it is in
> fact not still April 1st.

It's always April 1st somewhere on the Net?

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jnc@mercury.lcs.mit.edu  Sun Apr  7 15:53:48 2013
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 E066021F86C1 for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 15:53:48 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V+dG-VFpvZCy for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 15:53:48 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1B021F8539 for <ietf@ietf.org>; Sun,  7 Apr 2013 15:53:48 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 69ED918C136; Sun,  7 Apr 2013 18:53:47 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
Message-Id: <20130407225347.69ED918C136@mercury.lcs.mit.edu>
Date: Sun,  7 Apr 2013 18:53:47 -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: Sun, 07 Apr 2013 22:53:49 -0000

    > From: Andrew Sullivan <ajs@anvilwalrusden.com>

    > It's always April 1st somewhere on the Net?

Especially if you (or your packets, to be precise) can travel backwards in
time....

	Noel

From mnot@mnot.net  Sun Apr  7 17:55:18 2013
Return-Path: <mnot@mnot.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 87CC021F9012 for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 17:55:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.799
X-Spam-Level: 
X-Spam-Status: No, score=-105.799 tagged_above=-999 required=5 tests=[AWL=-3.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IC4JJ8Utx2KJ for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 17:55:17 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id CBE7E21F8FC7 for <ietf@ietf.org>; Sun,  7 Apr 2013 17:55:17 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.42.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id CF80E22E256; Sun,  7 Apr 2013 20:55:10 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Comments for Humorous RFCs or uncategorised RFCs or dated	April the first
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4613980CFC78314ABFD7F85CC3027721119FF4B7@IL-EX10.ad.checkpoint.com>
Date: Mon, 8 Apr 2013 10:55:06 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <F987F8E7-DAD1-4FE1-B236-AAC29895BF72@mnot.net>
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <577E2C0B-16F5-47D2-8D71-7A9D914ACF23@kumari.net> <CADnDZ8_p=hp+yP5YTso72LO6MEuONxpdw-QBsTCtXn+v9eVpaw@mail.gmail.com> <4613980CFC78314ABFD7F85CC3027721119FF4B7@IL-EX10.ad.checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1503)
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, 08 Apr 2013 00:55:18 -0000

On 07/04/2013, at 9:59 PM, Yoav Nir <ynir@checkpoint.com> wrote:

> I mostly share the sentiment that this is just humor, so what's the =
harm.
>=20
> That said, I did at one point have to exercise my diplomatic skills =
when I got forwarded a customer (nameless here for evermore) question =
about whether support for RFC 3514 was on our roadmap.
>=20
> While the people on this list generally "get" the joke, not all =
readers of RFCs are part of this group. The recent RFC 6919 is full of =
in-jokes (or perhaps, in-roast?) that many outside the IETF will not =
get. Anyways, it is an issue, but I think these are too much fun to do =
away with them.

Indeed.

The April 1 RFCs do a great job reminding readers that the authority of =
an RFC, on its own, approaches zero. OTOH, it should also be a bit of a =
wake-up call to folks here that people so often confuse "RFC" with =
"authoritative statement of the IETF."=20

Cheers,


--
Mark Nottingham   http://www.mnot.net/




From housley@vigilsec.com  Sun Apr  7 18:34:54 2013
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 E5D5721F901D for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 18:34:53 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4l67AMO2DqrS for <ietf@ietfa.amsl.com>; Sun,  7 Apr 2013 18:34:53 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2703021F8FF2 for <ietf@ietf.org>; Sun,  7 Apr 2013 18:34:53 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 48E59F24070 for <ietf@ietf.org>; Sun,  7 Apr 2013 21:34:49 -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 y3jgulPdGi+P for <ietf@ietf.org>; Sun,  7 Apr 2013 21:34:40 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 926FCF2406E for <ietf@ietf.org>; Sun,  7 Apr 2013 21:34:46 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: draft-housley-rfc2050bis-01
Date: Sun, 7 Apr 2013 21:34:40 -0400
Message-Id: <11301BFD-E4AD-4779-802E-6BAADD0381D4@vigilsec.com>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
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: Mon, 08 Apr 2013 01:34:54 -0000

Many of the comments that were posted to this list have been =
incorporated.

Please comment on the updated document.

Russ

=3D =3D =3D =3D =3D =3D =3D =3D =3D

A new version of I-D, draft-housley-rfc2050bis-01.txt
has been successfully submitted by Geoff Huston and posted to the
IETF repository.

Filename:	 draft-housley-rfc2050bis
Revision:	 01
Title:		 The Internet Numbers Registry System
Creation date:	 2013-04-08
Group:		 Individual Submission
Number of pages: 8
URL:             =
http://www.ietf.org/internet-drafts/draft-housley-rfc2050bis-01.txt
Status:          =
http://datatracker.ietf.org/doc/draft-housley-rfc2050bis
Htmlized:        http://tools.ietf.org/html/draft-housley-rfc2050bis-01
Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-housley-rfc2050bis-01

Abstract:
  This document provides information about the current Internet Numbers
  Registry System used in the distribution of globally unique Internet
  Protocol (IP) address space and autonomous system (AS) numbers.

  This document also provides information about the processes for
  further evolution of the Internet Numbers Registry System.

  This document replaces RFC 2050.

  This document does not propose any changes to the Internet Numbers
  Registry System.


From mansaxel@besserwisser.org  Mon Apr  8 00:21:55 2013
Return-Path: <mansaxel@besserwisser.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 301E021F930A for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 00:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_28=0.6, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PlbMOlxW+zSa for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 00:21:34 -0700 (PDT)
Received: from jaja.besserwisser.org (primary.se [IPv6:2a01:298:4::53]) by ietfa.amsl.com (Postfix) with ESMTP id 8A6DC21F9309 for <ietf@ietf.org>; Mon,  8 Apr 2013 00:21:31 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 653DD9DAA; Mon,  8 Apr 2013 09:21:29 +0200 (CEST)
Date: Mon, 8 Apr 2013 09:21:29 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: Proposed solution  for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Message-ID: <20130408072128.GC1162@besserwisser.org>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nmemrqcdn5VTmUEE"
Content-Disposition: inline
In-Reply-To: <5161DE0C.8060207@isdg.net>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
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, 08 Apr 2013 07:21:55 -0000

--nmemrqcdn5VTmUEE
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Proposed solution  for DPEP (Diversity Problem Entry Point) - IETF=
 April 1 jokes. Date: Sun, Apr 07, 2013 at 04:58:52PM -0400 Quoting Hector =
Santos (hsantos@isdg.net):
> This is one of those DPEP (Diversity Problem Entry Point) arising
> from globalization, April 1 HRC (Humor Recognition Culture)
> differences,  IETF "stalization" and the growth of I-D submissions.
> I suggest there is a direct correlation among these factors with the
> end goal efficacy of the submission.  Fortunately, there is a
> technical solution for this particular DPEP:
>=20
>     if Date is April.1 then
>          id.filename =3D "joke-"+id.filename.
>     end if
=20
This solution has all the virtues of carpet-bombing. Mission accomplished
but cost and collateral damage are improportionally large.  To me, both
as humour /per se/ and as sorting help when selecting vendors (cf. my
message in this thread yesterday), the value almost totally lies in the
subtle play with form and the resulting ambigousness. In other words,
if we make it possible to determine by simple logic whether a document
is a pun or dead serious, it is useless.

I am aware that my position as stated above will be possible to interpret
as excluding. As parent of a child diagnosed with Aspergers syndrome,
I fully well know the potential consequences of failure to interpret
social hints.

I believe that=20

* transient failure to get a joke not is cause for "safing" jokes. The
failure is part of the process.

* the speed with which  we "unfail" and start to appreciate this art
form is personal and differs according to our experience, background
and intellectual skills but that the initial failure is necessary. There
are subtler ways than policy and procedure to nudge people along when
they persist in failing.=20

* the Internet idea of loosely cooperating networks REQUIRES autonomous
judgement from the people operating the system. Fostering a culture
where IETF texts are seen as close to faultless holy scripture does
nothing to encourage skepticism and personal responsibility.

* enough has been said in this that we already are risking the sweet
uncertainity. Accordingly, I'll try to not communicate further on this,
and definitely not propose any procedure work.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
I am deeply CONCERNED and I want something GOOD for BREAKFAST!

--nmemrqcdn5VTmUEE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlFib/gACgkQ02/pMZDM1cVp0wCePKf4nLxF85ZBOACv1itL0G8s
pDwAoKPsjMy06MZRr2eMHiOegi5vCs/g
=UNMB
-----END PGP SIGNATURE-----

--nmemrqcdn5VTmUEE--

From melinda.shore@gmail.com  Mon Apr  8 01:30:31 2013
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 D284321F9334 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 01:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5AybtYuYAid for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 01:30:31 -0700 (PDT)
Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by ietfa.amsl.com (Postfix) with ESMTP id 47C1821F9298 for <ietf@ietf.org>; Mon,  8 Apr 2013 01:30:31 -0700 (PDT)
Received: by mail-vc0-f169.google.com with SMTP id hx10so2012861vcb.14 for <ietf@ietf.org>; Mon, 08 Apr 2013 01:30:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=E3rMGn94wWuYveIOMOnjwnlPeorzIX7sEsaCvD11ZRA=; b=bbXk0SqP3U2qy5cd2nxeVbURy0Cf4Zp5xtjx9wGcJePFB7vShgP0qTy2hRSKrMbLcv 3V7etvuun9fstwZs7IUkC1rMASjy/WPXW6ocl3BsDNWSjtCMz95SqMYLrWRkCKrsmA3G gc3rsZGzUdPEMbPAYqQ9Ssz4QiHo9+SnsuDSgzPCdyVa0tTqsbv2XsPYTyrWLwlcFWMB fopdwAiXsGgTQjvXY+gL0aXWde5VIjOmT/Katcu/filEWP1D4KI2YXPNgZDB51aJ4Pxt wwuWWZVupFZBjKE3HyfwFFTDVLVLAlwHNatvw2hkbUgFmhY7jjmYtkMZY1bfn6Rc3yhe bwIA==
MIME-Version: 1.0
X-Received: by 10.220.88.145 with SMTP id a17mr14949642vcm.66.1365409830545; Mon, 08 Apr 2013 01:30:30 -0700 (PDT)
Received: by 10.58.65.39 with HTTP; Mon, 8 Apr 2013 01:30:30 -0700 (PDT)
Received: by 10.58.65.39 with HTTP; Mon, 8 Apr 2013 01:30:30 -0700 (PDT)
In-Reply-To: <20130408072128.GC1162@besserwisser.org>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org>
Date: Mon, 8 Apr 2013 00:30:30 -0800
Message-ID: <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
From: Melinda Shore <melinda.shore@gmail.com>
To: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Content-Type: multipart/alternative; boundary=047d7b3a8f14ec2fb904d9d53f43
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, 08 Apr 2013 08:30:31 -0000

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

Doesn't it strike you as odd that this discussion has moved towards some
sort of tacit/accepted acknowledgment of the role of joke RFCs as
insider/outsider cultural markers rather than just clever bits of writing
that are widely enjoyed?  I'm a little surprised to find myself developing
sympathy for tiresome humorless whiny people.  (Wait, no I'm not).

Anyway this strikes me as an unfortunate use of those documents.

Melinda

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

<p>Doesn&#39;t it strike you as odd that this discussion has moved towards =
some sort of tacit/accepted acknowledgment of the role of joke RFCs as insi=
der/outsider cultural markers rather than just clever bits of writing that =
are widely enjoyed?=A0 I&#39;m a little surprised to find myself developing=
 sympathy for tiresome humorless whiny people.=A0 (Wait, no I&#39;m not).</=
p>

<p>Anyway this strikes me as an unfortunate use of those documents.=A0 </p>
<p>Melinda </p>

--047d7b3a8f14ec2fb904d9d53f43--

From mansaxel@besserwisser.org  Mon Apr  8 03:37:54 2013
Return-Path: <mansaxel@besserwisser.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 B279021F87D3 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 03:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3daX6RCjSH7w for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 03:37:54 -0700 (PDT)
Received: from jaja.besserwisser.org (primary.se [IPv6:2a01:298:4::53]) by ietfa.amsl.com (Postfix) with ESMTP id 2B95921F87D0 for <ietf@ietf.org>; Mon,  8 Apr 2013 03:37:53 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 9ABD59E71; Mon,  8 Apr 2013 12:37:51 +0200 (CEST)
Date: Mon, 8 Apr 2013 12:37:51 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Message-ID: <20130408103751.GD1162@besserwisser.org>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org> <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mJm6k4Vb/yFcL9ZU"
Content-Disposition: inline
In-Reply-To: <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
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, 08 Apr 2013 10:37:54 -0000

--mJm6k4Vb/yFcL9ZU
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - I=
ETF April 1 jokes. Date: Mon, Apr 08, 2013 at 12:30:30AM -0800 Quoting Meli=
nda Shore (melinda.shore@gmail.com):
> Doesn't it strike you as odd that this discussion has moved towards some
> sort of tacit/accepted acknowledgment of the role of joke RFCs as
> insider/outsider cultural markers rather than just clever bits of writing
> that are widely enjoyed?  I'm a little surprised to find myself developing
> sympathy for tiresome humorless whiny people.  (Wait, no I'm not).
>=09
> Anyway this strikes me as an unfortunate use of those documents.

Breaking my own promise to shut up I'll just try to share my (unfinished)
thoughts as why this is so.

Perhaps it is a reaction to the "businessisation" of the IETF. Everything
needs to be justified and documented (which for the most part is
good. Until it is not). So in order to keep the pastime that these
documents are,  we jerk and try to assign them procedural meaning. When
we simply should say "They are a funny way to look at ourselves busy
trying to describe the world" -- but we've somehow lost faith in that. Oh
to be an arts major and just being able to place feelings in words and
have them graded as passing the exam. ;-)

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
=2E.. I'm IMAGINING a sensuous GIRAFFE, CAVORTING in the BACK ROOM
of a KOSHER DELI --

--mJm6k4Vb/yFcL9ZU
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlFinf8ACgkQ02/pMZDM1cX28gCfZ1Lii85sK1okPjdFMphxFJXM
IJ4An2J8rQVziL5yPJK7/dvhKUDMx/nE
=gO3N
-----END PGP SIGNATURE-----

--mJm6k4Vb/yFcL9ZU--

From stbryant@cisco.com  Mon Apr  8 03:53:59 2013
Return-Path: <stbryant@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 C0D9E21F89DB; Mon,  8 Apr 2013 03:53:59 -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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8P-W1BmjXq2b; Mon,  8 Apr 2013 03:53:58 -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 A40BB21F8976; Mon,  8 Apr 2013 03:53:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5828; q=dns/txt; s=iport; t=1365418438; x=1366628038; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=tTBT4KoOfA85SAqYSkpTVGcwcw11IuVu/hPwk41Qyf8=; b=cSCssxix4FFUfg1Yei087L7I2pgWvS9/x13skTpSMbrPwJaeQrN5w1SN +DeSS9oEFvV4k24/d4eemINZwQWzFrb47VSpSVoMqS1hbTw5+SFaiKiYC HGJsw0bEVGX2p5WEjMzeYCToDqNK0jcTqA9MIOKHJNhLVPgSfG32xHb0q Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAAOhYlGQ/khN/2dsb2JhbABRgwY2wSiBBxZ0gh8BAQEDATgvEQEQCw4GBAkWCAcJAwIBAgE0EQYNAQUCAQEQh3oGDLxKjyMHg0EDlnSRDoMM
X-IronPort-AV: E=Sophos;i="4.87,429,1363132800"; d="scan'208";a="152633069"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 08 Apr 2013 10:53:56 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r38ArsSI003117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Apr 2013 10:53:54 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r38ArqHx024467; Mon, 8 Apr 2013 11:53:53 +0100 (BST)
Message-ID: <5162A1C0.9020409@cisco.com>
Date: Mon, 08 Apr 2013 11:53:52 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Richard Barnes <rlb@ipv.sx>
Subject: Re: Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-05
References: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com> <515AD8B1.20503@cisco.com> <CAL02cgTExcoC+fMYVs0KT==yx1vZgaK5Tc8Dij3vhiR9Os3YkQ@mail.gmail.com>
In-Reply-To: <CAL02cgTExcoC+fMYVs0KT==yx1vZgaK5Tc8Dij3vhiR9Os3YkQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>, Richard Barnes <rbarnes@bbn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: Mon, 08 Apr 2013 10:53:59 -0000

On 02/04/2013 15:28, Richard Barnes wrote:
> Thanks for following up, and for the re-send.  Just to be clear, I do 
> not mean these as blocking points.
>
> On the former point, I might just suggest a minor edit to the 
> introduction:
> OLD: "This document specifies the options for determination and 
> selection of next-hop Ethernet MAC addressing under these circumstances."
> NEW: "This document specifies the options for determination and 
> selection of next-hop Ethernet MAC addressing when MPLS-TP is used in 
> a "pure Ethernet" manner, without any IP forwarding capability."

After various rounds of tweeking:

"This document specifies the options for the determination and selection 
of the next-hop Ethernet MAC address when MPLS-TP is used between nodes 
that do not have an IP dataplane."

The subtly is the network may be mixed IP capable and non-IP capable.


>
> On the latter point, I can understand the desire to make the simple 
> case simple, and the text at the end of Section 2 sends a clear 
> warning. It does seems like GAP would also allow autoconfiguration 
> without further NMS interaction.  (Unless the NMS is configuring 
> per-Ethernet-address policies, e.g., "forward packets with this label 
> to 00:11:22:33:44:55". Is that the case?)
Yes. One case is a network that is generally NMS configured, and wants 
to use unicast MAC addresses, but wants to allow the craft people to 
plug in a new linecard without talking to the NMS. In such circumstances 
the only auto config would be teh MAC addresses.

Stewart

>
>
>
>
> On Tue, Apr 2, 2013 at 9:10 AM, Stewart Bryant <stbryant@cisco.com 
> <mailto:stbryant@cisco.com>> wrote:
>
>     Resending due to Richards change of address.
>
>     Stewart
>
>
>     On 11/02/2013 23:45, Richard Barnes wrote:
>>     I have been selected as the General Area Review Team (Gen-ART)
>>     reviewer for this draft (for background on Gen-ART,
>>     pleaseseehttp://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html
>>     <http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>). Please
>>     wait for direction from your document shepherd or AD before
>>     posting a new version of the draft. Document:
>>     draft-ietf-mpls-tp-ethernet-
>>     addressing-05
>>     Reviewer: Richard Barnes
>>     Review Date: 2013-02-11
>>     IETF LC End Date: 2013-02-18
>>     IESG Telechat date: TBD
>>
>>     Summary:  Ready, with a couple of minor questions / clarifications.
>>
>>     Comment:
>>
>>     The document is mostly very clearly written.  (Thanks!)  It would have helped me understand if it could have been clarified up front that the mechanism in this document is intended for "pure Ethernet" MPLS-TP (without assumptions about layer 3+).  The current introduction says as much, but in a negative way, in terms of ARP or ND not being available.
>>
>>     I have some minor unease about the distinction that this document makes between point-to-point and multipoint links.  The document correctly notes that a point-to-point link might become multipoint without either end being aware.  I would have thought this would argue for using GAP in all cases, but instead the document carries on with addressing the point-to-point case separately..
>>
>     Richard
>
>     It is always difficult when writing a simple draft dealing with a
>     small
>     component of a larger technology to know how much tutorial to include,
>     but I believe the point about operation in the absence IP would be
>     well known
>     to anyone implementing this. In particular we assume that anyone
>     implementing the draft would have read the required references called
>     up in the first paragraph of the Introduction:
>
>
>     " The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of
>     protocol
>     functions that meet the requirements [RFC5654] for the application of
>     MPLS to the construction and operation of packet-switched transport
>     networks. The MPLS-TP data plane consists of those MPLS-TP functions
>     concerned with the encapsulation and forwarding of MPLS-TP packets
>     and is described in [RFC5960]."
>
>     RFC5654 says:
>
>     "   36  It MUST be possible to operate and configure the MPLS-TP data
>             plane without any IP forwarding capability in the MPLS-TP data
>             plane.  That is, the data plane only operates on the MPLS label."
>     Thus I think that the text is complete as it stands and requires no
>     further clarification for anyone that needs to consider the technology
>     it describes.
>
>
>     With regard to your second point, the issue that we are have, is that
>     there are a number of deployment scenarios where the operator knows
>     that the link is Pt-Pt, and there is a reluctance by that community to
>     use anything other than NMS configuration. That has lead them
>     to use Ethernet broadcast addressing which allows the crafts to
>     change h/w without the need for reconfiguration by the NMS.
>     Against that background moving them onto the use of a Ethernet m/c
>     address is a step forward. To require using the GAP to that
>     community would illustrate that the IETF is out of touch with
>     their needs and methods of network operation.
>
>     Hopefully this additional background, which I believe is well
>     known to the MPLS-TP community to which this draft is directed,
>     satisfies your concern on the latter point.
>
>     - Stewart
>
>
>
>     -- 
>     For corporate legal information go to:
>
>     http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From Ted.Lemon@nominum.com  Mon Apr  8 04:32:42 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E98A21F9382 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 04:32:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MBeiT4cd04uP for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 04:32:41 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id AC77421F9380 for <ietf@ietf.org>; Mon,  8 Apr 2013 04:32:41 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUWKq2RdpmjN/y5oYpSClsBt3Ymiq6ed9@postini.com; Mon, 08 Apr 2013 04:32:41 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5000610838C for <ietf@ietf.org>; Mon,  8 Apr 2013 04:32:41 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 466FF190061; Mon,  8 Apr 2013 04:32:41 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Mon, 8 Apr 2013 04:32:36 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF	April 1 jokes.
Thread-Topic: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF	April 1 jokes.
Thread-Index: AQHONDNbJgYBePWyTkqW0aIJcv6jr5jMpngA
Date: Mon, 8 Apr 2013 11:32:35 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775138028@mbx-01.win.nominum.com>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org> <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com>
In-Reply-To: <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B630775138028mbx01winnominum_"
MIME-Version: 1.0
Cc: =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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, 08 Apr 2013 11:32:42 -0000

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

On Apr 8, 2013, at 4:30 AM, Melinda Shore <melinda.shore@gmail.com<mailto:m=
elinda.shore@gmail.com>> wrote:

Anyway this strikes me as an unfortunate use of those documents.

Although this is not entirely a good thing, it is worth noting that one pur=
pose in creating borders is to lure people across them.


--_000_8D23D4052ABE7A4490E77B1A012B630775138028mbx01winnominum_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <DFFD2B56F9A9DC4B948204613F6153CE@nominum.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; ">
<div>
<div>On Apr 8, 2013, at 4:30 AM, Melinda Shore &lt;<a href=3D"mailto:melind=
a.shore@gmail.com">melinda.shore@gmail.com</a>&gt;&nbsp;wrote:</div>
<blockquote type=3D"cite">
<p style=3D"font-family: Optima; font-size: medium; font-style: normal; fon=
t-variant: normal; font-weight: normal; letter-spacing: normal; line-height=
: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tran=
sform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-tex=
t-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
Anyway this strikes me as an unfortunate use of those documents.</p>
</blockquote>
</div>
Although this is not entirely a good thing, it is worth noting that one pur=
pose in creating borders is to lure people across them.
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B630775138028mbx01winnominum_--

From stbryant@cisco.com  Mon Apr  8 06:21:42 2013
Return-Path: <stbryant@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 B408221F93B1; Mon,  8 Apr 2013 06:21:42 -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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0nezbyUnOi14; Mon,  8 Apr 2013 06:21:41 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1144B21F919A; Mon,  8 Apr 2013 06:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4670; q=dns/txt; s=iport; t=1365427301; x=1366636901; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Q0Xt/neEuvjJ6JCFcjEgH/I9XOwQTECx19TufBP5sOg=; b=L43HiazZqRKXyhRDqPzEeBUuc+4IE7VzlYQOqaltgjxh5vpobmqVJaHa 9YdzYfxe8c4ouZHoDoT2O1QQF2LkCcCiT2VxhOTj4KpXN4LBaP/BwL5wM sbErua4gPogR16/WWCa491UvJnKK8OwfrZRwnFUxZaufRMbyGjfy9QyXB I=;
X-IronPort-AV: E=Sophos;i="4.87,431,1363132800"; d="scan'208";a="81832529"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 08 Apr 2013 13:21:40 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r38DLcUH023639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Apr 2013 13:21:38 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r38DLbpv004576; Mon, 8 Apr 2013 14:21:37 +0100 (BST)
Message-ID: <5162C461.8080303@cisco.com>
Date: Mon, 08 Apr 2013 14:21:37 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Subject: Re: Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
References: <94A203EA12AECE4BA92D42DBFFE0AE470F1636@eusaamb101.ericsson.se>
In-Reply-To: <94A203EA12AECE4BA92D42DBFFE0AE470F1636@eusaamb101.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org List" <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Acee Lindem <acee.lindem@ericsson.com>, "draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org>, "ospf-chairs@tools.ietf.org" <ospf-chairs@tools.ietf.org>, "Abhay Roy \(akr\)" <akr@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: Mon, 08 Apr 2013 13:21:43 -0000

Alvaro

Please can you add a line or two of motivation to the draft.

I don't think it needs to be major text, but it will be useful to
record the reason for the update to the registry.

Thanks

Stewart

On 06/03/2013 15:05, Acee Lindem wrote:
> I think the draft can talk to the motivation in general terms with the
> embedded routing draft cited as an example.
> Thanks,
> Acee
>
> On 3/6/13 7:01 AM, "Stewart Bryant" <stbryant@cisco.com> wrote:
>
>> Chairs
>>
>> Please can you re on the question posed by Alvaro below.
>>
>> Do you have any objection to adding motivation text to the draft?
>>
>> Certainly I think it would be useful in IESG review.
>>
>> Stewart
>>
>> On 11/02/2013 21:15, Alvaro Retana (aretana) wrote:
>>> On 1/16/13 5:17 PM, "Ben Campbell" <ben@nostrum.com> wrote:
>>>
>>> Ben:
>>>
>>> Hi!
>>>
>>> Sorry for the delay, my filters put this in a different place..  I'm
>>> explicitly adding the OSPF chairs.  Comments below.
>>>
>>>
>>>> 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-ospf-ospfv3-iid-registry-update-00
>>>> Reviewer: Ben Campbell
>>>> Review Date: 2013-01-16
>>>> IETF LC End Date: 2013-01-24
>>>>
>>>> Summary: This draft is not ready for publication as a proposed
>>>> standard.
>>>> There is a significant IANA registration issue described in the review
>>>> body.
>>>>
>>>> Major issues:
>>>>
>>>> This draft carves out a significant part of a registry with an
>>>> assignment
>>>> policy of "standards action" for "private use". It offers very little
>>>> motivation for the change. In my opinion, this sort of change should
>>>> come
>>>> with a clear justification.
>>>>
>>>> Specifically, the draft modifies the OSPFv3 Address Family Instance ID
>>>> registry to carve out half of the unassigned space for "private use".
>>>> The
>>>> justification for this is a single sentence saying that some networks
>>>> need to use IIDs to identify specific applications. I think that needs
>>>> significant elaboration in order to motivate the change in a way that
>>>> the
>>>> reader can evaluate.
>>>>
>>>> My understanding from the OFPS list is that this is in support of
>>>> draft-ietf-ospf-ipv4-embedded-ipv6-routing, which is an informational
>>>> draft. I have to wonder why the draft under review was not simply the
>>>> IANA considerations for that draft.
>>>>
>>>> I suggest one of two paths forward:
>>>>
>>>> 1) If this change is in support of that draft in particular, then this
>>>> draft should say that, and include a _normative_ reference. I recognize
>>>> the normative downref would complicate things--but I think that
>>>> complication is reasonable under the circumstances.
>>>>
>>>> 2) If this change is to support a general need that goes beyond
>>>> draft-ietf-ospf-ipv4-embedded-ipv6-routing, then this draft should
>>>> describe that need in enough detail for people to think about it,
>>>> perhaps
>>>> with an informative reference to
>>>> draft-ietf-ospf-ipv4-embedded-ipv6-routing as an _example_.
>>> In short (from the shepherd write-up): "The new range is for
>>> applications
>>> that do not justify a standards track OSPFv3 Instance ID allocation. An
>>> example would be "Routing for IPv4-embedded IPv6 Packets"".
>>>
>>> During pre-publication review, the WG chairs asked us to not include
>>> explicit references to draft-ietf-ospf-ipv4-embedded-ipv6-routing as
>>> that
>>> is just an example and not the only potential user/driver.  I don't
>>> have a
>>> problem adding an example, but I want to get agreement/comments/guidance
>>> from the chairs before adding the text.  Acee/Abhay??
>>>
>>>
>>>> Minor issues:
>>>>
>>>> -- section 3:
>>>>
>>>> I don't think it's appropriate to use normative language for IANA
>>>> requests. Especially not "MUST". (I think the strongest thing we can do
>>>> here is a polite request :-)  )   I suggest recasting that to
>>>> descriptive
>>>> language, and removing section 2 and the RFC 2119 reference.
>>> Yes, we already removed that in the -01 version.
>>>
>>> Thanks!!
>>>
>>> Alvaro.
>>>
>>> .
>>>
>>
>> -- 
>> For corporate legal information go to:
>>
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From melinda.shore@gmail.com  Mon Apr  8 06:38:20 2013
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 27C3421F940D for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 06:38:20 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VlYY6wYp3MUZ for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 06:38:19 -0700 (PDT)
Received: from mail-vb0-x22c.google.com (mail-vb0-x22c.google.com [IPv6:2607:f8b0:400c:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1E81C21F940F for <ietf@ietf.org>; Mon,  8 Apr 2013 06:38:16 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id e12so3862397vbg.3 for <ietf@ietf.org>; Mon, 08 Apr 2013 06:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ve7CNE1L0+udViUdvgrCcXTBsyQbpnxCGsiDKMVw+t0=; b=g4NNE+yq0zMDlBpyVveiElzniqAMHW+o9bmb7LeG75LVi5XNG2xFpQXL0xTWpv6FeQ qeq3V33/vqNBvKB3Ntb3gbbMTZMpMQ2x7fc87vKApTYKk52WZobAteChwZNBjcV1vEnV j7T08W0j5EgrldhqlWLWamxN8Qgj8Z7XMITRrS2PNhQXSgbWR181AWsZSYS6exAW5i3s K/ALxHb+iU/3/aRqsDRjKtNFyl/mW1YtOTIJW3kXGm62g/tkJySIPqY4Hnuglj4Ls4Au woD67FsmOfYSr9yIJaZGABpSstVFDCrOmZvwEH9vdDpG605o16Ao00bYDZTVKYRbVE8V LUxA==
MIME-Version: 1.0
X-Received: by 10.58.96.40 with SMTP id dp8mr15863498veb.41.1365428295741; Mon, 08 Apr 2013 06:38:15 -0700 (PDT)
Received: by 10.58.65.39 with HTTP; Mon, 8 Apr 2013 06:38:15 -0700 (PDT)
Received: by 10.58.65.39 with HTTP; Mon, 8 Apr 2013 06:38:15 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775138028@mbx-01.win.nominum.com>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org> <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775138028@mbx-01.win.nominum.com>
Date: Mon, 8 Apr 2013 05:38:15 -0800
Message-ID: <CAKRbAfA4S3iuYmER=Fm9b10yJ_yQ8hi+zY0uZifdXuSMt7C3FQ@mail.gmail.com>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
From: Melinda Shore <melinda.shore@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=089e01229c8a88baf004d9d98c2e
Cc: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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, 08 Apr 2013 13:38:20 -0000

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

Well, the timing of this strikes me as one of those "oh" moments, following
as quickly on the heels of the diversity discussion.  Not so much because
of language and culture issues (although those are unavoidable) but because
it strikes me as kind of unhealthy to use the April Fool RFCs as a tool to
partition the audience into "us" and "them".

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

<p>Well, the timing of this strikes me as one of those &quot;oh&quot; momen=
ts, following as quickly on the heels of the diversity discussion.=A0 Not s=
o much because of language and culture issues (although those are unavoidab=
le) but because it strikes me as kind of unhealthy to use the April Fool RF=
Cs as a tool to partition the audience into &quot;us&quot; and &quot;them&q=
uot;.=A0 </p>


--089e01229c8a88baf004d9d98c2e--

From Ted.Lemon@nominum.com  Mon Apr  8 06:50:46 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48FD121F9310 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 06:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.591
X-Spam-Level: 
X-Spam-Status: No, score=-106.591 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FMtVli7hnleY for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 06:50:45 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 32EC121F93EE for <ietf@ietf.org>; Mon,  8 Apr 2013 06:50:45 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUWLLNLb04d6ekX5iZEESe1FeIVXPsYqR@postini.com; Mon, 08 Apr 2013 06:50:45 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 41DCF108390 for <ietf@ietf.org>; Mon,  8 Apr 2013 06:50:44 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 36D71190061; Mon,  8 Apr 2013 06:50:44 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Mon, 8 Apr 2013 06:50:44 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Thread-Topic: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Thread-Index: AQHONF5T+AxkI98yjUytpmx8/mQFEJjMzLyA
Date: Mon, 8 Apr 2013 13:50:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751383B4@mbx-01.win.nominum.com>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org> <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775138028@mbx-01.win.nominum.com> <CAKRbAfA4S3iuYmER=Fm9b10yJ_yQ8hi+zY0uZifdXuSMt7C3FQ@mail.gmail.com>
In-Reply-To: <CAKRbAfA4S3iuYmER=Fm9b10yJ_yQ8hi+zY0uZifdXuSMt7C3FQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751383B4mbx01winnominum_"
MIME-Version: 1.0
Cc: =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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, 08 Apr 2013 13:50:46 -0000

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

On Apr 8, 2013, at 9:38 AM, Melinda Shore <melinda.shore@gmail.com<mailto:m=
elinda.shore@gmail.com>> wrote:

Well, the timing of this strikes me as one of those "oh" moments, following=
 as quickly on the heels of the diversity discussion.  Not so much because =
of language and culture issues (although those are unavoidable) but because=
 it strikes me as kind of unhealthy to use the April Fool RFCs as a tool to=
 partition the audience into "us" and "them".

Sure, that's clearly a problem to think about.   But my point was just that=
 you can see it as something to divide us, or something to bring us togethe=
r; what's important is that it in fact be used for the latter, and not the =
former.   But the essence of inclusiveness is not that we eliminate differe=
nces; if we did that, diversity wouldn't do us much good.   The essence of =
inclusiveness is being open and welcoming to diversity, and having, if not =
a sense of humor about differences, at least a tolerance for them.   Suppre=
ssing in-jokes is just as bad as excluding people who don't appreciate them=
.


--_000_8D23D4052ABE7A4490E77B1A012B6307751383B4mbx01winnominum_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <AD4CD3FC549CA8468C81FB8F57D2491B@nominum.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; ">
<div>
<div>On Apr 8, 2013, at 9:38 AM, Melinda Shore &lt;<a href=3D"mailto:melind=
a.shore@gmail.com">melinda.shore@gmail.com</a>&gt;&nbsp;wrote:</div>
<blockquote type=3D"cite">
<p>Well, the timing of this strikes me as one of those &quot;oh&quot; momen=
ts, following as quickly on the heels of the diversity discussion.&nbsp; No=
t so much because of language and culture issues (although those are unavoi=
dable) but because it strikes me as kind of unhealthy
 to use the April Fool RFCs as a tool to partition the audience into &quot;=
us&quot; and &quot;them&quot;.&nbsp;
</p>
</blockquote>
</div>
Sure, that's clearly a problem to think about. &nbsp; But my point was just=
 that you can see it as something to divide us, or something to bring us to=
gether; what's important is that it in fact be used for the latter, and not=
 the former. &nbsp; But the essence of inclusiveness
 is not that we eliminate differences; if we did that, diversity wouldn't d=
o us much good. &nbsp; The essence of inclusiveness is being open and welco=
ming to diversity, and having, if not a sense of humor about differences, a=
t least a tolerance for them. &nbsp; Suppressing
 in-jokes is just as bad as excluding people who don't appreciate them.
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751383B4mbx01winnominum_--

From melinda.shore@gmail.com  Mon Apr  8 06:57:55 2013
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 E8F5621F95DA for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 06:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level: 
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOHDFHf0qPJt for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 06:57:55 -0700 (PDT)
Received: from mail-vc0-f170.google.com (mail-vc0-f170.google.com [209.85.220.170]) by ietfa.amsl.com (Postfix) with ESMTP id 65E0521F95D2 for <ietf@ietf.org>; Mon,  8 Apr 2013 06:57:55 -0700 (PDT)
Received: by mail-vc0-f170.google.com with SMTP id lf10so1425835vcb.1 for <ietf@ietf.org>; Mon, 08 Apr 2013 06:57:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=rofznzZNjO2IY1Kzn2OGeFs8ILx+Z2EOmnqxCjbvjjU=; b=F2qx4iFipMt8I2PgJDWDXJXsVo2X4s45BF6qOIdd9BuKRvvvLZr3BrpCNvGDEcvVS7 DFkl0D5DnbGSyuQPx5vgFRShnIyeo3WA5tALl5F/vr/ybZi8FwWbUd/GA2VXXPNI22a2 Pt7NFrdtM2B7g6CNeRLhr5LO0CMdDlTlrkEQE3h0TGqpOATxYG0B+saiqFzUOnBaBDPV PkXUP6ZO0LAsMaImzS5XVf/pW1VDOD0MeXwzKhtem9l3BUomhbxmltyNQ4jcsWopjGOe ZcTjCek85aoOY3GmHDzFKR6o1VTv5VIxA6OXTduY0vfGldtTp+AMeWfp1uJRUUV+0T1r mNRw==
MIME-Version: 1.0
X-Received: by 10.52.97.131 with SMTP id ea3mr9690033vdb.71.1365429474930; Mon, 08 Apr 2013 06:57:54 -0700 (PDT)
Received: by 10.58.65.39 with HTTP; Mon, 8 Apr 2013 06:57:54 -0700 (PDT)
Received: by 10.58.65.39 with HTTP; Mon, 8 Apr 2013 06:57:54 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751383B4@mbx-01.win.nominum.com>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org> <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775138028@mbx-01.win.nominum.com> <CAKRbAfA4S3iuYmER=Fm9b10yJ_yQ8hi+zY0uZifdXuSMt7C3FQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751383B4@mbx-01.win.nominum.com>
Date: Mon, 8 Apr 2013 05:57:54 -0800
Message-ID: <CAKRbAfAxddKNKGPrvOTgMRD0AiJjEdZd9aKPMH_0gzTQn0DMgQ@mail.gmail.com>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
From: Melinda Shore <melinda.shore@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=20cf307cfc7ed1b61804d9d9d2fb
Cc: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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, 08 Apr 2013 13:57:56 -0000

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

I am absolutely not suggesting changing anything other than the
unfortunate  attitude that the right response to someone missing the joke
is to read them out of the meeting/declare them anathema or unworthy or not
members of this community.  Your beef isn't with me, it's with M=E5ns.

Melinda

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

<p>I am absolutely not suggesting changing anything other than the unfortun=
ate=A0 attitude that the right response to someone missing the joke is to r=
ead them out of the meeting/declare them anathema or unworthy or not member=
s of this community.=A0 Your beef isn&#39;t with me, it&#39;s with M=E5ns.<=
/p>

<p>Melinda </p>

--20cf307cfc7ed1b61804d9d9d2fb--

From wbeebee@cisco.com  Mon Apr  8 07:27:20 2013
Return-Path: <wbeebee@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 2864921F9798 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:27:20 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iLEJYdZUndMp for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:27:19 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 5A7EA21F9797 for <ietf@ietf.org>; Mon,  8 Apr 2013 07:27:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=132; q=dns/txt; s=iport; t=1365431239; x=1366640839; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=GEYu67WbwsupT1hh70vnJTTzI0cMgf8oGL28HA2VuQA=; b=Nzn+YN+wISAGMhF8nz5a1fqZHXa7iQD7aJ0cM1nFUUYLnOGFXRsA3tRV K+o2YoQAlx4odQtQklCMtlbs6UZpl6+Cbg+eZHt4/6NP9sG9zo/6JGI+I X+Hzh20MiPLSKzx3dqxSqU8Ub4a6VSOGhps+4riA/lArOBgXfYTCrIdu5 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAB3TYlGtJXHA/2dsb2JhbABRgwbBXoEIFnSCIQEEOlEBCCIUQiUCBAEaiAy8bY5yOIJgYQOoAoMLgig
X-IronPort-AV: E=Sophos;i="4.87,432,1363132800"; d="scan'208";a="196190370"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 08 Apr 2013 14:27:19 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r38ERIki015792 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 8 Apr 2013 14:27:18 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.173]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Mon, 8 Apr 2013 09:27:18 -0500
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
Thread-Topic: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
Thread-Index: AQHONGUs7oD0J9AT80iuEN0YYKw6Dg==
Date: Mon, 8 Apr 2013 14:27:17 +0000
Message-ID: <9515564336C5B442A00021645539CFCC28A1403D@xmb-rcd-x08.cisco.com>
In-Reply-To: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [10.131.71.105]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <93A46B21BD275E458953234F15B4C0E8@emea.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: Mon, 08 Apr 2013 14:27:20 -0000

>If the date is special then thoes RFCs SHOULD be *historical*.

I thought they should be classified as "hysterical".

- Wes


From dhc@dcrocker.net  Mon Apr  8 07:30:59 2013
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 AE7EA21F9423 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:30:59 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oyUlVMDMEIqF for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:30:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2033721F9415 for <ietf@ietf.org>; Mon,  8 Apr 2013 07:30:59 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r38EUvgD005598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 8 Apr 2013 07:30:58 -0700
Message-ID: <5162D4A0.3090101@dcrocker.net>
Date: Mon, 08 Apr 2013 07:30:56 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: team to look at diversity
References: <E41A7C0D-470D-4480-824F-2AA8CFAB3677@piuha.net> <C001659D-B342-4D84-9361-D617AF33BE4B@tzi.org>
In-Reply-To: <C001659D-B342-4D84-9361-D617AF33BE4B@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]); Mon, 08 Apr 2013 07:30:58 -0700 (PDT)
Cc: "ietf@ietf.org Discussion" <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, 08 Apr 2013 14:30:59 -0000

On 4/1/2013 11:09 PM, Carsten Bormann wrote:
> The most important insight is that diversity is not a "problem" that
> can be "fixed" by some set of measures, but a process that needs to be
> ongoing.

+1


> -- Reducing situations that are perceived as hostile by members of
>     specific groups.
>
> -- Working on incentive structures that are useful for diverse groups.

Reference to 'diversity' often simplifies to some statistics about 
representation of various, identified groups, without considering the 
pragmatics (and effects) of having diversity. Lack of diversity is, as 
you note, considered a "problem" that is fixed by improving some 
statistics and reducing the group's range permissible topics.  This 
makes the group environment more restrictive, rather than richer.

Such discussions will make polite reference to the need for cultural 
sensitivities, and the like, but don't actually grapple with the 
pragmatics of changing the group culture.  Besides a basic sense of 
fairness, what sorts of group changes in behavior are we looking for? 
These can be cast as affirmative /improvements/ in the culture.

What I like most about your note is that it seeks to consider this 
question.  The term "diversity" is essentially about inputs to the 
group.  Your note suggests thinking about what I'll conveniently call 
outputs of the group -- outputs to itself...

If we combine this line of consideration with the need for statistical 
diversity, we can seriously talk about ways to adjust IETF culture to 
maintain what we like and need in the IETF, and remove what we find 
counter-productive.


>    I don't even know what other people
> might perceive as hostile; that would be good input for the design
> team.

+1

We currently have a culture that is extraordinarily accepting of 
behaviors that are highly unprofessional, to the point of having chairs 
and area directors refusing to pursue ad hominem attacks.  An 
environment like that is particularly untenable to anyone from a culture 
that emphasizes politeness.


>     What can we
> improve with respect to the incentive structures for other groups,
> say, people from operators or from small businesses?

I suppose the first requirement is to identify the groups we want to 
provide with better incentives.  You've cited academics and operators, 
of course.  Who else?

Then the question is to guess at the sorts of changes, either in /what/ 
we do, or /how/ we do it, that might constitute improved incentives.

d/




-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From turners@ieca.com  Mon Apr  8 07:33:12 2013
Return-Path: <turners@ieca.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B7CA21F97B6 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.931
X-Spam-Level: 
X-Spam-Status: No, score=-101.931 tagged_above=-999 required=5 tests=[AWL=-0.266, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_66=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LazzePIKflcY for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:33:00 -0700 (PDT)
Received: from gateway03.websitewelcome.com (gateway03.websitewelcome.com [69.93.37.25]) by ietfa.amsl.com (Postfix) with ESMTP id 992AF21F9756 for <ietf@ietf.org>; Mon,  8 Apr 2013 07:32:58 -0700 (PDT)
Received: by gateway03.websitewelcome.com (Postfix, from userid 5007) id 555EC79CC001D; Mon,  8 Apr 2013 09:32:58 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway03.websitewelcome.com (Postfix) with ESMTP id 3601579CBFF84 for <ietf@ietf.org>; Mon,  8 Apr 2013 09:32:58 -0500 (CDT)
Received: from [108.45.16.214] (port=52304 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UPD7x-0001Dh-Nh; Mon, 08 Apr 2013 09:32:58 -0500
Message-ID: <5162D519.1090209@ieca.com>
Date: Mon, 08 Apr 2013 10:32:57 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Denis <denis.ietf@free.fr>
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP to Proposed Standard
References: <51536616.3020607@free.fr>
In-Reply-To: <51536616.3020607@free.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [108.45.16.214]:52304
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 6
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: ietf@ietf.org, Stephen Kent <kent@bbn.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, 08 Apr 2013 14:33:12 -0000

On 3/27/13 5:35 PM, Denis wrote:
> First of all, this is an announcement: I am retiring from Bull at the
> end of this week, this why I am now using a new email address.

Hopefully, you'll still find time in your retirement to keep on PKIXing!

> The second announcement is that I am taking one full month off
> (vacations) and will be traveling in Asia.
> So, I will not be able to respond quickly on the list.
>
> I am getting bored of 2560bis which was started more than 3 years ago
> and everybody in the WG is getting bored too.

I agree it's time to get this one done.

> However, it is the last chance to correct what is still incorrect in the
> draft.

There are some changes warranted by these comments.  Some are already 
addressed in v16.  Some I don't see consensus around making.

> During the PKIX WG last call, Stefan Santesson replied to many of my
> comments with "Not broken", meaning that it considered
> that the current wording did not have such problems that it merits a change.
>
> I said that it would have been a waste of time for both of us to argue
> again at the WG level and thus that I will resend
> these comments during the IETF LC. We are now at that stage.
>
> The 11 comments were originally numbered 2, 3, 7, 10, 12, 14, 15, 16,
> 17, 25 and 27. I have kept the same numbering.
>
> *Comment 2

Here we're talking about the protocol overview section, which is where 
authors usually say things like my protocol is great and here's why. The 
text says:

    OCSP may
    be used to satisfy some of the operational requirements of providing
    more timely revocation information ...

I'm not hearing a bunch of implementers saying the overview is confusing 
and they're being unfairly swayed/tricked in to implementing OCSP over 
CRLs; All thanks to that goes to the US DoD and their monolithic CRLs.

> The current text from section 2 states:
>
> 2.   Protocol Overview
>
>     In lieu of or as a supplement to checking against a periodic CRL, it
>     may be necessary to obtain*timely information*  regarding the
>     revocation status of a certificate (cf. RFC5280], Section 3.3).
>     Examples include high-value funds transfer or large stock trades.
>     The Online Certificate Status Protocol (OCSP) enables applications to
>     determine the (revocation) state of an identified certificate. OCSP
>     may be used to satisfy some of the operational requirements of
>     providing*more timely revocation information*  than is possible with
>     CRLs and may also be used to obtain additional status information.
>
> This text is misleading because readers may think that OCPS necessarily provides “timely information”.
>
> Proposed text replacement:
>
> *The Online Certificate Status Protocol (OCSP) is a client-server *
> *protocol which enables applications to obtain the revocation status *
> *of one or more certificates either "good", "revoked", or "unknown".*
> *The revocation status may be provided by the server either using a *
> *real time access to a database of issued certificates, or using a *
> *batch access to a database of issued certificates, or using a *
> *real time access to a database of revocation statuses of issued *
> *certificates, or using a batch access to a database of revocation *
> *statuses of issued certificates, or using CRLs, or using a *
> *combination of base CRLs and delta CRLs.*
> *In the first case, it is possible to obtain timely revocation status *
> *information, whereas in the other cases, the freshness of the *
> *revocation status is not better than the mechanisms it is based on.*
>
> Stefan answered “Not broken” and added “"may" does not mean "necessarily".
>
> This does not solve the issue since the text is misleading an OCSP
> server may only use CRLs
> and then it does not provides timely information since the information
> it provides is not better that CRLs.
> How can a normal reader guess this ?
>
> *Comment 3*

Addressed by in v16.

> The current text from section 2 states:
>
> *    An OCSP client issues a status request to an OCSP responder and*
> *    Suspends acceptance of the certificate in question until the*
> *    responder provides a response.*
> *  *
> *    This protocol specifies the data that needs to be exchanged between*
> *    an application checking the status of a certificate and the server*
> *    providing that status.*
>
> Thus is insufficient for an overview. More details are needed to know what the document provides,
> in particular that the request may contain several requests for several certificates issued by different CAs.
> The possibility of using extensions should also be advertised.
>
> Proposed text replacement:
>
> *When using OCSP, an OCSP client issues a certificate revocation ***
> *status request to an OCSP responder for one or more certificates ***
> *issued by the same CA or for one or more certificates issued by ***
> *different CAs and then suspends acceptance of the certificate(s) ***
> *in question until the responder provides a response.***
>
> **
>
> *This document specifies the data that needs to be exchanged between***
> *an application checking the status of a certificate and the server***
> *providing that status.***
>
> *OCSP may also provide additional status information using ***
> *extensions. ***
>
> When using the wording “acceptance of the certificate” the singular is
> being used
> and the reader may not realize that the protocol allows to ask the
> status of several certificates.
>
> *Comment 7

There's four things listed there.  status is discussed at length in s2.2 
and s4.2.2.3.  The remaining 3 fields are discussed in s4.2.2.3, 
s4.2.2.1, and s4.2.2.3, respectively.  The bits of text about 
determining who signed what is addressed in s4.2.2.2.

I think this one is addressed.  If others disagree, I have no doubt 
they'll let me know.

> *
> The text states on page 7:
>
> *The response for each of the certificates in a request consists of*
> *-target certificate identifier*
> *-certificate status value*
> *-response validity interval*
> *-optional extensions*
>
> However, there are no explanations for the purpose of these parameters
> and how they should be processed.
>
> There are also no explanations on how to process _a single response_ and
> how to verify that it is its presence
> within the signed structure is valid or not valid. This is a _major
> deficiency of the current description of RC 2560
> where there is no explanation on how to validate a single response. This
> is the most important comment.
> _
>
> Text proposal to be added after:
>
> *The purpose of the identifier of the OCSP server is to allow OCSP *
> *clients to find whether the definitive response was signed by a CA *
> *or by an OCSP Responder.
> *
>
> *The identifier of the OCSP server SHOULD either be the name or the *
> *key from a CA, or the name or the key from a OCSP Responder.*
> *Unless there exist local rules (which are outside the scope of this *
> *document) for verifying that a single response is correctly signed, *
> *the following applies:
>
> *
>
> *When the identifier matches with the name of the CA which has issued *
> *the target certificate or corresponds to the key used to issue the *
> *target certificate, then a single response is correctly signed *
> *only if the digital signature of the OCSP response is valid using the *
> *key used to sign the target certificate.
> *
>
> *When the identifier does not match with the name of the CA which has *
> *issued the target certificate or does not correspond to the key used *
> *to issue the target certificate, then an single response is correctly *
> *signed only if :
>
> *
>
> *(a) there exists in the response an OCSP certificate issued by *
> *the CA which has issued the target certificate which is *
> *signed by the same key as the one used to issue the *
> *target certificate, and*
> *(b) the digital signature of the OCSP response is valid using *
> *the subjectPublicKey contained in this OCSP certificate.*
>
> Stefan answered “Not broken” and claimed that “All of this is already
> covered by the document”.
>
> Unfortunately, this is not the case.
>
> *Comment 10

I think implementers can figure out that the bullets in s2.2:

  -  time when the response was generated
  -  response validity interval

correspond to producedAt and thisUpdate/nextUpdate in s2.4.  So I don't 
see the harm in leaving the section where it is.

I consider this one adddressed/adopted except for two little bits that 
need to be addressed/added:

Put a number in and I'll count 'em; there's four times in OCSPResponse. 
  Another time is in revokedInfo and we in fact need to say something 
about it in s2.2, s.2.4, and s4.2.2.1.

For s2.2:

OLD:

   o  the revocation status of the certificate (good, revoked, or
      unknown);

NEW:

   o  the revocation status of the certificate (good, revoked, or
      unknown); if revoked it indicates the time at which the
      certificate was revoked and optionally the reason why it
      was revoked.

For s2.4:

Responses can contain four times - thisUpdate, nextUpdate, producedAt, 
and revokedAt. The semantics of these fields are:

  - thisUpdate: The time at which the status being indicated is known
                to be correct.
  - nextUpdate: The time at or before which newer information will be
                available about the status of the certificate.
  - producedAt: The time at which the OCSP responder signed this
                response.
  - revokedAt: The time at which the certificate was revoked.

It will also stop people saying producedAt is the revocationTime.  It 
might be but it might not be.

For s4.2.2.1:

OLD:

  Responses can contain three times in them - thisUpdate, nextUpdate,
  and producedAt. ...

NEW:

  Responses can contain four times - thisUpdate, nextUpdate,
  producedAt, and revokedAt. ....

Somewhere the draft needs to say what format is required of 
GeneralizedTime.  I assume it's Zulu time.  If so add the following to 
the end of the 1st paragraph in s4.2.2.1:

   The format for GeneralizedTime is as specified in Section 4.1.2.5.2
   of [RFC5280].

After all this gets incorporated I'll consider this one addressed/adopted.

> The text states on page 8:
>
> *2.4Semantics of thisUpdate, nextUpdate and producedAt*
>
> This section is misplaced. At this time of reading, the reader does not
> know that thisUpdate,
> nextUpdate and producedAt are values used by the ASN.1 structures. It is
> appropriate to describe
> what theses parameters mean when the ASN.1 syntax is described.
> The current ASN.1 syntax is very badly described. One would expect that
> after every ASN.1 structure
> description every parameter is described.
>
> Unfortunately this is not the case.
>
> The text from this section is not aligned with the text that is present
> in section 4.2.2.1.
>
> In particular, in section 2.4:
>
> *
> If nextUpdate is not set, the responder is indicating that newer*
> *revocation information is available all the time.*
>
>
> While in section 4.2.2.1:
>
> *
> Responses where the nextUpdate value is not set are equivalent
> to a CRL with no time for nextUpdate (see Section 2.4).*
>
> It is not appropriate to have two different descriptions in two
> different places.
>
> Delete section 2.4. See comment number 19 for the description of these
> parameters.
>
> Stefan answered : Not broken and added ”The current text segments fits
> well into a protocol overview section”.
>
> However, he did not realize that the two sentences do not say the same
> thing.
>
> *Comment 14

v16 addresses this without removing the text.

> The text states on page 11:
>
> *
> 3.2Signed Response Acceptance Requirements*
>
> *Prior to accepting a signed response as valid, OCSP clients SHALL*
> *confirm that:*
>
> *1. The certificate identified in a received response corresponds to*
> *that which was identified in the corresponding request;*
>
> *2. The signature on the response is valid;*
>
> *3. The identity of the signer matches the intended recipient of the*
> *request.*
>
> *4. The signer is currently authorized to sign the response.*
>
> *5. The time at which the status being indicated is known to be*
> *correct (thisUpdate) is sufficiently recent.*
>
> *6. When available, the time at or before which newer information will*
> *be available about the status of the certificate (nextUpdate) is*
> *greater than the current time.*
>
>
> This section is misplaced since it uses terms from the ASN.1 syntax and
> the protocol description has not yet been made,
> since it is the next section 4. Its text is not correct either.
>
>
> This description does not take into account the fact that
> a*BasicOCSPResponse *may contain one or several *SingleResponses. *
> In particular, the sentence“*The signer is currently authorized to sign
> the response*” is misleading because a signer
> may be authorized to include some***SingleResponses *but not necessarily
> all of them.
>
>
> The appropriate explanations should be done after the description of the
> response, when describing the processing of the response.
>
>
> Delete that section.
>
> Stefan answered “Not broken”.
>
> However, the important matter is to make the difference between single
> responses and the basic response.
> The basic response cannot be validated, only single responses can be
> INDIVIDUALLY validated. This text is wrong
> (or is only valid when the request contains a single certificate request).
>
> *Comment 15*

When reading this comment I considered would implementers be confused by 
the lack of text about these fields.  I believe the answer is no, but I 
also know I'd hammer/discuss protocols for not describing them so some 
text will be included to describe the fields.

I'll leave it to the editor as to whether he'd prefer to leave it in 
s4.1.1 or move the whole thing to s4.1.2.  Here's my suggestion:

putting the following before the OCSPRequest ASN.1:

The ASN.1 structure corresponding to the OCSPRequest is:

In s4.1.2 before the existing text (and keep the existing text as is) 
I'd add:

The fields in OCSPRequest have the the following meanings:

o tbsRequest is the optionally signed OCSP request.

o optionalSignature contains the algorithm identifier and any associated 
algoirthm parameters in signatureAlgorithm, the signature value in 
signature, and optionally certificates the server needs to verify the 
signed response (normally up to but not including the client's root 
certificate).

The contents of tbdRequest include the following fields:

o version indicates the version of the protocol, which for this document 
is v1(0).

o requestorName is OPTIONAL and indicates the name of the OCSP requestor.

o requestList contains one or more single certificate status requests.

(note for you Stefan Denis says one or more but the ASN.1 doesn't say 
that - I think it's safe to say that's what was meant though.

o requestExtension is OPTIONAL and includes extension applicable to the 
all requests found in reqCert.  See Section 4.4.

o reqCert contains the identifier of a target certificate and includes:

* issuerNameHash is the hash of the Issuer's distinguished name.  The 
hash shall be calculated over the DER encoding of the issuer's name 
field in the certificate being checked.

* issuerKeyHash is the hash of the Issuer's public key.  The hash shall 
be calculated over the value (excluding tag and length) of the subject 
public key field in the issuer's certificate.

* The hash algorithm used for both these hashes, is identified in 
hashAlgorithm.

* singleRequestExtensions is OPTIONAL and includes extensions applicable 
to this single certificate status request.  See Section 4.4.

-----

Now don't go and say well now we need to do the same thing in s4.2.1; 
it's different all but one of those fields are discussed later :)  Might 
not be as explicit as s4.2.1, but the description in s4.2.2.3 is mighty 
clear.  The one missing description is for algorithmIdentifier and a one 
sentence addition in s4.2.1 fixes this (a new second sentence):

OLD:

  The value for signature SHALL be computed on the hash of the DER
  encoding ResponseData. The responder MAY include certificates in the
  certs field of BasicOCSPResponse that help the OCSP client verify the
  responder's signature. If no certificates are included then certs
  SHOULD be absent.

NEW:

  The value for signature SHALL be computed on the hash of the DER
  encoding ResponseData. The algorithm and any parameters used to
  generate the signature are included in the signatureAlgorithm field.
  The responder MAY include certificates in the certs field of
  BasicOCSPResponse that help the OCSP client verify the
  responder's signature. If no certificates are included then certs
  SHOULD be absent.

I consider this one addressed/adopted based on as-yet-not published v17.

> On page 12, after the ASN.1 description, the only parameters which are
> described are:
>
> *hashAlgorithm,**issuerNameHash, issuerKeyHash and serialNumber.*
>
> This is insufficient.In order to cover the full list of parameters, the
> following text is proposed:
>
> *requestorName is optional and MAY be used by the server for access *
>
> *control and audit purposes.*
>
> *requestList contains one or more single requests.*
>
> *requestExtensions is OPTIONAL.Any specific extension is OPTIONAL.*
>
> *The critical flag SHOULD NOT be set for any of them. Section 4.4 *
>
> *suggests several useful extensions.Additional extensions MAY be *
>
> *defined in additional RFCs.*
>
> *reqCert contains the identifier of a target certificate.*
>
> *issuerNameHash is the hash of the Issuer's distinguished name.The *
>
> *hash shall be calculated over the DER encoding of the issuer's name *
>
> *field in the certificate being checked. *
>
> *issuerKeyHash is the hash of the Issuer's public key.The hash *
>
> *shall be calculated over the value (excluding tag and length) of the *
>
> *subject public key field in the issuer's certificate.The hash *
>
> *algorithm used for both these hashes, is identified in *
>
> *hashAlgorithm. *
>
> *The primary reason to use the hash of the CA's public key in *
>
> *addition to the hash of the CA's name, to identify the issuer, *
>
> *is that it is possible that two CAs may choose to use the same *
>
> *name (uniqueness in the Name is a recommendation that cannot be *
>
> *enforced). Two CAs will never, however, have the same public key *
>
> *unless the CAs either explicitly decided to share their private *
>
> *key, or the key of one of the CAs was compromised.*
>
> *serialNumber is the serial number of the certificate for which *
>
> *status is being requested.*
>
> *singleRequestExtensions is OPTIONAL.Any specific extension is *
>
> *OPTIONAL.The critical flag SHOULD NOT be set for any of them. *
>
> *The requestor MAY choose to sign the OCSP request.In that case, the*
>
> *signature is computed over the tbsRequest structure.If the request*
>
> *is signed, the requestor SHALL specify its name in the requestorName*
>
> *field.Also, for signed requests, the requestor MAY include*
>
> *certificates that help the OCSP responder verify the requestor's*
>
> *signature in the certs field of Signature.*
>
> Stefan answered: “Not broken. The current text is short, but it is
> actually sufficient from the context of the ASN.1 definitions
> of the section. This is a detailed protocol section and the reader need
> to understand ASN.1 in any case to understand
> and implement the section.
>
>
> The information about criticality is already covered in the extension
> section”.
>
> I disagree the current text is so short that it omits to define the
> semantics and the use of most parameters.
>
> *Comment 16*

I can see moving all of the fields' descriptions to s4.1.2 or putting 
the new text in s4.1.1 and point back to s4.1.2.  I think this is 
editorial and I'll leave it to the editor.  In other words adopting 
comment 15 means this is adopted too in one form or another.

I consider this one addressed/adopted based on as-yet-not published v17.

> Section 4.1.2 is called: *“Notes on the Request Syntax”*
>
> The first paragraph has been moved after the description
> of*issuerKeyHash *and thus is no more needed.
>
> The second paragraph has been moved after the description
> of*requestExtensions. *
> However, the sentence
> “ *Unrecognized extensions MUST be ignored (unless they have the
> critical flag set and are not understood)*”
> has been deleted since it applies to the OCSP responder and not to the
> OCSP client. Thus it is no more needed.
>
> The third paragraph applies to signed requests. However, it should
> belong to a section dedicated on how clients should build OCPS requests,
> which is currently missing. See the next comment.
>
> This section should be deleted.
>
>
> Stefan answered ”Not broken”.
>
> I disagree. The rules are to describe the ASN.1 syntax and to explain
> every parameters used in the syntax. The initial draft has been very
> badly written and it is time to write it correctly now.
>
> *Comment 17*

There's two nuggets in here and the rest is text that need not be 
repeated (and in v16 Stefan addresses the multiples issue).

Nugget 1: The sentence about grouping status information about 
certificates from the same URI in on OCSPRequest.  The MAY adds nothing 
so I just can't see the need for it.  Clients might do it or they might 
not and that just doesn't seem like useful advice to implementers.

Nugget 2: For status checks on certificates beyond their validity 
there's an archive cutoff extension so indicating SHOULD NOT seems 
incorrect as you're basically deprecating that feature.  I've not seen 
any kind of consensus around that in the WG or here.

I'd consider this one closed unless a ground swell begins soon.

> There should be a new section called: “*Requirements for OCSP clients”. *
>
>
> It is important first to re-advertise that the request may be about
> several certificates.
> Thus it is important to describe the process for building a request,
> which is currently missing.
>
> *
> An OCSP request allows getting in the same response the revocation *
> *status of one or more certificates.In order to request the *
> *status of one or more certificates in a single request, OCSP *
> *clients SHALL follow the following rules :*
>
> **
>
> *For each candidate certificate, OCSP clients SHALL verify *
> *whether there exists a locally defined rule for the certificate in *
> *question which indicates the URI where the OCSP responder is *
> *located.If this rule exists, it SHALL be followed. *
> *Otherwise, OCSP clients SHALL determine whether the candidate *
> *certificate contains an AIA extension with an accessMethod which *
> *contains the id-ad-ocsp OID.If it is the case, the accessLocation *
> *contains a uniformResourceIdentifier (URI) which indicates the *
> *location of the OCSP server for that certificate. *
> *Certificates that contain the same URI MAY be grouped in a single *
> *request.*
>
> **
>
> *Note:For each candidate certificate, when performing the path *
> *validation algorithm, the OCSP client SHOULD verify that the *
> *current time is within the validity period of the target *
> *certificate.Certificates which are outside their validity *
> *period SHOULD NOT be included in the request.*
>
> **
>
> *The requestor MAY choose to sign the OCSP request. In that case, the*
> *signature is computed over the tbsRequest structure. If the request*
> *is signed, the requestor SHALL specify its name in the requestorName*
> *field. Also, for signed requests, the requestor MAY include*
> *certificates that help the OCSP responder verify the requestor's*
> *signature in the certs field of Signature.*
>
> Stefan answered “ Not broken.
>
> Your text may provide guidance that could be useful to some
> implementers, but is completely beyond this document and further, not
> generally applicable or true.
>
> As an example, an organisation may setup an in house locally configured
> OCSP responder that responds to all certificates "out there" that is
> relevant to that organisation.
>
> Such clients would just blindly send OCSP requests to their local
> responder, disregarding any information in the cert.
>
> It's totally beyond this spec to have an opinion about this”.
>
> The argumentation above is incorrect. The proposed text states:
>
> *OCSP clients SHALL verify *
>
> *whether there exists a locally defined rule for the certificate in *
>
> *question which indicates the URI where the OCSP*
>
> This means that OCSP clients would just blindly send OCSP requests to
> their local responder.
>
> *Comment 27*

After re-reading this text and RFC 4753, it's true for this protocol 
like others that it's difficult to tell the difference from a flash 
crowd vs DoS attack.  In the proposed text, even splitting the load 
amongst different OCSP servers still can't protect you against flash 
crowds.  And, the number of queries received isn't necessarily tied to 
how many servers you have.  I think the first paragraph is addressed 
adequately already in RFC 4732, which is included by reference.  There's 
volumes of text in RFC 4732 about DoS based on floods, but on 
cryptography there' also:

  In fact, poorly
  designed authentication mechanisms using cryptographic methods can
  exacerbate the problem.

If we look at the 2nd paragraph, the first sentence doesn't address the 
flash crowd issue.  If you split a server that would normally of had 10 
certificates on it two to 5 and 5 and one person is doing all the 
signing splitting didn't help one bit.  I think this one gets down to 
provisioning and is covered by RFC 4732:

  Thus, the first line
  of defense against DoS attacks must be to provision your service so
  that it can handle a foreseeable legitimate peak load.

The second sentence and following paragraph don't necessarily follow. 
Splitting won't necessarily have an impact on the number of queries 
received.

It seems that we're covered by reference on this one so I consider this 
one addressed.  If anybody else disagrees, I'm sure I'll hear about it.

> On page 24, text should be added to the Security consideration section:
>
> *
> Denial of service attack using a flood of queries*
> **
>
> *A denial of service vulnerability is evident with respect to a flood *
> *of queries.The production of a cryptographic signature *
> *significantly affects response generation cycle time, thereby *
> *exacerbating the situation. *
>
> **
> *The flood of queries may either come from a flood attack or from the *
> *fact that there are too many certificates supported by the same OCSP *
> *responder.In the later case, the number of queries can be *
> *reduced by using a technique similar to the splitting of CRLs: *
> **
>
> *When a block of certificates have been issued with the same *
> *accessLocation in the AIA extension field of these certificates, *
> *then the accessLocation should be changed.In this way, a given *
> *OCSP server will only be responsible for a block of certificates.*
>
> Stefan answered “If the security considerations section is talking about
> splitting OCSP responders
> in this way, then the document itself need to introduce the subject.
>
> I would suggest that it is beyond this update to do so.
>
> It is a good guidance to limit denial of service conditions.
> I believe that the IESG enjoys information in the security
> considerations section.
>
> :-)
>
> Denis

Thanks for continuing to slug away at it.

spt

From turners@ieca.com  Mon Apr  8 07:34:25 2013
Return-Path: <turners@ieca.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B9B21F935B for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.215
X-Spam-Level: 
X-Spam-Status: No, score=-102.215 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dgYnOBZOOvUa for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:34:24 -0700 (PDT)
Received: from gateway07.websitewelcome.com (gateway07.websitewelcome.com [69.56.159.26]) by ietfa.amsl.com (Postfix) with ESMTP id 6432D21F9771 for <ietf@ietf.org>; Mon,  8 Apr 2013 07:34:23 -0700 (PDT)
Received: by gateway07.websitewelcome.com (Postfix, from userid 5007) id 5711DE9A1AB43; Mon,  8 Apr 2013 09:34:15 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway07.websitewelcome.com (Postfix) with ESMTP id 25CACE9A1A9FC for <ietf@ietf.org>; Mon,  8 Apr 2013 09:34:15 -0500 (CDT)
Received: from [108.45.16.214] (port=52313 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1UPD9H-0001nt-Ls; Mon, 08 Apr 2013 09:34:19 -0500
Message-ID: <5162D56B.9060404@ieca.com>
Date: Mon, 08 Apr 2013 10:34:19 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
References: <20130323065208.090391A65A@ld9781.wdf.sap.corp>
In-Reply-To: <20130323065208.090391A65A@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator1743.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: (thunderfish.local) [108.45.16.214]:52313
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 9
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
Cc: pkix@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, 08 Apr 2013 14:34:25 -0000

Martin,

I went all the way to Sam's original message about his discuss on the 
draft that became RFC 5019:

https://www.ietf.org/mail-archive/web/pkix/current/msg03627.html

and reviewed the 60 or so messages in the thread.

Aside: I think when you're referring to "updating" RFC 5019 you're 
referring to the updates header.  I'd not put a lot of weight in the 
presence or absence of the updates header.  The IESG has waffled 
including it, authors forgetting about including it, etc.  What's clear 
in the thread was that there was a WGLC issued with the understanding 
that pre-RFC 5109 was going update the semantics of the error code in 
RFC 2560.  I can't find any objections and the WG consensus was to 
proceed.  Should the header have been added - maybe, but I don't 
actually find any messages asking for it to be added and push back on 
it.  What the text in 5019 says is that "this profile extends the RFC 
2560 [OCSP] definition of "unauthorized" as follows:"

Your issue, at least to me, seems to be that you'd prefer that new error 
codes be defined instead of double-upping on unauthorized error.  I've 
been letting this exchange go to see if anybody else rallies to your 
flag (i.e., joins your cause, gets on your bandwagon, etc).  I've not 
seen that and I think you're in the rough here.

But, as one of my fellow ADs constantly reminds everyone, one person can 
blow up consensus if they're right.  So...

I think all of this is based on your message to PKIX in late January:

"
The "unauthorized" response of rfc2560 means

"this is not a public service, and your OCSP request is outside of
  our terms-of-service.  Go away."
"

I think you're reading a whole lot in to definition from RFC 2560:

  The response "unauthorized" is returned in cases where the client is
  not authorized to make this query to this server.

I find it really hard to make the leap to if client sends a request to a 
non-public server and continues to request status information that it 
means they've violated the terms of use of the private server and by 
doing so the client has committed a crime.

If we're about interoperability, then I'm waiting for those that think 
this change breaks things.  To date I've not see folks say that it does.

Yes, this is all an odd way to use an error code for application
specific reasons. However, there really is no point is us moving away
from that (again, admittedly odd) behavior if there's no sign that any
client will be updated for this. The lack of implementers backing
your point seems to put you even deeper in the rough.

Unless I've misconstrued something, that's the rough consensus.

spt

On 3/23/13 2:52 AM, Martin Rex wrote:
> The IESG wrote:
>>
>> The IESG has received a request from the Public-Key Infrastructure
>> (X.509) WG (pkix) to consider the following document:
>> - 'X.509 Internet Public Key Infrastructure Online Certificate Status
>>     Protocol - OCSP'
>>    <draft-ietf-pkix-rfc2560bis-15.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 2013-03-27.
>
> I'm having an issue with a subtle, backwards-incompatible change
> of the semantics of the exception case with the error code
> "unauthorized", which tries to rewrite history 13 years into the
> without actually fitting the OCSP spec.
>
> It's about the second change from the introduction:
>
>       o  Section 2.3 extends the use of the "unauthorized" error
>           response, as specified in [RFC5019].
>
> While it is true that the error code abuse originally first appeared
> in rfc5019, the change was never declared as an update to rfc2560,
> nor filed as an errata to rfc2560.
>
> The original Exception cases in rfc2560 define the following semantics:
>
>    http://tools.ietf.org/html/rfc2560#section-2.3
>
>     2.3 Exception Cases
>
>     In case of errors, the OCSP Responder may return an error message.
>     These messages are not signed. Errors can be of the following types:
>
>     -- malformedRequest
>     -- internalError
>     -- tryLater
>     -- sigRequired
>     -- unauthorized
>
>   [...]
>
>     The response "sigRequired" is returned in cases where the server
>     requires the client sign the request in order to construct a
>     response.
>
>     The response "unauthorized" is returned in cases where the client is
>     not authorized to make this query to this server.
>
>
> The proposed "extended" semantics from the rfc2560bis draft:
>
>    http://tools.ietf.org/html/draft-ietf-pkix-rfc2560bis-15#page-9
>
>     The response "unauthorized" is returned in cases where the client is
>     not authorized to make this query to this server or the server is not
>     capable of responding authoritatively (cf. [RFC5019], Section 2.2.3).
>
> The rfc5019 semantics "The server can not provide an authoritative response
> to this specific request" is incompatible with the semantics "you are not
> authorized to sumbit OCSP requests to this service".
>
> There is another serious conflict with the rfc5019 repurposed error code
> semantics and rfc2560.  While rfc5019 is limited to a single status request,
> rfc2560 and rfc2560bis both allow a list of several Requests to
> be sent in a single OCSPRequest PDU.  An OCSP response, however, is
> not allowed to contain responseBytes when an error code is returned
> inthe response status:
>
>    http://tools.ietf.org/html/draft-ietf-pkix-rfc2560bis-15#section-4.2.1
>
>     4.2.1 ASN.1 Specification of the OCSP Response
>
>     An OCSP response at a minimum consists of a responseStatus field
>     indicating the processing status of the prior request. If the value
>     of responseStatus is one of the error conditions, responseBytes are
>     not set.
>
>     OCSPResponse ::= SEQUENCE {
>        responseStatus         OCSPResponseStatus,
>        responseBytes          [0] EXPLICIT ResponseBytes OPTIONAL }
>
>
> So it is impossible to convey "OCSP responder is not capable of
> responding authoritatively" for a subset of Requests in the requestList
> and regular status for the remaining Requests in the List by using
> a repurposed "unauthorized" error code.
>
> The current draft neither mention this contradiction, nor does it
> provide any guidance how an implementation should behave in this
> situation.
>
>
> I would appreciate if this problem of draft-*-rfc2560bis could be fixed
> prior to making it a successor for rfc2560.
>
>
> -Martin
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix
>

From dhc@dcrocker.net  Mon Apr  8 07:35:40 2013
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 2B61F21F97F3 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:35:40 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sGtJ+wF4btP0 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 07:35:39 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6943721F97F4 for <ietf@ietf.org>; Mon,  8 Apr 2013 07:35:39 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r38EZcR4005698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 8 Apr 2013 07:35:39 -0700
Message-ID: <5162D5B9.3010000@dcrocker.net>
Date: Mon, 08 Apr 2013 07:35:37 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: team to look at diversity
References: <E41A7C0D-470D-4480-824F-2AA8CFAB3677@piuha.net> <C001659D-B342-4D84-9361-D617AF33BE4B@tzi.org> <5162D4A0.3090101@dcrocker.net>
In-Reply-To: <5162D4A0.3090101@dcrocker.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.0 (sbh17.songbird.com [72.52.113.17]); Mon, 08 Apr 2013 07:35:39 -0700 (PDT)
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, 08 Apr 2013 14:35:40 -0000

Talk about timing!

This was in the very next message I looked at:

    How Internet Fighting Works

    http://www.smbc-comics.com/index.php?db=comics&id=2939#comic


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From Ted.Lemon@nominum.com  Mon Apr  8 08:38:44 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1DDF21F8B25 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 08:38:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QaXFGYTXsOS2 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 08:38:44 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 4029921F8AE3 for <ietf@ietf.org>; Mon,  8 Apr 2013 08:38:44 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUWLkgxRXXq1J9bhrzPmgoActS4OkWfHQ@postini.com; Mon, 08 Apr 2013 08:38:44 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B311E108393 for <ietf@ietf.org>; Mon,  8 Apr 2013 08:38:43 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 94398190061; Mon,  8 Apr 2013 08:38:43 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 8 Apr 2013 08:38:43 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Thread-Topic: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Thread-Index: AQHONF5T+AxkI98yjUytpmx8/mQFEJjMzLyAgAACAQCAABwqAA==
Date: Mon, 8 Apr 2013 15:38:43 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751387C6@mbx-01.win.nominum.com>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org> <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775138028@mbx-01.win.nominum.com> <CAKRbAfA4S3iuYmER=Fm9b10yJ_yQ8hi+zY0uZifdXuSMt7C3FQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751383B4@mbx-01.win.nominum.com> <CAKRbAfAxddKNKGPrvOTgMRD0AiJjEdZd9aKPMH_0gzTQn0DMgQ@mail.gmail.com>
In-Reply-To: <CAKRbAfAxddKNKGPrvOTgMRD0AiJjEdZd9aKPMH_0gzTQn0DMgQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751387C6mbx01winnominum_"
MIME-Version: 1.0
Cc: =?Windows-1252?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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, 08 Apr 2013 15:38:44 -0000

--_000_8D23D4052ABE7A4490E77B1A012B6307751387C6mbx01winnominum_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Apr 8, 2013, at 9:57 AM, Melinda Shore <melinda.shore@gmail.com<mailto:m=
elinda.shore@gmail.com>> wrote:
Your beef isn't with me, it's with M=E5ns.

I've got no beef with either of you=97I'm a vegetarian!   :)

(I actually found what M=E5ns had to say valuable, which illustrates one of=
 the great problems of communication: everybody reads what you say differen=
tly!)


--_000_8D23D4052ABE7A4490E77B1A012B6307751387C6mbx01winnominum_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <388269CD5DCC4A42B8BB8A1EC68D4337@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Apr 8, 2013, at 9:57 AM, Melinda Shore &lt;<a href=3D"mailto:melind=
a.shore@gmail.com">melinda.shore@gmail.com</a>&gt; wrote:</div>
<blockquote type=3D"cite"><span style=3D"font-family: Optima; font-size: me=
dium; 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; w=
ord-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width=
: 0px; display: inline !important; float: none; ">Your
 beef isn't with me, it's with M=E5ns.</span></blockquote>
</div>
<br>
<div>I've got no beef with either of you=97I'm a vegetarian! &nbsp; :)</div=
>
<div><br>
</div>
<div>(I actually found what&nbsp;M=E5ns had to say valuable, which illustra=
tes one of the great problems of communication: everybody reads what you sa=
y differently!)</div>
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751387C6mbx01winnominum_--

From farmer@umn.edu  Mon Apr  8 09:06:31 2013
Return-Path: <farmer@umn.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 A999F21F940D for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 09:06:31 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zog8HZeCj0LN for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 09:06:30 -0700 (PDT)
Received: from vs-m.tc.umn.edu (vs-m.tc.umn.edu [134.84.135.97]) by ietfa.amsl.com (Postfix) with ESMTP id 69CD721F93EE for <ietf@ietf.org>; Mon,  8 Apr 2013 09:06:30 -0700 (PDT)
Received: from mail-oa0-f72.google.com (mail-oa0-f72.google.com [209.85.219.72]) by vs-m.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Mon, 8 Apr 2013 11:06:19 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-oa0-f72.google.com [209.85.219.72] #+LO+TR
X-Umn-Classification: local
Received: by mail-oa0-f72.google.com with SMTP id j6so36299026oag.11 for <ietf@ietf.org>; Mon, 08 Apr 2013 09:06:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding:x-gm-message-state; bh=WZVnX3NsKypIrkWVQ8bp86fcLvJprcvA+ainTCMPprk=; b=hKy17LRUPcDf44HFBjQoNGf1zE+oy//RcS/JyZfy9nHtDSpv50TsGn/iE/YFXaxW5X 0mGx4IzBJYs1pv+NGm69BMOPfBByawxakHwNcJF6QPxMWJLas0STJqE6aqy4ZEyEFJNo kuGwulRA4agzv+o7/okDn76VT4HWWYmi62x28U+IlnCMvvy11OA3lqF+6P/9xCjIrHzy 8fgBrTrAPIH0WrdpkiI/7c++sJ1XMo2O6fI8giToKAorPXHH4b8UVJ5TD7jEi3YWb9Po FcR4zLc6qsf9iqqbZFnQS2WXHXApWi6biI36ahEa6poYt103mX6Qxy6CGJfq1TJnbaRA 9PHA==
X-Received: by 10.50.51.131 with SMTP id k3mr7383296igo.54.1365437179184; Mon, 08 Apr 2013 09:06:19 -0700 (PDT)
X-Received: by 10.50.51.131 with SMTP id k3mr7383243igo.54.1365437178245; Mon, 08 Apr 2013 09:06:18 -0700 (PDT)
Received: from x-128-101-234-172.uofm-secure.wireless.umn.edu (x-128-101-234-172.uofm-secure.wireless.umn.edu. [128.101.234.172]) by mx.google.com with ESMTPS id hi4sm19958564igc.6.2013.04.08.09.06.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Apr 2013 09:06:17 -0700 (PDT)
Message-ID: <5162EAFD.8060102@umn.edu>
Date: Mon, 08 Apr 2013 11:06:21 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-rfc2050bis-01
References: <11301BFD-E4AD-4779-802E-6BAADD0381D4@vigilsec.com>
In-Reply-To: <11301BFD-E4AD-4779-802E-6BAADD0381D4@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQlMB9uToen16oYSZuIR+RMCCZJrtP8B+vDPPn4sZPLcCtMmTmR7Elp801sPTYDGNh+I+2uC4rXRZjQOCTvmVHgWX7ohK4+qmHXxy1ew7LqiG4zDTTacXWIa+VAAraX8aIkWRD0O
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Apr 2013 16:06:31 -0000

On 4/7/13 20:34 , Russ Housley wrote:
> Many of the comments that were posted to this list have been incorporated.
>
> Please comment on the updated document.

1.  Section 6 and the last paragraph of section 1 are mostly 
duplicative, I'd suggest eliminating section 6 and merging it into the 
last paragraph of section 1.  In particular the part "and omits policy 
and operational procedures that have been superseded by ICANN and RIR 
policy since RFC 2050 publication."  That is the only thing in section 6 
that isn't already in the last paragraph of section 1.  Unless you have 
plans to dramatically increase whats in section 6.

2.  Also, the references for RFC 1366 and RFC 1466 are missing.

3.  Regarding Public WHOIS in section 4;  The constituencies and 
stakeholders for Public WHOIS are much broader than just the technical 
community, a number of constituencies in civil society have legitimate 
interests in Public WHOIS.  I guess the main point I'm trying to make is 
that Public WHOIS is more than just a technical issue, and section 4 
seems to scope it as solely a technical issue.

I don't think you need to refocus section 4 from "Technical 
Considerations" I think simply recognizing that there are more than just 
technical considerations, especially for Public WHOIS, something like 
the following should be sufficient;

    2) ...have included consideration of the technical and operational
       requirements, as well as requirements of other stakeholders, for
       supporting WHOIS services...

Other stakeholders are recognized in general in section 5, but this is a 
little different, this is recognizing while Public WHOIS is a technical 
issue, it is more than just a technical issue.  Whereas Reverse DNS is 
almost entirely a technical issue.

Thanks.

-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================

From pthaler@broadcom.com  Mon Apr  8 09:25:11 2013
Return-Path: <pthaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3704121F9487 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 09:25:11 -0700 (PDT)
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=-0.025, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUc9e1vFwk2F for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 09:25:10 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9745021F9434 for <ietf@ietf.org>; Mon,  8 Apr 2013 09:25:10 -0700 (PDT)
Received: from [10.9.208.53] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Mon, 08 Apr 2013 09:22:11 -0700
X-Server-Uuid: 06151B78-6688-425E-9DE2-57CB27892261
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Mon, 8 Apr 2013 09:25:01 -0700
Received: from SJEXCHMB09.corp.ad.broadcom.com ( [fe80::3da7:665e:cc78:181f]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Mon, 8 Apr 2013 09:25:00 -0700
From: "Pat Thaler" <pthaler@broadcom.com>
To: "Melinda Shore" <melinda.shore@gmail.com>, =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Subject: RE: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Thread-Topic: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Thread-Index: AQHOM9LrsL4yaY1ppUG5GVBAJjfTAZjMYRKAgAATSQCAAAqSwA==
Date: Mon, 8 Apr 2013 16:25:00 +0000
Message-ID: <EB9B93801780FD4CA165E0FBCB3C3E672AD17CF1@SJEXCHMB09.corp.ad.broadcom.com>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org> <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com>
In-Reply-To: <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7D7C31392ZC5072256-01-01
Content-Type: multipart/alternative; boundary=_000_EB9B93801780FD4CA165E0FBCB3C3E672AD17CF1SJEXCHMB09corpa_
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, 08 Apr 2013 16:25:11 -0000

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

RFC 1149 was the first humorous RFC I read and probably the first RFC I rea=
d. It was definitely accessible for me as a Layer 1 and 2 IETF outsider. Hu=
morous RFCs can be a nice introduction to the structure of RFCs.

Pat

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mel=
inda Shore
Sent: Monday, April 08, 2013 1:31 AM
To: M=E5ns Nilsson
Cc: ietf@ietf.org
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - I=
ETF April 1 jokes.


Doesn't it strike you as odd that this discussion has moved towards some so=
rt of tacit/accepted acknowledgment of the role of joke RFCs as insider/out=
sider cultural markers rather than just clever bits of writing that are wid=
ely enjoyed?  I'm a little surprised to find myself developing sympathy for=
 tiresome humorless whiny people.  (Wait, no I'm not).

Anyway this strikes me as an unfortunate use of those documents.

Melinda

--_000_EB9B93801780FD4CA165E0FBCB3C3E672AD17CF1SJEXCHMB09corpa_
Content-Type: text/html;
 charset=iso-8859-1
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=3Diso-8859-=
1">
<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;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@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:#10253F;mso-style-textfill-fill-co=
lor:#10253F;mso-style-textfill-fill-alpha:100.0%">RFC 1149 was the first hu=
morous RFC I read and probably the first RFC I read. It
 was definitely accessible for me as a Layer 1 and 2 IETF outsider. Humorou=
s RFCs can be a nice introduction to the structure of RFCs.<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#10253F;mso-style-textfill-fill-co=
lor:#10253F;mso-style-textfill-fill-alpha:100.0%"><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:#10253F;mso-style-textfill-fill-co=
lor:#10253F;mso-style-textfill-fill-alpha:100.0%">Pat<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"><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>Melinda Shore<br>
<b>Sent:</b> Monday, April 08, 2013 1:31 AM<br>
<b>To:</b> M=E5ns Nilsson<br>
<b>Cc:</b> ietf@ietf.org<br>
<b>Subject:</b> Re: Proposed solution for DPEP (Diversity Problem Entry Poi=
nt) - IETF April 1 jokes.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p>Doesn't it strike you as odd that this discussion has moved towards some=
 sort of tacit/accepted acknowledgment of the role of joke RFCs as insider/=
outsider cultural markers rather than just clever bits of writing that are =
widely enjoyed?&nbsp; I'm a little surprised
 to find myself developing sympathy for tiresome humorless whiny people.&nb=
sp; (Wait, no I'm not).<o:p></o:p></p>
<p>Anyway this strikes me as an unfortunate use of those documents.&nbsp; <=
o:p></o:p></p>
<p>Melinda <o:p></o:p></p>
</div>
</body>
</html>

--_000_EB9B93801780FD4CA165E0FBCB3C3E672AD17CF1SJEXCHMB09corpa_--


From moore@network-heretics.com  Mon Apr  8 09:29:42 2013
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 7D93821F8DBF for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 09:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.669
X-Spam-Level: 
X-Spam-Status: No, score=-2.669 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQDcPPYXDxCA for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 09:29:41 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 5B0D021F943A for <ietf@ietf.org>; Mon,  8 Apr 2013 09:29:41 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 9BCA42100E for <ietf@ietf.org>; Mon,  8 Apr 2013 12:29:40 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 08 Apr 2013 12:29:40 -0400
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=aYvFJkrplKW6MUQbNPvonj RGZLc=; b=KtNeGlu/Bz/d+FgWFanNHcCcQecomwfatufRPQppq6jTutVHvb//1A LxG+/9jmo0ziOuBFPNTcHQzprvoUJLMvb18Z2i+o5xo8UUw94cbALUqfLWq4jcZf NE5fXWLu55arWRmr7+k/TcO4B//qLGKqTn2zmf8LG0A3T0ZyO1bXI=
X-Sasl-enc: 5ee+VUWw4b2qyfQI0AIGz6+S61vPr5dPfBGJsqEEd2Ph 1365438580
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 189212000AE; Mon,  8 Apr 2013 12:29:40 -0400 (EDT)
Message-ID: <5162F067.7070407@network-heretics.com>
Date: Mon, 08 Apr 2013 12:29:27 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: On the tradition of I-D "Acknowledgements" sections
References: <20130320104353.27601.24590.idtracker@ietfa.amsl.com> <76F7932F-CABE-4825-80DB-461E95288402@jiaziyi.com> <CADnDZ89mBrJAHQOHegSXFacC_DHSn5R34BpMtbkQ1qjOF+vZYA@mail.gmail.com> <1227E12F-9593-4A8C-A54D-B210A61060D2@jiaziyi.com> <CADnDZ8-NN0pWh5WuoJg3Jmgw_MtLpw51mrhiW2=P8i8hXJoL0g@mail.gmail.com> <5E51EF77-3D8E-4D22-A753-329CEB53CD59@istaff.org> <6.2.5.6.2.20130324123511.0abd0878@resistor.net> <CADnDZ893B70g3i0rTTiy6JMH26SVkwyZwGS9vhY8DqEn0CU8NA@mail.gmail.com> <CADnDZ88Gs1VvvpEsEoPyMLyHV1JeTWVXtsfs4NgYrncCdvjZ7Q@mail.gmail.com> <514FB516.6050702@joelhalpern.com> <CADnDZ8_9ZHtNG7rVhMSCr8R9L6+MicM+LPQdaRP=_x==wAZWKA@mail.gmail.com> <514FE936.9040406@gmail.com>
In-Reply-To: <514FE936.9040406@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: Mon, 08 Apr 2013 16:29:42 -0000

On 03/25/2013 02:05 AM, Melinda Shore wrote:
> My experience over lo, these many years is that the best way to ensure 
> that you're recognized is to produce text/suggestions/ideas that other 
> people find valuable.
+1



From llynch@civil-tongue.net  Mon Apr  8 10:35:27 2013
Return-Path: <llynch@civil-tongue.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 7DFB421F975B for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 10:35:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6wz1GcUf3Gvi for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 10:35:27 -0700 (PDT)
Received: from hiroshima.bogus.com (hiroshima.bogus.com [IPv6:2001:418:1::80]) by ietfa.amsl.com (Postfix) with ESMTP id 23E6421F9758 for <ietf@ietf.org>; Mon,  8 Apr 2013 10:35:19 -0700 (PDT)
Received: from hiroshima.bogus.com (localhost [127.0.0.1]) by hiroshima.bogus.com (8.14.3/8.14.3) with ESMTP id r38HZFhs031424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 8 Apr 2013 10:35:15 -0700 (PDT) (envelope-from llynch@civil-tongue.net)
Received: from localhost (llynch@localhost) by hiroshima.bogus.com (8.14.3/8.14.3/Submit) with ESMTP id r38HZFIm031421; Mon, 8 Apr 2013 10:35:15 -0700 (PDT) (envelope-from llynch@civil-tongue.net)
Date: Mon, 8 Apr 2013 10:35:15 -0700 (PDT)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hiroshima.bogus.com
To: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
In-Reply-To: <9515564336C5B442A00021645539CFCC28A1403D@xmb-rcd-x08.cisco.com>
Message-ID: <alpine.BSF.2.00.1304081033200.14142@hiroshima.bogus.com>
References: <9515564336C5B442A00021645539CFCC28A1403D@xmb-rcd-x08.cisco.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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, 08 Apr 2013 17:35:27 -0000

On Mon, 8 Apr 2013, Wes Beebee (wbeebee) wrote:

>
>> If the date is special then thoes RFCs SHOULD be *historical*.
>
> I thought they should be classified as "hysterical".

there is an echo (echo) ((echo) ) in here (here) ((here))

> - Wes
>

From jcurran@istaff.org  Mon Apr  8 11:45:38 2013
Return-Path: <jcurran@istaff.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 C67E021F934D for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 11:45:38 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4lhB0-8GjbBj for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 11:45:38 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id 47ADE21F9322 for <ietf@ietf.org>; Mon,  8 Apr 2013 11:45:38 -0700 (PDT)
Received: from [12.52.207.243] (helo=[172.16.7.116]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1UPH4R-000HVL-PW; Mon, 08 Apr 2013 18:45:36 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 12.52.207.243
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+7Z+9B5oCmG8fjKl+7t3lR
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: draft-housley-rfc2050bis-01
From: John Curran <jcurran@istaff.org>
In-Reply-To: <5162EAFD.8060102@umn.edu>
Date: Mon, 8 Apr 2013 11:45:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EEBF37E5-E727-42F2-A237-53CF2971111B@istaff.org>
References: <11301BFD-E4AD-4779-802E-6BAADD0381D4@vigilsec.com> <5162EAFD.8060102@umn.edu>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.1503)
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, 08 Apr 2013 18:45:38 -0000

On Apr 8, 2013, at 9:06 AM, David Farmer <farmer@umn.edu> wrote:

> 3.  Regarding Public WHOIS in section 4;  The constituencies and =
stakeholders for Public WHOIS are much broader than just the technical =
community, a number of constituencies in civil society have legitimate =
interests in Public WHOIS.  I guess the main point I'm trying to make is =
that Public WHOIS is more than just a technical issue, and section 4 =
seems to scope it as solely a technical issue.

It's definitely a bigger issue, but it does not seem appropriate in=20
an IETF document to assert points about all aspects of the issue, but=20
instead better to just note the _technical considerations_ of the topic=20=

that are needed to keep the Internet running.

> I don't think you need to refocus section 4 from "Technical =
Considerations" I think simply recognizing that there are more than just =
technical considerations, especially for Public WHOIS, something like =
the following should be sufficient;
>=20
>   2) ...have included consideration of the technical and operational
>      requirements, as well as requirements of other stakeholders, for
>      supporting WHOIS services...

This text would be the authors asserting that these requirements (those =
of=20
other stakeholders of Whois) have been considered, and yet there are =
wide
range of non-technical aspects to Whois that quite probably have not =
been
fully considered; e.g. issues similar to those in various ongoing =
discussions=20
of DNS Whois at ICANN this week...

The section is about the _technical considerations_ that have been =
considered=20
in establishment of the Internet Numbers Registry System, and to change =
the=20
text as you suggest would significantly expand its scope into areas not =
currently=20
addressed in the text and not typical of other IETF documents, i.e. =
problematic.

FYI,
/John



From mansaxel@besserwisser.org  Mon Apr  8 12:19:57 2013
Return-Path: <mansaxel@besserwisser.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 2271021F9799 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 12:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.075
X-Spam-Level: 
X-Spam-Status: No, score=-2.075 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2TmxpFO4K7cg for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 12:19:56 -0700 (PDT)
Received: from jaja.besserwisser.org (primary.se [IPv6:2a01:298:4::53]) by ietfa.amsl.com (Postfix) with ESMTP id 8CBFD21F9577 for <ietf@ietf.org>; Mon,  8 Apr 2013 12:19:55 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id ED2A89E5B; Mon,  8 Apr 2013 21:19:53 +0200 (CEST)
Date: Mon, 8 Apr 2013 21:19:53 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Message-ID: <20130408191953.GE1162@besserwisser.org>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org> <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775138028@mbx-01.win.nominum.com> <CAKRbAfA4S3iuYmER=Fm9b10yJ_yQ8hi+zY0uZifdXuSMt7C3FQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751383B4@mbx-01.win.nominum.com> <CAKRbAfAxddKNKGPrvOTgMRD0AiJjEdZd9aKPMH_0gzTQn0DMgQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="10jrOL3x2xqLmOsH"
Content-Disposition: inline
In-Reply-To: <CAKRbAfAxddKNKGPrvOTgMRD0AiJjEdZd9aKPMH_0gzTQn0DMgQ@mail.gmail.com>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
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, 08 Apr 2013 19:19:57 -0000

--10jrOL3x2xqLmOsH
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - I=
ETF April 1 jokes. Date: Mon, Apr 08, 2013 at 05:57:54AM -0800 Quoting Meli=
nda Shore (melinda.shore@gmail.com):
> I am absolutely not suggesting changing anything other than the
> unfortunate  attitude that the right response to someone missing the joke
> is to read them out of the meeting/declare them anathema or unworthy or n=
ot
> members of this community.  Your beef isn't with me, it's with M=C3=A5ns.

To clarify:=20

I was thinking of vendors, not people .  The vendor that does not invest
in its staff enough to expose them to the IETF culture may not supply
my network with code and boxes.

People who initially fail to appreciate the jokes for what they are
should be enlightened in the most gentle way possible.

At no time have I proposed or held the belief that public humiliation
is in any way acceptable.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
We have DIFFERENT amounts of HAIR --

--10jrOL3x2xqLmOsH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlFjGFkACgkQ02/pMZDM1cU4cACfXaJ7xIDMbWQ+9IXMWcQHeOQO
IKAAnigHDggvVtBmhIJ2Euy3Da8gj2mG
=UeBq
-----END PGP SIGNATURE-----

--10jrOL3x2xqLmOsH--

From rlb@ipv.sx  Mon Apr  8 12:34:13 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54BF621F8D14 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 12:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.254
X-Spam-Level: 
X-Spam-Status: No, score=-2.254 tagged_above=-999 required=5 tests=[AWL=0.722,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HYcNDmOCoayy for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 12:34:12 -0700 (PDT)
Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) by ietfa.amsl.com (Postfix) with ESMTP id 1CAC721F891D for <ietf@ietf.org>; Mon,  8 Apr 2013 12:34:12 -0700 (PDT)
Received: by mail-oa0-f50.google.com with SMTP id n1so6674675oag.9 for <ietf@ietf.org>; Mon, 08 Apr 2013 12:34:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=V3lC1g8A4fJ+BwKMULhH1ucolMARKTbbrTU8Gbt609I=; b=gdCXWH96bxV3BEDJI+l/gPHTK/qbJBFC7zW1L51nqy37PB8kSXnCr3k9kFwKa/WAEH kqFJZSZXJ4IDZSYwvGOGWoMq6qzJ23Un5ORIrLCA10nMr1V5+QD/aKpUpSPdEofuD95Y xGsa8d6Xs2cz+s7jx2MyDAQO8A7fdyIxB6N6EK2yozF992w0ZoxyaKGQn4An1RWHtcAu iRzSeW44/CdO5kuKRsjD707Uh45mhMpUzvOY/omez3C+9rp6R8qOpTOwsdaHx0A2nAbc Yxcc0Madg9UXu/ny30l84pm3Z3A2yELUBTwV4YcD+EULI5LC+uQSroVDxH9TRUlbfp/h dGxQ==
MIME-Version: 1.0
X-Received: by 10.182.43.103 with SMTP id v7mr16300451obl.17.1365449651473; Mon, 08 Apr 2013 12:34:11 -0700 (PDT)
Received: by 10.60.25.196 with HTTP; Mon, 8 Apr 2013 12:34:11 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <5162A1C0.9020409@cisco.com>
References: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com> <515AD8B1.20503@cisco.com> <CAL02cgTExcoC+fMYVs0KT==yx1vZgaK5Tc8Dij3vhiR9Os3YkQ@mail.gmail.com> <5162A1C0.9020409@cisco.com>
Date: Mon, 8 Apr 2013 15:34:11 -0400
Message-ID: <CAL02cgRhzi7hE3LQt26cUjqo30CJurF5Sxpph=fdgfgpAX=0GQ@mail.gmail.com>
Subject: Re: Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-05
From: Richard Barnes <rlb@ipv.sx>
To: stbryant@cisco.com
Content-Type: multipart/alternative; boundary=f46d044794f36f602c04d9de853d
X-Gm-Message-State: ALoCoQkWVM8zg1dRaACwfVDsZc7gwjZ1sD1U+ja83BzXjbqg6re3aHDli+NDf4XyHc88efxISW5l
Cc: The IESG <iesg@ietf.org>, Richard Barnes <rbarnes@bbn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Apr 2013 19:34:13 -0000

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

Hi Stewart,

I think this resolves my issues.

Thanks,
--Richard


On Mon, Apr 8, 2013 at 6:53 AM, Stewart Bryant <stbryant@cisco.com> wrote:

> On 02/04/2013 15:28, Richard Barnes wrote:
>
>> Thanks for following up, and for the re-send.  Just to be clear, I do not
>> mean these as blocking points.
>>
>> On the former point, I might just suggest a minor edit to the
>> introduction:
>> OLD: "This document specifies the options for determination and selection
>> of next-hop Ethernet MAC addressing under these circumstances."
>> NEW: "This document specifies the options for determination and selection
>> of next-hop Ethernet MAC addressing when MPLS-TP is used in a "pure
>> Ethernet" manner, without any IP forwarding capability."
>>
>
> After various rounds of tweeking:
>
> "This document specifies the options for the determination and selection
> of the next-hop Ethernet MAC address when MPLS-TP is used between nodes
> that do not have an IP dataplane."
>
> The subtly is the network may be mixed IP capable and non-IP capable.
>
>
>
>
>> On the latter point, I can understand the desire to make the simple case
>> simple, and the text at the end of Section 2 sends a clear warning. It does
>> seems like GAP would also allow autoconfiguration without further NMS
>> interaction.  (Unless the NMS is configuring per-Ethernet-address policies,
>> e.g., "forward packets with this label to 00:11:22:33:44:55". Is that the
>> case?)
>>
> Yes. One case is a network that is generally NMS configured, and wants to
> use unicast MAC addresses, but wants to allow the craft people to plug in a
> new linecard without talking to the NMS. In such circumstances the only
> auto config would be teh MAC addresses.
>
> Stewart
>
>
>>
>>
>>
>> On Tue, Apr 2, 2013 at 9:10 AM, Stewart Bryant <stbryant@cisco.com<mailto:
>> stbryant@cisco.com>> wrote:
>>
>>     Resending due to Richards change of address.
>>
>>     Stewart
>>
>>
>>     On 11/02/2013 23:45, Richard Barnes wrote:
>>
>>>     I have been selected as the General Area Review Team (Gen-ART)
>>>     reviewer for this draft (for background on Gen-ART,
>>>     pleaseseehttp://www.**alvestrand.no/ietf/gen/art/**gen-art-FAQ.html<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>
>>>     <http://www.alvestrand.no/**ietf/gen/art/gen-art-FAQ.html<http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html>
>>> >**). Please
>>>
>>>     wait for direction from your document shepherd or AD before
>>>     posting a new version of the draft. Document:
>>>     draft-ietf-mpls-tp-ethernet-
>>>     addressing-05
>>>     Reviewer: Richard Barnes
>>>     Review Date: 2013-02-11
>>>     IETF LC End Date: 2013-02-18
>>>     IESG Telechat date: TBD
>>>
>>>     Summary:  Ready, with a couple of minor questions / clarifications.
>>>
>>>     Comment:
>>>
>>>     The document is mostly very clearly written.  (Thanks!)  It would
>>> have helped me understand if it could have been clarified up front that the
>>> mechanism in this document is intended for "pure Ethernet" MPLS-TP (without
>>> assumptions about layer 3+).  The current introduction says as much, but in
>>> a negative way, in terms of ARP or ND not being available.
>>>
>>>     I have some minor unease about the distinction that this document
>>> makes between point-to-point and multipoint links.  The document correctly
>>> notes that a point-to-point link might become multipoint without either end
>>> being aware.  I would have thought this would argue for using GAP in all
>>> cases, but instead the document carries on with addressing the
>>> point-to-point case separately..
>>>
>>>      Richard
>>
>>     It is always difficult when writing a simple draft dealing with a
>>     small
>>     component of a larger technology to know how much tutorial to include,
>>     but I believe the point about operation in the absence IP would be
>>     well known
>>     to anyone implementing this. In particular we assume that anyone
>>     implementing the draft would have read the required references called
>>     up in the first paragraph of the Introduction:
>>
>>
>>     " The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of
>>     protocol
>>     functions that meet the requirements [RFC5654] for the application of
>>     MPLS to the construction and operation of packet-switched transport
>>     networks. The MPLS-TP data plane consists of those MPLS-TP functions
>>     concerned with the encapsulation and forwarding of MPLS-TP packets
>>     and is described in [RFC5960]."
>>
>>     RFC5654 says:
>>
>>     "   36  It MUST be possible to operate and configure the MPLS-TP data
>>             plane without any IP forwarding capability in the MPLS-TP data
>>             plane.  That is, the data plane only operates on the MPLS
>> label."
>>     Thus I think that the text is complete as it stands and requires no
>>     further clarification for anyone that needs to consider the technology
>>     it describes.
>>
>>
>>     With regard to your second point, the issue that we are have, is that
>>     there are a number of deployment scenarios where the operator knows
>>     that the link is Pt-Pt, and there is a reluctance by that community to
>>     use anything other than NMS configuration. That has lead them
>>     to use Ethernet broadcast addressing which allows the crafts to
>>     change h/w without the need for reconfiguration by the NMS.
>>     Against that background moving them onto the use of a Ethernet m/c
>>     address is a step forward. To require using the GAP to that
>>     community would illustrate that the IETF is out of touch with
>>     their needs and methods of network operation.
>>
>>     Hopefully this additional background, which I believe is well
>>     known to the MPLS-TP community to which this draft is directed,
>>     satisfies your concern on the latter point.
>>
>>     - Stewart
>>
>>
>>
>>     --     For corporate legal information go to:
>>
>>     http://www.cisco.com/web/**about/doing_business/legal/**
>> cri/index.html<http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
>>
>>
>>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/**about/doing_business/legal/**cri/index.html<http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
>
>

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

Hi Stewart,<div><br></div><div>I think this resolves my issues.</div><div><=
br></div><div>Thanks,</div><div>--Richard</div><div><br><br><div class=3D"g=
mail_quote">On Mon, Apr 8, 2013 at 6:53 AM, Stewart Bryant <span dir=3D"ltr=
">&lt;<a href=3D"mailto:stbryant@cisco.com" target=3D"_blank">stbryant@cisc=
o.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"><div class=3D"im">On 02/04/2013 15:28, Richa=
rd Barnes wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Thanks for following up, and for the re-send. =A0Just to be clear, I do not=
 mean these as blocking points.<br>
<br>
On the former point, I might just suggest a minor edit to the introduction:=
<br>
OLD: &quot;This document specifies the options for determination and select=
ion of next-hop Ethernet MAC addressing under these circumstances.&quot;<br=
>
NEW: &quot;This document specifies the options for determination and select=
ion of next-hop Ethernet MAC addressing when MPLS-TP is used in a &quot;pur=
e Ethernet&quot; manner, without any IP forwarding capability.&quot;<br>

</blockquote>
<br></div>
After various rounds of tweeking:<br>
<br>
&quot;This document specifies the options for the determination and selecti=
on of the next-hop Ethernet MAC address when MPLS-TP is used between nodes =
that do not have an IP dataplane.&quot;<br>
<br>
The subtly is the network may be mixed IP capable and non-IP capable.<div c=
lass=3D"im"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
On the latter point, I can understand the desire to make the simple case si=
mple, and the text at the end of Section 2 sends a clear warning. It does s=
eems like GAP would also allow autoconfiguration without further NMS intera=
ction. =A0(Unless the NMS is configuring per-Ethernet-address policies, e.g=
., &quot;forward packets with this label to 00:11:22:33:44:55&quot;. Is tha=
t the case?)<br>

</blockquote></div>
Yes. One case is a network that is generally NMS configured, and wants to u=
se unicast MAC addresses, but wants to allow the craft people to plug in a =
new linecard without talking to the NMS. In such circumstances the only aut=
o config would be teh MAC addresses.<br>

<br>
Stewart<br>
<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>
<br>
<br>
On Tue, Apr 2, 2013 at 9:10 AM, Stewart Bryant &lt;<a href=3D"mailto:stbrya=
nt@cisco.com" target=3D"_blank">stbryant@cisco.com</a> &lt;mailto:<a href=
=3D"mailto:stbryant@cisco.com" target=3D"_blank">stbryant@cisco.com</a>&gt;=
&gt; wrote:<br>

<br>
=A0 =A0 Resending due to Richards change of address.<br>
<br>
=A0 =A0 Stewart<br>
<br>
<br>
=A0 =A0 On 11/02/2013 23:45, Richard Barnes wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"im">
=A0 =A0 I have been selected as the General Area Review Team (Gen-ART)<br>
=A0 =A0 reviewer for this draft (for background on Gen-ART,<br>
=A0 =A0 pleaseseehttp://<a href=3D"http://www.alvestrand.no/ietf/gen/art/ge=
n-art-FAQ.html" target=3D"_blank">www.<u></u>alvestrand.no/ietf/gen/art/<u>=
</u>gen-art-FAQ.html</a><br></div>
=A0 =A0 &lt;<a href=3D"http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.ht=
ml" target=3D"_blank">http://www.alvestrand.no/<u></u>ietf/gen/art/gen-art-=
FAQ.html</a>&gt;<u></u>). Please<div><div class=3D"h5"><br>
=A0 =A0 wait for direction from your document shepherd or AD before<br>
=A0 =A0 posting a new version of the draft. Document:<br>
=A0 =A0 draft-ietf-mpls-tp-ethernet-<br>
=A0 =A0 addressing-05<br>
=A0 =A0 Reviewer: Richard Barnes<br>
=A0 =A0 Review Date: 2013-02-11<br>
=A0 =A0 IETF LC End Date: 2013-02-18<br>
=A0 =A0 IESG Telechat date: TBD<br>
<br>
=A0 =A0 Summary: =A0Ready, with a couple of minor questions / clarification=
s.<br>
<br>
=A0 =A0 Comment:<br>
<br>
=A0 =A0 The document is mostly very clearly written. =A0(Thanks!) =A0It wou=
ld have helped me understand if it could have been clarified up front that =
the mechanism in this document is intended for &quot;pure Ethernet&quot; MP=
LS-TP (without assumptions about layer 3+). =A0The current introduction say=
s as much, but in a negative way, in terms of ARP or ND not being available=
.<br>

<br>
=A0 =A0 I have some minor unease about the distinction that this document m=
akes between point-to-point and multipoint links. =A0The document correctly=
 notes that a point-to-point link might become multipoint without either en=
d being aware. =A0I would have thought this would argue for using GAP in al=
l cases, but instead the document carries on with addressing the point-to-p=
oint case separately..<br>

<br>
</div></div></blockquote><div><div class=3D"h5">
=A0 =A0 Richard<br>
<br>
=A0 =A0 It is always difficult when writing a simple draft dealing with a<b=
r>
=A0 =A0 small<br>
=A0 =A0 component of a larger technology to know how much tutorial to inclu=
de,<br>
=A0 =A0 but I believe the point about operation in the absence IP would be<=
br>
=A0 =A0 well known<br>
=A0 =A0 to anyone implementing this. In particular we assume that anyone<br=
>
=A0 =A0 implementing the draft would have read the required references call=
ed<br>
=A0 =A0 up in the first paragraph of the Introduction:<br>
<br>
<br>
=A0 =A0 &quot; The MPLS Transport Profile (MPLS-TP) [RFC5921] is the set of=
<br>
=A0 =A0 protocol<br>
=A0 =A0 functions that meet the requirements [RFC5654] for the application =
of<br>
=A0 =A0 MPLS to the construction and operation of packet-switched transport=
<br>
=A0 =A0 networks. The MPLS-TP data plane consists of those MPLS-TP function=
s<br>
=A0 =A0 concerned with the encapsulation and forwarding of MPLS-TP packets<=
br>
=A0 =A0 and is described in [RFC5960].&quot;<br>
<br>
=A0 =A0 RFC5654 says:<br>
<br>
=A0 =A0 &quot; =A0 36 =A0It MUST be possible to operate and configure the M=
PLS-TP data<br>
=A0 =A0 =A0 =A0 =A0 =A0 plane without any IP forwarding capability in the M=
PLS-TP data<br>
=A0 =A0 =A0 =A0 =A0 =A0 plane. =A0That is, the data plane only operates on =
the MPLS label.&quot;<br>
=A0 =A0 Thus I think that the text is complete as it stands and requires no=
<br>
=A0 =A0 further clarification for anyone that needs to consider the technol=
ogy<br>
=A0 =A0 it describes.<br>
<br>
<br>
=A0 =A0 With regard to your second point, the issue that we are have, is th=
at<br>
=A0 =A0 there are a number of deployment scenarios where the operator knows=
<br>
=A0 =A0 that the link is Pt-Pt, and there is a reluctance by that community=
 to<br>
=A0 =A0 use anything other than NMS configuration. That has lead them<br>
=A0 =A0 to use Ethernet broadcast addressing which allows the crafts to<br>
=A0 =A0 change h/w without the need for reconfiguration by the NMS.<br>
=A0 =A0 Against that background moving them onto the use of a Ethernet m/c<=
br>
=A0 =A0 address is a step forward. To require using the GAP to that<br>
=A0 =A0 community would illustrate that the IETF is out of touch with<br>
=A0 =A0 their needs and methods of network operation.<br>
<br>
=A0 =A0 Hopefully this additional background, which I believe is well<br>
=A0 =A0 known to the MPLS-TP community to which this draft is directed,<br>
=A0 =A0 satisfies your concern on the latter point.<br>
<br>
=A0 =A0 - Stewart<br>
<br>
<br>
<br>
=A0 =A0 -- =A0 =A0 For corporate legal information go to:<br>
<br>
=A0 =A0 <a href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/=
index.html" target=3D"_blank">http://www.cisco.com/web/<u></u>about/doing_b=
usiness/legal/<u></u>cri/index.html</a><br>
<br>
<br>
</div></div></blockquote><div class=3D"HOEnZb"><div class=3D"h5">
<br>
<br>
-- <br>
For corporate legal information go to:<br>
<br>
<a href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.ht=
ml" target=3D"_blank">http://www.cisco.com/web/<u></u>about/doing_business/=
legal/<u></u>cri/index.html</a><br>
<br>
</div></div></blockquote></div><br></div>

--f46d044794f36f602c04d9de853d--

From swb@internet2.edu  Mon Apr  8 12:34:47 2013
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 4908721F8D2A for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 12:34:47 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JeDXO9lcr9Zy for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 12:34:46 -0700 (PDT)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe001.messaging.microsoft.com [213.199.154.204]) by ietfa.amsl.com (Postfix) with ESMTP id 872B721F891D for <ietf@ietf.org>; Mon,  8 Apr 2013 12:34:46 -0700 (PDT)
Received: from mail70-am1-R.bigfish.com (10.3.201.250) by AM1EHSOBE019.bigfish.com (10.3.207.141) with Microsoft SMTP Server id 14.1.225.23; Mon, 8 Apr 2013 19:34:45 +0000
Received: from mail70-am1 (localhost [127.0.0.1])	by mail70-am1-R.bigfish.com (Postfix) with ESMTP id 50F293E012B; Mon,  8 Apr 2013 19:34:45 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.241.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0810HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 7
X-BigFish: S7(zzbb2dI98dI1432Izz1f42h1fc6h1d77h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1082kzzz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1b1cn1b1bi1155h)
Received: from mail70-am1 (localhost.localdomain [127.0.0.1]) by mail70-am1 (MessageSwitch) id 1365449683798367_14820; Mon,  8 Apr 2013 19:34:43 +0000 (UTC)
Received: from AM1EHSMHS002.bigfish.com (unknown [10.3.201.252])	by mail70-am1.bigfish.com (Postfix) with ESMTP id B68962C0A51; Mon,  8 Apr 2013 19:34:43 +0000 (UTC)
Received: from BL2PRD0810HT003.namprd08.prod.outlook.com (157.56.241.101) by AM1EHSMHS002.bigfish.com (10.3.207.102) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 8 Apr 2013 19:34:42 +0000
Received: from swbi2mbp.local (208.54.95.22) by pod51019.outlook.com (10.255.110.38) with Microsoft SMTP Server (TLS) id 14.16.287.8; Mon, 8 Apr 2013 19:34:41 +0000
Message-ID: <51631BCD.3020601@internet2.edu>
Date: Mon, 8 Apr 2013 15:34:37 -0400
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Lucy Lynch <llynch@civil-tongue.net>
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
References: <9515564336C5B442A00021645539CFCC28A1403D@xmb-rcd-x08.cisco.com> <alpine.BSF.2.00.1304081033200.14142@hiroshima.bogus.com>
In-Reply-To: <alpine.BSF.2.00.1304081033200.14142@hiroshima.bogus.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [208.54.95.22]
X-OriginatorOrg: internet2.edu
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, 08 Apr 2013 19:34:47 -0000

On 04/08/13 13:35, Lucy Lynch allegedly wrote:
> On Mon, 8 Apr 2013, Wes Beebee (wbeebee) wrote:
> 
>>
>>> If the date is special then thoes RFCs SHOULD be *historical*.
>>
>> I thought they should be classified as "hysterical".
> 
> there is an echo (echo) ((echo) ) in here (here) ((here))

IETF humor has lots of hysteresis.


From ynir@checkpoint.com  Mon Apr  8 14:11:43 2013
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 D620321F913E for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 14:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.385
X-Spam-Level: 
X-Spam-Status: No, score=-10.385 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBUGj1u1tiFK for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 14:11:43 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id CB77E21F92B7 for <ietf@ietf.org>; Mon,  8 Apr 2013 14:11:42 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r38LBd1t019751; Tue, 9 Apr 2013 00:11:40 +0300
X-CheckPoint: {51633273-1-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Tue, 9 Apr 2013 00:11:39 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Thread-Topic: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
Thread-Index: AQHONI4cnBN2Wbum6UW6bwQTtHHuUpjMn/SA
Date: Mon, 8 Apr 2013 21:11:38 +0000
Message-ID: <8F6B7ADA-B9A7-4F3A-A59D-7C527B548CF6@checkpoint.com>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org> <CAKRbAfBQjs-tM4xmEN4m+HYqNDswNqoXBNSJTHYZ6h1XS9t8UA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775138028@mbx-01.win.nominum.com> <CAKRbAfA4S3iuYmER=Fm9b10yJ_yQ8hi+zY0uZifdXuSMt7C3FQ@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751383B4@mbx-01.win.nominum.com> <CAKRbAfAxddKNKGPrvOTgMRD0AiJjEdZd9aKPMH_0gzTQn0DMgQ@mail.gmail.com> <20130408191953.GE1162@besserwisser.org>
In-Reply-To: <20130408191953.GE1162@besserwisser.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.104]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <CE775A5432C0DE4FBCD21A188504D0D0@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, 08 Apr 2013 21:11:44 -0000

On Apr 8, 2013, at 10:19 PM, M=E5ns Nilsson <mansaxel@besserwisser.org> wro=
te:

> Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) -=
 IETF April 1 jokes. Date: Mon, Apr 08, 2013 at 05:57:54AM -0800 Quoting Me=
linda Shore (melinda.shore@gmail.com):
>> I am absolutely not suggesting changing anything other than the
>> unfortunate  attitude that the right response to someone missing the jok=
e
>> is to read them out of the meeting/declare them anathema or unworthy or =
not
>> members of this community.  Your beef isn't with me, it's with M=E5ns.
>=20
> To clarify:=20
>=20
> I was thinking of vendors, not people . =20

Hey! That's hurtful.    ;-)

> The vendor that does not invest
> in its staff enough to expose them to the IETF culture may not supply
> my network with code and boxes.

The IETF is an SDO. Standards are important in the creation of boxes and th=
e code that runs on them, but there's a lot more that goes into making good=
 code or a good box. I don't believe that appreciating the in-jokes of the =
IETF, or an understanding of the fine points of rough consensus are necessa=
ry for making good boxes. The culture of the IETF may or may not be crucial=
 for the functioning of the IETF, but I don't think you need to be in on it=
 to implement some RFC.

> People who initially fail to appreciate the jokes for what they are
> should be enlightened in the most gentle way possible.
>=20
> At no time have I proposed or held the belief that public humiliation
> is in any way acceptable.
>=20
> --=20
> M=E5ns Nilsson     primary/secondary/besserwisser/machina
> MN-1334-RIPE                             +46 705 989668
> We have DIFFERENT amounts of HAIR --


From braden@isi.edu  Mon Apr  8 14:39:31 2013
Return-Path: <braden@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 EF75B21F8EB1 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 14:39:31 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XRnRvoqj-AEk for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 14:39:31 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6C3E521F8EAE for <ietf@ietf.org>; Mon,  8 Apr 2013 14:39:31 -0700 (PDT)
Received: from [128.9.168.81] (rtb.isi.edu [128.9.168.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r38Lctgt024395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 8 Apr 2013 14:38:55 -0700 (PDT)
Message-ID: <516338F2.5080901@isi.edu>
Date: Mon, 08 Apr 2013 14:38:58 -0700
From: Bob Braden <braden@isi.edu>
Organization: USC/ISI
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
References: <CADnDZ88e4V30C4AfTDMF1-gTEi4qRV-H7R0-Es2oTzkqUgkJRw@mail.gmail.com> <516044AE.8080904@isdg.net> <CADnDZ88HYzq=ceaPn_8fht3J2Xp0PDSrV52uhfLF6Tc56XEZAA@mail.gmail.com> <CAKHUCzw3WZfae5AhM3UQYDZiZCwR6qfkMm7QMt9pZM9UgX2SFw@mail.gmail.com> <CAK=bVC9O=O9DUEmfCYFdAWWxnChiLQvuhmgZ-F2iY_GN1SY7hg@mail.gmail.com> <5463E929-0889-4C96-AC0E-28A37CFC4F4B@checkpoint.com>
In-Reply-To: <5463E929-0889-4C96-AC0E-28A37CFC4F4B@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: braden@isi.edu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Apr 2013 21:39:32 -0000

On 4/6/2013 2:59 PM, Yoav Nir wrote:
> On Apr 7, 2013, at 12:33 AM, Ulrich Herberg <ulrich@herberg.name> wrote:
>
>> Indeed. The wikipedia entry is somewhat misleading though:
>> http://en.wikipedia.org/wiki/April_Fools%27_Day_RFC
>>
>> "Almost every April Fools' Day (1 April) since 1989, the Internet
>> Engineering Task Force has published one or more humorous Request for
>> Comments (RFC) documents,"

Actually, the IETF has very little to do with April  1 RFCs, except to
enjoy them. The RFC Editor is entirely responsible. The RFC Editor
accepts submissions, consults with a few experienced
members of the Internet technical community, chooses which ones are
sufficiently well written and clever, and publishes them. There may be one
or more rounds of editorial suggestions and author updates before
publication.

Bob Braden

PS to Heather: Well done!

From doug.mtview@gmail.com  Mon Apr  8 21:18:28 2013
Return-Path: <doug.mtview@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 E839B21F9022 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 21:18:27 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id efvLvmcxgMJY for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 21:18:26 -0700 (PDT)
Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by ietfa.amsl.com (Postfix) with ESMTP id 8D5C721F9021 for <ietf@ietf.org>; Mon,  8 Apr 2013 21:18:26 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id bj3so3630710pad.34 for <ietf@ietf.org>; Mon, 08 Apr 2013 21:18:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:message-id:references:to:x-mailer; bh=KgQQMgOG3aZiEmG71+o3hZo/1PihditJwvWCueKNmaI=; b=kDIIoL0Se87nVBqP2tdpSvAgNNXUjc+624j2h0EQf2G+kpnUzcgWtrDXj6d468ycaE PkN9a8CPvtI9qOKRdRqGz515814KI26knpgVyFO2pLbn6pGUpAHTALzfRBcQEQ2jUtPN wHNG4eoMfiKfX+WxUSDF59Ri2Bf6DRU0soOrtm2O7ow2tNqEHNzEH72qtuqOGXXaxVOC KenpJCJkXzWTUhFV56QYf4N/832elL2reCXg8JA7I1/jCSy/ZRJ5zxHRn9a0l/6hRNSz 6AvlUmrlscoVDC0+HK8fUIviFYq6N5xqRJ8ACiubMBsiixiIILPb1jc2s1LFT0SL9HSz JqoQ==
X-Received: by 10.68.93.1 with SMTP id cq1mr509418pbb.50.1365481106081; Mon, 08 Apr 2013 21:18:26 -0700 (PDT)
Received: from [192.168.2.60] (c-24-6-101-92.hsd1.ca.comcast.net. [24.6.101.92]) by mx.google.com with ESMTPS id br2sm469045pbc.46.2013.04.08.21.18.23 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Apr 2013 21:18:24 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_E61A6F00-5CDD-4BC4-9069-A65F5B02E566"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Sufficient email authentication requirements for IPv6
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <5157F29F.30805@dougbarton.us>
Date: Mon, 8 Apr 2013 21:18:21 -0700
Message-Id: <AD75DF4E-7A7E-408B-B372-E876411CDBF4@gmail.com>
References: <CANB+R+WfeBu49YdsENwkJMZnu7zAHaNGSqOfkcmJOW7X5TOg9A@mail.gmail.com> <5154C9E0.7060408@isdg.net> <357617C8-766E-4CCF-A733-E032103211E1@gmail.com> <C91E67751B1EFF41B857DE2FE1F68ABA0BFF8A84@tk5ex14mbxc272.redmond.corp.microsoft.com> <5157F29F.30805@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1503)
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, 09 Apr 2013 04:18:28 -0000

--Apple-Mail=_E61A6F00-5CDD-4BC4-9069-A65F5B02E566
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Mar 31, 2013, at 1:23 AM, Doug Barton <dougb@dougbarton.us> wrote:

> On 03/30/2013 11:26 PM, Christian Huitema wrote:
>>> IPv6 makes publishing IP address reputations impractical.  Since IP =
address reputation has been a primary method for identifying abusive =
sources with IPv4, imposing ineffective and flaky > replacement =
strategies has an effect of deterring IPv6 use.
>>=20
>> In practice, the /64 prefix of the IPv6 address has very much the =
same "administrative" properties as the /32 value of the IPv4 address. =
It should be fairly straightforward to update a reputation system to =
manage the /64 prefixes of IPv6. This seems somewhat more practical than =
trying to change the behavior of mail agent if their connectivity =
happens to use IPv6.
>=20
> That only works insofar as the provider does not follow the standard =
recommendation to issue a /48. If they do, the abuser has 65k /64s to =
operate in.
>=20
> What's needed is a little more intelligence about how the networks =
which the IPv6 addresses are located are structured. Similar to the way =
that reputation lists nowadays will black list a whole /24 if 1 or a few =
addresses within it send spam.
>=20
> The problems are not insoluble, they're just different, and arguably =
more complex in v6. It's also likely that in the end more work on =
reputation lists will provide less benefit than it did in the v4 world. =
But that's the world we live in now.

Dear Doug,

Why aggregate into groups of 64k prefixes?  After all, this still does =
not offer a practical way to ascertain a granularity that isolates =
different entities at /64 or /48.  It is not possible to ascertain these =
boundaries even at a single prefix.  There is 37k BGP entries offering =
IPv6 connectivity.  Why not hold each announcement accountable and make =
consolidated reputation a problem ISPs must handle?  Of course, such an =
approach would carry an inordinate level of support and litigation costs =
due to inadvertent collateral blocking.  Such consolidation would be as =
impractical as would an arbitrary consolidation at /48. =20

Prior traffic is required to review reverse DNS PTR records, which is =
resource intensive due to unavoidable delays.  Our IPv4 reputation =
services will not block entire /24s based upon a few detected abusive =
sources.  CIDR listings grow only after abuse exceeds half.   Even this =
conservative approach is problematic in places like China.  There are 4 =
million /64 prefixes for every possible IPv4 address .  Taking an =
incremental CIDR blocking approach still involves keeping track of a =
prefix space 4 million times larger than the entire IPv4 address space, =
where it is generally understood sharing the same IP address carries a =
risk.  Are you really suggesting that sharing the same /48 carries a =
similar risk?

The goal should be to avoid guesswork and uncertainty currently plaguing =
email.

v6 BGP announcement growth graph is published at:=20
http://bgp.potaroo.net/v6/as2.0/

Regards,
Douglas Otis






--Apple-Mail=_E61A6F00-5CDD-4BC4-9069-A65F5B02E566
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 Mar 31, 2013, at 1:23 AM, Doug Barton &lt;<a =
href=3D"mailto:dougb@dougbarton.us">dougb@dougbarton.us</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">On 03/30/2013 11:26 PM, Christian Huitema =
wrote:<br><blockquote type=3D"cite"><blockquote type=3D"cite">IPv6 makes =
publishing IP address reputations impractical. &nbsp;Since IP address =
reputation has been a primary method for identifying abusive sources =
with IPv4, imposing ineffective and flaky &gt; replacement strategies =
has an effect of deterring IPv6 use.<br></blockquote><br>In practice, =
the /64 prefix of the IPv6 address has very much the same =
"administrative" properties as the /32 value of the IPv4 address. It =
should be fairly straightforward to update a reputation system to manage =
the /64 prefixes of IPv6. This seems somewhat more practical than trying =
to change the behavior of mail agent if their connectivity happens to =
use IPv6.<br></blockquote><br>That only works insofar as the provider =
does not follow the standard recommendation to issue a /48. If they do, =
the abuser has 65k /64s to operate in.<br><br>What's needed is a little =
more intelligence about how the networks which the IPv6 addresses are =
located are structured. Similar to the way that reputation lists =
nowadays will black list a whole /24 if 1 or a few addresses within it =
send spam.<br><br>The problems are not insoluble, they're just =
different, and arguably more complex in v6. It's also likely that in the =
end more work on reputation lists will provide less benefit than it did =
in the v4 world. But that's the world we live in =
now.<br></blockquote><br></div><div>Dear =
Doug,</div><div><br></div><div>Why aggregate into groups of 64k =
prefixes? &nbsp;After all, this still does not offer a&nbsp;practical =
way to ascertain a granularity that isolates different entities at /64 =
or /48.&nbsp;&nbsp;It is not possible to ascertain these boundaries even =
at a single prefix. &nbsp;There is 37k BGP entries offering IPv6 =
connectivity. &nbsp;Why not hold each announcement accountable and make =
consolidated reputation a problem ISPs must handle? &nbsp;Of course, =
such an approach would carry an inordinate level of support and =
litigation costs due to inadvertent collateral blocking. &nbsp;Such =
consolidation would be as impractical as would an arbitrary =
consolidation at /48. &nbsp;</div><div><br></div><div>Prior traffic is =
required to review reverse DNS PTR records, which is resource intensive =
due to unavoidable delays. &nbsp;Our IPv4 reputation services will not =
block entire /24s based upon a few detected abusive sources. &nbsp;CIDR =
listings grow only after abuse exceeds half. &nbsp; Even this =
conservative approach is problematic in places like China. &nbsp;There =
are 4 million /64 prefixes&nbsp;for every possible IPv4 address&nbsp;. =
&nbsp;Taking an incremental CIDR blocking approach still involves =
keeping track of a prefix space 4 million times larger than the entire =
IPv4 address space, where it is generally understood sharing the same IP =
address carries a risk. &nbsp;Are you really suggesting that sharing the =
same /48 carries a similar risk?</div><div><br></div><div>The goal =
should be to avoid guesswork and uncertainty currently plaguing =
email.</div><div><br></div><div><div>v6 BGP announcement growth graph is =
published at:&nbsp;</div><div><a =
href=3D"http://bgp.potaroo.net/v6/as2.0/">http://bgp.potaroo.net/v6/as2.0/=
</a></div><div><br></div></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div><div><br></div><div><br></div><br><div><br></div>=
</body></html>=

--Apple-Mail=_E61A6F00-5CDD-4BC4-9069-A65F5B02E566--

From joelja@bogus.com  Mon Apr  8 22:28:00 2013
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 6DE7521F8FA4 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 22:28:00 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ATR+rkWQEXYA for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 22:27:59 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A09F521F8F86 for <ietf@ietf.org>; Mon,  8 Apr 2013 22:27:59 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r395RtFh062071 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 9 Apr 2013 05:27:56 GMT (envelope-from joelja@bogus.com)
Message-ID: <5163A6D6.4040401@bogus.com>
Date: Mon, 08 Apr 2013 22:27:50 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:20.0) Gecko/20100101 Thunderbird/20.0
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>, Doug Barton <dougb@dougbarton.us>
Subject: Re: Sufficient email authentication requirements for IPv6
References: <CANB+R+WfeBu49YdsENwkJMZnu7zAHaNGSqOfkcmJOW7X5TOg9A@mail.gmail.com> <5154C9E0.7060408@isdg.net> <357617C8-766E-4CCF-A733-E032103211E1@gmail.com> <C91E67751B1EFF41B857DE2FE1F68ABA0BFF8A84@tk5ex14mbxc272.redmond.corp.microsoft.com> <5157F29F.30805@dougbarton.us> <AD75DF4E-7A7E-408B-B372-E876411CDBF4@gmail.com>
In-Reply-To: <AD75DF4E-7A7E-408B-B372-E876411CDBF4@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, 09 Apr 2013 05:27:56 +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: Tue, 09 Apr 2013 05:28:00 -0000

On 4/8/13 9:18 PM, Douglas Otis wrote:
>
> On Mar 31, 2013, at 1:23 AM, Doug Barton <dougb@dougbarton.us 
> <mailto:dougb@dougbarton.us>> wrote:
>
>> On 03/30/2013 11:26 PM, Christian Huitema wrote:
>>>> IPv6 makes publishing IP address reputations impractical.  Since IP 
>>>> address reputation has been a primary method for identifying 
>>>> abusive sources with IPv4, imposing ineffective and flaky > 
>>>> replacement strategies has an effect of deterring IPv6 use.
>>>
>>> In practice, the /64 prefix of the IPv6 address has very much the 
>>> same "administrative" properties as the /32 value of the IPv4 
>>> address. It should be fairly straightforward to update a reputation 
>>> system to manage the /64 prefixes of IPv6. This seems somewhat more 
>>> practical than trying to change the behavior of mail agent if their 
>>> connectivity happens to use IPv6.
>>
>> That only works insofar as the provider does not follow the standard 
>> recommendation to issue a /48. If they do, the abuser has 65k /64s to 
>> operate in.
>>
>> What's needed is a little more intelligence about how the networks 
>> which the IPv6 addresses are located are structured. Similar to the 
>> way that reputation lists nowadays will black list a whole /24 if 1 
>> or a few addresses within it send spam.
>>
>> The problems are not insoluble, they're just different, and arguably 
>> more complex in v6. It's also likely that in the end more work on 
>> reputation lists will provide less benefit than it did in the v4 
>> world. But that's the world we live in now.
>
> Dear Doug,
>
> Why aggregate into groups of 64k prefixes?  After all, this still does 
> not offer a practical way to ascertain a granularity that isolates 
> different entities at /64 or /48.  It is not possible to ascertain 
> these boundaries even at a single prefix.  There is 37k BGP entries 
> offering IPv6 connectivity.  Why not hold each announcement 
> accountable and make consolidated reputation a problem ISPs must 
> handle?  Of course, such an approach would carry an inordinate level 
> of support and litigation costs due to inadvertent collateral 
> blocking.  Such consolidation would be as impractical as would an 
> arbitrary consolidation at /48.
>
Plently of people use IP to ASN mappings as part of their input for 
reputation today.
> Prior traffic is required to review reverse DNS PTR records, which is 
> resource intensive due to unavoidable delays.  Our IPv4 reputation 
> services will not block entire /24s based upon a few detected abusive 
> sources.  CIDR listings grow only after abuse exceeds half.   Even 
> this conservative approach is problematic in places like China.  There 
> are 4 million /64 prefixes for every possible IPv4 address .  Taking 
> an incremental CIDR blocking approach still involves keeping track of 
> a prefix space 4 million times larger than the entire IPv4 address 
> space, where it is generally understood sharing the same IP address 
> carries a risk.  Are you really suggesting that sharing the same /48 
> carries a similar risk?
>
> The goal should be to avoid guesswork and uncertainty currently 
> plaguing email.
>
> v6 BGP announcement growth graph is published at:
> http://bgp.potaroo.net/v6/as2.0/
>
> Regards,
> Douglas Otis
>
>
>
>
>


From l.wood@surrey.ac.uk  Tue Apr  9 00:04:06 2013
Return-Path: <l.wood@surrey.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 05DF821F8766 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 00:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.848
X-Spam-Level: 
X-Spam-Status: No, score=-3.848 tagged_above=-999 required=5 tests=[AWL=-1.250, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCSoPLuZ+ITv for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 00:04:04 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.143]) by ietfa.amsl.com (Postfix) with ESMTP id 974DB21F84E2 for <ietf@ietf.org>; Tue,  9 Apr 2013 00:04:04 -0700 (PDT)
Received: from [195.245.231.67:27609] by server-7.bemta-5.messagelabs.com id 6C/3E-12441-26DB3615; Tue, 09 Apr 2013 07:04:02 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-82.messagelabs.com!1365491042!31813191!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17108 invoked from network); 9 Apr 2013 07:04:02 -0000
Received: from unknown (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-12.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 9 Apr 2013 07:04:02 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Tue, 9 Apr 2013 08:04:01 +0100
From: <l.wood@surrey.ac.uk>
To: <swb@internet2.edu>, <llynch@civil-tongue.net>
Date: Tue, 9 Apr 2013 08:01:37 +0100
Subject: RE: Comments for Humorous RFCs or uncategorised RFCs or dated April the first
Thread-Topic: Comments for Humorous RFCs or uncategorised RFCs or dated April	the first
Thread-Index: Ac40kDrrHbVjG2J1TuacVVbZzzridQAX9le7
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E57@EXMB01CMS.surrey.ac.uk>
References: <9515564336C5B442A00021645539CFCC28A1403D@xmb-rcd-x08.cisco.com> <alpine.BSF.2.00.1304081033200.14142@hiroshima.bogus.com>, <51631BCD.3020601@internet2.edu>
In-Reply-To: <51631BCD.3020601@internet2.edu>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org, 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: Tue, 09 Apr 2013 07:04:06 -0000

There's a lot of hysteresis... because calling it funny is often a stretch.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Scott Brim=
 [swb@internet2.edu]
Sent: 08 April 2013 20:34
To: Lucy Lynch
Cc: ietf; Abdussalam Baryun
Subject: Re: Comments for Humorous RFCs or uncategorised RFCs or dated Apri=
l    the first

On 04/08/13 13:35, Lucy Lynch allegedly wrote:
> On Mon, 8 Apr 2013, Wes Beebee (wbeebee) wrote:
>
>>
>>> If the date is special then thoes RFCs SHOULD be *historical*.
>>
>> I thought they should be classified as "hysterical".
>
> there is an echo (echo) ((echo) ) in here (here) ((here))

IETF humor has lots of hysteresis.


From peter@akayla.com  Tue Apr  9 01:12:50 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30B6821F8521; Tue,  9 Apr 2013 01:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=-0.400,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PXWzDy4zk0zN; Tue,  9 Apr 2013 01:12:49 -0700 (PDT)
Received: from p3plsmtpa08-05.prod.phx3.secureserver.net (p3plsmtpa08-05.prod.phx3.secureserver.net [173.201.193.106]) by ietfa.amsl.com (Postfix) with ESMTP id 25FCF21F8967; Tue,  9 Apr 2013 01:12:48 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa08-05.prod.phx3.secureserver.net with  id MkCm1l00Q1huGat01kCmbj; Tue, 09 Apr 2013 01:12:48 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Date: Tue, 9 Apr 2013 01:12:49 -0700
Message-ID: <054201ce34fa$0746ec80$15d4c580$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac409G6BqoWAcV+eTe6M/+710JRlsQ==
Content-Language: en-us
Cc: gen-art@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, 09 Apr 2013 08:12:50 -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-pcp-upnp-igd-interworking-07
Reviewer: Peter Yee
Review Date: Apr-08-2013
IETF LC End Date: Apr-08-2013
IESG Telechat date: Unknown

Summary: This draft is on the right track but has open issues, described in
the review. [Ready with issues]

This is a well-written draft describing how Universal Plug-and-Play Internet
Gateway Devices interwork with NAT devices that use the Port Control
Protocol.  My review is mostly nits with otherwise minor issues.  I have no
problems with the general concept and enjoyed reading a clearly articulated
concept.

Major Issues:

None.

Minor Issues:

Section 4.1: is the mapping of the state variables between the UPnP IGD
function and the PCP Client function really straightforward such that it
does not need further description?  I'm asking if an implementor would
naturally gravitate to the correct use of the mapping without further
instructions.  Similar questions arise for Sections 4.2 and 4.3, although I
believe those are more straightforward mappings.

Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP error
other than a short-lifetime error, or in the case of a failed resend, any
PCP error at all.  The wording makes it seem like the short-lifetime errors
are somehow not PCP errors and is therefore confusing.  It also doesn't
explicitly deal with how many repeats should be done on a resend.  

Nits:

General: replace "re-send" with "resend".

Page 3, 1st paragraph, 2nd sentence: insert "a" before each occurrence of
UPnP.  

Page 4, section 3, 4th bullet: consider changing "in" to "on" or "over".

Page 4, 1st paragraph after the bullet items: bracket "for instance" with
commas.

Page 5, Figure 3: perhaps the "LAN Side" label could move a bit to the left
to give it better delineation from the "External Side" label?

Page 5, 1st paragraph after Figure 4, 2nd sentence: add a comma after "
[I-D.ietf-pcp-base]".

Page 5, 2nd paragraph after Figure 4: change "can not" to "cannot".

Page 9, section 5, 3rd paragraph: insert "the same way" or "the same" before
"as any PCP Client".

Page 9, section 5.1, 2nd paragraph: insert "whether" before "it should".

Page 9, section 5.1, 3rd paragraph: insert "the" before "requesting UPnP
Control Point".

Page 10, Section 5.3, 2nd paragraph, 1st sentence: consider changing
"retrieve" to "extract".

Page 11, 1st paragraph after bullet items, 2nd sentence: change "to" to
"than".

Page 11, Section 5.6: swap the order of "AddPortMapping()" and
"AddAnyPortMapping()" to match the order of the subsequent subsections.

Page 11, Section 5.6.1, 2nd paragraph, 2nd sentence: change "30s" to "30
seconds".

Page 13, 1st paragraph, 4th sentence: change "re-issue" to "issue"; change
"new requested" to "different requested".

Page 14, last paragraph: delete the comma after "4 times)".

Page 15, Section 5.7, 1st paragraph: append a comma after
"GetSpecificPortMappingEntry()".

Page 15, Section 5.7, 3rd paragraph, 3rd sentence: replace "60s" with "60
seconds".

Page 15, Section 5.7, 3rd paragraph, last sentence: insert "the" before
"error code"; change "enquried" to "queried".

Page 15, Section 5.8, 1st paragraph: insert ", respectively" before the
period.

Page 15, Section 5.8, 2nd paragraph, 2nd sentence: insert "the" before '"606
Action Not'.

Page 16, last paragraph, 2nd sentence: insert "the" before'"731
PortMappingNotFound'.

Page 19, 1st continuation paragraph, 1st sentence fragment: change "of" to
"in".

Page 19, 1st continuation paragraph, 1st full sentence: consider swapping
the positions of "renew" and "periodically" for readability.

Page 19, Section 5.10, 1st paragraph, 2nd sentence: I prefer "In particular"
to "Particularly" here.

Page 19, Section 5.10, 3rd paragraph, 3rd sentence: replace "signalled" with
"signaled".




From chair@ietf.org  Tue Apr  9 03:27:42 2013
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 5E18C21F9311 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 03:27:42 -0700 (PDT)
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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3v9jDzrol7o for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 03:27:40 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id CED6121F930A for <ietf@ietf.org>; Tue,  9 Apr 2013 03:27:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id CB72012A299; Tue,  9 Apr 2013 03:27:40 -0700 (PDT)
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 HIo_6k2ml5jO; Tue,  9 Apr 2013 03:27:40 -0700 (PDT)
Received: from n238.nomadiclab.com (gw.nomadiclab.com [193.234.218.122]) by c8a.amsl.com (Postfix) with ESMTPSA id DC5A5128C5B; Tue,  9 Apr 2013 03:27:39 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: videos and blog posts on home networking, buffer bloat
Date: Tue, 9 Apr 2013 13:27:36 +0300
Message-Id: <25CBE1A6-DA1E-4CE5-871A-33E4CC445B47@ietf.org>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Cc: John Brzozowski <John_Brzozowski@Cable.Comcast.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, 09 Apr 2013 10:27:42 -0000

The good folks at ISOC shot a number of videos during IETF-86 with =
experts on various topics. These videos are now available, take a look =
at the blog post John and I wrote:

http://www.ietf.org/blog/2013/04/bits-n-bytes-on-video/

The videos can also be accessed directly at:

http://www.youtube.com/watch?v=3D3SvhtLl8aTg (John Brzozowski on HIPnet)
http://www.youtube.com/watch?v=3Dd-vwdD3Xtyg (Mark Townsley on HOMENET)
http://www.youtube.com/watch?v=3DNuHYOu4aAqg (Chris Griffiths and Dave =
T=E4ht on buffer bloat)

There was also an earlier blog post that focused on the importance on =
running code, written together with Chris:

http://www.ietf.org/blog/2013/03/running-code-at-ietf-86-2/

All in all, I thought these demos and videos were very interesting. It =
is excellent that we are building implementations of the things that we =
specify in the working groups. And interestingly, Bits-n-Bytes has =
become a place to show some these results. Thanks to everyone who was =
involved, and the sponsors who made it possible! I also think it would =
be great to have even more of this in the coming IETFs. If you have =
ideas, let us know!

Jari Arkko


From mohamed.boucadair@orange.com  Tue Apr  9 05:27:00 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C749621F8EDB; Tue,  9 Apr 2013 05:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TKQeWyT+Iblb; Tue,  9 Apr 2013 05:27:00 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id E739221F8EB2; Tue,  9 Apr 2013 05:26:59 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 8BA4F2645B2; Tue,  9 Apr 2013 14:26:57 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 5E41B4C015; Tue,  9 Apr 2013 14:26:57 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Tue, 9 Apr 2013 14:26:57 +0200
From: <mohamed.boucadair@orange.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org" <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
Date: Tue, 9 Apr 2013 14:26:55 +0200
Subject: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Thread-Topic: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Thread-Index: Ac409G6BqoWAcV+eTe6M/+710JRlsQAJssnw
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com>
In-Reply-To: <054201ce34fa$0746ec80$15d4c580$@akayla.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.3.25.85421
X-Mailman-Approved-At: Tue, 09 Apr 2013 08:55:15 -0700
Cc: "gen-art@ietf.org" <gen-art@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: Tue, 09 Apr 2013 12:27:00 -0000

Dear Peter,

Thanks for the review.=20
Please see inline.

Cheers,
Med

>-----Message d'origine-----
>De=A0: Peter Yee [mailto:peter@akayla.com]
>Envoy=E9=A0: mardi 9 avril 2013 10:13
>=C0=A0: draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org
>Cc=A0: gen-art@ietf.org; ietf@ietf.org
>Objet=A0: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>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-pcp-upnp-igd-interworking-07
>Reviewer: Peter Yee
>Review Date: Apr-08-2013
>IETF LC End Date: Apr-08-2013
>IESG Telechat date: Unknown
>
>Summary: This draft is on the right track but has open issues, described i=
n
>the review. [Ready with issues]
>
>This is a well-written draft describing how Universal Plug-and-Play
>Internet
>Gateway Devices interwork with NAT devices that use the Port Control
>Protocol.  My review is mostly nits with otherwise minor issues.  I have n=
o
>problems with the general concept and enjoyed reading a clearly articulate=
d
>concept.

[Med] Thanks.

>
>Major Issues:
>
>None.
>
>Minor Issues:
>
>Section 4.1: is the mapping of the state variables between the UPnP IGD
>function and the PCP Client function really straightforward such that it
>does not need further description?  I'm asking if an implementor would
>naturally gravitate to the correct use of the mapping without further
>instructions.  Similar questions arise for Sections 4.2 and 4.3, although =
I
>believe those are more straightforward mappings.

[Med] I don't think further explanation is needed. Pointers to the appropri=
ate sections is included in Section 4.2 and Section 4.3. FWIW, there are al=
ready existing implementations of the IWF and no "complaint" was received f=
rom these implementers.

>
>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP erro=
r
>other than a short-lifetime error, or in the case of a failed resend, any
>PCP error at all.  The wording makes it seem like the short-lifetime error=
s
>are somehow not PCP errors and is therefore confusing.  It also doesn't
>explicitly deal with how many repeats should be done on a resend.

[Med] The basic behavior is to relay the received error to the UPnP CP. For=
 the short-lifetime errors, the IWF may decide to resend the request and no=
t relay those errors immediately to the UPnP CP. The number of repeats is n=
ot specified here as it can be implementation-specific.=20


>Nits:

[Med] Fixed.=20

>
>General: replace "re-send" with "resend".
>
>Page 3, 1st paragraph, 2nd sentence: insert "a" before each occurrence of
>UPnP.
>
>Page 4, section 3, 4th bullet: consider changing "in" to "on" or "over".
>
>Page 4, 1st paragraph after the bullet items: bracket "for instance" with
>commas.
>
>Page 5, Figure 3: perhaps the "LAN Side" label could move a bit to the lef=
t
>to give it better delineation from the "External Side" label?
>
>Page 5, 1st paragraph after Figure 4, 2nd sentence: add a comma after "
>[I-D.ietf-pcp-base]".
>
>Page 5, 2nd paragraph after Figure 4: change "can not" to "cannot".
>
>Page 9, section 5, 3rd paragraph: insert "the same way" or "the same"
>before
>"as any PCP Client".
>
>Page 9, section 5.1, 2nd paragraph: insert "whether" before "it should".
>
>Page 9, section 5.1, 3rd paragraph: insert "the" before "requesting UPnP
>Control Point".
>
>Page 10, Section 5.3, 2nd paragraph, 1st sentence: consider changing
>"retrieve" to "extract".
>
>Page 11, 1st paragraph after bullet items, 2nd sentence: change "to" to
>"than".
>
>Page 11, Section 5.6: swap the order of "AddPortMapping()" and
>"AddAnyPortMapping()" to match the order of the subsequent subsections.
>
>Page 11, Section 5.6.1, 2nd paragraph, 2nd sentence: change "30s" to "30
>seconds".
>
>Page 13, 1st paragraph, 4th sentence: change "re-issue" to "issue"; change
>"new requested" to "different requested".
>
>Page 14, last paragraph: delete the comma after "4 times)".
>
>Page 15, Section 5.7, 1st paragraph: append a comma after
>"GetSpecificPortMappingEntry()".
>
>Page 15, Section 5.7, 3rd paragraph, 3rd sentence: replace "60s" with "60
>seconds".
>
>Page 15, Section 5.7, 3rd paragraph, last sentence: insert "the" before
>"error code"; change "enquried" to "queried".
>
>Page 15, Section 5.8, 1st paragraph: insert ", respectively" before the
>period.
>
>Page 15, Section 5.8, 2nd paragraph, 2nd sentence: insert "the" before
>'"606
>Action Not'.
>
>Page 16, last paragraph, 2nd sentence: insert "the" before'"731
>PortMappingNotFound'.
>
>Page 19, 1st continuation paragraph, 1st sentence fragment: change "of" to
>"in".
>
>Page 19, 1st continuation paragraph, 1st full sentence: consider swapping
>the positions of "renew" and "periodically" for readability.
>
>Page 19, Section 5.10, 1st paragraph, 2nd sentence: I prefer "In
>particular"
>to "Particularly" here.
>
>Page 19, Section 5.10, 3rd paragraph, 3rd sentence: replace "signalled"
>with
>"signaled".
>
>


From hotz@jpl.nasa.gov  Mon Apr  8 13:35:06 2013
Return-Path: <hotz@jpl.nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3FCB21F92FB; Mon,  8 Apr 2013 13:35:06 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bTdTjI9SGHIU; Mon,  8 Apr 2013 13:35:06 -0700 (PDT)
Received: from mail.jpl.nasa.gov (sentrion2.jpl.nasa.gov [128.149.139.106]) by ietfa.amsl.com (Postfix) with ESMTP id 3C5D921F92F4; Mon,  8 Apr 2013 13:35:06 -0700 (PDT)
Received: from laphotz.jpl.nasa.gov (laphotz.jpl.nasa.gov [128.149.133.44]) (authenticated (0 bits)) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r38KZ3xp002425 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Mon, 8 Apr 2013 13:35:04 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
In-Reply-To: <5162D56B.9060404@ieca.com>
Date: Mon, 8 Apr 2013 13:35:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <34EC8B90-9952-4B8E-BFC2-7913F198453F@jpl.nasa.gov>
References: <20130323065208.090391A65A@ld9781.wdf.sap.corp> <5162D56B.9060404@ieca.com>
To: Sean Turner <turners@ieca.com>
X-Mailer: Apple Mail (2.1503)
X-Source-Sender: hotz@jpl.nasa.gov
X-AUTH: Authorized
X-Mailman-Approved-At: Tue, 09 Apr 2013 08:55:59 -0700
Cc: pkix@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, 08 Apr 2013 20:35:06 -0000

Actually, what I get from this and all the other discussions is that =
it's unclear if the updated OCSP satisfies the "suitability for the =
intended purpose" test.  Or at least it fails the KISS principle w.r.t. =
that.

Rephrasing:  an OCSP client should be able to tell from an OCSP response =
if:  a) the subject cert is on the CAs white list, b) the subject cert =
is on the CAs black list, c) the subject cert is not on either list, or =
finally d) the OCSP server is obsolete, and doesn't support making those =
distinctions.  It's not trivial to see how to parse 2560bis responses =
w.r.t. those cases, therefore it's highly likely that computational =
complexity will prevent us from doing so.  Even if that's not actually =
the case, then implementor misunderstandings will prevent us from doing =
so in practice.

Therefore I vote against moving this draft forward.  I just don't see =
the point.

If someone were to write an informational RFC which explained how to =
determine which of the 4 cases an OCSP response fell into, AND if said =
RFC also convinced me that the decision process was easy to understand, =
THEN I would change my vote.  Obviously an appendix in 2560bis would =
serve just as well.=

From piyush@ditenity.com  Mon Apr  8 15:01:18 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A38021F8C3C for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 15:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.752
X-Spam-Level: 
X-Spam-Status: No, score=-0.752 tagged_above=-999 required=5 tests=[AWL=-1.348, BAYES_00=-2.599, DOS_OUTLOOK_TO_MX=1, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_EQ_LT4=0.442, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HcD9CqW58UL7 for <ietf@ietfa.amsl.com>; Mon,  8 Apr 2013 15:01:18 -0700 (PDT)
Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id F06A121F8BF8 for <ietf@ietf.org>; Mon,  8 Apr 2013 15:01:17 -0700 (PDT)
Received: by mail-yh0-f48.google.com with SMTP id q46so180422yhf.35 for <ietf@ietf.org>; Mon, 08 Apr 2013 15:01:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=p+ub5eUOxkf+ziEAp5KEwLsRcD51kOfQtWJ+qtiwD/A=; b=lbFTSqZCsmlkeX81rtUoLX4HNlqPrjJaRAnMQHCGBttHl9dGwM4VgAb8CQHNREr78f xdrPLr4rvbJkV5Xm2fxVFGVXHEz2qNDL+mV3TFxUyHlMFipjNsOrBhxtBWcHL+DiLN3q GFl3B4+q+KwwoKydGY4h9dNpwBrw5MponFih6nizeMEjifJ2m11OD7nSuCBu/UMPoqZY +Fs8YMJdhc5BaN0xy3AVPGwa190NDAVpLbZRkq7jcBqPa/fpt9qRSlPTErNb223lbO2p EgdazHVyAaEGe8CEvrXP+DsikfJgWW1LwtBR+VtEfS191YQj3qnrSauQVWpKEeDYdrOl /4cw==
X-Received: by 10.236.118.68 with SMTP id k44mr13687103yhh.70.1365458477423; Mon, 08 Apr 2013 15:01:17 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id y5sm27466733yhd.3.2013.04.08.15.01.16 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 08 Apr 2013 15:01:16 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, "'Sean Turner'" <turners@ieca.com>
References: <20130323065208.090391A65A@ld9781.wdf.sap.corp> <5162D56B.9060404@ieca.com> <34EC8B90-9952-4B8E-BFC2-7913F198453F@jpl.nasa.gov>
In-Reply-To: <34EC8B90-9952-4B8E-BFC2-7913F198453F@jpl.nasa.gov>
Subject: RE: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
Date: Mon, 8 Apr 2013 15:01:04 -0700
Message-ID: <07f001ce34a4$917507d0$b45f1770$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKR4daoZiTecUDX96ZN+L83E79W/AHMbHi3AmA5emuXJCAWEA==
Content-Language: en-us
X-Gm-Message-State: ALoCoQlma2MgLCiSxyiulrVAdCkUAPQgE8DiwQaAffAl+1cIV8rkY6hZkonIG09GXUYsarx7czcq
X-Mailman-Approved-At: Tue, 09 Apr 2013 08:56:31 -0700
Cc: pkix@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, 08 Apr 2013 22:01:18 -0000

+1. 

> -----Original Message-----
> From: pkix-bounces@ietf.org [mailto:pkix-bounces@ietf.org] On Behalf Of
> Henry B. Hotz
> Sent: Monday, April 08, 2013 1:35 PM
> To: Sean Turner
> Cc: pkix@ietf.org; ietf@ietf.org
> Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509
> Internet Public Key Infrastructure Online Certificate Status Protocol -
OCSP)
> to Proposed Standard
> 
> Actually, what I get from this and all the other discussions is that it's
unclear if
> the updated OCSP satisfies the "suitability for the intended purpose"
test.
> Or at least it fails the KISS principle w.r.t. that.
> 
> Rephrasing:  an OCSP client should be able to tell from an OCSP response
if:
> a) the subject cert is on the CAs white list, b) the subject cert is on
the CAs
> black list, c) the subject cert is not on either list, or finally d) the
OCSP server
> is obsolete, and doesn't support making those distinctions.  It's not
trivial to
> see how to parse 2560bis responses w.r.t. those cases, therefore it's
highly
> likely that computational complexity will prevent us from doing so.  Even
if
> that's not actually the case, then implementor misunderstandings will
> prevent us from doing so in practice.
> 
> Therefore I vote against moving this draft forward.  I just don't see the
point.
> 
> If someone were to write an informational RFC which explained how to
> determine which of the 4 cases an OCSP response fell into, AND if said RFC
> also convinced me that the decision process was easy to understand, THEN I
> would change my vote.  Obviously an appendix in 2560bis would serve just
as
> well.
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix


From salvatore.dantonio@uniparthenope.it  Tue Apr  9 08:40:37 2013
Return-Path: <salvatore.dantonio@uniparthenope.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 6407621F97A8; Tue,  9 Apr 2013 08:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.127
X-Spam-Level: **
X-Spam-Status: No, score=2.127 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GEnIxUhvZSvT; Tue,  9 Apr 2013 08:40:36 -0700 (PDT)
Received: from mail.uniparthenope.it (mail.uniparthenope.it [192.167.9.244]) by ietfa.amsl.com (Postfix) with ESMTP id B09E121F9798; Tue,  9 Apr 2013 08:40:32 -0700 (PDT)
Received: from mail2.uniparthenope.it (unknown [10.1.2.108]) by mail.uniparthenope.it (Postfix) with SMTP id EA27A41711; Tue,  9 Apr 2013 15:40:30 +0000 (UTC)
Received: from (unknown [192.168.241.108]) by mail2.uniparthenope.it with smtp id 1d43_cec0a27c_a12b_11e2_9101_001372515a5c; Tue, 09 Apr 2013 17:40:30 +0200
Received: from spamk.uniparthenope.it (localhost [127.0.0.1]) by spamk.uniparthenope.it (Postfix) with ESMTP id C174CC430A; Tue,  9 Apr 2013 17:40:29 +0200 (CEST)
Received: by spamk.uniparthenope.it (Postfix, from userid 500) id BA7F1C4302; Tue,  9 Apr 2013 17:40:29 +0200 (CEST)
Received: from mail.uniparthenope.it (unknown [192.168.241.109]) by spamk.uniparthenope.it (Postfix) with ESMTP id 593DCC4301; Tue,  9 Apr 2013 17:40:28 +0200 (CEST)
Received: by mail.uniparthenope.it (Postfix, from userid 108) id 452064181E; Tue,  9 Apr 2013 17:40:28 +0200 (CEST)
Received: from saldantoPC (unknown [192.168.162.11]) (Authenticated sender: salvatore.dantonio@uniparthenope.it) by mail.uniparthenope.it (Postfix) with ESMTPA id 803F841526; Tue,  9 Apr 2013 17:40:18 +0200 (CEST)
From: "Salvatore D'Antonio" <salvatore.dantonio@uniparthenope.it>
To: "'Benoit Claise'" <bclaise@cisco.com>, <draft-ietf-ipfix-flow-selection-tech@tools.ietf.org>
References: <20130401072846.32360.9502.idtracker@ietfa.amsl.com> <5162C44B.5030904@cisco.com>
In-Reply-To: <5162C44B.5030904@cisco.com>
Date: Tue, 9 Apr 2013 17:40:03 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac40XDRV3pT1xDzNTsGp6osHVZb3KAA1rsdA
Content-Language: it
Message-ID: <005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it>
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0058_01CE3549.52940480"
Subject: R: Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.42/RELEASE, bases: 20130409 #9883311, check: 20130409 clean
X-Mailman-Approved-At: Tue, 09 Apr 2013 08:57:11 -0700
Cc: rahulp@cisco.com, 'IETF discussion list' <ietf@ietf.org>, apps-discuss@ietf.org, 'General Area Review Team' <gen-art@ietf.org>, 'S Moonesamy' <sm+ietf@elandsys.com>, ipfix-chairs@tools.ietf.org, ipfix@ietf.org, iesg@ietf.org, "'A. Jean Mahoney'" <mahoney@nostrum.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, 09 Apr 2013 15:40:37 -0000

Messaggio multipart in formato MIME.

------=_NextPart_000_0058_01CE3549.52940480
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Dear all,

=20

A new version of the Internet Draft on Flow Selection Techniques has =
been submitted. It contains the following changes:

-          A new section illustrating the difference between =
Intermediate Flow Selection Process and Intermediate Selection Process =
has been added,

-          The sentence "In order to be compliant with this document, at =
least the Property  Match Filtering MUST be implemented." has been =
removed in Section 1,

-          =E2=80=9CMUST=E2=80=9D has been replaced with =
=E2=80=9CSHOULD=E2=80=9D in Section 5.1,

-          =E2=80=9CThe flowSelectorAlgorithm registry is maintained by =
IANA." has been replaced with =E2=80=9CIANA is requested to create the =
flowSelectorAlgorithm registry.=E2=80=9D

-          The sentence "The registry can be updated when specifications =
of the new  technique(s) and any new Information Elements are provided." =
has been removed since it did not clarify how the registry will be =
managed.

-           Section 6.1.1 =E2=80=9CProperty Match Filtering=E2=80=9D has =
been changed by adding some text on how Property Match Filtering can be  =
used by an Intermediate Flow Selection Process in the Metering Process, =
in the  Exporting Process and within an IPFIX Mediator.

=20

Best regards,

=20

Salvatore

=20

Da: Benoit Claise [mailto:bclaise@cisco.com]=20
Inviato: luned=C3=AC 8 aprile 2013 15:21
A: draft-ietf-ipfix-flow-selection-tech@tools.ietf.org
Cc: ipfix-chairs@tools.ietf.org
Oggetto: Fwd: Last Call Expired: =
<draft-ietf-ipfix-flow-selection-tech-14.txt>

=20

Dear authors,

The IETF last call has finished.
Can you please update your draft based on the feedback received.
Then I will progress it.

Regards, Benoit



-------- Original Message --------=20


Subject:=20

Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>


Date:=20

Mon, 01 Apr 2013 00:28:46 -0700


From:=20

DraftTracker Mail System  <mailto:iesg-secretary@ietf.org> =
<iesg-secretary@ietf.org>


To:=20

iesg@ietf.org, ipfix-chairs@tools.ietf.org, =
draft-ietf-ipfix-flow-selection-tech@tools.ietf.org


CC:=20

iesg-secretary@ietf.org

=20

Please DO NOT reply to this email.
=20
I-D: <draft-ietf-ipfix-flow-selection-tech-14.txt>
ID Tracker URL: =
http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/
=20
IETF Last Call has ended, and the state has been changed to
Waiting for AD Go-Ahead.
=20
=20
=20

=20

=20

  _____ =20

Nessun virus nel messaggio.
Controllato da AVG - www.avg.com
Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di =
rilascio: 07/04/2013


******************************************************************************=09=0A
IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO=0A
 =0A
Il 5 per mille all'Universita' degli Studi di Napoli "Parthenope" incrementa le borse di studio agli studenti - codice fiscale 80018240632=0A
http://www.uniparthenope.it/index.php/5xmille =0A
 =0A
http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille=0A
 =0A
Questa informativa e' inserita in automatico dal sistema al fine esclusivo della realizzazione dei fini istituzionali dell'ente.=0A

------=_NextPart_000_0058_01CE3549.52940480
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-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=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"Preformattato HTML Carattere";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.PreformattatoHTMLCarattere
	{mso-style-name:"Preformattato HTML Carattere";
	mso-style-priority:99;
	mso-style-link:"Preformattato HTML";
	font-family:Consolas;
	color:black;}
span.StileMessaggioDiPostaElettronica19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:217212090;
	mso-list-type:hybrid;
	mso-list-template-ids:308057158 -1513439274 134807555 134807557 =
134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</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 bgcolor=3Dwhite lang=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dear all,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A new version of the Internet Draft on Flow Selection =
Techniques
has been submitted. It contains the following =
changes:<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A new section illustrating the difference between =
Intermediate
Flow Selection Process and Intermediate Selection Process has been =
added,<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The sentence &quot;In order to be compliant with this =
document,
at least the Property =C2=A0Match Filtering MUST be implemented.&quot; =
has been removed
in Section 1,<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=E2=80=9CMUST=E2=80=9D has been replaced with =
=E2=80=9CSHOULD=E2=80=9D in Section 5.1,<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=E2=80=9CThe flowSelectorAlgorithm registry is maintained =
by IANA.&quot;
has been replaced with =E2=80=9CIANA is requested to create the =
flowSelectorAlgorithm
registry.=E2=80=9D<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The sentence &quot;The registry can be updated when
specifications of the new=C2=A0 technique(s) and any new Information =
Elements are
provided.&quot; has been removed since it did not clarify how the =
registry will
be managed.<o:p></o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span
style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=C2=A0Section 6.1.1 =E2=80=9CProperty Match =
Filtering=E2=80=9D has been changed by
adding some text on how Property Match Filtering can be =C2=A0used by an
Intermediate Flow Selection Process in the Metering Process, in the =
=C2=A0Exporting
Process and within an IPFIX Mediator.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Salvatore<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DIT =
style=3D'font-size:10.0pt;font-family:"Segoe UI","sans-serif";
color:windowtext'>Da:</span></b><span lang=3DIT =
style=3D'font-size:10.0pt;
font-family:"Segoe UI","sans-serif";color:windowtext'> Benoit Claise
[mailto:bclaise@cisco.com] <br>
<b>Inviato:</b> luned=C3=AC 8 aprile 2013 15:21<br>
<b>A:</b> draft-ietf-ipfix-flow-selection-tech@tools.ietf.org<br>
<b>Cc:</b> ipfix-chairs@tools.ietf.org<br>
<b>Oggetto:</b> Fwd: Last Call Expired:
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></span></p>=


</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Dear authors,<br>
<br>
The IETF last call has finished.<br>
Can you please update your draft based on the feedback received.<br>
Then I will progress it.<br>
<br>
Regards, Benoit<o:p></o:p></p>

<div>

<p class=3DMsoNormal><br>
<br>
-------- Original Message -------- <o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright =
style=3D'text-align:right'><b>Subject: <o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>Last Call Expired:
  &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>Date: =
<o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>Mon, 01 Apr 2013 00:28:46 -0700<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>From: =
<o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>DraftTracker Mail System <a
  =
href=3D"mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</=
a><o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>To: =
<o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal><a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>, <a
  =
href=3D"mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</=
a>, <a
  =
href=3D"mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft=
-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>CC: =
<o:p></o:p></b></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal><a =
href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a><o:p><=
/o:p></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p>

<pre>Please DO NOT reply to this =
email.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I-D: =
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></pre><pre>=
ID Tracker URL: <a
href=3D"http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-t=
ech/">http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tec=
h/</a><o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>IETF Last Call =
has ended, and the state has been changed =
to<o:p></o:p></pre><pre>Waiting for AD =
Go-Ahead.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o=
:p></pre><pre><o:p>&nbsp;</o:p></pre>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D1 width=3D"100%" noshade style=3D'color:#A0A0A0' =
align=3Dcenter>

</div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Nessun
virus nel messaggio.<br>
Controllato da AVG - <a href=3D"http://www.avg.com">www.avg.com</a><br>
Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di =
rilascio:
07/04/2013<o:p></o:p></p>

</div>


<br>=
<STYLE TYPE=3D"text/css">=0A
=09<!--=0A
=09=09@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }=0A
=09=09P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }=0A
=09=09P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }=0A
=09=09P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }=0A
=09=09P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }=0A
=09=09A:link { color: #0000ff }=0A
=09-->=0A
=09</STYLE>=0A
<!--</HEAD></BODY>-->=0A
<P LANG=3D"it-IT" TEXT=3D"#000000" LINK=3D"#0000ff" DIR=3D"LTR">=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">*******************************************************************************************************</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">IL=0A
MERITO DEGLI STUDENTI&nbsp;VIENE RICONOSCIUTO</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">Il=0A
5 per mille all'Universit&agrave degli Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli studenti=0A
- codice fiscale </FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif"><B>80018240632</B></FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">=0A
</FONT></FONT>=0A
</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/5xmille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/5xmille</U></FONT></FONT></A><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">&nbsp;</FONT></FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</U></FONT></FONT></A></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;<FONT FACE=3D"Arial, sans-serif"><BR>Questa=0A
informativa &egrave inserita in automatico dal sistema al fine esclusivo=0A
della realizzazione dei fini istituzionali dell&#39;ente.</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><BR>=0A
</P>=0A
<!--</BODY>-->=0A
<!--</HTML>-->=0A
<br>=
</body>

</html>

<br>=
<STYLE TYPE=3D"text/css">=0A
=09<!--=0A
=09=09@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }=0A
=09=09P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }=0A
=09=09P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }=0A
=09=09P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }=0A
=09=09P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }=0A
=09=09A:link { color: #0000ff }=0A
=09-->=0A
=09</STYLE>=0A
<!--</HEAD></BODY>-->=0A
<P LANG=3D"it-IT" TEXT=3D"#000000" LINK=3D"#0000ff" DIR=3D"LTR">=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">*******************************************************************************************************</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">IL=0A
MERITO DEGLI STUDENTI&nbsp;VIENE RICONOSCIUTO</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">Il=0A
5 per mille all'Universit&agrave degli Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli studenti=0A
- codice fiscale </FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif"><B>80018240632</B></FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">=0A
</FONT></FONT>=0A
</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/5xmille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/5xmille</U></FONT></FONT></A><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">&nbsp;</FONT></FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</U></FONT></FONT></A></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;<FONT FACE=3D"Arial, sans-serif"><BR>Questa=0A
informativa &egrave inserita in automatico dal sistema al fine esclusivo=0A
della realizzazione dei fini istituzionali dell&#39;ente.</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><BR>=0A
</P>=0A
<!--</BODY>-->=0A
<!--</HTML>-->=0A
<br>=
------=_NextPart_000_0058_01CE3549.52940480--

From moore@network-heretics.com  Tue Apr  9 09:56:38 2013
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 2E15121F9052 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 09:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.74
X-Spam-Level: 
X-Spam-Status: No, score=-1.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7SzwSeyjs-b7 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 09:56:34 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id EDF6321F9022 for <ietf@ietf.org>; Tue,  9 Apr 2013 09:56:31 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7B4CB20D73 for <ietf@ietf.org>; Tue,  9 Apr 2013 12:56:29 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 09 Apr 2013 12:56:29 -0400
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=C/nWE+3AMacUA3QDF/m6kI MdGwc=; b=oKz+VtclO4Qorfj2+grLqkLVumD8XaxJbpnqUlxfuodISptQx+eNlY XmXubNMC7EpceVdGJlTzK+w2zkzupNcYdXaaw2i+tjzkVAXffDVj7DxhzTViVJkY eilTXQO5oRdB4r1x3fMAmGGnbpscRqVHAs/wpIDdKwQRu/cLaWa0g=
X-Sasl-enc: GlO1YVr66kleF1AleIbpa2hmLTYvsQT/GJmSoC6E3Wzl 1365526589
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id EE324C80007; Tue,  9 Apr 2013 12:56:28 -0400 (EDT)
Message-ID: <5164483B.5090907@network-heretics.com>
Date: Tue, 09 Apr 2013 12:56:27 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sufficient email authentication requirements for IPv6
References: <20130329165843.7417.qmail@joyce.lan> <89A2F538-65CD-4E05-9251-40E55C895B95@gmail.com>
In-Reply-To: <89A2F538-65CD-4E05-9251-40E55C895B95@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: Tue, 09 Apr 2013 16:56:38 -0000

On 03/29/2013 01:28 PM, Douglas Otis wrote:
 > The Internet is under a DDoS attack specifically against an email 
address reputation service.

You have it backwards.  Internet email has long been under DDoS attack 
from email address reputation services.

Keith



From doug.mtview@gmail.com  Tue Apr  9 10:19:28 2013
Return-Path: <doug.mtview@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 AA2A621F93BF for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 10:19:28 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2TCAcjnVIMO for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 10:19:28 -0700 (PDT)
Received: from mail-pd0-f174.google.com (mail-pd0-f174.google.com [209.85.192.174]) by ietfa.amsl.com (Postfix) with ESMTP id 08F8F21F93BD for <ietf@ietf.org>; Tue,  9 Apr 2013 10:19:28 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id p12so3858954pdj.33 for <ietf@ietf.org>; Tue, 09 Apr 2013 10:19:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=auvViAzXOm3WylqWIqa5CHyh4QqpZzP5+8rLmXATc00=; b=xv9VdHnlYFmPXJQk8OVntqRr6pdTlWz1DKE3sXBAF4jVsv6SlurSxeQrrU7EnVRhLi AZg5MnxNRr3aj+twvjkQsV12hso/Ys0LjtUaiuhzyRqLvTlcV22dJrF6Z9tTOUt2fxTT zEHEKB1qJ0EcNsOrbnysgboLRBvriDD7P0YG5MCyTSrtqEFDx0c6iU24nueVqVmfQXF5 TYRS9r9gKsyzOcbm9+kqjnWfbualgPljPUW3lfcGSrfduQoV6k055H5SPjQJLZDGYvBa Hk9dLA3ZG+YURH0/3KFoqPorsKl6U8ySt1bT6g7QFayMAhW60Qq8IalvVOz1ZH0nRwEC gLhw==
X-Received: by 10.68.216.70 with SMTP id oo6mr3425503pbc.160.1365527967794; Tue, 09 Apr 2013 10:19:27 -0700 (PDT)
Received: from ?IPv6:2601:9:3180:3e:e4ff:a531:1858:e291? ([2601:9:3180:3e:e4ff:a531:1858:e291]) by mx.google.com with ESMTPS id jw10sm2924883pbb.3.2013.04.09.10.19.25 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Apr 2013 10:19:26 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Sufficient email authentication requirements for IPv6
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <5163A6D6.4040401@bogus.com>
Date: Tue, 9 Apr 2013 10:19:24 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B10091AB-7062-43D4-BFE1-A515499C9B56@gmail.com>
References: <CANB+R+WfeBu49YdsENwkJMZnu7zAHaNGSqOfkcmJOW7X5TOg9A@mail.gmail.com> <5154C9E0.7060408@isdg.net> <357617C8-766E-4CCF-A733-E032103211E1@gmail.com> <C91E67751B1EFF41B857DE2FE1F68ABA0BFF8A84@tk5ex14mbxc272.redmond.corp.microsoft.com> <5157F29F.30805@dougbarton.us> <AD75DF4E-7A7E-408B-B372-E876411CDBF4@gmail.com> <5163A6D6.4040401@bogus.com>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1503)
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, 09 Apr 2013 17:19:28 -0000

On Apr 8, 2013, at 10:27 PM, joel jaeggli <joelja@bogus.com> wrote:

> On 4/8/13 9:18 PM, Douglas Otis wrote:
>>=20
>> On Mar 31, 2013, at 1:23 AM, Doug Barton <dougb@dougbarton.us =
<mailto:dougb@dougbarton.us>> wrote:
>>=20
>>> On 03/30/2013 11:26 PM, Christian Huitema wrote:
>>>>> IPv6 makes publishing IP address reputations impractical.  Since =
IP address reputation has been a primary method for identifying abusive =
sources with IPv4, imposing ineffective and flaky > replacement =
strategies has an effect of deterring IPv6 use.
>>>>=20
>>>> In practice, the /64 prefix of the IPv6 address has very much the =
same "administrative" properties as the /32 value of the IPv4 address. =
It should be fairly straightforward to update a reputation system to =
manage the /64 prefixes of IPv6. This seems somewhat more practical than =
trying to change the behavior of mail agent if their connectivity =
happens to use IPv6.
>>>=20
>>> That only works insofar as the provider does not follow the standard =
recommendation to issue a /48. If they do, the abuser has 65k /64s to =
operate in.
>>>=20
>>> What's needed is a little more intelligence about how the networks =
which the IPv6 addresses are located are structured. Similar to the way =
that reputation lists nowadays will black list a whole /24 if 1 or a few =
addresses within it send spam.
>>>=20
>>> The problems are not insoluble, they're just different, and arguably =
more complex in v6. It's also likely that in the end more work on =
reputation lists will provide less benefit than it did in the v4 world. =
But that's the world we live in now.
>>=20
>> Dear Doug,
>>=20
>> Why aggregate into groups of 64k prefixes?  After all, this still =
does not offer a practical way to ascertain a granularity that isolates =
different entities at /64 or /48.  It is not possible to ascertain these =
boundaries even at a single prefix.  There is 37k BGP entries offering =
IPv6 connectivity.  Why not hold each announcement accountable and make =
consolidated reputation a problem ISPs must handle?  Of course, such an =
approach would carry an inordinate level of support and litigation costs =
due to inadvertent collateral blocking.  Such consolidation would be as =
impractical as would an arbitrary consolidation at /48.
>>=20
> Plently of people use IP to ASN mappings as part of their input for =
reputation today.

Dear Joel,

Unfortunately, ISPs are bad at responding to email abuse complaints.  =
There are exceptions where reputation needs to be escalated to the ASN, =
as was the case in Brazil which then involved litigation.  You're =
welcome, but operations at that level will not scale and might lead to =
balkanization.

With respect to IPv6 granularity, there is only ~7k ASNs.  As IPv6 =
adoption increases, this should approach 37k.  In addition, there are =
more /32 prefixes than /48.  Each /32 represents a span greater than the =
entire IPv4 Internet.  The network covered by each prefix represents an =
address span IPv4 squared in size.  The sparse nature of abuse and the =
size of IPv6 prefix space makes collecting evidence and distributing =
detected abuse by IP address or prefix both expensive and slow, where =
any IP address query mechanism is likely to result in self inflicted =
DDoS.=20

If email offered authentication of the sourcing domain or that of a =
domain certificate, then reputation could be fairly applied and easily =
distributed. This ability is essential for IPv6.

Regards,
Douglas Otis


From peter@akayla.com  Tue Apr  9 11:57:55 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00B9F21F960D; Tue,  9 Apr 2013 11:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jUJ8k1c9zHHE; Tue,  9 Apr 2013 11:57:54 -0700 (PDT)
Received: from p3plsmtpa11-08.prod.phx3.secureserver.net (p3plsmtpa11-08.prod.phx3.secureserver.net [68.178.252.109]) by ietfa.amsl.com (Postfix) with ESMTP id 4919421F95EB; Tue,  9 Apr 2013 11:57:54 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa11-08.prod.phx3.secureserver.net with  id Muxo1l00C1huGat01uxo6e; Tue, 09 Apr 2013 11:57:50 -0700
From: "Peter Yee" <peter@akayla.com>
To: <mohamed.boucadair@orange.com>, <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr>
Subject: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Date: Tue, 9 Apr 2013 11:57:50 -0700
Message-ID: <059701ce3554$235aa0b0$6a0fe210$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGru2VgIxcOQENUYzhlyQVOZ0pm1wHHP5CkmQTyuIA=
Content-Language: en-us
Cc: gen-art@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, 09 Apr 2013 18:57:55 -0000

Med,
	Thanks for the swift response to my review.  See my one reply
inline.

		Kind regards,
		-Peter

>>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP 
>>error other than a short-lifetime error, or in the case of a failed 
>>resend, any PCP error at all.  The wording makes it seem like the 
>>short-lifetime errors are somehow not PCP errors and is therefore 
>>confusing.  It also doesn't explicitly deal with how many repeats should
be done on a resend.

>[Med] The basic behavior is to relay the received error to the UPnP CP. For
the short-lifetime errors, the IWF may decide to resend the request and not
relay those errors immediately to the UPnP CP. The number of repeats is not
specified here as it can be implementation-specific. 

Your explanation is fine.  I just found the wording "If a PCP  error
response is received" to sound ambiguously as if the short-lifetime errors
were not a subset of PCP errors.



From sm@resistor.net  Tue Apr  9 11:58:48 2013
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 5FBAA21F9767 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 11:58:47 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rU7+-R2v3POd for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 11:58:46 -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 82EF721F9764 for <ietf@ietf.org>; Tue,  9 Apr 2013 11:58:46 -0700 (PDT)
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 r39IwfYF014412; Tue, 9 Apr 2013 11:58:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365533925; bh=vIqweEAOoNDkLr6LWQ9fZXeFnvKJ0vKT5VRr5Fd8+XA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=knyL8AdbHW0us6PLWzKfHbRXYDLzc2bbuDbiFGrtHIg4FLhLeUW+Upr+2ngTgjzQx j+vtYrd4jvhUHvs93nLd1i5q32gXD6cBekNi6cXnyQEnqe6JyVxb6OJfBo/77RH5AF QRhoH0yTt+sRE9lPa+wwYHKLFRYSHq5Z2S4q4vXs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365533925; i=@resistor.net; bh=vIqweEAOoNDkLr6LWQ9fZXeFnvKJ0vKT5VRr5Fd8+XA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Cg3ad2IHQOLX+syTzCVYxbNfqiw7m79AByO9DQRXFOTBad50ja9xTy1meNuD55H// fNOfAJmWrNa/9TXAZugvhse5bijFFgr1sp88oYdypKrnNM0NqjYHVtewUtnoAqdFNc FE44STKmMYpcsGEqz7H48ZdZcj+FHVqgsZDVDCFo=
Message-Id: <6.2.5.6.2.20130409105430.0ca71108@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 09 Apr 2013 11:28:53 -0700
To: Keith Moore <moore@network-heretics.com>
From: SM <sm@resistor.net>
Subject: Re: Sufficient email authentication requirements for IPv6
In-Reply-To: <5164483B.5090907@network-heretics.com>
References: <20130329165843.7417.qmail@joyce.lan> <89A2F538-65CD-4E05-9251-40E55C895B95@gmail.com> <5164483B.5090907@network-heretics.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, 09 Apr 2013 18:58:48 -0000

Hi Keith,
At 09:56 09-04-2013, Keith Moore wrote:
>You have it backwards.  Internet email has long been under DDoS 
>attack from email address reputation services.

Quoting Nathaniel Borenstein  [1]:

   "One man's blacklist is another's denial-of-service attack."

Email reputation services have a bad reputation.  In some respect it 
is similar to the email delivery problem where the smaller set of 
good people are negatively affected because of the larger set of "bad" people.

Regards,
-sm

P.S. You are the only participant who has been able to override the 
existing consensus during a Last Call. :-)

1. http://www.ietf.org/mail-archive/web/ietf/current/msg29826.html 


From doug.mtview@gmail.com  Tue Apr  9 12:22:28 2013
Return-Path: <doug.mtview@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 8644C21F9354 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 12:22:28 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fxM3I2SBiwk7 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 12:22:28 -0700 (PDT)
Received: from mail-pd0-f179.google.com (mail-pd0-f179.google.com [209.85.192.179]) by ietfa.amsl.com (Postfix) with ESMTP id 13AF221F942D for <ietf@ietf.org>; Tue,  9 Apr 2013 12:22:28 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id x11so3903211pdj.10 for <ietf@ietf.org>; Tue, 09 Apr 2013 12:22:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=mVoQMaROEDqDI8DnoFI6pK9s/3hISUhqBzL+g2aA5kE=; b=p7Y9aQ2fLI8VUBiGLXjlLo24jB1IsFYIWyE4ina62NZJmjo+7Dj4x8MMIDKZbZIQOa 9FM0nBjjeARSi+Q1SElgJa4ekQlkIR4c9NMFlPUgT1MU69IAoo5HR4Mz+hhZUmeCiVQ6 j2VZbyAkyTBhBWor78AVzo0GBIBmiNC22LMOKSG2G5WQYVxoE312rQUYkc+HSATSgh5U 8cyigg9ecvz/7FedWU+EPxw5irrXf6z0BcOkZlw1fc8yChWBHODG2hhkQ51o5khpFY5D ElifGpJfyEjuhf3wWLxrHQLJu17AwaqvE8JLahJPmjQX7pfe2u8zZFdWyFiME8dXL3h/ PR9Q==
X-Received: by 10.66.154.33 with SMTP id vl1mr45619395pab.60.1365535347915; Tue, 09 Apr 2013 12:22:27 -0700 (PDT)
Received: from dhcp186.priv.bungi.com (c-24-4-157-244.hsd1.ca.comcast.net. [24.4.157.244]) by mx.google.com with ESMTPS id ya4sm3250508pbb.24.2013.04.09.12.22.25 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Apr 2013 12:22:26 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Sufficient email authentication requirements for IPv6
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <6.2.5.6.2.20130409105430.0ca71108@resistor.net>
Date: Tue, 9 Apr 2013 12:22:25 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <18993D0C-AB02-4FC1-9B86-4D822B86E760@gmail.com>
References: <20130329165843.7417.qmail@joyce.lan> <89A2F538-65CD-4E05-9251-40E55C895B95@gmail.com> <5164483B.5090907@network-heretics.com> <6.2.5.6.2.20130409105430.0ca71108@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1503)
Cc: Keith Moore <moore@network-heretics.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: Tue, 09 Apr 2013 19:22:28 -0000

On Apr 9, 2013, at 11:28 AM, SM <sm@resistor.net> wrote:

> Hi Keith,
> At 09:56 09-04-2013, Keith Moore wrote:
>> You have it backwards.  Internet email has long been under DDoS =
attack from email address reputation services.
>=20
> Quoting Nathaniel Borenstein  [1]:
>=20
>  "One man's blacklist is another's denial-of-service attack."
>=20
> Email reputation services have a bad reputation.  In some respect it =
is similar to the email delivery problem where the smaller set of good =
people are negatively affected because of the larger set of "bad" =
people.
>=20
> Regards,
> -sm
>=20
> P.S. You are the only participant who has been able to override the =
existing consensus during a Last Call. :-)
>=20
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg29826.html=20

Dear SM,

In full agreement with Nathaniel.  Avoiding unfair collateral blocking =
is why source domain authentication, not authorization, is vital.

Regards,
Douglas Otis


From d3e3e3@gmail.com  Tue Apr  9 14:42:01 2013
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 6997D21F9760 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 14:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.7
X-Spam-Level: 
X-Spam-Status: No, score=-101.7 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_28=0.6, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gijzfr5fSbC6 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 14:42:00 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id D498121F83EF for <ietf@ietf.org>; Tue,  9 Apr 2013 14:42:00 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id er7so7295420obc.7 for <ietf@ietf.org>; Tue, 09 Apr 2013 14:42:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=7txMMvu9FaeL2JdbATxvnZPx4/N1x/KWM0kFHfywQxc=; b=Ta+aFSkjCFZ2ozwRUP7tyMFmtSZRpuqjbTe51nhkM5lICexgRbCJznH7u4scV9/7vw Hkmz54fZ9bIA1Syou4Gkk4gAUg2evn/2Qp9rhN1TK8LZBxNtw7lZL6Y2qF/X9WbyoOh3 USJb5K3dbyCAdNz62jOk5FHCxcGcdejfFh5Tn7EvJp7V+Kqa4ApzXaCHXa3rcjoailpH RBiKjc6s2qx/DzQSMLjLgFg2VIdjZfL0SkBKPEzhqGznzgn49im4e+owlWDeWz/KoEWh zWyjhtOFHgaz4AvIUxLwoZBz85iyexGEHjKrn/hdc3V3GFpphOT/8laSUzeuWNKSRvsf MsKQ==
X-Received: by 10.182.204.68 with SMTP id kw4mr19589230obc.5.1365543720447; Tue, 09 Apr 2013 14:42:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.10.8 with HTTP; Tue, 9 Apr 2013 14:41:40 -0700 (PDT)
In-Reply-To: <20130408072128.GC1162@besserwisser.org>
References: <20130407151508.75879.qmail@joyce.lan> <5161DE0C.8060207@isdg.net> <20130408072128.GC1162@besserwisser.org>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 9 Apr 2013 17:41:40 -0400
Message-ID: <CAF4+nEE+QsKM6sLKog8Q8LuRdAL_HP49FwE5qNvRdt1XXdLq5w@mail.gmail.com>
Subject: Re: Proposed solution for DPEP (Diversity Problem Entry Point) - IETF April 1 jokes.
To: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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: Tue, 09 Apr 2013 21:42:01 -0000

The theory that all April 1 dates RFCs are simply jokes and nothing
else is also easily refuted. Consider RFC 3092. It is an April 1st RFC
produced through that process and has certainly produced some
chuckles. Yet I've lost count of the number of emails I've gotten over
the years from non-English speakers thanking me for the RFC and saying
it was helpful to them...

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 Mon, Apr 8, 2013 at 3:21 AM, M=E5ns Nilsson <mansaxel@besserwisser.org> =
wrote:
> Subject: Proposed solution  for DPEP (Diversity Problem Entry Point) - IE=
TF April 1 jokes. Date: Sun, Apr 07, 2013 at 04:58:52PM -0400 Quoting Hecto=
r Santos (hsantos@isdg.net):
>> This is one of those DPEP (Diversity Problem Entry Point) arising
>> from globalization, April 1 HRC (Humor Recognition Culture)
>> differences,  IETF "stalization" and the growth of I-D submissions.
>> I suggest there is a direct correlation among these factors with the
>> end goal efficacy of the submission.  Fortunately, there is a
>> technical solution for this particular DPEP:
>>
>>     if Date is April.1 then
>>          id.filename =3D "joke-"+id.filename.
>>     end if
>
> This solution has all the virtues of carpet-bombing. Mission accomplished
> but cost and collateral damage are improportionally large.  To me, both
> as humour /per se/ and as sorting help when selecting vendors (cf. my
> message in this thread yesterday), the value almost totally lies in the
> subtle play with form and the resulting ambigousness. In other words,
> if we make it possible to determine by simple logic whether a document
> is a pun or dead serious, it is useless.
>
> I am aware that my position as stated above will be possible to interpret
> as excluding. As parent of a child diagnosed with Aspergers syndrome,
> I fully well know the potential consequences of failure to interpret
> social hints.
>
> I believe that
>
> * transient failure to get a joke not is cause for "safing" jokes. The
> failure is part of the process.
>
> * the speed with which  we "unfail" and start to appreciate this art
> form is personal and differs according to our experience, background
> and intellectual skills but that the initial failure is necessary. There
> are subtler ways than policy and procedure to nudge people along when
> they persist in failing.
>
> * the Internet idea of loosely cooperating networks REQUIRES autonomous
> judgement from the people operating the system. Fostering a culture
> where IETF texts are seen as close to faultless holy scripture does
> nothing to encourage skepticism and personal responsibility.
>
> * enough has been said in this that we already are risking the sweet
> uncertainity. Accordingly, I'll try to not communicate further on this,
> and definitely not propose any procedure work.
>
> --
> M=E5ns Nilsson     primary/secondary/besserwisser/machina
> MN-1334-RIPE                             +46 705 989668
> I am deeply CONCERNED and I want something GOOD for BREAKFAST!
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAlFib/gACgkQ02/pMZDM1cVp0wCePKf4nLxF85ZBOACv1itL0G8s
> pDwAoKPsjMy06MZRr2eMHiOegi5vCs/g
> =3DUNMB
> -----END PGP SIGNATURE-----
>

From housley@vigilsec.com  Tue Apr  9 15:36:25 2013
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 E63C421F90BB; Tue,  9 Apr 2013 15:36:25 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eExCO2rGBBNc; Tue,  9 Apr 2013 15:36:24 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id B1E8421F9051; Tue,  9 Apr 2013 15:36:24 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id B50D89A4112; Tue,  9 Apr 2013 18:36:29 -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 KKu1GypQBele; Tue,  9 Apr 2013 18:36:20 -0400 (EDT)
Received: from [192.168.2.100] (pool-173-79-232-68.washdc.fios.verizon.net [173.79.232.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id CC52F9A410F; Tue,  9 Apr 2013 18:36:27 -0400 (EDT)
Subject: Re: Gen-ART review of draft-ietf-savi-threat-scope-07
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293D371CF@MX15A.corp.emc.com>
Date: Tue, 9 Apr 2013 18:36:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <34B1BF5C-9A14-4B86-BA51-9780F2832ACF@vigilsec.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E055F69357F@MX14A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293D371CF@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF Gen-ART <gen-art@ietf.org>, savi@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, 09 Apr 2013 22:36:26 -0000

David:

Thanks for your efforts on this document.  Your first review was in May =
2011, and the document has improved greatly for you continued pushing on =
the concerns.

Russ


On Apr 3, 2013, at 1:04 PM, Black, David wrote:

> The -07 version of this draft resolves all of the issues raised by the =
Gen-ART
> review of the -06 version.  Discussion of the review with the authors =
has
> resulted in a common understanding that there is no need for =
additional text
> on statically allowing all source addresses through all links in a set =
of
> teamed/aggregated links - that's at best "nice to have" for this =
draft, but
> not essential.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Black, David
>> Sent: Monday, March 25, 2013 9:04 PM
>> To: McPherson, Danny; Fred Baker; joel.halpern@ericsson.com; =
gen-art@ietf.org
>> Cc: Jean-Michel Combes; Ted Lemon; savi@ietf.org; Black, David; =
ietf@ietf.org
>> Subject: Gen-ART review of draft-ietf-savi-threat-scope-06
>>=20
>> I have been selected as the General Area Review Team (Gen-ART) =
reviewer
>> for this draft (for background on Gen-ART, please see
>> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>>=20
>> Please wait for direction from your document shepherd or
>> AD before posting a new version of the draft.
>>=20
>> Document: draft-ietf-savi-threat-scope-06
>> Reviewer: David L. Black
>> Review Date: March 27, 2013
>> IESG Telechat Date: (if known)
>>=20
>> Summary: This draft is on the right track, but has open issues, =
described in
>> the review.
>>=20
>> Looking at the original Gen-ART review of the -05 draft and checking =
the diffs
>> between -05 and -06, the issues raised by that review have only been =
partially
>> addressed:
>>=20
>>> There is no discussion of link teaming or aggregation (e.g., via =
LACP); this
>>> may affect source address validation functionality by requiring the =
same
>>> validation checks on all aggregated ports.  An important case to =
discuss
>>> is where the aggregated host links are connected to ports on =
different
>>> switches (e.g., in an active/passive configuration).
>>=20
>> This is partially addressed on 4.1.2 (new section in -06), but only =
in terms
>> of moving validation state when something like LACP reconfigures.  =
This has a
>> couple of shortcomings:
>> a) the alternative of statically  allowing all source addresses =
through all
>> 	teamed/aggregated links (decouples SAVI state from link
>> teaming/aggregation
>> 	state) should also be mentioned, and
>> b) the new text implies that LACP is the only way to cause this =
situation -
>> it's
>> 	not, so LACP should be used as an example.  VRRP is another =
example.
>>=20
>>> (1) Some of the software switch implementations are single instance =
switches
>>> whose implementation is distributed across multiple physical =
servers.  This
>>> results in concerns similar to the link aggregation discussion =
above.
>>=20
>> I don't think this has been addressed, but the notion of =
single-instance
>> switches
>> could be added to the generalization of the new text in 4.1.2.
>>=20
>>> (2) Live migration of virtual machines among physical servers causes
>>> relocation of MAC addresses across switch ports.  A so-called =
"gratuitous
>> ARP"
>>> is often used to inform the network of the MAC address move; =
port-based
>>> source address validation information needs to move in response to =
such
>> ARPs.
>>>=20
>>> (3) MAC address relocation is also used as a failure recovery =
technique; the
>>> surviving hardware element (e.g., host in a cluster) takes over the =
MAC
>>> addresses of the failed hardware; like the previous case, a =
"gratuitous ARP"
>>> is a common means of informing the network that the MAC address has =
moved,
>>> and source address validation information needs to move in response =
to it.
>>>=20
>>> Minor issues:
>>>=20
>>> There doesn't seem to be much discussion of dynamic network =
reconfiguration,
>>> which may change traffic egress points.  VRRP may be a useful =
example to
>>> discuss beyond the typical routing protocol updates to forwarding =
tables.
>>=20
>> A paragraph has been added to 5.2.3 to address all three of the above
>> concerns.
>> I guess that's ok, but I would have liked to see some text pointing =
out that a
>> MAC move can be detected by the switches and used to update SAVI =
state about
>> which port(s) a MAC is accessed through.
>>=20
>> Thanks,
>> --David
>>=20
>>> -----Original Message-----
>>> From: Black, David
>>> Sent: Friday, May 13, 2011 1:03 AM
>>> To: McPherson, Danny; Fred Baker; joel.halpern@ericsson.com; gen-
>> art@ietf.org
>>> Cc: Black, David; Christian Vogt; Jean-Michel Combes; Jari Arkko;
>>> savi@ietf.org
>>> Subject: Gen-ART review of draft-ietf-savi-threat-scope-05
>>>=20
>>> 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>.
>>>=20
>>> Please resolve these comments along with any other Last Call =
comments
>>> you may receive.
>>>=20
>>> Document: draft-ietf-savi-threat-scope-05
>>> Reviewer: David L. Black
>>> Review Date: 12 May 2011
>>> IETF LC End Date: 18 May 2011
>>>=20
>>> Summary: This draft is on the right track, but has open issues, =
described in
>>> the review.
>>>=20
>>> This draft discusses the threats and deployment environment for IP =
source
>>> address validation with particular attention to finer-grain =
validation that
>>> could be used within a network to validate IP addresses closer to =
the
>> sources
>>> of network traffic than ingress to an ISP's network.
>>>=20
>>> Major issues:
>>>=20
>>> There is no discussion of link teaming or aggregation (e.g., via =
LACP); this
>>> may affect source address validation functionality by requiring the =
same
>>> validation checks on all aggregated ports.  An important case to =
discuss
>>> is where the aggregated host links are connected to ports on =
different
>>> switches
>>> (e.g., in an active/passive configuration).
>>>=20
>>> The discussion of multi-instance hosts in section 5.2.3 is =
incomplete
>>> in several important aspects:
>>>=20
>>> (1) Some of the software switch implementations are single instance =
switches
>>> whose implementation is distributed across multiple physical =
servers.  This
>>> results in concerns similar to the link aggregation discussion =
above.
>>>=20
>>> (2) Live migration of virtual machines among physical servers causes
>>> relocation of MAC addresses across switch ports.  A so-called =
"gratuitous
>> ARP"
>>> is often used to inform the network of the MAC address move; =
port-based
>>> source address validation information needs to move in response to =
such
>> ARPs.
>>>=20
>>> (3) MAC address relocation is also used as a failure recovery =
technique; the
>>> surviving hardware element (e.g., host in a cluster) takes over the =
MAC
>>> addresses of the failed hardware; like the previous case, a =
"gratuitous ARP"
>>> is a common means of informing the network that the MAC address has =
moved,
>>> and source address validation information needs to move in response =
to it.
>>>=20
>>> Minor issues:
>>>=20
>>> There doesn't seem to be much discussion of dynamic network =
reconfiguration,
>>> which may change traffic egress points.  VRRP may be a useful =
example to
>>> discuss beyond the typical routing protocol updates to forwarding =
tables.
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> idnits 2.12.11 ran clean.
>>>=20
>>> Thanks,
>>> --David
>>> ----------------------------------------------------
>>> David L. Black, Distinguished Engineer
>>> EMC Corporation, 176 South St., Hopkinton, MA  01748
>>> +1 (508) 293-7953             FAX: +1 (508) 293-7786
>>> david.black@emc.com        Mobile: +1 (978) 394-7754
>>> ----------------------------------------------------
>>>=20
>=20


From johnl@iecc.com  Tue Apr  9 17:07:37 2013
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 2EE9521F984E for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 17:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.899
X-Spam-Level: 
X-Spam-Status: No, score=-110.899 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tF0WMckNdIMv for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 17:07:36 -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 5A24721F9888 for <ietf@ietf.org>; Tue,  9 Apr 2013 17:07:33 -0700 (PDT)
Received: (qmail 48042 invoked from network); 10 Apr 2013 00:07:32 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 10 Apr 2013 00:07:32 -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; s=5164ad43.xn--9vv.k1304; i=johnl@user.iecc.com; bh=YtUXZP84VMzhUNyIeufxEna/RocZCgXPRTrJhF0FTIc=; b=eX3zTYeYndmAlUBamJSN/6Uzs4Gsg4gzKIdnTk5NcBkqiu8OqeIi9pY9HyRgg8RjGtZV6C+WCEvxHIpEnNulNlaqsQZSC1+rKnVVCqJuxhRrMfNLOUMn4a0CAVE6y0VbgsCCWKd0MKMV17O0218lBKqE5Dyob7DF+NXcBd8JrOY=
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; s=5164ad43.xn--9vv.k1304; olt=johnl@user.iecc.com; bh=YtUXZP84VMzhUNyIeufxEna/RocZCgXPRTrJhF0FTIc=; b=BGafcQmBDuilIW5WbK8A8dLWBqFwqi6yIjr6DfQCakWWTZxOwK22t1RX+ePnSqxninPE+6cbCq//3WxJ9hlN8+8JAiJDzTIgzklizQoxkvjlcW3BszIg95WgTZ3qTka8PH331ARzIBZTlufsI7b5sJo52CkYgvZ97wjwca7Tluo=
Date: 10 Apr 2013 00:07:09 -0000
Message-ID: <20130410000709.70385.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Sufficient email authentication requirements for IPv6
In-Reply-To: <6.2.5.6.2.20130409105430.0ca71108@resistor.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: sm@resistor.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, 10 Apr 2013 00:07:37 -0000

>Quoting Nathaniel Borenstein  [1]:
>
>   "One man's blacklist is another's denial-of-service attack."
>
>Email reputation services have a bad reputation.

They have a good enough reputation that every non-trivial mail system
in the world uses them.  They're not all the same, and a Darwinian
process has caused the best run ones to be the most widely used.

There seems to be a faction that feel that 15 years ago someone once
blacklisted them and caused them some inconvenience, therefore all
DNSBLs suck forever.  I could say similar things about buggy PC
implementations of TCP/IP, but I think a few things have changed since
then, in both cases.

R's,
John

From Ted.Lemon@nominum.com  Tue Apr  9 17:30:02 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C65A521F98CE; Tue,  9 Apr 2013 17:30:02 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmy5Pn66JXMQ; Tue,  9 Apr 2013 17:30:02 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 1592521F98A4; Tue,  9 Apr 2013 17:30:01 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUWSyiQyJGuHL2v8H7olDkAUw+VBzTHxz@postini.com; Tue, 09 Apr 2013 17:30:02 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7423B1B87B0; Tue,  9 Apr 2013 17:30:01 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6B970190061; Tue,  9 Apr 2013 17:30:01 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 9 Apr 2013 17:30:01 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Gen-ART review of draft-ietf-savi-threat-scope-07
Thread-Topic: Gen-ART review of draft-ietf-savi-threat-scope-07
Thread-Index: AQHOMI1VsmvJehwUjES862bjgyecEJjO+YyAgAAfwwA=
Date: Wed, 10 Apr 2013 00:30:01 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077513B7E4@mbx-01.win.nominum.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E055F69357F@MX14A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293AEEDC8@MX15A.corp.emc.com> <8D3D17ACE214DC429325B2B98F3AE71293D371CF@MX15A.corp.emc.com> <34B1BF5C-9A14-4B86-BA51-9780F2832ACF@vigilsec.com>
In-Reply-To: <34B1BF5C-9A14-4B86-BA51-9780F2832ACF@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D734FF2B9DAEB9469441AB80801ACC46@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Black, David" <david.black@emc.com>, "<savi@ietf.org>" <savi@ietf.org>, IETF Gen-ART <gen-art@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: Wed, 10 Apr 2013 00:30:02 -0000

On Apr 9, 2013, at 6:36 PM, Russ Housley <housley@vigilsec.com> wrote:
> Thanks for your efforts on this document.  Your first review was in May 2=
011, and the document has improved greatly for you continued pushing on the=
 concerns.

Can we take this to mean that the concerns expressed in your now-deprecated=
 DISCUSS have been successfully addressed?


From fgont@si6networks.com  Tue Apr  9 22:21:36 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09BCF21F93BF; Tue,  9 Apr 2013 22:21:36 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ONZepnlA06K9; Tue,  9 Apr 2013 22:21:35 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 4653221F93BD; Tue,  9 Apr 2013 22:21:35 -0700 (PDT)
Received: from 26-174-16-190.fibertel.com.ar ([190.16.174.26] helo=[192.168.1.113]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UPnSm-0004Hk-Ve; Wed, 10 Apr 2013 07:21:31 +0200
Message-ID: <5164F5F3.9030007@si6networks.com>
Date: Wed, 10 Apr 2013 02:17:39 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [OPSEC] Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <51559943.1010703@gmail.com> <515985E1.1000404@si6networks.com> <515AA8B4.5020707@gmail.com>
In-Reply-To: <515AA8B4.5020707@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: opsec@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, 10 Apr 2013 05:21:36 -0000

Hi, Brian,

My apologies for the delay in my response. Please find my comments
in-line...


On 04/02/2013 06:45 AM, Brian E Carpenter wrote:
> Fernando,
> 
> Rather than repeating myself, I'll suggest a change to the Introduction
> that would (IMHO) improve the message:
> 
> OLD:
> 
> 1.  Introduction
> 
>    Most general-purpose operating systems implement and enable native
>    IPv6 [RFC2460] support and a number of transition/co-existence
>    technologies by default.  For cases in which the corresponding
>    devices are deployed on networks that are assumed to be IPv4-only,
> 
> NEW:
> 
> 1.  Introduction
> 
>    Most general-purpose operating systems implement and enable native
>    IPv6 [RFC2460] support and a number of transition/co-existence
>    technologies by default [RFC6434]. Support of IPv6 by all nodes is
>    intended to become best current practice [RFC6540]. As a result,
>    networks will need to plan for and deploy IPv6 and its security
>    mechanisms. Some enterprise networks might, however, choose to delay
>    active use of IPv6. For networks that are assumed to be IPv4-only,

I've checked with a few folks, and it seems that the suggested text
would make everyone happy, except for the sentence that says "As a
result, networks will need to plan for and deploy IPv6 and its security
mechanisms.", on the basis that this is not the document to make a case
for v6 deployment. The suggestions has been to remove that sentence, and
apply the rest of your proposed text (or, alternatively, to tone down
that sentence).

For simplicity sake (and because I'm not sure how one would tone that
one down), my suggestion would be to apply you proposed text, modulo
that sentence.

Would that be okay with you? -- If not, please do let me know, so that
we can try to find a way forward that keeps everyone happy.

Thanks so much!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From sm@resistor.net  Tue Apr  9 22:41:16 2013
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 2A2EF21F9413 for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 22:41:16 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0r4nOmS1Kkle for <ietf@ietfa.amsl.com>; Tue,  9 Apr 2013 22:41:15 -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 8031621F93B6 for <ietf@ietf.org>; Tue,  9 Apr 2013 22:41:15 -0700 (PDT)
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 r3A5f51d023836; Tue, 9 Apr 2013 22:41:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365572470; bh=DZwfEDZ490UaawuosKJ8Vj4Z86cGJuRbReZM0dpYPlE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OvBgb9MIV03VV4QS7BQ2HcQgJBIWG6lA6qQPG9VGxpRPFGhRxrMcTFhyFJau2YYBL s+S/nNed5jOYCRBn3OAGj8oQRMItctti00DzcSfa9IahrNVzZxrbwWG4ofVwteX87Z eOvO3gkF8toecUFu7nqYVGC36BEtmCpMmrWLyzso=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365572470; i=@resistor.net; bh=DZwfEDZ490UaawuosKJ8Vj4Z86cGJuRbReZM0dpYPlE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xs3nImWuqwJAM3Swn9AsB5/ePMO4oFCQXOfO53FLB4MtowO4sMDF51UnKfIk4K+ny /MRzhNlt7aRJ22ePmPgvsrKaDl8xBTG5dvJVG9UZy6RaMbvAWNQG3px+1KbPCl5m/j KWjD+QPyqwP/5Sjr9e+uM1w3UByHdoCrdM7fS5Ek=
Message-Id: <6.2.5.6.2.20130409212535.0cd853e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 09 Apr 2013 22:12:06 -0700
To: Douglas Otis <doug.mtview@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Sufficient email authentication requirements for IPv6
In-Reply-To: <18993D0C-AB02-4FC1-9B86-4D822B86E760@gmail.com>
References: <20130329165843.7417.qmail@joyce.lan> <89A2F538-65CD-4E05-9251-40E55C895B95@gmail.com> <5164483B.5090907@network-heretics.com> <6.2.5.6.2.20130409105430.0ca71108@resistor.net> <18993D0C-AB02-4FC1-9B86-4D822B86E760@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: Wed, 10 Apr 2013 05:41:16 -0000

Hi Doug,
At 12:22 09-04-2013, Douglas Otis wrote:
>In full agreement with Nathaniel.  Avoiding unfair collateral 
>blocking is why source domain authentication, not authorization, is vital.

I doubt that what's mentioned in the subject line will not face 
strong resistance within an IETF context.  However, as it seems 
important I suggest submitting the proposal as an Internet-Draft and 
getting IETF participants to support for the proposal.  I suggest 
taking the discussion at 
http://www.ietf.org/mail-archive/web/asrg/current/msg16672.html into account.

Regards,
-sm 


From stefan@aaa-sec.com  Wed Apr 10 02:03:21 2013
Return-Path: <stefan@aaa-sec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41F2D21F8F0C for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 02:03:21 -0700 (PDT)
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.650, BAYES_00=-2.599, HELO_EQ_SE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aTMzoF9YPhj for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 02:03:20 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by ietfa.amsl.com (Postfix) with ESMTP id 9919421F9075 for <ietf@ietf.org>; Wed, 10 Apr 2013 02:03:20 -0700 (PDT)
Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id A68AE203FBBC for <ietf@ietf.org>; Wed, 10 Apr 2013 11:03:19 +0200 (CEST)
X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se
Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id e_ORweLDBvXY for <ietf@ietf.org>; Wed, 10 Apr 2013 11:03:16 +0200 (CEST)
Received: from s327.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id 86E83203FBDB for <ietf@ietf.org>; Wed, 10 Apr 2013 11:02:53 +0200 (CEST)
Received: (qmail 83046 invoked from network); 10 Apr 2013 09:02:47 -0000
Received: from gw.aaa-sec.ideon.se (HELO [192.168.1.201]) (stefan@fiddler.nu@[85.235.7.89]) (envelope-sender <stefan@aaa-sec.com>) by s327.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <hotz@jpl.nasa.gov>; 10 Apr 2013 09:02:47 -0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Wed, 10 Apr 2013 11:02:44 +0100
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
From: Stefan Santesson <stefan@aaa-sec.com>
To: "Henry B. Hotz" <hotz@jpl.nasa.gov>, Sean Turner <turners@ieca.com>
Message-ID: <CD8AF5C0.603DB%stefan@aaa-sec.com>
Thread-Topic: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
In-Reply-To: <34EC8B90-9952-4B8E-BFC2-7913F198453F@jpl.nasa.gov>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: pkix@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, 10 Apr 2013 09:03:21 -0000

Nothing has changed in this regard.

The good response is pretty clear that it by default provides information
that the cert is not on a black-list (is not know to be revoked).
However, it is also made clear that extensions may be used to expand this
default information about the status.

This is how it always have been, and still is in RFC 256bis.

The revoked response simply means that the certificate is revoked.
Combined with the new extension, it MAY also be used for non-issued certs.

It's really as simple as that.

It is only the discussion on this list that is confusing and that has
managed turn something really simple into a complicated debate.

/Stefan


On 4/8/13 9:35 PM, "Henry B. Hotz" <hotz@jpl.nasa.gov> wrote:

>Actually, what I get from this and all the other discussions is that it's
>unclear if the updated OCSP satisfies the "suitability for the intended
>purpose" test.  Or at least it fails the KISS principle w.r.t. that.
>
>Rephrasing:  an OCSP client should be able to tell from an OCSP response
>if:  a) the subject cert is on the CAs white list, b) the subject cert is
>on the CAs black list, c) the subject cert is not on either list, or
>finally d) the OCSP server is obsolete, and doesn't support making those
>distinctions.  It's not trivial to see how to parse 2560bis responses
>w.r.t. those cases, therefore it's highly likely that computational
>complexity will prevent us from doing so.  Even if that's not actually
>the case, then implementor misunderstandings will prevent us from doing
>so in practice.
>
>Therefore I vote against moving this draft forward.  I just don't see the
>point.
>
>If someone were to write an informational RFC which explained how to
>determine which of the 4 cases an OCSP response fell into, AND if said
>RFC also convinced me that the decision process was easy to understand,
>THEN I would change my vote.  Obviously an appendix in 2560bis would
>serve just as well.
>_______________________________________________
>pkix mailing list
>pkix@ietf.org
>https://www.ietf.org/mailman/listinfo/pkix



From acooper@cdt.org  Wed Apr 10 05:22:09 2013
Return-Path: <acooper@cdt.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 C7BF221F8EE1 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 05:22:08 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oPnk3Vlihwyp for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 05:22:08 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 33ACB21F8A4E for <ietf@ietf.org>; Wed, 10 Apr 2013 05:22:07 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Wed, 10 Apr 2013 08:21:53 -0400
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <5141D8E3.4000605@dcrocker.net>
Date: Wed, 10 Apr 2013 14:21:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB682B03-F1E3-487D-B56D-7BDBEC4EAA78@cdt.org>
References: <5141D8E3.4000605@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1499)
Cc: IAB IAB <iab@iab.org>, draft-iab-privacy-considerations.all@tools.ietf.org, 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: Wed, 10 Apr 2013 12:22:09 -0000

Hi Dave,

Thanks for your review. Some comments are inline. A pre-publication -08 =
version is available at =
<http://www.alissacooper.com/files/draft-iab-privacy-considerations-08.txt=
>. The diff from the -07 is available at <https://www.cdt.org/Z4Q>.=20

On Mar 14, 2013, at 10:04 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> Apologies for my sending this after the deadline.  I hope the comments =
are still usable...
>=20
>=20
>=20
> Review of:    Privacy Considerations for Internet Protocols
>=20
> I-D:          draft-iab-privacy-considerations-07.txt
>=20
> Reviewed by:  D. Crocker
>=20
> Review date:  14 March 2013
>=20
>=20
> Summary:
>=20
>   The document provides a broad introduction to the needs, nature and =
details of adding privacy considerations to IETF specifications. =
Broadly, it is divided into introduction, terminology, generic =
exposure/analysis model, threats, mitigations, and analysis guidelines.  =
The document is generally well-organized and written clearly.  An =
example analysis is provided that concretely demonstrates the approach =
to doing a considerations analysis; it was intentionally chosen as a =
difficult case, with inherent tradeoffs between privacy and required =
functionality.
>=20
>   As an introduction to the topic, the document is accessible and =
practical.
>=20
>   A glaring deficiency of the document is its conscious choice to =
refrain from defining the term 'privacy'.  The choice is understandable, =
a given long, messy and varying real-world history with term. However =
the reader is left with having to formulate their own -- possibly =
unvoiced and therefore entirely ambiguous -- working definition.  For =
doing the technical worked needed in a specification, this simply does =
not give the reader the linchpin to the topic, needed to anchor their =
understanding in a way that will be consistent across authors and =
readers of specifications.  The draft needs to choose a definition, in =
spite of the fact that other groups, people and contexts will use other =
definitions.  We do specifications and this starts with definitions.  It =
simply makes no sense to be missing a definition for the key word.
>=20
> By way of priming that pump, I'll proffer the simplest definition that =
seems plausible here:
>=20
>     Privacy is the concern for protecting information
>     of or about an individual person.
>=20
> Tweak this or replace it entirely, but /please/ provide a concrete, =
pragmatic definition that explicitly defines what is in scope and what =
is out, for them to focus their considerations on.

This suggestion has been debated at length within the IAB privacy =
program over the life of this document. Our thinking is that trying to =
define "privacy" in one sentence would be as counterproductive as trying =
to define "security" or "extensibility" in one sentence. All of those =
concepts are rich and nuanced enough to have entire documents dedicated =
to explaining them as concepts and exploring how those concepts should =
be tackled in the IETF. That is the purpose of this document. Given the =
extent to which we outline all the different facets of privacy threats, =
the feeling is that it would undercut the value of the document to boil =
privacy down to one sentence. What we want readers to do is take in the =
nuance and not think of privacy as one box they can simply tick off =
during the design process.

>=20
> Also, given the challenges of this topic and the desire to get useful =
privacy considerations into IETF work, I suggest creating a privacy =
directorate, which can be asked to assist authors and review their work. =
 Think of it as a topic-specific mentoring group=85

This has been tried before and did not work out so well =
<http://www.ietf.org/mail-archive/web/privacydir/current/maillist.html>, =
but there is some talk of trying again.

>=20
> Except for the requirement to define its motivating term, the draft is =
usable in its current form, although a number of specific improvements =
cited in the detailed comments are recommended.

Great!

>=20
>=20
>=20
> Detailed Comments:
>=20
> The following comments are left raw, written as I read the draft...
>=20
>=20
>> Abstract
>>=20
>>   This document offers guidance for developing privacy considerations
>>   for inclusion in protocol specifications.  It aims to make protocol
>>   designers aware of privacy-related design choices.  It suggests =
that
>>   whether any individual RFC warrants a specific privacy =
considerations
>>   section will depend on the document's content.
>=20
> Given the degree of ambiguity in the word 'privacy' -- since there is =
such a wide range of definitions people assign it, as noted in the =
second paragraph of the Introduction -- the Abstract needs to provide a =
summary of its definition here, so that the reader can understand the =
focus and scope of the term's use in this document.  The definitional =
text needs to refrain from using the word 'privacy' as part of the =
definition=85

Per my comment above, it is probably better to avoid stating this as =
concisely as would be necessary in the abstract.

>=20
>=20
>> 1. Introduction
>>=20
>>=20
>>   [RFC3552] provides detailed guidance to protocol designers about =
both
>>   how to consider security as part of protocol design and how to =
inform
>>   readers of protocol specifications about security issues.  This
>>   document intends to provide a similar set of guidance for =
considering
>>   privacy in protocol design.
>>=20
>>   Privacy is a complicated concept with a rich history that spans =
many
>>   disciplines.  With regard to data, often it is a concept applied to
>=20
> "With regard to data" implies that it could be with regard to =
something else.  What?

Peeping toms, for example. In many circles a distinction is made between =
"data protection" and "privacy," which can comprise aspects of personal =
intrusion that are not associated with stored or transmitted data.

>=20
>=20
>>   "personal data," information relating to an identified or
>>   identifiable individual.  Many sets of privacy principles and =
privacy
>>   design frameworks have been developed in different forums over the
>>   years.  These include the Fair Information Practices [FIPs], a
>>   baseline set of privacy protections pertaining to the collection =
and
>>   use of personal data (often based on the principles established in
>>   [OECD], for example), and the Privacy by Design concept, which
>>   provides high-level privacy guidance for systems design (see [PbD]
>>   for one example).  The guidance provided in this document is =
inspired
>>   by this prior work, but it aims to be more concrete, pointing
>>   protocol designers to specific engineering choices that can impact
>>   the privacy of the individuals that make use of Internet protocols.
>>=20
>>   Different people have radically different conceptions of what =
privacy
>>   means, both in general, and as it relates to them personally
>>   [Westin].  Furthermore, privacy as a legal concept is understood
>>   differently in different jurisdictions.  The guidance provided in
>>   this document is generic and can be used to inform the design of =
any
>>   protocol to be used anywhere in the world, without reference to
>>   specific legal frameworks.
>>=20
>>   Whether any individual document warrants a specific privacy
>>   considerations section will depend on the document's content.
>>   Documents whose entire focus is privacy may not merit a separate
>=20
> OK.  Enough is enough.  It's fine to have a quick survey of earlier =
work, but that's not sufficient.
>=20
> You keep using the word privacy, and I don't know what you mean.
>=20
> The typical writer and reader of RFCs is not experienced in the topic =
of privacy.  They won't know what you mean either:  they need very =
concrete guidance about the word's meaning.
>=20
> Telling me that different people mean different things with the term =
merely assures me that I have no idea what /you/ mean unless you tell =
me.  Having each reader make guesses about the meaning is a way to =
ensure non-interoperability of the construct.

Per my note above, the expectation is that the document as a whole will =
provide a rich explanation of what is meant by privacy. Of course, some =
people won't read the whole document, or even parts of it, but others =
will, and hopefully more so over time.

>=20
> Guidance can't be very helpful if the reader has no idea when to apply =
it.

If the reader is unsure about whether to go through the thought process =
outlined in section 7, there is no harm (other than the use of the =
reader's time) in doing it and then finding out that a particular =
specification is already solidly designed when it comes to privacy.

>=20
>=20
>>   section (for example, "Private Extensions to the Session Initiation
>>   Protocol (SIP) for Asserted Identity within Trusted Networks"
>>   [RFC3325]).  For certain specifications, privacy considerations are =
a
>>   subset of security considerations and can be discussed explicitly =
in
>=20
> I strongly suggest that any explicit privacy discussion be required to =
be an entirely separate from the 'security considerations' section.
>=20
> My reasoning is simple:  This community sees 'security' in terms of =
encryption and signing, traffic analysis, and other such mechanical, =
relatively low-level components.  Privacy is an entirely different and =
broader and more human beast, even when its details devolve to these =
familiar mechanics.
>=20
> At the least, making it a separate section will help writers and =
readers to distinguish privacy from the security stuff we are used to =
seeing discussed.

I think sections 4 and 7 demonstrate that privacy and security are =
interrelated at least in some respects.=20

There are two motivations for suggesting that privacy can be =
incorporated into security considerations in some cases. First, in a way =
we are trying to key off of the familiarity that people already have =
with security, and asking them to expand their security thinking a bit =
might be an easier sell than making a whole new/separate requirement. =
Second, it is a means to avoid duplication. It already happens that when =
authors insert a separate privacy considerations section it ends up =
making a bunch of references to the security considerations section. We =
don't want to recommend a document structure that will just end up =
seeming extraneous.

>=20
>=20
>>   the security considerations section.  Some documents will not =
require
>>   discussion of privacy considerations (for example, "Definition of =
the
>>   Opus Audio Codec" [RFC6716]).  The guidance provided here can and
>>   should be used to assess the privacy considerations of protocol,
>>   architectural, and operational specifications and to decide whether
>>   those considerations are to be documented in a stand-alone section,
>>   within the security considerations section, or throughout the
>>   document.
>=20
> Not sure whether this is a question or a suggestion; if it's the =
latter, I'm not sure what to suggest:  privacy issues often develop as a =
combinatorial problem -- 'correlation' as you note farther down -- that =
is, developing out of unpredicted integration of information from =
discrete services.  While any specific IETF specification might have its =
own, direct privacy issues needing consideration, where should =
discussion of these combinatorial dangers be discussed?

That is a good question and I'm not sure I know the answer. Of course =
there is nothing to prevent people from writing drafts about the privacy =
considerations associated with the combination of discrete =
services/protocols.=20

>=20
>=20
>> 2. Terminology
>>=20
>>=20
>>   This section defines basic terms used in this document, with
>>   references to pre-existing definitions as appropriate.  As in
>>   [RFC4949], each entry is preceded by a dollar sign ($) and a space
>>   for automated searching.  Note that this document does not try to
>>   attempt to define the term 'privacy' itself.  Instead privacy is =
the
>>   sum of what is contained in this document.  We therefore follow the
>>   approach taken by [RFC3552].
>=20
> Sorry.  Not workable, if you want meaningful consideration by authors =
and meaningful understanding by readers.

See above.

>=20
>=20
>>=20
>> 2.1. Entities
>>=20
>>=20
>>   Several of these terms are further elaborated in Section 3.
>>=20
>>   $ Attacker:   An entity that intentionally works against some =
privacy
>>      protection goal.  Unlike observers, attackers' behavior is
>>      unauthorized.
>=20
> This precludes accidental privacy violations?

Fixed.

>=20
>=20
>>=20
>>   $ Eavesdropper:   A type of attacker that passively observes an
>>      initiator's communications without the initiator's knowledge or
>>      authorization.  See [RFC4949].
>>=20
>>   $ Enabler:   A protocol entity that facilitates communication =
between
>>      an initiator and a recipient without being directly in the
>>      communications path.
>=20
> For example=85?

This is elaborated in section 3.

>=20
>=20
>> 2.3. Identifiability
> ...
>=20
>>   $ Personal Name:   A natural name for an individual.  Personal =
names
>>      are often not unique, and often comprise given names in
>>      combination with a family name.  An individual may have multiple
>>      personal names at any time and over a lifetime, including =
official
>>      names.  =46rom a technological perspective, it cannot always be
>>      determined whether a given reference to an individual is, or is
>>      based upon, the individual's personal name(s) (see Pseudonym).
>=20
> Official Names also are typically not unique.

Added a note to this affect.

>=20
>=20
>>   $ Pseudonym:   A name assumed by an individual in some context,
>>      unrelated to the individual's personal names known by others in
>>      that context, with an intent of not revealing the individual's
>>      identities associated with her other names.
>=20
> (Might be worth mentioning that this is sometimes called "persona".)
>=20
> Pseudonyms also often are not unique.
>=20
> My point is that it's good that you mentioned this issue and should =
repeat it for each term to which it applies.

Fixed.

>=20
>=20
>> 3. Communications Model
>>=20
>>=20
>>   To understand attacks in the privacy-harm sense, it is helpful to
>>   consider the overall communication architecture and different =
actors'
>>   roles within it.  Consider a protocol entity, the "initiator," that
>>   initiates communication with some recipient.  Privacy analysis is
>>   most relevant for protocols with use cases in which the initiator
>>   acts on behalf of an individual (or different individuals at
>>   different times).  It is this individual whose privacy is =
potentially
>>   threatened.
>=20
> If I receive a credit dunning notice or a legal notification, I'm the =
recipient, but unauthorized disclosure of such messages would be =
privacy-harm for me.  It isn't just initiator-side individuals.

Fixed.

>=20
>=20
>>=20
>>   Communications may be direct between the initiator and the =
recipient,
>>   or they may involve an application-layer intermediary (such as a
>>   proxy or cache) that is necessary for the two parties to =
communicate.
>=20
> proxy or cache -> proxy, cache or (mail) relay

Fixed.

>=20
>=20
>>   In some cases this intermediary stays in the communication path for
>>   the entire duration of the communication and sometimes it is only
>>   used for communication establishment, for either inbound or =
outbound
>>   communication.  In rare cases there may be a series of =
intermediaries
>=20
> For email, it isn't rare at all.  In fact, it's universal, probably =
for literally every email sent.

Fixed.

>=20
>=20
>>   that are traversed.  At lower layers, additional entities are
>>   involved in packet forwarding that may interfere with privacy
>>   protection goals as well.
> ...
>=20
>>   Protocol design is often predicated on the notion that recipients,
>>   intermediaries, and enablers are assumed to be authorized to =
receive
>>   and handle data from initiators.  As [RFC3552] explains, "we assume
>>   that the end-systems engaging in a protocol exchange have not
>>=20
>>=20
>>=20
>> Cooper, et al.           Expires August 27, 2013               [Page =
10]
>>=20
>>=20
>> Internet-Draft           Privacy Considerations            February =
2013
>>=20
>>=20
>>   themselves been compromised."  However, by its nature privacy
>=20
> which nature?
>=20
> seriously, how is the reader to know (or even guess) what exactly is =
being implied?

Fixed.

>=20
>=20
>>   analysis requires questioning this assumption since systems are =
often
>>   compromised for the purpose of obtaining personal data.
>>=20
>>   Although recipients, intermediaries, and enablers may not generally
>>   be considered as attackers, they may all pose privacy threats
>>   (depending on the context) because they are able to observe, =
collect,
>=20
> exactly!
>=20
>=20
>=20
>> 4. Privacy Threats
> ...
>=20
>>   This section lists common privacy threats (drawing liberally from
>>   [Solove], as well as [CoE]), showing how each of them may cause
>>   individuals to incur privacy harms and providing examples of how
>>   these threats can exist on the Internet.
>>=20
>>   Some privacy threats are already considered in IETF protocols as a
>=20
> cite some examples.

These are explained throughout section 4. This is just the introductory =
text to the section.

>=20
>=20
>>   matter of routine security analysis.  Others are more pure privacy
>=20
> What does it mean to be a "more pure privacy threat"?  Really, I can't =
guess.

Same as above -- this is explained throughout section 4.

>=20
>=20
>>   threats that existing security considerations do not usually =
address.
>>   The threats described here are divided into those that may also be
>>   considered security threats and those that are primarily privacy
>>   threats.
>>=20
>>   Note that an individual's awareness of and consent to the practices
>>   described below may change an individual's perception of and =
concern
>>   for the extent to which they threaten privacy.  If an individual
>>   authorizes surveillance of his own activities, for example, the
>>   individual may be able to take actions to mitigate the harms
>>   associated with it, or may consider the risk of harm to be =
tolerable.
>>=20
>> 4.1. Combined Security-Privacy Threats
>=20
> The fact that you have a string like "Combined Security-Privacy" =
supports the view that Privacy Considerations is distinct from Security =
and should not be in the Security Considerations section=85

Actually I think it's the opposite. Section 4 makes concrete =
distinctions between privacy threats that are already commonly covered =
by security considerations and those that are not.

>=20
>=20
>=20
>> 4.1.4. Misattribution
>>=20
>>=20
>>   Misattribution occurs when data or communications related to one
>>   individual are attributed to another.  Misattribution can result in
>>   adverse reputational, financial, or other consequences for
>>   individuals that are misidentified.
>=20
> It's probably worth mentioning that for spam, this is often called =
"spoofing".

Fixed.

>=20
>=20
>=20
>> 5.1. Data Minimization
>>=20
> ...
>=20
>>   However, the most direct application of data minimization to =
protocol
>>   design is limiting identifiability.  Reducing the identifiability =
of
>>   data by using pseudonyms or no identifiers at all helps to weaken =
the
>>   link between an individual and his or her communications.  Allowing
>>   for the periodic creation of new identifiers reduces the =
possibility
>=20
> also randomization of chosen identifiers

Fixed.

>=20
>=20
>=20
>> 5.2. User Participation
>>=20
>>=20
>>   As explained in Section 4.2.5, data collection and use that happens
>>   "in secret," without the individual's knowledge, is apt to violate
>>   the individual's expectation of privacy and may create incentives =
for
>>   misuse of data.  As a result, privacy regimes tend to include
>>   provisions to require informing individuals about data collection =
and
>>   use and involving them in decisions about the treatment of their
>>   data.  In an engineering context, supporting the goal of user
>>   participation usually means providing ways for users to control the
>>   data that is shared about them.  It may also mean providing ways =
for
>>   users to signal how they expect their data to be used and shared.
>=20
> There is a serious downside to this.  It presumes that this burden on =
users is reasonable.  For many scenarios, it isn't.  Rather, the focus =
on user participation is often used as an alternative to the difficult =
work (or research) on mechanisms that require less user participation.

I agree that sole reliance on user participation is undesirable. It's =
listed here as one of several protections, so sole reliance is not =
implied. For protocol design I would actually argue that we tend not to =
think about user participation enough (whereas I agree that privacy =
policy tends to focus on it too much).

>=20
>=20
>=20
>=20
>> 6. Scope of Privacy Implications of Internet Protocols
>>=20
>>=20
>>   Internet protocols are often built flexibly, making them useful in =
a
>>   variety of architectures, contexts, and deployment scenarios =
without
>>   requiring significant interdependency between disparately designed
>>   components.  Although protocol designers often have a particular
>>   target architecture or set of architectures in mind at design time,
>>   it is not uncommon for architectural frameworks to develop later,
>>   after implementations exist and have been deployed in combination
>>   with other protocols or components to form complete systems.
>=20
> Independent of the purpose of this draft, the above paragraph is quite =
a nice bit of text about an aspect of IETF technical work.

Thanks.

>=20
>=20
>>   As a consequence, the extent to which protocol designers can =
foresee
>>   all of the privacy implications of a particular protocol at design
>>   time is limited.  An individual protocol may be relatively benign =
on
>>   its own, and it may make use of privacy and security features at
>>   lower layers of the protocol stack (Internet Protocol Security,
>>   Transport Layer Security, and so forth) to mitigate the risk of
>>   attack.  But when deployed within a larger system or used in a way
>>   not envisioned at design time, its use may create new privacy =
risks.
>>   Protocols are often implemented and deployed long after design time
>>   by different people than those who did the protocol design.  The
>>   guidelines in Section 7 ask protocol designers to consider how =
their
>>   protocols are expected to interact with systems and information =
that
>>   exist outside the protocol bounds, but not to imagine every =
possible
>>   deployment scenario.
>>=20
>>   Furthermore, in many cases the privacy properties of a system are
>>   dependent upon the complete system design where various protocols =
are
>>   combined together to form a product solution; the implementation,
>>   which includes the user interface design; and operational =
deployment
>>   practices, including default privacy settings and security =
processes
>>   within the company doing the deployment.  These details are =
specific
>>   to particular instantiations and generally outside the scope of the
>>   work conducted in the IETF.  The guidance provided here may be =
useful
>>   in making choices about these details, but its primary aim is to
>>   assist with the design, implementation, and operation of protocols.
>=20
> Perhaps the largest challenge I repeatedly see in the IETF is what I =
call "systems thinking", which is considering an integrated set of =
components and their interactions.  The above three paragraphs very =
nicely target exactly that scope of concern, in the context of privacy.
>=20
> So I /strongly/ suggest you move the three paragraphs up to the =
Introduction.  Note that this would largely resolve the concern I raised =
there, that the Introduction really doesn't introduce cross-component =
(multi-specification) scoping issues for privacy.  Add a citation in it =
to this section.

This section has been moved to directly after the introduction.

>=20
>=20
>>   Transparency of data collection and use -- often effectuated =
through
>>   user interface design -- is normally a key factor in determining =
the
>=20
> I realize that's a common view, but has it been validated or is it =
merely the default perspective that user permission solves everything?

Good point. I've added some text to indicate that this is what often =
happens, whether rightly or wrongly.

>=20
>=20
>>   privacy impact of a system.  Although most IETF activities do not
>>   involve standardizing user interfaces or user-facing =
communications,
>>   in some cases understanding expected user interactions can be
>>   important for protocol design.  Unexpected user behavior may have =
an
>>   adverse impact on security and/or privacy.
>=20
> While a generically reasonable view, the challenge with its =
application in the IETF is our general tendency to think that we =
understand UI and UX issues, although few in the IETF actually have the =
background for it.  For example we tend to think that simply giving =
users more information is a universal palliative.  Most discussions here =
about "expected user interactions" are simply wrong.  Worse, I've no =
idea what to suggest to counter this for the draft.

Yeah, I'm not sure the draft can fix this problem. But agree that it's a =
problem.

>=20
>=20
>> 7. Guidelines
>>=20
>>=20
>>   This section provides guidance for document authors in the form of =
a
>>   questionnaire about a protocol being designed.  The questionnaire =
may
>>   be useful at any point in the design process, particularly after
>>   document authors have developed a high-level protocol model as
>>   described in [RFC4101].
>>=20
>>   Note that the guidance does not recommend specific practices.  The
>>   range of protocols developed in the IETF is too broad to make
>>   recommendations about particular uses of data or how privacy might =
be
>>   balanced against other design goals.  However, by carefully
>>   considering the answers to each question, document authors should =
be
>>   able to produce a comprehensive analysis that can serve as the =
basis
>>   for discussion of whether the protocol adequately protects against
>>   privacy threats.
>=20
> For some years after Security Considerations were made mandatory, =
authors mostly floundered with the topic, given their/our lack of =
background for assessing security considerations.  Eventually there was =
IETF focus on making the section useful.
>=20
> While this draft goes a long way to making the nature and requirements =
of a Privacy Considerations section substantive, it's going to be some =
time before the community develops helpful skills at writing these =
sections.
>=20

Agree.

> I suggest setting up a Privacy Directorate, essentially as a =
consulting/review service for authors to use in developing their text =
for the section in their documents.  The Directorate might also take =
initiative at reviewing new documents.

Perhaps this can be resurrected.

>=20
>=20
>>   The framework is divided into four sections that address each of =
the
>>   mitigation classes from Section 5, plus a general section.  =
Security
>>   is not fully elaborated since substantial guidance already exists =
in
>>   [RFC3552].
>>=20
>> 7.1. Data Minimization
>>=20
>>=20
>>      a.  Identifiers.  What identifiers does the protocol use for
>>      distinguishing initiators of communications?  Does the protocol
>>      use identifiers that allow different protocol interactions to be
>>      correlated?  What identifiers could be omitted or be made less
>>      identifying while still fulfilling the protocol's goals?
>=20
> I'd think that retention of recipient identifiers might also be an =
issue?

This is covered in 7.1g.

>=20
>=20
>>      b.  Data.  What information does the protocol expose about
>>      individuals, their devices, and/or their device usage (other =
than
>>      the identifiers discussed in (a))?  To what extent is this
>>      information linked to the identities of the individuals?  How =
does
>>      the protocol combine personal data with the identifiers =
discussed
>>      in (a)?
>>=20
>>      c.  Observers.  Which information discussed in (a) and (b) is
>>      exposed to each other protocol entity (i.e., recipients,
>>      intermediaries, and enablers)?  Are there ways for protocol
>>      implementers to choose to limit the information shared with each
>>      entity?  Are there operational controls available to limit the
>>      information shared with each entity?
>>=20
>>      d.  Fingerprinting.  In many cases the specific ordering and/or
>>      occurrences of information elements in a protocol allow users,
>>      devices, or software using the protocol to be fingerprinted.  Is
>>      this protocol vulnerable to fingerprinting?  If so, how?  Can it
>>=20
>>=20
>>=20
>> Cooper, et al.           Expires August 27, 2013               [Page =
25]
>>=20
>>=20
>> Internet-Draft           Privacy Considerations            February =
2013
>>=20
>>=20
>>      be designed to reduce or eliminate the vulnerability?  If not, =
why
>>      not?
>>=20
>>      e.  Persistence of identifiers.  What assumptions are made in =
the
>>      protocol design about the lifetime of the identifiers discussed =
in
>>      (a)?  Does the protocol allow implementers or users to delete or
>>      replace identifiers?  How often does the specification recommend
>>      to delete or replace identifiers by default?  Can the =
identifiers,
>>      along with other state information, be set to automatically
>>      expire?
>>=20
>>      f.  Correlation.  Does the protocol allow for correlation of
>>      identifiers?  Are there expected ways that information exposed =
by
>=20
> Is it productive to also look for 'unexpected' ways?  This could be a =
silly and wasteful exercise, or thinking creatively about strange =
combinations might trigger better insight.  I've no direct experience, =
so can't judge.

I think eventually that might be something we want to load onto protocol =
designers, but at this point even just scoping this to expected ways =
would be helpful IMO.

>=20
>=20
>> 8. Example
> ...
>=20
>>   The fundamental architecture defined in RFC 2778 and RFC 3859 is a
>>   mediated one.  Clients (presentities in RFC 2778 terms) publish =
their
>>   presence information to presence servers, which in turn distribute
>>   information to authorized watchers.  Presence servers thus retain
>>   presence information for an interval of time, until it either =
changes
>>   or expires, so that it can be revealed to authorized watchers upon
>>   request.  This architecture mirrors existing pre-standard =
deployment
>>   models.  The integration of an explicit authorization mechanism =
into
>>   the presence architecture has been widely successful in involving =
the
>>   end users in the decision making process before sharing =
information.
>>   Nearly all presence systems deployed today provide such a =
mechanism,
>>   typically through a reciprocal authorization system by which a pair
>>   of users, when they agree to be "buddies," consent to divulge their
>>   presence information to one another.  Buddylists are managed by
>>   servers but controlled by end users.  Users can also explicitly =
block
>>   one another through a similar interface, and in some deployments it
>>   is desirable to provide "polite blocking" of various kinds.
>=20
> As the discussion moves into the details of analyzing each type of =
privacy concern, I suggest making the format be bulleted and/or tabular. =
 This will make each segment of analysis more accessible to the reader =
and easier to correlate with the lists of privacy concerns/attributes =
provided earlier in the document.  It will also aid scanning for review =
and later consultation.

The goal of this section was to review how privacy decisions were made =
within the confines of one example architecture. In the IAB privacy =
program we plan to try to apply the guidance in more formal write-ups in =
the manner you suggest to some other existing protocols/architectures =
(likely selected from the reviews we've already done: =
<http://www.iab.org/activities/programs/privacy-program/privacy-reviews/>)=
.=20

>=20
>=20
>>   =46rom a perspective of privacy design, however, the classical =
presence
>>   architecture represents nearly a worst-case scenario.  In terms of
>>=20
>>=20
>>=20
>> Cooper, et al.           Expires August 27, 2013               [Page =
28]
>>=20
>>=20
>> Internet-Draft           Privacy Considerations            February =
2013
>>=20
>>=20
>>   data minimization, presentities share their sensitive information
>>   with presence services, and while services only share this presence
>>   information with watchers authorized by the user, no technical
>>   mechanism constrains those watchers from relaying presence to =
further
>=20
> Offhand, I don't know what mechanisms are practical to impose such a =
constraint, in a protocol specification.  It would help to see an =
example.

I don't think the implication is that they exist.

>=20
>=20
>>   third parties.  Any of these entities could conceivably log or =
retain
>>   presence information indefinitely.  The sensitivity cannot be
>>   mitigated by rendering the user anonymous, as it is indeed the
>>   purpose of the system to facilitate communications between users =
who
>>   know one another.  The identifiers employed by users are long-lived
>>   and often contain personal information, including personal names =
and
>>   the domains of service providers.  While users do participate in =
the
>>   construction of buddylists and blacklists, they do so with little
>>   prospect for accountability: the user effectively throws their
>>   presence information over the wall to a presence server that in =
turn
>>   distributes the information to watchers.  Users typically have no =
way
>>   to verify that presence is being distributed only to authorized
>>   watchers, especially as it is the server that authenticates =
watchers,
>>   not the end user.  Connections between the server and all =
publishers
>>   and consumers of presence data are moreover an attractive target =
for
>>   eavesdroppers, and require strong confidentiality mechanisms, =
though
>>   again the end user has no way to verify what mechanisms are in =
place
>>   between the presence server and a watcher.
>=20
> Again, what would be realistic choices for fixing this?  (It's =
possible that there aren't any and that privacy considerations would =
merely need to document an inherent and unfixable exposure.  In terms of =
guidance to writers of privacy considerations, that's ok, but it's worth =
making this point clear.)

Per the above, this was meant to provide a review of how the =
architecture was conceived of at the time it was designed.

>=20
> ...
>=20
>>   Privacy concerns about presence information largely arise due to =
the
>>   built-in mediation of the presence architecture.  The need for a
>>   presence server is motivated by two primary design requirements of
>>   presence: in the first place, the server can respond with an
>>   "offline" indication when the user is not online; in the second
>>   place, the server can compose presence information published by
>>   different devices under the user's control.  Additionally, to
>>=20
>>=20
>>=20
>> Cooper, et al.           Expires August 27, 2013               [Page =
29]
>>=20
>>=20
>> Internet-Draft           Privacy Considerations            February =
2013
>>=20
>>=20
>>   preserve the use of URIs as identifiers for entities, some service
>=20
> "preserve"?

Fixed.

>=20
>=20
>>   must operate a host with the domain name appearing in a presence =
URI,
>>   and in practical terms no commercial presence architecture would
>>   force end users to own and operate their own domain names.  Many =
end
>>   users of applications like presence are behind NATs or firewalls, =
and
>>   effectively cannot receive direct connections from the Internet - =
the
>>   persistent bidirectional channel these clients open and maintain =
with
>>   a presence server is essential to the operation of the protocol.
>=20
> So?  I'm not understanding what makes this a privacy issue.
>=20

This is explaining why the mediated model was chosen.

>=20
>>   One must first ask if the trade-off of mediation for presence is
>>   worth it.  Does a server need to be in the middle of all =
publications
>=20
>   worth it -> worthwhile.

Fixed.

>=20
>=20
>>   of presence information?  It might seem that end-to-end encryption =
of
>>   the presence information could solve many of these problems.  A
>=20
> Not as described:  You'd still have mediation.  That is, the solution =
you offer does not answer the question you ask.
>=20
> I think you mean to ask whether the intermediary needs to see all =
presence information in the clear.  If you really intend to suggest that =
an intermediary isn't needed, then you need to describe a scenario =
without one.

I think mediation is understood broadly here -- not as the question of =
whether an intermediary exists, but whether it actually mediates all =
aspects of the interaction.

>=20
>=20
>>   presentity could encrypt the presence information with the public =
key
>>   of a watcher, and only then send the presence information through =
the
>>   server.  The IETF defined an object format for presence information
>>   called the Presence Information Data Format (PIDF), which for the
>>   purposes of conveying location information was extended to the PIDF
>>   Location Object (PIDF-LO) - these XML objects were designed to
>>   accommodate an encrypted wrapper.  Encrypting this data would have
>>   the added benefit of preventing stored cleartext presence =
information
>>   from being seized by an attacker who manages to compromise a =
presence
>>   server.  This proposal, however, quickly runs into usability
>>   problems.  Discovering the public keys of watchers is the first
>>   difficulty, one that few Internet protocols have addressed
>>   successfully.  This solution would then require the presentity to
>>   publish one encrypted copy of its presence information per =
authorized
>>   watcher to the presence service, regardless of whether or not a
>>   watcher is actively seeking presence information - for a presentity
>>   with many watchers, this may place an unacceptable burden on the
>>   presence server, especially given the dynamism of presence
>>   information.  Finally, it prevents the server from composing =
presence
>>   information reported by multiple devices under the same user's
>>   control.  On the whole, these difficulties render object encryption
>>   of presence information a doubtful prospect.
>>=20
>>   Some protocols that provide presence information, such as SIP, can
>=20
> hmmm.  I didn't think that SIP, itself, provided presence =
information...?  SIMPLE uses SIP, but it isn't SIP doing the presence =
work.

Fixed.

>=20
>=20
>>   operate intermediaries in a redirecting mode, rather than a
>>   publishing or proxying mode.  Instead of sending presence =
information
>>   through the server, in other words, these protocols can merely
>>   redirect watchers to the presentity, and then presence information
>>   could pass directly and securely from the presentity to the =
watcher.
>>   It is worth noting that this would disclose the IP address of the
>>   presentity to the watcher, which has its own set of risks.  In that
>>   case, the presentity can decide exactly what information it would
>>   like to share with the watcher in question, it can authenticate the
>>   watcher itself with whatever strength of credential it chooses, and
>>   with end-to-end encryption it can reduce the likelihood of any
>>=20
>>=20
>>=20
>> Cooper, et al.           Expires August 27, 2013               [Page =
30]
>>=20
>>=20
>> Internet-Draft           Privacy Considerations            February =
2013
>>=20
>>=20
>>   eavesdropping.  In a redirection architecture, a presence server
>>   could still provide the necessary "offline" indication, without
>>   requiring the presence server to observe and forward all =
information
>>   itself.  This mechanism is more promising than encryption, but also
>>   suffers from significant difficulties.  It too does not provide for
>>   composition of presence information from multiple devices - it in
>>   fact forces the watcher to perform this composition itself.  The
>>   largest single impediment to this approach is however the =
difficulty
>>   of creating end-to-end connections between the presentity's =
device(s)
>>   and a watcher, as some or all of these endpoints may be behind NATs
>>   or firewalls that prevent peer-to-peer connections.  While there =
are
>>   potential solutions for this problem, like STUN and TURN, they add
>>   complexity to the overall system.
>=20
> Given the pragmatics, I'm surprised you'd call this 'promising'.

It's phrased relatively.

>=20
>=20
>>=20
>>   Consequently, mediation is a difficult feature of the presence
>>   architecture to remove, and due especially to the requirement for
>>   composition it is hard to minimize the data shared with
>>   intermediaries.  Control over sharing with intermediaries must
>>   therefore come from some other explicit component of the
>>   architecture.  As such, the presence work in the IETF focused on
>>   improving the user participation over the activities of the =
presence
>>   server.  This work began in the GEOPRIV working group, with =
controls
>>   on location privacy, as location of users is perceived as having
>>   especially sensitive properties.  With the aim to meet the privacy
>>   requirements defined in [RFC2779] a set of usage indications, such =
as
>>   whether retransmission is allowed or when the retention period
>>   expires, have been added to PIDF-LO that always travel with =
location
>>   information itself.  These privacy preferences apply not only to =
the
>>   intermediaries that store and forward presence information, but =
also
>>   to the watchers who consume it.
>>=20
>>   This approach very much follows the spirit of Creative Commons =
[CC],
>>   namely the usage of a limited number of conditions (such as 'Share
>>   Alike' [CC-SA]).  Unlike Creative Commons, the GEOPRIV working =
group
>>   did not, however, initiate work to produce legal language nor to
>>   design graphical icons since this would fall outside the scope of =
the
>=20
> hmmm.  This raises a possible issue with finding and liaising with =
other groups relevant to privacy and with complementary skills.  So, for =
example, here's a case of needing work to aid privacy that was =
identified but needed to be handed off to another group.
>=20
> Lining up such contacts ahead of time could be a useful bit of work =
for a privacy directorate?

Perhaps, it would depend on the nature of the use cases envisioned for =
the particular privacy preference expressions being built into =
protocols.

Thanks,
Alissa

>=20
>=20
>=20
> d/
>=20
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>=20



From moore@network-heretics.com  Wed Apr 10 06:26:49 2013
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 2039C21F9058 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 06:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=0.930,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fshpA0ABB0J6 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 06:26:48 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 65B5F21F8F62 for <ietf@ietf.org>; Wed, 10 Apr 2013 06:26:48 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1ED2F20A06 for <ietf@ietf.org>; Wed, 10 Apr 2013 09:26:47 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Wed, 10 Apr 2013 09:26:47 -0400
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=VlMOzw7WPsQZtY0Fk4WKWW i3k4Y=; b=kR4by4ZXKfWTSUNQj/1zQHRCjfzWmzYZjoK6Wb2Pv+qz6Nam1rQiC1 W34+qPV5l0dF60H3M8xuc/dpPwzGSbXG8iKyQNgGilY10H0W7BSxrccjRHNOMHsc EgqQBjV/n15POE6o7bNRIt50oQN50EABphqN5t+TCjR7LmKr/mutI=
X-Sasl-enc: zu3NlcW07gHv37lVFE8YWbYGyvcNrw+SUzV4FdLa0YsO 1365600406
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 88F4E200101; Wed, 10 Apr 2013 09:26:46 -0400 (EDT)
Message-ID: <51656892.2090907@network-heretics.com>
Date: Wed, 10 Apr 2013 09:26:42 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sufficient email authentication requirements for IPv6
References: <20130410000709.70385.qmail@joyce.lan>
In-Reply-To: <20130410000709.70385.qmail@joyce.lan>
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: Wed, 10 Apr 2013 13:26:49 -0000

On 04/09/2013 08:07 PM, John Levine wrote:
>> Quoting Nathaniel Borenstein  [1]:
>>
>>    "One man's blacklist is another's denial-of-service attack."
>>
>> Email reputation services have a bad reputation.
> They have a good enough reputation that every non-trivial mail system
> in the world uses them.  They're not all the same, and a Darwinian
> process has caused the best run ones to be the most widely used.
>
> There seems to be a faction that feel that 15 years ago someone once
> blacklisted them and caused them some inconvenience, therefore all
> DNSBLs suck forever.  I could say similar things about buggy PC
> implementations of TCP/IP, but I think a few things have changed since
> then, in both cases.

There's an inherent problem with letting 3rd parties affect email 
traffic, especially when there's no way to hold those 3rd parties 
accountable for negligence or malice.

Keith


From mohamed.boucadair@orange.com  Tue Apr  9 23:53:05 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9445721F8972; Tue,  9 Apr 2013 23:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LgSO57z68hJ8; Tue,  9 Apr 2013 23:53:05 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id BC0E321F8470; Tue,  9 Apr 2013 23:53:04 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id ED2BA2DC35A; Wed, 10 Apr 2013 08:53:03 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id CF75D23808A; Wed, 10 Apr 2013 08:53:03 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Wed, 10 Apr 2013 08:53:03 +0200
From: <mohamed.boucadair@orange.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-intarea-nat-reveal-analysis.all@tools.ietf.org" <draft-ietf-intarea-nat-reveal-analysis.all@tools.ietf.org>
Date: Wed, 10 Apr 2013 08:53:02 +0200
Subject: RE: Gen-ART review of draft-ietf-intarea-nat-reveal-analysis-06
Thread-Topic: Gen-ART review of draft-ietf-intarea-nat-reveal-analysis-06
Thread-Index: Ac4yVqRs/Mt47fa6QWSvsgPU2PDQHwDYPtrg
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC1AE7905@PUEXCB1B.nanterre.francetelecom.fr>
References: <030101ce3259$2b900520$82b00f60$@akayla.com>
In-Reply-To: <030101ce3259$2b900520$82b00f60$@akayla.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.10.60351
X-Mailman-Approved-At: Wed, 10 Apr 2013 08:12:52 -0700
Cc: "gen-art@ietf.org" <gen-art@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: Wed, 10 Apr 2013 06:53:05 -0000

RGVhciBQZXRlciwNCg0KVGhlIHR3byBPTEQgbml0cyBhcmUgYWxyZWFkeSBmaXhlZCBpbiBteSBs
b2NhbCBjb3B5Lg0KDQpBcyBmb3IgdGhlIG5ldyBvbmUsIEknbSBnZW5lcmF0aW5nIHRoZSByZWZl
cmVuY2VzIGF1dG9tYXRpY2FsbHkuIFRoZSBSRkMgRWRpdG9yIGNhbiBmaXggdGhpcyBpZiBuZWVk
ZWQuDQoNClRoYW5rcy4NCg0KQ2hlZXJzLA0KTWVkDQoNCj4tLS0tLU1lc3NhZ2UgZCdvcmlnaW5l
LS0tLS0NCj5EZcKgOiBQZXRlciBZZWUgW21haWx0bzpwZXRlckBha2F5bGEuY29tXQ0KPkVudm95
w6nCoDogc2FtZWRpIDYgYXZyaWwgMjAxMyAwMTo1Ng0KPsOAwqA6IGRyYWZ0LWlldGYtaW50YXJl
YS1uYXQtcmV2ZWFsLWFuYWx5c2lzLmFsbEB0b29scy5pZXRmLm9yZw0KPkNjwqA6IGdlbi1hcnRA
aWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj5PYmpldMKgOiBHZW4tQVJUIHJldmlldyBvZiBkcmFm
dC1pZXRmLWludGFyZWEtbmF0LXJldmVhbC1hbmFseXNpcy0wNg0KPg0KPkkgYW0gdGhlIGFzc2ln
bmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIEZvciBiYWNrZ3JvdW5kIG9uIEdl
bi0NCj5BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPjxodHRwOi8vd2lraS50b29scy5pZXRm
Lm9yZy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0ZmFxPg0KPg0KPlBsZWFzZSB3YWl0IGZvciBk
aXJlY3Rpb24gZnJvbSB5b3VyIGRvY3VtZW50IHNoZXBoZXJkIG9yIEFEIGJlZm9yZSBwb3N0aW5n
DQo+YSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQo+DQo+RG9jdW1lbnQ6IGRyYWZ0LWlldGYt
aW50YXJlYS1uYXQtcmV2ZWFsLWFuYWx5c2lzLTA2DQo+UmV2aWV3ZXI6IFBldGVyIFllZQ0KPlJl
dmlldyBEYXRlOiBBcHItNS0yMDEzDQo+SUVURiBMQyBFbmQgRGF0ZTogTWFyLTgtMjAxMw0KPklF
U0cgVGVsZWNoYXQgZGF0ZTogQXByLTExLTIwMTMNCj4NCj5UaGlzIGRyYWZ0IGlzIGJhc2ljYWxs
eSByZWFkeSBmb3IgcHVibGljYXRpb24sIGJ1dCBoYXMgbml0cyB0aGF0IHNob3VsZCBiZQ0KPmZp
eGVkIGJlZm9yZSBwdWJsaWNhdGlvbi4gW1JlYWR5IHdpdGggbml0c10NCj4NCj5JdCBhZGRyZXNz
ZXMgbW9zdCBvZiB0aGUgaXNzdWVzIHJhaXNlZCBpbiBteSByZXZpZXcgb2YgdGhlIC0wNSB2ZXJz
aW9uLg0KPlR3byBpdGVtcyBmcm9tIHRoYXQgcmV2aWV3IHRoYXQgSSdtDQo+cmV2aXNpdGluZyBh
cmUgbm90ZWQgYmVsb3cgd2l0aCB0ZXh0IGZyb20gdGhlIG9yaWdpbmFsIHJldmlldyBhbmQgcmVz
cG9uc2VzDQo+ZnJvbSBvbmUgb2YgdGhlIGF1dGhvcnMgKE1lZCkuDQo+V2UgYWdyZWVkIHRoYXQg
dGhvc2UgdHdvIHJldmlzaXRlZCBpdGVtcyBjb3VsZCBiZSBhZGRyZXNzZWQgaW4gYSBzdWJzZXF1
ZW50DQo+cmV2aXNpb247IHRoZXkgYXJlIGp1c3QNCj5yZWNvcmRlZCBoZXJlIGZvciBlYXNlIG9m
IHJlZmVyZW5jZS4NCj4NCj5NYWpvciBpc3N1ZXM6DQo+DQo+TWlub3IgaXNzdWVzOg0KPg0KPk5p
dHM6DQo+DQo+W09sZF0NCj4NCj4+PlNlY3Rpb24gMy4xLCA1dGggcGFyYWdyYXBoOiBJIGRvbid0
IHF1aXRlIGZvbGxvdyB3aGF0J3MgYmVpbmcgc2FpZCBoZXJlLg0KPj4+SXMgdGhlIHBvaW50IHRo
YXQgdGhlIGFkZHJlc3Mtc2hhcmluZyBmdW5jdGlvbiBzaG91bGQgcmV2ZWFsIHRoZSBzYW1lDQo+
Pj5IT1NUX0lEIGZvciBhbnkgZ2l2ZW4gaG9zdCByZWdhcmRsZXNzIG9mIHdoYXQgbGF5ZXIgb3Ig
bWVjaGFuaXNtIHRoYXQNCj4+PkhPU1RfSUQgaXMgYmVpbmcgY29udmV5ZWQgYWNyb3NzPyAgSG93
IGRvZXMgdGhpcyByZWxhdGUgdG8NCj4+PmludGVyZmVyZW5jZSBiZXR3ZWVuIEhPU1RfSURzPw0K
Pg0KPj5NZWQ6IFRoZSBwb2ludCBpczogd2hlbiBzZXZlcmFsIGxheWVycyBhcmUgdXNlZCB0byBp
bmplY3QgYSBob3N0X2lkLCB0aGUNCj5kZXZpY2Ugc2hvdWxkIGNoZWNrIHRoZSBzYW1lIHN1YnNl
dCBvZiBpbmZvcm1hdGlvbiBpcyByZXZlYWxlZC4gRm9yDQo+aW5zdGFuY2UsIHRoZXJlIHNob3Vs
ZCBub3QgYmUgY29uZmxpY3QsIGV0Yy4NCj4NCj5UaGVuIHBlcmhhcHMgeW91IGNvdWxkIHJld29y
ZCBzbyB0aGF0ICJzaG91bGQgcmV2ZWFsIHN1YnNldHMgb2YgdGhlIHNhbWUNCj5pbmZvcm1hdGlv
biIgYmVjb21lcyAic2hvdWxkIHJldmVhbCB0aGUgc2FtZSBzdWJzZXRzIG9mIGluZm9ybWF0aW9u
IGF0IGVhY2gNCj5sYXllciI/DQo+DQo+Pj5TZWN0aW9uIDQuOS4yLCA0dGggYnVsbGV0IGl0ZW0s
IDJuZCBzZW50ZW5jZTogRGVsZXRlICJoZWF2eSBhbmQiIHVubGVzcw0KPnlvdSB3YW50IHRvDQo+
Pj5leHBsYWluIHdoYXQgaGVhdnkgbWVhbnMuDQo+DQo+Pk1lZDogRXN0YWJsaXNoaW5nIGFncmVl
bWVudHMgd2l0aCB0aGUgb3duZXIgb2YgdGhlIGFkZHJlc3Mgc2hhcmluZw0KPmZ1bmN0aW9uIGFu
ZCBvd25lcnMgb2Ygc2VydmVycyBpcyBoZWF2eS4gVGhpcyBpcyBhbHJlYWR5IG1lbnRpb25lZCBp
biB0aGUNCj50ZXh0Lg0KPg0KPlBlcmhhcHMgeW91IGNvdWxkIHJlcGxhY2UgImhlYXZ5IiB3aXRo
ICJidXJkZW5zb21lIi4NCj4NCj5bTmV3XQ0KPg0KPkluIHRoZSByZWZlcmVuY2VzLCB0aGVyZSBz
ZWVtIHRvIGJlIGFuIGV4Y2VzcyBvZiBjb21tYXMgaW4gYSBjb3VwbGUgb2YNCj5wbGFjZXMuICAg
TG9vayBmb3IgdGhlIHN0cmluZyAiLCAsIiAoY29tbWEgc3BhY2UgY29tbWEpIGFuZCB5b3UnbGwg
c2VlIHdoYXQNCj5JIG1lYW4uICBUaGUgZG9jdW1lbnQgdGl0bGVzIHN0YXJ0IHdpdGggYW4gZXh0
cmEgY29tbWEgYW5kIGVuZCB3aXRoIG9uZS4NCj4NCj5BbHNvIGluIHRoZSByZWZlcmVuY2VzLCBm
b3IgUkZDIDE0MTMsIHB1dCBhIHNwYWNlIGJldHdlZW4gdGhlICJNLiIgYW5kIHRoZQ0KPiJDLiIg
aW4gTWlrZSBTdC4gSm9obnMnIGluaXRpYWxzLg0KPg0KDQo=

From mohamed.boucadair@orange.com  Wed Apr 10 00:49:28 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 636FF21F8F1A; Wed, 10 Apr 2013 00:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DDkryKzKuuaK; Wed, 10 Apr 2013 00:49:27 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id A066121F8F17; Wed, 10 Apr 2013 00:49:27 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 135533B47E9; Wed, 10 Apr 2013 09:49:27 +0200 (CEST)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id A1ABB27C0B4; Wed, 10 Apr 2013 09:49:26 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Wed, 10 Apr 2013 09:49:26 +0200
From: <mohamed.boucadair@orange.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org" <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
Date: Wed, 10 Apr 2013 09:49:25 +0200
Subject: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Thread-Topic: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Thread-Index: AQGru2VgIxcOQENUYzhlyQVOZ0pm1wHHP5CkmQTyuICAANuqoA==
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC1AE796C@PUEXCB1B.nanterre.francetelecom.fr>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr> <059701ce3554$235aa0b0$6a0fe210$@akayla.com>
In-Reply-To: <059701ce3554$235aa0b0$6a0fe210$@akayla.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.10.65417
X-Mailman-Approved-At: Wed, 10 Apr 2013 08:12:52 -0700
Cc: "gen-art@ietf.org" <gen-art@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: Wed, 10 Apr 2013 07:49:28 -0000

Dear Peter,

I changed the text as follows:

OLD:

   If the requested external port is not available, the PCP server will
   send a CANNOT_PROVIDE_EXTERNAL error response.  If a short lifetime
   error is returned, the IGD-PCP IWF MAY re-send the same request to
   the PCP Server after 30 seconds.  If a PCP error response is
   received, the IGD-PCP IWF relays a negative message to the UPnP
   Control Point with ConflictInMappingEntry as the error code.

NEW:

   If the requested external port is not available, the PCP server will
   send a CANNOT_PROVIDE_EXTERNAL error response:

   1.  If a short lifetime error is returned, the IGD-PCP IWF MAY resend
       the same request to the PCP Server after 30 seconds without
       relaying the error to the UPnP Control Point.  The IGD-PCP IWF
       MAY repeat this process until a positive answer is received or
       some maximum retry limit is reached.  When the maximum retry
       limit is reached, the IGD-PCP IWF relays a negative message to
       the UPnP Control Point with ConflictInMappingEntry as the error
       code.

   2.  If a long lifetime error is returned, the IGD-PCP IWF relays a
       negative message to the UPnP Control Point with
       ConflictInMappingEntry as the error code.

Better?

Cheers,
Med

>-----Message d'origine-----
>De=A0: Peter Yee [mailto:peter@akayla.com]
>Envoy=E9=A0: mardi 9 avril 2013 20:58
>=C0=A0: BOUCADAIR Mohamed OLNC/OLN; draft-ietf-pcp-upnp-igd-
>interworking.all@tools.ietf.org
>Cc=A0: gen-art@ietf.org; ietf@ietf.org
>Objet=A0: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>Med,
>	Thanks for the swift response to my review.  See my one reply
>inline.
>
>		Kind regards,
>		-Peter
>
>>>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP
>>>error other than a short-lifetime error, or in the case of a failed
>>>resend, any PCP error at all.  The wording makes it seem like the
>>>short-lifetime errors are somehow not PCP errors and is therefore
>>>confusing.  It also doesn't explicitly deal with how many repeats should
>be done on a resend.
>
>>[Med] The basic behavior is to relay the received error to the UPnP CP.
>For
>the short-lifetime errors, the IWF may decide to resend the request and no=
t
>relay those errors immediately to the UPnP CP. The number of repeats is no=
t
>specified here as it can be implementation-specific.
>
>Your explanation is fine.  I just found the wording "If a PCP  error
>response is received" to sound ambiguously as if the short-lifetime errors
>were not a subset of PCP errors.
>


From brian.e.carpenter@gmail.com  Wed Apr 10 09:06:16 2013
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 47B8621F98D2; Wed, 10 Apr 2013 09:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.96
X-Spam-Level: 
X-Spam-Status: No, score=-99.96 tagged_above=-999 required=5 tests=[AWL=-1.039, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CeaqOGhhcTxI; Wed, 10 Apr 2013 09:06:15 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 55E4321F9942; Wed, 10 Apr 2013 09:06:15 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id y10so6173580wgg.2 for <multiple recipients>; Wed, 10 Apr 2013 09:06:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Pvjq292gh7+UPVP5FivluKL/DfVTB1wtXrzVK1ar5d0=; b=VB6n+mwQpQHquXjZWDSwASZMJYKUm9rxPUZU8JYbNvPegsEXY7N44quFcf38vbpJxw cyKzr0DVK/cjBJRnHPUBxjtkh2+3Rdp/eGTKxoCF1hiXR5N8Ero8Y8zq4pMSZeBGzakY IP08wBNAvRYZvazfyD4CGtzgdN0433HPNLGHgBleFZlBE+flq/stzcAPEE+wl95hu69l ib/Puvrks4HRV15MeRId6tIr2V4CcttuDsn99OR2jAnJx3CdN3Y3iDCFNOdfahkisLRH RxQu1VRx0BHeV8I05Cmi8/K7eVnbxbBMVENyHGHPbE0SDiBGAYsWplQrMBHt1mD4qWlf otng==
X-Received: by 10.194.77.110 with SMTP id r14mr4751342wjw.2.1365609974544; Wed, 10 Apr 2013 09:06:14 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-189-175.as13285.net. [2.101.189.175]) by mx.google.com with ESMTPS id du2sm32657248wib.0.2013.04.10.09.06.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Apr 2013 09:06:13 -0700 (PDT)
Message-ID: <51658DFC.7010504@gmail.com>
Date: Wed, 10 Apr 2013 17:06:20 +0100
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: Fernando Gont <fgont@si6networks.com>
Subject: Re: [OPSEC] Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <51559943.1010703@gmail.com> <515985E1.1000404@si6networks.com> <515AA8B4.5020707@gmail.com> <5164F5F3.9030007@si6networks.com>
In-Reply-To: <5164F5F3.9030007@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: opsec@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, 10 Apr 2013 16:06:16 -0000

Hi Fernando,

On 10/04/2013 06:17, Fernando Gont wrote:
> Hi, Brian,
> 
> My apologies for the delay in my response. Please find my comments
> in-line...
> 
> 
> On 04/02/2013 06:45 AM, Brian E Carpenter wrote:
>> Fernando,
>>
>> Rather than repeating myself, I'll suggest a change to the Introduction
>> that would (IMHO) improve the message:
>>
>> OLD:
>>
>> 1.  Introduction
>>
>>    Most general-purpose operating systems implement and enable native
>>    IPv6 [RFC2460] support and a number of transition/co-existence
>>    technologies by default.  For cases in which the corresponding
>>    devices are deployed on networks that are assumed to be IPv4-only,
>>
>> NEW:
>>
>> 1.  Introduction
>>
>>    Most general-purpose operating systems implement and enable native
>>    IPv6 [RFC2460] support and a number of transition/co-existence
>>    technologies by default [RFC6434]. Support of IPv6 by all nodes is
>>    intended to become best current practice [RFC6540]. As a result,
>>    networks will need to plan for and deploy IPv6 and its security
>>    mechanisms. Some enterprise networks might, however, choose to delay
>>    active use of IPv6. For networks that are assumed to be IPv4-only,
> 
> I've checked with a few folks, and it seems that the suggested text
> would make everyone happy, except for the sentence that says "As a
> result, networks will need to plan for and deploy IPv6 and its security
> mechanisms.", on the basis that this is not the document to make a case
> for v6 deployment. The suggestions has been to remove that sentence, and
> apply the rest of your proposed text (or, alternatively, to tone down
> that sentence).
> 
> For simplicity sake (and because I'm not sure how one would tone that
> one down), my suggestion would be to apply you proposed text, modulo
> that sentence.
> 
> Would that be okay with you? -- If not, please do let me know, so that
> we can try to find a way forward that keeps everyone happy.

Well, it's not for me to call the consenus, but with that sentence
removed I would personally enter the "no objection" state.

Thanks

    Brian


From touch@isi.edu  Wed Apr 10 09:23:57 2013
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 EDE2721F85C4 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 09:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level: 
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XagFr-1TYSk0 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 09:23:55 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id C016121F85A0 for <ietf@ietf.org>; Wed, 10 Apr 2013 09:23:54 -0700 (PDT)
Received: from [192.168.1.89] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r3AGMpZc017130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Apr 2013 09:23:00 -0700 (PDT)
Message-ID: <516591DE.8030008@isi.edu>
Date: Wed, 10 Apr 2013 09:22:54 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: Re: question about draft-touch-tcp-ao-nat
References: <50B41378.6090105@isi.edu> <50B4182F.7040208@rfc-editor.org> <50B69BF3.9080309@isi.edu> <5149EC6E.1030509@isi.edu>
In-Reply-To: <5149EC6E.1030509@isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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, 10 Apr 2013 16:23:58 -0000

Hi, Nevil (and the IETF list, now).

This is my third attempt at requesting clarification about the status of 
this document. I have been trying to reach you since November.

Since you have not responded to any of my previous posts, I'm cc'ing the 
IETF list, which I sincerely hope you track.

For the IETF list - if anyone knows why these sort of questions are not 
being answered, please post.

Thanks,

Joe

On 3/20/2013 10:05 AM, Joe Touch wrote:
> Hi, Nevil,
>
> I sent this message back in November; the current version addresses all
> received comments. I do not know of any pending comments that have not
> been addressed.
>
> Can you please clarify the change of state yesterday from "None" to
> "Response to Review Needed"?
>
> AFAICT, the doc has been ready to go into final processing for nearly 4
> months now...
>
> Joe
>
> On 11/28/2012 3:19 PM, Joe Touch wrote:
>> Hi, Nevil,
>>
>> An update draft-touch-tcp-ao-nat-04 has been submitted and should appear
>> in the drafts directory shortly.

(the remainder has been deleted for brevity)

From peter@akayla.com  Wed Apr 10 09:46:54 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3F5021F88C6; Wed, 10 Apr 2013 09:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sk5C1wZBAbVm; Wed, 10 Apr 2013 09:46:54 -0700 (PDT)
Received: from p3plsmtpa08-06.prod.phx3.secureserver.net (p3plsmtpa08-06.prod.phx3.secureserver.net [173.201.193.107]) by ietfa.amsl.com (Postfix) with ESMTP id 21D2821F86CB; Wed, 10 Apr 2013 09:46:54 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa08-06.prod.phx3.secureserver.net with  id NGmr1l00P1huGat01GmrEq; Wed, 10 Apr 2013 09:46:53 -0700
From: "Peter Yee" <peter@akayla.com>
To: <mohamed.boucadair@orange.com>, <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr> <059701ce3554$235aa0b0$6a0fe210$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE796C@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EC1AE796C@PUEXCB1B.nanterre.francetelecom.fr>
Subject: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Date: Wed, 10 Apr 2013 09:46:55 -0700
Message-ID: <004c01ce360b$03fdade0$0bf909a0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGru2VgIxcOQENUYzhlyQVOZ0pm1wHHP5CkAxM512IB11gsjJjfEHeA
Content-Language: en-us
Cc: gen-art@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, 10 Apr 2013 16:46:54 -0000

Med,

	That looks great.  Thanks for accommodating my concern.

			Kind regards,
			-Peter

-----Original Message-----
From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =

Sent: Wednesday, April 10, 2013 12:49 AM
To: Peter Yee; draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org
Cc: gen-art@ietf.org; ietf@ietf.org
Subject: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07

Dear Peter,

I changed the text as follows:

OLD:

   If the requested external port is not available, the PCP server will
   send a CANNOT_PROVIDE_EXTERNAL error response.  If a short lifetime
   error is returned, the IGD-PCP IWF MAY re-send the same request to
   the PCP Server after 30 seconds.  If a PCP error response is
   received, the IGD-PCP IWF relays a negative message to the UPnP
   Control Point with ConflictInMappingEntry as the error code.

NEW:

   If the requested external port is not available, the PCP server will
   send a CANNOT_PROVIDE_EXTERNAL error response:

   1.  If a short lifetime error is returned, the IGD-PCP IWF MAY resend
       the same request to the PCP Server after 30 seconds without
       relaying the error to the UPnP Control Point.  The IGD-PCP IWF
       MAY repeat this process until a positive answer is received or
       some maximum retry limit is reached.  When the maximum retry
       limit is reached, the IGD-PCP IWF relays a negative message to
       the UPnP Control Point with ConflictInMappingEntry as the error
       code.

   2.  If a long lifetime error is returned, the IGD-PCP IWF relays a
       negative message to the UPnP Control Point with
       ConflictInMappingEntry as the error code.

Better?

Cheers,
Med

>-----Message d'origine-----
>De=A0: Peter Yee [mailto:peter@akayla.com] Envoy=E9=A0: mardi 9 avril =
2013=20
>20:58 =C0=A0: BOUCADAIR Mohamed OLNC/OLN; draft-ietf-pcp-upnp-igd-=20
>interworking.all@tools.ietf.org Cc=A0: gen-art@ietf.org; ietf@ietf.org=20
>Objet=A0: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>Med,
>	Thanks for the swift response to my review.  See my one reply
inline.
>
>		Kind regards,
>		-Peter
>
>>>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP =

>>>error other than a short-lifetime error, or in the case of a failed=20
>>>resend, any PCP error at all.  The wording makes it seem like the=20
>>>short-lifetime errors are somehow not PCP errors and is therefore=20
>>>confusing.  It also doesn't explicitly deal with how many repeats=20
>>>should
>be done on a resend.
>
>>[Med] The basic behavior is to relay the received error to the UPnP =
CP.
>For
>the short-lifetime errors, the IWF may decide to resend the request and =

>not relay those errors immediately to the UPnP CP. The number of=20
>repeats is not specified here as it can be implementation-specific.
>
>Your explanation is fine.  I just found the wording "If a PCP  error=20
>response is received" to sound ambiguously as if the short-lifetime=20
>errors were not a subset of PCP errors.
>



From doug.mtview@gmail.com  Wed Apr 10 10:38:31 2013
Return-Path: <doug.mtview@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 8A77D21F8E69 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 10:38:31 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wwy1DbB8HYa2 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 10:38:31 -0700 (PDT)
Received: from mail-bk0-x230.google.com (mail-bk0-x230.google.com [IPv6:2a00:1450:4008:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id ACE1621F8E62 for <ietf@ietf.org>; Wed, 10 Apr 2013 10:38:30 -0700 (PDT)
Received: by mail-bk0-f48.google.com with SMTP id jf3so382551bkc.21 for <ietf@ietf.org>; Wed, 10 Apr 2013 10:38:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=EhzqLafSxVbHDdFZ+QmChvbhiQgd5vAZ9GShn3iwX7U=; b=Rdu05cUbkgL79ruQd9R5J18BVoReFRP+HLg45vJz/Q0pG2WN7KpCV3h6Y/ApbnAsNW lFzKTYf/mhchQ21r3QeFUzD/6iPGzhfomu+XC1I9RwDOhwNPnFIzL4We+YSM0mCJl+TP mDTB6LTRi7MgKeCd3L5wD8JLl/BU32QBlijCY9PhGMW7hqXxy5/rbEGKhMAQRqCkmZW8 uYFQUNuRBXVav/+Yh/734u2C57YWo42v00YYIbwBhj64F4Nu6rCv24e2EKpTBw3/aEz8 IPW42H8ImnNqzxLRHWZ2hMV8PmSMwnX6gdWlOvrtSltxrTTfuGI0Un96mUw5o5iX3x8s ZaYg==
X-Received: by 10.205.24.11 with SMTP id rc11mr1211452bkb.39.1365615509663; Wed, 10 Apr 2013 10:38:29 -0700 (PDT)
Received: from ?IPv6:2601:9:3180:3e:417a:a837:e70e:ff5b? ([2601:9:3180:3e:417a:a837:e70e:ff5b]) by mx.google.com with ESMTPS id b21sm465004bkw.12.2013.04.10.10.38.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Apr 2013 10:38:27 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Sufficient email authentication requirements for IPv6
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <51656892.2090907@network-heretics.com>
Date: Wed, 10 Apr 2013 10:38:25 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <42D658A5-6925-4EE6-AD26-05A556716E8F@gmail.com>
References: <20130410000709.70385.qmail@joyce.lan> <51656892.2090907@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
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, 10 Apr 2013 17:38:31 -0000

On Apr 10, 2013, at 6:26 AM, Keith Moore <moore@network-heretics.com> =
wrote:

> On 04/09/2013 08:07 PM, John Levine wrote:
>>> Quoting Nathaniel Borenstein  [1]:
>>>=20
>>>   "One man's blacklist is another's denial-of-service attack."
>>>=20
>>> Email reputation services have a bad reputation.
>> They have a good enough reputation that every non-trivial mail system
>> in the world uses them.  They're not all the same, and a Darwinian
>> process has caused the best run ones to be the most widely used.
>>=20
>> There seems to be a faction that feel that 15 years ago someone once
>> blacklisted them and caused them some inconvenience, therefore all
>> DNSBLs suck forever.  I could say similar things about buggy PC
>> implementations of TCP/IP, but I think a few things have changed =
since
>> then, in both cases.
>=20
> There's an inherent problem with letting 3rd parties affect email =
traffic, especially when there's no way to hold those 3rd parties =
accountable for negligence or malice.

Dear Keith,

I share your ideals.  Being able to authenticate domains SOURCING emails =
brings self administration of sources much closer to a practical =
reality.  As stated in the pdf paper "Domains as a Basis for Managing =
Traffic", one hundred thousand domains control 90% of Internet traffic =
out of approximately 100 million domains active each month.  The top 150 =
domains control 50%, and the top 2,500 control 75% of the traffic. This =
level of consolidation permits effective fast-path white-listing, where =
then dealing with the remainder is less of a burden.

Let me assure you a third-party internationally offering services aimed =
at mitigating abuse either in the form of unwanted inundation of =
commercial solicitations that also affords the resources needed for =
protections against malicious code is not above the law.  We have =
endured many law suits brought by those wishing to profit on their =
various endeavors against the desires of our customers.  Truth is one of =
the first victims in the abatement process.  As such, evidence of abuse =
must be incontrovertible.  Authorization does not imply culpability any =
more than some signed message content independent of the intended =
recipient or the actual source.  Evidence must not rely on statistical =
likelihoods.  The stakes are far to high.=20

Regards,
Douglas Otis






From adrian@olddog.co.uk  Wed Apr 10 14:29:31 2013
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 D183F21F8FFC for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 14:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.956
X-Spam-Level: 
X-Spam-Status: No, score=-1.956 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pQKjCHK+W9qC for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 14:29:31 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id EC93121F8FF3 for <ietf@ietf.org>; Wed, 10 Apr 2013 14:29:30 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3ALTME0019185;  Wed, 10 Apr 2013 22:29:23 +0100
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 r3ALTJQP019147 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 10 Apr 2013 22:29:20 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Joe Touch'" <touch@isi.edu>, "'Nevil Brownlee'" <rfc-ise@rfc-editor.org>
References: <50B41378.6090105@isi.edu> <50B4182F.7040208@rfc-editor.org>	<50B69BF3.9080309@isi.edu> <5149EC6E.1030509@isi.edu> <516591DE.8030008@isi.edu>
In-Reply-To: <516591DE.8030008@isi.edu>
Subject: RE: question about draft-touch-tcp-ao-nat
Date: Wed, 10 Apr 2013 22:29:18 +0100
Message-ID: <018d01ce3632$76dc8030$64958090$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-gb
Thread-Index: AQHFpaHPZta1NDB8cKhjczIgvEj0zQHdmhOHAZB/cBwBbAwCnQG7LKlHmKxtBrA=
Cc: n.brownlee@auckland.ac.nz, 'IETF discussion list' <ietf@ietf.org>, ise@rfc-editor.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, 10 Apr 2013 21:29:31 -0000

Joe,

In my address book I also have ise@ref-editor.org and =
n.brownlee@auckland.ac.nz both cc'ed here.

Looking at http://datatracker.ietf.org/doc/draft-touch-tcp-ao-nat/ the =
I-D state is "Response to Review Needed" as you noted. I don't have an =
key to the ISE states, but this one would seem to be plain English. The =
History tab doesn't show more than the I-D revisions and state changes =
so I can't tell when the review came in or whether there was a =
subsequent review.

The ISE is, of course, out of the remit of the IESG, but you might try =
asking the IAB if they have a lever.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Joe
> Touch
> Sent: 10 April 2013 17:23
> To: Nevil Brownlee
> Cc: IETF discussion list
> Subject: Re: question about draft-touch-tcp-ao-nat
>=20
> Hi, Nevil (and the IETF list, now).
>=20
> This is my third attempt at requesting clarification about the status =
of
> this document. I have been trying to reach you since November.
>=20
> Since you have not responded to any of my previous posts, I'm cc'ing =
the
> IETF list, which I sincerely hope you track.
>=20
> For the IETF list - if anyone knows why these sort of questions are =
not
> being answered, please post.
>=20
> Thanks,
>=20
> Joe
>=20
> On 3/20/2013 10:05 AM, Joe Touch wrote:
> > Hi, Nevil,
> >
> > I sent this message back in November; the current version addresses =
all
> > received comments. I do not know of any pending comments that have =
not
> > been addressed.
> >
> > Can you please clarify the change of state yesterday from "None" to
> > "Response to Review Needed"?
> >
> > AFAICT, the doc has been ready to go into final processing for =
nearly 4
> > months now...
> >
> > Joe
> >
> > On 11/28/2012 3:19 PM, Joe Touch wrote:
> >> Hi, Nevil,
> >>
> >> An update draft-touch-tcp-ao-nat-04 has been submitted and should =
appear
> >> in the drafts directory shortly.
>=20
> (the remainder has been deleted for brevity)


From johnl@iecc.com  Wed Apr 10 15:56:03 2013
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 EA03C21F87E9 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 15:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.049
X-Spam-Level: 
X-Spam-Status: No, score=-111.049 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJBvzKmPzN48 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 15:56:03 -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 26D3A21F87CB for <ietf@ietf.org>; Wed, 10 Apr 2013 15:56:02 -0700 (PDT)
Received: (qmail 17470 invoked from network); 10 Apr 2013 22:56:03 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 10 Apr 2013 22:56:03 -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; s=5165ee02.xn--3zv.k1304; i=johnl@user.iecc.com; bh=v2HQfhvSCJMW/3MgAmjYl5iQ9Np2QRIy6I/6iRPEL88=; b=hBzDQJMCeinXteUJ5HxeuL3ZjNDSSjQ1wEIJajGUp/A9ei+/XPzGFWCz/04tV7QiCyrHCyeTtuOrVlJ8rowW7nz0juc3jRgf25P1diidNv0fuZCDJBMi54lhqPl2wSuPCA9jpQsDHsYo8eEhbnIXsoUNG3N/ZZbzilrClL/G5Hs=
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; s=5165ee02.xn--3zv.k1304; olt=johnl@user.iecc.com; bh=v2HQfhvSCJMW/3MgAmjYl5iQ9Np2QRIy6I/6iRPEL88=; b=qSKDusp2I3XsGG422GUobTKzVblD9636XZtjGLy720EEWu4vEe5QKHGR4WCdHml/ARVTYm2mVJfVOa4PRt2qCa6FZg7iLZJUw/HQZBvCP9TDGRx9ffGnA0ZBdgb0NIM5l2QrUJ4JUBpRJQW/BAnu18u9LqlY2gMgBZZD1dilkTg=
Date: 10 Apr 2013 22:55:39 -0000
Message-ID: <20130410225539.3090.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Sufficient email authentication requirements for IPv6
In-Reply-To: <51656892.2090907@network-heretics.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: moore@network-heretics.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: Wed, 10 Apr 2013 22:56:04 -0000

>> There seems to be a faction that feel that 15 years ago someone once
>> blacklisted them and caused them some inconvenience, therefore all
>> DNSBLs suck forever.  I could say similar things about buggy PC
>> implementations of TCP/IP, but I think a few things have changed since
>> then, in both cases.
>
>There's an inherent problem with letting 3rd parties affect email 
>traffic, especially when there's no way to hold those 3rd parties 
>accountable for negligence or malice.

Like I said, things have changed since 1996.  I talk to Spamhaus every
day am intimately familiar with their processes, and understand who
they report to.

In the meantime, see

http://www.circleid.com/posts/20130301_icann_announces_blocking_usage_review_panel/


From moore@network-heretics.com  Wed Apr 10 16:07:37 2013
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 9CD2721F8A3F for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 16:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.134
X-Spam-Level: 
X-Spam-Status: No, score=-3.134 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HyBHiFoybgBb for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 16:07:37 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id F0E2E21F8A38 for <ietf@ietf.org>; Wed, 10 Apr 2013 16:07:36 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C343820594; Wed, 10 Apr 2013 19:07:35 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Wed, 10 Apr 2013 19:07:35 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=sYL4xF4Ft3ivvizNZ9+1GH NnLv0=; b=R40YL9I/sOQjU5ysciBiGFtdp+1RV5/9sS3zi5dU5YpKAK7ObsJRrX /91bObFnKEjt5+KsHOQIzF4CdUrnZ8IO2SXdGapCoXPskfHrBXyRSw+akQ8FeKyO dEAlCeeJrYlTPFmf9pKehatf21pkLz2jioDAahpnXav0sYmgqeBKo=
X-Sasl-enc: mqdQmdGEsWp7Z5m3M2ZVPcIANpxGJKP+gDwgKx1XRGl0 1365635255
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2EEC7C80003; Wed, 10 Apr 2013 19:07:35 -0400 (EDT)
Message-ID: <5165F0B1.9060900@network-heretics.com>
Date: Wed, 10 Apr 2013 19:07:29 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Sufficient email authentication requirements for IPv6
References: <20130410225539.3090.qmail@joyce.lan>
In-Reply-To: <20130410225539.3090.qmail@joyce.lan>
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: Wed, 10 Apr 2013 23:07:37 -0000

On 04/10/2013 06:55 PM, John Levine wrote:
>>> There seems to be a faction that feel that 15 years ago someone once
>>> blacklisted them and caused them some inconvenience, therefore all
>>> DNSBLs suck forever.  I could say similar things about buggy PC
>>> implementations of TCP/IP, but I think a few things have changed since
>>> then, in both cases.
>> There's an inherent problem with letting 3rd parties affect email
>> traffic, especially when there's no way to hold those 3rd parties
>> accountable for negligence or malice.
> Like I said, things have changed since 1996.

Indeed they have.   Email is much less reliable now than it was then.

Keith


From johnl@taugh.com  Wed Apr 10 16:14:40 2013
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 4E91321F8AE3 for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 16:14:40 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nLTYJzZIpPEH for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 16:14:39 -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 2FEED21F8AD8 for <ietf@ietf.org>; Wed, 10 Apr 2013 16:14:39 -0700 (PDT)
Received: (qmail 22749 invoked from network); 10 Apr 2013 23:14:39 -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:user-agent:cleverness; s=58db.5165f25f.k1304; bh=GC9Q/keejgu01qhpQYFZA8zpvbLea3E19j3bRO2+GmI=; b=cZo4jIvGX4vL4VRz874RBs2ALqd+Am3LGv5b0cm+Qjnj1KYxOHBuXfjav1vLo9PiPi6e/ieiEHWv9DumivQAIHi+llEitb6d2/L0tMYpHdn1b7gW5+68vPih9N+aHDGXcEF97egiB0EaaG35+QVTCr4egRbHlpm4u+ms0c6zDmE=
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:user-agent:cleverness; s=58db.5165f25f.k1304; bh=GC9Q/keejgu01qhpQYFZA8zpvbLea3E19j3bRO2+GmI=; b=olXh8ESPLJXlAXLHMaJXzhVBK726IOuWKD+eIrvPE124KK9txQIwGq3OEG+/G86vvWGDVFweNwEJYhKCzH49qpuwW+fXwixFi455D9QwYyiO+6n5+AIspS3PuT+m82O5G2D6wvOTjg9SqCgZOxmQ/o4TduQ/b0SK7hYqiKwdVTQ=
Received: (ofmipd 127.0.0.1); 10 Apr 2013 23:14:17 -0000
Date: 10 Apr 2013 19:14:38 -0400
Message-ID: <alpine.BSF.2.00.1304101911240.2775@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Keith Moore" <moore@network-heretics.com>
Subject: Re: Sufficient email authentication requirements for IPv6
In-Reply-To: <5165F0B1.9060900@network-heretics.com>
References: <20130410225539.3090.qmail@joyce.lan> <5165F0B1.9060900@network-heretics.com>
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-1320999302-1365635678=:2775"
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: Wed, 10 Apr 2013 23:14:40 -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-1320999302-1365635678=:2775
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

>> Like I said, things have changed since 1996.
>
> Indeed they have.   Email is much less reliable now than it was then.

Agreed.  But it's not the DNSBLs, it's all the other stuff, notably 
heuristic content filters, that we have to do to deal with the 95% of mail 
that is spam these days.

I track what happens to the mail going out of my system, and the only time 
in recent history that any of it got blocked by significant* DNSBLs was 
when someone found a bug in my submit server and sent several thousand 
spams through it.  Oops.  I can't really blame people for not taking my 
mail until I'd shown that I'd fixed it.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

* - i.e., ones used by a perceptible number of recipients

--3825401791-1320999302-1365635678=:2775
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIJCQYJKoZIhvcNAQcCoIII+jCCCPYCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBjowggY2MIIFHqADAgECAgMGLywwDQYJKoZIhvcNAQEFBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xMzAzMTYxOTQ0MDdaFw0xNDAzMTgxMjI4MzVaMFUxGTAX
BgNVBA0TEHFaMXRuOTBuMkdVODZzemYxGDAWBgNVBAMMD2pvaG5sQHRhdWdo
LmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxAdGF1Z2guY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAve/4NFMbuvtD6QSuXAoYQ0SkaO9s
DiNHA4saJNV0OIXd6dtM87w7OETKWWVq24Ab6vQaYh218oCF1GDdLv6EiRB8
oL1k9sK2v70iAVT83vEnmaj6/hQVcBI6mZJH6LXyCgYSP2e5yBQqJu+hgLte
bdg7kOKW2tb937jDn9KYRVFIlEU0/iu/b/Buwq3ahg2BsG3vg92Zk+Dv5VON
QDLE8x8wdi1cor7qBY/RERw4O3LXo3644OU0t6KS3aQxLrXEvWZHHvLhsAu1
BjYbC+qdSddDT1t+adEnZq9/wMhNGhPWCd/uFDZanSpyM913b7eI1Q2aNgA0
cccjEgBsp8IipwIDAQABo4IC1TCCAtEwCQYDVR0TBAIwADALBgNVHQ8EBAMC
BLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSL
djRDW8NpGZJjlhjZ0SLge0hCvjAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6W
NU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0YXVnaC5jb20wggFMBgNVHSAE
ggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0
cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIw
geowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqB
vlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhl
IENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0
Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVk
IHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBv
YmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5zdGFy
dHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5Bggr
BgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv
Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNv
bS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYY
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IBAQCM
pgcOpxRJazPzEBYnhGENuQqzXeLyA3a8XL7YaxaAJwV7ucDVkyQHu35PUEkh
vVgIKnxq6N9WxHiO6GK/imdwS3LrUBbs+0v+95m6YhJv6ZfvAHTyTLqrozXU
ohR5NRFeL0p1OfK1llnl/I71Fe/JNgxJHDn1puzsFoJD3zYCKgNdST3FPNIb
2v/xIiubuB85tiJSWUlc56OkCdBK3ZgBnwYV8LxFmpOlwedaHC6sxIk1rsuX
BHbRIJwLFy2LqVtNm0M5NzBVyPQf72lPn/aaJLbqY5DDm4/lSy94R+CKXabE
6lWan7xmbqdDDlMxGbpMRWV2Cxi5ONp4uNgNcwI6MYIClzCCApMCAQEwgZQw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDBi8sMAkGBSsOAwIaBQCggdgwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNDEwMjMxNDM4WjAjBgkqhkiG
9w0BCQQxFgQUtpjefc2qW3BpT+Hdoc+I2S9RnR0weQYJKoZIhvcNAQkPMWww
ajALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFlAwQBAjAKBggq
hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4D
AgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAPtqhxCQ8GvwT
XiN2dYb/5NKNTVrlUymFM7zRJ6wDuxcgfTF0O2EKQeiOf3SmrdXjMm47sFUo
eOyrrxCvoaJfbK10YSj1kJNWMP4BkAk1J1l/QRRd6QjXfgUy3iBdg1Uu667G
0ci4uZkgwZKOUa8vNVzw2a2p8eSH6/pR7p+3/dbQJ4RWfZRBZWJOT50m6B2a
eVjRUTIi3YHLm2Srz1pIiG6feZNuvYsDbspVSZbOuJio4gdC+QTXZP+3lv2y
41mgP7+SDTZ+qkuE1ntXeQhJ+OE0+TE3OCwbB1b7sq6AwJYIOKxuAXKDWBE+
2qpy/zCNaUJUCgbeSKGLUpWXw3KUXA==

--3825401791-1320999302-1365635678=:2775--

From moore@network-heretics.com  Wed Apr 10 16:23:53 2013
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 3B63921F8C1A for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 16:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.289
X-Spam-Level: 
X-Spam-Status: No, score=-3.289 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V63slDkOmzcQ for <ietf@ietfa.amsl.com>; Wed, 10 Apr 2013 16:23:48 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id C5CA921F8C04 for <ietf@ietf.org>; Wed, 10 Apr 2013 16:23:47 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6B39520B30; Wed, 10 Apr 2013 19:23:47 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 10 Apr 2013 19:23:47 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=KsdgyIUzTWDjD5dJFJhhlx RafBo=; b=VqdYg4GPPKEK+RuOWrM4K0XXfmHAZ3Q6AfwD7auc2TF0HK8rk2VfT0 MT6nVwG8it8OC5jD7q/7ayqmDaKMkVhbiTYYWhZ4CiA56gL86WiX2aQwb79a9pWg mOoKizn5Qst2fboa6aThpXb9HohjdnbhzXyh6GFSGO4+XXx0UkOS4=
X-Sasl-enc: NUlUXxmPRIiLi5bEkffU3PYLBzKf2JQAiHv59fbmm+NC 1365636227
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id C4974C80005; Wed, 10 Apr 2013 19:23:46 -0400 (EDT)
Message-ID: <5165F47D.9060408@network-heretics.com>
Date: Wed, 10 Apr 2013 19:23:41 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: Sufficient email authentication requirements for IPv6
References: <20130410225539.3090.qmail@joyce.lan> <5165F0B1.9060900@network-heretics.com> <alpine.BSF.2.00.1304101911240.2775@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1304101911240.2775@joyce.lan>
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: Wed, 10 Apr 2013 23:23:53 -0000

On 04/10/2013 07:14 PM, John R Levine wrote:
>>> Like I said, things have changed since 1996.
>>
>> Indeed they have.   Email is much less reliable now than it was then.
>
> Agreed.  But it's not the DNSBLs, it's all the other stuff, notably 
> heuristic content filters, that we have to do to deal with the 95% of 
> mail that is spam these days.

In a sense, it's the same problem.   Bad heuristics are being used to 
filter content, generally without the affected users getting any 
notification or having any recourse.   Whether a DNS-based oracle is 
involved, or whether the heuristics are being applied to source IP or 
DNS name, are largely irrelevant.   Certainly using DNS doesn't make the 
use of bad heuristics any better.

Keith


From arturo.servin@gmail.com  Thu Apr 11 07:17:14 2013
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 197DE21F85B3 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 07:17:14 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bt6xyF9lOBDA for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 07:17:13 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2788721F859A for <ietf@ietf.org>; Thu, 11 Apr 2013 07:17:13 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id gd11so1318496vcb.17 for <ietf@ietf.org>; Thu, 11 Apr 2013 07:17:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=57EAec7wtKOcYSQTKxjRQvppi1f140Wq2Yl7t90VnsY=; b=R2wgh2jexQSnG6O1X5aRvxsM/JaqOrS8k3YEeO7h66JNsceWLi4/uT4xcx/Hf0s/ve w2YyR63X/YstmoboMoTPdu0DXrcNFujhXCLXWyDE2UETGCBuqCT6toR0B3YoOcqvgWMt kM8XVXd39Qc1TBhuDz0bJIemfR6BcycQtmLi15OKWLqDNW+1Vk9SEGsZqMLfIq3Nt7Fm pNULimFxa26yaWUNhUTl4bDsWwu5sG96/iWY81Y8x35niiqujfr0zFElST7/+B1WCqCB r7dVJbxmJXBwddTi7wHlGsxHbSNcWSvN3ryf66dalw0J6zfv6eJsy+q0ZrrlWhcn/rkR 9DFA==
X-Received: by 10.52.177.229 with SMTP id ct5mr4354861vdc.113.1365689832573; Thu, 11 Apr 2013 07:17:12 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:5c5a:ea8f:ad7f:7f83]) by mx.google.com with ESMTPS id h11sm4304954vdj.12.2013.04.11.07.17.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Apr 2013 07:17:11 -0700 (PDT)
Message-ID: <5166C5E3.3020207@gmail.com>
Date: Thu, 11 Apr 2013 11:17:07 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Sufficient email authentication requirements for IPv6
References: <20130410225539.3090.qmail@joyce.lan>
In-Reply-To: <20130410225539.3090.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, moore@network-heretics.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, 11 Apr 2013 14:17:14 -0000

On 4/10/13 7:55 PM, John Levine wrote:
>>> There seems to be a faction that feel that 15 years ago someone once
>>> blacklisted them and caused them some inconvenience, therefore all
>>> DNSBLs suck forever.  I could say similar things about buggy PC
>>> implementations of TCP/IP, but I think a few things have changed since
>>> then, in both cases.
>>
>> There's an inherent problem with letting 3rd parties affect email 
>> traffic, especially when there's no way to hold those 3rd parties 
>> accountable for negligence or malice.
> 
> Like I said, things have changed since 1996.  I talk to Spamhaus every
> day am intimately familiar with their processes, and understand who
> they report to.
> 
> In the meantime, see
> 
> http://www.circleid.com/posts/20130301_icann_announces_blocking_usage_review_panel/
> 

	Interesting, a discussion perhaps not for this list (but more
information could be), I am curious of how the review panel is selected,
when it is going to start to operate, and some others ops things.

	I looked around but I couldn't find anything really useful excepts for
some PRs. So if you have a pointer I would be grateful.

regards,
/as

From mohamed.boucadair@orange.com  Wed Apr 10 22:43:58 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE9D21F8D8D; Wed, 10 Apr 2013 22:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[AWL=-0.342, BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YojbI92zc7zW; Wed, 10 Apr 2013 22:43:57 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE5621F8D79; Wed, 10 Apr 2013 22:43:57 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 3185A2DC72E; Thu, 11 Apr 2013 07:43:56 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 11A2E4C070; Thu, 11 Apr 2013 07:43:56 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Thu, 11 Apr 2013 07:43:55 +0200
From: <mohamed.boucadair@orange.com>
To: Peter Yee <peter@akayla.com>, "draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org" <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
Date: Thu, 11 Apr 2013 07:43:53 +0200
Subject: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Thread-Topic: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Thread-Index: AQGru2VgIxcOQENUYzhlyQVOZ0pm1wHHP5CkAxM512IB11gsjJjfEHeAgADYYbA=
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC1AE7D6E@PUEXCB1B.nanterre.francetelecom.fr>
References: <054201ce34fa$0746ec80$15d4c580$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE76B6@PUEXCB1B.nanterre.francetelecom.fr> <059701ce3554$235aa0b0$6a0fe210$@akayla.com> <94C682931C08B048B7A8645303FDC9F36EC1AE796C@PUEXCB1B.nanterre.francetelecom.fr> <004c01ce360b$03fdade0$0bf909a0$@akayla.com>
In-Reply-To: <004c01ce360b$03fdade0$0bf909a0$@akayla.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.11.43316
X-Mailman-Approved-At: Thu, 11 Apr 2013 08:03:02 -0700
Cc: "gen-art@ietf.org" <gen-art@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, 11 Apr 2013 05:43:58 -0000

Dear Peter,

The new version is now available online. A diff is available here: http://w=
ww.ietf.org/rfcdiff?url2=3Ddraft-ietf-pcp-upnp-igd-interworking-08.

Thank you again for the review.

Cheers,
Med

>-----Message d'origine-----
>De=A0: Peter Yee [mailto:peter@akayla.com]
>Envoy=E9=A0: mercredi 10 avril 2013 18:47
>=C0=A0: BOUCADAIR Mohamed OLNC/OLN; draft-ietf-pcp-upnp-igd-
>interworking.all@tools.ietf.org
>Cc=A0: gen-art@ietf.org; ietf@ietf.org
>Objet=A0: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>Med,
>
>	That looks great.  Thanks for accommodating my concern.
>
>			Kind regards,
>			-Peter
>
>-----Original Message-----
>From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com]
>Sent: Wednesday, April 10, 2013 12:49 AM
>To: Peter Yee; draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org
>Cc: gen-art@ietf.org; ietf@ietf.org
>Subject: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>
>Dear Peter,
>
>I changed the text as follows:
>
>OLD:
>
>   If the requested external port is not available, the PCP server will
>   send a CANNOT_PROVIDE_EXTERNAL error response.  If a short lifetime
>   error is returned, the IGD-PCP IWF MAY re-send the same request to
>   the PCP Server after 30 seconds.  If a PCP error response is
>   received, the IGD-PCP IWF relays a negative message to the UPnP
>   Control Point with ConflictInMappingEntry as the error code.
>
>NEW:
>
>   If the requested external port is not available, the PCP server will
>   send a CANNOT_PROVIDE_EXTERNAL error response:
>
>   1.  If a short lifetime error is returned, the IGD-PCP IWF MAY resend
>       the same request to the PCP Server after 30 seconds without
>       relaying the error to the UPnP Control Point.  The IGD-PCP IWF
>       MAY repeat this process until a positive answer is received or
>       some maximum retry limit is reached.  When the maximum retry
>       limit is reached, the IGD-PCP IWF relays a negative message to
>       the UPnP Control Point with ConflictInMappingEntry as the error
>       code.
>
>   2.  If a long lifetime error is returned, the IGD-PCP IWF relays a
>       negative message to the UPnP Control Point with
>       ConflictInMappingEntry as the error code.
>
>Better?
>
>Cheers,
>Med
>
>>-----Message d'origine-----
>>De=A0: Peter Yee [mailto:peter@akayla.com] Envoy=E9=A0: mardi 9 avril 201=
3
>>20:58 =C0=A0: BOUCADAIR Mohamed OLNC/OLN; draft-ietf-pcp-upnp-igd-
>>interworking.all@tools.ietf.org Cc=A0: gen-art@ietf.org; ietf@ietf.org
>>Objet=A0: RE: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
>>
>>Med,
>>	Thanks for the swift response to my review.  See my one reply
>inline.
>>
>>		Kind regards,
>>		-Peter
>>
>>>>Page 13, 1st paragraph, 3rd sentence: what's meant here is if any PCP
>>>>error other than a short-lifetime error, or in the case of a failed
>>>>resend, any PCP error at all.  The wording makes it seem like the
>>>>short-lifetime errors are somehow not PCP errors and is therefore
>>>>confusing.  It also doesn't explicitly deal with how many repeats
>>>>should
>>be done on a resend.
>>
>>>[Med] The basic behavior is to relay the received error to the UPnP CP.
>>For
>>the short-lifetime errors, the IWF may decide to resend the request and
>>not relay those errors immediately to the UPnP CP. The number of
>>repeats is not specified here as it can be implementation-specific.
>>
>>Your explanation is fine.  I just found the wording "If a PCP  error
>>response is received" to sound ambiguously as if the short-lifetime
>>errors were not a subset of PCP errors.
>>
>


From rpelletier@isoc.org  Thu Apr 11 08:11:30 2013
Return-Path: <rpelletier@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 2E14421F9025 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.849
X-Spam-Level: 
X-Spam-Status: No, score=-102.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MQDYDvVrz0Al for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:11:29 -0700 (PDT)
Received: from smtp118.ord1c.emailsrvr.com (smtp118.ord1c.emailsrvr.com [108.166.43.118]) by ietfa.amsl.com (Postfix) with ESMTP id BA0EC21F9021 for <ietf@ietf.org>; Thu, 11 Apr 2013 08:11:29 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 608A11B80E1 for <ietf@ietf.org>; Thu, 11 Apr 2013 11:11:29 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 358BC1B8089 for <ietf@ietf.org>; Thu, 11 Apr 2013 11:11:29 -0400 (EDT)
From: Ray Pelletier <rpelletier@isoc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IETF Diversity Question on Berlin Registration?
Date: Thu, 11 Apr 2013 11:11:28 -0400
Message-Id: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
To: Discussion IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
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: Thu, 11 Apr 2013 15:11:30 -0000

All

The IETF is concerned about diversity.  As good engineers, we would like
to attempt to measure diversity while working on addressing and =
increasing
it.  To that end, we are considering adding some possibly sensitive
questions to the registration process, for example, gender.  Of course,
they need not be answered and would be clearly labeled as optional.

The IAOC would like to hear from the community on this proposal.  It =
plans to=20
make a decision on its 18 April call in order to make the changes in =
time for the=20
Berlin registration and will consider all input received by 17 April. =20=


Thanks for your feedback.

Ray
IAD


From arturo.servin@gmail.com  Thu Apr 11 08:14:16 2013
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 3DC9521F8F4D for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:14:16 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1NxEGMkJLIj for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:14:14 -0700 (PDT)
Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by ietfa.amsl.com (Postfix) with ESMTP id 642CC21F8F41 for <ietf@ietf.org>; Thu, 11 Apr 2013 08:14:11 -0700 (PDT)
Received: by mail-qa0-f49.google.com with SMTP id i13so337443qae.15 for <ietf@ietf.org>; Thu, 11 Apr 2013 08:14:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=HUH7SYpWJF8PSYgiW69a/p39ayyAfF/9+zk8lUJHRPE=; b=qACCOpHCPNl9Amn1B9icq3EU4jmxmrwzxm84CtyRI19izFz9JHQaj8/r0EZL2Kf/sK w+TXbZdx9/buiYyQhIEhRBQSlnHXtaqwLUfJXERTuTSEDqfj6IosQaAvxUN5P9lP53NJ F3B1m8rsJ79/7aNhftdGMd8ULjeCrf6cii2VoCtT1+S92ko1BQaTbDwb8KX/9Nwek7+7 LFZl3mvpD1Q+xxwcxYG8GD+PyUxdue67Nlb9hEbii+18AFkNzSzRWq0KfI9aAdtxnRqX hn+YZrQbWBCsj97Z6zHrRCTlJbHep8uAqIup+tbLL8ko99nTnrlkz006qTFBOdhNpxQk MUNw==
X-Received: by 10.229.14.130 with SMTP id g2mr1467178qca.90.1365693249572; Thu, 11 Apr 2013 08:14:09 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([200.7.87.33]) by mx.google.com with ESMTPS id 10sm7829094qax.13.2013.04.11.08.14.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Apr 2013 08:14:08 -0700 (PDT)
Message-ID: <5166D33D.2080409@gmail.com>
Date: Thu, 11 Apr 2013 12:14:05 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sufficient email authentication requirements for IPv6
References: <20130410225539.3090.qmail@joyce.lan> <5166C5E3.3020207@gmail.com>
In-Reply-To: <5166C5E3.3020207@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: Thu, 11 Apr 2013 15:14:16 -0000

	Somebody point me to see that the date of the post in circleid is April
1st ...

:)

-as

On 4/11/13 11:17 AM, Arturo Servin wrote:
> 
> 
> On 4/10/13 7:55 PM, John Levine wrote:
>>>> There seems to be a faction that feel that 15 years ago someone once
>>>> blacklisted them and caused them some inconvenience, therefore all
>>>> DNSBLs suck forever.  I could say similar things about buggy PC
>>>> implementations of TCP/IP, but I think a few things have changed since
>>>> then, in both cases.
>>>
>>> There's an inherent problem with letting 3rd parties affect email 
>>> traffic, especially when there's no way to hold those 3rd parties 
>>> accountable for negligence or malice.
>>
>> Like I said, things have changed since 1996.  I talk to Spamhaus every
>> day am intimately familiar with their processes, and understand who
>> they report to.
>>
>> In the meantime, see
>>
>> http://www.circleid.com/posts/20130301_icann_announces_blocking_usage_review_panel/
>>
> 
> 	Interesting, a discussion perhaps not for this list (but more
> information could be), I am curious of how the review panel is selected,
> when it is going to start to operate, and some others ops things.
> 
> 	I looked around but I couldn't find anything really useful excepts for
> some PRs. So if you have a pointer I would be grateful.
> 
> regards,
> /as
> 

From rpelletier@isoc.org  Thu Apr 11 08:17:17 2013
Return-Path: <rpelletier@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 EA40A21F8EC7 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:17:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.821
X-Spam-Level: 
X-Spam-Status: No, score=-102.821 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2x+5-LMKADzt for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:17:16 -0700 (PDT)
Received: from smtp94.ord1c.emailsrvr.com (smtp94.ord1c.emailsrvr.com [108.166.43.94]) by ietfa.amsl.com (Postfix) with ESMTP id 2212E21F8E6E for <ietf@ietf.org>; Thu, 11 Apr 2013 08:17:16 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id B0C9D14009D; Thu, 11 Apr 2013 11:17:15 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 18D98140126;  Thu, 11 Apr 2013 11:17:15 -0400 (EDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
Date: Thu, 11 Apr 2013 11:17:14 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
To: Ray Pelletier <rpelletier@isoc.org>
X-Mailer: Apple Mail (2.1085)
Cc: Discussion 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, 11 Apr 2013 15:17:17 -0000

And please direct your comments to iaoc@ietf.org

Thanks

Ray

On Apr 11, 2013, at 11:11 AM, Ray Pelletier wrote:

> All
>=20
> The IETF is concerned about diversity.  As good engineers, we would =
like
> to attempt to measure diversity while working on addressing and =
increasing
> it.  To that end, we are considering adding some possibly sensitive
> questions to the registration process, for example, gender.  Of =
course,
> they need not be answered and would be clearly labeled as optional.
>=20
> The IAOC would like to hear from the community on this proposal.  It =
plans to=20
> make a decision on its 18 April call in order to make the changes in =
time for the=20
> Berlin registration and will consider all input received by 17 April. =20=

>=20
> Thanks for your feedback.
>=20
> Ray
> IAD
>=20


From arturo.servin@gmail.com  Thu Apr 11 08:17:35 2013
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 8ED1721F8F6D for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:17:35 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rggu4YCSRZhU for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:17:35 -0700 (PDT)
Received: from mail-gh0-f178.google.com (mail-gh0-f178.google.com [209.85.160.178]) by ietfa.amsl.com (Postfix) with ESMTP id F41A221F8614 for <ietf@ietf.org>; Thu, 11 Apr 2013 08:17:34 -0700 (PDT)
Received: by mail-gh0-f178.google.com with SMTP id g24so250314ghb.9 for <ietf@ietf.org>; Thu, 11 Apr 2013 08:17:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=uF+eu0ituoqM70MyT5MEB5w+s0ziLiFdwXQ8ZHwf61k=; b=Rymcv4039AzsC87i7+ZsXm6drLUV6Mer/FB6wH7YZEjxSee5eilP3255W27+QqPaGD PwgU/GAf0/xMRioRMVbV7MYqwxnJAIVWHr+VmT+1KyM8tV3ZReHgtdgTw+ZMrtbPkm5b tslQBcfmsGDurZMsdx+1Hft5wg7LOEwQ4CXpzso5yBS7R39IJZCwun1gVwAgPbKYxNjO KppD76frJ5wuW8jC9QjHEvrMW59mro6WFwgQCNZG8VMPURBE6vX/LTvoD9MmEviy5Lgz zNC5qjSAaHNTp/JxIGXpQLXdFQX+JAE/Xne8XHGsrAUCmDugmFLxznHOReETKmSwF42P pkzQ==
X-Received: by 10.236.113.75 with SMTP id z51mr4352535yhg.54.1365693454540; Thu, 11 Apr 2013 08:17:34 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:59a4:4e7f:6415:a750]) by mx.google.com with ESMTPS id x71sm6233312yhg.17.2013.04.11.08.17.32 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Apr 2013 08:17:33 -0700 (PDT)
Message-ID: <5166D40A.9050903@gmail.com>
Date: Thu, 11 Apr 2013 12:17:30 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
In-Reply-To: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.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: Thu, 11 Apr 2013 15:17:35 -0000

	I see no harm in including these type of question as optional.
Personally I do not care if it were mandatory but I think that the most
sensible thing to do is to add it as optional.

	It would be also good to see the complete set of questions.

	So, I support.

Regards,
as


On 4/11/13 12:11 PM, Ray Pelletier wrote:
> All
> 
> The IETF is concerned about diversity.  As good engineers, we would like
> to attempt to measure diversity while working on addressing and increasing
> it.  To that end, we are considering adding some possibly sensitive
> questions to the registration process, for example, gender.  Of course,
> they need not be answered and would be clearly labeled as optional.
> 
> The IAOC would like to hear from the community on this proposal.  It plans to 
> make a decision on its 18 April call in order to make the changes in time for the 
> Berlin registration and will consider all input received by 17 April.  
> 
> Thanks for your feedback.
> 
> Ray
> IAD
> 

From dhc@dcrocker.net  Thu Apr 11 08:45:10 2013
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 C86DE21F90DF for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:45:10 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dbMlyvlJ3D8M for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 08:45:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECB621F90C5 for <ietf@ietf.org>; Thu, 11 Apr 2013 08:45:10 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3BFj92l010318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Apr 2013 08:45:09 -0700
Message-ID: <5166DA80.5060304@dcrocker.net>
Date: Thu, 11 Apr 2013 08:45:04 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
In-Reply-To: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.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, 11 Apr 2013 08:45:09 -0700 (PDT)
Cc: Discussion 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, 11 Apr 2013 15:45:10 -0000

On 4/11/2013 8:11 AM, Ray Pelletier wrote:
>      we are considering adding some possibly sensitive
> questions to the registration process, for example, gender.
...
> The IAOC would like to hear from the community on this proposal.


The world has quite a bit of experience with such survey efforts.  Done 
well, they can be helpful; done poorly that can be extremely 
problematic.  It is very easy to pursue this poorly and the IETF has no 
experience with this activity.

I encourage the IAOC to seek the services of an appropriate expert, to 
assist in the formulation and use of such questions.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From eckert@cisco.com  Thu Apr 11 09:02:53 2013
Return-Path: <eckert@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 82D4C21F910B; Thu, 11 Apr 2013 09:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.593
X-Spam-Level: 
X-Spam-Status: No, score=-9.593 tagged_above=-999 required=5 tests=[AWL=1.006,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pegMrUbc46UL; Thu, 11 Apr 2013 09:02:52 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id C906521F9128; Thu, 11 Apr 2013 09:02:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2526; q=dns/txt; s=iport; t=1365696172; x=1366905772; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=GUtzB89Q1W1V4Y1spEFhyjIYbbqrY/NQhKhkkEQrbZM=; b=jprHgayrwJZKnXJRZbXCNKQJIboNxIMejAnQei95TBXfAKMdDfXfnOv6 kPcwOj2+xgyJk/JB6RZb8mWRTWAFcHxyRLQIjsmuOTiYII859TDVpVf1Q SRxkWOl9dZ6jebkhLtMrzcocGTdoHzNs5RWeRqQDN7yhGBOhPvaad4T/u I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFADvdZlGrRDoJ/2dsb2JhbABQgwbBfoEFFnSCHwEBAQQ6PxALDgQGCSUPBTUUARIUh3+9d48WB4JgYQOJA4ozg0sBkQ+DKxw
X-IronPort-AV: E=Sophos;i="4.87,455,1363132800"; d="scan'208";a="78302405"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 11 Apr 2013 16:02:52 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3BG2kFI029320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Apr 2013 16:02:46 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r3BG0jp9001158;  Thu, 11 Apr 2013 09:01:00 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r3BG0jH6001157; Thu, 11 Apr 2013 09:00:45 -0700
Date: Thu, 11 Apr 2013 09:00:45 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Ray Pelletier <rpelletier@isoc.org>, iad@ietf.org, iaoc@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130411160045.GA32008@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org>
User-Agent: Mutt/1.4.2.2i
Cc: Discussion 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, 11 Apr 2013 16:02:53 -0000

Given how in my understanding, a key concern is really a perceived or real
diversity bias in IETF leadership, if you do add questions about diversity, please also add
the following questions. In fact, i think it would help the nomcom process to ask
these questions whether or not you also ask about diversity.

[Y/N] I understand the job requirements for an IESG member
[Y/N] I understand the job requirements for an IAB member
[Y/N] I consider myself qualified for an IESG/IAB position and I am willing to serve.
[XX]  How many hours per week does an IESG member need to spend on average on the job ?

Explanation:

The first three question could allow based on self assessment to evaluate whether
IETF leadership is biased based on diversity stats or not. Without these questions
i am sure somebody would come up with stats that simply map diversity of existing
leadership to the diversity stats of the community responding during registration.
Of course, self-assessment is not ideal, but much better than nothing.

Question number 4 is just a simple checksum question to assess if there was a mistake
in answering the prior three questions.

In addion of course  the generic questions i miss on almost every questionaire:

[ ] How much did you like the questions we asked (1=useless ... 5=perfect)

Please tell us what questions we should have asked:
[ at least 4 lines by 80 characters space for replies ]

Thanks
    Toerless

On Thu, Apr 11, 2013 at 11:17:14AM -0400, Ray Pelletier wrote:
> And please direct your comments to iaoc@ietf.org
> 
> Thanks
> 
> Ray
> 
> On Apr 11, 2013, at 11:11 AM, Ray Pelletier wrote:
> 
> > All
> > 
> > The IETF is concerned about diversity.  As good engineers, we would like
> > to attempt to measure diversity while working on addressing and increasing
> > it.  To that end, we are considering adding some possibly sensitive
> > questions to the registration process, for example, gender.  Of course,
> > they need not be answered and would be clearly labeled as optional.
> > 
> > The IAOC would like to hear from the community on this proposal.  It plans to 
> > make a decision on its 18 April call in order to make the changes in time for the 
> > Berlin registration and will consider all input received by 17 April.  
> > 
> > Thanks for your feedback.
> > 
> > Ray
> > IAD
> > 
> 

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From ted.ietf@gmail.com  Thu Apr 11 09:05:48 2013
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 6769421F925A; Thu, 11 Apr 2013 09:05:48 -0700 (PDT)
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.434,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KGY+FgR-FU27; Thu, 11 Apr 2013 09:05:47 -0700 (PDT)
Received: from mail-ia0-x22c.google.com (mail-ia0-x22c.google.com [IPv6:2607:f8b0:4001:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 6C37121F910B; Thu, 11 Apr 2013 09:05:47 -0700 (PDT)
Received: by mail-ia0-f172.google.com with SMTP id k38so1582469iah.3 for <multiple recipients>; Thu, 11 Apr 2013 09:05:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=S3UI0QEB/Bkl1T5VOtOldTIqfGgZuhqybeK3rZUIBo0=; b=Yz+LdiycEkHR3Bk5fxdtvVxh8tFqousIaXDsVP1uHLdt2O+BDqgLc1r6gLSxtrDDj8 iT10ssjdjDqEFINqH7hN+AiyfUFlJpGWVHPPUAQwPdjpf4ujDwWNi7pQdW5EocVtLS9A 3xHOH2YbqSQOEMGgAHSzNyNjF6LvUrNoIYRRYmvyzEtzfQfYXUHTBxgEMBXGldyOMT0U MYZfk5CvxewHELvFz58oKcq4MmUswgi5ImUAKrliQvCFpJmPfiynEH/nkjO60DkHpHxU 67oKFqN1YW+ih77a7MdQgG1SWeIWZhEuQInvafs6Y7ObDc9R3HynCSYjlPUMOTX69rqT kFBQ==
MIME-Version: 1.0
X-Received: by 10.50.93.3 with SMTP id cq3mr5026882igb.70.1365696347078; Thu, 11 Apr 2013 09:05:47 -0700 (PDT)
Received: by 10.43.135.202 with HTTP; Thu, 11 Apr 2013 09:05:46 -0700 (PDT)
In-Reply-To: <20130411151859.721.65724.idtracker@ietfa.amsl.com>
References: <20130411151859.721.65724.idtracker@ietfa.amsl.com>
Date: Thu, 11 Apr 2013 09:05:46 -0700
Message-ID: <CA+9kkMD4Ku-F40JhhQGOYenBH=3HWSV86Ht1nBYKFVZG=zipxw@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF Administrative Director <iad@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: iaoc@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, 11 Apr 2013 16:05:48 -0000

Hi Ray,

As you may know, the form of the question asked in any survey can have
a major impact on both how it is answered and the rates at which it is
answered.  If you are considering adding a question on gender, may I
suggest you look at:
http://www.hrc.org/resources/entry/collecting-transgender-inclusive-gender-data-in-workplace-and-other-surveys
.  It lays out some of the challenges faced there.  Since the next
meeting will be in Berlin, I also recommend that the IAOC read:
http://www.coe.int/t/dghl/monitoring/ecri/activities/themes/Ethnic_statistics_and_data_protection.pdf
as it lays out both case studies and at least a few pointers to the
relevant data protection requirements for collecting data deemed to be
"sensitive".

regards,

Ted Hardie



On Thu, Apr 11, 2013 at 8:18 AM, IETF Administrative Director
<iad@ietf.org> wrote:
>
> The IETF is concerned about diversity.  As good engineers, we would like
> to attempt to measure diversity while working on addressing and increasing
> it.  To that end, we are considering adding some possibly sensitive
> questions to the registration process, for example, gender.  Of course,
> they need not be answered and would be clearly labeled as optional.
>
> The IAOC would like to hear from the community on this proposal.  It
> plans to make a decision on its 18 April call in order to make the changes
> in
> time for the Berlin registration and will consider all input received by
> 17
> April.  Thanks for your feedback.
>
> Please direct your comments to iaoc@ietf.org
>
> Ray
> IAD

From melinda.shore@gmail.com  Thu Apr 11 09:09:39 2013
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 675EC21F8F5D for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 09:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.987
X-Spam-Level: 
X-Spam-Status: No, score=-2.987 tagged_above=-999 required=5 tests=[AWL=0.612,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1HXTe6g25A7 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 09:09:38 -0700 (PDT)
Received: from mail-vc0-f170.google.com (mail-vc0-f170.google.com [209.85.220.170]) by ietfa.amsl.com (Postfix) with ESMTP id 2325B21F8F2F for <ietf@ietf.org>; Thu, 11 Apr 2013 09:09:38 -0700 (PDT)
Received: by mail-vc0-f170.google.com with SMTP id lf10so1448447vcb.1 for <ietf@ietf.org>; Thu, 11 Apr 2013 09:09:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Z6iDBKIVqb9478tWwuxgrv6Sil+VDDiAlFaVikxQdf4=; b=tnppcHEIN6rCavM+qpSQT5Ox7zRPszhlX77/nKmgGGcm6skqmNBmeJmENh4CPaTuwg mh1nYJGm5EuFjBntmMLsOC/xMWxvrD852iqp8pLfse+hiAtc5LP3nGUAh0Jr9uVU3vnl YUbReltdlN8ChJbupMjJOybuGV8EenOcroPsowjk0AAJ3JLgNK2+rRAQbF+uBqx7EiRv /cEMnF7uAZ5OCTvRHncp8eSFX8+wzXbsKrx6VDCMRCaBlWrqpdoEX6JBHsTQ9w+8Ojl1 0m/kGshtJ1KflGutEgDkWsNxkSZzwHZueRxpC6v3dyHgHw0A1yDjYtQpW+sAXBOujjZ3 MlNw==
X-Received: by 10.52.29.19 with SMTP id f19mr880759vdh.100.1365696577634; Thu, 11 Apr 2013 09:09:37 -0700 (PDT)
Received: from [129.6.252.108] ([129.6.252.108]) by mx.google.com with ESMTPS id em6sm4731891vdb.3.2013.04.11.09.09.36 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Apr 2013 09:09:36 -0700 (PDT)
Message-ID: <5166E03E.7080006@gmail.com>
Date: Thu, 11 Apr 2013 08:09:34 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org> <20130411160045.GA32008@cisco.com>
In-Reply-To: <20130411160045.GA32008@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: Thu, 11 Apr 2013 16:09:39 -0000

On 4/11/2013 8:00 AM, Toerless Eckert wrote:
> The first three question could allow based on self assessment to evaluate whether
> IETF leadership is biased based on diversity stats or not.

There are actually several questions in there.  It
would be interesting to know how the pool of people
willing to serve in a leadership role relate to the
pool of participants.  It would also be interesting to
know how the pool of people recommended by the nomcom
relate to the pool of candidates who've accepted
nominations.  Those are two very different questions
but I think they're both good ones.

Melinda


From arturo.servin@gmail.com  Thu Apr 11 09:33:28 2013
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 6199E21F87B1 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 09:33:28 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I7YxJXkUwGbk for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 09:33:28 -0700 (PDT)
Received: from mail-vc0-f170.google.com (mail-vc0-f170.google.com [209.85.220.170]) by ietfa.amsl.com (Postfix) with ESMTP id C57E721F86F7 for <ietf@ietf.org>; Thu, 11 Apr 2013 09:33:27 -0700 (PDT)
Received: by mail-vc0-f170.google.com with SMTP id lf10so1470691vcb.1 for <ietf@ietf.org>; Thu, 11 Apr 2013 09:33:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=qVFupTT6JHP8QSFid3kyOIfWRUYglMSqioPDSkPhxJw=; b=jPAF1l42Fcf+4Qlt0mlcmAA7slmsqq2XxJM/ngY34Y2thedp4BtApEYT/DSUPDo6gY ETC6M4UuI8aqcU/YWij6vqR1RxMmR9k8TWk4w7vbriH1jzS9FcFkm1OhUO9oMsjnxeLS l4+CHrS4Rtm3YAjZvGnKRk5VafTnBZlBp/5TlvZ3QKQZPkQbmpTgDyeObmkC85IwHb4X ySJ1RgkLZmEvL9fYJTBzBw2BacvZdaWsMGNZtfuoCU+Rd4bcz1Hza3CJhzQf/wLE0IfZ x7/LpYNrdI0y6yAZuVoEbJ/cWriINkQi8l1kg6xHZPLk7CADhphWeu0+EZQ34qpBsMkb NF8Q==
X-Received: by 10.52.33.116 with SMTP id q20mr4762689vdi.65.1365698007345; Thu, 11 Apr 2013 09:33:27 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:59a4:4e7f:6415:a750]) by mx.google.com with ESMTPS id tb9sm4775364veb.6.2013.04.11.09.33.24 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Apr 2013 09:33:25 -0700 (PDT)
Message-ID: <5166E5D1.3010908@gmail.com>
Date: Thu, 11 Apr 2013 13:33:21 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org> <20130411160045.GA32008@cisco.com>
In-Reply-To: <20130411160045.GA32008@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: Thu, 11 Apr 2013 16:33:28 -0000

On 4/11/13 1:00 PM, Toerless Eckert wrote:
> if you do add questions about diversity, please also add
> the following questions.

	Please no.

	This is about the registration form, not a survey.

.as

From eckert@cisco.com  Thu Apr 11 09:55:52 2013
Return-Path: <eckert@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 AF6E421F8FC7 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 09:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.096
X-Spam-Level: 
X-Spam-Status: No, score=-10.096 tagged_above=-999 required=5 tests=[AWL=0.503, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wS6pCV0R-d6Z for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 09:55:52 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 27C8921F8FC0 for <ietf@ietf.org>; Thu, 11 Apr 2013 09:55:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=826; q=dns/txt; s=iport; t=1365699352; x=1366908952; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=hgsDKBxNMC19R/gVqGRXci2XMVugjopR+O8bjRnzrP8=; b=jWXD4ENy/xszWw20rursD0It+T2vHc97XR7rOMKw9G/UzXdGIpOJpvHU 9sl6klOtFTuBQiDM1uWHqUe+fLOHixFUv9aDlT1m9NxiwBUJPt4kITyZl 4MObCOVqvOA4POG/a7cowjX0nKfoVN0ISSS6WrsLVe4QYblEMSNCNNQce E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArAFAF7qZlGrRDoG/2dsb2JhbABQgwaDHb5hgQUWdIIfAQEBBBgiPxALEgYJJQ8FNRQTiBO9cY8WB4JgYQOJA41+AZEPgysc
X-IronPort-AV: E=Sophos;i="4.87,456,1363132800"; d="scan'208";a="75801652"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 11 Apr 2013 16:55:50 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3BGtjo1015513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Apr 2013 16:55:45 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r3BGsO3r003313;  Thu, 11 Apr 2013 09:54:39 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r3BGsObW003312; Thu, 11 Apr 2013 09:54:24 -0700
Date: Thu, 11 Apr 2013 09:54:24 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130411165424.GB32008@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org> <20130411160045.GA32008@cisco.com> <5166E5D1.3010908@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5166E5D1.3010908@gmail.com>
User-Agent: Mutt/1.4.2.2i
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, 11 Apr 2013 16:55:52 -0000

When adding diversity questions to the registration form, i think there should
be a very crisp description, whom exactly this information is made available to,
and how it is meant to be used.

If the total stats for example are simply made available publically and there
are not also other stats like the ones i asked for, then the effort will just
reinforce bogus statistical claims.

On Thu, Apr 11, 2013 at 01:33:21PM -0300, Arturo Servin wrote:
> 
> On 4/11/13 1:00 PM, Toerless Eckert wrote:
> > if you do add questions about diversity, please also add
> > the following questions.
> 
> 	Please no.
> 
> 	This is about the registration form, not a survey.
> 
> .as

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From tnadeau@lucidvision.com  Thu Apr 11 09:58:09 2013
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14C6921F9154 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 09:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7BvunsRw7Ij for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 09:58:08 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB5221F913E for <ietf@ietf.org>; Thu, 11 Apr 2013 09:58:08 -0700 (PDT)
Received: from [192.168.1.55] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id C5DDF245EBD1; Thu, 11 Apr 2013 12:58:07 -0400 (EDT)
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org> <20130411160045.GA32008@cisco.com> <5166E5D1.3010908@gmail.com> <20130411165424.GB32008@cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20130411165424.GB32008@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <445023BA-7743-4ACB-9313-46C737E8F7F8@lucidvision.com>
X-Mailer: iPhone Mail (10B329)
From: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Date: Thu, 11 Apr 2013 12:58:07 -0400
To: Toerless Eckert <eckert@cisco.com>
Cc: Arturo Servin <arturo.servin@gmail.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: Thu, 11 Apr 2013 16:58:09 -0000

questions must be optional to answer too.

Tom=20


On Apr 11, 2013, at 12:54 PM, Toerless Eckert <eckert@cisco.com> wrote:

> When adding diversity questions to the registration form, i think there sh=
ould
> be a very crisp description, whom exactly this information is made availab=
le to,
> and how it is meant to be used.
>=20
> If the total stats for example are simply made available publically and th=
ere
> are not also other stats like the ones i asked for, then the effort will j=
ust
> reinforce bogus statistical claims.
>=20
> On Thu, Apr 11, 2013 at 01:33:21PM -0300, Arturo Servin wrote:
>>=20
>> On 4/11/13 1:00 PM, Toerless Eckert wrote:
>>> if you do add questions about diversity, please also add
>>> the following questions.
>>=20
>>    Please no.
>>=20
>>    This is about the registration form, not a survey.
>>=20
>> .as
>=20
> --=20
> ---
> Toerless Eckert, eckert@cisco.com
> Cisco NSSTG Systems & Technology Architecture
> SDN: Let me play with the network, mommy!
>=20
>=20

From arturo.servin@gmail.com  Thu Apr 11 10:20:02 2013
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 C327321F926E for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 10:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.324
X-Spam-Level: 
X-Spam-Status: No, score=-2.324 tagged_above=-999 required=5 tests=[AWL=-1.276, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jb+ZHVNcT881 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 10:20:02 -0700 (PDT)
Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id E1C1721F9227 for <ietf@ietf.org>; Thu, 11 Apr 2013 10:20:01 -0700 (PDT)
Received: by mail-yh0-f48.google.com with SMTP id q46so266404yhf.7 for <multiple recipients>; Thu, 11 Apr 2013 10:20:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hq/vjT+5ETUop3XW/KbagM11C5n35i/l09S+rmGLYn0=; b=fVDwnn6B+uJTxsnW/2gkOowa6BT21qsRXkLhuyoTyhp2m8kHZZ6wo9AWsKJWjgVXnA KDTijRWHqwSTEHiZcf3Fi/WdRQznBxZMGkzE0rfznpKzvk/PJ6KUeKBiPETPGfvmP5eF J15T8i+/wi9ifG1OkTC1CS+w2bEgpw8EqOdBWNRvOZ02nPdnRS+KEu/xvI+VBizqbxO1 z/ZBrMJlBaARho2K3LSWhnvyFK3wRfxwbcdkXSsRvhEbGoUKswAqGXb4544auAAFTbTn CmI45ZRPstQk5hqCp+D7iqepULzaIsBym2SJhg27F/r4geVINXrh+junQc5n5fD9LScL xl3g==
X-Received: by 10.236.57.229 with SMTP id o65mr4550196yhc.76.1365700801505; Thu, 11 Apr 2013 10:20:01 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([200.7.87.33]) by mx.google.com with ESMTPS id s45sm6811994yhk.22.2013.04.11.10.19.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Apr 2013 10:19:59 -0700 (PDT)
Message-ID: <5166F0BB.1030302@gmail.com>
Date: Thu, 11 Apr 2013 14:19:55 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org> <20130411160045.GA32008@cisco.com> <5166E5D1.3010908@gmail.com> <20130411165424.GB32008@cisco.com> <445023BA-7743-4ACB-9313-46C737E8F7F8@lucidvision.com>
In-Reply-To: <445023BA-7743-4ACB-9313-46C737E8F7F8@lucidvision.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, ioac@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Apr 2013 17:20:03 -0000

	Yes, but then you would end up with a large registration form that
people may decide not to complete at all.

	
.as

On 4/11/13 1:58 PM, Thomas D. Nadeau wrote:
> questions must be optional to answer too.
> 
> Tom 
> 
> 
> On Apr 11, 2013, at 12:54 PM, Toerless Eckert <eckert@cisco.com> wrote:
> 
>> When adding diversity questions to the registration form, i think there should
>> be a very crisp description, whom exactly this information is made available to,
>> and how it is meant to be used.
>>
>> If the total stats for example are simply made available publically and there
>> are not also other stats like the ones i asked for, then the effort will just
>> reinforce bogus statistical claims.
>>
>> On Thu, Apr 11, 2013 at 01:33:21PM -0300, Arturo Servin wrote:
>>>
>>> On 4/11/13 1:00 PM, Toerless Eckert wrote:
>>>> if you do add questions about diversity, please also add
>>>> the following questions.
>>>
>>>    Please no.
>>>
>>>    This is about the registration form, not a survey.
>>>
>>> .as
>>
>> -- 
>> ---
>> Toerless Eckert, eckert@cisco.com
>> Cisco NSSTG Systems & Technology Architecture
>> SDN: Let me play with the network, mommy!
>>
>>

From eckert@cisco.com  Thu Apr 11 10:26:21 2013
Return-Path: <eckert@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 A1C9E21F9352 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 10:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.264
X-Spam-Level: 
X-Spam-Status: No, score=-10.264 tagged_above=-999 required=5 tests=[AWL=0.335, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAhxr+k5y7+Y for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 10:26:10 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id E445D21F86F7 for <ietf@ietf.org>; Thu, 11 Apr 2013 10:26:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1291; q=dns/txt; s=iport; t=1365701169; x=1366910769; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=FHw9s/cBr4EdE3bRmMG5MPv8KAgPUViX/AMnSXdUAHk=; b=f0Qt130nHLJtzxey3TDDzmgNdOb4gZQ5mZ7EuA0pRYiyS4LgK3ikpTAi k5RbDtve7K5R70HiMBvyoNwJzkQvKeqpOAz6AqJjCkz6yvOY/8DCkPMZl KQAjqAVEAB9jHmT8Kb2EPpB5p06SZpb152Lhdui9WVbIspidd14AmJNP/ Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGDxZlGrRDoG/2dsb2JhbABQgwbBfoEFFnSCHwEBAQMBGCI/BQsLEgYJJQ8FNRQTiA4FvW6PFgeCYGEDiQONfgGRD4MrHA
X-IronPort-AV: E=Sophos;i="4.87,456,1363132800"; d="scan'208";a="75803796"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 11 Apr 2013 17:26:07 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3BHPknj006854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Apr 2013 17:25:46 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r3BHNp7W004565;  Thu, 11 Apr 2013 10:24:06 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r3BHNpb9004564; Thu, 11 Apr 2013 10:23:51 -0700
Date: Thu, 11 Apr 2013 10:23:51 -0700
From: Toerless Eckert <eckert@cisco.com>
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130411172351.GC32008@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org> <20130411160045.GA32008@cisco.com> <5166E5D1.3010908@gmail.com> <20130411165424.GB32008@cisco.com> <445023BA-7743-4ACB-9313-46C737E8F7F8@lucidvision.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <445023BA-7743-4ACB-9313-46C737E8F7F8@lucidvision.com>
User-Agent: Mutt/1.4.2.2i
Cc: Arturo Servin <arturo.servin@gmail.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: Thu, 11 Apr 2013 17:26:21 -0000

On Thu, Apr 11, 2013 at 12:58:07PM -0400, Thomas D. Nadeau wrote:
> questions must be optional to answer too.

Definitely.

> Tom 
> 
> 
> On Apr 11, 2013, at 12:54 PM, Toerless Eckert <eckert@cisco.com> wrote:
> 
> > When adding diversity questions to the registration form, i think there should
> > be a very crisp description, whom exactly this information is made available to,
> > and how it is meant to be used.
> > 
> > If the total stats for example are simply made available publically and there
> > are not also other stats like the ones i asked for, then the effort will just
> > reinforce bogus statistical claims.
> > 
> > On Thu, Apr 11, 2013 at 01:33:21PM -0300, Arturo Servin wrote:
> >> 
> >> On 4/11/13 1:00 PM, Toerless Eckert wrote:
> >>> if you do add questions about diversity, please also add
> >>> the following questions.
> >> 
> >>    Please no.
> >> 
> >>    This is about the registration form, not a survey.
> >> 
> >> .as
> > 
> > -- 
> > ---
> > Toerless Eckert, eckert@cisco.com
> > Cisco NSSTG Systems & Technology Architecture
> > SDN: Let me play with the network, mommy!
> > 
> > 

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From touch@isi.edu  Thu Apr 11 10:54:50 2013
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 BCB2F21F85C4 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 10:54:50 -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=[AWL=-2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JO34nqIqoJPZ for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 10:54:46 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 1525B21F84E9 for <ietf@ietf.org>; Thu, 11 Apr 2013 10:54:41 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r3BHs6Ok012097 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Apr 2013 10:54:06 -0700 (PDT)
Message-ID: <5166F8BD.7010308@isi.edu>
Date: Thu, 11 Apr 2013 10:54:05 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Purpose of IESG Review
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 11 Apr 2013 17:54:50 -0000

Hi, all,

As an author who has had (and has) multiple documents in IESG review, 
I've noticed an increasing trend of this step to go beyond (IMO) its 
documented and original intent (BCP 9, currently RFC 2026):

    The IESG shall determine whether or not a specification submitted to
    it according to section 6.1.1 satisfies the applicable criteria for
    the recommended action (see sections 4.1 and 4.2), and shall in
    addition determine whether or not the technical quality and clarity
    of the specification is consistent with that expected for the
    maturity level to which the specification is recommended.

Although I appreciate that IESG members are often overloaded, and the 
IESG Review step is often the first time many see these documents, I 
believe they should be expected to more clearly differentiate their 
"IESG Review" (based on the above criteria) - and its accompanying 
Position ballot, with their personal review.

My concern is that by conflating their IESG position with their personal 
review, the document process is inappropriately delayed and that 
documents are modified to appease a small community that does not 
justify its position as representative.

How do others feel about this?

Joe

From eckert@cisco.com  Thu Apr 11 10:59:02 2013
Return-Path: <eckert@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 BB32221F89B0 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 10:59:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.348
X-Spam-Level: 
X-Spam-Status: No, score=-10.348 tagged_above=-999 required=5 tests=[AWL=0.252, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hRRwzYS7Ws6s for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 10:58:43 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id EA77021F896D for <ietf@ietf.org>; Thu, 11 Apr 2013 10:58:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1531; q=dns/txt; s=iport; t=1365703120; x=1366912720; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=CmfwXv07EoSsqFGeFnhQQt8dtg27AbBpCrFNaQXkXDI=; b=UP4D/+k7OVtcV64nU5jBuWnTZSTqlhMywmCNNJeFT96cACo6ty5uXaAq amo/wFmlWFUQcNie4nBNSP73rjnp6D9aS4znGOlr0jaUQkIua4jGBP00a z3fzjrghFRGCfAyBqT8Rl879EsczUrC/0K1Cu3IPcdS57OTm+uJQAQARv 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAFf5ZlGrRDoG/2dsb2JhbABQgwbBfoEGFnSCHwEBAQQYIj8QCxIGCSUPBTUUE4gTvW2PFgeCYGEDiQONfgGRD4MrHA
X-IronPort-AV: E=Sophos;i="4.87,456,1363132800"; d="scan'208";a="78309569"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 11 Apr 2013 17:58:26 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3BHw7LQ032237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Apr 2013 17:58:07 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r3BHtu86005867;  Thu, 11 Apr 2013 10:56:11 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r3BHtugV005865; Thu, 11 Apr 2013 10:55:56 -0700
Date: Thu, 11 Apr 2013 10:55:56 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130411175556.GD32008@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org> <20130411160045.GA32008@cisco.com> <5166E5D1.3010908@gmail.com> <20130411165424.GB32008@cisco.com> <445023BA-7743-4ACB-9313-46C737E8F7F8@lucidvision.com> <5166F0BB.1030302@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5166F0BB.1030302@gmail.com>
User-Agent: Mutt/1.4.2.2i
Cc: "ietf@ietf.org" <ietf@ietf.org>, ioac@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Apr 2013 17:59:03 -0000

That's the tail wagging the dog. 

On Thu, Apr 11, 2013 at 02:19:55PM -0300, Arturo Servin wrote:
> 
> 	Yes, but then you would end up with a large registration form that
> people may decide not to complete at all.
> 
> 	
> .as
> 
> On 4/11/13 1:58 PM, Thomas D. Nadeau wrote:
> > questions must be optional to answer too.
> > 
> > Tom 
> > 
> > 
> > On Apr 11, 2013, at 12:54 PM, Toerless Eckert <eckert@cisco.com> wrote:
> > 
> >> When adding diversity questions to the registration form, i think there should
> >> be a very crisp description, whom exactly this information is made available to,
> >> and how it is meant to be used.
> >>
> >> If the total stats for example are simply made available publically and there
> >> are not also other stats like the ones i asked for, then the effort will just
> >> reinforce bogus statistical claims.
> >>
> >> On Thu, Apr 11, 2013 at 01:33:21PM -0300, Arturo Servin wrote:
> >>>
> >>> On 4/11/13 1:00 PM, Toerless Eckert wrote:
> >>>> if you do add questions about diversity, please also add
> >>>> the following questions.
> >>>
> >>>    Please no.
> >>>
> >>>    This is about the registration form, not a survey.
> >>>
> >>> .as
> >>
> >> -- 
> >> ---
> >> Toerless Eckert, eckert@cisco.com
> >> Cisco NSSTG Systems & Technology Architecture
> >> SDN: Let me play with the network, mommy!
> >>
> >>

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From hsantos@isdg.net  Thu Apr 11 11:23:24 2013
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 DA31D21F85BF for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 11:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.735
X-Spam-Level: 
X-Spam-Status: No, score=-101.735 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id trJGPPy-g+3x for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 11:23:18 -0700 (PDT)
Received: from dkim.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5BC0321F84F9 for <ietf@ietf.org>; Thu, 11 Apr 2013 11:23:17 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2350; t=1365704582; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=SH7njYJ wBMQdThxqWsR7uUGH8f0=; b=vKrHnjQWD97I1zjvoLSETkmRiM8uro7MYE9vDTL f6KJR2L00cjnVU8aBi8UqAzN4CJGmQvlTAsGgCZ3lUUwnINRnfDnydJC8pWlOu3C SoNQm0eMlcx7LXxRun4KOyzWtNsMZqzzD+dcNHlqQRI0tzWIOzeHHoWsM2CsbtCC ozF8=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 11 Apr 2013 14:23:02 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 203318522.6801.2252; Thu, 11 Apr 2013 14:23:02 -0400
Message-ID: <5166FF49.70105@isdg.net>
Date: Thu, 11 Apr 2013 14:22:01 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Sufficient email authentication requirements for IPv6
References: <20130410225539.3090.qmail@joyce.lan> <5165F0B1.9060900@network-heretics.com>
In-Reply-To: <5165F0B1.9060900@network-heretics.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: Thu, 11 Apr 2013 18:23:25 -0000

I don't have the same overall feeling that its less reliable.

I believe it is 100% reliable when it comes to the "good" 
communications, the serious stuff, the work, business communications. 
Those get through and more importantly, above all, when there is a 
problem, good people complain, any email related problem is solved. On 
the other hand, "bad guys" don't complain, that includes the spammers.

I guess, in that sense, if you (speaking in general) are in the spamming 
business, part of a commercial bulk mailing business, then business is 
probably finding it harder to try to reach the eyeballs of end users.

SMTP systems are doing more of the filtering at the SMTP level - a 
Systems Level versus Users level, and at the user level, the online MUA 
(web interfaces), the backend has done a tremendous job in 
sorting/filtering spam into "Junk Folders."  Offline i.e. POP3, unless 
the user spent the effort to write the rules, its all in the same inbox. 
   In this sense, it is less reliable for the DMA, Spammers, etc, to get 
their mail to the eyeballs of users.

Lets also consider there is a higher (intentional) ignorance factor. 
Something we just don't wish to reply to a message received and read.

That would be akin to a phone call with caller ID and we ignore it, 
don't answer it.   In that vain, caller id has lowered the reliability 
of the phone protocol call being answered.  We do that total with SMTP 
connection filters, where the connection is immediately dropped (socket 
is closed).

All that doesn't make it unreliability - its done by design. It works.

--
HLS

On 4/10/2013 7:07 PM, Keith Moore wrote:
> On 04/10/2013 06:55 PM, John Levine wrote:
>>>> There seems to be a faction that feel that 15 years ago someone once
>>>> blacklisted them and caused them some inconvenience, therefore all
>>>> DNSBLs suck forever.  I could say similar things about buggy PC
>>>> implementations of TCP/IP, but I think a few things have changed since
>>>> then, in both cases.
>>> There's an inherent problem with letting 3rd parties affect email
>>> traffic, especially when there's no way to hold those 3rd parties
>>> accountable for negligence or malice.
>> Like I said, things have changed since 1996.
>
> Indeed they have.   Email is much less reliable now than it was then.
>
> Keith
>
>
>


From iab-chair@iab.org  Thu Apr 11 11:37:04 2013
Return-Path: <iab-chair@iab.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 43D9121F85D9; Thu, 11 Apr 2013 11:37:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vKL-gECXQJV; Thu, 11 Apr 2013 11:37:03 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id BD5D021F882A; Thu, 11 Apr 2013 11:37:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id BAC87127A74; Thu, 11 Apr 2013 11:37:03 -0700 (PDT)
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 2U6yVUlypppE; Thu, 11 Apr 2013 11:37:03 -0700 (PDT)
Received: from v150.vpn.iad.rg.net (v150.vpn.iad.rg.net [198.180.150.150]) by c8a.amsl.com (Postfix) with ESMTPSA id 0700C127250; Thu, 11 Apr 2013 11:37:02 -0700 (PDT)
From: IAB Chair <iab-chair@iab.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IAB Appoints Jonne Soininen as Liaison to the ICANN Board
Date: Thu, 11 Apr 2013 14:37:00 -0400
Message-Id: <8BBD3635-1329-4916-B69F-BA101D51946A@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: Thomas Narten <narten@us.ibm.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: Thu, 11 Apr 2013 18:37:04 -0000

The IAB has been deliberating the selection of the liaison from the IETF =
community to ICANN Board over the past several weeks.  The IAB was very =
pleased to have a strong set of candidates. We very much appreciate the =
willingness of so many talented people to serve the community in this =
position.

The IAB has selected Jonne Soininen for this position, replacing Thomas =
Narten.

The IAB extends our sincere thanks to Thomas for serving the community =
for so long in this role.  Thomas has done a fantastic job.

The IAB extends our sincere thanks to Jonne for agreeing to serve in =
this position.  We are sure that Jonne will do a fantastic job going =
forward.

Thomas and Jonne will be working out the transition of this role during =
the month of April.

On behalf of the IAB,
Russ Housley
IAB Chair

From paul.hoffman@vpnc.org  Thu Apr 11 11:55:10 2013
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 107BD21F8DFC for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 11:55:10 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ryQ+KG2lKrk2 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 11:55:09 -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 7C40F21F8F67 for <ietf@ietf.org>; Thu, 11 Apr 2013 11:55:09 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r3BIt8Qc065046 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 11 Apr 2013 11:55:08 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Purpose of IESG Review
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <5166F8BD.7010308@isi.edu>
Date: Thu, 11 Apr 2013 11:55:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org>
References: <5166F8BD.7010308@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1503)
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, 11 Apr 2013 18:55:10 -0000

On Apr 11, 2013, at 10:54 AM, Joe Touch <touch@isi.edu> wrote:

> As an author who has had (and has) multiple documents in IESG review, =
I've noticed an increasing trend of this step to go beyond (IMO) its =
documented and original intent (BCP 9, currently RFC 2026):
>=20
>   The IESG shall determine whether or not a specification submitted to
>   it according to section 6.1.1 satisfies the applicable criteria for
>   the recommended action (see sections 4.1 and 4.2), and shall in
>   addition determine whether or not the technical quality and clarity
>   of the specification is consistent with that expected for the
>   maturity level to which the specification is recommended.
>=20
> Although I appreciate that IESG members are often overloaded, and the =
IESG Review step is often the first time many see these documents, I =
believe they should be expected to more clearly differentiate their =
"IESG Review" (based on the above criteria) - and its accompanying =
Position ballot, with their personal review.
>=20
> My concern is that by conflating their IESG position with their =
personal review, the document process is inappropriately delayed and =
that documents are modified to appease a small community that does not =
justify its position as representative.
>=20
> How do others feel about this?

That it is too vague to comment on?

Please point to specific examples where you feel an IESG member's review =
went beyond determining the technical quality or clarity of the =
specification. That would help make the sure-to-be ensuing flamefest =
more light-filled.

--Paul Hoffman=

From sm@resistor.net  Thu Apr 11 12:50:28 2013
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 82EB921F8F28; Thu, 11 Apr 2013 12:50:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.637
X-Spam-Level: 
X-Spam-Status: No, score=-102.637 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f4jXiJhx++hx; Thu, 11 Apr 2013 12:50:25 -0700 (PDT)
Received: from mx.elandsys.com (ns1.qubic.net [208.69.177.116]) by ietfa.amsl.com (Postfix) with ESMTP id 78A5621F8F27; Thu, 11 Apr 2013 12:50:25 -0700 (PDT)
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 r3BJn2WH011410; Thu, 11 Apr 2013 12:49:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365709747; bh=Ppen6B3tU0EvM5T4Bz6qw8TvlmqdE1DPBLAKdXWAYfA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YWVEUjTfsxkyUzwCb798O5n120OO1jOkgAv/Dgtkl0RHZGPYVkuwC1Qk0ed9352YF 03NpIA/VuKk2tWLeGWKwEqrcxcrI69hZ5Kb8bJ+O3fqc7huSGT2KMULe7ypLjfszsN XufNtIdw+vu6dvjSgGORv7c0vTVp20S32AiGoigo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365709747; i=@resistor.net; bh=Ppen6B3tU0EvM5T4Bz6qw8TvlmqdE1DPBLAKdXWAYfA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Y3fdtq7TPPpYMMld13/V5RsKtM9Zwk8f/5pInAhqQfiEaqKMj/lZ0Jc8YD40K3vKe GH1cw6MIhkG31edncl4qwaDMQW/QN/gQMC6CWEjnh/RxVxZN3AvkZ/uSKmBB0u8LDH Rqq1udPIhum9IiSArLOOG70/dXeef7CrGLpwnBWk=
Message-Id: <6.2.5.6.2.20130411101504.0c42fed0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 11 Apr 2013 12:43:48 -0700
To: Ray Pelletier <rpelletier@isoc.org>
From: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iaoc@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, 11 Apr 2013 19:50:28 -0000

Hi Ray,
At 08:11 11-04-2013, Ray Pelletier wrote:
>The IETF is concerned about diversity.  As good engineers, we would like
>to attempt to measure diversity while working on addressing and increasing
>it.  To that end, we are considering adding some possibly sensitive
>questions to the registration process, for example, gender.  Of course,
>they need not be answered and would be clearly labeled as optional.

   12.5 % of IAOC voting members are female.
    0.1%  of IAB members are female
    0 %   of IESG members are female.

Based on the above measurements the IAOC is more "diverse".  The IAOC 
already collects gender-related information.  The other information 
requested in the meeting registration form is strictly for meeting 
attendance purposes.  The sensitive questions referred to above have 
nothing to do with meeting attendance.

Which other individual properties would the IAOC like to measure?

Regards,
-sm 


From ynir@checkpoint.com  Thu Apr 11 13:09:03 2013
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 1397621F8EB9; Thu, 11 Apr 2013 13:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.343
X-Spam-Level: 
X-Spam-Status: No, score=-9.343 tagged_above=-999 required=5 tests=[AWL=1.256,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CD0KbdF0I3pI; Thu, 11 Apr 2013 13:09:02 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 0E57521F89D3; Thu, 11 Apr 2013 13:09:01 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r3BK90Fu032364; Thu, 11 Apr 2013 23:09:00 +0300
X-CheckPoint: {5167181E-2-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Thu, 11 Apr 2013 23:09:00 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "iaoc@ietf.org" <iaoc@ietf.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbhCbdza+rPBk2gjpsxRzCHdJjRQPiA
Date: Thu, 11 Apr 2013 20:09:00 +0000
Message-ID: <1C594EEE-8388-4D47-8D69-DECC2920B047@checkpoint.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
In-Reply-To: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.199]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5F5A90FDB1E8904EB9F9238D66148D00@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 11 Apr 2013 20:09:03 -0000

On Apr 11, 2013, at 6:11 PM, Ray Pelletier <rpelletier@isoc.org> wrote:

> All
>=20
> The IETF is concerned about diversity.  As good engineers, we would like
> to attempt to measure diversity while working on addressing and increasin=
g
> it.  To that end, we are considering adding some possibly sensitive
> questions to the registration process, for example, gender.  Of course,
> they need not be answered and would be clearly labeled as optional.
>=20
> The IAOC would like to hear from the community on this proposal.  It plan=
s to=20
> make a decision on its 18 April call in order to make the changes in time=
 for the=20
> Berlin registration and will consider all input received by 17 April. =20

Seems like I'm in a minority among responders, but I think it's a bad idea.

First, what is suggested is not a survey. It's part of the registration for=
m. This makes it totally non-anonymous. These sensitive questions are going=
 to be linked to name and affiliation on the form. There is good reason why=
 such studies are always done through anonymous survey. People answer quest=
ions differently when they're anonymous vs when they're not, skewing the re=
sults. Alfred Kinsey would not have gotten the results he got in his sexual=
ity surveys without strict anonymity for the responders. Definitely not in =
the 1940s.

The other issue is that this will produce statistically invalid results bec=
ause of non-response bias. Non-responders may be positively or negatively c=
orrelated with several groups the survey would like to measure.

Dave Crocker suggested getting an expert. I don't think that would help. Su=
ch an expert would tell you that the questions you can ask depends on the g=
roup you are asking. Questions that would be acceptable in one country, wou=
ld be inappropriate in another. In Israel people are likely to answer sensi=
tive questions truthfully, while in Germany concern for privacy might make =
these questions seem too personal. So how do you fit such a questionnaire t=
o a, well, diverse group such as meeting attendants?=20

I think skewed surveys are a worse basis for planning policy than just usin=
g common sense (yes, I know that's just another name for our biases). Surve=
ys lend a scientific aura to data that is effectively non-representative.

Yoav=

From spencer@wonderhamster.org  Thu Apr 11 13:19:02 2013
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 428A121F86A6; Thu, 11 Apr 2013 13:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.261
X-Spam-Level: 
X-Spam-Status: No, score=-102.261 tagged_above=-999 required=5 tests=[AWL=0.338, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K8Z7Dl9fS+s1; Thu, 11 Apr 2013 13:19:01 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id ABF7521F8630; Thu, 11 Apr 2013 13:19:01 -0700 (PDT)
Received: from [192.168.12.117] ([50.58.7.243]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0Lwagh-1Ue4qj3M35-017xSP; Thu, 11 Apr 2013 16:18:54 -0400
Message-ID: <51671AA9.4060203@wonderhamster.org>
Date: Thu, 11 Apr 2013 15:18:49 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <1C594EEE-8388-4D47-8D69-DECC2920B047@checkpoint.com>
In-Reply-To: <1C594EEE-8388-4D47-8D69-DECC2920B047@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:eFzIXXhqde3NB5rB+mL5Ha9gLnxRbG3TalGInxOif/U XWdu8OVit9gV81OicQdDh3e2cSN0Xq8W31bpl77MsVHju7XbNN P1Z+3V9QunFA96087O1EaJ1IG3XFlHvsa8UIZXE0Wz4DQdHm0L rtoGJR1wSJFdaQcjld76VdCE4yVDnaI3a/MB+64dNSNUVwzUGd nB2YyA5RGz0ftTDdd5RjoCSez/AWRyR9kVvR9sJXQbxNHh12n7 Lw3bJKRnOoOO4IDYTxAbm5E4C94TX3Pd8gxbNWrYOgWQvAJZ7T BGQ93jpm0yjSE8Fkz8kh+cY40Nxm4MmEviYUCENFo8X/FuF0+u EmsaY28YzUGrTr+kP3ZAUlJDiJxZhRrUTyQ0BggEo
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, 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, 11 Apr 2013 20:19:02 -0000

On 4/11/2013 3:09 PM, Yoav Nir wrote:

> Dave Crocker suggested getting an expert. I don't think that would help. Such an expert would tell you that the questions you can ask depends on the group you are asking. Questions that would be acceptable in one country, would be inappropriate in another. In Israel people are likely to answer sensitive questions truthfully, while in Germany concern for privacy might make these questions seem too personal. So how do you fit such a questionnaire to a, well, diverse group such as meeting attendants?

OK, are you proposing an anonymous survey, unrelated to registration?

Thanks,

Spencer

From Ted.Lemon@nominum.com  Thu Apr 11 13:21:16 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53A5121F86A6; Thu, 11 Apr 2013 13:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.291
X-Spam-Level: 
X-Spam-Status: No, score=-106.291 tagged_above=-999 required=5 tests=[AWL=0.308, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eMac3ansjdHy; Thu, 11 Apr 2013 13:21:15 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 950B121F859A; Thu, 11 Apr 2013 13:21:15 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUWcbOiFNeLG3CH9e7o9Gd7B42tPOgrXL@postini.com; Thu, 11 Apr 2013 13:21:15 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4DDA01B8092; Thu, 11 Apr 2013 13:21:11 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 47B88190061; Thu, 11 Apr 2013 13:21:11 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 11 Apr 2013 13:21:11 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbesxw5RhqwwUuIKG4LfyrlCZjR4Y8AgAAKbwA=
Date: Thu, 11 Apr 2013 20:21:10 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130411101504.0c42fed0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <FFB860CC12752C4FA84C76CC7289F06D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, "<iaoc@ietf.org>" <iaoc@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Apr 2013 20:21:16 -0000

On Apr 11, 2013, at 3:43 PM, SM <sm@resistor.net> wrote:
>  12.5 % of IAOC voting members are female.
>   0.1%  of IAB members are female
>   0 %   of IESG members are female.
>=20
> Based on the above measurements the IAOC is more "diverse".  The IAOC alr=
eady collects gender-related information.  The other information requested =
in the meeting registration form is strictly for meeting attendance purpose=
s.  The sensitive questions referred to above have nothing to do with meeti=
ng attendance.

With respect, this is sampling noise.  12.5% of 8 is 1.   Don't get me wron=
g=97it's great that we have some diversity on the IAOC, but I don't think a=
nybody should be patting themselves on the back just yet!

What diversity is the IAOC measuring?


From mstjohns@comcast.net  Thu Apr 11 13:26:39 2013
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 A053821F86F7 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 13:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NhWtqtzMli26 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 13:26:37 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 0123421F868B for <ietf@ietf.org>; Thu, 11 Apr 2013 13:26:30 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by QMTA11.westchester.pa.mail.comcast.net with comcast id NjDf1l0061vXlb85BkSWyD; Thu, 11 Apr 2013 20:26:30 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta17.westchester.pa.mail.comcast.net with comcast id NkSV1l00Q2kB7pQ3dkSVzg; Thu, 11 Apr 2013 20:26:30 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 11 Apr 2013 16:26:32 -0400
To: Ray Pelletier <rpelletier@isoc.org>,Discussion IETF <ietf@ietf.org>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1365711990; bh=memlWPQeyIek7QnIxlsfBOqNnqElKqQW3AF5oWGpO6k=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=KSubS6pNDzMwXsWWe9jdkCDg5OfUrYDTevr8v05LfFRDFjy3aLc6hjQMiz/QPWBpZ myQ+h91nBdb6Tslj2sT3caVgQzCoaJu4uykKzJydzEDBjLZUUdiMpkP3mfbR5E+Iuz BmSCOsSgVvyuYccTqUQiwRC/KVBYNh/1fDI1xWjHGUd3d1P5ekA+GhirX3JDBg5bAI 7PoAB2Uyd/n3BulonRk+aTey6viRORe0p94ti1hioffgiTWanXCvoDQrhGmWLt4NsF DMBhaGdlRvKZvgSr0e2qRc731x1da/fFoQbbkTnJUZNi/8OxJN7PhDDJdkmQjjBgxQ CVniwoIcfQrPQ==
Message-Id: <20130411202631.0123421F868B@ietfa.amsl.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, 11 Apr 2013 20:26:39 -0000

At 11:11 AM 4/11/2013, Ray Pelletier wrote:
>All
>
>The IETF is concerned about diversity.  As good engineers, we would like
>to attempt to measure diversity while working on addressing and increasing
>it.  To that end, we are considering adding some possibly sensitive
>questions to the registration process, for example, gender.  Of course,
>they need not be answered and would be clearly labeled as optional.
>
>The IAOC would like to hear from the community on this proposal.  It plans to 
>make a decision on its 18 April call in order to make the changes in time for the 
>Berlin registration and will consider all input received by 17 April.  


I think this is a pretty underspecified proposal.

In general, you use a survey to answer specific questions that have come up during postulate creation.  As far as I can tell, the postulate so far is "We need to be more diverse".  And the question is "Just how diverse are we actually?"  Or is the postulate "We need a more diverse leadership"?  And the question is: "Does the diversity of the IETF as a whole differ from the diversity of the leadership in a statistically significant manner"?

Or more along the lines of "We think our ability to do the work of the IETF is impacted by the general composition of the IETF and IETF leadership"?  And the questions are "What work is impacted by the current composition?"  and "WIll a change in the general diversity structure mitigate those impacts?"

If we go with the diversity stuff, I ask what scales of diversity?

Gender?  
National Origin?
Company Size?
Company Sector (e.g. do we care about bell heads vs net heads)?  
Academic vs Commercial vs Fabrege Egg Headius ?  (Marshal Rose's term for those who attend standards meetings for the purpose of attending standards meetings).
Race?
Sexual Orientation?
Geek vs Nerd?
Age?


My personal observations over the years is that I've gotten the most useful forms of diversity FOR THE IETF PURPOSES by looking across company/organization and company size, region (pac/america/europe/asia - but after Company), and academic vs corporate.   Occasionally Geek vs Nerd (open source vs for profit stuff).

The rest - not so much.


I'd like a more fully specified proposal before saying yea or nay. I believe it should include the purpose (e.g.what exactly are you trying to find out and where did the question come from?)  and a list of a axes of diversity that might impact on the purpose.

Thanks - Mike





>Thanks for your feedback.
>
>Ray
>IAD



From john-ietf@jck.com  Thu Apr 11 13:38:37 2013
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 2455121F8F43; Thu, 11 Apr 2013 13:38:37 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FlKtuw4o8A+3; Thu, 11 Apr 2013 13:38:36 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7EE3C21F8A11; Thu, 11 Apr 2013 13:38:36 -0700 (PDT)
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 1UQOGR-0006Pu-Lk; Thu, 11 Apr 2013 16:38:35 -0400
Date: Thu, 11 Apr 2013 16:38:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir@checkpoint.com>, iaoc@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <378D3AC42F8DEDC1293EB93F@JcK-HP8200.jck.com>
In-Reply-To: <1C594EEE-8388-4D47-8D69-DECC2920B047@checkpoint.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <1C594EEE-8388-4D47-8D69-DECC2920B047@checkpoint.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 <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, 11 Apr 2013 20:38:37 -0000

--On Thursday, April 11, 2013 20:09 +0000 Yoav Nir
<ynir@checkpoint.com> wrote:

> 
> On Apr 11, 2013, at 6:11 PM, Ray Pelletier
> <rpelletier@isoc.org> wrote:
> 
>> All
>> 
>> The IETF is concerned about diversity.  As good engineers, we
>> would like to attempt to measure diversity while working on
>> addressing and increasing it.  To that end, we are
>> considering adding some possibly sensitive questions to the
>> registration process, for example, gender.  Of course, they
>> need not be answered and would be clearly labeled as optional.
>...
> Seems like I'm in a minority among responders, but I think
> it's a bad idea.
> 
> First, what is suggested is not a survey. It's part of the
> registration form. This makes it totally non-anonymous. These
> sensitive questions are going to be linked to name and
>...
> Dave Crocker suggested getting an expert. I don't think that
> would help. Such an expert would tell you that the questions
> you can ask depends on the group you are asking. Questions
> that would be acceptable in one country, would be
> inappropriate in another. In Israel people are likely to
> answer sensitive questions truthfully, while in Germany
> concern for privacy might make these questions seem too
> personal. So how do you fit such a questionnaire to a, well,
> diverse group such as meeting attendants? 
> 
> I think skewed surveys are a worse basis for planning policy
> than just using common sense (yes, I know that's just another
> name for our biases). Surveys lend a scientific aura to data
> that is effectively non-representative.

I'm a little more optimistic about the right sort of expert than
Yoav is, but generally agree with his point of view (so not that
small a minority).  An additional observation and a suggestion:

-- Part of my non-IETF life/history permits me to claim some
expertise in survey design and avoiding or compensating for
various threats to validity, including some of those to which
Dave referred.  But I won't touch the sort of stuff you are
wanting to ask about -- it is just too sensitive, too
subjective, too tied up with national laws, and so on for a
rather long list.  Yoav and Ted have identified some of the
reasons, as have others.

-- If you are going to do something like this, I suggest that
you include an option on the registration form that, if checked,
will branch the registrant off to a separate survey that would
be appropriately anonymized (be sure you can explain the
method(s) you use to do that to this sometimes-suspicious
community). If one cannot easily get to the survey without
registering, the IETF and the results are protected from several
varieties of nonsense.  You will lose a few people who might
have participated in an inline survey, but will pick up some who
would be reluctant to answer the same questions if they were
integral to the registration documents.  You may also get
better/more reliable answers to possibly-sensitive questions, at
least if the questions themselves are well-designed.

best,
  john



From l.wood@surrey.ac.uk  Thu Apr 11 13:39:56 2013
Return-Path: <l.wood@surrey.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 553D821F8F43 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 13:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mfxL8ZUTg4in for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 13:39:55 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.165]) by ietfa.amsl.com (Postfix) with ESMTP id E667021F8F4A for <ietf@ietf.org>; Thu, 11 Apr 2013 13:39:54 -0700 (PDT)
Received: from [195.245.230.131:10556] by server-5.bemta-3.messagelabs.com id FC/D0-30636-69F17615; Thu, 11 Apr 2013 20:39:50 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-78.messagelabs.com!1365712789!28301765!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14952 invoked from network); 11 Apr 2013 20:39:50 -0000
Received: from unknown (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-10.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 11 Apr 2013 20:39:50 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Thu, 11 Apr 2013 21:39:49 +0100
From: <l.wood@surrey.ac.uk>
To: <paul.hoffman@vpnc.org>, <touch@isi.edu>
Date: Thu, 11 Apr 2013 21:39:48 +0100
Subject: RE: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: Ac425jHgXp4C5sblRvC2lSDlCjbmXQADCXw7
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E5A@EXMB01CMS.surrey.ac.uk>
References: <5166F8BD.7010308@isi.edu>, <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org>
In-Reply-To: <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 11 Apr 2013 20:39:56 -0000

+1 to Joe's comment.

Example: the existence of the extensibility bit in multipath tcp, which i u=
nderstand came out of a review by the iesg member responsible for security.
In that context, that would be outside the scope of any security review, an=
d the comments weren't raised in a personal capacity years earlier on the r=
elevant mailing list.

Sure, getting past iesg only cost multipath tcp a bit. But iesg members exc=
eeding their bounds as reviewers and leaving a personal mark seems commonpl=
ace. iesg members are there for expertise in their area and to provide that=
 expertise in focused reviews, not to block until a protocol is redesigned =
to suit their personal tastes. (That transport expertise is lacking on iesg=
 last I looked and everyone believes they're an expert in transport  - 'hey=
, why can't we just turn off udp checksums for sctp over udp? It's faster!'=
 - another iesg redesign attempt overriding considered expertise of a workg=
roup - isn't helping here.)

There are two examples I know of, off the top of my head, telated to transp=
ort because that's my area of interest. Can others provide further examples=
?

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Paul Hoffm=
an [paul.hoffman@vpnc.org]
Sent: 11 April 2013 19:55
To: Joe Touch
Cc: IETF discussion list
Subject: Re: Purpose of IESG Review

On Apr 11, 2013, at 10:54 AM, Joe Touch <touch@isi.edu> wrote:

> As an author who has had (and has) multiple documents in IESG review, I'v=
e noticed an increasing trend of this step to go beyond (IMO) its documente=
d and original intent (BCP 9, currently RFC 2026):
>
>   The IESG shall determine whether or not a specification submitted to
>   it according to section 6.1.1 satisfies the applicable criteria for
>   the recommended action (see sections 4.1 and 4.2), and shall in
>   addition determine whether or not the technical quality and clarity
>   of the specification is consistent with that expected for the
>   maturity level to which the specification is recommended.
>
> Although I appreciate that IESG members are often overloaded, and the IES=
G Review step is often the first time many see these documents, I believe t=
hey should be expected to more clearly differentiate their "IESG Review" (b=
ased on the above criteria) - and its accompanying Position ballot, with th=
eir personal review.
>
> My concern is that by conflating their IESG position with their personal =
review, the document process is inappropriately delayed and that documents =
are modified to appease a small community that does not justify its positio=
n as representative.
>
> How do others feel about this?

That it is too vague to comment on?

Please point to specific examples where you feel an IESG member's review we=
nt beyond determining the technical quality or clarity of the specification=
. That would help make the sure-to-be ensuing flamefest more light-filled.

--Paul Hoffman

From spencer@wonderhamster.org  Thu Apr 11 13:46:44 2013
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 2647421F8F5C for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 13:46:44 -0700 (PDT)
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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hpM2l84AXTcN for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 13:46:41 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 733DB21F8F43 for <ietf@ietf.org>; Thu, 11 Apr 2013 13:46:41 -0700 (PDT)
Received: from [192.168.12.117] ([50.58.7.243]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MfWHD-1UEfDc1K8Z-00OinA; Thu, 11 Apr 2013 16:46:22 -0400
Message-ID: <5167211A.8080807@wonderhamster.org>
Date: Thu, 11 Apr 2013 15:46:18 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V02:K0:vUWgmCu/cNncGw6q1Q08g6SSVfpOSs+ZrdjBMGRxqn+ xYK6IRIMnIhnyg7DOZiO6j4A43rvkwJuxQw0sx+AekLyTklPjG KKFbraSS0GdhyduYqdY42de6MZY7/N4hl5p+AhFJRHwnH6JJSk 4WE1xaSuvcRaGHRJ4exyeYPbBgGJUYw1PMKU3b5ZOnV3FBAH3c ZlukX+FFOdop1BoXW8i5IW4+3PSUn5nglOMpyv0MYl+kKn8a7B Pc7TRn6AL/ioOOya58lyYu8Q/kQMXeKXjqyOxOlu1twvs181d+ jMun90MxRQaCKecqpVqvwKgvXkEnv8ehXGmlFekAyP+vFl6R/V P/nrsSQ3SRz9xQnE3bPzi+87poy8DP9AHAzL8cUge
Cc: SM <sm@resistor.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, 11 Apr 2013 20:46:44 -0000

Hi, SM,

This may be a misprint ...

On 4/11/2013 3:21 PM, Ted Lemon wrote:
> On Apr 11, 2013, at 3:43 PM, SM <sm@resistor.net> wrote:
>>   12.5 % of IAOC voting members are female.
>>    0.1%  of IAB members are female
>>    0 %   of IESG members are female.
>>
>> Based on the above measurements the IAOC is more "diverse".  The IAOC already collects gender-related information.  The other information requested in the meeting registration form is strictly for meeting attendance purposes.  The sensitive questions referred to above have nothing to do with meeting attendance.
>
> With respect, this is sampling noise.  12.5% of 8 is 1.   Don't get me wrong—it's great that we have some diversity on the IAOC, but I don't think anybody should be patting themselves on the back just yet!
>
> What diversity is the IAOC measuring?

By my count, the current IAB membership is 15 (12 Nomcom-selected, plus 
the IETF chair, plus the ExecDir, plus the IRTF Chair - these last two 
are ex-officio and non-voting).

If the IAB means "members", the number for females, as far as I know(*), 
is 2/15, or 13 percent. If it means voting members, the number for 
females is 1/13, or just under 8 percent.

Other diversities also matter, and I'm just doing math here (**).

Spencer

(*) In my spare time, I'm co-president of PFLAG Dallas, which is a local 
chapter of PFLAG, an abbreviated abbreviation of "Parents, Families and 
Friends of Lesbian, Gay, Bisexual _and Transgender_ people", so I know I 
can't claim definitive knowledge on who's what ... only on what people 
appear to be.

(**) I think diversity matters, and didn't want us to look less 
gender-diverse than we are ...

From dmm@1-4-5.net  Thu Apr 11 13:50:42 2013
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 D646421F8FF5 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 13:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Kt6AJJD0HaL for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 13:50:41 -0700 (PDT)
Received: from mail-qe0-f52.google.com (mail-qe0-f52.google.com [209.85.128.52]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDEF21F8F43 for <ietf@ietf.org>; Thu, 11 Apr 2013 13:50:41 -0700 (PDT)
Received: by mail-qe0-f52.google.com with SMTP id jy17so1153227qeb.25 for <ietf@ietf.org>; Thu, 11 Apr 2013 13:50:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=ttdUw0isTxd0yH5nTw/LE/8ti/9IvOiRp1b2rhZoRNQ=; b=VOV2JPY9YdSLY7nRuyWli+oOF6GWDu0WLRr1Wqgg+16RZAj71u4JlBkcpvDlnTkbcn +y29KmkGV4TZy17cTkco/ylszU3AamWgR2+MHqg89mHCPuGmpI4B4AZmPW4w9+YIeNBC mbsMgcZQF6M2zNoiDUZ85cN8gGPL8v+ggDC7zBDOkXClTI5O9egzB6yWWpaPPzk6gxON JphwhBnXqrPldv03Uec2ZrmtmFH7fuhJCwvLAEqgmtVhoXcfFRSZpEYMcoTX432pdtXH gOJ8D57JwkzoWtVRhnR4Cps8vEMOZobFHo+Ir+LDR9IPRqTSe13OBZzCVGKiXGZ6DxGN rgtw==
MIME-Version: 1.0
X-Received: by 10.229.69.16 with SMTP id x16mr3091864qci.53.1365713441097; Thu, 11 Apr 2013 13:50:41 -0700 (PDT)
Received: by 10.49.130.74 with HTTP; Thu, 11 Apr 2013 13:50:40 -0700 (PDT)
X-Originating-IP: [75.35.230.210]
In-Reply-To: <5167211A.8080807@wonderhamster.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org>
Date: Thu, 11 Apr 2013 13:50:40 -0700
Message-ID: <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: David Meyer <dmm@1-4-5.net>
To: Spencer Dawkins <spencer@wonderhamster.org>
Content-Type: multipart/alternative; boundary=0021cc02206685b23304da1bf0df
X-Gm-Message-State: ALoCoQl6CyHTY3UHwZgEJKvvCIRsvzCHOK1gNFjXLQzSGCZN9RgpoxoHcTPjrynvp9NcNQAb3q7k
Cc: SM <sm@resistor.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, 11 Apr 2013 20:50:43 -0000

--0021cc02206685b23304da1bf0df
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 11, 2013 at 1:46 PM, Spencer Dawkins
<spencer@wonderhamster.org>wrote:

> Hi, SM,
>
> This may be a misprint ...
>
> On 4/11/2013 3:21 PM, Ted Lemon wrote:
>
>> On Apr 11, 2013, at 3:43 PM, SM <sm@resistor.net> wrote:
>>
>>>   12.5 % of IAOC voting members are female.
>>>    0.1%  of IAB members are female
>>>    0 %   of IESG members are female.
>>>
>>> Based on the above measurements the IAOC is more "diverse".  The IAOC
>>> already collects gender-related information.  The other information
>>> requested in the meeting registration form is strictly for meeting
>>> attendance purposes.  The sensitive questions referred to above have
>>> nothing to do with meeting attendance.
>>>
>>
>> With respect, this is sampling noise.  12.5% of 8 is 1.   Don't get me
>> wrong=97it's great that we have some diversity on the IAOC, but I don't =
think
>> anybody should be patting themselves on the back just yet!
>>
>> What diversity is the IAOC measuring?
>>
>
> By my count, the current IAB membership is 15 (12 Nomcom-selected, plus
> the IETF chair, plus the ExecDir, plus the IRTF Chair - these last two ar=
e
> ex-officio and non-voting).
>
> If the IAB means "members", the number for females, as far as I know(*),
> is 2/15, or 13 percent. If it means voting members, the number for female=
s
> is 1/13, or just under 8 percent.
>
> Other diversities also matter, and I'm just doing math here (**).
>

Agreed, however, it would seem to me that at least one question that one
might as is whether these percentages are representative of the IETF
population at large.

--dmm


>
> Spencer
>
> (*) In my spare time, I'm co-president of PFLAG Dallas, which is a local
> chapter of PFLAG, an abbreviated abbreviation of "Parents, Families and
> Friends of Lesbian, Gay, Bisexual _and Transgender_ people", so I know I
> can't claim definitive knowledge on who's what ... only on what people
> appear to be.
>
> (**) I think diversity matters, and didn't want us to look less
> gender-diverse than we are ...
>

--0021cc02206685b23304da1bf0df
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Thu, Apr 11, 2013 at 1:46 PM, Spencer=
 Dawkins <span dir=3D"ltr">&lt;<a href=3D"mailto:spencer@wonderhamster.org"=
 target=3D"_blank">spencer@wonderhamster.org</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
Hi, SM,<br>
<br>
This may be a misprint ...<br>
<br>
On 4/11/2013 3:21 PM, Ted Lemon wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Apr 11, 2013, at 3:43 PM, SM &lt;<a href=3D"mailto:sm@resistor.net" targ=
et=3D"_blank">sm@resistor.net</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 12.5 % of IAOC voting members are female.<br>
=A0 =A00.1% =A0of IAB members are female<br>
=A0 =A00 % =A0 of IESG members are female.<br>
<br>
Based on the above measurements the IAOC is more &quot;diverse&quot;. =A0Th=
e IAOC already collects gender-related information. =A0The other informatio=
n requested in the meeting registration form is strictly for meeting attend=
ance purposes. =A0The sensitive questions referred to above have nothing to=
 do with meeting attendance.<br>

</blockquote>
<br>
With respect, this is sampling noise. =A012.5% of 8 is 1. =A0 Don&#39;t get=
 me wrong=97it&#39;s great that we have some diversity on the IAOC, but I d=
on&#39;t think anybody should be patting themselves on the back just yet!<b=
r>

<br>
What diversity is the IAOC measuring?<br>
</blockquote>
<br>
By my count, the current IAB membership is 15 (12 Nomcom-selected, plus the=
 IETF chair, plus the ExecDir, plus the IRTF Chair - these last two are ex-=
officio and non-voting).<br>
<br>
If the IAB means &quot;members&quot;, the number for females, as far as I k=
now(*), is 2/15, or 13 percent. If it means voting members, the number for =
females is 1/13, or just under 8 percent.<br>
<br>
Other diversities also matter, and I&#39;m just doing math here (**).<br></=
blockquote><div><br></div><div>Agreed, however, it would seem to me that at=
 least one question that one might as is whether these percentages are repr=
esentative of the IETF population at large.</div>
<div><br></div><div>--dmm</div><div>=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<br>
Spencer<br>
<br>
(*) In my spare time, I&#39;m co-president of PFLAG Dallas, which is a loca=
l chapter of PFLAG, an abbreviated abbreviation of &quot;Parents, Families =
and Friends of Lesbian, Gay, Bisexual _and Transgender_ people&quot;, so I =
know I can&#39;t claim definitive knowledge on who&#39;s what ... only on w=
hat people appear to be.<br>

<br>
(**) I think diversity matters, and didn&#39;t want us to look less gender-=
diverse than we are ...<br>
</blockquote></div><br>

--0021cc02206685b23304da1bf0df--

From Ted.Lemon@nominum.com  Thu Apr 11 14:07:08 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE0F21F8793 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.305
X-Spam-Level: 
X-Spam-Status: No, score=-106.305 tagged_above=-999 required=5 tests=[AWL=0.293, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iQ0mmh-svodJ for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:07:07 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id ECB4521F8920 for <ietf@ietf.org>; Thu, 11 Apr 2013 14:07:06 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUWcl+jZ3hBe+nhGFspUaww+k69lmyRyg@postini.com; Thu, 11 Apr 2013 14:07:07 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4BA0F1B80AE for <ietf@ietf.org>; Thu, 11 Apr 2013 14:07:06 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 42D01190061; Thu, 11 Apr 2013 14:07:06 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 11 Apr 2013 14:07:06 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: David Meyer <dmm@1-4-5.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbesxw5RhqwwUuIKG4LfyrlCZjR4Y8AgAAKbwCAAAcIAIAAATgAgAAEloA=
Date: Thu, 11 Apr 2013 21:07:05 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com>
In-Reply-To: <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751412A3mbx01winnominum_"
MIME-Version: 1.0
Cc: SM <sm@resistor.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, 11 Apr 2013 21:07:08 -0000

--_000_8D23D4052ABE7A4490E77B1A012B6307751412A3mbx01winnominum_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Apr 11, 2013, at 4:50 PM, David Meyer <dmm@1-4-5.net<mailto:dmm@1-4-5.ne=
t>> wrote:
Agreed, however, it would seem to me that at least one question that one mi=
ght as is whether these percentages are representative of the IETF populati=
on at large.

A rough eyeball check at the plenary in Orlando suggested that it was not. =
  But we don't have any statistics.   Personally I'm not sure how much the =
precise numbers matter when they are as low as they appear to be at present=
, though.


--_000_8D23D4052ABE7A4490E77B1A012B6307751412A3mbx01winnominum_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <0420BE2C56A42C45AD4F4DB4C9EB16E3@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Apr 11, 2013, at 4:50 PM, David Meyer &lt;<a href=3D"mailto:dmm@1-4=
-5.net">dmm@1-4-5.net</a>&gt; wrote:</div>
<blockquote type=3D"cite">
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
Agreed, however, it would seem to me that at least one question that one mi=
ght as is whether these percentages are representative of the IETF populati=
on at large.</div>
</blockquote>
</div>
<br>
<div>A rough eyeball check at the plenary in Orlando suggested that it was =
not. &nbsp; But we don't have any statistics. &nbsp; Personally I'm not sur=
e how much the precise numbers matter when they are as low as they appear t=
o be at present, though.</div>
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751412A3mbx01winnominum_--

From dmm@1-4-5.net  Thu Apr 11 14:10:25 2013
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 D178D21F902A for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDqYbwn0uK4s for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:10:25 -0700 (PDT)
Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0A23321F9025 for <ietf@ietf.org>; Thu, 11 Apr 2013 14:10:24 -0700 (PDT)
Received: by mail-lb0-f170.google.com with SMTP id x11so2037110lbi.29 for <ietf@ietf.org>; Thu, 11 Apr 2013 14:10:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=7hIVkfxgkogcPqJClH5OG9Mz07Rw+nPhmf2vhczdjQ4=; b=SJ1nU/yatNQvEOA6SXInoTIBnacdHU0nXL5krT2yzzvRmOPje2YH8MBC4VoNWZfo1j hSfPJsnjizYCLb6bfc5d4EflayhqrkZApgDzrlJ5N71V9jqH0GvJCPAS8dHrowduvcMo w6F6OKmHTOS1RSojsgX+XZwd5oOMhC31XgsPAGVW2RqKG7LmQdOtyvlPOXw607UMCaLX ByxOQzYFFfAwpSRyccHpfNYmAyNiPYNQnIq6DN3Fw/V75yf6jDmfc2bYN152HW0RaShI mmNLi9VrnBV9tTQx/9jfznMXVC8hDwRowagEm5Csp/UjLdfxPQJO90+pvNAC/nbcZB0H qWBw==
MIME-Version: 1.0
X-Received: by 10.112.199.230 with SMTP id jn6mr4089996lbc.131.1365714623769;  Thu, 11 Apr 2013 14:10:23 -0700 (PDT)
Received: by 10.112.104.10 with HTTP; Thu, 11 Apr 2013 14:10:23 -0700 (PDT)
X-Originating-IP: [75.35.230.210]
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com>
Date: Thu, 11 Apr 2013 14:10:23 -0700
Message-ID: <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: David Meyer <dmm@1-4-5.net>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11c3851603c68804da1c3718
X-Gm-Message-State: ALoCoQmA/SvnnUBUiIbxuHzY0xvDL8TdXIkg422T33tH4BpgvVra8Yfu1g3SAlpv8YrK7/80KAm5
Cc: SM <sm@resistor.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, 11 Apr 2013 21:10:26 -0000

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

On Thu, Apr 11, 2013 at 2:07 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

>  On Apr 11, 2013, at 4:50 PM, David Meyer <dmm@1-4-5.net> wrote:
>
>  Agreed, however, it would seem to me that at least one question that one
> might as is whether these percentages are representative of the IETF
> population at large.
>
>
> A rough eyeball check at the plenary in Orlando suggested that it was not.
>   But we don't have any statistics.   Personally I'm not sure how much the
> precise numbers matter when they are as low as they appear to be at
> present, though.
>

Yes, but that is a different question. --dmm

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

<br><br><div class=3D"gmail_quote">On Thu, Apr 11, 2013 at 2:07 PM, Ted Lem=
on <span dir=3D"ltr">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com" target=3D=
"_blank">Ted.Lemon@nominum.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">




<div style=3D"word-wrap:break-word">
<div>
<div>On Apr 11, 2013, at 4:50 PM, David Meyer &lt;<a href=3D"mailto:dmm@1-4=
-5.net" target=3D"_blank">dmm@1-4-5.net</a>&gt; wrote:</div>
<blockquote type=3D"cite">
<div style=3D"font-family:Optima;font-size:medium;font-style:normal;font-va=
riant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;te=
xt-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:norma=
l;word-spacing:0px">

Agreed, however, it would seem to me that at least one question that one mi=
ght as is whether these percentages are representative of the IETF populati=
on at large.</div>
</blockquote>
</div>
<br>
<div>A rough eyeball check at the plenary in Orlando suggested that it was =
not. =A0 But we don&#39;t have any statistics. =A0 Personally I&#39;m not s=
ure how much the precise numbers matter when they are as low as they appear=
 to be at present, though.</div>
</div></blockquote><div><br></div><div>Yes, but that is a different questio=
n. --dmm=A0</div></div><br>

--001a11c3851603c68804da1c3718--

From Ted.Lemon@nominum.com  Thu Apr 11 14:15:00 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D34321F9049 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.312
X-Spam-Level: 
X-Spam-Status: No, score=-106.312 tagged_above=-999 required=5 tests=[AWL=0.287, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PiOvEhl11fju for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:15:00 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 16C2D21F9036 for <ietf@ietf.org>; Thu, 11 Apr 2013 14:15:00 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUWcn08W7moNS955qVYB01JHDc01bj1uz@postini.com; Thu, 11 Apr 2013 14:15:00 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id CBA3C1B80A3 for <ietf@ietf.org>; Thu, 11 Apr 2013 14:14:59 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id C2A68190061; Thu, 11 Apr 2013 14:14:59 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 11 Apr 2013 14:14:59 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: David Meyer <dmm@1-4-5.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbesxw5RhqwwUuIKG4LfyrlCZjR4Y8AgAAKbwCAAAcIAIAAATgAgAAEloCAAADsgIAAAUgA
Date: Thu, 11 Apr 2013 21:14:59 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>
In-Reply-To: <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4FCB0E76EDBB85448BB4232F19EE45C7@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SM <sm@resistor.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, 11 Apr 2013 21:15:00 -0000

On Apr 11, 2013, at 5:10 PM, David Meyer <dmm@1-4-5.net>
> Yes, but that is a different question. --dmm=20


IOW, you are suggesting that the percentages among non-attending participan=
ts may be substantially different than the percentages among attending part=
icipants?   That's a point worth studying, but wouldn't likely be addressed=
 by the proposed survey, unless some way were added to include non-attendin=
g participants.


From adrian@olddog.co.uk  Thu Apr 11 14:17:41 2013
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 77E3D21F8EB7 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.383
X-Spam-Level: 
X-Spam-Status: No, score=-2.383 tagged_above=-999 required=5 tests=[AWL=0.216,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSc3g3mEbtLj for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:17:40 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 3F13621F8E5C for <ietf@ietf.org>; Thu, 11 Apr 2013 14:17:40 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3BLHcr9030798;  Thu, 11 Apr 2013 22:17:39 +0100
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 r3BLHcIb030792 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 11 Apr 2013 22:17:38 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l.wood@surrey.ac.uk>
References: <5166F8BD.7010308@isi.edu>, <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <290E20B455C66743BE178C5C84F12408223F494E5A@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E5A@EXMB01CMS.surrey.ac.uk>
Subject: RE: Purpose of IESG Review
Date: Thu, 11 Apr 2013 22:17:36 +0100
Message-ID: <048a01ce36f9$fdfac5f0$f9f051d0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-gb
Thread-Index: AQExZnB1jZJE0M6ORFVEYlcq0/omNQGPASWTAVNnkWiZ9BD8sA==
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, 11 Apr 2013 21:17:41 -0000

Hi Ian,

Examples are useful because they give the IESG something to chew on. If you
don't call us when we do "bad stuff" we might never know.

Examples can be dangerous because we can rat-hole into the specific rather than
the general, but i would like to use your example as data point to get some more
information that can possibly be generalised.

> Example: the existence of the extensibility bit in multipath tcp, which i
> understand came out of a review by the iesg member responsible for security.
> In that context, that would be outside the scope of any security review, and
the
> comments weren't raised in a personal capacity years earlier on the relevant
> mailing list.

Do people believe that the extensibility bit should not have been added?
I.e., is it a dumb or unnecessary thing that was forced on the community by the
IESG?
Maybe it is "harmless" so everyone said yes to get the document published.
Maybe the IESG had some "insight" suggesting that it was important to
future-proof the protocol even though the community didn't think it important.
Maybe it was a really cool idea that everyone missed.

I'm not asking in order to have a fight about whether the AD was right or wrong.
But I would like to understand more about the impact of this type of "blocking"
Discuss.

My point here is that sometimes it happens that ADs spot holes in protocols. In
those cases, I think we could live with publishing the RFCs and fixing them
later, but it is on the whole better to fix the issues at the time they are
spotted rather than later. The problem comes that an AD (especially out of
expertise) cannot tell between "I think there might be a problem here" and "I
know this is a serious bug".

I believe that the clue is in the word "Discuss" and I hope that I (at least) am
willing to listen when the response is "we thought about it, it's not a big
problem." Perhaps people will tell me I am not so good at listening! I know
other ADs also strive to that as an ideal, so perhaps we have something of a
communications breakdown...

Discuss is not meant to mean "and you shall not move unless you do exactly what
I say." It should mean "Please help me to be happy about publishing this
document because what I really want is you to publish the best possible document
as quickly as possible."

Thanks,
Adrian






> 
> Sure, getting past iesg only cost multipath tcp a bit. But iesg members
exceeding
> their bounds as reviewers and leaving a personal mark seems commonplace. iesg
> members are there for expertise in their area and to provide that expertise in
> focused reviews, not to block until a protocol is redesigned to suit their
personal
> tastes. (That transport expertise is lacking on iesg last I looked and
everyone
> believes they're an expert in transport  - 'hey, why can't we just turn off
udp
> checksums for sctp over udp? It's faster!' - another iesg redesign attempt
> overriding considered expertise of a workgroup - isn't helping here.)
> 
> There are two examples I know of, off the top of my head, telated to transport
> because that's my area of interest. Can others provide further examples?
> 
> Lloyd Wood
> http://sat-net.com/L.Wood/
> 
> 
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Paul Hoffman
> [paul.hoffman@vpnc.org]
> Sent: 11 April 2013 19:55
> To: Joe Touch
> Cc: IETF discussion list
> Subject: Re: Purpose of IESG Review
> 
> On Apr 11, 2013, at 10:54 AM, Joe Touch <touch@isi.edu> wrote:
> 
> > As an author who has had (and has) multiple documents in IESG review, I've
> noticed an increasing trend of this step to go beyond (IMO) its documented and
> original intent (BCP 9, currently RFC 2026):
> >
> >   The IESG shall determine whether or not a specification submitted to
> >   it according to section 6.1.1 satisfies the applicable criteria for
> >   the recommended action (see sections 4.1 and 4.2), and shall in
> >   addition determine whether or not the technical quality and clarity
> >   of the specification is consistent with that expected for the
> >   maturity level to which the specification is recommended.
> >
> > Although I appreciate that IESG members are often overloaded, and the IESG
> Review step is often the first time many see these documents, I believe they
> should be expected to more clearly differentiate their "IESG Review" (based on
> the above criteria) - and its accompanying Position ballot, with their
personal
> review.
> >
> > My concern is that by conflating their IESG position with their personal
review,
> the document process is inappropriately delayed and that documents are
> modified to appease a small community that does not justify its position as
> representative.
> >
> > How do others feel about this?
> 
> That it is too vague to comment on?
> 
> Please point to specific examples where you feel an IESG member's review went
> beyond determining the technical quality or clarity of the specification. That
> would help make the sure-to-be ensuing flamefest more light-filled.
> 
> --Paul Hoffman


From eckert@cisco.com  Thu Apr 11 14:41:16 2013
Return-Path: <eckert@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 C98EB21F86C5 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.398
X-Spam-Level: 
X-Spam-Status: No, score=-10.398 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ty1PMbaFcDR for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 14:41:14 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 8F66A21F86C4 for <ietf@ietf.org>; Thu, 11 Apr 2013 14:41:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=907; q=dns/txt; s=iport; t=1365716474; x=1366926074; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=XgBhI9HDEJRkp2f3Be54LYfHI/Hf7TBbr8nNUNRct+c=; b=NMWedY7FpMh8s90sss7/ilr6I+QYNI0QcKmn4CKa0BiYF2tIhhAA9dOe W5S6jkefL7gfgNWezSSGL+CnazRgLYQtfpEeSTHKe1Pnw3BdPE0Ox2Y6T 6DCN58UtXmqt/AFvgXkncO3lbFnIrKasDfTpddEi4AeM9cKGsnSlrYdrr k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArAFABUtZ1GrRDoI/2dsb2JhbABQgwaDHb5igQcWdIIfAQEBBBgiPxALEgYJJQ8FNRQTiBO9U48WB4JgYQOJA41+AZEPgysc
X-IronPort-AV: E=Sophos;i="4.87,458,1363132800"; d="scan'208";a="78326173"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 11 Apr 2013 21:41:13 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3BLf7pV019985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Apr 2013 21:41:07 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r3BLcaE7017149;  Thu, 11 Apr 2013 14:38:51 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r3BLcZkq017148; Thu, 11 Apr 2013 14:38:35 -0700
Date: Thu, 11 Apr 2013 14:38:35 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130411213835.GA8968@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>
User-Agent: Mutt/1.4.2.2i
Cc: SM <sm@resistor.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, 11 Apr 2013 21:41:16 -0000

Suggesting that simply diversity stats across all IETF participants can help
to deduce anything about leadership diversity bias is ignoring qualification
and availability of candidates. Thats why i proposed the questions i would like to see
in a questionaire.


On Thu, Apr 11, 2013 at 09:14:59PM +0000, Ted Lemon wrote:
> On Apr 11, 2013, at 5:10 PM, David Meyer <dmm@1-4-5.net>
> > Yes, but that is a different question. --dmm 
> 
> 
> IOW, you are suggesting that the percentages among non-attending participants may be substantially different than the percentages among attending participants?   That's a point worth studying, but wouldn't likely be addressed by the proposed survey, unless some way were added to include non-attending participants.
> 

-- 
---
Toerless Eckert, eckert@cisco.com
Cisco NSSTG Systems & Technology Architecture
SDN: Let me play with the network, mommy!


From john@jlc.net  Thu Apr 11 15:08:03 2013
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 C54A221F86F7 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.199
X-Spam-Level: 
X-Spam-Status: No, score=-107.199 tagged_above=-999 required=5 tests=[AWL=-0.599, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLreQ3u0oW0s for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:08:01 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id A182D21F85DA for <ietf@ietf.org>; Thu, 11 Apr 2013 15:08:01 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id B5E5B33C26; Thu, 11 Apr 2013 18:08:01 -0400 (EDT)
Date: Thu, 11 Apr 2013 18:08:01 -0400
From: John Leslie <john@jlc.net>
To: l.wood@surrey.ac.uk
Subject: Re: Purpose of IESG Review
Message-ID: <20130411220801.GI71270@verdi>
References: <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <290E20B455C66743BE178C5C84F12408223F494E5A@EXMB01CMS.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E5A@EXMB01CMS.surrey.ac.uk>
User-Agent: Mutt/1.4.1i
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, 11 Apr 2013 22:08:03 -0000

l.wood@surrey.ac.uk <l.wood@surrey.ac.uk> wrote:
> 
> +1 to Joe's comment.
> 
> Example: the existence of the extensibility bit in multipath tcp,
> which i understand came out of a review by the iesg member responsible
> for security.

   I assume you're talking RFC 6824. I recommend reading the Narrative
Minutes of September 13th:

http://www.ietf.org/iesg/minutes/2012/narrative-minutes-2012-09-13.html

There were DISCUSSes from Stephen Farrell (Security), Barry Leiba
(Applications), Robert Sparks (RAI), and Sean Turner (Security).
Stephen Farrell did complain about a negotiation scheme that only allowed
seven security algorithms; and asked "how you could practically extend
this design for stronger cryptographic security".

> In that context, that would be outside the scope of any security
> review,

   Hardly! Those are exactly what I would hope for in a Security review.

> and the comments weren't raised in a personal capacity years earlier
> on the relevant mailing list.

   I'm not going to research that; but it seems hardly relevant...

> Sure, getting past iesg only cost multipath tcp a bit.

   (which, BTW, I strongly endorse!)

> But iesg members exceeding their bounds as reviewers and leaving a
> personal mark seems commonplace.

   Perception is easily mistaken for reality. :^(

   But if you look at the datatracker history:

http://datatracker.ietf.org/doc/draft-ietf-mptcp-multiaddressed/history/

you'll see that all four DISCUSSes were cleared by October 22.

   Considering that this document started life in June of 2010, and
was a major enhancement of TCP, 40 days doesn't seem excessive, IMHO.

> iesg members are there for expertise in their area and to provide that
> expertise in focused reviews,

   Note that there's really a lot of overlap between areas: so "focused"
may not be the right criterion.

> not to block until a protocol is redesigned to suit their personal
> tastes.

   I am told this used to happen. I have not experienced it in the five
years I have been scribing.

====

   I really don't know how to change the perception -- but I strongly
recommend referring to the Narrative Minutes. Hopefully that history
will be preserved "forever".

--
John Leslie <john@jlc.net>

From dhc@dcrocker.net  Thu Apr 11 15:10:08 2013
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 2B61721F85DA for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A75Kh2ZGK+qp for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:10:03 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5DD9C21F8733 for <ietf@ietf.org>; Thu, 11 Apr 2013 15:10:02 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3BMA0Gt020505 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Apr 2013 15:10:00 -0700
Message-ID: <516734B3.2080400@dcrocker.net>
Date: Thu, 11 Apr 2013 15:09:55 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <20130411202631.0123421F868B@ietfa.amsl.com>
In-Reply-To: <20130411202631.0123421F868B@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, 11 Apr 2013 15:10:01 -0700 (PDT)
Cc: Discussion 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, 11 Apr 2013 22:10:08 -0000

On 4/11/2013 1:26 PM, Michael StJohns wrote:
> I think this is a pretty underspecified proposal.
>
> In general, you use a survey to answer specific questions that have come up during postulate creation.
...
> I'd like a more fully specified proposal before saying yea or nay.

+10

Those are some of the reasons I suggested the IAOC get an appropriate 
expert.

As has been amply recounted by the various postings, this is a complex 
and sensitive topic that is far too easily mishandled -- semantically, 
socially and legally.

Get the help of someone with the necessary, specific skills.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From adrian@olddog.co.uk  Thu Apr 11 15:16:39 2013
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 D120F21F89D3 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.403
X-Spam-Level: 
X-Spam-Status: No, score=-2.403 tagged_above=-999 required=5 tests=[AWL=0.196,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mPYV9gLnm+Zi for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:16:38 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id BEB3A21F8940 for <ietf@ietf.org>; Thu, 11 Apr 2013 15:16:32 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3BMGDKT027353;  Thu, 11 Apr 2013 23:16:13 +0100
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 r3BMGCES027337 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 11 Apr 2013 23:16:12 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l.wood@surrey.ac.uk>
References: <5166F8BD.7010308@isi.edu>, <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org>	<290E20B455C66743BE178C5C84F12408223F494E5A@EXMB01CMS.surrey.ac.uk> <048a01ce36f9$fdfac5f0$f9f051d0$@olddog.co.uk>
In-Reply-To: <048a01ce36f9$fdfac5f0$f9f051d0$@olddog.co.uk>
Subject: RE: Purpose of IESG Review
Date: Thu, 11 Apr 2013 23:16:11 +0100
Message-ID: <04c901ce3702$2caab3d0$86001b70$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-gb
Thread-Index: AQExZnB1jZJE0M6ORFVEYlcq0/omNQGPASWTAVNnkWgBRCOqDpnqAo7Q
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, 11 Apr 2013 22:16:40 -0000

And that should, of course, have read "Hi Lloyd"
Sorry about that, Lloyd.
The rest of the message still stands.
Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Adrian
> Farrel
> Sent: 11 April 2013 22:18
> To: l.wood@surrey.ac.uk
> Cc: ietf@ietf.org
> Subject: RE: Purpose of IESG Review
> 
> Hi Ian,
> 
> Examples are useful because they give the IESG something to chew on. If you
> don't call us when we do "bad stuff" we might never know.
> 
> Examples can be dangerous because we can rat-hole into the specific rather
than
> the general, but i would like to use your example as data point to get some
more
> information that can possibly be generalised.
> 
> > Example: the existence of the extensibility bit in multipath tcp, which i
> > understand came out of a review by the iesg member responsible for security.
> > In that context, that would be outside the scope of any security review, and
> the
> > comments weren't raised in a personal capacity years earlier on the relevant
> > mailing list.
> 
> Do people believe that the extensibility bit should not have been added?
> I.e., is it a dumb or unnecessary thing that was forced on the community by
the
> IESG?
> Maybe it is "harmless" so everyone said yes to get the document published.
> Maybe the IESG had some "insight" suggesting that it was important to
> future-proof the protocol even though the community didn't think it important.
> Maybe it was a really cool idea that everyone missed.
> 
> I'm not asking in order to have a fight about whether the AD was right or
wrong.
> But I would like to understand more about the impact of this type of
"blocking"
> Discuss.
> 
> My point here is that sometimes it happens that ADs spot holes in protocols.
In
> those cases, I think we could live with publishing the RFCs and fixing them
> later, but it is on the whole better to fix the issues at the time they are
> spotted rather than later. The problem comes that an AD (especially out of
> expertise) cannot tell between "I think there might be a problem here" and "I
> know this is a serious bug".
> 
> I believe that the clue is in the word "Discuss" and I hope that I (at least)
am
> willing to listen when the response is "we thought about it, it's not a big
> problem." Perhaps people will tell me I am not so good at listening! I know
> other ADs also strive to that as an ideal, so perhaps we have something of a
> communications breakdown...
> 
> Discuss is not meant to mean "and you shall not move unless you do exactly
what
> I say." It should mean "Please help me to be happy about publishing this
> document because what I really want is you to publish the best possible
> document
> as quickly as possible."
> 
> Thanks,
> Adrian
> 
> 
> 
> 
> 
> 
> >
> > Sure, getting past iesg only cost multipath tcp a bit. But iesg members
> exceeding
> > their bounds as reviewers and leaving a personal mark seems commonplace.
> iesg
> > members are there for expertise in their area and to provide that expertise
in
> > focused reviews, not to block until a protocol is redesigned to suit their
> personal
> > tastes. (That transport expertise is lacking on iesg last I looked and
> everyone
> > believes they're an expert in transport  - 'hey, why can't we just turn off
> udp
> > checksums for sctp over udp? It's faster!' - another iesg redesign attempt
> > overriding considered expertise of a workgroup - isn't helping here.)
> >
> > There are two examples I know of, off the top of my head, telated to
transport
> > because that's my area of interest. Can others provide further examples?
> >
> > Lloyd Wood
> > http://sat-net.com/L.Wood/
> >
> >
> > ________________________________________
> > From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Paul
> Hoffman
> > [paul.hoffman@vpnc.org]
> > Sent: 11 April 2013 19:55
> > To: Joe Touch
> > Cc: IETF discussion list
> > Subject: Re: Purpose of IESG Review
> >
> > On Apr 11, 2013, at 10:54 AM, Joe Touch <touch@isi.edu> wrote:
> >
> > > As an author who has had (and has) multiple documents in IESG review, I've
> > noticed an increasing trend of this step to go beyond (IMO) its documented
and
> > original intent (BCP 9, currently RFC 2026):
> > >
> > >   The IESG shall determine whether or not a specification submitted to
> > >   it according to section 6.1.1 satisfies the applicable criteria for
> > >   the recommended action (see sections 4.1 and 4.2), and shall in
> > >   addition determine whether or not the technical quality and clarity
> > >   of the specification is consistent with that expected for the
> > >   maturity level to which the specification is recommended.
> > >
> > > Although I appreciate that IESG members are often overloaded, and the IESG
> > Review step is often the first time many see these documents, I believe they
> > should be expected to more clearly differentiate their "IESG Review" (based
on
> > the above criteria) - and its accompanying Position ballot, with their
> personal
> > review.
> > >
> > > My concern is that by conflating their IESG position with their personal
> review,
> > the document process is inappropriately delayed and that documents are
> > modified to appease a small community that does not justify its position as
> > representative.
> > >
> > > How do others feel about this?
> >
> > That it is too vague to comment on?
> >
> > Please point to specific examples where you feel an IESG member's review
> went
> > beyond determining the technical quality or clarity of the specification.
That
> > would help make the sure-to-be ensuing flamefest more light-filled.
> >
> > --Paul Hoffman


From touch@isi.edu  Thu Apr 11 15:41:48 2013
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 685F821F87E9 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level: 
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIM0r4KS3bNG for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 15:41:48 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id E18C421F87D5 for <ietf@ietf.org>; Thu, 11 Apr 2013 15:41:47 -0700 (PDT)
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 r3BMfIgv025250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Apr 2013 15:41:18 -0700 (PDT)
Message-ID: <51673C0E.2080700@isi.edu>
Date: Thu, 11 Apr 2013 15:41:18 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org>
In-Reply-To: <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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, 11 Apr 2013 22:41:48 -0000

On 4/11/2013 11:55 AM, Paul Hoffman wrote:
> On Apr 11, 2013, at 10:54 AM, Joe Touch <touch@isi.edu> wrote:
>
>> As an author who has had (and has) multiple documents in IESG review, I've noticed an increasing trend of this step to go beyond (IMO) its documented and original intent (BCP 9, currently RFC 2026):
>>
>>    The IESG shall determine whether or not a specification submitted to
>>    it according to section 6.1.1 satisfies the applicable criteria for
>>    the recommended action (see sections 4.1 and 4.2), and shall in
>>    addition determine whether or not the technical quality and clarity
>>    of the specification is consistent with that expected for the
>>    maturity level to which the specification is recommended.
>>
>> Although I appreciate that IESG members are often overloaded, and the IESG Review step is often the first time many see these documents, I believe they should be expected to more clearly differentiate their "IESG Review" (based on the above criteria) - and its accompanying Position ballot, with their personal review.
>>
>> My concern is that by conflating their IESG position with their personal review, the document process is inappropriately delayed and that documents are modified to appease a small community that does not justify its position as representative.
>>
>> How do others feel about this?
>
> That it is too vague to comment on?
>
> Please point to specific examples where you feel an IESG member's review went beyond determining the technical quality or clarity of the specification. That would help make the sure-to-be ensuing flamefest more light-filled.

I've already done that within the IESG; the point of the message wasn't 
to have dozens of opinions of whether my feedback was beyond scope, but 
whether others were getting that feeling as well. At least first...

Joe

From mcr@sandelman.ca  Thu Apr 11 15:53:51 2013
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 6AFE521F89C3; Thu, 11 Apr 2013 15:53:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvvJsxrkrZ+u; Thu, 11 Apr 2013 15:53:50 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id A5BD921F89B0; Thu, 11 Apr 2013 15:53:50 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4D0FF2016F; Thu, 11 Apr 2013 18:56:32 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id D9093A9946; Thu, 11 Apr 2013 18:46:27 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C0B6EB9396; Thu, 11 Apr 2013 18:46:27 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <6.2.5.6.2.20130411101504.0c42fed0@resistor.net>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 11 Apr 2013 18:46:27 -0400
Message-ID: <27744.1365720387@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: ietf@ietf.org, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Apr 2013 22:53:51 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "SM" =3D=3D SM  <sm@resistor.net> writes:
    SM> 12.5 % of IAOC voting members are female.
    SM> 0.1%  of IAB members are female
    SM> 0 %   of IESG members are female.

    SM> Based on the above measurements the IAOC is more "diverse".  The
    SM> IAOC already

Stats without standard deviations are meaningless.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUWc9Q4qHRg3pndX9AQIkzgP/RwclzfyMSqLrIfKr3Xg7qetUHbdfl/uv
czYFG5XcjLZ1aKjTgaPxZ4LCF53v13eOkDtRwEJnWPCDXhHi2uStfGQ1Jx+MJVoV
3SAEqLk1L6TQADnPfvnuPTmlx9zRu4esKsNhwLYPlmMCsjZ7R9bWyln6sCJGVTMy
/qP8lSbCBRs=
=HAk7
-----END PGP SIGNATURE-----
--=-=-=--

From fred@cisco.com  Thu Apr 11 17:27:44 2013
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 E4AE221F8917 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 17:27:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ze7R-gyrlR2K for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 17:27:44 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 415ED21F878F for <ietf@ietf.org>; Thu, 11 Apr 2013 17:27:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1300; q=dns/txt; s=iport; t=1365726464; x=1366936064; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ZadPOkDD82AqSOrcfvX0XEKDhso4hWKC9K+PSPQ7CaE=; b=QdqNv6F6ePa0hXEBjcTkqkws4NiIKMDtqhPjcQeqy7QTCpYDmVR9vtBI pb7o4BGTvxz8dNgCt1ANenvFkDQSxu9ZYBVggdOhtZC1SVYWtAcvVwkhY DnemVWHXHv60z6GpgylwwqerP+2lniIVU/IfiR2cNh4WTC50S6oQHDbQy I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAI9UZ1GtJV2b/2dsb2JhbABQDoJ4wg+BCBZ0giABAQR5EAIBCCIkMiUCBA4NiAy9MI5jAjEHgmBhA4hLn0aCTD+CKA
X-IronPort-AV: E=Sophos;i="4.87,459,1363132800"; d="scan'208";a="197851000"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP; 12 Apr 2013 00:27:43 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3C0Rhrq030775 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 12 Apr 2013 00:27:43 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Thu, 11 Apr 2013 19:27:43 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Joe Touch <touch@ISI.EDU>
Subject: Re: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: AQHONt3LK12oZOZLWkuxlgRbIFWFfJjRskCAgAA/MgCAAB23gA==
Date: Fri, 12 Apr 2013 00:27:42 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu>
In-Reply-To: <51673C0E.2080700@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.88.195]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <979FBBEDCA0A9B4C9108F9AE2042D276@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Paul Hoffman <paul.hoffman@vpnc.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, 12 Apr 2013 00:27:45 -0000

In my opinion, some individual ADs seem to, from their behavior, feel that =
they have not done their jobs unless they have raised a "discuss". The one =
that took the cake for me personally was a "discuss" raised by a particular=
 AD (who shall remain nameless) that in essence wondered what he should rai=
se a "discuss" about in my document. There were a couple of errors in that;=
 he told me later that what he had done was opened the comment tool and typ=
ed that question, and subsequently accidentally hit the equivalent of "send=
" - the question wasn't intended to go out. But the question itself is tell=
ing: the issue was not "does the document meet the requirements of BCP 9", =
it was "what comment shall I raise"?

Also, in my opinion, IESG review that raises a certain number of issues sho=
uld not result in the document sitting in the IESG's queue for a few months=
 while the authors go back and forth with the AD or the GEN-ART reviewer po=
unding the document into someone's idea of "shape" without working group in=
volvement. I personally would prefer that simple matters get sorted out bet=
ween the ADs and the author, but complex changes or additional content requ=
ested by the AD should result in the document being sent back to the workin=
g group. =

From melinda.shore@gmail.com  Thu Apr 11 17:41:02 2013
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 62EEB21F89A6 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 17:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.226
X-Spam-Level: 
X-Spam-Status: No, score=-3.226 tagged_above=-999 required=5 tests=[AWL=0.373,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsIF7UeGGnbr for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 17:41:02 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id CC76F21F8A4E for <ietf@ietf.org>; Thu, 11 Apr 2013 17:41:01 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id gd11so1782705vcb.31 for <ietf@ietf.org>; Thu, 11 Apr 2013 17:41:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=f5IWMuJkvvxo2zztuGtA1WmcyX4khDbDkpVI7qXjnTc=; b=pncbN6Up+Q8D30hwrTRKFOyFu0zUabd2Dv8AkoR6FoEp9iSoY8wtCltEYRgJiVn6Rx embaob/KOyYR4fHAEeAvERJuJ0k1milN85C5xuVwYrXdI3ie0zTcSdTaGEpiaWD24Id/ YVbQ5UodD/C6FabGBpslo/8dHrqtrbKHIL/VFIqjVVz/bD+p5GJSOyGUqDlDUjJRnDzO TtOq290720dgU4B05qBzmnwWcaOd1LYqO6dQRkMErMw2L+Bfz4+AgKw1SGU192mxBju0 xNZ/N0UFERAu53EgRzScvfDf3gb/h9J+UyakN0F3EGg3YBfAQBEsn9bYTGvJ5UNLfbVO qMoA==
X-Received: by 10.220.52.201 with SMTP id j9mr384846vcg.33.1365727261298; Thu, 11 Apr 2013 17:41:01 -0700 (PDT)
Received: from [107.16.91.90] (dhcp107-16-91-90.hil-gaighhf.dca.wayport.net. [107.16.91.90]) by mx.google.com with ESMTPS id d13sm6531958vdj.8.2013.04.11.17.41.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Apr 2013 17:41:00 -0700 (PDT)
Message-ID: <51675819.9070302@gmail.com>
Date: Thu, 11 Apr 2013 16:40:57 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com>
In-Reply-To: <20130411213835.GA8968@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, 12 Apr 2013 00:41:02 -0000

On 4/11/2013 1:38 PM, Toerless Eckert wrote:
> Suggesting that simply diversity stats across all IETF participants can help
> to deduce anything about leadership diversity bias is ignoring qualification
> and availability of candidates. Thats why i proposed the questions i would like to see
> in a questionaire.

You don't really need a questionnaire to go to that.
Nominations are a crude metric but they're a metric
nevertheless, and it would be an interesting exercise
to see how the pool of people recommended represents
(or not) the overall pool of people who've accepted
their nominations.

However.  The question that would answer (approximately)
is whether or not there's bias in the nomcom process.

My own feeling is that if we were to find that the
numbers supported the notion that there's bias
present in the system we probably couldn't do anything
about it without tearing the organization apart, so,
we live with bias, and trying to identify whether or
not there's bias in the nomcom process would be something
along the general lines of opening the gates of hell
and we'd probably be better off not knowing for sure.

But I digress.  It seems to me that it might be more
useful to identify what it is you're trying to find out,
first, and in this case I'm really not sure why Ray asked
that particular question.

Melinda


From stefan@aaa-sec.com  Thu Apr 11 21:37:58 2013
Return-Path: <stefan@aaa-sec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA9C21E8039 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 21:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.891
X-Spam-Level: 
X-Spam-Status: No, score=-101.891 tagged_above=-999 required=5 tests=[AWL=0.358, BAYES_00=-2.599, HELO_EQ_SE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ll2BEuugjfDT for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 21:37:57 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by ietfa.amsl.com (Postfix) with ESMTP id AAF3221E803D for <ietf@ietf.org>; Thu, 11 Apr 2013 21:37:57 -0700 (PDT)
Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id 4BAC42063A71 for <ietf@ietf.org>; Fri, 12 Apr 2013 06:37:56 +0200 (CEST)
X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se
Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xXyxonjO_dAW for <ietf@ietf.org>; Fri, 12 Apr 2013 06:37:54 +0200 (CEST)
Received: from s327.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id 2A5D42063A6B for <ietf@ietf.org>; Fri, 12 Apr 2013 06:37:54 +0200 (CEST)
Received: (qmail 46278 invoked from network); 12 Apr 2013 04:37:53 -0000
Received: from gw.aaa-sec.ideon.se (HELO [192.168.1.201]) (stefan@fiddler.nu@[85.235.7.89]) (envelope-sender <stefan@aaa-sec.com>) by s327.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <hotz@jpl.nasa.gov>; 12 Apr 2013 04:37:53 -0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Fri, 12 Apr 2013 06:37:49 +0100
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
From: Stefan Santesson <stefan@aaa-sec.com>
To: "Henry B. Hotz" <hotz@jpl.nasa.gov>
Message-ID: <CD8D5988.608C9%stefan@aaa-sec.com>
Thread-Topic: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
In-Reply-To: <04F36061-25C5-4159-A724-26B192C120DE@jpl.nasa.gov>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: pkix@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, 12 Apr 2013 04:37:58 -0000

On 4/12/13 1:31 AM, "Henry B. Hotz" <hotz@jpl.nasa.gov> wrote:

>What I would find helpful, and what I think some people really would
>like, is for OCSP to be able to provide white-list information in
>addition to the previous black-list information.  When I read through
>2560bis, I could not tell if there was an extension which would allow an
>RP to tell if "good" actually meant a cert was on the white list (and to
>know the responder has the white list), or merely not on the black list.
>(Yes, I'm repeating myself.  Am I making more sense, or just wasting
>everyone's time?)

What we have done is to roll out the red carpet and made it possible for
you to do that.

- The only thing you need to do now is to define a "white-list" extension.


To put it simply. Given how OCSP is designed, the only way to allow "good"
to represent a white-list, is if "revoked" can be returned for everything
else.
Everything else in this context means every other revoked or non-issued
certificate serial number under that CA.


With RFC 2560 that is not possible in a clean way.
With this new extension in RFC 2560bis, it is now possible.



From narten@us.ibm.com  Thu Apr 11 21:53:09 2013
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 44CD121F8696 for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 21:53:09 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6l1G5uoC8ZSE for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 21:53:08 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id CB51B21F8499 for <ietf@ietf.org>; Thu, 11 Apr 2013 21:53:07 -0700 (PDT)
Received: from /spool/local by e39.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, 11 Apr 2013 22:53:06 -0600
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 11 Apr 2013 22:53:06 -0600
Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 1ADAE38C801A for <ietf@ietf.org>; Fri, 12 Apr 2013 00:53:05 -0400 (EDT)
Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r3C4r5Cc30408810 for <ietf@ietf.org>; Fri, 12 Apr 2013 00:53:05 -0400
Received: from d01av05.pok.ibm.com (loopback [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r3C4r4Fs011817 for <ietf@ietf.org>; Fri, 12 Apr 2013 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r3C4r4wc011814 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 12 Apr 2013 00:53:04 -0400
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 r3C4r3Tb002163 for <ietf@ietf.org>; Fri, 12 Apr 2013 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r3C4r3Oj002151 for ietf@ietf.org; Fri, 12 Apr 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201304120453.r3C4r3Oj002151@rotala.raleigh.ibm.com>
Date: Fri, 12 Apr 2013 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-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13041204-3620-0000-0000-00000200BB3C
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Apr 2013 04:53:09 -0000

Total of 173 messages in the last 7 days.
 
script run at: Fri Apr 12 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.20% |    9 |  4.70% |    62873 | ted.lemon@nominum.com
  4.05% |    7 |  3.16% |    42214 | melinda.shore@gmail.com
  3.47% |    6 |  3.18% |    42603 | abdussalambaryun@gmail.com
  3.47% |    6 |  2.64% |    35325 | moore@network-heretics.com
  2.89% |    5 |  3.02% |    40419 | adrian@olddog.co.uk
  2.89% |    5 |  2.68% |    35849 | eckert@cisco.com
  2.89% |    5 |  2.41% |    32184 | arturo.servin@gmail.com
  2.31% |    4 |  2.96% |    39570 | dave@cridland.net
  2.89% |    5 |  2.38% |    31793 | mansaxel@besserwisser.org
  2.89% |    5 |  2.36% |    31626 | ynir@checkpoint.com
  2.31% |    4 |  2.81% |    37617 | stbryant@cisco.com
  2.31% |    4 |  2.72% |    36426 | doug.mtview@gmail.com
  2.89% |    5 |  2.14% |    28671 | dhc@dcrocker.net
  2.31% |    4 |  2.70% |    36191 | mohamed.boucadair@orange.com
  1.16% |    2 |  3.32% |    44357 | turners@ieca.com
  2.31% |    4 |  2.10% |    28067 | peter@akayla.com
  2.31% |    4 |  2.09% |    28013 | housley@vigilsec.com
  2.31% |    4 |  2.02% |    27017 | johnl@taugh.com
  2.31% |    4 |  1.89% |    25239 | hsantos@isdg.net
  2.31% |    4 |  1.86% |    24847 | brian.e.carpenter@gmail.com
  2.31% |    4 |  1.79% |    24011 | braden@isi.edu
  0.58% |    1 |  3.52% |    47129 | acooper@cdt.org
  0.58% |    1 |  3.28% |    43830 | cabo@tzi.org
  1.73% |    3 |  1.55% |    20695 | l.wood@surrey.ac.uk
  1.73% |    3 |  1.35% |    18113 | sm@resistor.net
  1.73% |    3 |  1.34% |    17886 | touch@isi.edu
  1.73% |    3 |  1.30% |    17378 | spencer@wonderhamster.org
  1.16% |    2 |  1.85% |    24715 | ron.even.tlv@gmail.com
  0.58% |    1 |  2.06% |    27500 | salvatore.dantonio@uniparthenope.it
  1.16% |    2 |  1.39% |    18635 | dmm@1-4-5.net
  1.16% |    2 |  1.07% |    14250 | barryleiba@computer.org
  0.58% |    1 |  1.52% |    20327 | rlb@ipv.sx
  1.16% |    2 |  0.93% |    12499 | swb@internet2.edu
  1.16% |    2 |  0.89% |    11864 | wbeebee@cisco.com
  1.16% |    2 |  0.88% |    11751 | nico@cryptonector.com
  1.16% |    2 |  0.87% |    11653 | mcr+ietf@sandelman.ca
  1.16% |    2 |  0.82% |    10914 | loa@pi.nu
  1.16% |    2 |  0.81% |    10839 | rpelletier@isoc.org
  1.16% |    2 |  0.79% |    10635 | steve@shinkuro.com
  0.58% |    1 |  0.90% |    12015 | kaduk@mit.edu
  0.58% |    1 |  0.86% |    11529 | jun@wide.ad.jp
  0.58% |    1 |  0.76% |    10179 | pthaler@broadcom.com
  0.58% |    1 |  0.74% |     9943 | ulrich@herberg.name
  0.58% |    1 |  0.66% |     8804 | narten@us.ibm.com
  0.58% |    1 |  0.66% |     8788 | d3e3e3@gmail.com
  0.58% |    1 |  0.63% |     8368 | joelja@bogus.com
  0.58% |    1 |  0.58% |     7773 | piyush@ditenity.com
  0.58% |    1 |  0.58% |     7727 | mstjohns@comcast.net
  0.58% |    1 |  0.58% |     7705 | farmer@umn.edu
  0.58% |    1 |  0.56% |     7530 | stefan@aaa-sec.com
  0.58% |    1 |  0.56% |     7521 | john-ietf@jck.com
  0.58% |    1 |  0.54% |     7207 | fred@cisco.com
  0.58% |    1 |  0.50% |     6688 | fgont@si6networks.com
  0.58% |    1 |  0.50% |     6629 | jcurran@istaff.org
  0.58% |    1 |  0.50% |     6624 | ted.ietf@gmail.com
  0.58% |    1 |  0.49% |     6590 | john@jlc.net
  0.58% |    1 |  0.49% |     6560 | superuser@gmail.com
  0.58% |    1 |  0.48% |     6389 | mrw@lilacglade.org
  0.58% |    1 |  0.47% |     6275 | heas@shrubbery.net
  0.58% |    1 |  0.47% |     6254 | jmpolk@cisco.com
  0.58% |    1 |  0.47% |     6244 | paul.hoffman@vpnc.org
  0.58% |    1 |  0.45% |     6060 | tjc@ecs.soton.ac.uk
  0.58% |    1 |  0.45% |     5999 | hotz@jpl.nasa.gov
  0.58% |    1 |  0.45% |     5975 | chair@ietf.org
  0.58% |    1 |  0.44% |     5833 | warren@kumari.net
  0.58% |    1 |  0.43% |     5734 | tnadeau@lucidvision.com
  0.58% |    1 |  0.41% |     5543 | iab-chair@iab.org
  0.58% |    1 |  0.41% |     5491 | bob.hinden@gmail.com
  0.58% |    1 |  0.41% |     5461 | dwm@xpasc.com
  0.58% |    1 |  0.40% |     5416 | yaronf.ietf@gmail.com
  0.58% |    1 |  0.40% |     5309 | mnot@mnot.net
  0.58% |    1 |  0.35% |     4695 | john@jck.com
  0.58% |    1 |  0.35% |     4657 | ajs@anvilwalrusden.com
  0.58% |    1 |  0.34% |     4591 | llynch@civil-tongue.net
  0.58% |    1 |  0.34% |     4529 | elwynd@dial.pipex.com
  0.58% |    1 |  0.29% |     3832 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |  173 |100.00% |  1337992 | Total


From sm@resistor.net  Thu Apr 11 23:08:37 2013
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 DDEF721F8A7E for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 23:08:37 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dqUGoxDjiqhH for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 23:08:37 -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 2C40621F8994 for <ietf@ietf.org>; Thu, 11 Apr 2013 23:08:37 -0700 (PDT)
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 r3C68PeJ026947; Thu, 11 Apr 2013 23:08:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365746914; bh=b3mLTx5/bX6FOjL76Cm5TKBxT5YyBBOP/wzts58p1F8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pa5JTn6WYgdTY/zKwhIH7bJQozDhwHAMYeZ1f+S2JZPd97wz+nc82WL622RTEtHwA 81JdEhtNnkpqTg4KOg809IyM0nH1IEMvwVWjEnAUwf2c4QGZmSLVKlOPZ4QPOaiS/V YlSa03vLLaT2UyWS7ZlWBkDHKJ8V93ilXF7Jilbg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365746914; i=@resistor.net; bh=b3mLTx5/bX6FOjL76Cm5TKBxT5YyBBOP/wzts58p1F8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Js9GspGYESPhN0r2WWNQnhULljm50WbIXSKPmQiXV/kveOaaE42OG4Ux0zgBTfdRj MGYxxf0lbuse4GlhmI1R4w554e5/RAwizNRMhpNGNHLTw7xKQBZo/D/e/mkrjMi+Au 33UsMKVoY91iBRI3xGj6ddCus745aqi23F+XjWnA=
Message-Id: <6.2.5.6.2.20130411140916.0c412c70@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 11 Apr 2013 22:49:15 -0700
To: Spencer Dawkins <spencer@wonderhamster.org>, Ted Lemon <Ted.Lemon@nominum.com>, Yoav Nir <ynir@checkpoint.com>, Melinda Shore <melinda.shore@gmail.com>, iaoc@ietf.org
From: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <5167211A.8080807@wonderhamster.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
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: Fri, 12 Apr 2013 06:08:38 -0000

At 13:46 11-04-2013, Spencer Dawkins wrote:
>If the IAB means "members", the number for=20
>females, as far as I know(*), is 2/15, or 13=20
>percent. If it means voting members, the number=20
>for females is 1/13, or just under 8 percent.

If I use the 13% I can say that the IAB is more=20
"diverse" than the IAOC.  Some organizations use=20
political arithmetic to look good.

At 13:21 11-04-2013, Ted Lemon wrote:
>With respect, this is sampling noise.  12.5% of=20
>8 is 1.   Don't get me wrong=97it's great that we=20
>have some diversity on the IAOC, but I don't=20
>think anybody should be patting themselves on the back just yet!

Yes.

At 13:09 11-04-2013, Yoav Nir wrote:
>I think skewed surveys are a worse basis for=20
>planning policy than just using common sense=20
>(yes, I know that's just another name for our=20
>biases). Surveys lend a scientific aura to data=20
>that is effectively non-representative.

Yes.

At 17:40 11-04-2013, Melinda Shore wrote:
>However.  The question that would answer (approximately)
>is whether or not there's bias in the nomcom process.
>
>My own feeling is that if we were to find that the
>numbers supported the notion that there's bias
>present in the system we probably couldn't do anything
>about it without tearing the organization apart, so,
>we live with bias, and trying to identify whether or
>not there's bias in the nomcom process would be something
>along the general lines of opening the gates of hell
>and we'd probably be better off not knowing for sure.

Yes.

The concern mentioned in the message from the=20
IAOC is about diversity.  The definition I found for diversity is:

    "the condition of having or being composed of differing elements,
     the inclusion of different types of people (as people of different
     races or cultures) in a group"

Is that the definition the IAOC is using?

Regards,
-sm=20


From john@jlc.net  Thu Apr 11 23:10:20 2013
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 A498021F8A8A for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 23:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.049
X-Spam-Level: 
X-Spam-Status: No, score=-107.049 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wzbjh+XLjnLf for <ietf@ietfa.amsl.com>; Thu, 11 Apr 2013 23:10:20 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id F35EE21F8A80 for <ietf@ietf.org>; Thu, 11 Apr 2013 23:10:19 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id B936233C23; Fri, 12 Apr 2013 02:10:18 -0400 (EDT)
Date: Fri, 12 Apr 2013 02:10:18 -0400
From: John Leslie <john@jlc.net>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Purpose of IESG Review
Message-ID: <20130412061018.GA56434@verdi>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.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: Fri, 12 Apr 2013 06:10:20 -0000

Fred Baker (fred) <fred@cisco.com> wrote:
> 
> Also, in my opinion, IESG review that raises a certain number of issues
> should not result in the document sitting in the IESG's queue for a
> few months while the authors go back and forth with the AD or the
> GEN-ART reviewer pounding the document into someone's idea of "shape"
> without working group involvement. I personally would prefer that
> simple matters get sorted out between the ADs and the author, but
> complex changes or additional content requested by the AD should
> result in the document being sent back to the working group.

   This is pretty much the call of Working Group Chairs, so perhaps you
should ask WGCs what they intend to do -- I don't think an IETF-wide
policy would work well here.

   Note also that when this is done, it seems to reinforce the attitude
that "We should humor the IESG!"

   (Even so, I personally prefer to hear about such changes. ;^)

--
John Leslie <john@jlc.net> 

From brian.e.carpenter@gmail.com  Fri Apr 12 00:13:22 2013
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 1D4A621F871C for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 00:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.614
X-Spam-Level: 
X-Spam-Status: No, score=-99.614 tagged_above=-999 required=5 tests=[AWL=-0.693, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cSzJxehjTQfU for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 00:13:21 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id 58B0921F86CB for <ietf@ietf.org>; Fri, 12 Apr 2013 00:13:21 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id c10so1268681wiw.13 for <ietf@ietf.org>; Fri, 12 Apr 2013 00:13:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Y1l44FEPE0sdJOI/dVrWvqhzzyzTnhDiGc4jDMd3410=; b=DSpKG1Z31s3i5ZoMDrsqXD13Ed/aFDJMHk8Gc7xoayiafCaI1XP85Ms2u+n8aA2OAe 4LXZ6MsvaPBNIfOm9XzKvuio2NW02M1mql3wQz++2AhDdOGpxb6suFVWyfBqrmTYSbcE mGbnOBqroqG+7Cv/rJIFcvoAiSGA1wDB4WOF3pMK+qgzb+msn5GNGk9f3qb2wXi320N1 WEj2pdwD/vvoz0cLrMY3ibyjsxecRhoPNrJermfV/Etb6cq27eLmIFtgcyiZjS4n20md 4MCxL2t+QbiAlH9qQ1Y1D3BRmQMZr8pnQmylO3rAfddtnDIgPrHNUZapDWwkwNvg8RC+ D9Ig==
X-Received: by 10.180.108.106 with SMTP id hj10mr2021290wib.0.1365750800525; Fri, 12 Apr 2013 00:13:20 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-188-167.as13285.net. [2.101.188.167]) by mx.google.com with ESMTPS id ej8sm1454202wib.9.2013.04.12.00.13.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 00:13:19 -0700 (PDT)
Message-ID: <5167B41A.2070209@gmail.com>
Date: Fri, 12 Apr 2013 08:13:30 +0100
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: Joe Touch <touch@isi.edu>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu>
In-Reply-To: <5166F8BD.7010308@isi.edu>
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: Fri, 12 Apr 2013 07:13:22 -0000

Seeing randomly selected drafts as a Gen-ART reviewer, I can
say that serious defects quite often survive WG review and
sometimes survive IETF Last Call review, so the final review
by the IESG does serve a purpose.

IMHO, if the IESG members sticks to their own criteria at
http://www.ietf.org/iesg/statement/discuss-criteria.html,
i.e. do not DISCUSS a document for spurious reasons, they
are doing just fine. If they don't stick to those criteria,
complaint is justified.

Of course this will always be a matter of judgment.

Regards
   Brian

On 11/04/2013 18:54, Joe Touch wrote:
> Hi, all,
> 
> As an author who has had (and has) multiple documents in IESG review,
> I've noticed an increasing trend of this step to go beyond (IMO) its
> documented and original intent (BCP 9, currently RFC 2026):
> 
>    The IESG shall determine whether or not a specification submitted to
>    it according to section 6.1.1 satisfies the applicable criteria for
>    the recommended action (see sections 4.1 and 4.2), and shall in
>    addition determine whether or not the technical quality and clarity
>    of the specification is consistent with that expected for the
>    maturity level to which the specification is recommended.
> 
> Although I appreciate that IESG members are often overloaded, and the
> IESG Review step is often the first time many see these documents, I
> believe they should be expected to more clearly differentiate their
> "IESG Review" (based on the above criteria) - and its accompanying
> Position ballot, with their personal review.
> 
> My concern is that by conflating their IESG position with their personal
> review, the document process is inappropriately delayed and that
> documents are modified to appease a small community that does not
> justify its position as representative.
> 
> How do others feel about this?
> 
> Joe
> 

From daedulus@btconnect.com  Fri Apr 12 01:25:52 2013
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 352C721F8A4F; Fri, 12 Apr 2013 01:25:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id InGY0h7vVHZm; Fri, 12 Apr 2013 01:25:48 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) by ietfa.amsl.com (Postfix) with ESMTP id C6CDE21F8A0C; Fri, 12 Apr 2013 01:25:47 -0700 (PDT)
Received: from mail221-ch1-R.bigfish.com (10.43.68.245) by CH1EHSOBE005.bigfish.com (10.43.70.55) with Microsoft SMTP Server id 14.1.225.23; Fri, 12 Apr 2013 08:25:47 +0000
Received: from mail221-ch1 (localhost [127.0.0.1])	by mail221-ch1-R.bigfish.com (Postfix) with ESMTP id E2A284038B; Fri, 12 Apr 2013 08:25:46 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371I542I1432I1418Idb82hzz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz1033IL8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah304l1155h)
Received: from mail221-ch1 (localhost.localdomain [127.0.0.1]) by mail221-ch1 (MessageSwitch) id 1365755144521825_2166; Fri, 12 Apr 2013 08:25:44 +0000 (UTC)
Received: from CH1EHSMHS008.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.247])	by mail221-ch1.bigfish.com (Postfix) with ESMTP id 7D1D232005E;	Fri, 12 Apr 2013 08:25:44 +0000 (UTC)
Received: from AMSPRD0710HT002.eurprd07.prod.outlook.com (157.56.249.85) by CH1EHSMHS008.bigfish.com (10.43.70.8) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 12 Apr 2013 08:25:44 +0000
Received: from DB3PRD0511HT004.eurprd05.prod.outlook.com (157.56.254.213) by pod51017.outlook.com (10.255.160.165) with Microsoft SMTP Server (TLS) id 14.16.293.5; Fri, 12 Apr 2013 08:25:38 +0000
Message-ID: <000901ce3756$a9d8dcc0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Ray Pelletier <rpelletier@isoc.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <4A102652-5627-4711-8EC2-6779443EDC01@isoc.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
Date: Fri, 12 Apr 2013 09:20:50 +0100
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.254.213]
X-OriginatorOrg: btconnect.com
Cc: iaoc@ietf.org, Discussion 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, 12 Apr 2013 08:25:52 -0000

Ray

Expert as the IETF (and its allied organisations) is in Internet
Engineering, I doubt if many of those skills transfer into Social
Engineering, which is the field in which I think this question lies.
Lacking such expertise, into how to frame a question in order to get the
answer which is wanted, how to interpret the results of a self-selecting
survey, complying with the legislation relating to the handling of
personal information in the countries involved, I think that the IETF
should stay out of this.

Tom Petch

----- Original Message -----
From: "Ray Pelletier" <rpelletier@isoc.org>
To: "Ray Pelletier" <rpelletier@isoc.org>
Cc: "Discussion IETF" <ietf@ietf.org>
Sent: Thursday, April 11, 2013 4:17 PM
Subject: Re: IETF Diversity Question on Berlin Registration?

And please direct your comments to iaoc@ietf.org

Thanks

Ray

On Apr 11, 2013, at 11:11 AM, Ray Pelletier wrote:

> All
>
> The IETF is concerned about diversity.  As good engineers, we would
like
> to attempt to measure diversity while working on addressing and
increasing
> it.  To that end, we are considering adding some possibly sensitive
> questions to the registration process, for example, gender.  Of
course,
> they need not be answered and would be clearly labeled as optional.
>
> The IAOC would like to hear from the community on this proposal.  It
plans to
> make a decision on its 18 April call in order to make the changes in
time for the
> Berlin registration and will consider all input received by 17 April.
>
> Thanks for your feedback.
>
> Ray
> IAD
>




From abdussalambaryun@gmail.com  Fri Apr 12 02:33:28 2013
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 363C721F8A2A for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 02:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8pV0nExAmgC0 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 02:33:26 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 2B83621F89D3 for <ietf@ietf.org>; Fri, 12 Apr 2013 02:33:26 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id 3so1318993pdj.41 for <ietf@ietf.org>; Fri, 12 Apr 2013 02:33:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=PnO0FWxJu3zM5Vu6mZKBchKXawv4bKGB/3eE5t0MqIM=; b=PKJxD8i2qeogsVe9bpphkb3oIUft2mm0pud3JhE4tyefjNPVXXQ2Pw76SJX7invpVc 446SOWAmNky1JUP7PoH22QY8xpxGGC6MSOYa0LHTVoCppBItSx20hGKfNALGFajCqUrU j0B26PpVzxf3rei1DrFT5fspc7jXVg/CeeOnx2IiSq1KSv4YZHZn+HXhlNCcZrTa/zRL 3Emz/RKQE5rZhtLTDBnKmunJVoIU9K+qgdg9Tzu0J2HR3cSc8taonzYnEWOzUt2AeXry ++RJHuHq0X7A0I4+2X5b2aH16ZXP46qZwgj7RvqmwW4WsGWbNZC9BFb1CEmbRWJOjAQ8 wXTQ==
MIME-Version: 1.0
X-Received: by 10.68.209.162 with SMTP id mn2mr13516622pbc.190.1365759205820;  Fri, 12 Apr 2013 02:33:25 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Fri, 12 Apr 2013 02:33:25 -0700 (PDT)
Date: Fri, 12 Apr 2013 11:33:25 +0200
Message-ID: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com>
Subject: Re: Purpose of IESG Review
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: touch <touch@isi.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: Fri, 12 Apr 2013 09:33:28 -0000

Reply to below message
The subject SHOULD be: Evaluating Review Process Performance
I prefer the Subject is: Evaluating WG input, the WG review process,
and the WG output, NOT IESG review.
------------------------------------------------------------------------------------------------

Hi Joe,

My comments mostly is on your message, but I comment also on I-Ds or
RFCs related to IETF (including joky RFCs).

I don't think it is write to evaluate the review of an IESG as long as
when we created the I-D and adopted it into IETF SYSTEM, it is already
agreeing on the methods of process that I-D is going through. So the
problem is to evaluate three things not one: 1) the input, 2) the
process review, 3) the output.

We may make different input methods that go to another body than IESG,
but if you decided to make I-D under IETF current procedure, it will
have to go to IESG.

I think the IESG are doing an excellent job, but it is best them to
evaluate their performance not the community. Or it is better to find
a body that evaluates the IESG performance not on this list.

I consider your input on the list as a complain about the process, so
I ask you to notice that your input has an error that needs evaluation
befor going to process evaluation. You may evaluate output, but I
remind you to evaluate input of WGs and inputs of individuals.

I think the BIG problem of delay in I-Ds or RFC, is the cause of the
WG not the IESG, if you do an excellent WG processes you will get
quick results at IESG.

AB
+++++++++++++
Hi, all,


As an author who has had (and has) multiple documents in IESG review,
I've noticed an increasing trend of this step to go beyond (IMO) its
documented and original intent (BCP 9, currently RFC 2026):
   The IESG shall determine whether or not a specification submitted to
   it according to section 6.1.1 satisfies the applicable criteria for
   the recommended action (see sections 4.1 and 4.2), and shall in
   addition determine whether or not the technical quality and clarity
   of the specification is consistent with that expected for the
   maturity level to which the specification is recommended.


Although I appreciate that IESG members are often overloaded, and the
IESG Review step is often the first time many see these documents, I
believe they should be expected to more clearly differentiate their
"IESG Review" (based on the above criteria) - and its accompanying
Position ballot, with their personal review.

My concern is that by conflating their IESG position with their
personal review, the document process is inappropriately delayed and
that documents are modified to appease a small community that does not
justify its position as representative.
How do others feel about this?

Joe

From dhc@dcrocker.net  Fri Apr 12 05:22:59 2013
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 975AD21F861A for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 05:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NrNK39XYPVYd for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 05:22:58 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 52B8721F854E for <ietf@ietf.org>; Fri, 12 Apr 2013 05:22:58 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3CCMtE7000883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 12 Apr 2013 05:22:56 -0700
Message-ID: <5167FC99.8020704@dcrocker.net>
Date: Fri, 12 Apr 2013 05:22:49 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <5167B41A.2070209@gmail.com>
In-Reply-To: <5167B41A.2070209@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]); Fri, 12 Apr 2013 05:22:56 -0700 (PDT)
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, 12 Apr 2013 12:22:59 -0000

On 4/12/2013 12:13 AM, Brian E Carpenter wrote:
> Seeing randomly selected drafts as a Gen-ART reviewer, I can
> say that serious defects quite often survive WG review and
> sometimes survive IETF Last Call review, so the final review
> by the IESG does serve a purpose.


Brian,

Of course it "serves" a purpose.  The lack of perfection in the 
specifications that reach the IESG has always been the justification for 
the current review model.

But what is tiring about this line of justification is its continuing 
failure to balance the analysis by looking at the costs and problems 
that come with it.  Does it provide regular and sufficient benefit to 
justify its considerable costs?

First, it is a phenomenally expensive step, with a very damaging 
organizational cost:  the time and effort burden put on ADs makes the 
pool of available ADs tiny, including dramatically reducing the range of 
companies that can afford to donate senior (strategic) staff to it.

Along with this is the general issue that has triggered Joe's query: 
the tendency of ADs to inject spontaneous, late-stage personal 
engineering preferences, which might have been reasonable to add to the 
original working group discussion but realistically have no place in a 
final review.  It's not that the preferences are necessarily 
inappropriate, it's that they typically are not essential to the success 
of the spec.

But in terms of the specific logic you've used, the presumption of the 
"it catches errors sometimes" language is that the final output that is 
the result is somehow perfect.  Of course, that's a silly assumption. 
But as soon as one acknowledges this, we are left with a model that must 
class this as merely one more review in an imperfect sequence, with the 
likelihood that an every new review will find more problems.  Or we are 
left with the view that pragmatics dictate accepting imperfections 
because each step of the quality assurance model -- of which this is a 
part -- really does need a strict cost/benefit analysis.  This needs to 
be done in terms of trade-offs, rather than an isolated approach that 
counts the detection of an occasional problem as somehow an inherent and 
controlling good.

An essential component to such a trade-off based model is recognizing 
that the ultimate quality assurance step always has been, and remains, 
the market.  No amount of IETF q/a guarantees success.  We have lots of 
failures and we won't ever get to zero.

If the IESG review step really is essential, then we should show a 
consistent pattern of its finding /essential/ errors that would have 
caused failure in the field.

But if we can find that -- which I believe we cannot -- we have deeper 
problems, of course, because that sort of shit needs to be found mch, 
much sooner.

At base, the IESG review seeks to compensate for seriously inadequate 
quality control during the development process...

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From fred@cisco.com  Fri Apr 12 06:17:28 2013
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 45ACC21F8842 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 06:17:28 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GudHMGQYAwYW for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 06:17:27 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9D72C21F875A for <ietf@ietf.org>; Fri, 12 Apr 2013 06:17:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=653; q=dns/txt; s=iport; t=1365772647; x=1366982247; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Y5s6i49VxoG+7xR85z/XGubC6ctTH72X7K7yjPEIU+c=; b=E92SV9oNYPT4D59AMpfp8fhSn9VDRYPmcdeWF0GcUiFoXw2+I7+Ei3jt Psv09USCWd5V3WlgpNgTwXBJKo4S00AeEghHXQaTfrzsLwUX6WfqPWMDX 3W13TVjMod5t4d09EHcsSRzi0TFan6FZOYANSP0fpoaB8WtiXd7HAIiCp M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj4FAH0IaFGtJV2b/2dsb2JhbABQgwbCEYEKFnSCHwEBAQMBOj8FCwIBCCIUECERJQIEDgUIh3oDCQazag2JXYxDgiACMQeCYGEDlR+HOIYehRyDC4Io
X-IronPort-AV: E=Sophos;i="4.87,462,1363132800"; d="scan'208";a="197848654"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-1.cisco.com with ESMTP; 12 Apr 2013 13:17:19 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3CDHJde009707 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 12 Apr 2013 13:17:19 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.02.0318.004; Fri, 12 Apr 2013 08:17:19 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: AQHONt3LK12oZOZLWkuxlgRbIFWFfJjSgI4AgABlu4A=
Date: Fri, 12 Apr 2013 13:17:18 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B80B284@xmb-rcd-x09.cisco.com>
References: <5166F8BD.7010308@isi.edu> <5167B41A.2070209@gmail.com>
In-Reply-To: <5167B41A.2070209@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.88.195]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BAF136361E8C864E9ED1EAD33EC88D41@emea.cisco.com>
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: Fri, 12 Apr 2013 13:17:28 -0000

On Apr 12, 2013, at 12:13 AM, Brian E Carpenter <brian.e.carpenter@gmail.co=
m> wrote:

> Seeing randomly selected drafts as a Gen-ART reviewer, I can
> say that serious defects quite often survive WG review and
> sometimes survive IETF Last Call review, so the final review
> by the IESG does serve a purpose.

I'm not saying it doesn't serve a purpose. I'm saying that I know of drafts=
 that have been nearly rewritten during such back-and-forth, so what popped=
 out was largely unrelated to what went in. In such cases, I think the docu=
ment should have been returned to the working group with comments, not work=
ed on privately.=

From brian.e.carpenter@gmail.com  Fri Apr 12 06:50:48 2013
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 BC32121F86C4 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 06:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.44
X-Spam-Level: 
X-Spam-Status: No, score=-99.44 tagged_above=-999 required=5 tests=[AWL=-0.519, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jse45Ra9u36v for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 06:50:47 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 09D4321F8689 for <ietf@ietf.org>; Fri, 12 Apr 2013 06:50:46 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id k13so1572543wgh.1 for <ietf@ietf.org>; Fri, 12 Apr 2013 06:50:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XUjpRulJ9jIkd3gxODsO56cx/UZiKCVFdAuvp5Csm68=; b=xKrwjrWXL6mVGesbfY7sh5hdA3lUgQ1wlkDGa9rW7KIvssQgYrN5T2bEq99d8kdS2l vf71GAlSs3DO1RoFjgN/vvfifoNECiP9g8qt4aRE+o9Q9DbiorNLx66PatyoSBGKBk7p hjCvisSKCriFN9inqTgKoau6kS1M/mK0XV4QXABEIeLVIFdMGxIJFqdumwqp0pxvBCRA DGeaMI+O2Lzs54chLnzOR2+lHQ/06CyZrGhHSSC7DmCm0e9C5HNmB4WLiF1qwBWUSpXl 4dlnxgV6xJRZtCnPS3xZm7ba7zFm/g9d7fs7UPxnN8kLqLZ/RrLacWoPxIVOGR1hcUOx u1hA==
X-Received: by 10.194.171.74 with SMTP id as10mr17726294wjc.0.1365774645936; Fri, 12 Apr 2013 06:50:45 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-188-167.as13285.net. [2.101.188.167]) by mx.google.com with ESMTPS id n2sm3431940wiy.6.2013.04.12.06.50.44 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 06:50:45 -0700 (PDT)
Message-ID: <51681141.8040309@gmail.com>
Date: Fri, 12 Apr 2013 14:50:57 +0100
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: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <5167B41A.2070209@gmail.com> <8C48B86A895913448548E6D15DA7553B80B284@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B80B284@xmb-rcd-x09.cisco.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: Fri, 12 Apr 2013 13:50:48 -0000

On 12/04/2013 14:17, Fred Baker (fred) wrote:
> On Apr 12, 2013, at 12:13 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> Seeing randomly selected drafts as a Gen-ART reviewer, I can
>> say that serious defects quite often survive WG review and
>> sometimes survive IETF Last Call review, so the final review
>> by the IESG does serve a purpose.
> 
> I'm not saying it doesn't serve a purpose. I'm saying that I know of drafts that have been nearly rewritten during such back-and-forth, so what popped out was largely unrelated to what went in. In such cases, I think the document should have been returned to the working group with comments, not worked on privately.

I agree. That should be standard operating procedure.

   Brian

From spencer@wonderhamster.org  Fri Apr 12 07:39:10 2013
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 3163321F8A91; Fri, 12 Apr 2013 07:39:10 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ar3eY-c8SieE; Fri, 12 Apr 2013 07:39:09 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFBE21F87B6; Fri, 12 Apr 2013 07:39:09 -0700 (PDT)
Received: from [192.168.1.74] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net [99.108.174.213]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0Lz3f6-1Ue5KX338C-0142jr; Fri, 12 Apr 2013 10:39:01 -0400
Message-ID: <51681C7C.7050408@wonderhamster.org>
Date: Fri, 12 Apr 2013 09:38:52 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <6.2.5.6.2.20130411140916.0c412c70@resistor.net>
In-Reply-To: <6.2.5.6.2.20130411140916.0c412c70@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:O9juldHqwAzzpTXP60iX1w6Qvimp86Wp6wHX/zIo+8m rRFH8tDUZcyol8DyUH4L0GJBf4XIqZ50ZMbgJP94Bvn2uaKfuq 0vSnk2B24kIX3aVESNdMnEzurzUGGoVjlhr5ZhD1O3rHoXjdRX /ZqAvFOBT8LroTE/lbrWtxrpOHQE3kx3akuXFbjqry0WBHdkf8 t+GJSmsfgJqZxAH34mAKlzrmtOfqGejElhLeM8merJFraV7vgI x+Fssd8jCTOCGS7geDVMrCAh/52WXURIrrcG6XbuprskrUI4FH DVXF0+U4Mdqwgqzpv8kXBL7u1Bkyxg4WNgyCEhKhgpo/24Z1Yu UEXWfGTt04DcNvNbBRSkjJNhs9ExUWUfaGhdimfRt
Cc: ietf@ietf.org, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Apr 2013 14:39:10 -0000

On 4/12/2013 12:49 AM, SM wrote:
> At 13:46 11-04-2013, Spencer Dawkins wrote:
>> If the IAB means "members", the number for females, as far as I
>> know(*), is 2/15, or 13 percent. If it means voting members, the
>> number for females is 1/13, or just under 8 percent.
>
> If I use the 13% I can say that the IAB is more "diverse" than the
> IAOC.  Some organizations use political arithmetic to look good.

Hi, SM,

I was just checking the math.

I couldn't possibly say what "good" means, and I'm interested in better 
understanding what "diverse" means, to this, ummm, at least somewhat 
diverse community ...

Spencer

p.s. And I wasn't trying to be snarky about the math. I blew the 
percentages in the first draft of my response, so I know it happens to 
the best of us :-)

From farmer@umn.edu  Fri Apr 12 08:15:44 2013
Return-Path: <farmer@umn.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 7642B21F8C9B for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 08:15:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4hNoYG1NUXG for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 08:15:43 -0700 (PDT)
Received: from vs-a.tc.umn.edu (vs-a.tc.umn.edu [134.84.135.107]) by ietfa.amsl.com (Postfix) with ESMTP id 2F77B21F8B15 for <ietf@ietf.org>; Fri, 12 Apr 2013 08:15:43 -0700 (PDT)
Received: from mail-ie0-f197.google.com (mail-ie0-f197.google.com [209.85.223.197]) by vs-a.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Fri, 12 Apr 2013 10:15:32 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ie0-f197.google.com [209.85.223.197] #+LO+TR
X-Umn-Classification: local
Received: by mail-ie0-f197.google.com with SMTP id a11so15602980iee.0 for <ietf@ietf.org>; Fri, 12 Apr 2013 08:15:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding:x-gm-message-state; bh=AQm5DAKQoyHVF5618f3dPVKoRuLiQvXnxRcqeibSvYw=; b=T6jH/xAwENSQsU9+Fzq4RoQYLrWy4BlrEJsO/M85pLgzRjHuZv0ySqBGaOMkIPEZZn IZRd5M+Y24J38LTfATqSvz0AaFHrFNdOjBnF0vCGohzvcN25HRJfeEbBQ5a24GEl/HS3 +6tqKjzNaOezjwwnbaS9EUvO+DrkQiJDiPe1/CzzOK7EG0v8w1EvTzlmLKGR5vNkQQBr DKAC0h2DCQD0YJ7GygZ7RVl75raP+aJrawIWilWzHffLvE18fJrf3hcMF3NaU0G6Mno6 2KOTccYF19boc2UbODqYO51S5MBmgZ3Co/7IeYBEmtwUZUJTCMTkj8+cbW6+Egl2Ueye sLfg==
X-Received: by 10.50.208.40 with SMTP id mb8mr1983621igc.91.1365779732109; Fri, 12 Apr 2013 08:15:32 -0700 (PDT)
X-Received: by 10.50.208.40 with SMTP id mb8mr1983613igc.91.1365779731994; Fri, 12 Apr 2013 08:15:31 -0700 (PDT)
Received: from oit201651646.local (c-24-118-200-23.hsd1.mn.comcast.net. [24.118.200.23]) by mx.google.com with ESMTPS id ur12sm3324351igb.8.2013.04.12.08.15.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 08:15:30 -0700 (PDT)
Message-ID: <51682512.50505@umn.edu>
Date: Fri, 12 Apr 2013 10:15:30 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: John Curran <jcurran@istaff.org>
Subject: Re: draft-housley-rfc2050bis-01
References: <11301BFD-E4AD-4779-802E-6BAADD0381D4@vigilsec.com> <5162EAFD.8060102@umn.edu> <EEBF37E5-E727-42F2-A237-53CF2971111B@istaff.org>
In-Reply-To: <EEBF37E5-E727-42F2-A237-53CF2971111B@istaff.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQmXZExraetepXRruHL3JQG2W3+Vw85NUNlBDWUb0rhXPu+a/QEzOLh8BaWf+z3sjdxxoW3dU+VD3EuITFgo3Zdc1nPBdCihoIL9cyNTPYEAZ6c3q7Ede4ynlHDOdhRsfp3/f0Se
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Apr 2013 15:15:44 -0000

On 4/8/13 13:45 , John Curran wrote:
> On Apr 8, 2013, at 9:06 AM, David Farmer <farmer@umn.edu> wrote:
>
>> 3.  Regarding Public WHOIS in section 4;  The constituencies and stakeholders for Public WHOIS are much broader than just the technical community, a number of constituencies in civil society have legitimate interests in Public WHOIS.  I guess the main point I'm trying to make is that Public WHOIS is more than just a technical issue, and section 4 seems to scope it as solely a technical issue.
>
> It's definitely a bigger issue, but it does not seem appropriate in
> an IETF document to assert points about all aspects of the issue, but
> instead better to just note the _technical considerations_ of the topic
> that are needed to keep the Internet running.
>
>> I don't think you need to refocus section 4 from "Technical Considerations" I think simply recognizing that there are more than just technical considerations, especially for Public WHOIS, something like the following should be sufficient;
>>
>>    2) ...have included consideration of the technical and operational
>>       requirements, as well as requirements of other stakeholders, for
>>       supporting WHOIS services...
>
> This text would be the authors asserting that these requirements (those of
> other stakeholders of Whois) have been considered, and yet there are wide
> range of non-technical aspects to Whois that quite probably have not been
> fully considered; e.g. issues similar to those in various ongoing discussions
> of DNS Whois at ICANN this week...
>
> The section is about the _technical considerations_ that have been considered
> in establishment of the Internet Numbers Registry System, and to change the
> text as you suggest would significantly expand its scope into areas not currently
> addressed in the text and not typical of other IETF documents, i.e. problematic.

You are probably right, but the first paragraph of section 4 says;

    As a result of the system of technical standards and guidelines
    established by the IETF as well as historical and operational
    constraints, there have been technical considerations regarding the
    services provided by the Internet Numbers Registry System as it
    evolved.  These technical considerations have included:

Specifically where it says "as well as historical and operational 
constraints" seems to open the door for what I'm talking about.  The way 
it is written, the "historical and" seem to stand apart from, separate 
from, or in addition too, the "technical standards and guidelines" of 
the IETF.  Historical constraints is rather broad and could easily 
include non-technical considerations.  Which the issues of broader 
society and Public WHOIS are certainly some of the historical 
non-technical considerations.

So I'd suggest that paragraph should get some work, to better represent 
the intent you have stated for this section.  I suggest the following 
text, based on my interpretation of what you are saying.  I feel it 
better constrains the discussion to the technical domain.  In particular 
changing "historical and operational constraints" to something like 
"historic operational practices".

    As a result of the system of technical standards and guidelines
    established by the IETF, as well as historic operational
    practices of the Internet community, there are technical
    considerations regarding the services provided by the Internet
    Numbers Registry System, these included:

Thanks.

-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================

From mrex@sap.com  Fri Apr 12 08:26:20 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97A4121F8554 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 08:26:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZeiDTCylYfI for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 08:26:19 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA7021F8550 for <ietf@ietf.org>; Fri, 12 Apr 2013 08:26:19 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r3CFQHPa018187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 12 Apr 2013 17:26:17 +0200 (MEST)
Subject: Re: Purpose of IESG Review
In-Reply-To: <5167B41A.2070209@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Fri, 12 Apr 2013 17:26:17 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130412152617.438721A6AD@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: Fri, 12 Apr 2013 15:26:20 -0000

Brian E Carpenter wrote:
>
> Seeing randomly selected drafts as a Gen-ART reviewer, I can
> say that serious defects quite often survive WG review and
> sometimes survive IETF Last Call review, so the final review
> by the IESG does serve a purpose.

I'm currently seeing a document with some serious defects in
IETF Last Call (rfc2560bis) and an apparent desire to have
it Rubberstamped by the IESG (recycling at Proposed Standard).

While that seems procedurally permitted for the IESG to do such
rubberstamping (aka "waive") for a proposed standard
(rfc2026, last paragraph on page 12):

   http://tools.ietf.org/html/rfc2026#page-12

   A Proposed Standard should have no known technical omissions with
   respect to the requirements placed upon it.  However, the IESG may
   waive this requirement in order to allow a specification to advance
   to the Proposed Standard state when it is considered to be useful and
   necessary (and timely) even with known technical omissions.

one should really consider the consequences of such a decision,
especially for -bis and -ter documents.

The original draft (and now full) standard requires that such defects
are removed _before_ the document is advanced.  So when "waiving" known
defects/omissions (in particular obvious and formally provable ones),
this means that there will have to be a ter document produced where
this defects are fixed and this document be recycled at Proposed
one more time before the standard can progress on the maturity level.

It turns out that for a non-negligible amount of the defects there
is a constituency that want the defect to be retained rather than
fixed, and they expect the IESG to waive defects on -bis, -ter etc.
documents whenever it was previously accepted for Proposed with
that defect.


> 
> IMHO, if the IESG members sticks to their own criteria at
> http://www.ietf.org/iesg/statement/discuss-criteria.html,
> i.e. do not DISCUSS a document for spurious reasons, they
> are doing just fine. If they don't stick to those criteria,
> complaint is justified.
> 
> Of course this will always be a matter of judgment.
> 
> Regards
>    Brian
> 
> On 11/04/2013 18:54, Joe Touch wrote:
> > 
> > My concern is that by conflating their IESG position with their personal
> > review, the document process is inappropriately delayed and that
> > documents are modified to appease a small community that does not
> > justify its position as representative.

What do you want to see the IESG do instead?

Simply Rubberstamp WG consensus?  That would turn the whole IESG
diversity discussion into an absurd waste of time...

-Martin

From doug.mtview@gmail.com  Fri Apr 12 09:01:19 2013
Return-Path: <doug.mtview@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 8720521F8DB2 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 09:01:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZhB3NcsF7QDt for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 09:01:18 -0700 (PDT)
Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com [209.85.220.53]) by ietfa.amsl.com (Postfix) with ESMTP id A3C1A21F8D2C for <ietf@ietf.org>; Fri, 12 Apr 2013 09:01:18 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id bh4so1526041pad.26 for <ietf@ietf.org>; Fri, 12 Apr 2013 09:01:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=E7Wk8k66dBfjIO4xg6XfGMCR0MjaKPCB5i98CHJIpfE=; b=AjTadBT+UrPU/7cxev36GBWn9aS9sOdTAFCzo668fBYYKxtIY/JsvUhS3kaS+ICYlk 8I4/TDgh8c+MfCZgOxjTjrcSeqs9+m2EvCcoO9ktYfjdK71CbI7yjjESVs32XAWdndgb +iLmOjfPPYcvOKyfxjxcYY9z7p5Pig3DIJaBtBwKN4wRFLi2OFQv8TUUbzXKa52dq7WG vmoM3CVzMHbkIsDjyTsEcirbc9XtDc6vwAqD+me7cN990AKDendf/P02ewnfaGlwvjI9 XQJdw2zDZKQ18GixN82pBd/eV6xx3h0RE08qP7VQVJPNNC03QOdZmPqPqIlraNSd+JMZ QCUg==
X-Received: by 10.68.216.165 with SMTP id or5mr15546565pbc.152.1365782478488;  Fri, 12 Apr 2013 09:01:18 -0700 (PDT)
Received: from farside-home.private (c-24-6-101-92.hsd1.ca.comcast.net. [24.6.101.92]) by mx.google.com with ESMTPS id do4sm9091363pbc.8.2013.04.12.09.01.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 09:01:17 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
Date: Fri, 12 Apr 2013 09:01:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9ACCAD1C-3BDF-4379-81B6-6B8431B10109@gmail.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>
To: Ray Pelletier <rpelletier@isoc.org>
X-Mailer: Apple Mail (2.1503)
Cc: Discussion 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, 12 Apr 2013 16:01:19 -0000

Dear Ray,

Outcomes, good or bad, are often influenced by groups sharing a common =
interest.  Important questions should attempt to measure whether these =
interests reflect those of the larger Internet communities.=20

No gender, sexual orientation, ethic, religious, or political background =
should be excluded, but attempting to ascertain the breath and =
distribution of interests based on questions used to measure some =
possible selection bias based on distributions of aspects unrelated to =
the endeavors of the IETF seems unlikely to improve outcomes.

When faced with some distraction from endeavors at hand, a friend of =
mine would exclaim "squirrel!"=20

Regards,
Douglas Otis

On Apr 11, 2013, at 8:11 AM, Ray Pelletier <rpelletier@isoc.org> wrote:

> All
>=20
> The IETF is concerned about diversity.  As good engineers, we would =
like
> to attempt to measure diversity while working on addressing and =
increasing
> it.  To that end, we are considering adding some possibly sensitive
> questions to the registration process, for example, gender.  Of =
course,
> they need not be answered and would be clearly labeled as optional.
>=20
> The IAOC would like to hear from the community on this proposal.  It =
plans to=20
> make a decision on its 18 April call in order to make the changes in =
time for the=20
> Berlin registration and will consider all input received by 17 April. =20=

>=20
> Thanks for your feedback.
>=20
> Ray
> IAD
>=20


From brian.e.carpenter@gmail.com  Fri Apr 12 09:21:48 2013
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 8F77C21F8EB2 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 09:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.475
X-Spam-Level: 
X-Spam-Status: No, score=-99.475 tagged_above=-999 required=5 tests=[AWL=-0.554, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mBG1Gohj8XXb for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 09:21:47 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5D621F8E6E for <ietf@ietf.org>; Fri, 12 Apr 2013 09:21:47 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hm11so1852864wib.1 for <ietf@ietf.org>; Fri, 12 Apr 2013 09:21:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=r4ZriSJEWQueyHLC0XJhXDXbI8oUrIjC2r/8DVqsvGk=; b=ucL8kol0K3+wN8Ua/Pn5Sdt8+t4kiqPZKEDIQ6LElV0ftToGPwMmSIllM0xCTF3MX1 Y9zrt9PbTxwDAeyf0RKF6bpbWpJfKCeHmAV+L9ht5sVnR94eB5pljPFePcb/IrUTv0SN U5TqW3uB3driP0ZItpsst848YNz1aohBeaQwU7tYLwq7iCgHDvLzxaCbb+i7XXp+ZUMG HQrUgCulhXSxFLgaBvSmKzzzDio4Sf36AkEgFhTYWMcRuYF/YdWxCfuF69CTF13FiE5j 3Jg1hlBv2X/pVpb6QJsbnzDvVRpCMVsucPxrvvnhEhI3QuMNKVNyi+3Fv88gg7XsFR0h WByg==
X-Received: by 10.194.82.104 with SMTP id h8mr18819743wjy.3.1365783706303; Fri, 12 Apr 2013 09:21:46 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-188-167.as13285.net. [2.101.188.167]) by mx.google.com with ESMTPS id t7sm4215409wij.2.2013.04.12.09.21.44 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 09:21:45 -0700 (PDT)
Message-ID: <516834A5.1020209@gmail.com>
Date: Fri, 12 Apr 2013 17:21:57 +0100
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: mrex@sap.com
Subject: Re: Purpose of IESG Review
References: <20130412152617.438721A6AD@ld9781.wdf.sap.corp>
In-Reply-To: <20130412152617.438721A6AD@ld9781.wdf.sap.corp>
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: Fri, 12 Apr 2013 16:21:48 -0000

I have no interest in or knowledge of the technical details,
but there is a pretty complicated DISCUSS against this draft,
which doesn't look like rubber-stamping to me:
https://datatracker.ietf.org/doc/draft-ietf-pkix-rfc2560bis/ballot/

I assume you've already let the IESG know about the defects you're
concerned about.

  Brian

On 12/04/2013 16:26, Martin Rex wrote:
> Brian E Carpenter wrote:
>> Seeing randomly selected drafts as a Gen-ART reviewer, I can
>> say that serious defects quite often survive WG review and
>> sometimes survive IETF Last Call review, so the final review
>> by the IESG does serve a purpose.
> 
> I'm currently seeing a document with some serious defects in
> IETF Last Call (rfc2560bis) and an apparent desire to have
> it Rubberstamped by the IESG (recycling at Proposed Standard).
> 
> While that seems procedurally permitted for the IESG to do such
> rubberstamping (aka "waive") for a proposed standard
> (rfc2026, last paragraph on page 12):
> 
>    http://tools.ietf.org/html/rfc2026#page-12
> 
>    A Proposed Standard should have no known technical omissions with
>    respect to the requirements placed upon it.  However, the IESG may
>    waive this requirement in order to allow a specification to advance
>    to the Proposed Standard state when it is considered to be useful and
>    necessary (and timely) even with known technical omissions.
> 
> one should really consider the consequences of such a decision,
> especially for -bis and -ter documents.
> 
> The original draft (and now full) standard requires that such defects
> are removed _before_ the document is advanced.  So when "waiving" known
> defects/omissions (in particular obvious and formally provable ones),
> this means that there will have to be a ter document produced where
> this defects are fixed and this document be recycled at Proposed
> one more time before the standard can progress on the maturity level.
> 
> It turns out that for a non-negligible amount of the defects there
> is a constituency that want the defect to be retained rather than
> fixed, and they expect the IESG to waive defects on -bis, -ter etc.
> documents whenever it was previously accepted for Proposed with
> that defect.
> 
> 
>> IMHO, if the IESG members sticks to their own criteria at
>> http://www.ietf.org/iesg/statement/discuss-criteria.html,
>> i.e. do not DISCUSS a document for spurious reasons, they
>> are doing just fine. If they don't stick to those criteria,
>> complaint is justified.
>>
>> Of course this will always be a matter of judgment.
>>
>> Regards
>>    Brian
>>
>> On 11/04/2013 18:54, Joe Touch wrote:
>>> My concern is that by conflating their IESG position with their personal
>>> review, the document process is inappropriately delayed and that
>>> documents are modified to appease a small community that does not
>>> justify its position as representative.
> 
> What do you want to see the IESG do instead?
> 
> Simply Rubberstamp WG consensus?  That would turn the whole IESG
> diversity discussion into an absurd waste of time...
> 
> -Martin
> 

From Ted.Lemon@nominum.com  Fri Apr 12 09:31:10 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E10CC21F8F0E for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 09:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.362
X-Spam-Level: 
X-Spam-Status: No, score=-106.362 tagged_above=-999 required=5 tests=[AWL=0.237, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iyz87NlsGovK for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 09:31:10 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 579C221F8F07 for <ietf@ietf.org>; Fri, 12 Apr 2013 09:31:10 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUWg2zam6jVNId9eZ4+xR/Etg5QO6a6do@postini.com; Fri, 12 Apr 2013 09:31:10 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5C0B31B80AB for <ietf@ietf.org>; Fri, 12 Apr 2013 09:31:09 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 52132190061; Fri, 12 Apr 2013 09:31:09 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 12 Apr 2013 09:31:09 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<mrex@sap.com>" <mrex@sap.com>
Subject: Re: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: AQHONt2z+kkmqEfX7EKa70fj1HnPWJjSohUAgACJr4CAABIeAA==
Date: Fri, 12 Apr 2013 16:31:09 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775143616@mbx-01.win.nominum.com>
References: <20130412152617.438721A6AD@ld9781.wdf.sap.corp>
In-Reply-To: <20130412152617.438721A6AD@ld9781.wdf.sap.corp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AC3752C2668A8746B2D45FE36E62DA1E@nominum.com>
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: Fri, 12 Apr 2013 16:31:11 -0000

On Apr 12, 2013, at 11:26 AM, Martin Rex <mrex@sap.com> wrote:
> I'm currently seeing a document with some serious defects in
> IETF Last Call (rfc2560bis) and an apparent desire to have
> it Rubberstamped by the IESG (recycling at Proposed Standard).

FWIW, I raised the same question during IESG review.   It didn't seem like =
a "serious defect" to me, but it did seem like a strange design choice.   I=
 ultimately withdrew my objection after we walked through the problem.   If=
 we were doing a clean slate design, fixing the problem as you proposed wou=
ld be a net win.   Given that there are substantial existing deployments, i=
t doesn't look like a net win to me.

I think this is really a matter of judgment, not a matter of fact, so while=
 I sympathize that it didn't come out your way, I don't agree with you that=
 the wrong thing happened.


From mrex@sap.com  Fri Apr 12 11:04:20 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E50421F8B15 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 11:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OoORR5bWv6TS for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 11:04:20 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id AB5B821F8758 for <ietf@ietf.org>; Fri, 12 Apr 2013 11:04:19 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r3CI4HIR009033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 12 Apr 2013 20:04:17 +0200 (MEST)
Subject: Re: Purpose of IESG Review
In-Reply-To: <516834A5.1020209@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Fri, 12 Apr 2013 20:04:17 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130412180417.6D0F11A6AD@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: Fri, 12 Apr 2013 18:04:20 -0000

Brian E Carpenter wrote:
>
> I have no interest in or knowledge of the technical details,
> but there is a pretty complicated DISCUSS against this draft,
> which doesn't look like rubber-stamping to me:
> https://datatracker.ietf.org/doc/draft-ietf-pkix-rfc2560bis/ballot/
> 
> I assume you've already let the IESG know about the defects you're
> concerned about.

The concern I originally raised durint LC is primarily a defect of rfc5019
that rfc2560bis does not properly deal with, and is in theory fairly
trivial to fix.

A much more concerning defect has just recently been uncovered:
  http://www.ietf.org/mail-archive/web/pkix/current/msg32635.html

the complete absence of requirements to allow OCSP response caching
(and OCSP response cache updating),  which is going to become important
for the two work items that are currently active in TLS:
  - a TLS extension for multiple OCSP response stapling
  - a TLS caching extension

and I strongly believe that PKIX needs to fix that defect/omission
and clarify the OCSP response caching semantics in rfc2560bis
(and document requirements for "thisUpdate"), or this will result
in unexpected and undesirable behaviour (aka interop problems).


I have no implementation experience with OCSP, so a number of problems
will not be directly apparent to me.  But I'm really wondering why noone
who has implemented OCSP response caching so far (and I believe there
are implementations) has ever brought up this issue against rfc2560
so far.  This is close to impossible to miss _for_an_implementor_.  


-Martin

From eckert@cisco.com  Fri Apr 12 11:14:18 2013
Return-Path: <eckert@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 8384221F87E0 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 11:14:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.431
X-Spam-Level: 
X-Spam-Status: No, score=-10.431 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B9HfEvyr1JJa for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 11:14:17 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id CBEDD21F84B0 for <ietf@ietf.org>; Fri, 12 Apr 2013 11:14:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1452; q=dns/txt; s=iport; t=1365790457; x=1367000057; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=N6+YJRkBuFncRz5wqBNjlyKn75FckrvfQ7ulqCDXrsU=; b=GopwNNPDp3g/gwU8a802VSypE/2r4PB3XcnLER5uxAszo0QYSSkcrSGo nNU8spfAzVzY2IY27L3wa+fVoWn9YOmY+gkgP8EtCHXZ2p7s2LwNV+V+Z ucx7GqUXzdPQemR5njhTzdYZWSpMwInm0GNPwW75JxCiPtcMv0Hpy32QF k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAJhNaFGrRDoH/2dsb2JhbABGCoMGwheBDBZ0gh8BAQEDATo/BQsLGAklDwVJJ4d6Bb0GjVuBPAeCYGEDiQONfgGREYMrHA
X-IronPort-AV: E=Sophos;i="4.87,464,1363132800"; d="scan'208";a="78397786"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 12 Apr 2013 18:14:16 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r3CIEB6D030724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Apr 2013 18:14:11 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r3CICoVI015384;  Fri, 12 Apr 2013 11:13:05 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r3CICoI7015383; Fri, 12 Apr 2013 11:12:50 -0700
Date: Fri, 12 Apr 2013 11:12:50 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130412181250.GA14224@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51675819.9070302@gmail.com>
User-Agent: Mutt/1.4.2.2i
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, 12 Apr 2013 18:14:18 -0000

On Thu, Apr 11, 2013 at 04:40:57PM -0800, Melinda Shore wrote:
> My own feeling is that if we were to find that the
> numbers supported the notion that there's bias
> present in the system we probably couldn't do anything
> about it without tearing the organization apart, so,
> we live with bias, and trying to identify whether or
> not there's bias in the nomcom process would be something
> along the general lines of opening the gates of hell
> and we'd probably be better off not knowing for sure.

I still think that the IETF community at large has no intentional
diversity bias, so the process of discussing and analyzing
diversity in the context of leadership is to help better describe 
diversity induced job qualifications as well as uncovering any
potential unconscious bias to help overcoming it.

> But I digress.  It seems to me that it might be more
> useful to identify what it is you're trying to find out,
> first, and in this case I'm really not sure why Ray asked
> that particular question.

Right. Being nomcom, i am of course interested to see what
answers we can get to help improve analyzing our situation, so
whether or not we can create good analysis vs. divesity fators,
I think the questions i proposed just by themselves would give
a good insight about awareness in the community about the role
of leadership, and maybe give us some more insight into the possible
pool.

Cheers
    Toerless

From melinda.shore@gmail.com  Fri Apr 12 11:33:19 2013
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 2049A21F8D23 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 11:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.985
X-Spam-Level: *
X-Spam-Status: No, score=1.985 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RCVD_IN_XBL=3.033, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ni70eBmtTC1s for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 11:33:18 -0700 (PDT)
Received: from mail-da0-x22a.google.com (mail-da0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A908A21F8AA6 for <ietf@ietf.org>; Fri, 12 Apr 2013 11:33:18 -0700 (PDT)
Received: by mail-da0-f42.google.com with SMTP id n15so1250501dad.1 for <ietf@ietf.org>; Fri, 12 Apr 2013 11:33:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+4+qcKF4IPttoveAZ+RBgOShutlm3tFzs7ozMT6X5vE=; b=DK+hi8coL04oLsTP5WnRrgDmdagmMZAWCa+DdFTYk3bF0gfRbKZlXwIRWnO8nNdA/j HEIxZEOqAB8fTMGjSxNyVOBjIuZezCaA8X0Er7lnfTIiNB25ovPJeq6/3j/LoogwzWQd Zh5GMawZ09BuhlNemgjJUX+S+qxxBSZwoZG4wNeg4JDMScaiO6w7gxEWJw96J5vEmYpx w8Xi1zZSLr3k0olm2Nq4VpiFp520yUNh2DAsBrEPt+7Vudv6ehFIzt8TVdwTvoJ69/G2 fsa/59SSYcD/qXydpNQd1QRLozryjvpHiD1gqZQ2Fi0FnfBslV64ltF9wNygUQxOg59/ SGNA==
X-Received: by 10.66.248.99 with SMTP id yl3mr17145468pac.134.1365791598457; Fri, 12 Apr 2013 11:33:18 -0700 (PDT)
Received: from [10.252.122.254] ([198.134.93.254]) by mx.google.com with ESMTPS id wz9sm9522692pbc.5.2013.04.12.11.33.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 11:33:17 -0700 (PDT)
Message-ID: <51685369.4000306@gmail.com>
Date: Fri, 12 Apr 2013 10:33:13 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Toerless Eckert <eckert@cisco.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com>
In-Reply-To: <20130412181250.GA14224@cisco.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: Fri, 12 Apr 2013 18:33:19 -0000

On 4/12/2013 10:12 AM, Toerless Eckert wrote:
> I still think that the IETF community at large has no intentional
> diversity bias, so the process of discussing and analyzing
> diversity in the context of leadership is to help better describe 
> diversity induced job qualifications as well as uncovering any
> potential unconscious bias to help overcoming it.

I think it's unintentional, as well, but I'm not sure
that's *much* of an improvement over malicious bias.
It certainly makes it far, far, far more difficult to
address.  As I said I think that looking at the pool of
nominees who've accepted their nominations and comparing
it to the pool of people selected would provide one
very rough measure of bias (explicit or otherwise) in
one stage of the process.

Melinda


From hotz@jpl.nasa.gov  Thu Apr 11 17:32:04 2013
Return-Path: <hotz@jpl.nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8823621F89A6; Thu, 11 Apr 2013 17:32:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aqjs4z4TLyUC; Thu, 11 Apr 2013 17:32:03 -0700 (PDT)
Received: from mail.jpl.nasa.gov (mailhost.jpl.nasa.gov [128.149.139.109]) by ietfa.amsl.com (Postfix) with ESMTP id 1A18421F892D; Thu, 11 Apr 2013 17:32:02 -0700 (PDT)
Received: from laphotz.jpl.nasa.gov (laphotz.jpl.nasa.gov [128.149.133.44]) (authenticated (0 bits)) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r3C0VjmB023159 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Thu, 11 Apr 2013 17:31:46 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
In-Reply-To: <CD8AF5C0.603DB%stefan@aaa-sec.com>
Date: Thu, 11 Apr 2013 17:31:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <04F36061-25C5-4159-A724-26B192C120DE@jpl.nasa.gov>
References: <CD8AF5C0.603DB%stefan@aaa-sec.com>
To: Stefan Santesson <stefan@aaa-sec.com>
X-Mailer: Apple Mail (2.1503)
X-Source-Sender: hotz@jpl.nasa.gov
X-AUTH: Authorized
X-Mailman-Approved-At: Fri, 12 Apr 2013 12:02:36 -0700
Cc: pkix@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, 12 Apr 2013 00:32:04 -0000

On Apr 10, 2013, at 3:02 AM, Stefan Santesson <stefan@aaa-sec.com> =
wrote:

> Nothing has changed in this regard.
>=20
> The good response is pretty clear that it by default provides =
information
> that the cert is not on a black-list (is not know to be revoked).
> However, it is also made clear that extensions may be used to expand =
this
> default information about the status.
>=20
> This is how it always have been, and still is in RFC 256bis.

So a non-issued cert may be "good".

> The revoked response simply means that the certificate is revoked.
> Combined with the new extension, it MAY also be used for non-issued =
certs.

So a non-issued cert may be "revoked".

> It's really as simple as that.

I would have thought that what was simple was to say a non-issued cert =
was "unknown", since it's neither known-good, nor known-revoked.  Is =
there any collection of extensions which will allow an RP to know, for =
sure, what value will be returned for a never-issued cert?

> It is only the discussion on this list that is confusing and that has
> managed turn something really simple into a complicated debate.

What *I* find confusing is the apparent degree of belief that it is =
possible to improve 2560 and simultaneously to maintain backward =
compatibility.  That should only be possible if there are some =
previously-ignored extensions which alter the semantics of the =
information --- effectively creating a version 2 protocol. =20

I don't find the claim that nothing has changed helpful.

What I would find helpful, and what I think some people really would =
like, is for OCSP to be able to provide white-list information in =
addition to the previous black-list information.  When I read through =
2560bis, I could not tell if there was an extension which would allow an =
RP to tell if "good" actually meant a cert was on the white list (and to =
know the responder has the white list), or merely not on the black list. =
 (Yes, I'm repeating myself.  Am I making more sense, or just wasting =
everyone's time?)

> /Stefan
>=20
>=20
> On 4/8/13 9:35 PM, "Henry B. Hotz" <hotz@jpl.nasa.gov> wrote:
>=20
>> Actually, what I get from this and all the other discussions is that =
it's
>> unclear if the updated OCSP satisfies the "suitability for the =
intended
>> purpose" test.  Or at least it fails the KISS principle w.r.t. that.
>>=20
>> Rephrasing:  an OCSP client should be able to tell from an OCSP =
response
>> if:  a) the subject cert is on the CAs white list, b) the subject =
cert is
>> on the CAs black list, c) the subject cert is not on either list, or
>> finally d) the OCSP server is obsolete, and doesn't support making =
those
>> distinctions.  It's not trivial to see how to parse 2560bis responses
>> w.r.t. those cases, therefore it's highly likely that computational
>> complexity will prevent us from doing so.  Even if that's not =
actually
>> the case, then implementor misunderstandings will prevent us from =
doing
>> so in practice.
>>=20
>> Therefore I vote against moving this draft forward.  I just don't see =
the
>> point.
>>=20
>> If someone were to write an informational RFC which explained how to
>> determine which of the 4 cases an OCSP response fell into, AND if =
said
>> RFC also convinced me that the decision process was easy to =
understand,
>> THEN I would change my vote.  Obviously an appendix in 2560bis would
>> serve just as well.

------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu


From lberger@labn.net  Fri Apr 12 12:04:55 2013
Return-Path: <lberger@labn.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 80D7821F8EBD for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:04:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.304
X-Spam-Level: 
X-Spam-Status: No, score=-102.304 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TCUX86pB6woF for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:04:55 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id E42CA21F8EB7 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:04:54 -0700 (PDT)
Received: (qmail 7373 invoked by uid 0); 12 Apr 2013 19:04:30 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy7.bluehost.com with SMTP; 12 Apr 2013 19:04:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject:References:In-Reply-To:Message-ID:Date:CC:To:From; bh=gK7x+P5vPfsAgx4CJ+zRViCCtt4SdArLuXhChh71GzM=;  b=IPN/HAUSEIFh/z8zzOeXu2n7gd8Lxe7So+2l6jYOrINGSimNixlGKCmmQsxVhr0Y+FkE2O+9n/mFnkOQsH9PTHWj8k+FX3kh+yT0k2IVn+pI2eOKyDNdFgJ/TpOZ3qSD;
Received: from box313.bluehost.com ([69.89.31.113]:48398 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1UQjGv-0007Z3-QM; Fri, 12 Apr 2013 13:04:29 -0600
From: Lou Berger <lberger@labn.net>
To: Melinda Shore <melinda.shore@gmail.com>, Toerless Eckert <eckert@cisco.com>
Date: Fri, 12 Apr 2013 15:04:27 -0400
Message-ID: <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <51685369.4000306@gmail.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 AquaMail/1.2.3.4 (build: 2100270)
Subject: Re: IETF Diversity Question on Berlin Registration?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.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, 12 Apr 2013 19:04:55 -0000

On April 12, 2013 2:33:13 PM Melinda Shore <melinda.shore@gmail.com> wrote:
> On 4/12/2013 10:12 AM, Toerless Eckert wrote:
> > I still think that the IETF community at large has no intentional
> > diversity bias, so the process of discussing and analyzing
> > diversity in the context of leadership is to help better describe 
> diversity induced job qualifications as well as uncovering any
> > potential unconscious bias to help overcoming it.
>
> I think it's unintentional, as well, but I'm not sure
> that's *much* of an improvement over malicious bias.
> It certainly makes it far, far, far more difficult to
> address.  As I said I think that looking at the pool of
> nominees who've accepted their nominations and comparing
> it to the pool of people selected would provide one
> very rough measure of bias (explicit or otherwise) in
> one stage of the process.
>

While I've been very reluctant to jump on this topic, I have to ask what's 
the basis for this assertion?  A willingness to do/volunteer for a job says 
nothing about one's qualifications for a job.  Now if we somehow could 
compare 'qualified' nominees vs selected, I'd agree that that could be 
interesting....

Lou

> Melinda
>
>



From melinda.shore@gmail.com  Fri Apr 12 12:11:40 2013
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 6154521F8F33 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.468
X-Spam-Level: 
X-Spam-Status: No, score=0.468 tagged_above=-999 required=5 tests=[AWL=1.516,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HR+qHmcxVsFE for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:11:38 -0700 (PDT)
Received: from mail-da0-x22d.google.com (mail-da0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id B0B2921F8F13 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:11:37 -0700 (PDT)
Received: by mail-da0-f45.google.com with SMTP id v40so1269433dad.4 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:11:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VjnXUhVO28EVR+LCZvSgQZcvf82ieYv1Rq2dr6kAeb8=; b=efwYaq2ub6lWm+i9+Q0cG8dyLHyBgFFQC8xxDjFi4XuSDZc+JKYzG97pp4iAsO9MRF OS0ltvhkaog6RyLz0dmZBokUnaOOYdrvrI50REs+g1ViKsE4bYSB2jlyTWwTCeFh87Av N/uC+CcB9DhrwGZctJcnbCaHx2i2MWtfzE+C0hJCly+dlf0Mf7WF+z3OR5RyMnaqwqQv Pn7cGWM7VswbH06Tn2eXdBBITSesfUJ3AW0VmAsUdvCRHpui17OAPrB3+fhiSuSQBN+n fRA6o4KKJZEiVA/4b1N9GuGDhhKkFfWBlVo1bB06NJR+xFvT8ZWE13yEI3VtvO878ubx j4ZA==
X-Received: by 10.66.149.227 with SMTP id ud3mr14422974pab.33.1365793897396; Fri, 12 Apr 2013 12:11:37 -0700 (PDT)
Received: from [10.252.122.254] ([198.134.89.98]) by mx.google.com with ESMTPS id ak5sm10646400pac.4.2013.04.12.12.11.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 12:11:36 -0700 (PDT)
Message-ID: <51685C64.3010803@gmail.com>
Date: Fri, 12 Apr 2013 11:11:32 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.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: Fri, 12 Apr 2013 19:11:40 -0000

On 4/12/2013 11:04 AM, Lou Berger wrote:
> While I've been very reluctant to jump on this topic, I have to ask
> what's the basis for this assertion? 

I think the numbers are pretty compelling, which is why
I think they would deserve scrutiny if there's the
possibility of remediation if a problem is identified.
However, it's pretty clear from the tone of the discussion
so far that no remediation would be possible, and so I
actually think it's probably a bad idea to attack the
question.  That does not mean, however, that the question
does not exist.

And I don't know if you intended to or not, but what you
communicated is "The best candidates are nearly always
western white guys," since that's who's being selected.
That's a problematic suggestion.

Melinda


From abdussalambaryun@gmail.com  Fri Apr 12 12:24:20 2013
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 062EC21F8ECE for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.069
X-Spam-Level: 
X-Spam-Status: No, score=-3.069 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHRpFPr-MEiN for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:24:19 -0700 (PDT)
Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com [209.85.160.48]) by ietfa.amsl.com (Postfix) with ESMTP id 7ADDD21F8ECC for <ietf@ietf.org>; Fri, 12 Apr 2013 12:24:18 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id xb4so1560227pbc.7 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=SD7SpYr6QdHo1msW20CODHODDt+CNDWRJNOjeteDgJc=; b=Sm5ZVBK1xnAXsa3JDtD1DjCh9c7vO41RTwmshO+KJ3WXy546q6l3sr2toCIYKC5AEv OEuBgX2lQbkp6n5MzC6ATnxKwDG//8cew1BuLOtQPhzQOgnVgNvgMQq6y43qPyR3DcxO JhGpb+wRR7fQfTJuBGbQpoL7HlA74cEa/+jh8XeGrITvspLxtsP/WZUfpfFVoMEObQ+H Fz1hbKBmcwqS1U9eSKT9OuGJai4UJ8BKAKe3Num/91KLRTOSEOfIQFutAULckrpCyTws aIRm8Y+F29r3O/aPnKDVDL+nqti8sMGZbKXSWf0nAAYpXX3TBxppvbZbV2Z1wlXlHXhL kQOQ==
MIME-Version: 1.0
X-Received: by 10.66.89.199 with SMTP id bq7mr17308958pab.202.1365794648708; Fri, 12 Apr 2013 12:24:08 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Fri, 12 Apr 2013 12:24:08 -0700 (PDT)
In-Reply-To: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com>
References: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com>
Date: Fri, 12 Apr 2013 20:24:08 +0100
Message-ID: <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.com>
Subject: Re: Purpose of IESG Review
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d042ef591df5bbe04da2ed8ff
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Apr 2013 19:24:20 -0000

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

How can a memebr of staff in a company argue with the manager about the
manager's decisions or performance? Only Owners/shareholders can question
managers and staff. IMO, the meeting/list discussions on any issue
without an I-D written is the staff talking/working.

If you write an I-D and to update the procedure related to the subject, you
should consider many issues and I think will need many years of
discussions, but then better effort result. IMHO, writing an I-D and
getting back up by community discussion (with rough consensus) is in the
top level and is the owner talking.

I hope that when I review and comment on an I-D, it should be considered as
one owner is talking, but seems like editors think they are the only
owners. When IESG comment on the I-D it is managers/excutives talking. All
parts are important to the best of output.

AB


On Fri, Apr 12, 2013 at 10:33 AM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> Reply to below message
> The subject SHOULD be: Evaluating Review Process Performance
> I prefer the Subject is: Evaluating WG input, the WG review process,
> and the WG output, NOT IESG review.
>
> ------------------------------------------------------------------------------------------------
>
> Hi Joe,
>
> My comments mostly is on your message, but I comment also on I-Ds or
> RFCs related to IETF (including joky RFCs).
>
> I don't think it is write to evaluate the review of an IESG as long as
> when we created the I-D and adopted it into IETF SYSTEM, it is already
> agreeing on the methods of process that I-D is going through. So the
> problem is to evaluate three things not one: 1) the input, 2) the
> process review, 3) the output.
>
> We may make different input methods that go to another body than IESG,
> but if you decided to make I-D under IETF current procedure, it will
> have to go to IESG.
>
> I think the IESG are doing an excellent job, but it is best them to
> evaluate their performance not the community. Or it is better to find
> a body that evaluates the IESG performance not on this list.
>
> I consider your input on the list as a complain about the process, so
> I ask you to notice that your input has an error that needs evaluation
> befor going to process evaluation. You may evaluate output, but I
> remind you to evaluate input of WGs and inputs of individuals.
>
> I think the BIG problem of delay in I-Ds or RFC, is the cause of the
> WG not the IESG, if you do an excellent WG processes you will get
> quick results at IESG.
>
> AB
> +++++++++++++
> Hi, all,
>
>
> As an author who has had (and has) multiple documents in IESG review,
> I've noticed an increasing trend of this step to go beyond (IMO) its
> documented and original intent (BCP 9, currently RFC 2026):
>    The IESG shall determine whether or not a specification submitted to
>    it according to section 6.1.1 satisfies the applicable criteria for
>    the recommended action (see sections 4.1 and 4.2), and shall in
>    addition determine whether or not the technical quality and clarity
>    of the specification is consistent with that expected for the
>    maturity level to which the specification is recommended.
>
>
> Although I appreciate that IESG members are often overloaded, and the
> IESG Review step is often the first time many see these documents, I
> believe they should be expected to more clearly differentiate their
> "IESG Review" (based on the above criteria) - and its accompanying
> Position ballot, with their personal review.
>
> My concern is that by conflating their IESG position with their
> personal review, the document process is inappropriately delayed and
> that documents are modified to appease a small community that does not
> justify its position as representative.
> How do others feel about this?
>
> Joe
>

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

<div dir=3D"ltr"><div>How can a memebr of staff in a company argue with the=
 manager about the manager&#39;s decisions or performance? Only Owners/shar=
eholders can question managers and staff. IMO, the=A0meeting/list discussio=
ns on any issue without=A0an I-D written=A0is the staff talking/working.</d=
iv>
<div>=A0</div><div>If you write an I-D and to update the procedure related =
to the subject, you should consider many issues and I think will need many =
years of discussions, but=A0then better effort result. IMHO, writing an I-D=
 and getting back up by community discussion=A0(with rough consensus)=A0is =
in the top level=A0and is the owner talking.</div>
<div>=A0</div><div>I hope that when I review and comment on an I-D, it shou=
ld be considered as one owner is talking, but seems like editors think they=
 are the only owners. When IESG comment on the I-D it is managers/excutives=
 talking. All parts are important to the best of output.</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Fri, Apr 12, 2013 at 10:33 AM, Abdussalam Baryun <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:abdussalambaryun@gmail.com" target=3D"=
_blank">abdussalambaryun@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">Reply to below message<br>
The subject SHOULD be: Evaluating Review Process Performance<br>
I prefer the Subject is: Evaluating WG input, the WG review process,<br>
and the WG output, NOT IESG review.<br>
---------------------------------------------------------------------------=
---------------------<br>
<br>
Hi Joe,<br>
<br>
My comments mostly is on your message, but I comment also on I-Ds or<br>
RFCs related to IETF (including joky RFCs).<br>
<br>
I don&#39;t think it is write to evaluate the review of an IESG as long as<=
br>
when we created the I-D and adopted it into IETF SYSTEM, it is already<br>
agreeing on the methods of process that I-D is going through. So the<br>
problem is to evaluate three things not one: 1) the input, 2) the<br>
process review, 3) the output.<br>
<br>
We may make different input methods that go to another body than IESG,<br>
but if you decided to make I-D under IETF current procedure, it will<br>
have to go to IESG.<br>
<br>
I think the IESG are doing an excellent job, but it is best them to<br>
evaluate their performance not the community. Or it is better to find<br>
a body that evaluates the IESG performance not on this list.<br>
<br>
I consider your input on the list as a complain about the process, so<br>
I ask you to notice that your input has an error that needs evaluation<br>
befor going to process evaluation. You may evaluate output, but I<br>
remind you to evaluate input of WGs and inputs of individuals.<br>
<br>
I think the BIG problem of delay in I-Ds or RFC, is the cause of the<br>
WG not the IESG, if you do an excellent WG processes you will get<br>
quick results at IESG.<br>
<br>
AB<br>
+++++++++++++<br>
Hi, all,<br>
<br>
<br>
As an author who has had (and has) multiple documents in IESG review,<br>
I&#39;ve noticed an increasing trend of this step to go beyond (IMO) its<br=
>
documented and original intent (BCP 9, currently RFC 2026):<br>
=A0 =A0The IESG shall determine whether or not a specification submitted to=
<br>
=A0 =A0it according to section 6.1.1 satisfies the applicable criteria for<=
br>
=A0 =A0the recommended action (see sections 4.1 and 4.2), and shall in<br>
=A0 =A0addition determine whether or not the technical quality and clarity<=
br>
=A0 =A0of the specification is consistent with that expected for the<br>
=A0 =A0maturity level to which the specification is recommended.<br>
<br>
<br>
Although I appreciate that IESG members are often overloaded, and the<br>
IESG Review step is often the first time many see these documents, I<br>
believe they should be expected to more clearly differentiate their<br>
&quot;IESG Review&quot; (based on the above criteria) - and its accompanyin=
g<br>
Position ballot, with their personal review.<br>
<br>
My concern is that by conflating their IESG position with their<br>
personal review, the document process is inappropriately delayed and<br>
that documents are modified to appease a small community that does not<br>
justify its position as representative.<br>
How do others feel about this?<br>
<br>
Joe<br>
</blockquote></div><br></div>

--f46d042ef591df5bbe04da2ed8ff--

From arturo.servin@gmail.com  Fri Apr 12 12:29:01 2013
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 966F921F8F3C for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:29:01 -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=0.300, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gAcX96GCL7kA for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:29:01 -0700 (PDT)
Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 0DF2021F8F13 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:29:00 -0700 (PDT)
Received: by mail-yh0-f50.google.com with SMTP id 25so480920yhr.9 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:29:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=B9AT2/I+c3WWML2QDMQokmF9rnSGChiTTnhQ3DiNhtQ=; b=RrTNxl1fu5CNTFuEzmcfWvJ1MGWpE8e8QoOxioFJZ8F70hwKByeRwSLSNJi9G0GyAm r4gRRVuCAb4pIg1Aj7q9LHO50nfxdsJTgQU5rwlU44dg4xR/kVYabc5rGINDBrO6HQpR C4um2Q1tiWpIo1Vf45dhA2p1RGhVIhuZ/Fcu3x2GMYUYqTNS9sRcyk0RT1bAFhgksCUR WMka3KfkGrsWOpSut8y+4wxC3hUt1UzJsWdjCSjv60dFkHd4R2x7AxnkEKncIa2d01dn z+Ehs983IaIWslP35YscuXZUmWLF956F7wasFjYLj2sy42lM5IsIPA2NMiPC+RNAbEA6 JutQ==
X-Received: by 10.236.151.20 with SMTP id a20mr7723613yhk.9.1365794940409; Fri, 12 Apr 2013 12:29:00 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:3906:b16b:a2de:9407]) by mx.google.com with ESMTPS id a26sm13515308yhe.9.2013.04.12.12.28.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 12:28:58 -0700 (PDT)
Message-ID: <51686076.3010508@gmail.com>
Date: Fri, 12 Apr 2013 16:28:54 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu>
In-Reply-To: <5166F8BD.7010308@isi.edu>
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, 12 Apr 2013 19:29:01 -0000

	Not answering any particular post. Just a comment.

	The IESG should be there to attest that the IETF procedure was followed
and the document reached consensus in the WG and in the IETF LC and it
was successfully reviewed by the Gen-ART. If it wasn't then this
particular process should be reviewed and take actions accordingly (e.g.
returning the document to the wg).

	But if a single individual of the IESG can technically challenge and
change the work of a whole WG and the IETF, then we have something wrong
in our process because that means that the document had a serious
problem and we didn't spot it in the process or an IESG member is using
its power to change a document according to its personal beliefs.

Just a thought,
as

On 4/11/13 2:54 PM, Joe Touch wrote:
> Hi, all,
> 
> As an author who has had (and has) multiple documents in IESG review,
> I've noticed an increasing trend of this step to go beyond (IMO) its
> documented and original intent (BCP 9, currently RFC 2026):
> 
>    The IESG shall determine whether or not a specification submitted to
>    it according to section 6.1.1 satisfies the applicable criteria for
>    the recommended action (see sections 4.1 and 4.2), and shall in
>    addition determine whether or not the technical quality and clarity
>    of the specification is consistent with that expected for the
>    maturity level to which the specification is recommended.
> 
> Although I appreciate that IESG members are often overloaded, and the
> IESG Review step is often the first time many see these documents, I
> believe they should be expected to more clearly differentiate their
> "IESG Review" (based on the above criteria) - and its accompanying
> Position ballot, with their personal review.
> 
> My concern is that by conflating their IESG position with their personal
> review, the document process is inappropriately delayed and that
> documents are modified to appease a small community that does not
> justify its position as representative.
> 
> How do others feel about this?
> 
> Joe

From melinda.shore@gmail.com  Fri Apr 12 12:32:47 2013
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 6D9E421F863B for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.565
X-Spam-Level: 
X-Spam-Status: No, score=-1.565 tagged_above=-999 required=5 tests=[AWL=2.034,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MU0wAigBLj1G for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:32:47 -0700 (PDT)
Received: from mail-pb0-f42.google.com (mail-pb0-f42.google.com [209.85.160.42]) by ietfa.amsl.com (Postfix) with ESMTP id F2D1E21F8630 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:32:46 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id up7so1575659pbc.15 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:32:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=bfAB/xAcKT5BlK7mBYKr/xfrJRmmSVuYhB1/ejzaNQU=; b=B/bBXLX74I0KYlm4HzQS7/gRXTZKw2/jt29el6elK0STum5buoQ0e1ow6WmfUphokK rQoRPUaZstgfcSImTOfpN4nRiMWbjbOcbewtKtb0RDt2s6Bz9NJDVGID/i1IeSL9np2s I0Naw5NVI20XR2VRWQPeU9ckpYBH6rqKdOC2a6INARVQGryU57eBFQUiTajnwE3ACOVq pk6wy716L20QPo3NmD7F+NeWpF0MnNikwfZJOKSinDXJ6KW/sAjQuvu3t/zbRq6Qya4C Heq2uw2iGJLaYc6Qz/B43p27NcVpWuRPzoSzMtZZoxA70tUazLJQu8agt1++yOOjy3GR AmdQ==
X-Received: by 10.68.216.37 with SMTP id on5mr16983388pbc.35.1365795166821; Fri, 12 Apr 2013 12:32:46 -0700 (PDT)
Received: from [10.252.122.254] ([198.134.89.98]) by mx.google.com with ESMTPS id fb7sm10683607pab.16.2013.04.12.12.32.44 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 12:32:45 -0700 (PDT)
Message-ID: <5168615A.1030907@gmail.com>
Date: Fri, 12 Apr 2013 11:32:42 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <51686076.3010508@gmail.com>
In-Reply-To: <51686076.3010508@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: Fri, 12 Apr 2013 19:32:47 -0000

On 4/12/2013 11:28 AM, Arturo Servin wrote:
> 	But if a single individual of the IESG can technically challenge and
> change the work of a whole WG and the IETF, then we have something wrong
> in our process because that means that the document had a serious
> problem and we didn't spot it in the process or an IESG member is using
> its power to change a document according to its personal beliefs.

We've had that happen in a working group I chair and I do
think that it was the result of process failure in the
working group.  That said, there seemed to be broad
agreement across the IESG that the document had certain
specific flaws - I do think there's a problem if a single
IESG member can reject working group consensus and hold
up a document - it seems as if there should be wider
agreement that the document is too flawed to progress.

Melinda



From abdussalambaryun@gmail.com  Fri Apr 12 12:58:55 2013
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 D70E021F8689 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.216
X-Spam-Level: 
X-Spam-Status: No, score=-2.216 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16iUnqejV0pS for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 12:58:54 -0700 (PDT)
Received: from mail-da0-x22a.google.com (mail-da0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D9CB121F8659 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:58:54 -0700 (PDT)
Received: by mail-da0-f42.google.com with SMTP id n15so1269559dad.29 for <ietf@ietf.org>; Fri, 12 Apr 2013 12:58:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=Ea59cXt9N8DFTbWgzbgQ1/YRqSaFLSPN9UaBfmrKYyM=; b=f6lAH/0+zPjNgX0fCVAUriJoSpFjIE6tlQb/7Q5ggYZ5RfdbkbttI6WsVp4L4ZKVG7 p7t8ZSNGVGcOsX0Ehm0diW8x4tXt4s6kBcHvjemrzLtYXrjddXK+1+sZ25WgYLM2+oCV Fm00Hy0IrAOZbLyUWoRrDHVXCCMg03uf0eXwoOvTSGy2hv8Fg2EaeYzqpsI9dzcJiTZy FxUfamyngBk396KM1xeeeK7KIF03x+Jk7BZgfAXxlAOp74xSZllvgurLZve+LPA43WGH CF7OdR6fHV0xkAoCEa4+Ttru5vvLbEoFKGv/xMeeWkQBXVryFRbv+nk7KhEv7nHyJPNk 9LAw==
MIME-Version: 1.0
X-Received: by 10.69.12.37 with SMTP id en5mr4259663pbd.93.1365796734623; Fri, 12 Apr 2013 12:58:54 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Fri, 12 Apr 2013 12:58:54 -0700 (PDT)
Date: Fri, 12 Apr 2013 20:58:54 +0100
Message-ID: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com>
Subject: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b67422033e72b04da2f55cf
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Apr 2013 19:58:56 -0000

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

I just change the subject because I still beleive the problem with review
is in the WG not IESG. Some WGs have few reviews on each WG document, that
may not be bad, but I think having only one review or comment (excluding
authors) within a WGLC is wrong in a WG review process. I think WG chair
can find two participants to do it.

I recommend WG's process to change their purpose so we have to get *two
participants* which are not authors to review the work and comment within
WGLC (even small text comment is ok). I recommend WG chairs to think about
this proposal, if not then I will try write an I-D for this and communicate
with community.

AB

On Fri, Apr 12, 2013 at 8:24 PM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> How can a memebr of staff in a company argue with the manager about the
> manager's decisions or performance? Only Owners/shareholders can question
> managers and staff. IMO, the meeting/list discussions on any issue
> without an I-D written is the staff talking/working.
>
> If you write an I-D and to update the procedure related to the subject,
> you should consider many issues and I think will need many years of
> discussions, but then better effort result. IMHO, writing an I-D and
> getting back up by community discussion (with rough consensus) is in the
> top level and is the owner talking.
>
> I hope that when I review and comment on an I-D, it should be considered
> as one owner is talking, but seems like editors think they are the only
> owners. When IESG comment on the I-D it is managers/excutives talking. All
> parts are important to the best of output.
>
> AB
>
>
> On Fri, Apr 12, 2013 at 10:33 AM, Abdussalam Baryun <
> abdussalambaryun@gmail.com> wrote:
>
>> Reply to below message
>> The subject SHOULD be: Evaluating Review Process Performance
>> I prefer the Subject is: Evaluating WG input, the WG review process,
>> and the WG output, NOT IESG review.
>>
>> ------------------------------------------------------------------------------------------------
>>
>> Hi Joe,
>>
>> My comments mostly is on your message, but I comment also on I-Ds or
>> RFCs related to IETF (including joky RFCs).
>>
>> I don't think it is write to evaluate the review of an IESG as long as
>> when we created the I-D and adopted it into IETF SYSTEM, it is already
>> agreeing on the methods of process that I-D is going through. So the
>> problem is to evaluate three things not one: 1) the input, 2) the
>> process review, 3) the output.
>>
>> We may make different input methods that go to another body than IESG,
>> but if you decided to make I-D under IETF current procedure, it will
>> have to go to IESG.
>>
>> I think the IESG are doing an excellent job, but it is best them to
>> evaluate their performance not the community. Or it is better to find
>> a body that evaluates the IESG performance not on this list.
>>
>> I consider your input on the list as a complain about the process, so
>> I ask you to notice that your input has an error that needs evaluation
>> befor going to process evaluation. You may evaluate output, but I
>> remind you to evaluate input of WGs and inputs of individuals.
>>
>> I think the BIG problem of delay in I-Ds or RFC, is the cause of the
>> WG not the IESG, if you do an excellent WG processes you will get
>> quick results at IESG.
>>
>> AB
>> +++++++++++++
>> Hi, all,
>>
>>
>> As an author who has had (and has) multiple documents in IESG review,
>> I've noticed an increasing trend of this step to go beyond (IMO) its
>> documented and original intent (BCP 9, currently RFC 2026):
>>    The IESG shall determine whether or not a specification submitted to
>>    it according to section 6.1.1 satisfies the applicable criteria for
>>    the recommended action (see sections 4.1 and 4.2), and shall in
>>    addition determine whether or not the technical quality and clarity
>>    of the specification is consistent with that expected for the
>>    maturity level to which the specification is recommended.
>>
>>
>> Although I appreciate that IESG members are often overloaded, and the
>> IESG Review step is often the first time many see these documents, I
>> believe they should be expected to more clearly differentiate their
>> "IESG Review" (based on the above criteria) - and its accompanying
>> Position ballot, with their personal review.
>>
>> My concern is that by conflating their IESG position with their
>> personal review, the document process is inappropriately delayed and
>> that documents are modified to appease a small community that does not
>> justify its position as representative.
>> How do others feel about this?
>>
>> Joe
>>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">I just change the subject becau=
se I still beleive the problem with review is in the WG not IESG. Some WGs=
=A0have few reviews on each WG document, that may not be bad, but I think h=
aving only one review or comment (excluding authors) within a WGLC is wrong=
 in a WG review process. I think WG chair can find=A0two participants to do=
 it.</div>
<div class=3D"gmail_extra">=A0</div><div class=3D"gmail_extra">I recommend =
WG&#39;s=A0process to change their purpose so we have to get *two participa=
nts* which are not authors to review the work and comment within WGLC (even=
 small text comment is ok). I recommend WG chairs to think about this propo=
sal, if not then I will try write an I-D for this and communicate with comm=
unity.</div>
<div class=3D"gmail_extra">=A0</div><div class=3D"gmail_extra">AB<br><br></=
div><div class=3D"gmail_quote">On Fri, Apr 12, 2013 at 8:24 PM, Abdussalam =
Baryun <span dir=3D"ltr">&lt;<a href=3D"mailto:abdussalambaryun@gmail.com" =
target=3D"_blank">abdussalambaryun@gmail.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote"><div dir=3D"ltr"><div>How can a memebr of staff in a compa=
ny argue with the manager about the manager&#39;s decisions or performance?=
 Only Owners/shareholders can question managers and staff. IMO, the=A0meeti=
ng/list discussions on any issue without=A0an I-D written=A0is the staff ta=
lking/working.</div>

<div>=A0</div><div>If you write an I-D and to update the procedure related =
to the subject, you should consider many issues and I think will need many =
years of discussions, but=A0then better effort result. IMHO, writing an I-D=
 and getting back up by community discussion=A0(with rough consensus)=A0is =
in the top level=A0and is the owner talking.</div>

<div>=A0</div><div>I hope that when I review and comment on an I-D, it shou=
ld be considered as one owner is talking, but seems like editors think they=
 are the only owners. When IESG comment on the I-D it is managers/excutives=
 talking. All parts are important to the best of output.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div>=A0</div><div>AB</div></font></span></div><div class=3D"HOEnZb"><div c=
lass=3D"h5"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Fri, Apr 12, 2013 at 10:33 AM, Abdussalam Baryun <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:abdussalambaryun@gmail.com" target=3D"_blank">abdussalambar=
yun@gmail.com</a>&gt;</span> wrote:<br>

<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">Reply to below message<br>
The subject SHOULD be: Evaluating Review Process Performance<br>
I prefer the Subject is: Evaluating WG input, the WG review process,<br>
and the WG output, NOT IESG review.<br>
---------------------------------------------------------------------------=
---------------------<br>
<br>
Hi Joe,<br>
<br>
My comments mostly is on your message, but I comment also on I-Ds or<br>
RFCs related to IETF (including joky RFCs).<br>
<br>
I don&#39;t think it is write to evaluate the review of an IESG as long as<=
br>
when we created the I-D and adopted it into IETF SYSTEM, it is already<br>
agreeing on the methods of process that I-D is going through. So the<br>
problem is to evaluate three things not one: 1) the input, 2) the<br>
process review, 3) the output.<br>
<br>
We may make different input methods that go to another body than IESG,<br>
but if you decided to make I-D under IETF current procedure, it will<br>
have to go to IESG.<br>
<br>
I think the IESG are doing an excellent job, but it is best them to<br>
evaluate their performance not the community. Or it is better to find<br>
a body that evaluates the IESG performance not on this list.<br>
<br>
I consider your input on the list as a complain about the process, so<br>
I ask you to notice that your input has an error that needs evaluation<br>
befor going to process evaluation. You may evaluate output, but I<br>
remind you to evaluate input of WGs and inputs of individuals.<br>
<br>
I think the BIG problem of delay in I-Ds or RFC, is the cause of the<br>
WG not the IESG, if you do an excellent WG processes you will get<br>
quick results at IESG.<br>
<br>
AB<br>
+++++++++++++<br>
Hi, all,<br>
<br>
<br>
As an author who has had (and has) multiple documents in IESG review,<br>
I&#39;ve noticed an increasing trend of this step to go beyond (IMO) its<br=
>
documented and original intent (BCP 9, currently RFC 2026):<br>
=A0 =A0The IESG shall determine whether or not a specification submitted to=
<br>
=A0 =A0it according to section 6.1.1 satisfies the applicable criteria for<=
br>
=A0 =A0the recommended action (see sections 4.1 and 4.2), and shall in<br>
=A0 =A0addition determine whether or not the technical quality and clarity<=
br>
=A0 =A0of the specification is consistent with that expected for the<br>
=A0 =A0maturity level to which the specification is recommended.<br>
<br>
<br>
Although I appreciate that IESG members are often overloaded, and the<br>
IESG Review step is often the first time many see these documents, I<br>
believe they should be expected to more clearly differentiate their<br>
&quot;IESG Review&quot; (based on the above criteria) - and its accompanyin=
g<br>
Position ballot, with their personal review.<br>
<br>
My concern is that by conflating their IESG position with their<br>
personal review, the document process is inappropriately delayed and<br>
that documents are modified to appease a small community that does not<br>
justify its position as representative.<br>
How do others feel about this?<br>
<br>
Joe<br>
</blockquote></div><br></div>
</div></div></blockquote></div><div class=3D"gmail_extra"><br></div></div>

--047d7b67422033e72b04da2f55cf--

From sm@resistor.net  Fri Apr 12 13:05:53 2013
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 430C321F8E91 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:05:53 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOFfENyY3Qkv for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:05:52 -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 82EA321F8E6E for <ietf@ietf.org>; Fri, 12 Apr 2013 13:05:52 -0700 (PDT)
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 r3CK5hZJ028410; Fri, 12 Apr 2013 13:05:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365797151; bh=nAe5K8IrpWXMscAqD9Cq5N31n6pLJYlqLPHd0Vfy8Jo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=DhjnWh2I9pJgoFe4W4vhr7vOgXNa+20TvQp3FpySf0saKas5M38aGwgocQ5Inmczx O6SadEJfBE4W/jhpgIi8r83qpeeaBpwSF9TxmSdxW+okr18lgEovctQZCt8srVen83 M3v2BFt97O4hAAIkA6EXhxetLImQpP5JL3t9CToQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365797151; i=@resistor.net; bh=nAe5K8IrpWXMscAqD9Cq5N31n6pLJYlqLPHd0Vfy8Jo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rhvAlWStmLNgYNYwEXS35nf9Ki/04dkt3JwewPBbtxk6OAkzSx6JR2yPbLxcR9tPK Lv3ROC7Ke7Nxp31NkGBv1b/AkSzZK1LPGTHVsfHSD2/k65uXfXr9AKDajo1vAD0grM Yni3P5t18PlRVNO7YggB8nsFI2cAx7GzEkanZ4FE=
Message-Id: <6.2.5.6.2.20130412074639.0ae536b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 12 Apr 2013 13:01:00 -0700
To: Spencer Dawkins <spencer@wonderhamster.org>
From: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <51681C7C.7050408@wonderhamster.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <6.2.5.6.2.20130411140916.0c412c70@resistor.net> <51681C7C.7050408@wonderhamster.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Apr 2013 20:05:53 -0000

Hi Spencer,
At 07:38 12-04-2013, Spencer Dawkins wrote:
>I was just checking the math.

I understand. :-)

>I couldn't possibly say what "good" means, and I'm interested in 
>better understanding what "diverse" means, to this, ummm, at least 
>somewhat diverse community ...

There is an underlying uneasiness.  It has probably been there for a 
while.  Five women went to the microphone to openly raise an 
issue.  Some individuals from the IETF community  understood that the 
issue would not go away.  The word "diverse" is currently used as a 
placeholder for the issue.  I asked [1] the IETF Administrative 
Oversight Committee (IAOC) what their definition of "diversity" is 
as, as good engineers, the IAOC [2] would like to measure it.

Hannes Tschofenig once said that "nowadays everyone claims to be open 
and transparent" [3].  What was visible at a plenary was that there 
was one woman within a group of men facing a larger group in which 
there are only a few women.  There was also something else which was 
visible.  My guess is that it is a case of what I say and what I do 
are two different things.

Douglas Otis mentioned that "outcomes, good or bad, are often 
influenced by groups sharing a common interest.  Important questions 
should attempt to measure whether these interests reflect those of 
the larger Internet communities" [4].

Let's take IAOC members as an example.  NomCom chose two men from the 
United States.  The IAB chose a man from the United States.  The IESG 
chose a man from the United States.  The ISOC Board of Trustees chose 
a man from the United States.  There is a chart of IETF attendance by 
regions for the last seven meetings.  There isn't any publicly 
available information about attendance by men and women.  It's going 
to be difficult to argue that the IAOC reflects the interests of the 
IETF community unless a very large number of participants are men 
from the United States.

There hasn't been a woman on the IESG since 2009.  The last time 
there were two women on the IESG was in 2005.  There has been one or 
two women on the IAB over the years.

>p.s. And I wasn't trying to be snarky about the math. I blew the 
>percentages in the first draft of my response, so I know it happens 
>to the best of us :-)

Don't worry about that, I did not read it as snarky or anything negative. :-)

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg78592.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg78551.html
3. http://www.ietf.org/mail-archive/web/ietf/current/msg62409.html
4. http://www.ietf.org/mail-archive/web/ietf/current/msg78603.html 


From ajs@anvilwalrusden.com  Fri Apr 12 13:17:37 2013
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 466C321F8470 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:17:37 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99xucw8RwHsA for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:17:36 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id D09DF21F843E for <ietf@ietf.org>; Fri, 12 Apr 2013 13:17:36 -0700 (PDT)
Received: from mx1.yitter.info (li440-116.members.linode.com [50.116.54.116]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 04A208A031 for <ietf@ietf.org>; Fri, 12 Apr 2013 20:17:35 +0000 (UTC)
Date: Fri, 12 Apr 2013 16:17:32 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130412201732.GI3876@mx1.yitter.info>
References: <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51685369.4000306@gmail.com>
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: Fri, 12 Apr 2013 20:17:37 -0000

On Fri, Apr 12, 2013 at 10:33:13AM -0800, Melinda Shore wrote:

> address.  As I said I think that looking at the pool of
> nominees who've accepted their nominations and comparing
> it to the pool of people selected would provide one
> very rough measure of bias (explicit or otherwise) in
> one stage of the process.

Speaking only personally, but as one of the fat middle-aged white men
from North America whose mother tongue is English, and as someone who
was selected by the Nomcom for something this year, I strongly support
the above.  It would not be a result to give us anything remotely like
hard data, but it would be a result that could suggest further
inquiry.  And it oughta be cheap to generate.  As long as we use it
carefully, such a result could be useful.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From arturo.servin@gmail.com  Fri Apr 12 13:22:37 2013
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 E11EB21F8650 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:22:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.686
X-Spam-Level: 
X-Spam-Status: No, score=-1.686 tagged_above=-999 required=5 tests=[AWL=-0.638, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCZ8ikwraM1U for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:22:37 -0700 (PDT)
Received: from mail-gg0-x235.google.com (mail-gg0-x235.google.com [IPv6:2607:f8b0:4002:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 4130B21F8648 for <ietf@ietf.org>; Fri, 12 Apr 2013 13:22:37 -0700 (PDT)
Received: by mail-gg0-f181.google.com with SMTP id l4so482305ggi.40 for <ietf@ietf.org>; Fri, 12 Apr 2013 13:22:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Av+y93F+90mg3NGDptk1uuD4Cch+6/OmkA+JZJbUhZ4=; b=DZA8W4ZVhaWjq6bSlO8112RJdamw+RCqLOdBSKx5bEYHdhcGDjG6oTZCtCPmvdYVB/ jgZJGPWcC3JNxls4p7yt0OHXyKoDRhA4hU6xkboYNkuCffWKsxuM1tWRfC618hOkVlR5 0PEtyNyYUmDRsqQSD+dJOdxmqxGxIh7qFpQ/X9KyEH5ngDgEZRUV9ww+sI422HlNTbkr r6LpwM+HoXU/ZabkwlWcCAztijuuFF48dHYG5tP63EjmIvzNJylafDUJ2qe65iBlMxnM d7AyKiOEoiiuQoOeDiQ1e9+ysQlfcczJGEuLv4QYGQwMUbpS/LI3VbRFtgZ5QEPqrAB7 R2dQ==
X-Received: by 10.236.66.10 with SMTP id g10mr7430064yhd.206.1365798155882; Fri, 12 Apr 2013 13:22:35 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([200.7.87.33]) by mx.google.com with ESMTPS id t9sm13830665yhh.0.2013.04.12.13.22.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 13:22:34 -0700 (PDT)
Message-ID: <51686D07.7040804@gmail.com>
Date: Fri, 12 Apr 2013 17:22:31 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <51686076.3010508@gmail.com> <5168615A.1030907@gmail.com>
In-Reply-To: <5168615A.1030907@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: Fri, 12 Apr 2013 20:22:38 -0000

On 4/12/13 4:32 PM, Melinda Shore wrote:
> On 4/12/2013 11:28 AM, Arturo Servin wrote:
>> 	But if a single individual of the IESG can technically challenge and
>> change the work of a whole WG and the IETF, then we have something wrong
>> in our process because that means that the document had a serious
>> problem and we didn't spot it in the process or an IESG member is using
>> its power to change a document according to its personal beliefs.
> 
> We've had that happen in a working group I chair and I do
> think that it was the result of process failure in the
> working group.  That said, there seemed to be broad
> agreement across the IESG that the document had certain
> specific flaws 

	I think that exemplifies well what the IESG should do.

- I do think there's a problem if a single
> IESG member can reject working group consensus and hold
> up a document - it seems as if there should be wider
> agreement that the document is too flawed to progress.
> 
> Melinda
> 
	Yes.

	
Best wishes,
as

From arturo.servin@gmail.com  Fri Apr 12 13:34:46 2013
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 ED95A21F8E87 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:34:46 -0700 (PDT)
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.150,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QYyEpblBHBFO for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:34:46 -0700 (PDT)
Received: from mail-gg0-x233.google.com (mail-gg0-x233.google.com [IPv6:2607:f8b0:4002:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 0794D21F8E7E for <ietf@ietf.org>; Fri, 12 Apr 2013 13:34:45 -0700 (PDT)
Received: by mail-gg0-f179.google.com with SMTP id i2so483370ggm.24 for <ietf@ietf.org>; Fri, 12 Apr 2013 13:34:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=c4FlOjOLsT2LeZ8/A3GjsVfmezdDneeT7OpeHJ4mSl8=; b=GG3D5KmZmWAm686R2wncwhnevsKmEIsobIsYX0m7gvD9aBKnL1zFWSxFYdlZy00ma2 2kLC0Tq9zfM/Pb5wql7mMxj4Df1TpUu/Q7cauK3Ab8wMLJXkvkn5hN2yfZA5qhGDUaxy xnUP+CqrnX9HQFywzG1950QsWgwpiPsoMcYjWy85hpVrEHA+ngtgeOJ1OQIuHqU8lqA8 SJ0y4blsFMSvejtKpGpNy3nQJ5wdPsRYnfg8A5wwFB1PtC31mLyXGktmT69vvJzepOrx 2Z/EUpNrOuTazsaer0/8PpDZSZ/yFNRah+ycwXcjjng7kVSftwST6keqEgIgaZ8XIyY3 rWwg==
X-Received: by 10.236.138.167 with SMTP id a27mr7611298yhj.116.1365798885596;  Fri, 12 Apr 2013 13:34:45 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:3906:b16b:a2de:9407]) by mx.google.com with ESMTPS id u33sm13855150yhn.7.2013.04.12.13.34.43 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 13:34:44 -0700 (PDT)
Message-ID: <51686FE0.8000201@gmail.com>
Date: Fri, 12 Apr 2013 17:34:40 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com>
In-Reply-To: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com>
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, 12 Apr 2013 20:34:47 -0000

On 4/12/13 4:58 PM, Abdussalam Baryun wrote:
> I just change the subject because I still beleive the problem with
> review is in the WG not IESG. Some WGs have few reviews on each WG
> document, that may not be bad, but I think having only one review or
> comment (excluding authors) within a WGLC is wrong in a WG review
> process. I think WG chair can find two participants to do it.

	It seems plausible.

>  
> I recommend WG's process to change their purpose so we have to get *two
> participants* which are not authors to review the work and comment
> within WGLC (even small text comment is ok). I recommend WG chairs to
> think about this proposal, if not then I will try write an I-D for this
> and communicate with community.

	Possible we would need any how an I+D to change the process and mandate
this new review.

	I haven't made my mind but it seems like a good idea.

>  
> AB

Regards
as

From jmpolk@cisco.com  Fri Apr 12 13:37:04 2013
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 D19B321F8F1E for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:37:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6zUkbhYOZEw for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:37:04 -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 4546321F8F1C for <ietf@ietf.org>; Fri, 12 Apr 2013 13:37:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2283; q=dns/txt; s=iport; t=1365799024; x=1367008624; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=fH9H4xspBpd9vtf0+niovyW8KGcBiVnLlasnSv//xJE=; b=VcIReTrrlXn30gMc2h6ntmnC2s4+xJvryDcwmmbrS/6P21GiFstrGIEw V18QxE4fRltqzNw/Omm+Uspd2AL9PRxIpBXV203ZqdWlruV83JpLbJ/ke EJv2eLBySnYuhD/MfTwOb+GPYK3Buln9+BM9zeIRsOR8czS/slyFV4Je7 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAAJvaFGtJV2Z/2dsb2JhbABQgwbCGYENFnSCHwEBAQQ4Aj8QBwQYCRUQDwo+BgGIJrx+jWeBMAeDQQOJA58QgykegS8
X-IronPort-AV: E=Sophos;i="4.87,465,1363132800"; d="scan'208";a="198241618"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP; 12 Apr 2013 20:37:03 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r3CKb3IM013046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Apr 2013 20:37:03 GMT
Message-Id: <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 12 Apr 2013 15:37:03 -0500
To: Melinda Shore <melinda.shore@gmail.com>, Lou Berger <lberger@labn.net>
From: James Polk <jmpolk@cisco.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <51685C64.3010803@gmail.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
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, 12 Apr 2013 20:37:04 -0000

At 02:11 PM 4/12/2013, Melinda Shore wrote:
>And I don't know if you intended to or not, but what you
>communicated is "The best candidates are nearly always
>western white guys," since that's who's being selected.
>That's a problematic suggestion.

I respect you, Melinda. I think you are smarter and more technically 
and philosophically qualified than me.

Having said that, what Lou asked was an honest question, yet you 
seemed to take it in the worst possible way. I'd say each of us is 
likely bringing our own baggage to how we each look at this 
'problem', if there is a problem at all (which doesn't appear to be 
universally agreed upon).

"since that's who's being selected" is a biased observation in and of 
itself. That's saying that because of the outcome, there "has to be 
bias" to skew the results this way - because it's the only logical 
explanation that could answer these results. My BS-meter is pegging 
into the red on that one.

The nomcom isn't randomly picking hats in a crowd. They are picking 
talent of those that have volunteered to serve. At any given time 
there could be 1 or 2 or 5 women how volunteered to server at 
particular AD slot, but there might be 1 "white guy" that is more 
qualified. From the audience at any plenary - that could appear "the 
fix is in" to ace out the women, but clearly (in this hypothetical 
example) it's not the case at all.

Eyeballing the IETF (and I've missed 2 meetings since IETF45, been a 
WG chair for 8 years, and written or revised over 300 submitted IDs) 
there is consistently about a 70-to-1 ratio of men to women.

I'd observe that this is likely the case of hurt feelings rather than 
unqualified males achieving the AD position in lieu of more qualified 
females - especially in the face of these rough ratio approximations.

I believe "we" need to reduce that ratio, and am for anything that 
increases the number of (qualified) women in this engineering 
organization. I am against artificially forcing the nomcom to 
implement a quota system to overcome low participation numbers of any 
diversity aspect.

Admittedly, I'm only teasing out the male/female diversity facet, and 
not any other the other - equally deserving diversity criteria.

James


From daedulus@btconnect.com  Fri Apr 12 13:57:56 2013
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 921D321F8528 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:57:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJPYYB1xsoND for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 13:57:53 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 95BBD21F8526 for <ietf@ietf.org>; Fri, 12 Apr 2013 13:57:53 -0700 (PDT)
Received: from mail82-va3-R.bigfish.com (10.7.14.234) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.23; Fri, 12 Apr 2013 20:57:52 +0000
Received: from mail82-va3 (localhost [127.0.0.1])	by mail82-va3-R.bigfish.com (Postfix) with ESMTP id 3D6E41A0360; Fri, 12 Apr 2013 20:57:52 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: PS-26(zzbb2dI98dI9371I542I1432I1db9Mzz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah304l1155h)
Received: from mail82-va3 (localhost.localdomain [127.0.0.1]) by mail82-va3 (MessageSwitch) id 1365800228993962_15239; Fri, 12 Apr 2013 20:57:08 +0000 (UTC)
Received: from VA3EHSMHS021.bigfish.com (unknown [10.7.14.247])	by mail82-va3.bigfish.com (Postfix) with ESMTP id E55273202A6; Fri, 12 Apr 2013 20:57:08 +0000 (UTC)
Received: from DB3PRD0710HT002.eurprd07.prod.outlook.com (157.56.253.85) by VA3EHSMHS021.bigfish.com (10.7.99.31) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 12 Apr 2013 20:57:08 +0000
Received: from DBXPRD0611HT001.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.75.37) with Microsoft SMTP Server (TLS) id 14.16.293.5; Fri, 12 Apr 2013 20:57:06 +0000
Message-ID: <006e01ce37bf$a45c0ba0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Arturo Servin <arturo.servin@gmail.com>, <ietf@ietf.org>
References: <5166F8BD.7010308@isi.edu> <51686076.3010508@gmail.com>
Subject: Re: Purpose of IESG Review
Date: Fri, 12 Apr 2013 21:52:20 +0100
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.254.85]
X-FOPE-CRA-SourceIpAddress: 157.56.253.85
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: arturo.servin@gmail.com
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, 12 Apr 2013 20:57:56 -0000

----- Original Message -----
From: "Arturo Servin" <arturo.servin@gmail.com>
To: <ietf@ietf.org>
Sent: Friday, April 12, 2013 8:28 PM
>
> Not answering any particular post. Just a comment.
>
> The IESG should be there to attest that the IETF procedure was
followed
> and the document reached consensus in the WG and in the IETF LC and it
> was successfully reviewed by the Gen-ART. If it wasn't then this
> particular process should be reviewed and take actions accordingly
(e.g.
> returning the document to the wg).
>
> But if a single individual of the IESG can technically challenge and
> change the work of a whole WG and the IETF, then we have something
wrong
> in our process because that means that the document had a serious
> problem and we didn't spot it in the process or an IESG member is
using
> its power to change a document according to its personal beliefs.

My experience has been the former, where the IESG has raised concerns
about arcane topics, such as security and congestion, of which the WG
had limited expertise.  This might be caught by a directorate review,
but those seem patchy; it might be caught by IETF Last Call, but if you
are an expert at an arcane topic then you are probably too busy to
follow them.

So I do see the IESG DISCUSSing, when it would have been lovely to have
had, but it is hard to see quite how, it resolved earlier.  We just do
not have the breadth of knowledge of arcane topics.

Tom Petch

> Just a thought,
> as
>
> On 4/11/13 2:54 PM, Joe Touch wrote:
> > Hi, all,
> >
> > As an author who has had (and has) multiple documents in IESG
review,
> > I've noticed an increasing trend of this step to go beyond (IMO) its
> > documented and original intent (BCP 9, currently RFC 2026):
> >
> >    The IESG shall determine whether or not a specification submitted
to
> >    it according to section 6.1.1 satisfies the applicable criteria
for
> >    the recommended action (see sections 4.1 and 4.2), and shall in
> >    addition determine whether or not the technical quality and
clarity
> >    of the specification is consistent with that expected for the
> >    maturity level to which the specification is recommended.
> >
> > Although I appreciate that IESG members are often overloaded, and
the
> > IESG Review step is often the first time many see these documents, I
> > believe they should be expected to more clearly differentiate their
> > "IESG Review" (based on the above criteria) - and its accompanying
> > Position ballot, with their personal review.
> >
> > My concern is that by conflating their IESG position with their
personal
> > review, the document process is inappropriately delayed and that
> > documents are modified to appease a small community that does not
> > justify its position as representative.
> >
> > How do others feel about this?
> >
> > Joe
>



From Ted.Lemon@nominum.com  Fri Apr 12 14:06:18 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0930B21F8F0D; Fri, 12 Apr 2013 14:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.366
X-Spam-Level: 
X-Spam-Status: No, score=-106.366 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HlJ2DyR7EIck; Fri, 12 Apr 2013 14:06:17 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 425B821F8E94; Fri, 12 Apr 2013 14:06:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUWh3Sfj24SZFkLeUellJv32JL92or6gH@postini.com; Fri, 12 Apr 2013 14:06:17 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E3D611B80C1; Fri, 12 Apr 2013 14:06:16 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id DA62F190061; Fri, 12 Apr 2013 14:06:16 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 12 Apr 2013 14:06:16 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbesxw5RhqwwUuIKG4LfyrlCZjR4Y8AgAAKbwCAAAcIAIAAl7OAgACT+QCAAFoBAIAAEjuA
Date: Fri, 12 Apr 2013 21:06:16 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775143E80@mbx-01.win.nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <6.2.5.6.2.20130411140916.0c412c70@resistor.net> <51681C7C.7050408@wonderhamster.org> <6.2.5.6.2.20130412074639.0ae536b0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130412074639.0ae536b0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1131BAF5B0D85E4389934153E41518AA@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iaoc@ietf.org" <iaoc@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, 12 Apr 2013 21:06:18 -0000

On Apr 12, 2013, at 4:01 PM, SM <sm@resistor.net> wrote:
> Let's take IAOC members as an example.  NomCom chose two men from the Uni=
ted States.  The IAB chose a man from the United States.  The IESG chose a =
man from the United States.  The ISOC Board of Trustees chose a man from th=
e United States.  There is a chart of IETF attendance by regions for the la=
st seven meetings.  There isn't any publicly available information about at=
tendance by men and women.  It's going to be difficult to argue that the IA=
OC reflects the interests of the IETF community unless a very large number =
of participants are men from the United States.

I'd like to take slight exception to one thing that this paragraph implies:=
 that only a person who looks like me and comes from the same region can re=
present my interests.   I realize that given that I happen to be a white ma=
le from the United States, the world's smallest violin is playing somewhat =
unenthusiastically on my behalf at the moment.  But in fact I would object =
quite strongly to another white male from the United States representing me=
 rather than a non-white, non-male not from the United States with whom I s=
hared more views in common.   And this is not a matter of purely academic i=
nterest: there are many white males from the United States whose views I fi=
nd vary across the range from puzzling to upsetting.

So in fact you don't need to put some percentage of white males on the IESG=
, the IAB or the IAOC to make me happy.   I want people on these bodies who=
 feel strongly about open standards, rough consensus and running code.   Th=
at's the kool-aid I have drunk, and I want them to have drunk it too.


From lberger@labn.net  Fri Apr 12 14:27:07 2013
Return-Path: <lberger@labn.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 1288321F8C55 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 14:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.301
X-Spam-Level: 
X-Spam-Status: No, score=-102.301 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F63RkQMRsD7j for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 14:27:04 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id CE58F21F8A3F for <ietf@ietf.org>; Fri, 12 Apr 2013 14:27:04 -0700 (PDT)
Received: (qmail 8106 invoked by uid 0); 12 Apr 2013 21:26:41 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 12 Apr 2013 21:26:41 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=IofUGfDbyxKgP9OJrCWBCqbE9N3R/6OaTXMXNhUvDiI=;  b=ootIjGuXvTlsxvw70VNnzqHPERD0FvCbS//jGJAn+6OwTJMkrcy/Log6UITFru/j35JABE5iYGspSC6ALRA6gpBXjDHMJkaH0l/+44cvFa9QrzLL4r2yG1aEscauGS+G;
Received: from box313.bluehost.com ([69.89.31.113]:41128 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1UQlUW-0005H9-Sx; Fri, 12 Apr 2013 15:26:41 -0600
Message-ID: <51687C0D.8090804@labn.net>
Date: Fri, 12 Apr 2013 17:26:37 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com>
In-Reply-To: <51685C64.3010803@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.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, 12 Apr 2013 21:27:07 -0000

Melinda,

On 4/12/2013 3:11 PM, Melinda Shore wrote:
> On 4/12/2013 11:04 AM, Lou Berger wrote:
>> While I've been very reluctant to jump on this topic, I have to ask
>> what's the basis for this assertion? 
> 
> I think the numbers are pretty compelling, which is why
> I think they would deserve scrutiny if there's the
> possibility of remediation if a problem is identified.
>
> However, it's pretty clear from the tone of the discussion
> so far that no remediation would be possible, and so I
> actually think it's probably a bad idea to attack the
> question.  


> That does not mean, however, that the question
> does not exist.

No argument from me, I'm just asking that a comment/position/question
that I don't understand be substantiated.  I'm not sure if you missed my
point that you cut from my mail:

> A willingness to do/volunteer for a job says nothing about one's
> qualifications for a job.

I guess from your response that you disagree with the statement (which I
thought was pretty noncontroversial).

> And I don't know if you intended to or not, but what you
> communicated is "The best candidates are nearly always
> western white guys," since that's who's being selected.
> That's a problematic suggestion.

I certainly, in no way, shape, or form intended such an implication.  I
have not idea how one could read it that way, but clearly we all have
our own biases that lead to what we imply and infer.

You may have also missed that I suggested that it would be interesting
to get a better understanding of the issue by comparing 'qualified'
nominees vs selected.  I just don't have any idea how to ascertain this
number. We could ask the nomcom folks for such statistics but, of
course, one would need to (a) trust the nomcom -- and I'm not implying
that any do not, and (b) ensure that the information could not be
related back to any particular nominee -- which I think is an issue that
makes this thought and question impractical given the size of the sample
pool.

Lou

> 
> Melinda
> 

From arturo.servin@gmail.com  Fri Apr 12 14:32:43 2013
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 CB74C21F855C for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 14:32:43 -0700 (PDT)
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.100, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rUc6XYac3TUl for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 14:32:43 -0700 (PDT)
Received: from mail-yh0-x22c.google.com (mail-yh0-x22c.google.com [IPv6:2607:f8b0:4002:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 0244521F842A for <ietf@ietf.org>; Fri, 12 Apr 2013 14:32:42 -0700 (PDT)
Received: by mail-yh0-f44.google.com with SMTP id m1so508683yhg.17 for <ietf@ietf.org>; Fri, 12 Apr 2013 14:32:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=kVkuK2MZx2JNOsgqUSnhJuG71TPkoTuP9l9lkYdngy8=; b=GGkxTM+b6iQpsBNj9J/pW8xI1jBmyZwXxTfvuhi57uItNBnrTVIyIF3BYqVthlAGmZ OhNqsoV7B3roetvGBvKCvrdMZbCESBdDmHsDAYTM+HBPTYBkeL0QzpdjKr0/Fl5FoqyY ZNbuNhAKBld0IdyKCoEcNc0X/4n6zWtek8ueMU0+SqDHObNaIXJBcXu+gXT0L6oHfD+d IFU/OkwOjR3Fg7nSoXy1+N1TsykROA3gpQRWYO+39efiVRPtT6mGjkjJaDgPjH/OwwBu inRKIKrOE4rqsIOQ/ZO4fSeqvAUM0krksxeNy60Kk8gOwpaox9opJDSPJwrvFFvU5qWU Vqwg==
X-Received: by 10.236.74.201 with SMTP id x49mr7819900yhd.80.1365802362539; Fri, 12 Apr 2013 14:32:42 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba31:194:7406:990e:1d23:d776]) by mx.google.com with ESMTPS id s10sm14126754yho.13.2013.04.12.14.32.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 14:32:41 -0700 (PDT)
Message-ID: <51687D74.3050202@gmail.com>
Date: Fri, 12 Apr 2013 18:32:36 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <51686076.3010508@gmail.com> <006e01ce37bf$a45c0ba0$4001a8c0@gateway.2wire.net>
In-Reply-To: <006e01ce37bf$a45c0ba0$4001a8c0@gateway.2wire.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: Fri, 12 Apr 2013 21:32:43 -0000

On 4/12/13 5:52 PM, t.p. wrote:
> ----- Original Message -----
> From: "Arturo Servin" <arturo.servin@gmail.com>
> To: <ietf@ietf.org>
> Sent: Friday, April 12, 2013 8:28 PM
>>
>> Not answering any particular post. Just a comment.
>>
>> The IESG should be there to attest that the IETF procedure was
> followed
>> and the document reached consensus in the WG and in the IETF LC and it
>> was successfully reviewed by the Gen-ART. If it wasn't then this
>> particular process should be reviewed and take actions accordingly
> (e.g.
>> returning the document to the wg).
>>
>> But if a single individual of the IESG can technically challenge and
>> change the work of a whole WG and the IETF, then we have something
> wrong
>> in our process because that means that the document had a serious
>> problem and we didn't spot it in the process or an IESG member is
> using
>> its power to change a document according to its personal beliefs.
> 
> My experience has been the former, where the IESG has raised concerns
> about arcane topics, such as security and congestion, of which the WG
> had limited expertise.  This might be caught by a directorate review,
> but those seem patchy; it might be caught by IETF Last Call, but if you
> are an expert at an arcane topic then you are probably too busy to
> follow them.
> 
> So I do see the IESG DISCUSSing, when it would have been lovely to have
> had, but it is hard to see quite how, it resolved earlier.  We just do
> not have the breadth of knowledge of arcane topics.


	Perhaps we need an "arcane topic reviewer" before the LC.

	
.as

> 
> Tom Petch
> 
>> Just a thought,
>> as
>>
>> On 4/11/13 2:54 PM, Joe Touch wrote:
>>> Hi, all,
>>>
>>> As an author who has had (and has) multiple documents in IESG
> review,
>>> I've noticed an increasing trend of this step to go beyond (IMO) its
>>> documented and original intent (BCP 9, currently RFC 2026):
>>>
>>>    The IESG shall determine whether or not a specification submitted
> to
>>>    it according to section 6.1.1 satisfies the applicable criteria
> for
>>>    the recommended action (see sections 4.1 and 4.2), and shall in
>>>    addition determine whether or not the technical quality and
> clarity
>>>    of the specification is consistent with that expected for the
>>>    maturity level to which the specification is recommended.
>>>
>>> Although I appreciate that IESG members are often overloaded, and
> the
>>> IESG Review step is often the first time many see these documents, I
>>> believe they should be expected to more clearly differentiate their
>>> "IESG Review" (based on the above criteria) - and its accompanying
>>> Position ballot, with their personal review.
>>>
>>> My concern is that by conflating their IESG position with their
> personal
>>> review, the document process is inappropriately delayed and that
>>> documents are modified to appease a small community that does not
>>> justify its position as representative.
>>>
>>> How do others feel about this?
>>>
>>> Joe
>>
> 

From john-ietf@jck.com  Fri Apr 12 15:19:10 2013
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 F250F21F8D28 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 15:19:09 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFy1znIOav2y for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 15:19:09 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6CFAC21F8C98 for <ietf@ietf.org>; Fri, 12 Apr 2013 15:19:09 -0700 (PDT)
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 1UQmJI-000CdN-OW; Fri, 12 Apr 2013 18:19:08 -0400
Date: Fri, 12 Apr 2013 18:18:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Subject: Re: Purpose of IESG Review
Message-ID: <DC0F69276BCB2F0B5758CFC3@JcK-HP8200.jck.com>
In-Reply-To: <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.com>
References: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com> <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.c om>
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, 12 Apr 2013 22:19:10 -0000

--On Friday, April 12, 2013 20:24 +0100 Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:

> How can a memebr of staff in a company argue with the manager
> about the manager's decisions or performance?

In most successful companies, yes.  

> Only
> Owners/shareholders can question managers and staff.

And companies that behave that way don't last very long in
rapidly evolving fields... at least unless the managers are
endowed with perfect wisdom.  It is not an accident that most
management schools teach would-be managers that listening
--especially to the people on  the front lines-- is a very
important skill.

So, at the risk of generalizing too much... What on earth are
you talking about and what experience do you have and use to
justify it?

    john


From mcr@sandelman.ca  Fri Apr 12 16:13:30 2013
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 2DCD721F8A52 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 16:13:30 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-HDsrupLBDW for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 16:13:29 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 424BD21F884F for <ietf@ietf.org>; Fri, 12 Apr 2013 16:13:29 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 37B372016D for <ietf@ietf.org>; Fri, 12 Apr 2013 19:23:10 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id AF0F7638F7; Fri, 12 Apr 2013 19:13:01 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A2507638E8 for <ietf@ietf.org>; Fri, 12 Apr 2013 19:13:01 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 12 Apr 2013 19:13:01 -0400
Message-ID: <3950.1365808381@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: Fri, 12 Apr 2013 23:13:30 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "James" =3D=3D James Polk <jmpolk@cisco.com> writes:
    James> The nomcom isn't randomly picking hats in a crowd. They are
    James> picking talent of those that have volunteered to serve. At

Volunteered, and who have employer/funding support.

The apparent bias that we are experiencing is the result of 30+ years of
high-tech employment bias towards the white male.  To be a qualified
candidate requires a bunch of things:
(and I mean "qualified" in both the qualities of the person, and the=20
 various supports needed to do the job)

1) working for a moderate to large company for a sufficiently long time
   such that the company can spare the salary.
   (Or being sufficiently well connected that the person can find sponsorsh=
ip)

2) being able to travel for a week+ at a time.

3) having been able to do (2) for enough years to have met enough people
   that the person's qualifications have been recognized.

and of course:
4) doing actual technical work!

that's some serious hurdles.  There a bias here towards older people who
have been in the same company for a long time, and who either have no
children, or had them at least ten years ago.=20=20

Having a child (and I didn't do the hard work), restricted my ability to
travel sufficiently that I wasn't nomcom eligible for 5 years....=20

True, we have had people overcome hurdles: at least one IESG baby is
expected this year, and we didn't even have a parental leave policy
until Lisa wrote one.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09


--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUWiU/YqHRg3pndX9AQJH5AP8DtA4FpVU1Akbnt3mLxOiqfrnkP0cX8Ni
TcO+7zZdRNeunSS255Gp7PcwcVyXFigu4++5vLElUmVTpb+AyrXwX2Fgaba0lwlx
K2RiKOLQAx4Vcozrmpc5y4qLqRitpZrTV/1jvpav3dOAxcZgp1B1MEXeqzhnNAVe
OVORp25Wtdw=
=kJ1d
-----END PGP SIGNATURE-----
--=-=-=--

From sm@resistor.net  Fri Apr 12 16:41:18 2013
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 0C0BD21F8F0D; Fri, 12 Apr 2013 16:41:18 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A+78w-ii0wK6; Fri, 12 Apr 2013 16:41:17 -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 62BEB21F8EFC; Fri, 12 Apr 2013 16:41:17 -0700 (PDT)
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 r3CNfBPT024012; Fri, 12 Apr 2013 16:41:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365810076; bh=MaugU+kDIUUKBLfmga8AQD7kYvb7EFFlF7llpeHkaPo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=I1AwvKnhUQZkgbu9I0UsuZuc1mCA3cuWKUgTbx/huBmZ4CTjrAJYbR01VeTt/Idi7 dmVkinqi/WUi6qvt26srkHDnNC3oF7PTKc3SbwUCWTTnb/Kz55N/nUplHhf9jp3TxV +N5o5RfNSnPThL42RzirZ5ZdjFHhQii5U0gXmpKw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365810076; i=@resistor.net; bh=MaugU+kDIUUKBLfmga8AQD7kYvb7EFFlF7llpeHkaPo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=oYv/vlLmYRF+4QIfHlz6W5ky5G6o076XSzfxRzPxmgiP8KsCQnEiGf0aOeoMVOhhf gVtxmDQBdJhzgjyy01AsCf3qxpZlyiesWglQh0B5Pk96KSvNDr/99aIoYcDqhuFH30 zpgKV9kAjXLXE3b77yKaTkBR6Yf514LhWhKCeFDE=
Message-Id: <6.2.5.6.2.20130412150127.0d2db9d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 12 Apr 2013 16:32:51 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>
From: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775143E80@mbx-01.win.nominu m.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <6.2.5.6.2.20130411140916.0c412c70@resistor.net> <51681C7C.7050408@wonderhamster.org> <6.2.5.6.2.20130412074639.0ae536b0@resistor.net> <8D23D4052ABE7A4490E77B1A012B630775143E80@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iaoc@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, 12 Apr 2013 23:41:18 -0000

Hi Ted,
At 14:06 12-04-2013, Ted Lemon wrote:
>I'd like to take slight exception to one thing that this paragraph 
>implies: that only a person who looks like me and comes from the 
>same region can represent my interests.   I

Let's see how many IETF participants (I'll exclude voting members of 
I* bodies if you are ok with that) share the view mentioned above.

I'll take the liberty of not expressing my view.

>So in fact you don't need to put some percentage of white males on 
>the IESG, the IAB or the IAOC to make me happy.   I want people on 
>these bodies who feel strongly about open standards, rough consensus 
>and running code.   That's the kool-aid I have drunk, and I

Thomas Narten mentioned that: "we have the tendency to pick the 
people we know and trust, which is understandable".  How many IAB 
members feel strongly about open standards, rough consensus and 
running code?  To know the answer I would have to actually know the 
IAB members.

Regards,
-sm 


From pthaler@broadcom.com  Fri Apr 12 16:51:01 2013
Return-Path: <pthaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E31D421F8F63 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 16:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.318
X-Spam-Level: 
X-Spam-Status: No, score=-6.318 tagged_above=-999 required=5 tests=[AWL=0.281,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F+6hOXkL1U-e for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 16:51:00 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 52B9521F8F5C for <ietf@ietf.org>; Fri, 12 Apr 2013 16:51:00 -0700 (PDT)
Received: from [10.9.208.53] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Fri, 12 Apr 2013 16:42:45 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS05.corp.ad.broadcom.com (10.16.203.12) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.1.438.0; Fri, 12 Apr 2013 16:50:44 -0700
Received: from SJEXCHMB09.corp.ad.broadcom.com ( [fe80::3da7:665e:cc78:181f]) by SJEXCHCAS05.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Fri, 12 Apr 2013 16:50:43 -0700
From: "Pat Thaler" <pthaler@broadcom.com>
To: "John C Klensin" <john-ietf@jck.com>, "Abdussalam Baryun" <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Subject: RE: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: AQHON2DHP1iO4QahakOXV5IFCl6485jTbTIAgAAw1YD//5oUQA==
Date: Fri, 12 Apr 2013 23:50:43 +0000
Message-ID: <EB9B93801780FD4CA165E0FBCB3C3E672AD2DF79@SJEXCHMB09.corp.ad.broadcom.com>
References: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com> <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.c om> <DC0F69276BCB2F0B5758CFC3@JcK-HP8200.jck.com>
In-Reply-To: <DC0F69276BCB2F0B5758CFC3@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7D76447F35W545320-01-01
Content-Type: text/plain; charset=us-ascii
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: Fri, 12 Apr 2013 23:51:01 -0000

+1 on for John's response.
=20
I will argue with my manager if I think they are wrong and I've gotten posi=
tive results from giving managers feedback on their performance. Of course,=
 disagreeing with management won't always get the decision changed, but I'v=
e never felt I lost anything by raising the discussion.

I've also seen some bad decisions made when someone had good reasons why a =
decision was wrong but didn't surface them because they didn't feel they co=
uld argue with management.

IETF participant to IETF leadership isn't the same as employee to manager o=
f course. We are all volunteers collaborating to get good results and if we=
 feel there is a process problem we can discuss it. IETF formalizes this by=
 having open mike sessions for example.=20

A thread on whether there is a problem with the IESG review process is appr=
opriate, IMO.

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Joh=
n C Klensin
Sent: Friday, April 12, 2013 3:19 PM
To: Abdussalam Baryun; ietf
Subject: Re: Purpose of IESG Review



--On Friday, April 12, 2013 20:24 +0100 Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:

> How can a memebr of staff in a company argue with the manager
> about the manager's decisions or performance?

In most successful companies, yes. =20

> Only
> Owners/shareholders can question managers and staff.

And companies that behave that way don't last very long in
rapidly evolving fields... at least unless the managers are
endowed with perfect wisdom.  It is not an accident that most
management schools teach would-be managers that listening
--especially to the people on  the front lines-- is a very
important skill.

So, at the risk of generalizing too much... What on earth are
you talking about and what experience do you have and use to
justify it?

    john




From mrex@sap.com  Fri Apr 12 16:55:45 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2568621F8F70; Fri, 12 Apr 2013 16:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h9nDMMna4zlm; Fri, 12 Apr 2013 16:55:44 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 04C2321F8F5C; Fri, 12 Apr 2013 16:55:43 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r3CNtgkc023011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 13 Apr 2013 01:55:42 +0200 (MEST)
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <6.2.5.6.2.20130412150127.0d2db9d0@resistor.net>
To: SM <sm@resistor.net>
Date: Sat, 13 Apr 2013 01:55:42 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130412235542.8CEDA1A6AD@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: Fri, 12 Apr 2013 23:55:45 -0000

SM wrote:
> 
> Ted Lemon wrote:
> > 
> >So in fact you don't need to put some percentage of white males on 
> >the IESG, the IAB or the IAOC to make me happy.   I want people on 
> >these bodies who feel strongly about open standards, rough consensus 
> >and running code.   That's the kool-aid I have drunk, and I

Me 2!

> 
> Thomas Narten mentioned that: "we have the tendency to pick the 
> people we know and trust, which is understandable".  How many IAB 
> members feel strongly about open standards, rough consensus and 
> running code?  To know the answer I would have to actually know the 
> IAB members.

I believe there is a problem for human beings that with more "choice"
the "picks" may get worse, based on an evolutionary cognitive limit.

  http://en.wikipedia.org/wiki/Dunbar%27s_number
  http://www.cracked.com/article_14990_what-monkeysphere.html


-Martin

From Ted.Lemon@nominum.com  Fri Apr 12 18:51:36 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 098D321F8E8F; Fri, 12 Apr 2013 18:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.371
X-Spam-Level: 
X-Spam-Status: No, score=-106.371 tagged_above=-999 required=5 tests=[AWL=0.228, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p+qelr-xfVDn; Fri, 12 Apr 2013 18:51:35 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD9A21F8E7E; Fri, 12 Apr 2013 18:51:35 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUWi6JwMzLCcXm4+AlW6xwb+l+x8C5QI/@postini.com; Fri, 12 Apr 2013 18:51:35 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 02CAE1B80AB; Fri, 12 Apr 2013 18:51:35 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id ED90E190061; Fri, 12 Apr 2013 18:51:34 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 12 Apr 2013 18:51:34 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbesxw5RhqwwUuIKG4LfyrlCZjR4Y8AgAAKbwCAAAcIAIAAl7OAgACT+QCAAFoBAIAAEjuA//+1+piAAJnBgA==
Date: Sat, 13 Apr 2013 01:51:35 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775144439@mbx-01.win.nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <6.2.5.6.2.20130411140916.0c412c70@resistor.net> <51681C7C.7050408@wonderhamster.org> <6.2.5.6.2.20130412074639.0ae536b0@resistor.net> <8D23D4052ABE7A4490E77B1A012B630775143E80@mbx-01.win.nominum.com> <6.2.5.6.2.20130412150127.0d2db9d0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130412150127.0d2db9d0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A54EA876467794498C09D95420A7786D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<iaoc@ietf.org>" <iaoc@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, 13 Apr 2013 01:51:36 -0000

On Apr 12, 2013, at 7:32 PM, SM <sm@resistor.net> wrote:
> Thomas Narten mentioned that: "we have the tendency to pick the people we=
 know and trust, which is understandable".  How many IAB members feel stron=
gly about open standards, rough consensus and running code?  To know the an=
swer I would have to actually know the IAB members.

Are they really that hard to get to know?   A number of them are participat=
ing in this conversation. It's certainly hard to get time to sit with them =
at IETF meetings.   I don't know what the workload is like for IAB members,=
 but I think I worked at least an 80 hour week in Orlando.


From barryleiba.mailing.lists@gmail.com  Fri Apr 12 19:12:02 2013
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 0C3F721F8EB7; Fri, 12 Apr 2013 19:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.803
X-Spam-Level: 
X-Spam-Status: No, score=-102.803 tagged_above=-999 required=5 tests=[AWL=0.173, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E4eK5POKHzSj; Fri, 12 Apr 2013 19:12:01 -0700 (PDT)
Received: from mail-ve0-f179.google.com (mail-ve0-f179.google.com [209.85.128.179]) by ietfa.amsl.com (Postfix) with ESMTP id 24B0521F8EA5; Fri, 12 Apr 2013 19:12:00 -0700 (PDT)
Received: by mail-ve0-f179.google.com with SMTP id cz11so2876498veb.24 for <multiple recipients>; Fri, 12 Apr 2013 19:12:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=MgjJEl+0XF2xcWv/HrVvGSKSjZ5DApPrWxWNmRmvs+M=; b=rYgjhWm8IVfGdJ/149lvz/KtroLCivrc4yfmcPqmlWbv+Kmn1U8a844OngzgGVIoZX /4H/+U0mUrYALi4XfxRB4Tlvtz17j9Uq6PLHlXskqrkF3m4ktpaIMJSERRITQ8ghGBo0 MDhqvyjhWl6ZoNO9qHqOVcVBpe1RhU3AgKWLlEDCMJtneWI7YX+jYLOaPx/sr6VCoja9 zaDXsozNipbYSR525q3PRfCZwpURGOf/EDE54UIhyurQjSVp3fZSxF2aFld9jusWWYqf rgIubBNjB12shy3f0WJJ1z9EvBpUkLz/xR6R+JLrMd1g9rivviU61JWzwz+IjkrlawWM UUpg==
MIME-Version: 1.0
X-Received: by 10.59.3.9 with SMTP id bs9mr10361962ved.38.1365819120285; Fri, 12 Apr 2013 19:12:00 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Fri, 12 Apr 2013 19:12:00 -0700 (PDT)
In-Reply-To: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>
Date: Fri, 12 Apr 2013 22:12:00 -0400
X-Google-Sender-Auth: Fw8dIUzcku401r7QXK4PGwKWLjw
Message-ID: <CAC4RtVABudiEa_cqqr9OmcbUsAuWGXftisrjEATRLgNvJubXzw@mail.gmail.com>
Subject: Re: Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness of Running Code: the Implementation Status Section) to Experimental RFC
From: Barry Leiba <barryleiba@computer.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8f9219367dff6b04da348b41
Cc: 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: Sat, 13 Apr 2013 02:12:02 -0000

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

This dude's ready to ship.  Thanks for addressing my earlier comments.

Barry

On Friday, April 12, 2013, The IESG wrote:

>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Improving Awareness of Running Code: the Implementation Status
> Section'
>   <draft-sheffer-running-code-04.txt> as Experimental 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 <javascript:;> mailing lists by 2013-05-10. Exceptionally,
> comments may be
> sent to iesg@ietf.org <javascript:;> instead. In either case, please
> retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document describes a simple process that allows authors of
>    Internet-Drafts to record the status of known implementations by
>    including an Implementation Status section.  This will allow
>    reviewers and working groups to assign due consideration to documents
>    that have the benefit of running code, by considering the running
>    code as evidence of valuable experimentation and feedback that has
>    made the implemented protocols more mature.
>
>    The process in this document is offered as an experiment.  Authors of
>    Internet-Drafts are encouraged to consider using the process for
>    their documents, and working groups are invited to think about
>    applying the process to all of their protocol specifications.  The
>    authors of this document intend to collate experiences with this
>    experiment and to report them to the community.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-sheffer-running-code/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-sheffer-running-code/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

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

This dude&#39;s ready to ship. =A0Thanks for addressing my earlier comments=
.<span></span><div><br></div><div>Barry<br><br>On Friday, April 12, 2013, T=
he IESG  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The IESG has received a request from an individual submitter to consider<br=
>
the following document:<br>
- &#39;Improving Awareness of Running Code: the Implementation Status<br>
Section&#39;<br>
=A0 &lt;draft-sheffer-running-code-04.txt&gt; as Experimental RFC<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;ietf@iet=
f.org&#39;)">ietf@ietf.org</a>=A0mailing lists by 2013-05-10. Exceptionally=
, comments may be<br>
sent to <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;=
iesg@ietf.org&#39;)">iesg@ietf.org</a> instead. In either case, please reta=
in the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=A0 =A0This document describes a simple process that allows authors of<br>
=A0 =A0Internet-Drafts to record the status of known implementations by<br>
=A0 =A0including an Implementation Status section. =A0This will allow<br>
=A0 =A0reviewers and working groups to assign due consideration to document=
s<br>
=A0 =A0that have the benefit of running code, by considering the running<br=
>
=A0 =A0code as evidence of valuable experimentation and feedback that has<b=
r>
=A0 =A0made the implemented protocols more mature.<br>
<br>
=A0 =A0The process in this document is offered as an experiment. =A0Authors=
 of<br>
=A0 =A0Internet-Drafts are encouraged to consider using the process for<br>
=A0 =A0their documents, and working groups are invited to think about<br>
=A0 =A0applying the process to all of their protocol specifications. =A0The=
<br>
=A0 =A0authors of this document intend to collate experiences with this<br>
=A0 =A0experiment and to report them to the community.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-sheffer-running-code/" tar=
get=3D"_blank">http://datatracker.ietf.org/doc/draft-sheffer-running-code/<=
/a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-sheffer-running-code/ballo=
t/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-sheffer-running=
-code/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
</blockquote></div>

--e89a8f9219367dff6b04da348b41--

From melinda.shore@gmail.com  Fri Apr 12 19:22:26 2013
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 1744F21F8EF2 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 19:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rr+-I9KeDJDW for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 19:22:24 -0700 (PDT)
Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com [209.85.160.45]) by ietfa.amsl.com (Postfix) with ESMTP id 4444E21F8E72 for <ietf@ietf.org>; Fri, 12 Apr 2013 19:22:21 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id ro12so1708917pbb.4 for <ietf@ietf.org>; Fri, 12 Apr 2013 19:22:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=47VrUNc3gRhyLu/ozxomVEGVxdZwILbhOozlZtDa3m8=; b=drddo5dOi7pS4M49wG8XMgu+bp54yJ/ryhk1w1V49eLx8R5yRYjds1FCGmiX4VNQiM axXYK4HmkhO+UIeW3J+e2zpNASr0IsYazQrolKVcF/7CVceOK50AFLfqDlmhxqBFMGmC G/BCAkGhKCP8hs0hUUvNQhNQ0RUCRooPQgRmyOE7ZWyq8xVMYyD9ZbVoUk++uIZ8eiPY U/I1WFKoSpI3kI5r2MgAhCNeZW49Eu1qhsssQNKFUfazSyNoaTcxZLViFKPyiuXiq9qx 28sh43t1Q0BFRGkb/l4+dHjv5Rh9I5TrElv4PyZHfbQlO8bpCXl0u6PBJx7oBpaoCv21 NlKA==
X-Received: by 10.66.248.193 with SMTP id yo1mr18547797pac.120.1365819741029;  Fri, 12 Apr 2013 19:22:21 -0700 (PDT)
Received: from spandex.local (66-230-88-244-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.88.244]) by mx.google.com with ESMTPS id ao5sm8606170pbc.25.2013.04.12.19.22.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Apr 2013 19:22:20 -0700 (PDT)
Message-ID: <5168C159.3050004@gmail.com>
Date: Fri, 12 Apr 2013 18:22:17 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net>
In-Reply-To: <51687C0D.8090804@labn.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, 13 Apr 2013 02:22:28 -0000

On 4/12/13 1:26 PM, Lou Berger wrote:
> No argument from me, I'm just asking that a comment/position/question
> that I don't understand be substantiated. 

And I'm telling you that I think the numbers are highly suggestive
of bias.  We can take a swing at getting a very rough handle on
that but I'm actually not sure that we should because it appears
to be the case that the cost of any remediation that some of us
might want to undertake would be higher than the cost of living
with bias in the system (this would be the considerable downside
to consensus decision-making processes with a very large participant
base).

>> And I don't know if you intended to or not, but what you
>> communicated is "The best candidates are nearly always
>> western white guys," since that's who's being selected.
>> That's a problematic suggestion.
> 
> I certainly, in no way, shape, or form intended such an implication.  I
> have not idea how one could read it that way, [ ... ]

A (male) friend once said that men are no more likely to notice
sexism than fish are to notice water.  I think that was far
too broad but generally true.  If I think that white western
men are being selected in disproportion to their presence in
the candidate pool, and I do, then telling me that "we only
choose the best" is telling me that white, western men tend
to be the best.  Pretty much every organization that applauds
itself for its meritocratic reward structure (to the extent
that an I* gig is a "reward") and yet only advances white
guys says the same thing.  It is a trope, and a familiar one.

Melinda

From mrex@sap.com  Fri Apr 12 19:35:33 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3818F21F8E6D; Fri, 12 Apr 2013 19:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vg2pNY7gwjyO; Fri, 12 Apr 2013 19:35:32 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id DECAB21F8E77; Fri, 12 Apr 2013 19:35:31 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r3D2ZHN5024358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 13 Apr 2013 04:35:17 +0200 (MEST)
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
In-Reply-To: <04F36061-25C5-4159-A724-26B192C120DE@jpl.nasa.gov>
To: "Henry B. Hotz" <hotz@jpl.nasa.gov>
Date: Sat, 13 Apr 2013 04:35:16 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130413023516.EB38A1A6AD@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ietf@ietf.org, pkix@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: Sat, 13 Apr 2013 02:35:33 -0000

Henry B. Hotz wrote:
> 
> Stefan Santesson <stefan@aaa-sec.com> wrote:
> >
> > Nothing has changed in this regard.
> > 
> > The good response is pretty clear that it by default provides information
> > that the cert is not on a black-list (is not know to be revoked).
> > However, it is also made clear that extensions may be used to expand this
> > default information about the status.
> > 
> > This is how it always have been, and still is in RFC 256bis.
> 
> So a non-issued cert may be "good".

An rfc2560 OCSP responder might return "good" status for a "not issued"
cert.  That is listed as a caveat in the rfc2560 description for "good".

> 
> > The revoked response simply means that the certificate is revoked.
> > Combined with the new extension, it MAY also be used for non-issued certs.
> 
> So a non-issued cert may be "revoked".

Yes.  That is already possible and fully conforming with rfc2560.
It is just not explicitly standardized how to do it.

IMO it is preferable to standardize how to do it consistently,
rather than "letting a thousand flowers bloom" on the significantly
underspecified rfc2560.


> 
> > It's really as simple as that.
> 
> I would have thought that what was simple was to say a non-issued cert
> was "unknown", since it's neither known-good, nor known-revoked.


That is another permissible response for an rfc2560 OCSP responder.
But there is more to consider than just what is permissible by the spec,
and that is client behaviour of an installed base that has grown over
more than a decade.  If a non-marginal fraction of the installed base
will either fallback to CRL checking or do a soft-fail (assume good)
upon receiving "unknown" status, then this choice of response might
not be very sensible.


>
> Is there any collection of extensions which will allow an RP to know,
> for sure, what value will be returned for a never-issued cert?

The two MUSTs at the end of section 2.2 in rfc2560bis-18 plus the
MUST contain the responseExtension from section 4.4.8.


To facilitate recognizing the revocationTime from the end of
section 2.2 rfc2560bis-18, it really ought to be written as UTCTime!

from (-18):
 -  MUST specify the revocationTime January 1, 1970, and;

to (example):
 -  MUST specify the revocationTime "700101000000Z"


> 
> > It is only the discussion on this list that is confusing and that has
> > managed turn something really simple into a complicated debate.
> 
> What *I* find confusing is the apparent degree of belief that it is
> possible to improve 2560 and simultaneously to maintain backward
> compatibility.  That should only be possible if there are some
> previously-ignored extensions which alter the semantics of the
> information --- effectively creating a version 2 protocol.  

As far as the spec rfc2560 is concerned, this is trivial from a formal
perspective since there is hardly any client behaviour defined in rfc2560.

But the absence of definition  of client behaviour in rfc2560 also
limits what kind of behaviour can be added now.  In particular, mandating
specific behaviour (MUST rather than SHOULD) or prohibiting specific
behaviour (MUST NOR rather than SHOULD NOT) is going to be a backwards
incompatible change, and unless there is a really convincing rationale
for addition of MUST / MUST NOT behaviour, this will result in a
conflict with rfc2119 Section 6!
  http://tools.ietf.org/html/rfc2119#section-6


> 
> I don't find the claim that nothing has changed helpful.


The claim that "nothing has changed" is provably untrue as long as
the imperative MUST for using the Extension in section 4.4.8 of
rfc2560bis-18 persists.

 
> 
> What I would find helpful, and what I think some people really would
> like, is for OCSP to be able to provide white-list information in
> addition to the previous black-list information.  When I read through
> 2560bis, I could not tell if there was an extension which would allow
> an RP to tell if "good" actually meant a cert was on the white list
> (and to know the responder has the white list), or merely not on the
> black list.  (Yes, I'm repeating myself.  Am I making more sense,
> or just wasting everyone's time?)

You're correct, a white-list confirmation is not in rfc2560bis.

There seem to be white-list confirmations in current use as OCSP extensions
for some "Qualified Electronic Signature" (QES) usage scenarios, but the
PKIX WG constituency in favour of the rfc2560 defects prevented that any
existing solutions would be adopted for rfc2560bis.


The technical issue with white-listing is, that the original claim about
the OCSP protocol properties is technically wrong.  rfc2560 OCSP,
just like CRLs, is _not_ about the status of certificates, it is purely
about the status of certificate serial numbers.

In order to obtain a technically sound white-listing response, the
"good" response will have to include a certificate hash in an OCSP
singleResponse extension, not just a mere serial number.  And that
seems to be the solution adopted by some existing "QES" usage scenarios.

Since such solutions exist, adopting one of those in rfc2560bis should
be technically trivial.  But... this is PKIX WG, and my impression over
the past 2 years following this WG is that _nothing_ is trivial in PKIX.


I remember that fruitless discussion about an rfc5280 CRL processing defect.
A related, more severe defect exists in X.509 08/2005. Curiously, the X.509
defect has already been sensibly fixed in X.509 11/2008. However, it turned
out to be impossible to make PKIX adopt the X.509 11/2008 fix for rfc5280bis.
During a hot debate, a significant momentum even emerged to adopt further
breakage from X.509 08/2005 instead the fix from X.509 11/2008, and it
took some effort to prevent the additional breakage from getting
rough consensus within PKIX WG...


-Martin

From l.wood@surrey.ac.uk  Fri Apr 12 19:49:07 2013
Return-Path: <l.wood@surrey.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 D1A2E21F8ED4 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 19:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.848
X-Spam-Level: 
X-Spam-Status: No, score=-3.848 tagged_above=-999 required=5 tests=[AWL=-1.250, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sPN5V0BvWcg1 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 19:49:06 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) by ietfa.amsl.com (Postfix) with ESMTP id 224F621F8EA5 for <ietf@ietf.org>; Fri, 12 Apr 2013 19:49:05 -0700 (PDT)
Received: from [195.245.231.67:31014] by server-13.bemta-5.messagelabs.com id FC/1E-20553-D97C8615; Sat, 13 Apr 2013 02:49:01 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-82.messagelabs.com!1365821341!11551872!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21051 invoked from network); 13 Apr 2013 02:49:01 -0000
Received: from unknown (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-15.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 13 Apr 2013 02:49:01 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Sat, 13 Apr 2013 03:49:00 +0100
From: <l.wood@surrey.ac.uk>
To: <daedulus@btconnect.com>, <arturo.servin@gmail.com>, <ietf@ietf.org>
Date: Sat, 13 Apr 2013 03:46:38 +0100
Subject: RE: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: Ac43wHjwFrYcHDIUQmW8tpHoy/JWwAAMKX+I
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E5F@EXMB01CMS.surrey.ac.uk>
References: <5166F8BD.7010308@isi.edu> <51686076.3010508@gmail.com>, <006e01ce37bf$a45c0ba0$4001a8c0@gateway.2wire.net>
In-Reply-To: <006e01ce37bf$a45c0ba0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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: Sat, 13 Apr 2013 02:49:07 -0000

If you think security and congestion are arcane, you have... problems.

This was an actual ietf working geoup, and not some e.g. W3c thing?

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of t.p. [daed=
ulus@btconnect.com]
Sent: 12 April 2013 21:52
To: Arturo Servin; ietf@ietf.org
Subject: Re: Purpose of IESG Review

----- Original Message -----
From: "Arturo Servin" <arturo.servin@gmail.com>
To: <ietf@ietf.org>
Sent: Friday, April 12, 2013 8:28 PM
>
> Not answering any particular post. Just a comment.
>
> The IESG should be there to attest that the IETF procedure was
followed
> and the document reached consensus in the WG and in the IETF LC and it
> was successfully reviewed by the Gen-ART. If it wasn't then this
> particular process should be reviewed and take actions accordingly
(e.g.
> returning the document to the wg).
>
> But if a single individual of the IESG can technically challenge and
> change the work of a whole WG and the IETF, then we have something
wrong
> in our process because that means that the document had a serious
> problem and we didn't spot it in the process or an IESG member is
using
> its power to change a document according to its personal beliefs.

My experience has been the former, where the IESG has raised concerns
about arcane topics, such as security and congestion, of which the WG
had limited expertise.  This might be caught by a directorate review,
but those seem patchy; it might be caught by IETF Last Call, but if you
are an expert at an arcane topic then you are probably too busy to
follow them.

So I do see the IESG DISCUSSing, when it would have been lovely to have
had, but it is hard to see quite how, it resolved earlier.  We just do
not have the breadth of knowledge of arcane topics.

Tom Petch

> Just a thought,
> as
>
> On 4/11/13 2:54 PM, Joe Touch wrote:
> > Hi, all,
> >
> > As an author who has had (and has) multiple documents in IESG
review,
> > I've noticed an increasing trend of this step to go beyond (IMO) its
> > documented and original intent (BCP 9, currently RFC 2026):
> >
> >    The IESG shall determine whether or not a specification submitted
to
> >    it according to section 6.1.1 satisfies the applicable criteria
for
> >    the recommended action (see sections 4.1 and 4.2), and shall in
> >    addition determine whether or not the technical quality and
clarity
> >    of the specification is consistent with that expected for the
> >    maturity level to which the specification is recommended.
> >
> > Although I appreciate that IESG members are often overloaded, and
the
> > IESG Review step is often the first time many see these documents, I
> > believe they should be expected to more clearly differentiate their
> > "IESG Review" (based on the above criteria) - and its accompanying
> > Position ballot, with their personal review.
> >
> > My concern is that by conflating their IESG position with their
personal
> > review, the document process is inappropriately delayed and that
> > documents are modified to appease a small community that does not
> > justify its position as representative.
> >
> > How do others feel about this?
> >
> > Joe
>



From spencer@wonderhamster.org  Fri Apr 12 20:11:16 2013
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 CCAA521F8E4B; Fri, 12 Apr 2013 20:11:15 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oc+CeiiNamw3; Fri, 12 Apr 2013 20:11:13 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB5821F8E47; Fri, 12 Apr 2013 20:11:04 -0700 (PDT)
Received: from [192.168.1.74] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net [99.108.174.213]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0M3iQL-1UiWJ20BAf-00rcbq; Fri, 12 Apr 2013 23:10:57 -0400
Message-ID: <5168CCBA.4080002@wonderhamster.org>
Date: Fri, 12 Apr 2013 22:10:50 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <6.2.5.6.2.20130411140916.0c412c70@resistor.net> <51681C7C.7050408@wonderhamster.org> <6.2.5.6.2.20130412074639.0ae536b0@resistor.net> <8D23D4052ABE7A4490E77B1A012B630775143E80@mbx-01.win.nominum.com> <6.2.5.6.2.20130412150127.0d2db9d0@resistor.net> <8D23D4052ABE7A4490E77B1A012B630775144439@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775144439@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:euBcnBuKKGAh3anJXWymy2zHcJo4wHwMlIijagYKU/P 6nlQIySTsI/1+p8WvUCybyJX/C0EZnHkxadLopzZCT/ku6dqxx RRyGVwdVtNbVDoK094zOhhH1K4G3OF/0yPXV0WmUM/iMuRiY3r l/eLIq0LV8fvIp4JoaDWG6O3kjX2hTwGpNdjgLHssNerilTPCJ LKtPDSVTghhGIeoxcn3YO8GJCkxx8OrYC+rYQeKkWuy0iU0AUg KspEkSgJ4oUxM30QxX2tQLbKvBV1tkLjl8ieHZUSD44XDMVJsr KaOBa4fZ3dpcnJ32/qiiBcPc2QMOa8skDJOAq3vmZEKDfZpxc4 0uBQlo3ALuXIezPHQdJO0FVIZGig6blwb0RW74JT0
Cc: SM <sm@resistor.net>, "<ietf@ietf.org>" <ietf@ietf.org>, "<iaoc@ietf.org>" <iaoc@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Apr 2013 03:11:16 -0000

On 4/12/2013 8:51 PM, Ted Lemon wrote:
> On Apr 12, 2013, at 7:32 PM, SM <sm@resistor.net> wrote:
>> Thomas Narten mentioned that: "we have the tendency to pick the people we know and trust, which is understandable".  How many IAB members feel strongly about open standards, rough consensus and running code?  To know the answer I would have to actually know the IAB members.
>
> Are they really that hard to get to know?   A number of them are participating in this conversation. It's certainly hard to get time to sit with them at IETF meetings.   I don't know what the workload is like for IAB members, but I think I worked at least an 80 hour week in Orlando.

So, I can only answer for one IAB member ...

I'm less busy during IETF weeks than most IESG members.

It happens that SM grabbed me for at least one extended conversation in 
the hallway in Orlando (he grabbed me for several conversations, but not 
all of them lasted half an hour), and I found that conversation very 
helpful from my side.

Again, for myself - I see my role as an IAB member to be as helpful as I 
can be, so answering questions is something I do, and I need to do more 
often.

There are places I have to be, during IETF weeks - for instance, we were 
interviewing ISOC Board of Trustee nominees at specific times - but 
there are places I'm going that I don't have to get to, if someone needs 
to talk with me.

Finally - there are people on the IAB with fabulous social skills, but 
I'm not one of them. If someone needs to spend time picking my brain, I 
usually do have multiple meals open during IETF week.

Spencer

From fgont@si6networks.com  Fri Apr 12 20:30:21 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1FC821F8EBE; Fri, 12 Apr 2013 20:30:21 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0lIYa9o7-Y3C; Fri, 12 Apr 2013 20:30:21 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE9921F8E47; Fri, 12 Apr 2013 20:30:20 -0700 (PDT)
Received: from 26-174-16-190.fibertel.com.ar ([190.16.174.26] helo=[192.168.1.113]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UQrAN-0008Cz-Gt; Sat, 13 Apr 2013 05:30:15 +0200
Message-ID: <5168D137.4090305@si6networks.com>
Date: Sat, 13 Apr 2013 00:29:59 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [OPSEC] Last Call: <draft-ietf-opsec-ipv6-implications-on-ipv4-nets-03.txt> (Security Implications of IPv6 on IPv4 Networks) to Informational RFC
References: <20130329130326.13012.1402.idtracker@ietfa.amsl.com> <51559943.1010703@gmail.com> <515985E1.1000404@si6networks.com> <515AA8B4.5020707@gmail.com> <5164F5F3.9030007@si6networks.com> <51658DFC.7010504@gmail.com>
In-Reply-To: <51658DFC.7010504@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: opsec@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, 13 Apr 2013 03:30:22 -0000

Hi, Brian,

On 04/10/2013 01:06 PM, Brian E Carpenter wrote:
>> For simplicity sake (and because I'm not sure how one would tone that
>> one down), my suggestion would be to apply you proposed text, modulo
>> that sentence.
>>
>> Would that be okay with you? -- If not, please do let me know, so that
>> we can try to find a way forward that keeps everyone happy.
> 
> Well, it's not for me to call the consenus, but with that sentence
> removed I would personally enter the "no objection" state.

Good.

BTW, it's unclear to me whether I should keep in in the acks or not...
so please do let me know how you'd like me to proceed in this respect.


P.S.: For any other future reviews: I usually do my best to address
others' comments. In the event that you submit feedback, and it looks
like I have not tried to address it, please resend/ping me (most likely
I tried but failed, the feedback slipped by, or whatever... )

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From ajs@anvilwalrusden.com  Fri Apr 12 20:38:01 2013
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 3A1F321F86AD for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 20:38:01 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIvLY+REQKTs for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 20:37:59 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id F2ED721F85D6 for <ietf@ietf.org>; Fri, 12 Apr 2013 20:37:58 -0700 (PDT)
Received: from mx1.yitter.info (li440-116.members.linode.com [50.116.54.116]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 0BFB28A031 for <ietf@ietf.org>; Sat, 13 Apr 2013 03:37:58 +0000 (UTC)
Date: Fri, 12 Apr 2013 23:37:55 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130413033755.GC5403@mx1.yitter.info>
References: <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5168C159.3050004@gmail.com>
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: Sat, 13 Apr 2013 03:38:01 -0000

On Fri, Apr 12, 2013 at 06:22:17PM -0800, Melinda Shore wrote:

> to be the best.  Pretty much every organization that applauds
> itself for its meritocratic reward structure (to the extent
> that an I* gig is a "reward") and yet only advances white
> guys says the same thing. 

Speaking only personally, I tend to agree with the above.  Despite my
earlier remark that I think it'd be good to get a rough idea about the
size of the problem, I'm not sure what to do about it.  I'm
particularly worried that I'm going to get to live through a repeat
experience.  The following is a cautionary tale, cartoonish but not so
far from the way I observed it.

In the parts of Canada where I lived in the 1990s, philosophy
departments (which had truly abysmal numbers of female faculty)
decided there was a shortage of female faculty -- despite the "facts"
that they'd always promoted only the best, were all sooper-rational
detached unbiased people, and so on.  The problem was, of course, made
considerably worse by the tenure system, which (owing to the quirks of
the historic expansion of departments) meant that an overwhelming
number of tenured faculty were roughly the same age.  In any case, the
Canadian Philosophical Association and, correspondingly, most
departments decided to adopt a principle that, whenever there was an
open spot, if there were two qualified people and one of them was a
woman, the woman should be chosen.

You can imagine the effect.  A large number of (usually in my
experience truly mediocre) male PhDs concluded that the only reason
they didn't get a tenured job was because there were "quotas".  (It
certainly had nothing to do with the overabundance of mediocre PhDs in
philosophy.)  Meanwhile, any woman who wasn't doing things from a
feminist perspective was automatically pegged as some sort of toady
trying to get in good with the patriarchy in order to get her portion
of the quota.  Deeply sexist men who went around enforcing the
"girls do girl-philsophy, not this hard stuff I do" could congratulate
themselves for being open minded and non-sexist, even if they made
jaw-droppingly obscene remarks to female students.  The entire
atmosphere was poisoned.  None of this was the reason I quit my
doctoral program (I was one of the mediocrities), but it sure didn't
count as a reason to stay.

The only lesson I really learned from that experience is that it is
incredibly hard for women[1] to be treated as adult colleagues in an
environment that acts overwhelmingly as a white male club.  I still
have no idea how to do anything about it except to try to be super
attentive to the problem all the time.  That's why I'd like us to have
an idea of roughly how badly we're doing: then we can pay attention to
our weaknesses in an effort to turn such attention into a strength.

[1] In this case, but I actually think this generalizes to other
groups pretty well.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From scott@kitterman.com  Fri Apr 12 22:36:58 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56C9A21F8F56 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 22:36:58 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6ges0ekkmPl for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 22:36:57 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0AABD21F8F4D for <ietf@ietf.org>; Fri, 12 Apr 2013 22:36:56 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id DC9EED04088; Sat, 13 Apr 2013 00:36:53 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1365831413; bh=X1wRl/u+mOfru2JdTAXAfd290PRAxOJbrne8fPLK11o=; h=In-Reply-To:References:Subject:From:Date:To:From; b=gAwdt2rAFSkPFRe7hO9UimsSlSoZ3UUDXvV+scAiMa/m93zttXckyJJHj7ocxXvp+ UXJJ1juh8BIj50xu20ykAE3upml/zC/vOYmUK6rS6WOncNGIO6eQCMslvHmhJ8ymmT sWi7cngkiLEC+ZK5iqzdezhj7Y5azetYqoUT9Rio=
Received: from [IPV6:2600:1002:b10b:eb7d:82bb:5363:3b75:3fe3] (unknown [IPv6:2600:1002:b10b:eb7d:82bb:5363:3b75:3fe3]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 71345D04059;  Sat, 13 Apr 2013 00:36:53 -0500 (CDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <20130413033755.GC5403@mx1.yitter.info>
References: <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <20130413033755.GC5403@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Scott Kitterman <scott@kitterman.com>
Date: Sat, 13 Apr 2013 01:36:50 -0400
To: ietf@ietf.org
Message-ID: <257c15fa-a86f-44db-a499-8d0ebf9e9488@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Apr 2013 05:36:58 -0000

Andrew Sullivan <ajs@anvilwalrusden.com> wrote:

>On Fri, Apr 12, 2013 at 06:22:17PM -0800, Melinda Shore wrote:
>
>> to be the best.  Pretty much every organization that applauds
>> itself for its meritocratic reward structure (to the extent
>> that an I* gig is a "reward") and yet only advances white
>> guys says the same thing. 
>
>Speaking only personally, I tend to agree with the above.  Despite my
>earlier remark that I think it'd be good to get a rough idea about the
>size of the problem, I'm not sure what to do about it.  I'm
>particularly worried that I'm going to get to live through a repeat
>experience.  The following is a cautionary tale, cartoonish but not so
>far from the way I observed it.
>
>In the parts of Canada where I lived in the 1990s, philosophy
>departments (which had truly abysmal numbers of female faculty)
>decided there was a shortage of female faculty -- despite the "facts"
>that they'd always promoted only the best, were all sooper-rational
>detached unbiased people, and so on.  The problem was, of course, made
>considerably worse by the tenure system, which (owing to the quirks of
>the historic expansion of departments) meant that an overwhelming
>number of tenured faculty were roughly the same age.  In any case, the
>Canadian Philosophical Association and, correspondingly, most
>departments decided to adopt a principle that, whenever there was an
>open spot, if there were two qualified people and one of them was a
>woman, the woman should be chosen.
>
>You can imagine the effect.  A large number of (usually in my
>experience truly mediocre) male PhDs concluded that the only reason
>they didn't get a tenured job was because there were "quotas".  (It
>certainly had nothing to do with the overabundance of mediocre PhDs in
>philosophy.)  Meanwhile, any woman who wasn't doing things from a
>feminist perspective was automatically pegged as some sort of toady
>trying to get in good with the patriarchy in order to get her portion
>of the quota.  Deeply sexist men who went around enforcing the
>"girls do girl-philsophy, not this hard stuff I do" could congratulate
>themselves for being open minded and non-sexist, even if they made
>jaw-droppingly obscene remarks to female students.  The entire
>atmosphere was poisoned.  None of this was the reason I quit my
>doctoral program (I was one of the mediocrities), but it sure didn't
>count as a reason to stay.
>
>The only lesson I really learned from that experience is that it is
>incredibly hard for women[1] to be treated as adult colleagues in an
>environment that acts overwhelmingly as a white male club.  I still
>have no idea how to do anything about it except to try to be super
>attentive to the problem all the time.  That's why I'd like us to have
>an idea of roughly how badly we're doing: then we can pay attention to
>our weaknesses in an effort to turn such attention into a strength.
>
>[1] In this case, but I actually think this generalizes to other
>groups pretty well.

I've seen similar things in other contexts too.  I'd suggest turning the question around. I don't think the question of if there is bias or not is reasonably measurable. 

There is also a reasonable body of evidence that people who are in a small minority will tend to feel unwelcome regardless of if there are any actual bias or barriers. 

Rather the engage in navel gazing about bias detection, engage in finding ways to engage in encouraging more participation from ${group}.

The question to ask is "What can the IETF do to be more open/inviting?"

Scott K


From abdussalambaryun@gmail.com  Fri Apr 12 23:37:27 2013
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 4198321F8E2C for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 23:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.102
X-Spam-Level: 
X-Spam-Status: No, score=-3.102 tagged_above=-999 required=5 tests=[AWL=0.497,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9QM6R5uNGYHt for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 23:37:25 -0700 (PDT)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by ietfa.amsl.com (Postfix) with ESMTP id 3331C21F8825 for <ietf@ietf.org>; Fri, 12 Apr 2013 23:37:25 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id lb1so1789289pab.5 for <ietf@ietf.org>; Fri, 12 Apr 2013 23:37:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=7rcD2ZmoRBTbCfswPQ1Umw8O6k1CbIHywKLxBMyQqeA=; b=u3yaaoh8L92ODaHYNeRgxEzzwKLPlwliY0eyZevf9nnEky7RtMmOvQHeULsUohKg1S oz2F24QXeSbgjzvd6s3UxRG641MTxD57ShaD68EqFv7s2O01eSNS9WP1ktZPvtY2bPEi IDoZEwxHGGQBrFlR+reP5qL9w3OVRrzxFPkeJ1IzLVI9q9Cklxoi8jZ2MtTushRYfEPK a1+LUPN5GL+4jYyQo0Lvyhj7of5KUsFSLHF1/MoPo7JU743eNObyM1YXNGMX/tRdRprk elvCiXiOQDnZtPYPlwBtiaDYmTl1q3ngskYQJ/Ijnl5viSo8hImsjOO7j4/O56G5GIIO JL0Q==
MIME-Version: 1.0
X-Received: by 10.69.12.37 with SMTP id en5mr6218973pbd.93.1365835043968; Fri, 12 Apr 2013 23:37:23 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Fri, 12 Apr 2013 23:37:23 -0700 (PDT)
In-Reply-To: <51686FE0.8000201@gmail.com>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <51686FE0.8000201@gmail.com>
Date: Sat, 13 Apr 2013 08:37:23 +0200
Message-ID: <CADnDZ8-AHNGCGcvx2_Ug1Le3VLE7eqstCJUWwEXQ8Mp7jsnNUw@mail.gmail.com>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Arturo Servin <arturo.servin@gmail.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: Sat, 13 Apr 2013 06:37:27 -0000

Hi Arturo, and all,
(sorry that this message is long but I want to make this my last post
on the subject)

The reason of this message/subject is that I want to avoid some group
working together to achieve their purpose (while they may be fogetting
the IETF purpose) within a WG. If I am a company and interested to
publish a standard in IETF, I may think to find interest in my market
place (i.e. interest usually in my local country or city which depends
on relations), when that is gained then the purpose is to publish it
in IETF while there already gauranteed sort of back up in that
country/city. I name that a *group purpose* not the *WG purpose*.
Group purpose is good but may lack technical experience, which needs
following WG purpose.

Any group (usually authors+ WhoInterestedToPublish) needs to convence
the WG by technical discussions. Consensus and running code, may work
for the group purpose more than the WG purpose if the WG are not
reactive to inputs. I recommend that WG chairs are already aware of
this and try to find independent reviewers from the WG to put some
effort before it is submitted to the IESG. Usually WG participants are
bussy and may not be interested to argue with a group (one reviewer
may get many replies with arguments that he/she has no much time to
DISCUSS, or reply).

 That is why the IESG's DISCUSS position is strong and important to
make the group answer to purpose, and that position is weak in WGs.
Groups always don't like delays in process, but WGs don't like
changing their IETF purpose or their IETF vision. I recommend that WG
chairs try to do their best to have two independent WG participants to
review (not authors and not from the same company of authors or same
state/city).

If you send me a reply I will reply privately so I don't disturb,
because the subject may not be important for others, thanking you,

AB

We need diversity :-)
-------------------------------
On 4/12/13, Arturo Servin <arturo.servin@gmail.com> wrote:
>
>
> On 4/12/13 4:58 PM, Abdussalam Baryun wrote:
>> I just change the subject because I still beleive the problem with
>> review is in the WG not IESG. Some WGs have few reviews on each WG
>> document, that may not be bad, but I think having only one review or
>> comment (excluding authors) within a WGLC is wrong in a WG review
>> process. I think WG chair can find two participants to do it.
>
> 	It seems plausible.
>
>>
>> I recommend WG's process to change their purpose so we have to get *two
>> participants* which are not authors to review the work and comment
>> within WGLC (even small text comment is ok). I recommend WG chairs to
>> think about this proposal, if not then I will try write an I-D for this
>> and communicate with community.
>
> 	Possible we would need any how an I+D to change the process and mandate
> this new review.
>
> 	I haven't made my mind but it seems like a good idea.
>
>>
>> AB
>
> Regards
> as
>

From abdussalambaryun@gmail.com  Fri Apr 12 23:55:11 2013
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 17C0921F8FD7 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 23:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.131
X-Spam-Level: 
X-Spam-Status: No, score=-3.131 tagged_above=-999 required=5 tests=[AWL=0.468,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eA++iacacdsL for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 23:55:09 -0700 (PDT)
Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by ietfa.amsl.com (Postfix) with ESMTP id 5092421F89D8 for <ietf@ietf.org>; Fri, 12 Apr 2013 23:55:09 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id bj3so1806857pad.34 for <ietf@ietf.org>; Fri, 12 Apr 2013 23:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=tOFFUYYH9gyqTFBpuuySW2z1/HQ/M20KOKbNhmo08SM=; b=mZXUvbvzKSjG/9WnjoC0d3miOZha5j1KbMw4Bs6nKfi2Z9owwhpBPZ1SJfmvF+t2Zs XFU4y1vELelZavLXUIA4JmddjeqakhgmsYkiNxWGkl3IRQzz6xWbg7Fs4OWQu6xgFzFM zM+YMKiM1gbcorf4c/grzlkU9u5A1Z9VRh+OtxBDGMa7iRLqvGuNnGwHxr9SLIbX4mI4 Ou11hNNmGpuTGKWkHyxvM78XOEPN4W5rLUrJZGeP5pj7F6ZWFnxQauika/uTkh88fFrH QIQVR74n0sIys6cxwHKFMxCviOzVbswA17Jycvbwl2XM6TY4svrDVIF46Klomh2MPQcY GN+A==
MIME-Version: 1.0
X-Received: by 10.66.122.8 with SMTP id lo8mr19219195pab.163.1365836109064; Fri, 12 Apr 2013 23:55:09 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Fri, 12 Apr 2013 23:55:08 -0700 (PDT)
In-Reply-To: <EB9B93801780FD4CA165E0FBCB3C3E672AD2DF79@SJEXCHMB09.corp.ad.broadcom.com>
References: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com> <DC0F69276BCB2F0B5758CFC3@JcK-HP8200.jck.com> <EB9B93801780FD4CA165E0FBCB3C3E672AD2DF79@SJEXCHMB09.corp.ad.broadcom.com>
Date: Sat, 13 Apr 2013 08:55:08 +0200
Message-ID: <CADnDZ88gy9nwVX2EyTFeuyAeBNtV9zOYHczNYAqUKV8EAuBM=A@mail.gmail.com>
Subject: Re: Purpose of IESG Review
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Pat Thaler <pthaler@broadcom.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.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: Sat, 13 Apr 2013 06:55:11 -0000

Do you raise a discussion saying the below?

I believe you should be expected to more clearly differentiate your
*Review* (based on the such procedure criteria) - and its accompanying
Position ballot, with your personal review.
(Modified from the first message of thread)

Refering to first message:
I believe they should be expected to more clearly differentiate their
"IESG Review" (based on the above criteria) - and its accompanying
Position ballot, with their personal review.

We need manager's personal review and experience, I think the business
needs manager's personal views as well.

AB

On 4/13/13, Pat Thaler <pthaler@broadcom.com> wrote:
> +1 on for John's response.
>
> I will argue with my manager if I think they are wrong and I've gotten
> positive results from giving managers feedback on their performance. Of
> course, disagreeing with management won't always get the decision changed,
> but I've never felt I lost anything by raising the discussion.
>
> I've also seen some bad decisions made when someone had good reasons why a
> decision was wrong but didn't surface them because they didn't feel they
> could argue with management.
>
> IETF participant to IETF leadership isn't the same as employee to manager of
> course. We are all volunteers collaborating to get good results and if we
> feel there is a process problem we can discuss it. IETF formalizes this by
> having open mike sessions for example.
>
> A thread on whether there is a problem with the IESG review process is
> appropriate, IMO.
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of John
> C Klensin
> Sent: Friday, April 12, 2013 3:19 PM
> To: Abdussalam Baryun; ietf
> Subject: Re: Purpose of IESG Review
>
>
>
> --On Friday, April 12, 2013 20:24 +0100 Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>
>> How can a memebr of staff in a company argue with the manager
>> about the manager's decisions or performance?
>
> In most successful companies, yes.
>
>> Only
>> Owners/shareholders can question managers and staff.
>
> And companies that behave that way don't last very long in
> rapidly evolving fields... at least unless the managers are
> endowed with perfect wisdom.  It is not an accident that most
> management schools teach would-be managers that listening
> --especially to the people on  the front lines-- is a very
> important skill.
>
> So, at the risk of generalizing too much... What on earth are
> you talking about and what experience do you have and use to
> justify it?
>
>     john
>
>
>
>

From stefan@aaa-sec.com  Sat Apr 13 00:03:41 2013
Return-Path: <stefan@aaa-sec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 288C121F8F56 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 00:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbY8qIBR7pQL for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 00:03:40 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by ietfa.amsl.com (Postfix) with ESMTP id 8D39621F8AAA for <ietf@ietf.org>; Sat, 13 Apr 2013 00:03:39 -0700 (PDT)
Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id 2F2E3209376B for <ietf@ietf.org>; Sat, 13 Apr 2013 09:03:39 +0200 (CEST)
X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se
Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3Ng86utq-yjI for <ietf@ietf.org>; Sat, 13 Apr 2013 09:03:38 +0200 (CEST)
Received: from s327.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id D72032093763 for <ietf@ietf.org>; Sat, 13 Apr 2013 09:03:38 +0200 (CEST)
Received: (qmail 76317 invoked from network); 13 Apr 2013 07:03:38 -0000
Received: from 81-232-51-61-no39.business.telia.com (HELO [192.168.0.104]) (stefan@fiddler.nu@[81.232.51.61]) (envelope-sender <stefan@aaa-sec.com>) by s327.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <hotz@jpl.nasa.gov>; 13 Apr 2013 07:03:38 -0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Sat, 13 Apr 2013 09:03:35 +0200
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
From: Stefan Santesson <stefan@aaa-sec.com>
To: "Henry B. Hotz" <hotz@jpl.nasa.gov>
Message-ID: <CD8ECDB9.60B3E%stefan@aaa-sec.com>
Thread-Topic: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
In-Reply-To: <18ED26A1-402F-40F3-A97F-380441620175@jpl.nasa.gov>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: pkix@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, 13 Apr 2013 07:03:41 -0000

On 4/13/13 2:53 AM, "Henry B. Hotz" <hotz@jpl.nasa.gov> wrote:

>You've just said that there are only two valid responses from an OCSP
>server which has access to a white list.  In other words such a server
>inherently cannot provide any information about the actual revocation
>status of a cert, and its responses cannot distinguish between a
>lost/forged/whatever cert and a known-bad (actually revoked) cert.

I realize it's unfair of me to take this quote out of context.  Apologies,
but I want to focus on it. (Stole your words :))


No that is NOT what I say.

An extension may differentiate which serial number that results in a
"revoked" response, that is actually issued and revoked, or if there is
any other particular reason for responding "revoked".
In my universe a syntactically valid serial number can only be good,
revoked or non-issued. But expressing this in general terms anyway.

So with the help of extensions, a responder can provide both white and
black list data.

The legacy client will just look at the status and act accordingly. The
extension aware client and a later audit can use the extensions to further
determine what happened.

/Stefan



From brian.e.carpenter@gmail.com  Sat Apr 13 00:06:01 2013
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 EAE4221F8CF0 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 00:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.877
X-Spam-Level: 
X-Spam-Status: No, score=-99.877 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XkVlsoZkmiFF for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 00:06:01 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E95EC21F85E7 for <ietf@ietf.org>; Sat, 13 Apr 2013 00:06:00 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id k13so210409wgh.1 for <ietf@ietf.org>; Sat, 13 Apr 2013 00:06:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bmon0K9R/VMkOhB91GTPI12C7fUIAoHJgTSYt26+mcc=; b=aefanmGW4y0PvwYM6dTR8G+TSIwxjdPcTMU7RKpJlHXGKv1k0xq7jLDd51EtcML3wV 7gmfxqEs4iXKOfPAselYVPnVlc8lXxz38d2chK2nUDqLkDX1agKxSOzS52l4R/Bkfez9 gx/4bSc7c8FciJodp3DLzAr3CwumhoVfjnTdNX49AvOshIR9sTiTWAffbY1Hdpq6UDW7 qPj5V2k/sNlrlEL5JpuHCmXpKnDR/w6t9zTLqVY1pBlXkCeUS7xmj5IA5t+MsayizljJ GmhZ5p51G2IAb5/A6jAPIZwbrdGLXHDGiPVco7/Un1c5AixAp6h2VsRL9Fpaz2D59HOa 8i2g==
X-Received: by 10.194.177.200 with SMTP id cs8mr4782666wjc.22.1365836759950; Sat, 13 Apr 2013 00:05:59 -0700 (PDT)
Received: from [192.168.1.65] (host-84-13-239-74.opaltelecom.net. [84.13.239.74]) by mx.google.com with ESMTPS id q13sm1646153wie.0.2013.04.13.00.05.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 13 Apr 2013 00:05:59 -0700 (PDT)
Message-ID: <516903E5.6090400@gmail.com>
Date: Sat, 13 Apr 2013 08:06:13 +0100
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: l.wood@surrey.ac.uk
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <51686076.3010508@gmail.com>, <006e01ce37bf$a45c0ba0$4001a8c0@gateway.2wire.net> <290E20B455C66743BE178C5C84F12408223F494E5F@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E5F@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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: Sat, 13 Apr 2013 07:06:02 -0000

On 13/04/2013 03:46, l.wood@surrey.ac.uk wrote:
> If you think security and congestion are arcane, you have... problems.

I think this may be the point that Diana Raft was making in draft-draft-draft
about 12 days ago.

   Brian

> 
> This was an actual ietf working geoup, and not some e.g. W3c thing?
> 
> Lloyd Wood
> http://sat-net.com/L.Wood/
> 
> 
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of t.p. [daedulus@btconnect.com]
> Sent: 12 April 2013 21:52
> To: Arturo Servin; ietf@ietf.org
> Subject: Re: Purpose of IESG Review
> 
> ----- Original Message -----
> From: "Arturo Servin" <arturo.servin@gmail.com>
> To: <ietf@ietf.org>
> Sent: Friday, April 12, 2013 8:28 PM
>> Not answering any particular post. Just a comment.
>>
>> The IESG should be there to attest that the IETF procedure was
> followed
>> and the document reached consensus in the WG and in the IETF LC and it
>> was successfully reviewed by the Gen-ART. If it wasn't then this
>> particular process should be reviewed and take actions accordingly
> (e.g.
>> returning the document to the wg).
>>
>> But if a single individual of the IESG can technically challenge and
>> change the work of a whole WG and the IETF, then we have something
> wrong
>> in our process because that means that the document had a serious
>> problem and we didn't spot it in the process or an IESG member is
> using
>> its power to change a document according to its personal beliefs.
> 
> My experience has been the former, where the IESG has raised concerns
> about arcane topics, such as security and congestion, of which the WG
> had limited expertise.  This might be caught by a directorate review,
> but those seem patchy; it might be caught by IETF Last Call, but if you
> are an expert at an arcane topic then you are probably too busy to
> follow them.
> 
> So I do see the IESG DISCUSSing, when it would have been lovely to have
> had, but it is hard to see quite how, it resolved earlier.  We just do
> not have the breadth of knowledge of arcane topics.
> 
> Tom Petch
> 
>> Just a thought,
>> as
>>
>> On 4/11/13 2:54 PM, Joe Touch wrote:
>>> Hi, all,
>>>
>>> As an author who has had (and has) multiple documents in IESG
> review,
>>> I've noticed an increasing trend of this step to go beyond (IMO) its
>>> documented and original intent (BCP 9, currently RFC 2026):
>>>
>>>    The IESG shall determine whether or not a specification submitted
> to
>>>    it according to section 6.1.1 satisfies the applicable criteria
> for
>>>    the recommended action (see sections 4.1 and 4.2), and shall in
>>>    addition determine whether or not the technical quality and
> clarity
>>>    of the specification is consistent with that expected for the
>>>    maturity level to which the specification is recommended.
>>>
>>> Although I appreciate that IESG members are often overloaded, and
> the
>>> IESG Review step is often the first time many see these documents, I
>>> believe they should be expected to more clearly differentiate their
>>> "IESG Review" (based on the above criteria) - and its accompanying
>>> Position ballot, with their personal review.
>>>
>>> My concern is that by conflating their IESG position with their
> personal
>>> review, the document process is inappropriately delayed and that
>>> documents are modified to appease a small community that does not
>>> justify its position as representative.
>>>
>>> How do others feel about this?
>>>
>>> Joe
> 
> 
> 

From lear@cisco.com  Sat Apr 13 00:12:43 2013
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 E670521F87B6 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 00:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.298
X-Spam-Level: 
X-Spam-Status: No, score=-110.298 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4MXCZWGmXga for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 00:12:42 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDEC21F86D9 for <ietf@ietf.org>; Sat, 13 Apr 2013 00:12:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2923; q=dns/txt; s=iport; t=1365837162; x=1367046762; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=dvTw33ojByV2HMTUZj9ahwuZyCaZFrmI3Z8lT9yMp2E=; b=drvWDYm3BLrpxI0aXkTdyXrMVuxs/5+iMAtSBnO9QHWKJ/vyXqmK93O0 03J8e+eXrOLsczGT/6V1FpQTWyAQvUQF+7wF25nHvdNWKRUqhoF6Aq5j2 s+/4t7tFLkTgqyHoNQFE7SyNahx8wBAXOa9XwDjN8J2EkvDtZyjIlbXnQ U=;
X-IronPort-AV: E=Sophos;i="4.87,466,1363132800"; d="scan'208,217";a="81960725"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 13 Apr 2013 07:12:41 +0000
Received: from mctiny.local ([10.61.211.12]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3D7CcbL026589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Apr 2013 07:12:39 GMT
Message-ID: <51690566.6000303@cisco.com>
Date: Sat, 13 Apr 2013 09:12:38 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com>
In-Reply-To: <51685369.4000306@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative; boundary="------------010309080907070804000606"
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, 13 Apr 2013 07:12:44 -0000

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

I struggle to engage in this debate because in general I'm not sure how
my voice helps advance the general discussion.  But I do want to make
two points:

On 4/12/13 8:33 PM, Melinda Shore wrote:
> I think it's unintentional [...]

 1. As others have said there are many forms of bias in play, which may
    require different forms of redress.  I expect we can be more
    successful in some areas than others.
 2. Let's be careful with using words like "unintentional".  For all we
    know there may be very good reasons that led to the results of this
    year.  This is not something I would expect to come out of a NOMCOM
    report, by the way, due to their confidentiality requirements.  And
    there is where I think we are most wrapped around the axle.

In any case, hard as it may be, we as a community have identified a huge
concern, and it would be regrettable if we didn't explore that concern
and try to find areas in which we could improve.  I claim  that doing so
will improve the IETF in the longer term.

Eliot

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

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I struggle to engage in this debate because in general I'm not sure
    how my voice helps advance the general discussion.  But I do want to
    make two points:<br>
    <br>
    <div class="moz-cite-prefix">On 4/12/13 8:33 PM, Melinda Shore
      wrote:<br>
    </div>
    <blockquote cite="mid:51685369.4000306@gmail.com" type="cite">
      <pre wrap="">
I think it's unintentional [...]</pre>
    </blockquote>
    <br>
    <ol>
      <li>As others have said there are many forms of bias in play,
        which may require different forms of redress.  I expect we can
        be more successful in some areas than others. </li>
      <li>Let's be careful with using words like "unintentional".  For
        all we know there may be very good reasons that led to the
        results of this year.  This is not something I would expect to
        come out of a NOMCOM report, by the way, due to their
        confidentiality requirements.  And there is where I think we are
        most wrapped around the axle. <br>
      </li>
    </ol>
    In any case, hard as it may be, we as a community have identified a
    huge concern, and it would be regrettable if we didn't explore that
    concern and try to find areas in which we could improve.  I claim 
    that doing so will improve the IETF in the longer term.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------010309080907070804000606--

From stbryant@cisco.com  Sat Apr 13 01:13:14 2013
Return-Path: <stbryant@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 E39A921F8B5F for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 01:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.028
X-Spam-Level: 
X-Spam-Status: No, score=-110.028 tagged_above=-999 required=5 tests=[AWL=0.572, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zoAdyQCctiTI for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 01:13:13 -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 AE18721F8B11 for <ietf@ietf.org>; Sat, 13 Apr 2013 01:13:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1124; q=dns/txt; s=iport; t=1365840792; x=1367050392; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=aKLKBoV9aCfXjaYFcyuT5297mhcBSr8I4bC1C7xc06o=; b=VKz+s/gSk5v1QL9E+iUcMI8MmN3o+18oZ7ExbDK5WpotJE20FpdJkUhW Jr787AohVU8Fl11LTt8tzaarMQk1F2w9YmBLfVZNAEFDuwjHDT18gNr0H RWd5PPNv3NhS/H6hRkjdkaHXzTPkN5Z2vqs8ioMZQrUq1bndsrK5iwsbF E=;
X-IronPort-AV: E=Sophos;i="4.87,466,1363132800"; d="scan'208";a="152856590"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 13 Apr 2013 08:13:11 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3D8D9IO021318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Apr 2013 08:13:09 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3D8D8X3002361; Sat, 13 Apr 2013 09:13:09 +0100 (BST)
Message-ID: <51691394.2040807@cisco.com>
Date: Sat, 13 Apr 2013 09:13:08 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <5167B41A.2070209@gmail.com> <8C48B86A895913448548E6D15DA7553B80B284@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B80B284@xmb-rcd-x09.cisco.com>
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
Reply-To: stbryant@cisco.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: Sat, 13 Apr 2013 08:13:14 -0000

On 12/04/2013 14:17, Fred Baker (fred) wrote:
> On Apr 12, 2013, at 12:13 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>
>> Seeing randomly selected drafts as a Gen-ART reviewer, I can
>> say that serious defects quite often survive WG review and
>> sometimes survive IETF Last Call review, so the final review
>> by the IESG does serve a purpose.
> I'm not saying it doesn't serve a purpose. I'm saying that I know of drafts that have been nearly rewritten during such back-and-forth, so what popped out was largely unrelated to what went in. In such cases, I think the document should have been returned to the working group with comments, not worked on privately.

Fred

The Discusses and Comments are public, all versions of the draft are 
public, the authors and chairs (who are usually the shepherds) see all 
the review emails. Now maybe the IESG need to be more pro-active in 
sending drafts back to the WG, although that may also be unpopular, but 
if an author, shepherd or chair made that request I can think of few 
circumstances where an AD that would likely refuse.

- Stewart



From stbryant@cisco.com  Sat Apr 13 02:17:04 2013
Return-Path: <stbryant@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 E205721F8738 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 02:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.099
X-Spam-Level: 
X-Spam-Status: No, score=-110.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5kc9QPjjWl2Q for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 02:17:04 -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 EE4C021F871C for <ietf@ietf.org>; Sat, 13 Apr 2013 02:17:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1600; q=dns/txt; s=iport; t=1365844624; x=1367054224; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=UvzFSh1CJnLjHGI6p4jqVfE/GHBGeqkbROq+2vmgqv0=; b=VwOpS9qPiHkESCQfIZ/AwEGzC/LIUtWqGdcjvqKzJjlyFrnZLKDOm01p gT1eTv3C0DGp4wNKgc1naiDGFDPIOm0wIy4+bMQi0OJht+MBACLnaforU SPbsa3Jgs40lT9i50kOLaLbeotCjhwMbYqGAnkmNLL/iGzOyxJYuXCU/B 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0FAEkiaVGQ/khR/2dsb2JhbABQgwa/HYJngQYWdIIfAQEBBDhAARALGAkWDwkDAgECAUUGDQEHAQEQiAC8Lo8XB4NBA5cCkRGDDA
X-IronPort-AV: E=Sophos;i="4.87,466,1363132800"; d="scan'208";a="13308673"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 13 Apr 2013 09:16:47 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3D9GjfE001668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Apr 2013 09:16:45 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3D9GiNC004415; Sat, 13 Apr 2013 10:16:45 +0100 (BST)
Message-ID: <5169227C.3090905@cisco.com>
Date: Sat, 13 Apr 2013 10:16:44 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Purpose of IESG Review
References: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com> <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.com>
In-Reply-To: <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: Sat, 13 Apr 2013 09:17:05 -0000

AB

Have you considered that the key thing to remember in the
IETF is that:

"Foo is broken because of (carefully reasoned) Bar" always trumps
"Foo is OK because of who I am" ... and of course vise versa.

Thus in the IETF influence is a function of the ability to
carefully construct a well reasoned technical argument rather
than organizational position.

Of course you have to accept that no matter how carefully
reasoned your case for Bar is, your reasoning may be flawed,
and if that is the case you will normally be told so, sometimes
fairly bluntly, and that the NULL argument will likely be ignored
as noise.

- Stewart


On 12/04/2013 20:24, Abdussalam Baryun wrote:
> How can a memebr of staff in a company argue with the manager about 
> the manager's decisions or performance? Only Owners/shareholders can 
> question managers and staff. IMO, the meeting/list discussions on any 
> issue without an I-D written is the staff talking/working.
> If you write an I-D and to update the procedure related to the 
> subject, you should consider many issues and I think will need many 
> years of discussions, but then better effort result. IMHO, writing an 
> I-D and getting back up by community discussion (with rough 
> consensus) is in the top level and is the owner talking.
> I hope that when I review and comment on an I-D, it should be 
> considered as one owner is talking, but seems like editors think they 
> are the only owners. When IESG comment on the I-D it is 
> managers/excutives talking. All parts are important to the best of output.
> AB


From sm@resistor.net  Sat Apr 13 02:41:48 2013
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 217F021F85F3; Sat, 13 Apr 2013 02:41:48 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8sjliO7SglJq; Sat, 13 Apr 2013 02:41:47 -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 810A221F85EE; Sat, 13 Apr 2013 02:41:47 -0700 (PDT)
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 r3D9fe33008997; Sat, 13 Apr 2013 02:41:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365846106; bh=OG+oYEXwieBXty/wcu2YE+5i7GHYjeoj/6ygrDkwDv8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MfL4JDOGnR5JIgeSsG2w3fs2OMR3Pj9Il1vfpTuD947Uyu3CCcFLO3StoV1nlPn15 djdPebxCu/tlWv1aQWitx6mKicGunlYIGVl34GBGGXAAsOCnfDwCAXPZeJUUkCarzX eaCFnFOf768Ni6O+AmtYshSms5GcQDPa/nXQMOOM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365846106; i=@resistor.net; bh=OG+oYEXwieBXty/wcu2YE+5i7GHYjeoj/6ygrDkwDv8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RjMHXzDXlYA66WYi8nV5BGZyxnVeJDuYZRZAejFHlYd0qZwYhJOr7GCzl+3oPwr2W acMjcvqh/89GBhlGxznm/72WV5PU0wFRFwtexSliJAx27nIA1ta5Ade2bfUagRVyOS vRGt74gWXh3miGraOdc4uhuCMpsD2EYEIC1qZS2E=
Message-Id: <6.2.5.6.2.20130412214008.0da31498@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 13 Apr 2013 00:04:57 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>, Spencer Dawkins <spencer@wonderhamster.org>
From: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775144439@mbx-01.win.nominu m.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <6.2.5.6.2.20130411140916.0c412c70@resistor.net> <51681C7C.7050408@wonderhamster.org> <6.2.5.6.2.20130412074639.0ae536b0@resistor.net> <8D23D4052ABE7A4490E77B1A012B630775143E80@mbx-01.win.nominum.com> <6.2.5.6.2.20130412150127.0d2db9d0@resistor.net> <8D23D4052ABE7A4490E77B1A012B630775144439@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iaoc@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, 13 Apr 2013 09:41:48 -0000

Hi Ted, Spencer

[I am merging my replies for convenience]

At 18:51 12-04-2013, Ted Lemon wrote:
>Are they really that hard to get to know?   A number of them are 
>participating in this conversation. It's certainly hard to get time 
>to sit with them at IETF meetings.   I don't know what the workload 
>is like for IAB members, but I think I worked at least an 80 hour 
>week in Orlando.

It's not that hard to get to meet an IAB member.  However, they have 
a busy workload which makes it difficult to meet them for a 
chat.  Speaking for myself, I have not had any difficult meeting a 
few IAB members.  I do not assume that the average IETF participant 
will get to know them.

At 20:10 12-04-2013, Spencer Dawkins wrote:
>It happens that SM grabbed me for at least one extended conversation 
>in the hallway in Orlando (he grabbed me for several conversations, 
>but not all of them lasted half an hour), and I found that 
>conversation very helpful from my side.

I found the conversation helpful too.

>Finally - there are people on the IAB with fabulous social skills, 
>but I'm not one of them. If someone needs to spend time picking my 
>brain, I usually do have multiple meals open during IETF week.

I think that you are underestimating your skills. :-)  I would have 
spent that half an hour chatting with you even if you weren't an IAB member.

Regards,
-sm 


From sm@resistor.net  Sat Apr 13 03:23:22 2013
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 B211621F8733 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 03:23:22 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-jkFUSkLEWC for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 03:23:22 -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 CF9CF21F86E6 for <ietf@ietf.org>; Sat, 13 Apr 2013 03:23:21 -0700 (PDT)
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 r3DANAkP002650; Sat, 13 Apr 2013 03:23:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365848594; bh=1TV6d+Ne0i0L3S0pqIJ1tUlHrmCRgkrPZjDDTBhYBE0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4kvaS3yIuZ2DbZX13+UZATkjJWotN3zM2r3r84Pasn2LKi7rrvdxI81mHtDBSVZ5B XjoCfEwvQOCDhNITUIIh07MQQ05H3xzLIYtRIB7VOxumR42qazB2fox0UPTKkXvNG1 GtxrFPQr+rrIOFkxLu8e0qf+l2nbrhSek7wGwigI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365848594; i=@resistor.net; bh=1TV6d+Ne0i0L3S0pqIJ1tUlHrmCRgkrPZjDDTBhYBE0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZClORm7Xe55003R3B2Ro3KMK+DYwbC59/BKmTmNyDxg1bwjAp4lepDXzV8vS3bld2 t9SjMo7otcT6jC7H5UdoT123rNEpBw267nyrBXm2KQpfP+Bc4LAkWo+/XTrv1v/xy8 W9T3ucnutzBLNxvpagFMnfciWEogXNCBpV1YAT0I=
Message-Id: <6.2.5.6.2.20130413001404.0da31870@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 13 Apr 2013 03:19:21 -0700
To: Melinda Shore <melinda.shore@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <5168C159.3050004@gmail.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@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, 13 Apr 2013 10:23:22 -0000

Hi Melinda,
At 19:22 12-04-2013, Melinda Shore wrote:
>to be the best.  Pretty much every organization that applauds
>itself for its meritocratic reward structure (to the extent
>that an I* gig is a "reward") and yet only advances white
>guys says the same thing.  It is a trope, and a familiar one.

If you pick an Area Director who does not do the work the effects 
will be apparent within the area and during IESG evaluation.  If you 
pick a Working Group Chair who does not do the work the effects will 
only be visible within the working group.  The Area Director will 
probably step in and to limit damage.  If you pick an IAB members who 
does not do the work the effects will not be visible.  That applies 
for IAOC members too.

Michael Richardson commented about the "apparent bias that we are 
experiencing" [1].  The Area Directors, except for two of them, work 
for large vendors.  Is there a bias in favor of vendors? I don't 
think so; large vendors have money and can afford to provide funding 
support.  Is the problem about women being qualified and not having 
having met enough people that the person's qualifications has been 
recognized?  I don't know.

Andrw Sullivan provided a cautionary tale [2] about quotas.  My 
reason for not favoring quotas is that the entire atmosphere will be 
poisoned.  I would not try to convince anyone about that.  My opinion 
is what Andrew Sullivan mentioned; it is incredibly hard for women to 
be treated as colleagues in an environment that acts overwhelmingly 
as a male club.  An alternative is to have more women, not as tokens, 
but as persons who can make the environment less harsh.

What's missing in the discussion is how to make that happen.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg78626.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg78637.html


From arturo.servin@gmail.com  Sat Apr 13 03:45:07 2013
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 BA5A921F896D for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 03:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.77
X-Spam-Level: 
X-Spam-Status: No, score=-0.77 tagged_above=-999 required=5 tests=[AWL=-1.680,  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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Zl04OZ1kGMY for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 03:45:06 -0700 (PDT)
Received: from mail-yh0-x22b.google.com (mail-yh0-x22b.google.com [IPv6:2607:f8b0:4002:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id E350221F87B6 for <ietf@ietf.org>; Sat, 13 Apr 2013 03:45:05 -0700 (PDT)
Received: by mail-yh0-f43.google.com with SMTP id f73so532221yha.2 for <ietf@ietf.org>; Sat, 13 Apr 2013 03:45:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qfWrp1AScHWJkVbrezPGiudGCa4xnXQGo1ld6t7qkKM=; b=w8sZY1Ry29sYzj5gWgXo9wGMzreh6cjSo358qud1P8NECz+TVWIbnLjzjWITTUG+bC 7p3oQUOOka+hnZpcDGsCKqi4lHALM/tN8swCsfsrqf/LQ6ttSi92Vzo0Gz41bP3VoDMY bHE6oz1uFyKsv9qDU2kH6Uqg3wythwDm8v4QTy/ujjrJdJPLbJk2DW+4Szboq1vCE5uj 8Ar8+YmAy5XLNdDdo41bHH1aozrxdy1TQCi6JACHKUWJYFsF0vbEkKXr690pDMTI6s6h Wy+Yc+Sa9Ak+6WEH40KhzRDuTXpUvBqjVCHRyLjHsm+DJgbSsV21Ljj+lEyjFKftxI80 Sj6Q==
X-Received: by 10.236.117.170 with SMTP id j30mr7394868yhh.51.1365849905481; Sat, 13 Apr 2013 03:45:05 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (r186-48-254-213.dialup.adsl.anteldata.net.uy. [186.48.254.213]) by mx.google.com with ESMTPS id y5sm17021091yhd.3.2013.04.13.03.45.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 13 Apr 2013 03:45:04 -0700 (PDT)
Message-ID: <51693729.4010502@gmail.com>
Date: Sat, 13 Apr 2013 07:44:57 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <20130412235542.8CEDA1A6AD@ld9781.wdf.sap.corp>
In-Reply-To: <20130412235542.8CEDA1A6AD@ld9781.wdf.sap.corp>
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, 13 Apr 2013 10:45:07 -0000

On 4/12/13 8:55 PM, Martin Rex wrote:
> SM wrote:
>>
>> Ted Lemon wrote:
>>>
>>> So in fact you don't need to put some percentage of white males on 
>>> the IESG, the IAB or the IAOC to make me happy.   I want people on 
>>> these bodies who feel strongly about open standards, rough consensus 
>>> and running code.   That's the kool-aid I have drunk, and I
> 
> Me 2!
> 

	Me too, but when you have a diverse pool of people
who feel strongly about open standards, rough consensus and running code
and you choose only one category of the group, then we need to think
about how we end up in that situation.

Regards,
as

From lberger@labn.net  Sat Apr 13 05:10:23 2013
Return-Path: <lberger@labn.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 895D721F8A52 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 05:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.298
X-Spam-Level: 
X-Spam-Status: No, score=-102.298 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AMwoQ+zNCboP for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 05:10:22 -0700 (PDT)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [69.89.24.6]) by ietfa.amsl.com (Postfix) with SMTP id 4BC6F21F8A4F for <ietf@ietf.org>; Sat, 13 Apr 2013 05:10:22 -0700 (PDT)
Received: (qmail 32729 invoked by uid 0); 13 Apr 2013 12:10:00 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy9.bluehost.com with SMTP; 13 Apr 2013 12:10:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=QarikspAFmvsNySJejcaGzMTzwmkuWNzdNDIUnIXsWE=;  b=Djj3vGn7d6wc5zvl5qrevQR5HDVMH80tmgbEx80nGlV2PWfJbs/TrsfKCbRNsm9vJ4nAHWQb5IZwQJy6+g1yLx+vYjxBFXm4kvUH1gB5P15Yy6CJtSIY0FCvwCpu+yAa;
Received: from box313.bluehost.com ([69.89.31.113]:36101 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1UQzHM-0004lI-8U; Sat, 13 Apr 2013 06:10:00 -0600
Message-ID: <51694B16.4090504@labn.net>
Date: Sat, 13 Apr 2013 08:09:58 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com>
In-Reply-To: <5168C159.3050004@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.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: Sat, 13 Apr 2013 12:10:23 -0000

Melinda,
	I'm not so sure debating the merits of a specific measure has value or
not is really that helpful, and I probably just should have ignore this
small point.  Let's say some limited measure of diversity is valid, what
do we learn from it?  Is the conclusion that only one group is being
discriminated against and that the IETF needs to address this one
specific form of discrimination, or is it that the top of the IETF is
far from diverse?  If the latter, I buy it -- the IETF has a diversity
issue.

As many others have said, there are many forms of bias and
discrimination -- all of which are harmful, and only some of which have
the legal protection (in your favorite country) that they should.
Irrespective of any specific statistic, I think this discussion has
shown that there is consensus that working to eliminate bias and
discrimination *in all forms* from the IETF is worth paying attention
to.  Do you disagree, are you saying that the IETF should only/first try
to address only gender bias?

I personally think all IETF participants should have voice in this
discussion, no matter if they fall into an obviously discriminated
against group or not.  This includes the full range of participants,
even newcomers, folks who have never authored an I-D, folks who by any
measure are significant I* contributors, and even "western white guys".
IMO the exclusion of any voice is itself a manifestation of bias.

Lou

On 4/12/2013 10:22 PM, Melinda Shore wrote:
> On 4/12/13 1:26 PM, Lou Berger wrote:
>> No argument from me, I'm just asking that a comment/position/question
>> that I don't understand be substantiated. 
> 
> And I'm telling you that I think the numbers are highly suggestive
> of bias.  We can take a swing at getting a very rough handle on
> that but I'm actually not sure that we should because it appears
> to be the case that the cost of any remediation that some of us
> might want to undertake would be higher than the cost of living
> with bias in the system (this would be the considerable downside
> to consensus decision-making processes with a very large participant
> base).
> 
>>> And I don't know if you intended to or not, but what you
>>> communicated is "The best candidates are nearly always
>>> western white guys," since that's who's being selected.
>>> That's a problematic suggestion.
>>
>> I certainly, in no way, shape, or form intended such an implication.  I
>> have not idea how one could read it that way, [ ... ]
> 
> A (male) friend once said that men are no more likely to notice
> sexism than fish are to notice water.  I think that was far
> too broad but generally true.  If I think that white western
> men are being selected in disproportion to their presence in
> the candidate pool, and I do, then telling me that "we only
> choose the best" is telling me that white, western men tend
> to be the best.  Pretty much every organization that applauds
> itself for its meritocratic reward structure (to the extent
> that an I* gig is a "reward") and yet only advances white
> guys says the same thing.  It is a trope, and a familiar one.
> 
> Melinda
> 
> 
> 
> 

From Ted.Lemon@nominum.com  Sat Apr 13 05:32:25 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8BA121F85E7 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 05:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.379
X-Spam-Level: 
X-Spam-Status: No, score=-106.379 tagged_above=-999 required=5 tests=[AWL=0.220, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RyTtJ7-GWVfd for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 05:32:25 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 2F77E21F8A4E for <ietf@ietf.org>; Sat, 13 Apr 2013 05:32:25 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUWlQWZmo75YqOJjcfxpHAQAnlmqDn7yy@postini.com; Sat, 13 Apr 2013 05:32:25 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D963A1B80C2 for <ietf@ietf.org>; Sat, 13 Apr 2013 05:32:24 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D1E02190061; Sat, 13 Apr 2013 05:32:24 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sat, 13 Apr 2013 05:32:18 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbesxw5RhqwwUuIKG4LfyrlCZjR4Y8AgAAKbwCAAAcIAIAAl7OAgACT+QCAAFoBAIAAEjuA//+1+piAAHleAIAAtWaAgAAd/gA=
Date: Sat, 13 Apr 2013 12:32:18 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775144AF2@mbx-01.win.nominum.com>
References: <20130412235542.8CEDA1A6AD@ld9781.wdf.sap.corp> <51693729.4010502@gmail.com>
In-Reply-To: <51693729.4010502@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <6471B73B9F1F5B4D8964A29A992500A6@nominum.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: Sat, 13 Apr 2013 12:32:25 -0000

On Apr 13, 2013, at 6:44 AM, Arturo Servin <arturo.servin@gmail.com> wrote:
> 	Me too, but when you have a diverse pool of people
> who feel strongly about open standards, rough consensus and running code
> and you choose only one category of the group, then we need to think
> about how we end up in that situation.

Yes.   I'm not arguing that there is not a problem: I'm arguing that if the=
 problem were solved, it would not make me feel less well represented.   Th=
e point is definitely not to turn that around and suggest to those who curr=
ently do not feel well-represented that they should not=97the situations ar=
en't analogous.


From stephen.farrell@cs.tcd.ie  Sat Apr 13 05:47:00 2013
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 13B1B21F8CA1 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 05:47:00 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9jLqO2epqxqw for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 05:46:59 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3702021F8C55 for <ietf@ietf.org>; Sat, 13 Apr 2013 05:46:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C4516BE5D; Sat, 13 Apr 2013 13:46:18 +0100 (IST)
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 Y3muE2WmW4GT; Sat, 13 Apr 2013 13:46:18 +0100 (IST)
Received: from [10.87.48.4] (unknown [86.45.56.45]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 0BA45BE59; Sat, 13 Apr 2013 13:46:18 +0100 (IST)
Message-ID: <51695398.3000708@cs.tcd.ie>
Date: Sat, 13 Apr 2013 13:46:16 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net>
In-Reply-To: <51694B16.4090504@labn.net>
X-Enigmail-Version: 1.5.1
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, 13 Apr 2013 12:47:00 -0000

On 04/13/2013 01:09 PM, Lou Berger wrote:
> gender bias
...
> "western white guys".

It may be that the latter phrase is a common term in
north America, (I dunno) but fwiw it grates on me at
least.

If the issue we're talking about relates to gender,
then I think sticking to that is better and figuring
out how to make progress ought be doable even if
dissecting past or current nomcom decisions is not. I
really hope the design team folks succeed there since
its quite possible, even if may take quite a while for
success to be fully apparent.

If we're talking about many more kinds of diversity
then that's a different discussion, and IMO English
language fluency and funding are by far the most
overwhelming sources of skew. Skin colour is (I hope,
but also believe) far down the list so the "white"
bit above appears from my perspective like name
calling or something.

And of course I personally don't consider myself
"western" but Irish. I've no clue if that makes a
difference in this kind of discussion:-)

S.



From eckert@cisco.com  Sat Apr 13 05:58:51 2013
Return-Path: <eckert@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 6163321F89D8 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 05:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.155
X-Spam-Level: 
X-Spam-Status: No, score=-10.155 tagged_above=-999 required=5 tests=[AWL=-0.156, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VEOMMLXPU9nJ for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 05:58:50 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id E20D321F8842 for <ietf@ietf.org>; Sat, 13 Apr 2013 05:58:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1798; q=dns/txt; s=iport; t=1365857930; x=1367067530; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=WweATA8Qf97/zFGtyw3wjPXLL341xen4EvwfCwYCK3Q=; b=T6bhmYuzQr56q3cgegW0Szh1kvxDfvu+UcWd1gIpmhb46WD36U4/yHFg LuMldqqYlr7GlyDZesx0SSugZQnD4KtpANjAuGiNFph2RpL2BjybOuFDx dw707Ev2JPiqX4AayVAnpZtsfKR6F2YpCM1ow1kCKbPaopWUnFZj1qTHE U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsFAD1WaVGrRDoI/2dsb2JhbABQgwbCBIEGFnSCHwEBAQQ6LwEPEAsYCSUPBQ08E4gCAw6yHA2JXYxEglMHgmBhA4kDjByBYgGLdYUcgysc
X-IronPort-AV: E=Sophos;i="4.87,468,1363132800"; d="scan'208";a="75457066"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 13 Apr 2013 12:58:48 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3DCwgNh025852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Apr 2013 12:58:42 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r3DCuqUG005027;  Sat, 13 Apr 2013 05:57:07 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r3DCuqQT005025; Sat, 13 Apr 2013 05:56:52 -0700
Date: Sat, 13 Apr 2013 05:56:52 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130413125652.GA3818@cisco.com>
References: <20130412235542.8CEDA1A6AD@ld9781.wdf.sap.corp> <51693729.4010502@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775144AF2@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775144AF2@mbx-01.win.nominum.com>
User-Agent: Mutt/1.4.2.2i
Cc: Arturo Servin <arturo.servin@gmail.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: Sat, 13 Apr 2013 12:58:51 -0000

A question because my institutional memory does reach as far back:
How much was Europe represented over the decades in IETF leadership ? 

Right now for example IESG seems to have maybe at least 5
europeans (don't really know how to figure out location for all of them,
those where just the easy ones for me).   But i would expect that this
was by far not the case going back in time.

Nobody cares about "diversity" for europeans in this round of the 
discussion, but i wonder if this was equally true in the past.

Maybe this evolution would be a good example to folks without that long
reaching institutional memory to show how the IETF leadership
does pretty well  reflect the evolution of the industry. If the
industry will become more diverse, IETF will reflect this equally.
If on the other hand we try to achieve greater diversity than the
industry, then we have a real challenge on our hand. 

The concentration to fewer and larger companies in todays vs. past
leadership was mentioned in before as "bad". I think its exactly
for the same reason.


On Sat, Apr 13, 2013 at 12:32:18PM +0000, Ted Lemon wrote:
> On Apr 13, 2013, at 6:44 AM, Arturo Servin <arturo.servin@gmail.com> wrote:
> > 	Me too, but when you have a diverse pool of people
> > who feel strongly about open standards, rough consensus and running code
> > and you choose only one category of the group, then we need to think
> > about how we end up in that situation.
> 
> Yes.   I'm not arguing that there is not a problem: I'm arguing that if the problem were solved, it would not make me feel less well represented.   The point is definitely not to turn that around and suggest to those who currently do not feel well-represented that they should not?the situations aren't analogous.
> 

From john-ietf@jck.com  Sat Apr 13 06:37:48 2013
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 4F3B721F8491 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 06:37:47 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Iqd44l56N3h for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 06:37:46 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7C9F921F848D for <ietf@ietf.org>; Sat, 13 Apr 2013 06:37:46 -0700 (PDT)
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 1UR0eE-000GUl-VH; Sat, 13 Apr 2013 09:37:42 -0400
Date: Sat, 13 Apr 2013 09:37:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pat Thaler <pthaler@broadcom.com>
Subject: RE: Purpose of IESG Review
Message-ID: <43F5ACE96A13F40BE2B15494@JcK-HP8200.jck.com>
In-Reply-To: <EB9B93801780FD4CA165E0FBCB3C3E672AD2DF79@SJEXCHMB09.corp.ad.broadcom.com>
References: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com> <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.c om> <DC0F69276BCB2F0B5758CFC3@JcK-HP8200.jck.com> <EB9B93801780FD4CA165E0FBCB3C3E672AD2DF79@SJEXCHMB09.corp.ad.broadcom.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 <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: Sat, 13 Apr 2013 13:37:48 -0000

--On Friday, April 12, 2013 23:50 +0000 Pat Thaler
<pthaler@broadcom.com> wrote:

> +1 on for John's response.
>  
> I will argue with my manager if I think they are wrong and
> I've gotten positive results from giving managers feedback on
> their performance. Of course, disagreeing with management
> won't always get the decision changed, but I've never felt I
> lost anything by raising the discussion.

I should probably have added that, for some specific classes of
issues and for those who are members of ACM, IEEE, and several
other professional societies, failure to do so is a violation of
the standards of professional ethics to which they have agreed.
Then again, so is discriminatory behavior.  See, e.g.,
http://www.acm.org/about/code-of-ethics and
http://www.ieee.org/about/corporate/governance/p7-8.html .

> I've also seen some bad decisions made when someone had good
> reasons why a decision was wrong but didn't surface them
> because they didn't feel they could argue with management.

Yep.  I didn't say it always worked out well or that all
managers are competent and secure enough to tolerate feedback.  

> IETF participant to IETF leadership isn't the same as employee
> to manager of course. We are all volunteers collaborating to
> get good results and if we feel there is a process problem we
> can discuss it. IETF formalizes this by having open mike
> sessions for example. 

And appeal procedures as an integral part of the decision-making
process.  I've said this before, but I believe we don't use
those enough for "normal" situations where issues and tradeoffs
have not been considered properly.  That lack of use has led to
an impression that appeals were the tools and refuge of crazies
and trolls, which was certainly never the intent.

> A thread on whether there is a problem with the IESG review
> process is appropriate, IMO.

Oh, indeed.  And, at a slightly more indirect level, I believe
that the ways in which carefully thought-out constructive
discussion and suggestions have sometimes been belittled and
suppressed lies at the root of some of our larger problems.
Unfortunately, noise from crazies, people who strongly push
suggestions or comments without bothering to try to understand
the actual situations or history, a few people who think that
making IETF more like some other body would automatically make
it better, fear of change by those in leadership positions, and
miscellaneous trolls has made those more constructive
conversations difficult as well.

    john


From rpelletier@isoc.org  Sat Apr 13 08:18:34 2013
Return-Path: <rpelletier@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 4E08521F86C5 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 08:18:34 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XgzIosgMXUsB for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 08:18:33 -0700 (PDT)
Received: from smtp142.ord.emailsrvr.com (smtp142.ord.emailsrvr.com [173.203.6.142]) by ietfa.amsl.com (Postfix) with ESMTP id A724821F84E0 for <ietf@ietf.org>; Sat, 13 Apr 2013 08:18:33 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp10.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id 2E57E370098; Sat, 13 Apr 2013 11:18:33 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp10.relay.ord1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id B408237008A;  Sat, 13 Apr 2013 11:18:32 -0400 (EDT)
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51695398.3000708@cs.tcd.ie>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org>
X-Mailer: iPhone Mail (10B329)
From: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
Date: Sat, 13 Apr 2013 11:18:29 -0400
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
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, 13 Apr 2013 15:18:34 -0000

On Apr 13, 2013, at 8:46 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wro=
te:

>=20
>=20
> On 04/13/2013 01:09 PM, Lou Berger wrote:
>> gender bias
> ...
>> "western white guys".
>=20
> It may be that the latter phrase is a common term in
> north America, (I dunno) but fwiw it grates on me at
> least.
>=20
> If the issue we're talking about relates to gender,

That's the question:

Optional question:
Check the block. Male/Female

Ray



> then I think sticking to that is better and figuring
> out how to make progress ought be doable even if
> dissecting past or current nomcom decisions is not. I
> really hope the design team folks succeed there since
> its quite possible, even if may take quite a while for
> success to be fully apparent.
>=20
> If we're talking about many more kinds of diversity
> then that's a different discussion, and IMO English
> language fluency and funding are by far the most
> overwhelming sources of skew. Skin colour is (I hope,
> but also believe) far down the list so the "white"
> bit above appears from my perspective like name
> calling or something.
>=20
> And of course I personally don't consider myself
> "western" but Irish. I've no clue if that makes a
> difference in this kind of discussion:-)
>=20
> S.
>=20
>=20

From lear@cisco.com  Sat Apr 13 08:48:22 2013
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 1F3FD21F86CE; Sat, 13 Apr 2013 08:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.329
X-Spam-Level: 
X-Spam-Status: No, score=-110.329 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id saWs31ZWy-E9; Sat, 13 Apr 2013 08:48:21 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0A1C021F86C3; Sat, 13 Apr 2013 08:48:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=850; q=dns/txt; s=iport; t=1365868101; x=1367077701; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=LtldLYIh69OkCjgm8X+rC0O2U5529I/0yu3tq0/W7GQ=; b=GbZ3sDQUppKoD2xuIcHS8e7mhDV76ENmB9TnX14JFhStCWauKBcZsSLL 5cPyj0FQz9CT5O62xRGMfzKHhGLTOrFZ6wmRh53saL/xE1+G8WBCWPwSR TQOUAHt+bcifWzSEbl/kqoOM12tZ0YL3wjfon2xj73+82mUwnIhHSNTku w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAOl8aVGQ/khL/2dsb2JhbABQgwaDZr4dgQQWdIIfAQEBBCNIDQEQCxgCAgUWCwICCQMCAQIBKxoGDQEHAQGIEKkPkhSBI410B4IugRMDlwWREYMNOg
X-IronPort-AV: E=Sophos;i="4.87,468,1363132800"; d="scan'208";a="81965878"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 13 Apr 2013 15:48:18 +0000
Received: from mctiny.local ([10.61.194.164]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r3DFmFi0027290 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Apr 2013 15:48:16 GMT
Message-ID: <51697E3F.7010404@cisco.com>
Date: Sat, 13 Apr 2013 17:48:15 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <6.2.5.6.2.20130411140916.0c412c70@resistor.net> <51681C7C.7050408@wonderhamster.org> <6.2.5.6.2.20130412074639.0ae536b0@resistor.net> <8D23D4052ABE7A4490E77B1A012B630775143E80@mbx-01.win.nominum.com> <6.2.5.6.2.20130412150127.0d2db9d0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130412150127.0d2db9d0@resistor.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: iaoc@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, 13 Apr 2013 15:48:22 -0000

SM,

Since you asked,  the IAB spoke on this subject as one voice last year
when the OpenStand RFC was released. 

As a current IAB member, and speaking for myself...

On 4/13/13 1:32 AM, SM wrote:
>
> Thomas Narten mentioned that: "we have the tendency to pick the people
> we know and trust, which is understandable".  How many IAB members
> feel strongly about open standards, rough consensus and running code? 
> To know the answer I would have to actually know the IAB members.

Well, say what you will about whether you believe me, but all THREE of
those are important to me, personally.  No standards organization
produces perfect results, but you have far less chance of spotting a
problem if you hide your processes from the public, reduce the voice of
experts, and don't pay attention to operational experience.

Eliot

From klensin@jck.com  Sat Apr 13 09:15:53 2013
Return-Path: <klensin@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 11FE721F884A for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 09:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.769
X-Spam-Level: 
X-Spam-Status: No, score=-2.769 tagged_above=-999 required=5 tests=[AWL=-0.170, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aR1kPPifQLD for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 09:15:52 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 28C6521F8825 for <ietf@ietf.org>; Sat, 13 Apr 2013 09:15:42 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1UR373-000H42-Jf; Sat, 13 Apr 2013 12:15:37 -0400
Date: Sat, 13 Apr 2013 12:15:22 -0400
From: John C Klensin <klensin@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <0145DF6A724D1CA5E664213E@JcK-HP8200.jck.com>
In-Reply-To: <20130413033755.GC5403@mx1.yitter.info>
References: <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com>	<20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net>	<5168C159.3050004@gmail.com> <20130413033755.GC5403@mx1.yitter.info>
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: Sat, 13 Apr 2013 16:15:53 -0000

--On Friday, April 12, 2013 23:37 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> The only lesson I really learned from that experience is that
> it is incredibly hard for women[1] to be treated as adult
> colleagues in an environment that acts overwhelmingly as a
> white male club. 

JJ Thompson, Grace Anscomb, etc., notwithstanding.  Similarly,
Grace Hopper, Jean Sammet, Jane Thompson, Martha Steenstrup,
Deborah Estrin, Sally Floyd, etc.

That doesn't change your point other than to identify a
different fallacy in the "girl-philosophy" hypothesis and its
computer science / networking analogies.   If you haven't heard
of some of the above, it demonstrations a slightly different
point.   It may also suggest that there is an area in which the
IETF is absolutely non-discriminatory: there is no evidence
that the IETF has been any more effective in driving, e.g.,
Martha or Deborah out than with Crowcroft, Elz, Clark, Chapin,
...

    :-(
    john






From melinda.shore@gmail.com  Sat Apr 13 09:57:22 2013
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 41FF621F8B07 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 09:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.534
X-Spam-Level: 
X-Spam-Status: No, score=-1.534 tagged_above=-999 required=5 tests=[AWL=-1.565, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ll+YeNGEoF00 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 09:57:21 -0700 (PDT)
Received: from mail-da0-x22a.google.com (mail-da0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id CF49521F8AE8 for <ietf@ietf.org>; Sat, 13 Apr 2013 09:57:14 -0700 (PDT)
Received: by mail-da0-f42.google.com with SMTP id n15so1531243dad.15 for <ietf@ietf.org>; Sat, 13 Apr 2013 09:57:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=i9izLmr1AGm6gLmdkrD7QE/c8e3Dg6jbFzlZSOpw7tw=; b=00mZfLcSofbx1M7LyVEkv8TsXTMoA8cS2LVq6hROM/bV/67mMrvLlW3MjU/6B3mxFP +/6RrfxjsqioowYuXvOSgVcrSLM2V/YvE40MkjmTPWIhymDaUk2qUjO/CE+wJnT6vRvN 38jGHpivyN6HH4BwvgAVPbjNEZlzd3PRp068L+vV0jRY/YbcQtWFvVe+osivs+hjGSKf JcWyK6YSQs9xbTfm0KodgA8KVRFmo3A4ufl2e848QP7NYi8otepTzZsZwVuh4oGcqIN4 eT09UvFyB5sPbmNwR6xZo4EjojKdv1rJJfIsDjL5xv5gJhEW2lqg8ehPPkctVy41hLMV 1n3Q==
X-Received: by 10.68.251.194 with SMTP id zm2mr20217379pbc.81.1365872233483; Sat, 13 Apr 2013 09:57:13 -0700 (PDT)
Received: from spandex.local (66-230-88-244-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.88.244]) by mx.google.com with ESMTPS id vk7sm13176862pbc.41.2013.04.13.09.57.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 13 Apr 2013 09:57:12 -0700 (PDT)
Message-ID: <51698E65.30105@gmail.com>
Date: Sat, 13 Apr 2013 08:57:09 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Lou Berger <lberger@labn.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net>
In-Reply-To: <51694B16.4090504@labn.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, 13 Apr 2013 16:57:22 -0000

On 4/13/13 4:09 AM, Lou Berger wrote:
> Do you disagree, are you saying that the IETF should only/first try
> to address only gender bias?

Clearly not, Lou.  For one thing, I've repeatedly said that
we're underperforming on a number of axes - repeatedly, and
for another I've said some number of times that I don't think
that we can do anything about gender bias and that the costs
of addressing it given our decision-making structures
combined with the very vocal opposition to even looking at
the question, let alone addressing it.  Experience suggests
that gender bias is one of the most deeply-rooted, difficult-
to-deal-with bias problems.  The IETF punts on a large number
of hard technical problems and it would not be inconsistent
to punt on a hard social problem.

So no, I'm not saying that at all, Lou.  I thought I was
pretty clear about that.

Melinda


From mstjohns@comcast.net  Sat Apr 13 10:05:55 2013
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 576FB21F8B9B for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 10:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cafqpi-XdLCF for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 10:05:54 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id D569721F8B61 for <ietf@ietf.org>; Sat, 13 Apr 2013 10:05:53 -0700 (PDT)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by QMTA11.westchester.pa.mail.comcast.net with comcast id PUtl1l0030SCNGk5BV5twz; Sat, 13 Apr 2013 17:05:53 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta09.westchester.pa.mail.comcast.net with comcast id PV5s1l00S2kB7pQ3VV5sbs; Sat, 13 Apr 2013 17:05:53 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sat, 13 Apr 2013 13:05:57 -0400
To: John C Klensin <klensin@jck.com>, Andrew Sullivan <ajs@anvilwalrusden.com>,ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <0145DF6A724D1CA5E664213E@JcK-HP8200.jck.com>
References: <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <20130413033755.GC5403@mx1.yitter.info> <0145DF6A724D1CA5E664213E@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1365872753; bh=/Vl1JpD3vIG67MJWqzqyCa7kh0Qjr1PdJBPrX71JRG0=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=NFGHC0LtjZ/0jXi7hmHVDVixz20LJhNeO2cQhoEKLgVV6fOzhaDj/pCKUqlN2GXJi kl0O8RB5eB7YiPrMFZ/1UQTHSJtsYpB33uGANkgAhUiN2luMf2M6iFmDwohmPb9uzi Pprj/mYZdB81YdZp1tfWgR+V4f/mxLjpTdh870dFnvRDB/jR27k4G/eI7ALw9Cv1pG 5fsAqddn/fFAL1MA/zF3e9kW4gj5K+/2d3uf32/0/BTlPoSzgpScCguBN/BWmKcsP4 5qlYO5gvWpRD1UL0WxdpVlFd/I7Rs0UAyhbuBXapPk2d7Ak2iSpEPsJvtGKGg+zSVB cF7C10hzNOtjg==
Message-Id: <20130413170553.D569721F8B61@ietfa.amsl.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, 13 Apr 2013 17:05:55 -0000

At 12:15 PM 4/13/2013, John C Klensin wrote:


>--On Friday, April 12, 2013 23:37 -0400 Andrew Sullivan
><ajs@anvilwalrusden.com> wrote:
>
>> The only lesson I really learned from that experience is that
>> it is incredibly hard for women[1] to be treated as adult
>> colleagues in an environment that acts overwhelmingly as a
>> white male club. 
>
>JJ Thompson, Grace Anscomb, etc., notwithstanding.  Similarly,
>Grace Hopper, Jean Sammet, Jane Thompson, Martha Steenstrup,
>Deborah Estrin, Sally Floyd, etc.

And to confuse this even more, what was most important about Martha, Debbie and Sally with respect to the health of the IETF were their presenence in the academic and research space, not so much their gender except as possibly role models for new female attendees.  

Maybe what we do is ask some of the large network companies to fund a few research fellowships on topics that might be of interest to the IETF in the 3-5 year time frame for post-doc types?


>That doesn't change your point other than to identify a
>different fallacy in the "girl-philosophy" hypothesis and its
>computer science / networking analogies.   If you haven't heard
>of some of the above, it demonstrations a slightly different
>point.   It may also suggest that there is an area in which the
>IETF is absolutely non-discriminatory: there is no evidence
>that the IETF has been any more effective in driving, e.g.,
>Martha or Deborah out than with Crowcroft, Elz, Clark, Chapin,
>...
>
>    :-(
>    john



From lberger@labn.net  Sat Apr 13 10:17:21 2013
Return-Path: <lberger@labn.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 9480021F86B7 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 10:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.296
X-Spam-Level: 
X-Spam-Status: No, score=-102.296 tagged_above=-999 required=5 tests=[AWL=-0.031, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oa-PUddTRsYv for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 10:17:21 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id 070CE21F86A8 for <ietf@ietf.org>; Sat, 13 Apr 2013 10:17:20 -0700 (PDT)
Received: (qmail 23459 invoked by uid 0); 13 Apr 2013 17:16:59 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy7.bluehost.com with SMTP; 13 Apr 2013 17:16:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject:References:In-Reply-To:Message-ID:Date:CC:To:From; bh=KqsIrfjLudPUv4ad2bDoV2W2oh6ct7FxurNbH0iSTnE=;  b=2h7zNq6ROLkhuRW7VZ4m7tOZg08cVJMybR+T8IvUZr25HCJYHE/lugS03vYgyKOvU6edeEqHrW5C9y1jZ78WZeV/gYKYfeJi0/fVF6SMwblgbzUFkqtNgbJM1mFRuzbM;
Received: from box313.bluehost.com ([69.89.31.113]:56717 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1UR44R-000286-15; Sat, 13 Apr 2013 11:16:59 -0600
From: Lou Berger <lberger@labn.net>
To: Melinda Shore <melinda.shore@gmail.com>
Date: Sat, 13 Apr 2013 13:16:56 -0400
Message-ID: <13e04665527.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <51698E65.30105@gmail.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51698E65.30105@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 AquaMail/1.2.3.4 (build: 2100270)
Subject: Re: IETF Diversity Question on Berlin Registration?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.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: Sat, 13 Apr 2013 17:17:21 -0000

On April 13, 2013 12:57:09 PM Melinda Shore <melinda.shore@gmail.com> wrote:
> On 4/13/13 4:09 AM, Lou Berger wrote:
> > Do you disagree, are you saying that the IETF should only/first try
> > to address only gender bias?
>
> Clearly not, Lou.

Great. Glad to hear we agree.  That said, some may prefer to focus on just 
gender (or some other form of) bias first, and I wouldn't fault them for 
that...

Lou



From stephen.farrell@cs.tcd.ie  Sat Apr 13 10:33:15 2013
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 0EE7C21F8A53 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 10:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ZT-GW2alHLI for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 10:33:13 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id ADADC21F8654 for <ietf@ietf.org>; Sat, 13 Apr 2013 10:33:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7EFC6BE62; Sat, 13 Apr 2013 18:32:46 +0100 (IST)
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 t1sIhI+THH5J; Sat, 13 Apr 2013 18:32:45 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.45.56.45]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 414ECBE6F; Sat, 13 Apr 2013 18:32:45 +0100 (IST)
References: <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <20130413033755.GC5403@mx1.yitter.info> <0145DF6A724D1CA5E664213E@JcK-HP8200.jck.com> <20130413170553.D569721F8B61@ietfa.amsl.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20130413170553.D569721F8B61@ietfa.amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BFDB67F-13C7-4043-A51C-06BA30DE2F8D@cs.tcd.ie>
X-Mailer: iPhone Mail (10B329)
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: IETF Diversity Question on Berlin Registration?
Date: Sat, 13 Apr 2013 18:32:42 +0100
To: Michael StJohns <mstjohns@comcast.net>
Cc: John C Klensin <klensin@jck.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: Sat, 13 Apr 2013 17:33:15 -0000

On 13 Apr 2013, at 18:05, Michael StJohns <mstjohns@comcast.net> wrote:

> Maybe what we do is ask some of the large network companies to fund a few r=
esearch fellowships on topics that might be of interest to the IETF in the 3=
-5 year time frame for post-doc types?

They actually do that already. More of would be welcomed of course.

But there's no emphasis on grant holders coming to the IETF. I think that'd b=
e a fine thing for the grant-givers to strongly encourage since its not on m=
ost grant holders radar. (Grant-givers can't require it btw and get their ta=
x back in some places as I understand it - awards have to have no strings at=
tached.)

But throwing in some dosh for a few IETF meetings is something some people r=
eading this could maybe make happen.

S=

From stefan@aaa-sec.com  Sat Apr 13 10:35:34 2013
Return-Path: <stefan@aaa-sec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 147B621F8E5A for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 10:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.963
X-Spam-Level: 
X-Spam-Status: No, score=-101.963 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599, HELO_EQ_SE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZyN82732WE9U for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 10:35:32 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by ietfa.amsl.com (Postfix) with ESMTP id 8871A21F8AE8 for <ietf@ietf.org>; Sat, 13 Apr 2013 10:35:32 -0700 (PDT)
Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id E19C9209B11C for <ietf@ietf.org>; Sat, 13 Apr 2013 19:35:30 +0200 (CEST)
X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se
Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1OrMzE787l2R for <ietf@ietf.org>; Sat, 13 Apr 2013 19:35:30 +0200 (CEST)
Received: from s327.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id 1B461209B11E for <ietf@ietf.org>; Sat, 13 Apr 2013 19:35:30 +0200 (CEST)
Received: (qmail 39895 invoked from network); 13 Apr 2013 17:35:29 -0000
Received: from gw.aaa-sec.ideon.se (HELO [192.168.1.203]) (stefan@fiddler.nu@[85.235.7.89]) (envelope-sender <stefan@aaa-sec.com>) by s327.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <piyush@ditenity.com>; 13 Apr 2013 17:35:29 -0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Sat, 13 Apr 2013 19:35:25 +0200
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
From: Stefan Santesson <stefan@aaa-sec.com>
To: Piyush Jain <piyush@ditenity.com>, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>
Message-ID: <CD8F5E1F.60C5A%stefan@aaa-sec.com>
Thread-Topic: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
In-Reply-To: <007d01ce3867$260e4760$722ad620$@ditenity.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: pkix@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, 13 Apr 2013 17:35:34 -0000

On 4/13/13 6:51 PM, "Piyush Jain" <piyush@ditenity.com> wrote:

>
>> An extension may differentiate which serial number that results in a
>> "revoked" response, that is actually issued and revoked, or if there is
>any
>> other particular reason for responding "revoked".
>> In my universe a syntactically valid serial number can only be good,
>revoked
>> or non-issued. But expressing this in general terms anyway.
>
>[Piyush]  From an RP's perspective finding status of serial numbers serves
>no purpose unless they can associate that serial number with a
>certificate.

Absolutely, that is the client's perspective of this.

>When an OCSP client extracts the serial number from a certificate and
>sends
>it the responder to determine the status, it is acting under a very
>important assumption - the CA has issued that certificate and that it has
>issued only one certificate with that serial.

Absolutely

>If you say that this assumption is invalid, your trichotomy of serial
>status
>is not mutually exclusive any more. Same serial can now be associated
>with a
>good, revoked and non-issued status.

I didn't say that. I said it can "only be good, revoked or non-issued"

Notice the difference? My sentence contains the word "or", yours the word
"and".

These are the three possible states of a serial number. It must always be
in ONE of these states.

>And also the client cannot be sure if
>the CA delegated responder's certificate is good or non-issued. This
>renders
>OCSP completely useless.

I did not talk about responder certificates.


>
>> 
>> So with the help of extensions, a responder can provide both white and
>black
>> list data.
>
>[Piyush] May be you are right. But I doubt that you want a discussion on
>feasibility/security implications of this, otherwise it would've been a
>stated goal of 2560bis and would have been captured in the abstract.

If new extensions are defined, then the RFC defining these extensions will
discuss relevant security implications related to those extensions.

>I tried to think ahead but I cannot figure out a way to communicate the
>white listed status of a CA delegated responder to the client without
>avoiding circular logic.

I can.

The "good" response provides by default a minimum level of positive
confirmation.
But it is also make clear that an extensions allows "good" to say more, as
long as it fits within that default statement of "good".

A white list falls within that basic statement.
That is, the serial numbers that will return "good" in a "white-list"
scenario would also return "good" if the responder provided default OCSP
status information.
White listing will simply reduce the number of "good" status to occasions
where it represent a known existing certificate.



>
>I completely fail to see why revoked for non-issued is a pre-requisite for
>future extensions that can be used to provide white-list data (if it is
>even
>possible under CA delegated responder trust model).

I'll try again. It is only possible to reduce the "good" status responses
to white listed certificates if another suitable status can be return for
any other requested serial number.
That is, the combined set of revoked and non-issued serial numbers that
does not belong in the while list.

Responding "unknown" may not be desirable, as it is likely to cause the
client to try another source.

With the update of RFC2560bis it is now being made clear (in the
definition of "revoked"), that it is conformant to respond "revoked" to
both revoked and "non-issued" certificates, while before, that could be
questioned as a stretch of semantics.

So yes indeed, the updates makes it easy to take the next step into a
white-list OCSP responder by adding a suitable extension.
Of course, only those understanding the new extension will know that it is
a "white list" response.

/Stefan



From mcr@sandelman.ca  Sat Apr 13 11:02:22 2013
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 944F821F8D46 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 11:02:22 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D9APesQrxEvZ for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 11:02:22 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id D60A321F8D05 for <ietf@ietf.org>; Sat, 13 Apr 2013 11:02:21 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E852E2016D for <ietf@ietf.org>; Sat, 13 Apr 2013 14:12:06 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 27EBA638F7; Sat, 13 Apr 2013 14:01:55 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 143A9638E8 for <ietf@ietf.org>; Sat, 13 Apr 2013 14:01:55 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <6.2.5.6.2.20130413001404.0da31870@resistor.net>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <6.2.5.6.2.20130413001404.0da31870@resistor.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sat, 13 Apr 2013 14:01:55 -0400
Message-ID: <28010.1365876115@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: Sat, 13 Apr 2013 18:02:22 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "SM" =3D=3D SM  <sm@resistor.net> writes:
    SM> Michael Richardson commented about the "apparent bias that we are
    SM> experiencing" [1].  The Area Directors, except for two of them,
    SM> work for large vendors.  Is there a bias in favor of vendors? I
    SM> don't think so; large vendors have money and can afford to
    SM> provide funding support.  Is the problem=20
=20
I believe that there is a bias in favour of large vendors.
It's not that the nomcom picks people from large vendors, but rather
than it only gets candidates with support, and large vendors find it
much easier to support people.

AS A RESULT, we have 30+ years of the promotion and retention (not getting
laid off..) of people from those large vendors as well.=20=20

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUWmdkoqHRg3pndX9AQI+8wP/f7AXp1m5Qamg2LYSJxohObh1LktcgmJC
HUjVdlcs0gY3PFfdcjOlOIcAe8jJTghSKhq/JOfYg3bm0faU5MUlVX4Ceerblhnt
NfsoAUmVTyixuIW2C29gpuTYbNZgDNiZV3d3i/kpzvca16ReLIpPHlkxc5biqJ8C
mIMtU6gSzlw=
=mo0i
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Sat Apr 13 11:11:28 2013
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 1E32521F8D5F for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 11:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[AWL=0.288,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MFk3dS8RMzWq for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 11:11:27 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 7D97521F8D2C for <ietf@ietf.org>; Sat, 13 Apr 2013 11:11:27 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0A94120171 for <ietf@ietf.org>; Sat, 13 Apr 2013 14:21:18 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 29900638F7; Sat, 13 Apr 2013 14:11:06 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 19A65638E8 for <ietf@ietf.org>; Sat, 13 Apr 2013 14:11:06 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <28010.1365876115@sandelman.ca>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <6.2.5.6.2.20130413001404.0da31870@resistor.net> <28010.1365876115@sandelman.ca>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sat, 13 Apr 2013 14:11:06 -0400
Message-ID: <29733.1365876666@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: Sat, 13 Apr 2013 18:11:28 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Michael" =3D=3D Michael Richardson <mcr+ietf@sandelman.ca> writes:
    Michael> AS A RESULT, we have 30+ years of the promotion and
    Michael> retention (not getting=20
    Michael> laid off..) of people from those large vendors as well.=20=20

I missed a few words there.

As a result of the fact that we have representation mostly from large
vendors, (some of which did grow from nothing, mind you), there are the
various set of biases that have been inherent in the industry for 30
years in who gets support.=20=20=20=20

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUWmfuoqHRg3pndX9AQKTNQP9Fcfz8CnWL9HGcHtUMsE+bLNNAhzV0A10
FAPmVYHtMbDhhsRJNMPYjdUsMABlUZByERxM3Tokmd0pQ39FIp0hcGAsW2Jal7Mn
6nBphsxKVQDJBwyvY8TH+6ejTO6r/8MP9fQub41L7W7J/QS/HXD1+3L3dvsiWER3
VGlxO/qYl6A=
=KMkG
-----END PGP SIGNATURE-----
--=-=-=--

From sm@resistor.net  Sat Apr 13 11:28:46 2013
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 02DEF21F892B; Sat, 13 Apr 2013 11:28:46 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aphfr6lTKoZg; Sat, 13 Apr 2013 11:28:45 -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 72A6E21F86A8; Sat, 13 Apr 2013 11:28:45 -0700 (PDT)
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 r3DISaRK005674; Sat, 13 Apr 2013 11:28:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365877722; bh=34wcuvIT7kPifaKlV3MBxB6v8kH2C3x1MQl6qDBu2es=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hRCvo7AaVY73oVV0J9KeGvHxChCy2DDRr5N15hy49VEmqZs0zuLoxChJEmpeOyG6h VT9oNbzhAJ3Bw0mkFvykkJyR9Uf1ZZ7XMgK2Ieq7PtCpRDVh+/DO3jpdtT7Nh0imp3 yqEbba0pVVBY+67BoOrHvktMmZCf2ZGcyZ1eI66E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365877722; i=@resistor.net; bh=34wcuvIT7kPifaKlV3MBxB6v8kH2C3x1MQl6qDBu2es=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KdIabkmx0vi2bpkxtmtJTu/T+gSnKZey4TBkrHnfYx23ES0t3BGVff7NJq44xbdGc VZqEtEEcGS7wSYvK/1Ol/LdLxDXuwglYQnOJUqYUv4q/qasFXohG/sYNhyX4WX1J7e A8OX/kuEnXrL7731MyMQlHu7WS7JCAxHIno6te/M=
Message-Id: <6.2.5.6.2.20130413094153.0d70f9f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 13 Apr 2013 11:22:24 -0700
To: Eliot Lear <lear@cisco.com>
From: SM <sm@resistor.net>
Subject: Open standards (was: IETF Diversity Question on Berlin Registration?)
In-Reply-To: <51697E3F.7010404@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <6.2.5.6.2.20130411140916.0c412c70@resistor.net> <51681C7C.7050408@wonderhamster.org> <6.2.5.6.2.20130412074639.0ae536b0@resistor.net> <8D23D4052ABE7A4490E77B1A012B630775143E80@mbx-01.win.nominum.com> <6.2.5.6.2.20130412150127.0d2db9d0@resistor.net> <51697E3F.7010404@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iaoc@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, 13 Apr 2013 18:28:46 -0000

Hi Eliot,
At 08:48 13-04-2013, Eliot Lear wrote:
>Since you asked,  the IAB spoke on this subject as one voice last year
>when the OpenStand RFC was released.

I was actually not asking the question.

>Well, say what you will about whether you believe me, but all THREE of

I believe you.

The text which led to this message is: "whether these interests 
reflect those of the larger Internet communities".  That's not 
related to the initial topic (of diversity).

Regards,
-sm 


From sm@resistor.net  Sat Apr 13 12:45:23 2013
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 2D6BD21F8E62 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 12:45:23 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6r7FE9SILER for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 12:45:22 -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 8AE9921F8E6D for <ietf@ietf.org>; Sat, 13 Apr 2013 12:45:22 -0700 (PDT)
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 r3DJjGLF010930; Sat, 13 Apr 2013 12:45:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1365882321; bh=tUX2fd0oXXFZp/EWIlu+f4v2/n/n9xd+aAyKm0Z9qw4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VKHHO6v3G6UvvSiOnVMJamvphROEgj/y3/9OKSEPsbiCjDFLD9EYtbNR+hhJMOKUW wzNs2Je1bP0VKI+Nmndfbaqe8vE7n8eBEk5ja9OG1tQVIOtJG8K4x755gUuRs+IGnb bpZVJdKaRoabvX81OBpc6qC6zr0KCtQbuvKaigFA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1365882321; i=@resistor.net; bh=tUX2fd0oXXFZp/EWIlu+f4v2/n/n9xd+aAyKm0Z9qw4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=g0pM17DDi8l/cuLPX8O67NF9/QtQfNrFM9F/S3+xCYaTVsbLhf2ddu3siFfuKbp8j f/kd/2KclYhrMnIpppkHFAJlGd+r3rrT78s5G90a0g5rBqzvDYYYCas7q+IlT6AOhm DEO2g8NPRdeHm4VZnQdj2IDvEUxCpTJLcv1UA9A0=
Message-Id: <6.2.5.6.2.20130413112948.0d711398@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 13 Apr 2013 12:32:27 -0700
To: Michael Richardson <mcr+ietf@sandelman.ca>
From: SM <sm@resistor.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <28010.1365876115@sandelman.ca>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <6.2.5.6.2.20130413001404.0da31870@resistor.net> <28010.1365876115@sandelman.ca>
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, 13 Apr 2013 19:45:23 -0000

Hi Michael,
At 11:01 13-04-2013, Michael Richardson wrote:
>AS A RESULT, we have 30+ years of the promotion and retention (not getting
>laid off..) of people from those large vendors as well.

This is a variation of the old boys club.  Let's say that there are 
two candidates.  Candidate A has 20 years of IETF 
experience.  Candidate B has 5 years of IETF experience.  If the 
choice is about choosing the best Candidate A will always be selected.

The following was written ten years ago:

   "The IETF appears to have created a 'ruling class' system which tends
    to re-select the same leaders from a limited pool of people who have
    proved competent and committed in the past."

   "Newcomers to the organization and others outside the 'ruling class'
    are reluctant to challenge the apparent authority of the extended
    'ruling class' during debates and consequently influence remains
    concentrated in a relatively small group of people.  This
    reluctance may also be exacerbated if participants come from a
    different cultural background than the dominant one."

NomCom rejected kings and presidents and created a ruling class instead. :-)

Regards,
-sm   


From ajs@anvilwalrusden.com  Sat Apr 13 15:03:34 2013
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 51CC421F8E49 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 15:03:34 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fen-25zbpN+s for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 15:03:33 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id CD12321F863C for <ietf@ietf.org>; Sat, 13 Apr 2013 15:03:33 -0700 (PDT)
Received: from mx1.yitter.info (li440-116.members.linode.com [50.116.54.116]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 09B888A031 for <ietf@ietf.org>; Sat, 13 Apr 2013 22:03:33 +0000 (UTC)
Date: Sat, 13 Apr 2013 18:03:30 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130413220330.GF7832@mx1.yitter.info>
References: <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <20130413033755.GC5403@mx1.yitter.info> <0145DF6A724D1CA5E664213E@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0145DF6A724D1CA5E664213E@JcK-HP8200.jck.com>
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: Sat, 13 Apr 2013 22:03:34 -0000

On Sat, Apr 13, 2013 at 12:15:22PM -0400, John C Klensin wrote:
> 
> JJ Thompson, Grace Anscomb, etc., notwithstanding.  Similarly,
> Grace Hopper, Jean Sammet, Jane Thompson, Martha Steenstrup,
> Deborah Estrin, Sally Floyd, etc.

I think we're in agreement, but just to emphasise: I have no idea what
the experiences of any of these were like, but I don't think
it's relevant that we can name some successful superstars.  My
point was that it is _difficult_, not that it's impossible.

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From stefan@aaa-sec.com  Sat Apr 13 16:24:16 2013
Return-Path: <stefan@aaa-sec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD96F21F8B08 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 16:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.996
X-Spam-Level: 
X-Spam-Status: No, score=-101.996 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599, HELO_EQ_SE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y59+G1B4IfW3 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 16:24:16 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by ietfa.amsl.com (Postfix) with ESMTP id DDD7B21F8825 for <ietf@ietf.org>; Sat, 13 Apr 2013 16:24:15 -0700 (PDT)
Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id 2A38520A0BE3 for <ietf@ietf.org>; Sun, 14 Apr 2013 01:24:14 +0200 (CEST)
X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se
Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id wKkMY6JvD5uS for <ietf@ietf.org>; Sun, 14 Apr 2013 01:24:13 +0200 (CEST)
Received: from s327.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id B071C20A0BE7 for <ietf@ietf.org>; Sun, 14 Apr 2013 01:24:13 +0200 (CEST)
Received: (qmail 28479 invoked from network); 13 Apr 2013 23:24:13 -0000
Received: from gw.aaa-sec.ideon.se (HELO [192.168.1.203]) (stefan@fiddler.nu@[85.235.7.89]) (envelope-sender <stefan@aaa-sec.com>) by s327.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <piyush@ditenity.com>; 13 Apr 2013 23:24:13 -0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Sun, 14 Apr 2013 01:24:09 +0200
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
From: Stefan Santesson <stefan@aaa-sec.com>
To: Piyush Jain <piyush@ditenity.com>, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>
Message-ID: <CD8FB284.60CB7%stefan@aaa-sec.com>
Thread-Topic: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
In-Reply-To: <008201ce3878$a699c790$f3cd56b0$@ditenity.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: pkix@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, 13 Apr 2013 23:24:17 -0000

On 4/13/13 8:56 PM, "Piyush Jain" <piyush@ditenity.com> wrote:

>> >[Piyush]  From an RP's perspective finding status of serial numbers
>> >serves no purpose unless they can associate that serial number with a
>> >certificate.
>> 
>> Absolutely, that is the client's perspective of this.
>
>Great. We agree
>> 
>> >When an OCSP client extracts the serial number from a certificate and
>> >sends it the responder to determine the status, it is acting under a
>> >very important assumption - the CA has issued that certificate and that
>> >it has issued only one certificate with that serial.
>> 
>> Absolutely
>Great. We agree.  
>Let me reiterate -OCSP client extracts the serial number assuming that the
>CA issued the certificate and issued only one certificate with that serial
>number. So why do we need the responder to return non-issued for the same
>certificate?

Because of your lack of fantasy :)
Shift your focus from the client to the server.

A client have control over never asking for a non-issued certificate,
unless the CA is broken.
The server have not.

A bad, broken or malicious client may for what ever reason it may have,
send a request for a non-issued certificate.
If that happens, the protocol should allows ways to handle that.

Just imagine a such benign situation of a client with a bug, that sends
the wrong serial number if the most significant bit is set.
For half of it's requests it sends requests for completely non existent
certs.

Perhaps not likely, but possible.

The chance of discovering this error increase significantly if the
non-issued serial number requests returns "revoked" instead of "good".

This just on top of the case of a broken CA.


>
>> 
>> >If you say that this assumption is invalid, your trichotomy of serial
>> >status is not mutually exclusive any more. Same serial can now be
>> >associated with a good, revoked and non-issued status.
>> 
>> I didn't say that. I said it can "only be good, revoked or non-issued"
>> Notice the difference? My sentence contains the word "or", yours the
>>word
>> "and".
>
>I stand by my words :).

Feel free. But saying a million times that a black stone is white, does
not change its colour.

>
>> These are the three possible states of a serial number. It must always
>>be
>in
>> ONE of these states.
>As long as you assume that a certificate signed by the CA cannot be
>non-issued i.e. CA knows what certificates it issued.
>If you break that assumption, you have to deal with the possibility of
>different certificates with same serial numbers (after all certificates
>are
>getting issued without CA's knowledge). This implies that the same serial
>number can be associated with a good certificate and a non-issued
>certificate.
>
>Let me frame it in a different way. If you get a "good" response from a
>responder that issues "revoked" for "non-issued", can you be sure that the
>certificate you are checking is not a non-issued certificate?
>

No, to take it to that level, you need a new white list extension.
You see this from the wrong angle.

This change is not intended to provide the client indisputable knowledge
about whether a certificate is non-issued or not.
It is intended to give the responder a means of causing the client to
reject rather than accept something that is known not to be good.


>
>> 
>> >And also the client cannot be sure if
>> >the CA delegated responder's certificate is good or non-issued. This
>> >renders OCSP completely useless.
>> 
>> I did not talk about responder certificates.
>
>You did not. But that does not make my statement any less relevant or
>incorrect and strengthens Henry's point about this spec achieving what it
>is
>trying to do.
>


It makes your statement totally irrelevant until the point where you can
demonstrate its relevance.

/Stefan





From superuser@gmail.com  Sat Apr 13 17:27:03 2013
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 90CA621F8E6D for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 17:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-4z8ye-6E5U for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 17:27:03 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A75F121F8A6B for <ietf@ietf.org>; Sat, 13 Apr 2013 17:27:02 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id c10so579915wiw.8 for <ietf@ietf.org>; Sat, 13 Apr 2013 17:27:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=0Dv9V9F3q4KJ8XYmC6zwQ3ODW67+zZp+iX9DiFyDjm0=; b=qxYtlYr1wCmf7EYkUo5yN7W0wAwDzwa4YPCxMhWGsZ6HT17ghuZF8A8H3TinSRyO7B RgHL1uJyLIgm2U6LCakSwhs4KfjxXlmIXZPuRDdhuZD/Ta+1EVXsrpu/6JBzuRk8TT4S ZrqtLwudsXrf9jkNM1CjSUncNoiiFmeQVFkaknnXiijPuWjyHIMrtxHPVi9wKbg0hWXR DUMnPvNnTiDKMSp/kKWccHS6BTjcyl0LbSUnePTjYSQ1EMMwqVr0h0tyqJVodRrqqCQ3 gBofpJ3+5n09tm7ryvgFlJCs1oKnPsZRjDszJDof5ADVP7WG4mtvxdHjQwPaET99hgnl WXfQ==
MIME-Version: 1.0
X-Received: by 10.194.93.68 with SMTP id cs4mr24934928wjb.17.1365899221869; Sat, 13 Apr 2013 17:27:01 -0700 (PDT)
Received: by 10.180.36.176 with HTTP; Sat, 13 Apr 2013 17:27:01 -0700 (PDT)
In-Reply-To: <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.com>
References: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com> <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.com>
Date: Sat, 13 Apr 2013 17:27:01 -0700
Message-ID: <CAL0qLwZFCYgb-h7VwGAOiy+5AsRqrHmor_WfRwsB5AYmZacR_A@mail.gmail.com>
Subject: Re: Purpose of IESG Review
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d8cffeb2a3604da473161
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, 14 Apr 2013 00:27:03 -0000

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

On Fri, Apr 12, 2013 at 12:24 PM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> How can a memebr of staff in a company argue with the manager about the
> manager's decisions or performance? Only Owners/shareholders can question
> managers and staff. IMO, the meeting/list discussions on any issue
> without an I-D written is the staff talking/working.
>

That is, as John said, completely wrong for any organization that wants to
be successful.  That goes for the IETF as well.  If I thought the IETF
operated in the restricted way you're describing, I'd have walked away long
ago.  The same goes for any serious job I've ever had.

In my experience here, there's always room to ask for justification for a
decision, and push back on things with which you disagree, be they
technical or procedural.  Different personalities respond to those
challenges differently, of course, but that doesn't change the point.


> I hope that when I review and comment on an I-D, it should be considered
> as one owner is talking, but seems like editors think they are the only
> owners. When IESG comment on the I-D it is managers/excutives talking. All
> parts are important to the best of output.
>

The role of a document editor is to record consensus.  If you comment on
something and nobody supports your perspective and the editor doesn't adopt
your suggestions, then the editor may seem like she or he is ignoring you
but has actually done the job properly.

-MSK

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

<div dir=3D"ltr">On Fri, Apr 12, 2013 at 12:24 PM, Abdussalam Baryun <span =
dir=3D"ltr">&lt;<a href=3D"mailto:abdussalambaryun@gmail.com" target=3D"_bl=
ank">abdussalambaryun@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmai=
l_extra">
<div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>How can a memebr =
of staff in a company argue with the manager about the manager&#39;s decisi=
ons or performance? Only Owners/shareholders can question managers and staf=
f. IMO, the=A0meeting/list discussions on any issue without=A0an I-D writte=
n=A0is the staff talking/working.</div>
</div></blockquote><div><br></div><div>That is, as John said, completely wr=
ong for any organization that wants to be successful.=A0 That goes for the =
IETF as well.=A0 If I thought the IETF operated in the restricted way you&#=
39;re describing, I&#39;d have walked away long ago.=A0 The same goes for a=
ny serious job I&#39;ve ever had.<br>
<br></div><div>In my experience here, there&#39;s always room to ask for ju=
stification for a decision, and push back on things with which you disagree=
, be they technical or procedural.=A0 Different personalities respond to th=
ose challenges differently, of course, but that doesn&#39;t change the poin=
t. <br>
</div><div>=A0<br></div></div><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr"><div>I hope that when I review and comment o=
n an I-D, it should be considered as one owner is talking, but seems like e=
ditors think they are the only owners. When IESG comment on the I-D it is m=
anagers/excutives talking. All parts are important to the best of output.</=
div>
</div></blockquote><div><br></div><div>The role of a document editor is to =
record consensus.=A0 If you comment on something and nobody supports your p=
erspective and the editor doesn&#39;t adopt your suggestions, then the edit=
or may seem like she or he is ignoring you but has actually done the job pr=
operly.<br>
<br></div><div>-MSK<br></div></div></div></div>

--047d7b5d8cffeb2a3604da473161--

From huitema@microsoft.com  Sat Apr 13 20:18:04 2013
Return-Path: <huitema@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 A0D1721F8E9E for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 20:18:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZWBx4sJ8OGz for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 20:18:04 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) by ietfa.amsl.com (Postfix) with ESMTP id E790C21F8712 for <ietf@ietf.org>; Sat, 13 Apr 2013 20:18:03 -0700 (PDT)
Received: from BL2FFO11FD007.protection.gbl (10.173.161.201) by BL2FFO11HUB039.protection.gbl (10.173.160.245) with Microsoft SMTP Server (TLS) id 15.0.664.0; Sun, 14 Apr 2013 03:13:40 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD007.mail.protection.outlook.com (10.173.161.3) with Microsoft SMTP Server (TLS) id 15.0.675.0 via Frontend Transport; Sun, 14 Apr 2013 03:13:39 +0000
Received: from TK5EX14MBXC272.redmond.corp.microsoft.com ([169.254.2.149]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.02.0318.003; Sun, 14 Apr 2013 03:13:39 +0000
From: Christian Huitema <huitema@microsoft.com>
To: SM <sm@resistor.net>, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbwwl2LLJoxmkeCMXsLhpVRxJjRbDcAgAAKcACAAAcGAIAAATgAgAAEloCAAADsgIAAAUqAgAAGmICAADLzgIABJeUAgAAFsoCAAAi6gIAAAfoAgAAlvoCAAFKcgIAAhUuAgACBPYCAABlLgIAAfwfQ
Date: Sun, 14 Apr 2013 03:13:38 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0C02FEFA@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <6.2.5.6.2.20130413001404.0da31870@resistor.net> <28010.1365876115@sandelman.ca> <6.2.5.6.2.20130413112948.0d711398@resistor.net>
In-Reply-To: <6.2.5.6.2.20130413112948.0d711398@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.36]
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:(189002)(199002)(81542001)(74502001)(74662001)(47776003)(50986001)(81342001)(49866001)(54356001)(55846006)(4396001)(44976002)(46102001)(56776001)(33656001)(20776003)(16406001)(66066001)(65816001)(80022001)(23726001)(77982001)(51856001)(69226001)(46406002)(31966008)(79102001)(47976001)(56816002)(47736001)(53806001)(76482001)(50466001)(63696002)(59766001)(47446002)(54316002); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB039; H:TK5EX14HUBC102.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0816F1D86E
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: Sun, 14 Apr 2013 03:18:04 -0000

> This is a variation of the old boys club.  Let's say that there are two c=
andidates.  Candidate A has 20 years of IETF experience.  Candidate B has 5=
 years of IETF experience.  If the choice is about choosing the best Candid=
ate A will always be selected.

There may well be some of that going on, but there is something else as wel=
l, tied to very large time commitment required for area directors.=20

At some point, the candidate has to be able to say something like "I spoke =
to my boss and he agrees with the time commitment." We already know that th=
is creates a bias towards large companies whose products are directly affec=
ted by IETF standards. But it also creates a bias towards folks who are "we=
ll connected" inside their own company, and can use these connections to ge=
t someone to agree to foot their bill. And being "well connected" is typica=
l of the old boys clubs.

Bias reduction would certainly be much easier if the time commitment requir=
ed from volunteers was not so large.

-- Christian Huitema



From abdussalambaryun@gmail.com  Sun Apr 14 00:28:20 2013
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 BC72021F8E5E for <ietf@ietfa.amsl.com>; Sun, 14 Apr 2013 00:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[AWL=0.288,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNDWPkoekOHR for <ietf@ietfa.amsl.com>; Sun, 14 Apr 2013 00:28:20 -0700 (PDT)
Received: from mail-da0-x22f.google.com (mail-da0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 43CD821F8C98 for <ietf@ietf.org>; Sun, 14 Apr 2013 00:28:20 -0700 (PDT)
Received: by mail-da0-f47.google.com with SMTP id s35so1659042dak.6 for <ietf@ietf.org>; Sun, 14 Apr 2013 00:28:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=FDMiBZYHEQoPpzfipRXkYHNasB5wDP9vy/Yhuat3byE=; b=hOluYcQgO9zrizVFZ5AmE13St7pM3Fs+PlsN/psDpzeF5jtYTTVVfhgNsq4iEbc/F0 uGNMKiiFe5qhWj9DON5D/0g7InjQ1Vqd12hlj8gXDjgEoL0aRa252iQH9vLhDnbrnHyO Ek0C86YzpIw720O+BmuEU2O6urMZ/wn432lm6vULORVYg18CrrY1w8ytNQWp5XrRPYrB UhXmsku/+4NSjTbFdpGkLITaRbbwI6yRG988582D8tsMN1ZcU76Kni+NXa8J28kJdIY0 Z3eAKSr5f+cEwbmbBFM81oc4arKxEYFDrYouuPjddi4/QdWePxIGnkSK1sVf0iUUYTw+ Di6g==
MIME-Version: 1.0
X-Received: by 10.66.222.228 with SMTP id qp4mr23555447pac.113.1365924500059;  Sun, 14 Apr 2013 00:28:20 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Sun, 14 Apr 2013 00:28:19 -0700 (PDT)
In-Reply-To: <CAL0qLwZFCYgb-h7VwGAOiy+5AsRqrHmor_WfRwsB5AYmZacR_A@mail.gmail.com>
References: <CADnDZ88WZNYFs6u9N_pbQ=f3TdNK_N+S+aox1g9e2bmvmUL8sw@mail.gmail.com> <CADnDZ88_iN6sV3nW-MufcFrzs4Q=G0GLwEOHhwco=AXXLkLy+w@mail.gmail.com> <CAL0qLwZFCYgb-h7VwGAOiy+5AsRqrHmor_WfRwsB5AYmZacR_A@mail.gmail.com>
Date: Sun, 14 Apr 2013 09:28:19 +0200
Message-ID: <CADnDZ89WK5J=o-LqENp4EXuJj++GpmGmjbCTKQYGAh5NG5-EfA@mail.gmail.com>
Subject: Re: Purpose of IESG Review
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.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, 14 Apr 2013 07:28:20 -0000

Hi Murray,

I don't want me, you or anyother volunteer to leave, but also don't
want IESG memebrs to leave. I don't disagree with the concept of
discussing with managers or in the IETF to discuss with IESG (against
indirect methods of doing that). Please don't ignore that the first
message and all thread (related to subject) was not sent to IESG
address (or even copied). Speaking directly to the problem or to the
one making an error in performance is always the right thing to do. We
all work together in a friendly environment, by solving all problems
by direct effective efforts. Thanking you,

AB


On 4/14/13, Murray S. Kucherawy <superuser@gmail.com> wrote:
> On Fri, Apr 12, 2013 at 12:24 PM, Abdussalam Baryun <
> abdussalambaryun@gmail.com> wrote:
>
>> How can a memebr of staff in a company argue with the manager about the
>> manager's decisions or performance? Only Owners/shareholders can question
>> managers and staff. IMO, the meeting/list discussions on any issue
>> without an I-D written is the staff talking/working.
>>
>
> That is, as John said, completely wrong for any organization that wants to
> be successful.  That goes for the IETF as well.  If I thought the IETF
> operated in the restricted way you're describing, I'd have walked away long
> ago.  The same goes for any serious job I've ever had.
>
> In my experience here, there's always room to ask for justification for a
> decision, and push back on things with which you disagree, be they
> technical or procedural.  Different personalities respond to those
> challenges differently, of course, but that doesn't change the point.
>
>
>> I hope that when I review and comment on an I-D, it should be considered
>> as one owner is talking, but seems like editors think they are the only
>> owners. When IESG comment on the I-D it is managers/excutives talking.
>> All
>> parts are important to the best of output.
>>
>
> The role of a document editor is to record consensus.  If you comment on
> something and nobody supports your perspective and the editor doesn't adopt
> your suggestions, then the editor may seem like she or he is ignoring you
> but has actually done the job properly.
>
> -MSK
>

From brian.e.carpenter@gmail.com  Sun Apr 14 01:13:31 2013
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 CC12A21F8EB5 for <ietf@ietfa.amsl.com>; Sun, 14 Apr 2013 01:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.921
X-Spam-Level: 
X-Spam-Status: No, score=-98.921 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kqm78vii-kyF for <ietf@ietfa.amsl.com>; Sun, 14 Apr 2013 01:13:30 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3611021F8D94 for <ietf@ietf.org>; Sun, 14 Apr 2013 01:13:28 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hr17so680581wib.17 for <ietf@ietf.org>; Sun, 14 Apr 2013 01:13:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7v7q72I5x3u7uIwEMdMu7pFpZjeox+cp83Er5BUUE5Y=; b=QA1m5fhjVmcfOc1rbPIcJ6D4Bd8QWN90R4P5VcOWf4gMcGsYyKn5JQsqco+T6xo7rG iVVIjtWiqeG2s7V6Y87AJMnSnyeCEKwQG+rRqmH5zZ/IyqElSuDOHJGwHEozTC2ERKan XxrbbEzsTVNJjs28C6qhvc+zrNSQHW3nx3CrOUelARwAc7dpYLcwPvvJd2DlDzzX3AzP Lun5fXUW2w0gFCZzmF7lL+pmLxP6fNWFaZ/cVuUkK3tamBXXCYThJktfn5p2bbZtNBZQ 4+Do19yUIUezI00I+GU1fRWWmCa6fM8cZv2PcF3aATG5v+SySaKeXLWgIQCA9e/kEazk rPuQ==
X-Received: by 10.194.176.195 with SMTP id ck3mr20882188wjc.5.1365927207314; Sun, 14 Apr 2013 01:13:27 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-172.as13285.net. [2.102.216.172]) by mx.google.com with ESMTPS id bq19sm7627411wib.7.2013.04.14.01.13.25 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 14 Apr 2013 01:13:26 -0700 (PDT)
Message-ID: <516A6524.6010501@gmail.com>
Date: Sun, 14 Apr 2013 09:13:24 +0100
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 C Klensin <klensin@jck.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>	<20130411213835.GA8968@cisco.com>	<51675819.9070302@gmail.com>	<20130412181250.GA14224@cisco.com>	<51685369.4000306@gmail.com>	<13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>	<51685C64.3010803@gmail.com>	<51687C0D.8090804@labn.net>	<5168C159.3050004@gmail.com>	<20130413033755.GC5403@mx1.yitter.info> <0145DF6A724D1CA5E664213E@JcK-HP8200.jck.com>
In-Reply-To: <0145DF6A724D1CA5E664213E@JcK-HP8200.jck.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: Sun, 14 Apr 2013 08:13:31 -0000

On 13/04/2013 17:15, John C Klensin wrote:
> 
> --On Friday, April 12, 2013 23:37 -0400 Andrew Sullivan
> <ajs@anvilwalrusden.com> wrote:
> 
>> The only lesson I really learned from that experience is that
>> it is incredibly hard for women[1] to be treated as adult
>> colleagues in an environment that acts overwhelmingly as a
>> white male club. 
> 
> JJ Thompson, Grace Anscomb, etc., notwithstanding.  Similarly,
> Grace Hopper, Jean Sammet, Jane Thompson, Martha Steenstrup,
> Deborah Estrin, Sally Floyd, etc.
> 
> That doesn't change your point other than to identify a
> different fallacy in the "girl-philosophy" hypothesis and its
> computer science / networking analogies.   If you haven't heard
> of some of the above, it demonstrations a slightly different
> point.   It may also suggest that there is an area in which the
> IETF is absolutely non-discriminatory: there is no evidence
> that the IETF has been any more effective in driving, e.g.,
> Martha or Deborah out than with Crowcroft, Elz, Clark, Chapin,

And I'm not sure about the driving "out" rather than driving *on*
to bigger and better things. Also, speaking from personal
observation over the last 12 months in Cambridge (the original one),
at least one of those you mentioned is leading a very lively
research group including several active IETF contributors.

   Brian

From daedulus@btconnect.com  Mon Apr 15 01:49:26 2013
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 3684021F8F26 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 01:49:26 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pcJDQXSjVbA3 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 01:49:25 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe004.messaging.microsoft.com [216.32.181.184]) by ietfa.amsl.com (Postfix) with ESMTP id 72C5421F8A74 for <ietf@ietf.org>; Mon, 15 Apr 2013 01:49:25 -0700 (PDT)
Received: from mail144-ch1-R.bigfish.com (10.43.68.232) by CH1EHSOBE018.bigfish.com (10.43.70.68) with Microsoft SMTP Server id 14.1.225.23; Mon, 15 Apr 2013 08:49:23 +0000
Received: from mail144-ch1 (localhost [127.0.0.1])	by mail144-ch1-R.bigfish.com (Postfix) with ESMTP id 90647400C4; Mon, 15 Apr 2013 08:49:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: PS-19(zz9371I542I1432Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz1033IL8275bh8275dh8275chz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah304l1155h)
Received: from mail144-ch1 (localhost.localdomain [127.0.0.1]) by mail144-ch1 (MessageSwitch) id 1366015761625462_20358; Mon, 15 Apr 2013 08:49:21 +0000 (UTC)
Received: from CH1EHSMHS041.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.239])	by mail144-ch1.bigfish.com (Postfix) with ESMTP id 94BCC2E0061;	Mon, 15 Apr 2013 08:49:21 +0000 (UTC)
Received: from AMSPRD0711HT001.eurprd07.prod.outlook.com (157.56.250.181) by CH1EHSMHS041.bigfish.com (10.43.69.250) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 15 Apr 2013 08:49:18 +0000
Received: from DB3PRD0411HT002.eurprd04.prod.outlook.com (157.56.253.53) by pod51017.outlook.com (10.242.14.162) with Microsoft SMTP Server (TLS) id 14.16.293.5; Mon, 15 Apr 2013 08:49:10 +0000
Message-ID: <00a401ce39b5$708d5f20$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Lou Berger <lberger@labn.net>, Melinda Shore <melinda.shore@gmail.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org><6.2.5.6.2.20130411101504.0c42fed0@resistor.net><8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com><5167211A.8080807@wonderhamster.org><CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com><8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com><CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com><8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com><20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com><20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com><13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net><51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net><5168C159.3050004@gmail.com> <51694B16.4090504@labn.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
Date: Mon, 15 Apr 2013 09:44:20 +0100
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.253.53]
X-FOPE-CRA-SourceIpAddress: 157.56.250.181
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: melinda.shore@gmail.com
X-FOPE-BFA-RECEIVER: lberger@labn.net
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: Mon, 15 Apr 2013 08:49:26 -0000

----- Original Message -----
From: "Lou Berger" <lberger@labn.net>
To: "Melinda Shore" <melinda.shore@gmail.com>
Cc: <ietf@ietf.org>
Sent: Saturday, April 13, 2013 1:09 PM
> Melinda,
> I'm not so sure debating the merits of a specific measure has value or
> not is really that helpful, and I probably just should have ignore
this
> small point.  Let's say some limited measure of diversity is valid,
what
> do we learn from it?  Is the conclusion that only one group is being
> discriminated against and that the IETF needs to address this one
> specific form of discrimination, or is it that the top of the IETF is
> far from diverse?  If the latter, I buy it -- the IETF has a diversity
> issue.
>
> As many others have said, there are many forms of bias and
> discrimination -- all of which are harmful, and only some of which
have
> the legal protection (in your favorite country) that they should.
> Irrespective of any specific statistic, I think this discussion has
> shown that there is consensus that working to eliminate bias and
> discrimination *in all forms* from the IETF is worth paying attention
> to.  Do you disagree, are you saying that the IETF should only/first
try
> to address only gender bias?
>
> I personally think all IETF participants should have voice in this
> discussion, no matter if they fall into an obviously discriminated
> against group or not.  This includes the full range of participants,
> even newcomers, folks who have never authored an I-D, folks who by any
> measure are significant I* contributors, and even "western white
guys".
> IMO the exclusion of any voice is itself a manifestation of bias.

I am in the happy position of not having attended an IETF meeting for a
while and for many, perhaps most, of those active on the lists I track,
I have no idea what they look like. White or black, western or eastern,
I have no idea.  An e-mail address of a CJK company used to suggest a
person of eastern origins, now it just means that the CJK company has
taken control of the western one.  Sometimes I cannot even tell male or
female, although the name used may give me a clue.  In one case, an AD
referred to a contribution as coming from a 'he' which is surely wrong,
that is a woman's name; but I do not know, cannot tell, only that the
contributions that she/he makes are valuable and I would be happy to see
them as, e.g., AD.

So perhaps, to reduce the bias, e.g. towards "western white", any system
of choosing should give preference to the views of those who do not
attend IETF meetings, for whom judgement is based solely on the
contributions the person in question is seen to make - via the mailing
lists - towards open standards and running code.

Tom Petch
(white, western)

> Lou
>



From daedulus@btconnect.com  Mon Apr 15 02:12:15 2013
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 4A74221F9335 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 02:12:15 -0700 (PDT)
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=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6pthY7fF0j82 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 02:12:14 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id 0F38321F9330 for <ietf@ietf.org>; Mon, 15 Apr 2013 02:12:13 -0700 (PDT)
Received: from mail5-va3-R.bigfish.com (10.7.14.252) by VA3EHSOBE001.bigfish.com (10.7.40.21) with Microsoft SMTP Server id 14.1.225.23; Mon, 15 Apr 2013 09:12:13 +0000
Received: from mail5-va3 (localhost [127.0.0.1])	by mail5-va3-R.bigfish.com (Postfix) with ESMTP id 42FED203ED	for <ietf@ietf.org>; Mon, 15 Apr 2013 09:12:13 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: PS-27(zzbb2dI98dI9371I542I1432I1418I1db9Mzz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah304l1155h)
Received: from mail5-va3 (localhost.localdomain [127.0.0.1]) by mail5-va3 (MessageSwitch) id 1366017074231698_8119; Mon, 15 Apr 2013 09:11:14 +0000 (UTC)
Received: from VA3EHSMHS014.bigfish.com (unknown [10.7.14.235])	by mail5-va3.bigfish.com (Postfix) with ESMTP id A97C84C0089; Mon, 15 Apr 2013 09:10:57 +0000 (UTC)
Received: from AM2PRD0710HT005.eurprd07.prod.outlook.com (157.56.249.213) by VA3EHSMHS014.bigfish.com (10.7.99.24) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 15 Apr 2013 09:10:57 +0000
Received: from DB3PRD0411HT003.eurprd04.prod.outlook.com (157.56.253.53) by pod51017.outlook.com (10.255.165.40) with Microsoft SMTP Server (TLS) id 14.16.293.5; Mon, 15 Apr 2013 09:10:43 +0000
Message-ID: <012a01ce39b8$73c3caa0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <l.wood@surrey.ac.uk>, <ietf@ietf.org>
References: <5166F8BD.7010308@isi.edu> <51686076.3010508@gmail.com>, <006e01ce37bf$a45c0ba0$4001a8c0@gateway.2wire.net> <290E20B455C66743BE178C5C84F12408223F494E5F@EXMB01CMS.surrey.ac.uk>
Subject: Re: Purpose of IESG Review
Date: Mon, 15 Apr 2013 10:03:39 +0100
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.253.53]
X-FOPE-CRA-Verdict: 157.56.249.213$surrey.ac.uk%13189%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: Mon, 15 Apr 2013 09:12:15 -0000

----- Original Message -----
From: <l.wood@surrey.ac.uk>
To: <daedulus@btconnect.com>; <arturo.servin@gmail.com>; <ietf@ietf.org>
Sent: Saturday, April 13, 2013 3:46 AM

If you think security and congestion are arcane, you have... problems.

This was an actual ietf working geoup, and not some e.g. W3c thing?

<tp>
Lloyd

Yes, e.g. in Operations and Management.

I track ICCRG (and have some familiarity with congestive collapse,
having had to trouble shoot it) but I also track some transport groups
and see pressure to allow traffic to build up faster, coming I think
from a major 'vendor'.  I do not think that there is agreement on
whether or not we should speed up networks (e.g. initial window = 10)
thereby increasing the risk of congestion.

Equally, I track SSH and TLS and continue, even after many years, to be
surprised at the hostile actions that are devised against networks and
the measures that get taken to counter them.

In both areas, I find the IESG to be cautious (and wonder if they are
being too cautious); but I am no expert in those fields and continue to
be surprised by the IESG.  I think that for many outside Security or
Transport Areas, these topics are still arcane.

Tom Petch

p.s. the last response I made to Lloyd got a reply to the effect that
Lloyd was no longer at the University of Surrey, so I do not know if
this will reach you/him.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of t.p.
[daedulus@btconnect.com]
Sent: 12 April 2013 21:52
To: Arturo Servin; ietf@ietf.org
Subject: Re: Purpose of IESG Review

----- Original Message -----
From: "Arturo Servin" <arturo.servin@gmail.com>
To: <ietf@ietf.org>
Sent: Friday, April 12, 2013 8:28 PM
>
> Not answering any particular post. Just a comment.
>
> The IESG should be there to attest that the IETF procedure was
followed
> and the document reached consensus in the WG and in the IETF LC and it
> was successfully reviewed by the Gen-ART. If it wasn't then this
> particular process should be reviewed and take actions accordingly
(e.g.
> returning the document to the wg).
>
> But if a single individual of the IESG can technically challenge and
> change the work of a whole WG and the IETF, then we have something
wrong
> in our process because that means that the document had a serious
> problem and we didn't spot it in the process or an IESG member is
using
> its power to change a document according to its personal beliefs.

My experience has been the former, where the IESG has raised concerns
about arcane topics, such as security and congestion, of which the WG
had limited expertise.  This might be caught by a directorate review,
but those seem patchy; it might be caught by IETF Last Call, but if you
are an expert at an arcane topic then you are probably too busy to
follow them.

So I do see the IESG DISCUSSing, when it would have been lovely to have
had, but it is hard to see quite how, it resolved earlier.  We just do
not have the breadth of knowledge of arcane topics.

Tom Petch

> Just a thought,
> as
>
> On 4/11/13 2:54 PM, Joe Touch wrote:
> > Hi, all,
> >
> > As an author who has had (and has) multiple documents in IESG
review,
> > I've noticed an increasing trend of this step to go beyond (IMO) its
> > documented and original intent (BCP 9, currently RFC 2026):
> >
> >    The IESG shall determine whether or not a specification submitted
to
> >    it according to section 6.1.1 satisfies the applicable criteria
for
> >    the recommended action (see sections 4.1 and 4.2), and shall in
> >    addition determine whether or not the technical quality and
clarity
> >    of the specification is consistent with that expected for the
> >    maturity level to which the specification is recommended.
> >
> > Although I appreciate that IESG members are often overloaded, and
the
> > IESG Review step is often the first time many see these documents, I
> > believe they should be expected to more clearly differentiate their
> > "IESG Review" (based on the above criteria) - and its accompanying
> > Position ballot, with their personal review.
> >
> > My concern is that by conflating their IESG position with their
personal
> > review, the document process is inappropriately delayed and that
> > documents are modified to appease a small community that does not
> > justify its position as representative.
> >
> > How do others feel about this?
> >
> > Joe
>





From bclaise@cisco.com  Mon Apr 15 02:36:29 2013
Return-Path: <bclaise@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 77B9F21F936D; Mon, 15 Apr 2013 02:36:29 -0700 (PDT)
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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1-YI7+ehvAv; Mon, 15 Apr 2013 02:36:29 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id A6CA121F9361; Mon, 15 Apr 2013 02:36:28 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3F9aPdv015778; Mon, 15 Apr 2013 11:36:25 +0200 (CEST)
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3F9Zdhs010177; Mon, 15 Apr 2013 11:35:54 +0200 (CEST)
Message-ID: <516BC9EB.3000303@cisco.com>
Date: Mon, 15 Apr 2013 11:35:39 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [Gen-art]  Review: draft-ietf-ipfix-flow-selection-tech-14.txt
References: <4F6BB53A.3070609@nostrum.com> <514B808F.3050203@joelhalpern.com>
In-Reply-To: <514B808F.3050203@joelhalpern.com>
Content-Type: multipart/alternative; boundary="------------090206070705000507060502"
Cc: General Area Review Team <gen-art@ietf.org>, ipfix-chairs@tools.ietf.org, "A. Jean Mahoney" <mahoney@nostrum.com>, draft-ietf-ipfix-flow-selection-tech@tools.ietf.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: Mon, 15 Apr 2013 09:36:29 -0000

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

Joel,

Thanks for your review.
>
> Minor issues:
>
>     If compliance is a big issue, then this document seems 
> under-specified. For example, it says in section 5.1 "In order to be 
> compliant with this document, at least the Property Match Filtering 
> MUST be implemented." However, Property Match Filtering as defined in 
> section 5.1.1 is a range of behaviors, so it is unclear which property 
> tests must be supported (any, all possible?) in order to be compliant.
>
I believe that this is fine.
The compliance statement is similar (i.e. generic) to the PSAMP RFC 5475.


        7 <http://tools.ietf.org/html/rfc5475#section-7>. Parameters for
        the Description of Selection Techniques

        This section gives an overview of different alternative selection
        schemes and their required parameters.  In order to be compliant with
        PSAMP, at least one of proposed schemes MUST be implemented.

Regards, Benoit.

--------------090206070705000507060502
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 text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Joel,<br>
      <br>
      Thanks for your review.<br>
    </div>
    <blockquote cite="mid:514B808F.3050203@joelhalpern.com" type="cite">
      <br>
      Minor issues:
      <br>
      <br>
      &nbsp;&nbsp;&nbsp;&nbsp;If compliance is a big issue, then this document seems
      under-specified. For example, it says in section 5.1 "In order to
      be compliant with this document, at least the Property Match
      Filtering MUST be implemented." However, Property Match Filtering
      as defined in section 5.1.1 is a range of behaviors, so it is
      unclear which property tests must be supported (any, all
      possible?) in order to be compliant.
      <br>
      <br>
    </blockquote>
    I believe that this is fine.<br>
    The compliance statement is similar (i.e. generic) to the PSAMP RFC
    5475.<br>
    <blockquote>
      <pre class="newpage"><span class="h2"><h2><a class="selflink" name="section-7" href="http://tools.ietf.org/html/rfc5475#section-7">7</a>.  Parameters for the Description of Selection Techniques</h2></span>   This section gives an overview of different alternative selection
   schemes and their required parameters.  In order to be compliant with
   PSAMP, at least one of proposed schemes MUST be implemented.

</pre>
    </blockquote>
    Regards, Benoit.<br>
  </body>
</html>

--------------090206070705000507060502--

From jari.arkko@piuha.net  Mon Apr 15 06:09:33 2013
Return-Path: <jari.arkko@piuha.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 BA40221F8E62 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 06:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.855
X-Spam-Level: 
X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=-0.745, BAYES_05=-1.11, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7h4fYvBnlYTj for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 06:09:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6DEC121F9381 for <ietf@ietf.org>; Mon, 15 Apr 2013 06:09:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E6D412CC50; Mon, 15 Apr 2013 16:09:30 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gO70nnV6WpZu; Mon, 15 Apr 2013 16:09:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 208412CC46; Mon, 15 Apr 2013 16:09:30 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Purpose of IESG Review
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com>
Date: Mon, 15 Apr 2013 16:09:30 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D80A2E6C-F325-4F63-AAB3-37E5C515851D@piuha.net>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
Cc: "adrian@olddog.co.uk Farrel" <adrian@olddog.co.uk>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.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, 15 Apr 2013 13:09:33 -0000

Responding to various people in one e-mail.

To summarise, we have procedures that say what kinds of Discusses are =
appropriate, and personal engineering preferences are not. Legitimate =
issues should be raised, however, and in the case of most big issues, =
the right approach would be to send a document back to the working group =
for revision. But overall, my perception is that the ADs take their task =
very seriously, and try to do the right thing when performing their IESG =
reviews. I think they make a significant contribution to the quality of =
our documents.

That being said, a couple of other things are also obvious.=20

First, we have a very tail-heavy process. I get a lot of comments about =
that, and you all know it too. Moving more of the problem finding to =
earlier parts of the process is necessary (but also not easy).

Secondly, I know from personal experience that feedback on what kinds of =
things get raised in the IESG review is very useful. Even if we are =
trying to do the right thing, we make mistake, and perhaps more =
importantly, our understanding of what kinds of discusses are useful =
keeps evolving. Please tell us when you think we are doing the wrong =
thing (be it not raising an issue or raising it in the wrong category).

Finally, today too many big revisions are handled as a discussion =
between the authors and ADs. Big discussions should be done publicly in =
the working group, and in some cases the right action is for a document =
to be sent to the working group so that it can be reprocesses and =
returned.

And then to the specific responses.

Fred:

> In my opinion, some individual ADs seem to, from their behavior, feel =
that they have not done their jobs unless they have raised a "discuss". =
The one that took the cake for me personally was a "discuss" raised by a =
particular AD (who shall remain nameless) that in essence wondered what =
he should raise a "discuss" about in my document. There were a couple of =
errors in that; he told me later that what he had done was opened the =
comment tool and typed that question, and subsequently accidentally hit =
the equivalent of "send" - the question wasn't intended to go out. But =
the question itself is telling: the issue was not "does the document =
meet the requirements of BCP 9", it was "what comment shall I raise"?

And this is of course completely against our rules in the Discuss =
criteria document. But accidents do happen. If there were an intentional =
"I owe you" Discuss, that is obviously something that should go away, =
and authors and other ADs should complain about it.

> Also, in my opinion, IESG review that raises a certain number of =
issues should not result in the document sitting in the IESG's queue for =
a few months while the authors go back and forth with the AD or the =
GEN-ART reviewer pounding the document into someone's idea of "shape" =
without working group involvement. I personally would prefer that simple =
matters get sorted out between the ADs and the author, but complex =
changes or additional content requested by the AD should result in the =
document being sent back to the working group.


> I'm not saying it doesn't serve a purpose. I'm saying that I know of =
drafts that have been nearly rewritten during such back-and-forth, so =
what popped out was largely unrelated to what went in. In such cases, I =
think the document should have been returned to the working group with =
comments, not worked on privately.


I agree 100% with this.

Adrian:

> Examples are useful because they give the IESG something to chew on. =
If you
> don't call us when we do "bad stuff" we might never know.

Indeed. For what it is worth, my own idea of what kinds of things I =
should as an AD complain about has evolved quite a bit. As a new AD I =
was overly eager, ready to defend the Internet against=85 bad documents. =
In some cases filing Discusses that in retrospect I probably should have =
filed as Comments. Over the years I've come to the realisation that most =
things are additional Comments for the authors to take into account, but =
that real brokenness should still cause a Discuss to be raised. But for =
such development to occur, you need to gain some perspective. Part of =
that process is getting feedback.

> I believe that the clue is in the word "Discuss" and I hope that I (at =
least) am
> willing to listen when the response is "we thought about it, it's not =
a big
> problem."

+1

Brian:

> Seeing randomly selected drafts as a Gen-ART reviewer, I can
> say that serious defects quite often survive WG review and
> sometimes survive IETF Last Call review, so the final review
> by the IESG does serve a purpose.

This is one of the big issues. I think we all agree that our process is =
tail-heavy. More review and more problem discoveries occur at the end. =
This is trivial to see, but the crux is how that could be changed.

Dave:

> the tendency of ADs to inject spontaneous, late-stage personal =
engineering preferences, which might have been reasonable to add to the =
original working group discussion but realistically have no place in a =
final review

And personal engineering preferences are against our rules for =
Discusses. But beauty is in the eye of the beholder, and so are bugs :-) =
Is a particular spec bug an legitimate, serious technical problem, =
otherwise somehow against agreed IETF consensus, or is it an engineering =
preference?

> But what is tiring about this line of justification is its continuing =
failure to balance the analysis by looking at the costs and problems =
that come with it.  Does it provide regular and sufficient benefit to =
justify its considerable costs?


Agreed.=20

Jari


From Ted.Lemon@nominum.com  Mon Apr 15 06:50:54 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0135D21F93B4 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 06:50:54 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a6QIL+gT6NSU for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 06:50:53 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6811B21F936C for <ietf@ietf.org>; Mon, 15 Apr 2013 06:50:53 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUWwFvB5WrKU0yE/4UtshONtv4IAmheRi@postini.com; Mon, 15 Apr 2013 06:50:53 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9C8E71B80E8 for <ietf@ietf.org>; Mon, 15 Apr 2013 06:50:52 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 95492190061; Mon, 15 Apr 2013 06:50:52 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 15 Apr 2013 06:50:52 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: t.p. <daedulus@btconnect.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHOObVrsxw5RhqwwUuIKG4LfyrlCZjXwmmA
Date: Mon, 15 Apr 2013 13:50:51 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775148A0C@mbx-01.win.nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org><6.2.5.6.2.20130411101504.0c42fed0@resistor.net><8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com><5167211A.8080807@wonderhamster.org><CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com><8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com><CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com><8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com><20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com><20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com><13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net><51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net><5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <00a401ce39b5$708d5f20$4001a8c0@gateway.2wire.net>
In-Reply-To: <00a401ce39b5$708d5f20$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <AEF9A26C6316814988CEF592815C01ED@nominum.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, 15 Apr 2013 13:50:54 -0000

On Apr 15, 2013, at 4:44 AM, t.p. <daedulus@btconnect.com> wrote:
> So perhaps, to reduce the bias, e.g. towards "western white", any system
> of choosing should give preference to the views of those who do not
> attend IETF meetings, for whom judgement is based solely on the
> contributions the person in question is seen to make - via the mailing
> lists - towards open standards and running code.

We could also all be assigned masks, vocoders and randomly-generated number=
s at the beginning of each IETF, and go around wearing burlap robes.

The problem with your solution is that at the moment it's actually pretty h=
ard to participate in IETF without going to meetings.   It's a source of so=
me frustration to me that despite having basically invented the Internet, t=
he IETF still does business as if we were living in the pre-Internet era.  =
 Three face-to-face meetings a year is a lot of carbon, and I think it also=
 creates barriers for participation that are only readily surpassed by peop=
le who for whatever reason happen to have a great deal of advantage.   The =
degree of good fortune that allows me to participate in IETF as I do is bre=
athtaking in its improbability.


From hotz@jpl.nasa.gov  Fri Apr 12 17:53:37 2013
Return-Path: <hotz@jpl.nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA96721F8E7B; Fri, 12 Apr 2013 17:53:37 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ZmHqNHCj0GF; Fri, 12 Apr 2013 17:53:37 -0700 (PDT)
Received: from mail.jpl.nasa.gov (sentrion2.jpl.nasa.gov [128.149.139.106]) by ietfa.amsl.com (Postfix) with ESMTP id 1AACE21F8E77; Fri, 12 Apr 2013 17:53:36 -0700 (PDT)
Received: from laphotz.jpl.nasa.gov (laphotz.jpl.nasa.gov [128.149.133.44]) (authenticated (0 bits)) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r3D0rJAX010491 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Fri, 12 Apr 2013 17:53:20 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
In-Reply-To: <CD8D5988.608C9%stefan@aaa-sec.com>
Date: Fri, 12 Apr 2013 17:53:10 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <18ED26A1-402F-40F3-A97F-380441620175@jpl.nasa.gov>
References: <CD8D5988.608C9%stefan@aaa-sec.com>
To: Stefan Santesson <stefan@aaa-sec.com>
X-Mailer: Apple Mail (2.1503)
X-Source-Sender: hotz@jpl.nasa.gov
X-AUTH: Authorized
X-Mailman-Approved-At: Mon, 15 Apr 2013 06:59:33 -0700
Cc: pkix@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, 13 Apr 2013 00:53:37 -0000

On Apr 11, 2013, at 10:37 PM, Stefan Santesson <stefan@aaa-sec.com> =
wrote:

> To put it simply. Given how OCSP is designed, the only way to allow =
"good"
> to represent a white-list, is if "revoked" can be returned for =
everything
> else.

I realize it's unfair of me to take this quote out of context.  =
Apologies, but I want to focus on it.

You've just said that there are only two valid responses from an OCSP =
server which has access to a white list.  In other words such a server =
inherently cannot provide any information about the actual revocation =
status of a cert, and its responses cannot distinguish between a =
lost/forged/whatever cert and a known-bad (actually revoked) cert.

The actual information which an OCSP responder might (should?) have =
would include both a white list and a black list.  An RP using OCSP to =
determine "the current status of a digital certificate without requiring =
CRLs" (as it says in the abstract) would hope to receive the available =
information about a subject cert.  In other words, after a successful =
query, it would hope to know if the subject cert was known-good, =
known-bad, or neither.

By combining the known-bad and neither responses, the RP must now use =
CRLs in order to distinguish those two cases. =20

This situation would appear to contradict the first sentence in the =
abstract of the document.  Doesn't a change which requires a change in =
the abstract exceed the authorized scope of this revision to 2560?  If =
it doesn't then I think the abstract needs to be updated.

I don't understand why we're trying so hard to avoid providing both the =
white-list and the black-list information at the same time in OCSP =
responses. =20

(Nit:  Since the Introduction repeats the Abstract, the reference to =
5912 added to the Abstract should also be added to the Introduction.)
------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu


From andy@yumaworks.com  Fri Apr 12 19:47:09 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DAC921F8F15 for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 19:47:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.74
X-Spam-Level: 
X-Spam-Status: No, score=-1.74 tagged_above=-999 required=5 tests=[AWL=0.238,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x0WXnc+wAWUO for <ietf@ietfa.amsl.com>; Fri, 12 Apr 2013 19:47:09 -0700 (PDT)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 1DF2221F8ED4 for <ietf@ietf.org>; Fri, 12 Apr 2013 19:47:08 -0700 (PDT)
Received: by mail-ie0-f171.google.com with SMTP id e14so4108454iej.16 for <ietf@ietf.org>; Fri, 12 Apr 2013 19:47:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=HdF+bCFX1NnPgNkzKCmcjhUg/b9nmyQ3gD/B5T1DTo4=; b=Q3edg1JzaWGoD2HHbK71lNYDLS7LScYT0oTft+UDjqtWjfuEaD7TBw3zNEvX7sLrw4 gP0v74Jbgc7sAY+R9Pi7i8Ik7B2dEuL3aidwh0/FQMvPBjM1m6mMcTOWkSVtj8pLoU6b 6h6Sdgp7WRLj+I5Xocy0eJF0Yb30NdF/uWFD44JNYfP73/urjoNp4JfKL9E+Yf/ns1ux URcNh74UWPKuMA5JV9nd1h7SeexWdLDIBi4LGBXBwx6L/2MD6Gvlw39m8yN80LsrD4tv 4EFN0s2uano0pIwy3iZQimHGeTqGCof3glrx/Tb/feWvdKUssZ84QZ4Bq3Cn0DwnYoCD TUDQ==
MIME-Version: 1.0
X-Received: by 10.50.114.195 with SMTP id ji3mr625430igb.67.1365821228658; Fri, 12 Apr 2013 19:47:08 -0700 (PDT)
Received: by 10.231.125.202 with HTTP; Fri, 12 Apr 2013 19:47:08 -0700 (PDT)
In-Reply-To: <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com>
Date: Fri, 12 Apr 2013 19:47:08 -0700
Message-ID: <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com>
Subject: Re: Purpose of IESG Review
From: Andy Bierman <andy@yumaworks.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQn5zUCVvdONuDm7DCU4pD7Bl/XwJDm8CHDAAJmKm8iZE6fC6WakAqGV9XVhYLJFew6FJnF8
X-Mailman-Approved-At: Mon, 15 Apr 2013 06:59:33 -0700
Cc: IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Apr 2013 02:47:09 -0000

On Thu, Apr 11, 2013 at 5:27 PM, Fred Baker (fred) <fred@cisco.com> wrote:
> In my opinion, some individual ADs seem to, from their behavior, feel tha=
t they have not done their jobs unless they have raised a "discuss". The on=
e that took the cake for me personally was a "discuss" raised by a particul=
ar AD (who shall remain nameless) that in essence wondered what he should r=
aise a "discuss" about in my document. There were a couple of errors in tha=
t; he told me later that what he had done was opened the comment tool and t=
yped that question, and subsequently accidentally hit the equivalent of "se=
nd" - the question wasn't intended to go out. But the question itself is te=
lling: the issue was not "does the document meet the requirements of BCP 9"=
, it was "what comment shall I raise"?
>
> Also, in my opinion, IESG review that raises a certain number of issues s=
hould not result in the document sitting in the IESG's queue for a few mont=
hs while the authors go back and forth with the AD or the GEN-ART reviewer =
pounding the document into someone's idea of "shape" without working group =
involvement. I personally would prefer that simple matters get sorted out b=
etween the ADs and the author, but complex changes or additional content re=
quested by the AD should result in the document being sent back to the work=
ing group.

Many of us can change the acronyms and describe a similar experience.
I would say "We don't have the authority to make that decision
without asking the WG" a lot.

But this is a 2nd order problem.
The real issue is the way the IESG manages WGs.
Good management doesn't fall out for free.
It is yet another continuous integration progress.
The IESG is the overworked bottleneck in the system
and the review process is the main reason.

The ADs that own a WG should be the main IESG members
that get involved at the details for any possible issue,
and hopefully make these comments/changes as early
in the WG process as possible.

During IESG review, the ADs from other areas should
restrict their comments to issues related to their area.
The final review should avoid changes made
which are feature redesigns or feature enhancements,
and limit changes to bug fixes only.


Andy

From piyush@ditenity.com  Sat Apr 13 09:51:34 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E06621F89D8 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 09:51:34 -0700 (PDT)
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=1.190,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zKgF3-QseNnw for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 09:51:34 -0700 (PDT)
Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by ietfa.amsl.com (Postfix) with ESMTP id 05E6721F86CA for <ietf@ietf.org>; Sat, 13 Apr 2013 09:51:33 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id bv4so260477qab.8 for <ietf@ietf.org>; Sat, 13 Apr 2013 09:51:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=rfcjEINVaNvjAQBA/G1PDBor5+uznTVkQOF2j+6mCOg=; b=QNYzj5HpZQLrwnfYx6g+mh86OJ1gPa6WpXaKTEn3WcrYGWcHskDoRWA32X/oP9bgC3 VLsbXrUDnIIGEAOefyELjwoZgyO67rLdzpWH5ouVLAggffPu7OjHWOdmJV31pT4rlVwU yzEo8v0WPqQat08eDU6IkX0XV+Ezvxwd6XF1t+2wZbA/i+ZbJiusgfgk8nO6OtGDVVFk dCEw59A+5Dl+wp4YupY7SYjyNGLVAhxcqGj1R+t+viNs0u/RgJdQXerjqnX7EgAV/Iqg KvDfEg7Hlb+7JliKDx63NvQFTMpJnXk9hh/3EcHxWRsgJ9hhzorM9oaP/J4CAk35FJkj 8+Ew==
X-Received: by 10.224.70.199 with SMTP id e7mr16314579qaj.6.1365871893475; Sat, 13 Apr 2013 09:51:33 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id r3sm7084573qef.5.2013.04.13.09.51.31 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 13 Apr 2013 09:51:32 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Stefan Santesson'" <stefan@aaa-sec.com>, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>
References: <18ED26A1-402F-40F3-A97F-380441620175@jpl.nasa.gov> <CD8ECDB9.60B3E%stefan@aaa-sec.com>
In-Reply-To: <CD8ECDB9.60B3E%stefan@aaa-sec.com>
Subject: RE: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
Date: Sat, 13 Apr 2013 09:51:28 -0700
Message-ID: <007d01ce3867$260e4760$722ad620$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQKUjVtic7F3hCrinY8N0Gyh7+jf4ZdHogRw
Content-Language: en-us
X-Gm-Message-State: ALoCoQkpKVGKuhWqpODyF/hg54fKbgbi17hTfyXFrtmww9hzYdtgyfFppk2KRr/Jo8cDrsyqX3UW
X-Mailman-Approved-At: Mon, 15 Apr 2013 06:59:33 -0700
Cc: pkix@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, 13 Apr 2013 16:51:34 -0000

> An extension may differentiate which serial number that results in a
> "revoked" response, that is actually issued and revoked, or if there is
any
> other particular reason for responding "revoked".
> In my universe a syntactically valid serial number can only be good,
revoked
> or non-issued. But expressing this in general terms anyway.

[Piyush]  From an RP's perspective finding status of serial numbers serves
no purpose unless they can associate that serial number with a certificate.
When an OCSP client extracts the serial number from a certificate and sends
it the responder to determine the status, it is acting under a very
important assumption - the CA has issued that certificate and that it has
issued only one certificate with that serial.
If you say that this assumption is invalid, your trichotomy of serial status
is not mutually exclusive any more. Same serial can now be associated with a
good, revoked and non-issued status. And also the client cannot be sure if
the CA delegated responder's certificate is good or non-issued. This renders
OCSP completely useless.

> 
> So with the help of extensions, a responder can provide both white and
black
> list data.

[Piyush] May be you are right. But I doubt that you want a discussion on
feasibility/security implications of this, otherwise it would've been a
stated goal of 2560bis and would have been captured in the abstract.
I tried to think ahead but I cannot figure out a way to communicate the
white listed status of a CA delegated responder to the client without
avoiding circular logic.

I completely fail to see why revoked for non-issued is a pre-requisite for
future extensions that can be used to provide white-list data (if it is even
possible under CA delegated responder trust model).


From piyush@ditenity.com  Sat Apr 13 11:56:51 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7812C21F8E49 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 11:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=1.085,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VuOv2f-NnIyq for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 11:56:51 -0700 (PDT)
Received: from mail-qe0-f51.google.com (mail-qe0-f51.google.com [209.85.128.51]) by ietfa.amsl.com (Postfix) with ESMTP id D646321F8CEB for <ietf@ietf.org>; Sat, 13 Apr 2013 11:56:50 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id 1so2071706qec.24 for <ietf@ietf.org>; Sat, 13 Apr 2013 11:56:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=0FoCA3B1iGRre80EctKcr4we4lQMxae2u7Y94oUZG7g=; b=Vy4+/2w/TiembfBzIKNqBFzBiwcGU00vzldr1tmzTXTPSXiPc88kc4N+anqi7v4KV5 j8qjFRbOLLdk+qOmI3Ftgp2g6EIsKp+Rgj7jabwa7tsFGsrCx4owPaZfduHRcHO3OZRV t1aHpNLLkwmsFMB4VoVX8Qn2ezyVxA2fzMjuOqcdJ0le7Y7qULqlTyR9DZnmESYxSygS KPy1kwEXu0vNY7TA67qzatGuzn1wyxFIjG4KA0EgwB8h3jyL8CvlbOIXtdD2E9akqXpy 3BM6HjTI4cGFu+Jw8NZzka4ZblO9vkP4XItSfF3NC7YYkKjX35DzPvHHNuSY/8j6v1AZ byFw==
X-Received: by 10.224.218.68 with SMTP id hp4mr6937641qab.16.1365879410313; Sat, 13 Apr 2013 11:56:50 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id ed8sm21024155qeb.7.2013.04.13.11.56.48 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 13 Apr 2013 11:56:49 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Stefan Santesson'" <stefan@aaa-sec.com>, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>
References: <007d01ce3867$260e4760$722ad620$@ditenity.com> <CD8F5E1F.60C5A%stefan@aaa-sec.com>
In-Reply-To: <CD8F5E1F.60C5A%stefan@aaa-sec.com>
Subject: RE: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
Date: Sat, 13 Apr 2013 11:56:46 -0700
Message-ID: <008201ce3878$a699c790$f3cd56b0$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQFqOMgQFAa3BzgFJfiV+G2zb+DLfJmcdlUw
Content-Language: en-us
X-Gm-Message-State: ALoCoQnr4CvKL+zhzO25gVHUPgNPb2dr+mjbnSfkAsuMeoOpMOnN8DQSTSkwlechlJy5vsUrGpcS
X-Mailman-Approved-At: Mon, 15 Apr 2013 06:59:33 -0700
Cc: pkix@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, 13 Apr 2013 18:56:51 -0000

> >[Piyush]  From an RP's perspective finding status of serial numbers
> >serves no purpose unless they can associate that serial number with a
> >certificate.
> 
> Absolutely, that is the client's perspective of this.

Great. We agree
> 
> >When an OCSP client extracts the serial number from a certificate and
> >sends it the responder to determine the status, it is acting under a
> >very important assumption - the CA has issued that certificate and that
> >it has issued only one certificate with that serial.
> 
> Absolutely
Great. We agree.  
Let me reiterate -OCSP client extracts the serial number assuming that the
CA issued the certificate and issued only one certificate with that serial
number. So why do we need the responder to return non-issued for the same
certificate?

> 
> >If you say that this assumption is invalid, your trichotomy of serial
> >status is not mutually exclusive any more. Same serial can now be
> >associated with a good, revoked and non-issued status.
> 
> I didn't say that. I said it can "only be good, revoked or non-issued"
> Notice the difference? My sentence contains the word "or", yours the word
> "and".

I stand by my words :).

> These are the three possible states of a serial number. It must always be
in
> ONE of these states.
As long as you assume that a certificate signed by the CA cannot be
non-issued i.e. CA knows what certificates it issued.
If you break that assumption, you have to deal with the possibility of
different certificates with same serial numbers (after all certificates are
getting issued without CA's knowledge). This implies that the same serial
number can be associated with a good certificate and a non-issued
certificate.

Let me frame it in a different way. If you get a "good" response from a
responder that issues "revoked" for "non-issued", can you be sure that the
certificate you are checking is not a non-issued certificate? 


> 
> >And also the client cannot be sure if
> >the CA delegated responder's certificate is good or non-issued. This
> >renders OCSP completely useless.
> 
> I did not talk about responder certificates.

You did not. But that does not make my statement any less relevant or
incorrect and strengthens Henry's point about this spec achieving what it is
trying to do.





From piyush@ditenity.com  Sat Apr 13 18:01:13 2013
Return-Path: <piyush@ditenity.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7360221F87D0 for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 18:01:13 -0700 (PDT)
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=1.012,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iwnUyIZzrdvI for <ietf@ietfa.amsl.com>; Sat, 13 Apr 2013 18:01:12 -0700 (PDT)
Received: from mail-qe0-f48.google.com (mail-qe0-f48.google.com [209.85.128.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5521921F875C for <ietf@ietf.org>; Sat, 13 Apr 2013 18:01:12 -0700 (PDT)
Received: by mail-qe0-f48.google.com with SMTP id 2so2120094qea.7 for <ietf@ietf.org>; Sat, 13 Apr 2013 18:01:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language:x-gm-message-state; bh=De8a4pnypHuAIWwMgu8b11faAF6ffDIgDbPyqLhiAR0=; b=g1bU6WI6ebl1CXopXqwHKJDO9sHh1Pvjs5klAGp01qqNI8dW+F/Vi4w/x2QW2MrhHC 19FTZuCc5kVD4qB2W+IO34fq23YC7gn3qUe2yrCicoXzbJV7vz7bxJ4+bNKtpiSHqDDF jyKvfTb27hCa6XSbDi1zkHa578kE2gy8eOswFwUzsGWjWj4MUeNjrfzk2cmU8+PP555f I4WLGT9gK07zn5fsFrztVeYcB75kolill8AVyNgbjCbnuyZkkQr3Sf+VxwS2oy9So4ke cdm1MH0i9oumSgUPYOyzhaYjZ+DboqQCNM23ZouirouZUg8O680xYTCrxFirF/NHgXxB QiYw==
X-Received: by 10.224.149.134 with SMTP id t6mr17477214qav.18.1365901271660; Sat, 13 Apr 2013 18:01:11 -0700 (PDT)
Received: from hp13 (75-25-128-241.lightspeed.sjcpca.sbcglobal.net. [75.25.128.241]) by mx.google.com with ESMTPS id ds5sm23512123qab.11.2013.04.13.18.01.09 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 13 Apr 2013 18:01:11 -0700 (PDT)
From: "Piyush Jain" <piyush@ditenity.com>
To: "'Stefan Santesson'" <stefan@aaa-sec.com>, "'Henry B. Hotz'" <hotz@jpl.nasa.gov>
References: <008201ce3878$a699c790$f3cd56b0$@ditenity.com> <CD8FB284.60CB7%stefan@aaa-sec.com>
In-Reply-To: <CD8FB284.60CB7%stefan@aaa-sec.com>
Subject: RE: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
Date: Sat, 13 Apr 2013 18:01:07 -0700
Message-ID: <009001ce38ab$8d019fa0$a704dee0$@ditenity.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQKGwC1UBG7VOr+jzSvkxe+3k9I1/Zdjwqag
Content-Language: en-us
X-Gm-Message-State: ALoCoQkxcWzU61kgGymeh5N4N40vTcLuELCooYC8WnPdm0lkYECmaHkCLYpvonT6+pWBGqjvRHtv
X-Mailman-Approved-At: Mon, 15 Apr 2013 06:59:33 -0700
Cc: pkix@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: Sun, 14 Apr 2013 01:01:13 -0000

Stefan,

I don't think that we have any gaps in the technical understanding of this
proposal. Based on the discussions over the last few months, I can
confidently say that the difference of opinion is around the benefits of
adoptions and the costs associated with it.

Here are the possible goals that had been discussed
1) Address CA compromise issue
2) Provide certificate white list/black list information to the clients
3) Allow CAs to return revoked for non-issued. Some clients in some
situation benefit by not falling back to CRL validation.

I understand that according to you, 3 is the only goal for this update. So I
am basing the following on that goal

Benefits
~~~~~~~
- In some situations, It allows clients to reject some (not all)
fraudulently issued certificates that are and not detected by the CA.
- It allows buggy clients sending incorrect serial number to detect the bug.
(This is based on your last post, but I don't think that you seriously
consider this a benefit :))
Limitations
~~~~~~~~
- Works only if attacker fraudulently issued a certificate with a serial
that is not associated with a good certificate.
- Works only if attacker did not fraudulently issued a responder
certificate.
- Works only if client is configured to use OCSP as primary validation
option
- Works only if responder is not a CRL based responder.
- Works only if responder is producing live responses. 

Cons (this is where we have the disagreement)
~~~~
- Stated goal leaves it to the imagination of readers to figure out the
problem that is being tackled.
- Provides false sense of security. Readers may believe that it addresses CA
compromise issue.
- Challenges the fundamental assumption behind x.509 processing that
certificate signature and certificate issuance are equivalent.
- Leaves the clients to deal with the paradox of responder trust if they
choose to interpret the response as meaning non-issued as opposed to revoked
- It's a change in the main document, so every implementer will have to go
through it even though the benefit is very limited to specific scenarios.
- The unintended consequence is that people will incorrectly start believing
that CRLs are less secure that OCSP.
- The draft exceeds the stated goal in the abstract (protocol useful in
determining the current   status of a digital certificate without requiring
CRLs)

I understand that you don't see the cons listed above as major problem.  
Your position is that it does not affect any other deployments except the
CAs who want to support it. That is technically correct, but the side effect
of this explicit endorsement from pkix is that the proponents start touting
this as the secure solution that needs to be adopted by everyone. They don't
have the luxury/motivation to look at pkix discussions to understand the
limitations of this approach.
As an example, there was a proposal in CAB forum to move away from CRL based
responders. Thankfully, a few vendors who have heavily invested in
pre-signed OCSP infrastructure voted against it.

On a final note, I understand there are facts and there are opinions and
this particular instance there are opinions galore (including mine:) ).
I suggest we move on, and let the IETF decide. I don't think our opinions
will converge with any more discussion. We'll have lot more data in a few
years to evaluate the diverse opinions that were presented in this WG. There
is always the option of coming out with another update if things don't go as
planned :).

-Piyush

> -----Original Message-----
> From: Stefan Santesson [mailto:stefan@aaa-sec.com]
> Sent: Saturday, April 13, 2013 4:24 PM
> To: Piyush Jain; 'Henry B. Hotz'
> Cc: pkix@ietf.org; ietf@ietf.org
> Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509
> Internet Public Key Infrastructure Online Certificate Status Protocol -
OCSP)
> to Proposed Standard
> 
> 
> 
> On 4/13/13 8:56 PM, "Piyush Jain" <piyush@ditenity.com> wrote:
> 
> >> >[Piyush]  From an RP's perspective finding status of serial numbers
> >> >serves no purpose unless they can associate that serial number with
> >> >a certificate.
> >>
> >> Absolutely, that is the client's perspective of this.
> >
> >Great. We agree
> >>
> >> >When an OCSP client extracts the serial number from a certificate
> >> >and sends it the responder to determine the status, it is acting
> >> >under a very important assumption - the CA has issued that
> >> >certificate and that it has issued only one certificate with that
serial.
> >>
> >> Absolutely
> >Great. We agree.
> >Let me reiterate -OCSP client extracts the serial number assuming that
> >the CA issued the certificate and issued only one certificate with that
> >serial number. So why do we need the responder to return non-issued for
> >the same certificate?
> 
> Because of your lack of fantasy :)
> Shift your focus from the client to the server.
> 
> A client have control over never asking for a non-issued certificate,
unless
> the CA is broken.
> The server have not.
> 
> A bad, broken or malicious client may for what ever reason it may have,
send
> a request for a non-issued certificate.
> If that happens, the protocol should allows ways to handle that.
> 
> Just imagine a such benign situation of a client with a bug, that sends
the
> wrong serial number if the most significant bit is set.
> For half of it's requests it sends requests for completely non existent
certs.
> 
> Perhaps not likely, but possible.
> 
> The chance of discovering this error increase significantly if the
non-issued
> serial number requests returns "revoked" instead of "good".
> 
> This just on top of the case of a broken CA.
> 
> 
> >
> >>
> >> >If you say that this assumption is invalid, your trichotomy of
> >> >serial status is not mutually exclusive any more. Same serial can
> >> >now be associated with a good, revoked and non-issued status.
> >>
> >> I didn't say that. I said it can "only be good, revoked or non-issued"
> >> Notice the difference? My sentence contains the word "or", yours the
> >>word  "and".
> >
> >I stand by my words :).
> 
> Feel free. But saying a million times that a black stone is white, does
not
> change its colour.
> 
> >
> >> These are the three possible states of a serial number. It must
> >>always be
> >in
> >> ONE of these states.
> >As long as you assume that a certificate signed by the CA cannot be
> >non-issued i.e. CA knows what certificates it issued.
> >If you break that assumption, you have to deal with the possibility of
> >different certificates with same serial numbers (after all certificates
> >are getting issued without CA's knowledge). This implies that the same
> >serial number can be associated with a good certificate and a
> >non-issued certificate.
> >
> >Let me frame it in a different way. If you get a "good" response from a
> >responder that issues "revoked" for "non-issued", can you be sure that
> >the certificate you are checking is not a non-issued certificate?
> >
> 
> No, to take it to that level, you need a new white list extension.
> You see this from the wrong angle.
> 
> This change is not intended to provide the client indisputable knowledge
> about whether a certificate is non-issued or not.
> It is intended to give the responder a means of causing the client to
reject
> rather than accept something that is known not to be good.
> 
> 
> >
> >>
> >> >And also the client cannot be sure if the CA delegated responder's
> >> >certificate is good or non-issued. This renders OCSP completely
> >> >useless.
> >>
> >> I did not talk about responder certificates.
> >
> >You did not. But that does not make my statement any less relevant or
> >incorrect and strengthens Henry's point about this spec achieving what
> >it is trying to do.
> >
> 
> 
> It makes your statement totally irrelevant until the point where you can
> demonstrate its relevance.
> 
> /Stefan
> 
> 
> 



From klaas@wierenga.net  Mon Apr 15 00:54:49 2013
Return-Path: <klaas@wierenga.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 8C97421F9339 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 00:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7A6dJK7seQ1f for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 00:54:49 -0700 (PDT)
Received: from out28-ams.mf.surf.net (out28-ams.mf.surf.net [145.0.1.28]) by ietfa.amsl.com (Postfix) with ESMTP id C7A4E21F9335 for <ietf@ietf.org>; Mon, 15 Apr 2013 00:54:48 -0700 (PDT)
Received: from teletubbie.het.net.je (teletubbie.het.net.je [192.87.110.29]) by outgoing1-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r3F7sjVJ028719; Mon, 15 Apr 2013 09:54:45 +0200
Received: from 64-103-25-233.cisco.com ([64.103.25.233] helo=dhcp-10-61-101-72.cisco.com) by teletubbie.het.net.je with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1 (FreeBSD)) (envelope-from <klaas@wierenga.net>) id 1UReFJ-000Iim-55; Mon, 15 Apr 2013 09:54:37 +0200
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
From: Klaas Wierenga <klaas@wierenga.net>
In-Reply-To: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com>
Date: Mon, 15 Apr 2013 09:54:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1503)
X-Antivirus: no malware found
X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN)
X-CanIt-Geo: ip=192.87.110.29; country=NL; latitude=52.5000; longitude=5.7500; http://maps.google.com/maps?q=52.5000,5.7500&z=6
X-CanItPRO-Stream: p-out:default (inherits from p:default,base:default)
X-Canit-Stats-ID: 0uJo7SJfA - 69412b6378f5 - 20130415 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com)
X-Mailman-Approved-At: Mon, 15 Apr 2013 06:59:33 -0700
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, 15 Apr 2013 07:54:49 -0000

>=20
> On Fri, Apr 12, 2013 at 8:24 PM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:
> How can a memebr of staff in a company argue with the manager about =
the manager's decisions or performance? Only Owners/shareholders can =
question managers and staff. IMO, the meeting/list discussions on any =
issue without an I-D written is the staff talking/working.

??? Not in the country I live in or the company I work for. It is IMO =
the *obligation* of a professional to call his manager on wrong =
decisions or performance. I think you have a strange view on IETF =
leadership, I for one, as a chair of a WG regard myself as the *servant* =
of the WG rather than the *boss*. We decide based on consensus, not on =
hierarchy.

Klaas=

From bclaise@cisco.com  Mon Apr 15 02:44:32 2013
Return-Path: <bclaise@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 18A8821F9393; Mon, 15 Apr 2013 02:44:32 -0700 (PDT)
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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pAhkDykt+3bA; Mon, 15 Apr 2013 02:44:30 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 0A91921F938E; Mon, 15 Apr 2013 02:44:29 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3F9iA4R016779; Mon, 15 Apr 2013 11:44:10 +0200 (CEST)
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3F9glMg020166; Mon, 15 Apr 2013 11:43:07 +0200 (CEST)
Message-ID: <516BCB97.9040404@cisco.com>
Date: Mon, 15 Apr 2013 11:42:47 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "Salvatore D'Antonio" <salvatore.dantonio@uniparthenope.it>
Subject: Re: R: Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>
References: <20130401072846.32360.9502.idtracker@ietfa.amsl.com> <5162C44B.5030904@cisco.com> <005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it>
In-Reply-To: <005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it>
Content-Type: multipart/alternative; boundary="------------040708030002030600080801"
X-Mailman-Approved-At: Mon, 15 Apr 2013 06:59:33 -0700
Cc: rahulp@cisco.com, 'IETF discussion list' <ietf@ietf.org>, draft-ietf-ipfix-flow-selection-tech@tools.ietf.org, apps-discuss@ietf.org, 'General Area Review Team' <gen-art@ietf.org>, 'S Moonesamy' <sm+ietf@elandsys.com>, ipfix-chairs@tools.ietf.org, ipfix@ietf.org, iesg@ietf.org, "'A. Jean Mahoney'" <mahoney@nostrum.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, 15 Apr 2013 09:44:32 -0000

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

Salvatore
>
> Dear all,
>
> A new version of the Internet Draft on Flow Selection Techniques has 
> been submitted. It contains the following changes:
>
> -A new section illustrating the difference between Intermediate Flow 
> Selection Process and Intermediate Selection Process has been added,
>
> -The sentence "In order to be compliant with this document, at least 
> the Property  Match Filtering MUST be implemented." has been removed 
> in Section 1,
>
> -“MUST” has been replaced with “SHOULD” in Section 5.1,
>
Actually, the feedback was:

    In Section 1:

       "In order to be compliant with this document, at least the Property
        Match Filtering MUST be implemented."

    The above text is repeated in Section 5.1.  I suggest removing this
    sentence as it does not seem related to scope.

    My reading of the "MUST" is that it is being used for compliance
    instead of the reasons described in RFC 2119.  I suggest reviewing
    the usage of RFC 2119 key words in Section 5.1.

So the solution is not to change MUST to SHOULD.
The question is whether "MUST" versus "must" must be used.
I understand the concern. For compliance reason with the PSAMP RFC 5475 
(which is closely related) ...


        7 <http://tools.ietf.org/html/rfc5475#section-7>. Parameters for
        the Description of Selection Techniques

        This section gives an overview of different alternative selection
        schemes and their required parameters.  In order to be compliant with
        PSAMP, at least one of proposed schemes MUST be implemented.

... I would keep the initial "MUST" from the previous draft version.

> -“The flowSelectorAlgorithm registry is maintained by IANA." has been 
> replaced with “IANA is requested to create the flowSelectorAlgorithm 
> registry.”
>
> -The sentence "The registry can be updated when specifications of the 
> new  technique(s) and any new Information Elements are provided." has 
> been removed since it did not clarify how the registry will be managed.
>
> - Section 6.1.1 “Property Match Filtering” has been changed by adding 
> some text on how Property Match Filtering can be  used by an 
> Intermediate Flow Selection Process in the Metering Process, in the 
>  Exporting Process and within an IPFIX Mediator.
>
When publishing a new version, please correct this editorial issue.

  " ... and Flow duration. in
    the An example is the selection of the largest ..."


> Best regards,
>
> Salvatore
>
> *Da:*Benoit Claise [mailto:bclaise@cisco.com]
> *Inviato:* lunedì 8 aprile 2013 15:21
> *A:* draft-ietf-ipfix-flow-selection-tech@tools.ietf.org
> *Cc:* ipfix-chairs@tools.ietf.org
> *Oggetto:* Fwd: Last Call Expired: 
> <draft-ietf-ipfix-flow-selection-tech-14.txt>
>
> Dear authors,
>
> The IETF last call has finished.
> Can you please update your draft based on the feedback received.
> Then I will progress it.
>
> Regards, Benoit
>
>
>
> -------- Original Message --------
>
> *Subject: *
>
> 	
>
> Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>
>
> *Date: *
>
> 	
>
> Mon, 01 Apr 2013 00:28:46 -0700
>
> *From: *
>
> 	
>
> DraftTracker Mail System <iesg-secretary@ietf.org> 
> <mailto:iesg-secretary@ietf.org>
>
> *To: *
>
> 	
>
> iesg@ietf.org <mailto:iesg@ietf.org>, ipfix-chairs@tools.ietf.org 
> <mailto:ipfix-chairs@tools.ietf.org>, 
> draft-ietf-ipfix-flow-selection-tech@tools.ietf.org 
> <mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org>
>
> *CC: *
>
> 	
>
> iesg-secretary@ietf.org <mailto:iesg-secretary@ietf.org>
>
> Please DO NOT reply to this email.
>   
> I-D: <draft-ietf-ipfix-flow-selection-tech-14.txt>
> ID Tracker URL:http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/
>   
> IETF Last Call has ended, and the state has been changed to
> Waiting for AD Go-Ahead.
>   
>   
>   
>
> ------------------------------------------------------------------------
>
> Nessun virus nel messaggio.
> Controllato da AVG - www.avg.com <http://www.avg.com>
> Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di 
> rilascio: 07/04/2013
>
>
> *******************************************************************************************************
>
> IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO
>
> Il 5 per mille all'Università degli Studi di Napoli 
> "Parthenope"incrementa le borse di studio agli studenti - codice 
> fiscale *80018240632*
>
> _http://www.uniparthenope.it/index.php/5xmille_
>
> _http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille_
>
>
> Questa informativa è inserita in automatico dal sistema al fine 
> esclusivo della realizzazione dei fini istituzionali dell'ente.
>
>
>
>
> *******************************************************************************************************
>
> IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO
>
> Il 5 per mille all'Università degli Studi di Napoli 
> "Parthenope"incrementa le borse di studio agli studenti - codice 
> fiscale *80018240632*
>
> _http://www.uniparthenope.it/index.php/5xmille_
>
> _http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille_
>
>
> Questa informativa è inserita in automatico dal sistema al fine 
> esclusivo della realizzazione dei fini istituzionali dell'ente.
>
>
>


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

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Salvatore<br>
    </div>
    <blockquote
      cite="mid:005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
      <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"Preformattato HTML Carattere";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.PreformattatoHTMLCarattere
	{mso-style-name:"Preformattato HTML Carattere";
	mso-style-priority:99;
	mso-style-link:"Preformattato HTML";
	font-family:Consolas;
	color:black;}
span.StileMessaggioDiPostaElettronica19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:217212090;
	mso-list-type:hybrid;
	mso-list-template-ids:308057158 -1513439274 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
      <div class="Section1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dear
            all,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">A
            new version of the Internet Draft on Flow Selection
            Techniques
            has been submitted. It contains the following changes:<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">         
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">A
            new section illustrating the difference between Intermediate
            Flow Selection Process and Intermediate Selection Process
            has been added,<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">         
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The
            sentence "In order to be compliant with this document,
            at least the Property  Match Filtering MUST be implemented."
            has been removed
            in Section 1,<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">         
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">“MUST”
            has been replaced with “SHOULD” in Section 5.1,</span></p>
      </div>
    </blockquote>
    Actually, the feedback was:<br>
    <blockquote>In Section 1:
      <br>
      <br>
        "In order to be compliant with this document, at least the
      Property
      <br>
         Match Filtering MUST be implemented."
      <br>
      <br>
      The above text is repeated in Section 5.1.  I suggest removing
      this sentence as it does not seem related to scope.
      <br>
      <br>
      My reading of the "MUST" is that it is being used for compliance
      instead of the reasons described in RFC 2119.  I suggest reviewing
      the usage of RFC 2119 key words in Section 5.1.
      <br>
      <br>
    </blockquote>
    So the solution is not to change MUST to SHOULD.<br>
    The question is whether "MUST" versus "must" must be used.<br>
    I understand the concern. For compliance reason with the PSAMP RFC
    5475 (which is closely related) ...<br>
    <blockquote>
      <pre class="newpage"><span class="h2"><h2><a class="selflink" name="section-7" href="http://tools.ietf.org/html/rfc5475#section-7">7</a>.  Parameters for the Description of Selection Techniques</h2></span>   This section gives an overview of different alternative selection
   schemes and their required parameters.  In order to be compliant with
   PSAMP, at least one of proposed schemes MUST be implemented.

</pre>
    </blockquote>
    ... I would keep the initial "MUST" from the previous draft version.
    <blockquote> </blockquote>
    <blockquote
      cite="mid:005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it"
      type="cite">
      <div class="Section1">
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">         
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">“The
            flowSelectorAlgorithm registry is maintained by IANA."
            has been replaced with “IANA is requested to create the
            flowSelectorAlgorithm
            registry.”<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">         
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The
            sentence "The registry can be updated when
            specifications of the new  technique(s) and any new
            Information Elements are
            provided." has been removed since it did not clarify how the
            registry will
            be managed.<o:p></o:p></span></p>
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span
              style="mso-list:Ignore">-<span style="font:7.0pt
                &quot;Times New Roman&quot;">         
              </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"> Section
            6.1.1 “Property Match Filtering” has been changed by
            adding some text on how Property Match Filtering can be
             used by an
            Intermediate Flow Selection Process in the Metering Process,
            in the  Exporting
            Process and within an IPFIX Mediator.</span></p>
      </div>
    </blockquote>
    When publishing a new version, please correct this editorial issue.<br>
    <br>
    <pre class="newpage"> " ... and Flow duration. in
   the An example is the selection of the largest ..."</pre>
    <br>
    <blockquote
      cite="mid:005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it"
      type="cite">
      <div class="Section1">
        <p class="MsoListParagraph"
          style="text-indent:-18.0pt;mso-list:l0 level1 lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best
            regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Salvatore<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #B5C4DF
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal"><b><span
                  style="font-size:10.0pt;font-family:&quot;Segoe
                  UI&quot;,&quot;sans-serif&quot;;
                  color:windowtext" lang="IT">Da:</span></b><span
                style="font-size:10.0pt;
                font-family:&quot;Segoe
                UI&quot;,&quot;sans-serif&quot;;color:windowtext"
                lang="IT"> Benoit Claise
                [<a class="moz-txt-link-freetext" href="mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>] <br>
                <b>Inviato:</b> lunedì 8 aprile 2013 15:21<br>
                <b>A:</b>
                <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><br>
                <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</a><br>
                <b>Oggetto:</b> Fwd: Last Call Expired:
                &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Dear authors,<br>
          <br>
          The IETF last call has finished.<br>
          Can you please update your draft based on the feedback
          received.<br>
          Then I will progress it.<br>
          <br>
          Regards, Benoit<o:p></o:p></p>
        <div>
          <p class="MsoNormal"><br>
            <br>
            -------- Original Message -------- <o:p></o:p></p>
          <table class="MsoNormalTable" border="0" cellpadding="0"
            cellspacing="0">
            <tbody>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>Subject: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal">Last Call Expired:
                    &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></p>
                </td>
              </tr>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>Date: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal">Mon, 01 Apr 2013 00:28:46 -0700<o:p></o:p></p>
                </td>
              </tr>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>From: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal">DraftTracker Mail System <a
                      moz-do-not-send="true"
                      href="mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</a><o:p></o:p></p>
                </td>
              </tr>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>To: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal"><a moz-do-not-send="true"
                      href="mailto:iesg@ietf.org">iesg@ietf.org</a>, <a
                      moz-do-not-send="true"
                      href="mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</a>,
                    <a moz-do-not-send="true"
                      href="mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><o:p></o:p></p>
                </td>
              </tr>
              <tr>
                <td style="padding:0cm 0cm 0cm 0cm" nowrap="nowrap"
                  valign="top">
                  <p class="MsoNormal" style="text-align:right"
                    align="right"><b>CC: <o:p></o:p></b></p>
                </td>
                <td style="padding:0cm 0cm 0cm 0cm">
                  <p class="MsoNormal"><a moz-do-not-send="true"
                      href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a><o:p></o:p></p>
                </td>
              </tr>
            </tbody>
          </table>
          <p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
          <pre>Please DO NOT reply to this email.<o:p></o:p></pre>
          <pre><o:p> </o:p></pre>
          <pre>I-D: &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></pre>
          <pre>ID Tracker URL: <a moz-do-not-send="true" href="http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/">http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/</a><o:p></o:p></pre>
          <pre><o:p> </o:p></pre>
          <pre>IETF Last Call has ended, and the state has been changed to<o:p></o:p></pre>
          <pre>Waiting for AD Go-Ahead.<o:p></o:p></pre>
          <pre><o:p> </o:p></pre>
          <pre><o:p> </o:p></pre>
          <pre><o:p> </o:p></pre>
          <p class="MsoNormal"><o:p> </o:p></p>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div class="MsoNormal" style="text-align:center" align="center">
          <hr style="color:#A0A0A0" noshade="noshade" size="1"
            width="100%" align="center">
        </div>
        <p class="MsoNormal"
          style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Nessun
virus
          nel messaggio.<br>
          Controllato da AVG - <a moz-do-not-send="true"
            href="http://www.avg.com">www.avg.com</a><br>
          Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data
          di rilascio:
          07/04/2013<o:p></o:p></p>
      </div>
      <br>
      <style type="text/css">

	<!--

		@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }

		P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }

		P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }

		P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }

		P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }

		A:link { color: #0000ff }

	-->

	</style>
      <!--</HEAD></BODY>-->
      <p text="#000000" link="#0000ff" dir="LTR" lang="it-IT">
      </p>
      <p class="western" style="margin-bottom: 0cm"><font face="Arial,
          sans-serif">*******************************************************************************************************</font></p>
      <p class="western" style="margin-bottom: 0cm"><font face="Arial,
          sans-serif">IL
          MERITO DEGLI STUDENTI VIENE RICONOSCIUTO</font></p>
      <p class="western" style="margin-bottom: 0cm"> </p>
      <p class="western" style="margin-bottom: 0cm"><font
          color="#000000"><font face="Arial, sans-serif">Il
            5 per mille all'Università degli Studi di Napoli
            "Parthenope"incrementa le borse di studio agli studenti
            - codice fiscale </font></font><font color="#000000"><font
            face="Arial, sans-serif"><b>80018240632</b></font></font><font
          color="#000000"><font face="Arial, sans-serif">
          </font></font>
      </p>
      <p class="western" style="margin-bottom: 0cm"><a
          moz-do-not-send="true"
          href="http://www.uniparthenope.it/index.php/5xmille"><font
            color="#0000ff"><font face="Arial, sans-serif"><u>http://www.uniparthenope.it/index.php/5xmille</u></font></font></a><font
          color="#000000"><font face="Arial, sans-serif"> </font></font></p>
      <p class="western" style="margin-bottom: 0cm"> </p>
      <p class="western" style="margin-bottom: 0cm"><a
          moz-do-not-send="true"
href="http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><font
            color="#0000ff"><font face="Arial, sans-serif"><u>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</u></font></font></a></p>
      <p class="western" style="margin-bottom: 0cm"> <font face="Arial,
          sans-serif"><br>
          Questa
          informativa è inserita in automatico dal sistema al fine
          esclusivo
          della realizzazione dei fini istituzionali dell'ente.</font></p>
      <p class="western" style="margin-bottom: 0cm"><br>
      </p>
      <!--</BODY>-->
      <!--</HTML>-->
      <br>
      <br>
      <style type="text/css">

	<!--

		@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }

		P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }

		P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }

		P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }

		P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }

		A:link { color: #0000ff }

	-->

	</style>
      <!--</HEAD></BODY>-->
      <p text="#000000" link="#0000ff" dir="LTR" lang="it-IT">
      </p>
      <p class="western" style="margin-bottom: 0cm"><font face="Arial,
          sans-serif">*******************************************************************************************************</font></p>
      <p class="western" style="margin-bottom: 0cm"><font face="Arial,
          sans-serif">IL
          MERITO DEGLI STUDENTI VIENE RICONOSCIUTO</font></p>
      <p class="western" style="margin-bottom: 0cm"> </p>
      <p class="western" style="margin-bottom: 0cm"><font
          color="#000000"><font face="Arial, sans-serif">Il
            5 per mille all'Università degli Studi di Napoli
            "Parthenope"incrementa le borse di studio agli studenti
            - codice fiscale </font></font><font color="#000000"><font
            face="Arial, sans-serif"><b>80018240632</b></font></font><font
          color="#000000"><font face="Arial, sans-serif">
          </font></font>
      </p>
      <p class="western" style="margin-bottom: 0cm"><a
          moz-do-not-send="true"
          href="http://www.uniparthenope.it/index.php/5xmille"><font
            color="#0000ff"><font face="Arial, sans-serif"><u>http://www.uniparthenope.it/index.php/5xmille</u></font></font></a><font
          color="#000000"><font face="Arial, sans-serif"> </font></font></p>
      <p class="western" style="margin-bottom: 0cm"> </p>
      <p class="western" style="margin-bottom: 0cm"><a
          moz-do-not-send="true"
href="http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><font
            color="#0000ff"><font face="Arial, sans-serif"><u>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</u></font></font></a></p>
      <p class="western" style="margin-bottom: 0cm"> <font face="Arial,
          sans-serif"><br>
          Questa
          informativa è inserita in automatico dal sistema al fine
          esclusivo
          della realizzazione dei fini istituzionali dell'ente.</font></p>
      <p class="western" style="margin-bottom: 0cm"><br>
      </p>
      <!--</BODY>-->
      <!--</HTML>-->
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------040708030002030600080801--

From jari.arkko@piuha.net  Mon Apr 15 07:14:33 2013
Return-Path: <jari.arkko@piuha.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 D568921F93DD for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 07:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Level: 
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8BtRi3j5o+83 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 07:14:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B612621F93DF for <ietf@ietf.org>; Mon, 15 Apr 2013 07:14:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 755A82CC50; Mon, 15 Apr 2013 17:14:31 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UMEgs1fkvS7J; Mon, 15 Apr 2013 17:14:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 99E1E2CC46; Mon, 15 Apr 2013 17:14:30 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20130413125652.GA3818@cisco.com>
Date: Mon, 15 Apr 2013 17:14:30 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <240B7997-A9B8-4385-80B7-D9E8616DBD9F@piuha.net>
References: <20130412235542.8CEDA1A6AD@ld9781.wdf.sap.corp> <51693729.4010502@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775144AF2@mbx-01.win.nominum.com> <20130413125652.GA3818@cisco.com>
To: Toerless Eckert <eckert@cisco.com>
X-Mailer: Apple Mail (2.1503)
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, 15 Apr 2013 14:14:34 -0000

Toerless,

> A question because my institutional memory does reach as far back:
> How much was Europe represented over the decades in IETF leadership ?=20=

>=20
> Right now for example IESG seems to have maybe at least 5
> europeans (don't really know how to figure out location for all of =
them,
> those where just the easy ones for me).   But i would expect that this
> was by far not the case going back in time.
>=20
> Nobody cares about "diversity" for europeans in this round of the=20
> discussion, but i wonder if this was equally true in the past.

Can't say much about the leadership situation, as I have not tracked it. =
But there has definitely been significant increase of Europeans =
participating in the IETF work over time, though most of it happened =
many years ago. See =
http://www.arkko.com/tools/rfcstats/d-contdistrhist_norm.html  Asian =
growth has been a more recent occurrence.=20

> Maybe this evolution would be a good example to folks without that =
long
> reaching institutional memory to show how the IETF leadership
> does pretty well  reflect the evolution of the industry. If the
> industry will become more diverse, IETF will reflect this equally.
> If on the other hand we try to achieve greater diversity than the
> industry, then we have a real challenge on our hand.=20
>=20
> The concentration to fewer and larger companies in todays vs. past
> leadership was mentioned in before as "bad". I think its exactly
> for the same reason.

True. And the Asian growth and lack of some other parts of world reflect =
some of those industry situations. But at the same time, I feel the =
situation is a little bit like discussing something in a group here you =
actually want to hear everyone's opinion. Since there will always be a =
few quiet ones, you take special care to ask the quiet ones for their =
opinions, and in the end may learn something important from them. The =
ones who do not have the strongest and largest industries may also have =
important input for us with regards to the Internet. This is why we need =
to continue with things like the ISOC fellowship program, or make an =
extra effort to get smaller companies involved. We can't change where =
work actually happens, but we should at least know who the "silent ones" =
are in the Internet community (yet with knowledge) and make an extra =
effort to get at least some involvement from them. Just think how much =
real-world networking and Internet work actually is being done around =
the world still in small companies, for instance, in addition to our =
large companies.

Jari


From Ted.Lemon@nominum.com  Mon Apr 15 07:23:05 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCA7A21F8F76 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 07:23:05 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k20r6D6GlWCJ for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 07:23:02 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id E663F21F86E6 for <ietf@ietf.org>; Mon, 15 Apr 2013 07:23:01 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUWwNRcLSkVlYEptdLWsRdKWlIKRSj7j2@postini.com; Mon, 15 Apr 2013 07:23:01 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3153A1B80E8 for <ietf@ietf.org>; Mon, 15 Apr 2013 07:23:01 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2A304190061; Mon, 15 Apr 2013 07:23:01 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 15 Apr 2013 07:23:01 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: AQHONt2z+kkmqEfX7EKa70fj1HnPWJjR08iAgAA/MgCAAB26AIABuUoAgAPnEwA=
Date: Mon, 15 Apr 2013 14:23:00 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com> <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com>
In-Reply-To: <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <39A67687152A1C4EBB3AE7612EB56E55@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Paul Hoffman <paul.hoffman@vpnc.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: Mon, 15 Apr 2013 14:23:05 -0000

On Apr 12, 2013, at 10:47 PM, Andy Bierman <andy@yumaworks.com> wrote:
> During IESG review, the ADs from other areas should
> restrict their comments to issues related to their area.
> The final review should avoid changes made
> which are feature redesigns or feature enhancements,
> and limit changes to bug fixes only.

I have some sympathy for this argument, since most of the comments I've mad=
e about drafts since I started reviewing them as an AD, where I felt the mo=
st unsure I should be making the comment, have indeed been out-of-area or p=
rocess comments.   At the same time, I have expertise in quite a few protoc=
ols that aren't in my area, and I don't claim to be a perfect expert on eve=
ry protocol that's being worked on by a working group for which I am respon=
sible AD.

So in practice, although I feel great sympathy for this position, I think i=
t's mistaken.   I want the other ADs to comment on anything that they notic=
e that looks like a problem.   Then we can have a conversation about it.   =
What I've seen in the past two formal telechats, which are the only two I'v=
e been on as an AD, as opposed to a guest, is that out-of-area DISCUSSes an=
d comments do get raised, and they get discussed, which is the whole point.=
  Typically either some adjustment is made to the spec to make it clearer (=
this has been the case for nearly all of my DISCUSSes), or the AD who raise=
d the DISCUSS is satisfied by the discussion and clears the DISCUSS without=
 any change being made to the document.

So it's hard to see the harm in this, although I know it's stressful for th=
e authors and working group chairs who have to answer the questions.   I've=
 been there, and I know what it's like, and I'm very conscious of that when=
 I write a DISCUSS or a comment.

On the other hand, sometimes a document attracts a great deal of comment.  =
 Sometimes someone raises a point that is impossible to refute, and that cl=
early matters.   I want that point to be raised whether the AD raising it i=
s responsible for that area or not.

Reviewing documents as an AD is really hard work.   We had an easy telechat=
 last Thursday=97I think we had less than 150 pages of protocol specs to re=
ad for the telechat.   It would not surprise me if the number of careful re=
views of those documents doubled last week, for most of the documents.   I =
think it's absurd to suggest that such a review won't catch any issues, and=
 it's unreasonable to suggest that a reviewer keep silent on an issue he or=
 she sees simply because it's "not their area."=

From brian.e.carpenter@gmail.com  Mon Apr 15 07:45:16 2013
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 418FB21F93BB for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 07:45:16 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gu68MpFLv-4G for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 07:45:15 -0700 (PDT)
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC1E21F93BE for <ietf@ietf.org>; Mon, 15 Apr 2013 07:45:15 -0700 (PDT)
Received: by mail-wg0-f51.google.com with SMTP id b12so4608233wgh.18 for <ietf@ietf.org>; Mon, 15 Apr 2013 07:45:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=GRJkjGmVIgreE7P+APeXhmFbyxv798VHyYjN9FjfGWU=; b=TZ+5lcNBNDWtY0fwFob26O3+rCyAI7CFNk5bkPsr5zvV6Ivx0BOVOrkJ+rCpNm4CZZ /N4Ajw85pp6xh2dUB3JANWA0CPlzhnyqcrPDUUrI1SCUbdZBcPQWzDY4jcsOMo86RLwC ZlyE+VZv4n0BJkO7A5xVGg4VGol9/LCHPuYw5JpkszqRB+Gr9M1iI0/3mSMR2y7HueLy 2nRijBMcZMDDOvjVSrb2FPxryj05Vb1FKUGsMTJmW3N2mO3ZGo3N/wPSPjwwaVtJ2XZm Yah7/9GQDDqycYuMI9+AZYGXsnAGEOQegosRiGtq5kc6YnCYIg8MMzxuH7wkTERO9UTF Mujw==
X-Received: by 10.181.11.196 with SMTP id ek4mr12588945wid.30.1366037114585; Mon, 15 Apr 2013 07:45:14 -0700 (PDT)
Received: from [10.3.2.18] (a2.norwich.yourspac.nsdsl.net. [94.229.131.97]) by mx.google.com with ESMTPS id fz3sm182140wib.0.2013.04.15.07.45.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Apr 2013 07:45:13 -0700 (PDT)
Message-ID: <516C1277.9020304@gmail.com>
Date: Mon, 15 Apr 2013 15:45:11 +0100
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: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu>	<A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org>	<51673C0E.2080700@isi.edu>	<8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com>	<CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Andy Bierman <andy@yumaworks.com>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Apr 2013 14:45:16 -0000

On 15/04/2013 15:23, Ted Lemon wrote:

...
> So in practice, although I feel great sympathy for this position, I think it's mistaken.   I want the other ADs to comment on anything that they notice that looks like a problem.

There's an important class of problem that can only be found by someone
who is *not* a specialist - that is to say wording that's perfectly
clear and unambiguous to someone very familiar with the topic, but is
quite unclear to someone who isn't. This matters because we (presumably)
want our specifications to be useful to people who are implementing or
deploying them without already being members of the inner circle.

Just to be specific, here is a piece of text that came out of a WG
not so long ago. I have bowdlerised it:

"The Foobar standards [RFCxxx], [RFCyyy] provide useful generic
functionality like blah, blah and blah for reducing the overhead in
Boofar networks.  This functionality can be partly applied to Bleep."

That was it - a third party implementing Bleep was apparently supposed
to guess which bits of those RFCs applied where.

This led to a DISCUSS and seven months of delay before that "partly"
was disambiguated. Was that inappropriate out-of-area review?

   Brian

From fred@cisco.com  Mon Apr 15 08:29:19 2013
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 6012E21F9387 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 08:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.507
X-Spam-Level: 
X-Spam-Status: No, score=-106.507 tagged_above=-999 required=5 tests=[AWL=4.092, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFIjkBBhGUIS for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 08:29:18 -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 A002121F912C for <ietf@ietf.org>; Mon, 15 Apr 2013 08:29:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2044; q=dns/txt; s=iport; t=1366039758; x=1367249358; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Pxe/ZYKzDSUH+iKlh6kltrnZw5G+6zw4LBpsRC7qUfo=; b=PD1yiUNTVEOnJlysGx7qEgPNmaMuUhR+RCmvVx7WXtVwiY+jMa+9A00m xGZ/Va9wLyATKEO9f6W8Bqw2YJVpmlWwEluhBPFH8Bv+QRGbCHStkzWrd Y6bk9t22MVeQXC8GwoCKqQlWP++Gb4cWXXjVDpD2rIxvXpO7L7rE0+Q4Q 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlUFALUbbFGtJXHA/2dsb2JhbABQgwbBOoEHFnSCHwEBAQMBOj8FCwIBCBgKFBAhESUCBA4FCId6AwkGsgkNiV2MRIIgAjEHgmBhA5UijViFHIMLgig
X-IronPort-AV: E=Sophos;i="4.87,476,1363132800"; d="scan'208";a="198984098"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-4.cisco.com with ESMTP; 15 Apr 2013 15:29:18 +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 r3FFTH3T024723 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 15 Apr 2013 15:29:18 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.02.0318.004; Mon, 15 Apr 2013 10:29:17 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: AQHONt3LK12oZOZLWkuxlgRbIFWFfJjRskCAgAA/MgCAAB23gIABuU4AgAPnFQCAAAYzgIAADE6A
Date: Mon, 15 Apr 2013 15:29:16 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B80DD21@xmb-rcd-x09.cisco.com>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org>	<51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com> <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com> <516C1277.9020304@gmail.com>
In-Reply-To: <516C1277.9020304@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.94.2]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7E1EC4202783734DA182E8CCC8CA8A2B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Andy Bierman <andy@yumaworks.com>, Paul Hoffman <paul.hoffman@vpnc.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: Mon, 15 Apr 2013 15:29:19 -0000

On Apr 15, 2013, at 7:45 AM, Brian E Carpenter <brian.e.carpenter@gmail.com=
>
 wrote:

> On 15/04/2013 15:23, Ted Lemon wrote:
>=20
> ...
>> So in practice, although I feel great sympathy for this position, I thin=
k it's mistaken.   I want the other ADs to comment on anything that they no=
tice that looks like a problem.
>=20
> There's an important class of problem that can only be found by someone
> who is *not* a specialist - that is to say wording that's perfectly
> clear and unambiguous to someone very familiar with the topic, but is
> quite unclear to someone who isn't. This matters because we (presumably)
> want our specifications to be useful to people who are implementing or
> deploying them without already being members of the inner circle.
>=20
> Just to be specific, here is a piece of text that came out of a WG
> not so long ago. I have bowdlerized it:
>=20
> "The Foobar standards [RFCxxx], [RFCyyy] provide useful generic
> functionality like blah, blah and blah for reducing the overhead in
> Boofar networks.  This functionality can be partly applied to Bleep."
>=20
> That was it - a third party implementing Bleep was apparently supposed
> to guess which bits of those RFCs applied where.
>=20
> This led to a DISCUSS and seven months of delay before that "partly"
> was disambiguated. Was that inappropriate out-of-area review?

No, it was not. But I would argue that "seven months" in an IESG review was=
 too long. At some point, the responsible AD should have written a set of q=
uestions and sent it back to whatever working group it came from with "don'=
t send it back until you have answered those questions". The ADs shouldn't =
have spent their time trying to have the conversation; they should only hav=
e ensured that they were OK with the result.

>From the working group side, it would *also* have been helpful to have the =
AD that raised the question get involved in the WG discussion, if only to e=
nsure that s/he was OK with the outcome when it came.=

From touch@isi.edu  Mon Apr 15 08:36:46 2013
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 4086921F93D7 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 08:36:46 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R5HdOzr+DI9H for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 08:36:45 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id C2C0621F93C6 for <ietf@ietf.org>; Mon, 15 Apr 2013 08:36:45 -0700 (PDT)
Received: from [192.168.1.96] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r3FFaChi013785 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Apr 2013 08:36:21 -0700 (PDT)
Message-ID: <516C1E6E.40602@isi.edu>
Date: Mon, 15 Apr 2013 08:36:14 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com> <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF discussion list <ietf@ietf.org>, Andy Bierman <andy@yumaworks.com>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Apr 2013 15:36:46 -0000

On 4/15/2013 7:23 AM, Ted Lemon wrote:

> So it's hard to see the harm in [late non-area input by the IESG],

It gives the IESG an exemption to participating in WG and IESG last call 
processes, which then frustrates the rest of the community that does not 
have this opportunity.

It says that the opinion of the IESG is more important than that of the 
WG; we should be judging ideas on their own merit, not their origin.

Joe

From Ted.Lemon@nominum.com  Mon Apr 15 09:09:45 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A29621F9361 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:09:45 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tocfk5zNTALC for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:09:44 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id CBDD621F86D3 for <ietf@ietf.org>; Mon, 15 Apr 2013 09:09:44 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUWwmSFWGq01ziSQNofbBl9zlAin9Fyeq@postini.com; Mon, 15 Apr 2013 09:09:44 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7343F1B80F0 for <ietf@ietf.org>; Mon, 15 Apr 2013 09:09:44 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6CEC0190061; Mon, 15 Apr 2013 09:09:44 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 15 Apr 2013 09:09:44 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: AQHONt2z+kkmqEfX7EKa70fj1HnPWJjR08iAgAA/MgCAAB26AIABuUoAgAPnEwCAABR5AIAACVuA
Date: Mon, 15 Apr 2013 16:09:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775149465@mbx-01.win.nominum.com>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com> <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com> <516C1E6E.40602@isi.edu>
In-Reply-To: <516C1E6E.40602@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <6B98C5CCFFA7DA4AAAEE959518FEB1D9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>, Andy Bierman <andy@yumaworks.com>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Apr 2013 16:09:45 -0000

On Apr 15, 2013, at 11:36 AM, Joe Touch <touch@isi.edu> wrote:
> It gives the IESG an exemption to participating in WG and IESG last call =
processes, which then frustrates the rest of the community that does not ha=
ve this opportunity.

You could equally say that the IETF last call frustrates the WG process, si=
nce a document can fail IETF last call, and this can be extremely frustrati=
ng for working groups.   Witness the fiasco in the MIF working group when t=
hey tried to advance a DHCP route option, for example.

The IETF last call process is important, but it's not a panacea.   Too many=
 documents come through the last call process for each one to get thorough =
review by every IETF participant.   The IESG are effectively the sacrificia=
l lambs of the IETF who have to read every single document on the IETF trac=
k that makes it through last call.

When you say that the IESG should not get special treatment, I think you ar=
e misunderstanding what is special about the treatment the IESG gets.   Wha=
t is special is that we are expected to review every document.   We could i=
mpose that requirement on the IETF as a whole.   If all IETF participants w=
ere willing to do that, then IETF review might well be effective enough to =
eliminate the need for the IESG.   But I don't think that's a realistic exp=
ectation, and I do not mean that as a criticism.   What you would have acco=
mplished if you did this would be to have turned every IETF participant int=
o an AD, working 35 hours a week on document review.


From elwynd@dial.pipex.com  Mon Apr 15 09:20:29 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 380D521F9339 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:20:29 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dEaWWkwq07w for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:20:28 -0700 (PDT)
Received: from mk-outboundfilter-1.mail.uk.tiscali.com (mk-outboundfilter-1.mail.uk.tiscali.com [212.74.114.37]) by ietfa.amsl.com (Postfix) with ESMTP id 4787521F912C for <ietf@ietf.org>; Mon, 15 Apr 2013 09:20:28 -0700 (PDT)
X-Trace: 717079984/mk-outboundfilter-1.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/81.187.254.249/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 81.187.254.249
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-Originating-Country: GB/UNITED KINGDOM
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAEAKonbFFRu/75/2dsb2JhbABKBsFWgmqBHYMTAQEFDioPHhMBEAsYCRYPCQMCAQIBRQYNAQcBAYgUrU2OKY1VHIEmB4NBA5cFhXKLH4MMgXI
X-IronPort-AV: E=Sophos;i="4.87,477,1363132800"; d="scan'208";a="717079984"
X-IP-Direction: OUT
Received: from weee-pc2.folly.org.uk (HELO [81.187.254.249]) ([81.187.254.249]) by smtp.pipex.tiscali.co.uk with ESMTP; 15 Apr 2013 17:20:20 +0100
Message-ID: <516C285A.2000202@dial.pipex.com>
Date: Mon, 15 Apr 2013 17:18:34 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu>	<A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org>	<51673C0E.2080700@isi.edu>	<8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com>	<CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com> <516C1277.9020304@gmail.com>
In-Reply-To: <516C1277.9020304@gmail.com>
Content-Type: text/plain; charset=windows-1252; 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, 15 Apr 2013 16:20:29 -0000

On 15/04/13 15:45, Brian E Carpenter wrote:
> On 15/04/2013 15:23, Ted Lemon wrote:
>
> ...
>> So in practice, although I feel great sympathy for this position, I think it's mistaken.   I want the other ADs to comment on anything that they notice that looks like a problem.
> There's an important class of problem that can only be found by someone
> who is *not* a specialist - that is to say wording that's perfectly
> clear and unambiguous to someone very familiar with the topic, but is
> quite unclear to someone who isn't. This matters because we (presumably)
> want our specifications to be useful to people who are implementing or
> deploying them without already being members of the inner circle.
>
> Just to be specific, here is a piece of text that came out of a WG
> not so long ago. I have bowdlerised it:
>
> "The Foobar standards [RFCxxx], [RFCyyy] provide useful generic
> functionality like blah, blah and blah for reducing the overhead in
> Boofar networks.  This functionality can be partly applied to Bleep."
>
> That was it - a third party implementing Bleep was apparently supposed
> to guess which bits of those RFCs applied where.
>
> This led to a DISCUSS and seven months of delay before that "partly"
> was disambiguated. Was that inappropriate out-of-area review?
>
>     Brian
On 15/04/13 14:09, Jari Arkko wrote:
> [Responding to Dave Crocker]
>> But what is tiring about this line of justification is its continuing failure to balance the analysis by looking at the costs and problems that come with it.  Does it provide regular and sufficient benefit to justify its considerable costs?
> Agreed.
I would say it usually does justify its costs - skimping on the QA is 
almost always a bad idea.  Speaking also from a gen-art perspective, 
getting a level of clarity and ease of use into a document may take a 
little while  for a number of reviewers and authors, but the costs  and 
benefits need to include the effort of implementers, testers and future 
users who will not appreciate getting a product that doesn't 
interoperate because the spec was unclear or they missed a point that 
might have been 'obvious' to the original authors.  The size of the 
affected population is much bigger after publication (at least if 
anybody actually cares about the RFC).

I have to say that in my experience the seven months of delay that Brian 
cites is rather unusual.   For the vast majority of documents, the sorts 
of clarification needed can be sorted out in a couple of rounds of 
email, and the results are unlikely to require recycling back to the 
WG.  That being said, there certainly are documents where I wonder why 
anybody seriously thought the document was ready for publication; trying 
to fix the process 'tail heaviness' (as Jari describes it) would help if 
we could find a way.  It could be argued that the tail process is just 
too polite.  Once a document embarks on the publication process we 
seemingly inevitably send it through all those reviews resulting in 
multitudinous politely phrased DISCUSSes and comments when what it 
really needs is a blunt refusal followed by some competent editing.

/Elwyn

From mcr@sandelman.ca  Mon Apr 15 09:24:02 2013
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 40C7B21F93BD for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:24:02 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C1LZ6Q4KpQdS for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:24:01 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id E1E8C21F912C for <ietf@ietf.org>; Mon, 15 Apr 2013 09:24:00 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id D876C20168 for <ietf@ietf.org>; Mon, 15 Apr 2013 12:33:57 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 3D78B638F7; Mon, 15 Apr 2013 12:23:38 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 2CDFD638E4 for <ietf@ietf.org>; Mon, 15 Apr 2013 12:23:38 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Purpose of IESG Review
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775149465@mbx-01.win.nominum.com>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com> <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com> <516C1E6E.40602@isi.edu> <8D23D4052ABE7A4490E77B1A012B630775149465@mbx-01.win.nominum.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 15 Apr 2013 12:23:38 -0400
Message-ID: <10853.1366043018@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, 15 Apr 2013 16:24:02 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Ted" =3D=3D Ted Lemon <Ted.Lemon@nominum.com> writes:
    Ted> You could equally say that the IETF last call frustrates the WG
    Ted> process, since a document can fail IETF last call, and this can
    Ted> be extremely frustrating for working groups.   Witness the
    Ted> fiasco in the MIF working group when they tried to advance a
    Ted> DHCP route option, for example.=20

Maybe we should have an IETF first call (for objections), rather than
last call.=20

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUWwpioqHRg3pndX9AQJTEwP/cVwmu01u2sJhov7H5R7QpFqvIYvtYAJM
ZjVrPe2oD2ieBEQL4HkzK7rKS1Y3iXP/8HlXI3WSInjUgQ7oeW74BaekkdVGkdj4
i/T0P3TMcYDn0i6nnn84kon1ZyWpcBK/nt+8qUXW5DtK+bcAGDVA4XMjK1hzoRay
J9Y01eJLHfI=
=aDHa
-----END PGP SIGNATURE-----
--=-=-=--

From touch@isi.edu  Mon Apr 15 09:27:35 2013
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 CE9BC21F93E1 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:27:35 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMzWl1CvNgkT for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:27:35 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5459121F94FD for <ietf@ietf.org>; Mon, 15 Apr 2013 09:27:35 -0700 (PDT)
Received: from [192.168.1.92] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r3FGQV01023978 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 15 Apr 2013 09:26:40 -0700 (PDT)
Subject: Re: Purpose of IESG Review
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=windows-1252
From: Joe Touch <touch@isi.edu>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775149465@mbx-01.win.nominum.com>
Date: Mon, 15 Apr 2013 09:26:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF49F4F7-DDA1-4388-B205-CCC012F6A2C4@isi.edu>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com> <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com> <516C1E6E.40602@isi.edu> <8D23D4052ABE7A4490E77B1A012B630775149465@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1503)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF discussion list <ietf@ietf.org>, Andy Bierman <andy@yumaworks.com>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Apr 2013 16:27:35 -0000

On Apr 15, 2013, at 9:09 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Apr 15, 2013, at 11:36 AM, Joe Touch <touch@isi.edu> wrote:
>> It gives the IESG an exemption to participating in WG and IESG last =
call processes, which then frustrates the rest of the community that =
does not have this opportunity.
>=20
> You could equally say that the IETF last call frustrates the WG =
process, since a document can fail IETF last call, and this can be =
extremely frustrating for working groups.   Witness the fiasco in the =
MIF working group when they tried to advance a DHCP route option, for =
example.

IETF LC does not come with a list of constraints of what is in and not =
in scope.

> The IETF last call process is important, but it's not a panacea.   Too =
many documents come through the last call process for each one to get =
thorough review by every IETF participant.   The IESG are effectively =
the sacrificial lambs of the IETF who have to read every single document =
on the IETF track that makes it through last call.

If docs get out of WG LC with no review, then there's a failure of IETF =
process. Every such doc should be read at least by a few independent =
reviewers, by the WG chairs, and by the ADs in that area.

The same failure can - and does - happen at the IESG level. We can =
continue to appoint groups with additional rounds of review, but IMO, =
they are scoped (and the IESG review guidance appears to back up that =
point).

Joe


From Ted.Lemon@nominum.com  Mon Apr 15 09:28:12 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8613F21F9434 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:28:12 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id euKxQMfI8W1O for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:28:12 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id 0933421F918F for <ietf@ietf.org>; Mon, 15 Apr 2013 09:28:12 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKUWwqmzU9NVVIVPwWgYGHUMEisYSWltTW@postini.com; Mon, 15 Apr 2013 09:28:12 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AC24F1B80F4 for <ietf@ietf.org>; Mon, 15 Apr 2013 09:28:11 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A3F73190061; Mon, 15 Apr 2013 09:28:11 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Mon, 15 Apr 2013 09:28:11 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Purpose of IESG Review
Thread-Topic: Purpose of IESG Review
Thread-Index: AQHONt2z+kkmqEfX7EKa70fj1HnPWJjR08iAgAA/MgCAAB26AIABuUoAgAPnEwCAABR5AIAACVuAgAAD4wCAAAFEAA==
Date: Mon, 15 Apr 2013 16:28:10 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751495C0@mbx-01.win.nominum.com>
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com> <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com> <516C1E6E.40602@isi.edu> <8D23D4052ABE7A4490E77B1A012B630775149465@mbx-01.win.nominum.com> <10853.1366043018@sandelman.ca>
In-Reply-To: <10853.1366043018@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <ADAD2A33FBF7C642BFED1FD8EB5F67AD@nominum.com>
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: Mon, 15 Apr 2013 16:28:12 -0000

On Apr 15, 2013, at 12:23 PM, Michael Richardson <mcr+ietf@sandelman.ca> wr=
ote:
> Maybe we should have an IETF first call (for objections), rather than
> last call.=20

I think that would look a lot like a DoS attack on the IETF, but it would b=
e nice if there were a way to make it work.


From stephen.farrell@cs.tcd.ie  Mon Apr 15 09:35:23 2013
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 A489921F9450 for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:35:23 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XSWv7Ploef6a for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 09:35:23 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0F82D21F943C for <ietf@ietf.org>; Mon, 15 Apr 2013 09:35:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 22070BE4C; Mon, 15 Apr 2013 17:34:58 +0100 (IST)
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 DzgV2WW8J0Ht; Mon, 15 Apr 2013 17:34:58 +0100 (IST)
Received: from [IPv6:2001:770:10:203:59aa:418:47ca:6300] (unknown [IPv6:2001:770:10:203:59aa:418:47ca:6300]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9F79DBE56; Mon, 15 Apr 2013 17:34:57 +0100 (IST)
Message-ID: <516C2C32.2050201@cs.tcd.ie>
Date: Mon, 15 Apr 2013 17:34:58 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Purpose of IESG Review
References: <5166F8BD.7010308@isi.edu> <A95F5634-91A5-4089-AD31-2D51AAF1BFBF@vpnc.org> <51673C0E.2080700@isi.edu> <8C48B86A895913448548E6D15DA7553B80A6A0@xmb-rcd-x09.cisco.com> <CABCOCHQCXQd=-X-gu0kAudfMAZayYrknPqLE8z17LDjbZN5U9g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775148CF9@mbx-01.win.nominum.com> <516C1E6E.40602@isi.edu> <8D23D4052ABE7A4490E77B1A012B630775149465@mbx-01.win.nominum.com> <AF49F4F7-DDA1-4388-B205-CCC012F6A2C4@isi.edu>
In-Reply-To: <AF49F4F7-DDA1-4388-B205-CCC012F6A2C4@isi.edu>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Andy Bierman <andy@yumaworks.com>, Paul Hoffman <paul.hoffman@vpnc.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: Mon, 15 Apr 2013 16:35:23 -0000

On 04/15/2013 05:26 PM, Joe Touch wrote:
> We can continue to appoint groups with additional rounds of review, but IMO, they are scoped (and the IESG review guidance appears to back up that point).

I think Joe is correct there. Another data point is that we
asked secdir (who currently have an 80% review rate for
documents) if they could see a way to get more done earlier
and thus reduce the review-all requirement for ADs. There were
a significant number of secdir folks who thought that increasing
the expectations on them might well mean getting far less
than 80% of documents reviewed - basically, they're also very
busy folks and our current 20% dropped-review rate might
just shoot up if we ask for too much.

I do wish there were a good way to reduce the AD review
burden and am happy to chat on or offlist with anyone who
has ideas, but I for one am not seeing anything obvious.

S.

From doug.mtview@gmail.com  Mon Apr 15 10:46:31 2013
Return-Path: <doug.mtview@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 AC6D021F942C for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 10:46:31 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tv2rUx0bqdtl for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 10:46:31 -0700 (PDT)
Received: from mail-da0-x235.google.com (mail-da0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id 296EF21F9425 for <ietf@ietf.org>; Mon, 15 Apr 2013 10:46:31 -0700 (PDT)
Received: by mail-da0-f53.google.com with SMTP id n34so2159601dal.40 for <ietf@ietf.org>; Mon, 15 Apr 2013 10:46:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=4lPrTW05ZbC+Z+RLQsFAsyRJ36oR1yDJGNY+YCHMLFM=; b=RdMv9bcUO1RD59ZRNpznXdWQs9VBNioEH/GuLm6UrRIJWoIf7pQ2kmMPjA6N5IWRnn 9sprlO3kI1gRQR8NAKcgUjC5GhkRGyWhixREezCRJIdhXJUdm0ZP5ryPU6KzrcX5mkKg 8D/ZfsgXGSixiRjQVqDKa2Bjq5duqLmGSg7V+zdOarW04l2552yQ9VGjs2NtExzCvwSl KQVzp3nqwmLOZSraaBUauRqBurd5HjI6ci6LIhTHR6/VDOFVKM+83f7cEV6/0nKX/hHL /FbT7Vo6rZyW2QUWIxcbjBtapPJl/yT97AGDjlO7u+a62EmdHj8VM2/a9hDVuFEk+rw5 9AdA==
X-Received: by 10.68.134.68 with SMTP id pi4mr30177404pbb.20.1366047990866; Mon, 15 Apr 2013 10:46:30 -0700 (PDT)
Received: from ?IPv6:2601:9:3180:3e:4151:c79b:7f04:bdd? ([2601:9:3180:3e:4151:c79b:7f04:bdd]) by mx.google.com with ESMTPS id ew5sm21125912pbc.9.2013.04.15.10.46.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Apr 2013 10:46:29 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775148A0C@mbx-01.win.nominum.com>
Date: Mon, 15 Apr 2013 10:46:26 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FBD25865-A4E0-41DD-AF3F-E32C76EB19DC@gmail.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org><6.2.5.6.2.20130411101504.0c42fed0@resistor.net><8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com><5167211A.8080807@wonderhamster.org><CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com><8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com><CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com><8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com><20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com><20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com><13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net><51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net><5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <00a401ce39b5$708d5f20$4001a8c0@gateway.2wire.net> <8D23D4052ABE7A4490E77B1A012B630775148A0C@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1503)
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, 15 Apr 2013 17:46:31 -0000

On Apr 15, 2013, at 6:50 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Apr 15, 2013, at 4:44 AM, t.p. <daedulus@btconnect.com> wrote:
>> So perhaps, to reduce the bias, e.g. towards "western white", any =
system
>> of choosing should give preference to the views of those who do not
>> attend IETF meetings, for whom judgement is based solely on the
>> contributions the person in question is seen to make - via the =
mailing
>> lists - towards open standards and running code.
>=20
> We could also all be assigned masks, vocoders and randomly-generated =
numbers at the beginning of each IETF, and go around wearing burlap =
robes.
>=20
> The problem with your solution is that at the moment it's actually =
pretty hard to participate in IETF without going to meetings.   It's a =
source of some frustration to me that despite having basically invented =
the Internet, the IETF still does business as if we were living in the =
pre-Internet era.   Three face-to-face meetings a year is a lot of =
carbon, and I think it also creates barriers for participation that are =
only readily surpassed by people who for whatever reason happen to have =
a great deal of advantage.   The degree of good fortune that allows me =
to participate in IETF as I do is breathtaking in its improbability.

Dear Ted,

Well said.  This speaks directly to what is limiting diversity, costs =
the Internet should remedy.  Although resources necessary to host =
meetings online are substantial, they pale in comparison with physical =
presence requirements.   I would have preferred if more females were in =
my all male engineering classes.  Lowering cost should reduce average =
participant age which should offer better gender/ethnic balance.=20

IMHO, diversity is more sensitive to a predominance of those wanting to =
generate ad revenue with a preference for dancing fruit, at the expense =
of security.  This has introduced i-frames, pdf with javascript, java, =
and many other types of unauthenticated active and proprietary content =
that remain major security issues.

How can the IETF increase the preference for clean, simple, open, and =
secure working code?

Perhaps registration forms could ask about roles as related to =
marketing, engineering, management, or support.  =46rom this, perhaps =
needed outreach can be better determined.

Regards,
Douglas Otis






From dharkins@lounge.org  Mon Apr 15 11:17:35 2013
Return-Path: <dharkins@lounge.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 78B2A21F966C for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 11:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J7XbntpumBWs for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 11:17:35 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 02BF121F966A for <ietf@ietf.org>; Mon, 15 Apr 2013 11:17:35 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 5FD90A888008; Mon, 15 Apr 2013 11:17:34 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Mon, 15 Apr 2013 11:17:34 -0700 (PDT)
Message-ID: <463e9ab5e2931397b989f87cd3e8e09d.squirrel@www.trepanning.net>
In-Reply-To: <5168C159.3050004@gmail.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com>
Date: Mon, 15 Apr 2013 11:17:34 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: "Melinda Shore" <melinda.shore@gmail.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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, 15 Apr 2013 18:17:35 -0000

On Fri, April 12, 2013 7:22 pm, Melinda Shore wrote:
> On 4/12/13 1:26 PM, Lou Berger wrote:
>> No argument from me, I'm just asking that a comment/position/question
>> that I don't understand be substantiated.
>
> And I'm telling you that I think the numbers are highly suggestive
> of bias.

  This is the classic fallacy of "Affirming the Consequent". And like
all fallacies, the reasoning is just plain wrong.

  Dan.



From jari.arkko@piuha.net  Mon Apr 15 11:52:12 2013
Return-Path: <jari.arkko@piuha.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 44D3D21F967D for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 11:52:12 -0700 (PDT)
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.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wdgAdkAyAGbx for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 11:52:11 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id F16E021F9673 for <ietf@ietf.org>; Mon, 15 Apr 2013 11:52:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1BD082CC5F; Mon, 15 Apr 2013 21:52:06 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kT73wsAzhVjZ; Mon, 15 Apr 2013 21:52:05 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4DFB02CC60; Mon, 15 Apr 2013 21:52:05 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51675819.9070302@gmail.com>
Date: Mon, 15 Apr 2013 21:52:04 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <0DDC7AF9-3D82-4E42-BACE-FE3948F41A3D@piuha.net>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1503)
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, 15 Apr 2013 18:52:12 -0000
X-List-Received-Date: Mon, 15 Apr 2013 18:52:12 -0000

Melinda,

> My own feeling is that if we were to find that the
> numbers supported the notion that there's bias
> present in the system we probably couldn't do anything
> about it without tearing the organization apart, so,

I am actually a little bit more optimistic about it, for a couple of =
reasons. First, it does not take genius to understand that we have =
biases. We all do. And I'm not trying to minimise the problem by =
presenting it as a common occurrence, but it is a fact that we have =
biases. People tend to prefer status quo, select similar people to =
themselves for various roles, carry society's stereotypes about various =
tasks, etc. Not surprising that the IETF has that too, but of course it =
does not make me happy. We can try to reduce the bias, however.

What helps with this is education, information, and good examples. As =
for the information & education part, I think the discussion we've had =
on diversity has already made the issue better highlighted. When =
something is in people's mind they tend to take it into account. FWIW, =
personnel discussions that I've been involved as the chair have had a =
very serious discussion about whether there was something we could do =
here to improve some aspect of diversity. Again, this isn't the only =
factor to consider, and most IETF leadership discussions are pretty =
constrained, have limited pools of volunteers to choose from, and so on. =
But I think we'll see the effect of that in coming years. There won't be =
a revolution, but I think we'll see some effect.=20

Secondly - and this is why I though some knowledge of our participant =
base would be useful - what I'd find useful is to get to a mode where we =
can look at progress. Is there a way to increase #countries #small =
companies #women etc? Be it about the participants or the leadership. =
Could we set a goal that we'll increase some aspect every year, 2014 to =
be better than 2013? It would be wonderful if we could track that =
somehow, while of course respecting people's privacy, not retaining any =
data, checking with experts, etc. And we could, of course, conduct a far =
more comprehensive surveys, I think we'll get to that as well. Later, =
perhaps when the design team comes up with some recommendations. And by =
their nature, such comprehensive surveys will be separate efforts. But =
Ray's question was prompted by the need to have the IETF-87 registration =
form up and running very soon and we wondered if some very basic =
information could be collected.

(Registration questions are not the only way to do this of course, =
separate surveys are a possibility. And I've experimented with using =
heuristics to make a guess of population's gender percentages. If you =
look at my document statistics page, you'll see the beginnings of some =
of the analysis. With truly massive error rates, of course. This could =
be repeated for meetings as well, I suppose. Not sure this is a viable =
approach, though.)

Jari


From dharkins@lounge.org  Mon Apr 15 17:00:36 2013
Return-Path: <dharkins@lounge.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 0D85421F93BD for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 17:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zvkOLlWNRJXG for <ietf@ietfa.amsl.com>; Mon, 15 Apr 2013 17:00:34 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id B7B1C21F93EE for <ietf@ietf.org>; Mon, 15 Apr 2013 17:00:32 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 9539DA888006; Mon, 15 Apr 2013 17:00:31 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Mon, 15 Apr 2013 17:00:32 -0700 (PDT)
Message-ID: <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net>
In-Reply-To: <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org>
Date: Mon, 15 Apr 2013 17:00:32 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: "Ray Pelletier" <rpelletier@isoc.org>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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, 16 Apr 2013 00:00:36 -0000

On Sat, April 13, 2013 8:18 am, Ray Pelletier wrote:
>
> On Apr 13, 2013, at 8:46 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
> wrote:
>
>>
>> On 04/13/2013 01:09 PM, Lou Berger wrote:
>>> gender bias
>> ...
>>> "western white guys".
>>
>> It may be that the latter phrase is a common term in
>> north America, (I dunno) but fwiw it grates on me at
>> least.
>>
>> If the issue we're talking about relates to gender,
>
> That's the question:
>
> Optional question:
> Check the block. Male/Female

  Under the belief of "garbage in, garbage out", I tend to lie on
these sorts of repugnant questions. I invite others to join me.
The more suspect the quality of the data, the less value it has.

  Dan.




From l.wood@surrey.ac.uk  Tue Apr 16 02:24:22 2013
Return-Path: <l.wood@surrey.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 2DE9921F8C3C for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 02:24:22 -0700 (PDT)
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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YRitvArBB0NN for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 02:24:21 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id AE74B21F8BE4 for <ietf@ietf.org>; Tue, 16 Apr 2013 02:24:20 -0700 (PDT)
Received: from [193.109.255.147:50625] by server-16.bemta-14.messagelabs.com id AE/8F-29589-3C81D615; Tue, 16 Apr 2013 09:24:19 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-72.messagelabs.com!1366104257!9038278!11
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28106 invoked from network); 16 Apr 2013 09:24:19 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-2.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 16 Apr 2013 09:24:19 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Tue, 16 Apr 2013 10:24:15 +0100
From: <l.wood@surrey.ac.uk>
To: <jari.arkko@piuha.net>
Date: Tue, 16 Apr 2013 10:24:14 +0100
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: Ac4547ysn+FFYp0zReK7tHGU4UTuPwAnzjk8
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E64@EXMB01CMS.surrey.ac.uk>
References: <20130412235542.8CEDA1A6AD@ld9781.wdf.sap.corp> <51693729.4010502@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775144AF2@mbx-01.win.nominum.com> <20130413125652.GA3818@cisco.com>, <240B7997-A9B8-4385-80B7-D9E8616DBD9F@piuha.net>
In-Reply-To: <240B7997-A9B8-4385-80B7-D9E8616DBD9F@piuha.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 16 Apr 2013 09:24:22 -0000

> Just think how much real-world networking and Internet work actually is
> being done around the world still in small companies, for instance, in ad=
dition to our large companies.

Well, yes.

I'm typing this in Tarawa where I've been upgrading the island's internet, =
and my chances of attending an
IETF are rather slim. I'll just have to leave it to all you first-world wes=
tern northern-hemisphere types,
no matter how much diversity you lack, and how much transport perspective y=
ou need.

Lloyd Wood
http://sat-net.com/L.Wood/

From worley@shell01.TheWorld.com  Tue Apr 16 08:52:03 2013
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 392A821F977A for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 08:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.415
X-Spam-Level: 
X-Spam-Status: No, score=-2.415 tagged_above=-999 required=5 tests=[AWL=0.565,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IVWzpetd14or for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 08:52:02 -0700 (PDT)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 559F621F973B for <ietf@ietf.org>; Tue, 16 Apr 2013 08:52:02 -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 r3GFpZ4m008482 for <ietf@ietf.org>; Tue, 16 Apr 2013 11:51:37 -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 r3GFpYMW2785062 for <ietf@ietf.org>; Tue, 16 Apr 2013 11:51:34 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r3GFpYgE2798122; Tue, 16 Apr 2013 11:51:34 -0400 (EDT)
Date: Tue, 16 Apr 2013 11:51:34 -0400 (EDT)
Message-Id: <201304161551.r3GFpYgE2798122@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.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, 16 Apr 2013 15:52:03 -0000

> > How can a memebr of staff in a company argue with the manager
> > about the manager's decisions or performance?
> 
> It is IMO the *obligation* of a professional to call his manager on
> wrong decisions or performance.

I've advocated the equivalent of the following opinion before
(http://www.ietf.org/mail-archive/web/ietf/current/msg77479.html), but
in the current context it bears repeating:  Here in the IETF we accept
that low-status people may argue regarding technical matters, but
reserve for high-status people having opinions about our procedures.

Dale

From Ted.Lemon@nominum.com  Tue Apr 16 10:49:26 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4643E21F96BC for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 10:49:26 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9QIHWAJruvij for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 10:49:25 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 81C6021F96B1 for <ietf@ietf.org>; Tue, 16 Apr 2013 10:49:25 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUW2PJL7RztohMmbKzDH6RqnySVKIKHcV@postini.com; Tue, 16 Apr 2013 10:49:25 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 33CF71B80FB for <ietf@ietf.org>; Tue, 16 Apr 2013 10:49:24 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 29B5B190061; Tue, 16 Apr 2013 10:49:24 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 16 Apr 2013 10:49:24 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOOrpFwg1p2tWRi02k4zw4onir7JjZlVmA
Date: Tue, 16 Apr 2013 17:49:23 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com>
In-Reply-To: <201304161551.r3GFpYgE2798122@shell01.TheWorld.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BDB226EAD096E6478796BF9E5BAF32DE@nominum.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: Tue, 16 Apr 2013 17:49:26 -0000

On Apr 16, 2013, at 11:51 AM, Dale R. Worley <worley@ariadne.com> wrote:
> I've advocated the equivalent of the following opinion before
> (http://www.ietf.org/mail-archive/web/ietf/current/msg77479.html), but
> in the current context it bears repeating:  Here in the IETF we accept
> that low-status people may argue regarding technical matters, but
> reserve for high-status people having opinions about our procedures.

I thought your original message (the one you cite above) was very good, but=
 I'm not sure I like the terms "low-status" and "high-status," simply becau=
se tey could be easily taken to mean something other than what I think you =
intend them to mean.


From abdussalambaryun@gmail.com  Tue Apr 16 21:51:24 2013
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 7163821F97B3 for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 21:51:24 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QjCTxlEepg3z for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 21:51:23 -0700 (PDT)
Received: from mail-da0-x236.google.com (mail-da0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 64F2F21F96BC for <ietf@ietf.org>; Tue, 16 Apr 2013 21:51:23 -0700 (PDT)
Received: by mail-da0-f54.google.com with SMTP id p1so591347dad.13 for <ietf@ietf.org>; Tue, 16 Apr 2013 21:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=R9Zard04JM68PlPZ0X39BEoTCu/ceXFzTEC+03/0W7M=; b=b7PvAY40TwP9jEKzm2B4s7MecyiNGRDQogc2FSGJwL4oHgVqxQ70NN5Ln/58AZlW2d vjLeekl3oGmb/S2S6DPjviSXE8R/22IrVyS4h5Nx8iAk8cQ65zV0YONRF+vLfCgkgNBJ /XnAyitvEh1X0zyHPL2qDKDK32njJL+BuIx3ARDTG1e3mdsl2EcN4B++qsLxusR4PIna CS6OydjDHHiwvjppJIJxefd6kQE/vmqCdxrLjhtQGoFu4NQIgcWET5ojIZ0wj0fp06Sh m0gq/uwqN8rT9J/KCneyyFStXIrUagSN6wq2i8GwxHlzOUddID45FZsRkCYmCImNN1T8 4viQ==
MIME-Version: 1.0
X-Received: by 10.68.209.162 with SMTP id mn2mr7035659pbc.190.1366174283025; Tue, 16 Apr 2013 21:51:23 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Tue, 16 Apr 2013 21:51:22 -0700 (PDT)
Date: Wed, 17 Apr 2013 06:51:22 +0200
Message-ID: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
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: Wed, 17 Apr 2013 04:51:24 -0000

>> My own feeling is that if we were to find that the
>> numbers supported the notion that there's bias
>> present in the system we probably couldn't do anything
>> about it without tearing the organization apart, so,
>
> Is there a way to increase #countries #small companies #women etc? Be
> it about the participants or the leadership. Could we set a goal that
> we'll increase some aspect every year, 2014 to be better than 2013?
>

IMO we can do many thing about it, if we discuss these issues into an I-D.
- There is a way to increase #women when they decide together as a
group what is missing, and what should be done,
- There is a way to increase #small companies when they are
accepted/involved in IETF WGs documents. If individuals are encouraged
then SMEs will be as well,
- There is a way to increase #countries/states when each have their
accepted access to the IETF WG system.

I may suggest that each WG system to not only have two chairs, but
also 5 administrated participants (for each continent, they may give
chance to SMEs access and new I-Ds) that should look into the
implementation/running-code of the IETF WG standards in real life.
They can look into countries/states challenges/involvement in such
work of the WG, to be documented if available. Countries will only
increase-in/use IETF if their SMEs are using IETF systems. Now it
seems that there are influences/directions from the industry/countries
to IETF WGs' work but not seen/clear to others.

For women, I think there must be at least 10% of women in the IETF
leadership, as we should not ignore that many research/SMEs in
industry are directed by women. They should publish an I-D related if
they are interested. Is IETF still directed by men or both?

AB

From l.wood@surrey.ac.uk  Tue Apr 16 22:41:20 2013
Return-Path: <l.wood@surrey.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 8080221F9762 for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 22:41:20 -0700 (PDT)
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=[AWL=-1.000, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CyplqTPL1scf for <ietf@ietfa.amsl.com>; Tue, 16 Apr 2013 22:41:19 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.143]) by ietfa.amsl.com (Postfix) with ESMTP id 5152B21F97C9 for <ietf@ietf.org>; Tue, 16 Apr 2013 22:41:19 -0700 (PDT)
Received: from [195.245.231.67:62785] by server-7.bemta-5.messagelabs.com id 51/43-12441-BF53E615; Wed, 17 Apr 2013 05:41:15 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-82.messagelabs.com!1366177274!30431419!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22741 invoked from network); 17 Apr 2013 05:41:15 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-4.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 17 Apr 2013 05:41:15 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Wed, 17 Apr 2013 06:41:06 +0100
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>, <ietf@ietf.org>
Date: Wed, 17 Apr 2013 06:38:42 +0100
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: Ac47J032RGV+aKE2SRuUp4XPQxXH5AABoSIr
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E69@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com>
In-Reply-To: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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, 17 Apr 2013 05:41:20 -0000

I am deeply offended by your '5 continents' and lack of inclusiveness.

Lloyd Wood
http://sat-net.com/L.Wood/

I come from a land down under.
________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Abdussalam=
 Baryun [abdussalambaryun@gmail.com]
Sent: 17 April 2013 05:51
To: ietf
Subject: Re: IETF Diversity Question on Berlin Registration?

>> My own feeling is that if we were to find that the
>> numbers supported the notion that there's bias
>> present in the system we probably couldn't do anything
>> about it without tearing the organization apart, so,
>
> Is there a way to increase #countries #small companies #women etc? Be
> it about the participants or the leadership. Could we set a goal that
> we'll increase some aspect every year, 2014 to be better than 2013?
>

IMO we can do many thing about it, if we discuss these issues into an I-D.
- There is a way to increase #women when they decide together as a
group what is missing, and what should be done,
- There is a way to increase #small companies when they are
accepted/involved in IETF WGs documents. If individuals are encouraged
then SMEs will be as well,
- There is a way to increase #countries/states when each have their
accepted access to the IETF WG system.

I may suggest that each WG system to not only have two chairs, but
also 5 administrated participants (for each continent, they may give
chance to SMEs access and new I-Ds) that should look into the
implementation/running-code of the IETF WG standards in real life.
They can look into countries/states challenges/involvement in such
work of the WG, to be documented if available. Countries will only
increase-in/use IETF if their SMEs are using IETF systems. Now it
seems that there are influences/directions from the industry/countries
to IETF WGs' work but not seen/clear to others.

For women, I think there must be at least 10% of women in the IETF
leadership, as we should not ignore that many research/SMEs in
industry are directed by women. They should publish an I-D related if
they are interested. Is IETF still directed by men or both?

AB

From jari.arkko@piuha.net  Wed Apr 17 01:25:44 2013
Return-Path: <jari.arkko@piuha.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 4FD9C21F8A80 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 01:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQlzj1fm8So1 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 01:25:43 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 827D921F844F for <ietf@ietf.org>; Wed, 17 Apr 2013 01:25:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 92DD12CC50; Wed, 17 Apr 2013 11:25:42 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id azADzekbm-Kg; Wed, 17 Apr 2013 11:25:42 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 236862CC3C; Wed, 17 Apr 2013 11:25:42 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com>
Date: Wed, 17 Apr 2013 11:25:43 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <465602F9-A251-475A-9BC3-1AD4DAB5E2E9@piuha.net>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1503)
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, 17 Apr 2013 08:25:44 -0000

AB,

I think we do not want to change the nature of the IETF, we will still =
go with organisation that is designed around what needs to be achieved. =
Two working group chairs is a good, well working setup from a practical =
management standpoint. We've seen examples elsewhere of what happens =
when there's country-based voting and other things where geography or =
political considerations have been taken too far.

(But we do of course increase the diversity of all the people involved =
in the process, whether participant or WG chair or other.)

Jari


From abdussalambaryun@gmail.com  Wed Apr 17 03:43:32 2013
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 DAE8121F8825 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 03:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkmUC5TzbrPN for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 03:43:29 -0700 (PDT)
Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) by ietfa.amsl.com (Postfix) with ESMTP id 75B5A21F8AF8 for <ietf@ietf.org>; Wed, 17 Apr 2013 03:43:28 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id kq13so871734pab.1 for <ietf@ietf.org>; Wed, 17 Apr 2013 03:43:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=6enRLHBRgi7AKNPc8/pVgNglcHjPgySMClwGzFd2Ji8=; b=QDa/mmPM/rbrlwxEwzEkXK4Mq9lnUxT0+VqWeW6TSGDfcIEhvL6WJZQoqs6zcuvmAh XqnCwGDi8jtYYDNyosAcMOqLAoQqkuvv7MRjn1Q+lSTIu9VqOaC3hz+xzcV7gQVG/WAa 3HOZ8y4ybNKDe/aSBB6K2kTI+lCeZoTl6dhdgehgNUaS3nfWr4eXCivuOHx7sOmKfNnr hZhsfTa+M7ZumxrfUaooWbj5BIswj634KanNPPCGYm12YdWPeD4CXvMs6MCj9qXtay5b yIYaktivBjumHufdRG17ldJIOr48qnBL3Xwgyo5sYoAZAU50TWXI4GcKQmyIN7VoxY1m dj9Q==
MIME-Version: 1.0
X-Received: by 10.66.222.228 with SMTP id qp4mr8168083pac.113.1366195408270; Wed, 17 Apr 2013 03:43:28 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Wed, 17 Apr 2013 03:43:28 -0700 (PDT)
Date: Wed, 17 Apr 2013 12:43:28 +0200
Message-ID: <CADnDZ88JCxsOhLu4GJZ5krdWLKH08Csj350xV0J_bLj_TQGZHw@mail.gmail.com>
Subject: Where was the standard demanded and how can it be continued used in other?
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: Wed, 17 Apr 2013 10:43:33 -0000

IMO, may be better to add tasks to WG chairs to support the implementations
of their WG standards within the community (this helps SMEs/cities to
implement or
standard). Producing standards is a responsibility and supporting
their implementations in the community is another. For example one
protocol [1] is an IETF general purpose standard but in some cities
[2] they may be implementing it in more specific way. Still one
informational I-D [3] is not adopted by the IETF WG, which I think
needs to be encouraged (draft expired not renewed).

[1] http://tools.ietf.org/html/draft-ietf-manet-olsrv2-19
[2] http://www.ietf.org/mail-archive/web/manet/current/msg13655.html
[3] http://tools.ietf.org/html/draft-funkfeuer-manet-olsrv2-etx-01

So when we make a standard should we document *where* it is more
demanded, or do we leave the demand open and let the community find
out *where-used* by research,

AB

On 4/17/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
>>> My own feeling is that if we were to find that the
>>> numbers supported the notion that there's bias
>>> present in the system we probably couldn't do anything
>>> about it without tearing the organization apart, so,
>>
>> Is there a way to increase #countries #small companies #women etc? Be
>> it about the participants or the leadership. Could we set a goal that
>> we'll increase some aspect every year, 2014 to be better than 2013?
>>
>
> IMO we can do many thing about it, if we discuss these issues into an I-D.
> - There is a way to increase #women when they decide together as a
> group what is missing, and what should be done,
> - There is a way to increase #small companies when they are
> accepted/involved in IETF WGs documents. If individuals are encouraged
> then SMEs will be as well,
> - There is a way to increase #countries/states when each have their
> accepted access to the IETF WG system.
>
> I may suggest that each WG system to not only have two chairs, but
> also 5 administrated participants (for each continent, they may give
> chance to SMEs access and new I-Ds) that should look into the
> implementation/running-code of the IETF WG standards in real life.
> They can look into countries/states challenges/involvement in such
> work of the WG, to be documented if available. Countries will only
> increase-in/use IETF if their SMEs are using IETF systems. Now it
> seems that there are influences/directions from the industry/countries
> to IETF WGs' work but not seen/clear to others.
>
> For women, I think there must be at least 10% of women in the IETF
> leadership, as we should not ignore that many research/SMEs in
> industry are directed by women. They should publish an I-D related if
> they are interested. Is IETF still directed by men or both?
>
> AB
>

From jdrake@juniper.net  Wed Apr 17 04:56:55 2013
Return-Path: <jdrake@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 5848321F8ADC for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 04:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.392
X-Spam-Level: 
X-Spam-Status: No, score=-3.392 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L1Vhsf5194gi for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 04:56:54 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id AE1E121F8A8A for <ietf@ietf.org>; Wed, 17 Apr 2013 04:56:54 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUW6N/vfMxfyxGxy7dXU4Ou1MzC+Tdi4S@postini.com; Wed, 17 Apr 2013 04:56:54 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; Wed, 17 Apr 2013 04:54:23 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Wed, 17 Apr 2013 04:54:22 -0700
Received: from DB8EHSOBE007.bigfish.com (213.199.154.188) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 17 Apr 2013 05:04:14 -0700
Received: from mail116-db8-R.bigfish.com (10.174.8.234) by DB8EHSOBE007.bigfish.com (10.174.4.70) with Microsoft SMTP Server id 14.1.225.23; Wed, 17 Apr 2013 11:54:20 +0000
Received: from mail116-db8 (localhost [127.0.0.1])	by mail116-db8-R.bigfish.com (Postfix) with ESMTP id 7D21C4E0716	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Wed, 17 Apr 2013 11:54:20 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT005.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -23
X-BigFish: PS-23(zz9371I542I1432Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz1033IL8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1155h)
Received: from mail116-db8 (localhost.localdomain [127.0.0.1]) by mail116-db8 (MessageSwitch) id 1366199658927289_24743; Wed, 17 Apr 2013 11:54:18 +0000 (UTC)
Received: from DB8EHSMHS028.bigfish.com (unknown [10.174.8.240])	by mail116-db8.bigfish.com (Postfix) with ESMTP id D690C240045; Wed, 17 Apr 2013 11:54:18 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS028.bigfish.com (10.174.4.38) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 17 Apr 2013 11:54:18 +0000
Received: from BL2PRD0510MB349.namprd05.prod.outlook.com ([169.254.1.181]) by BL2PRD0510HT005.namprd05.prod.outlook.com ([10.255.100.40]) with mapi id 14.16.0293.003; Wed, 17 Apr 2013 11:54:11 +0000
From: John E Drake <jdrake@juniper.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHOOyc1KuoMqWAFtkmNWH3bnXdwmJjaTf5g
Date: Wed, 17 Apr 2013 11:54:10 +0000
Message-ID: <0182DEA5604B3A44A2EE61F3EE3ED69E1D4A54A1@BL2PRD0510MB349.namprd05.prod.outlook.com>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com>
In-Reply-To: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.224.53]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%GMAIL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
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: Wed, 17 Apr 2013 11:56:55 -0000

AB,

Is it true that you are really Professor Irwin Corey?

Irrespectively Yours,

John


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Abdussalam Baryun
> Sent: Tuesday, April 16, 2013 9:51 PM
> To: ietf
> Subject: Re: IETF Diversity Question on Berlin Registration?
>=20
> >> My own feeling is that if we were to find that the numbers supported
> >> the notion that there's bias present in the system we probably
> >> couldn't do anything about it without tearing the organization
> apart,
> >> so,
> >
> > Is there a way to increase #countries #small companies #women etc? Be
> > it about the participants or the leadership. Could we set a goal that
> > we'll increase some aspect every year, 2014 to be better than 2013?
> >
>=20
> IMO we can do many thing about it, if we discuss these issues into an
> I-D.
> - There is a way to increase #women when they decide together as a
> group what is missing, and what should be done,
> - There is a way to increase #small companies when they are
> accepted/involved in IETF WGs documents. If individuals are encouraged
> then SMEs will be as well,
> - There is a way to increase #countries/states when each have their
> accepted access to the IETF WG system.
>=20
> I may suggest that each WG system to not only have two chairs, but also
> 5 administrated participants (for each continent, they may give chance
> to SMEs access and new I-Ds) that should look into the
> implementation/running-code of the IETF WG standards in real life.
> They can look into countries/states challenges/involvement in such work
> of the WG, to be documented if available. Countries will only increase-
> in/use IETF if their SMEs are using IETF systems. Now it seems that
> there are influences/directions from the industry/countries to IETF
> WGs' work but not seen/clear to others.
>=20
> For women, I think there must be at least 10% of women in the IETF
> leadership, as we should not ignore that many research/SMEs in industry
> are directed by women. They should publish an I-D related if they are
> interested. Is IETF still directed by men or both?
>=20
> AB



From jmpolk@cisco.com  Wed Apr 17 07:08:16 2013
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 0AA7121F8691 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 07:08:16 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fwsr9rVhb6Cq for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 07:08:15 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4BBE321F8681 for <ietf@ietf.org>; Wed, 17 Apr 2013 07:08:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1984; q=dns/txt; s=iport; t=1366207695; x=1367417295; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=1k5PdsEc81ugMj7LvI/PF7PUjnUiQ4Lj42u3okAUozU=; b=WwG7N3KTnMiPnY33128hPdJrT4Lq/pgscj8OzGz9lollizRS1W/kB38W IoZiD7Dc7pqFGXLyheraZXqwNbHBySxNpPrZAFJadPpnG1oNR2b+W7Hfz yegUcGdG+QLfI5UftthU8Irxku05NmSmuhhFA1qH/EpPIr5RuNpZYB2ZG Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAHirblGtJXHB/2dsb2JhbABQgwbBQoEEFnSCHwEBAQQ4Ak8HBBgJFRAPCj4GASuHe71PjyGDRgOJBp8Ugyke
X-IronPort-AV: E=Sophos;i="4.87,492,1363132800"; d="scan'208";a="196821757"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 17 Apr 2013 14:08:14 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r3HE8EQ4030324 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Apr 2013 14:08:14 GMT
Message-Id: <201304171408.r3HE8EQ4030324@rcdn-core2-6.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 17 Apr 2013 09:08:14 -0500
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
From: James Polk <jmpolk@cisco.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.g mail.com>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Apr 2013 14:08:16 -0000

what you are suggesting is quotas and forced participation from a 
volunteer organization... are you serious?

At 11:51 PM 4/16/2013, Abdussalam Baryun wrote:
> >> My own feeling is that if we were to find that the
> >> numbers supported the notion that there's bias
> >> present in the system we probably couldn't do anything
> >> about it without tearing the organization apart, so,
> >
> > Is there a way to increase #countries #small companies #women etc? Be
> > it about the participants or the leadership. Could we set a goal that
> > we'll increase some aspect every year, 2014 to be better than 2013?
> >
>
>IMO we can do many thing about it, if we discuss these issues into an I-D.
>- There is a way to increase #women when they decide together as a
>group what is missing, and what should be done,
>- There is a way to increase #small companies when they are
>accepted/involved in IETF WGs documents. If individuals are encouraged
>then SMEs will be as well,
>- There is a way to increase #countries/states when each have their
>accepted access to the IETF WG system.
>
>I may suggest that each WG system to not only have two chairs, but
>also 5 administrated participants (for each continent, they may give
>chance to SMEs access and new I-Ds) that should look into the
>implementation/running-code of the IETF WG standards in real life.
>They can look into countries/states challenges/involvement in such
>work of the WG, to be documented if available. Countries will only
>increase-in/use IETF if their SMEs are using IETF systems. Now it
>seems that there are influences/directions from the industry/countries
>to IETF WGs' work but not seen/clear to others.
>
>For women, I think there must be at least 10% of women in the IETF
>leadership, as we should not ignore that many research/SMEs in
>industry are directed by women. They should publish an I-D related if
>they are interested. Is IETF still directed by men or both?
>
>AB


From lear@cisco.com  Wed Apr 17 07:52:51 2013
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 01F0E21E803F for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 07:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.198
X-Spam-Level: 
X-Spam-Status: No, score=-110.198 tagged_above=-999 required=5 tests=[AWL=0.401, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7xdaiDJaiYT0 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 07:52:50 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9A35121F8A48 for <ietf@ietf.org>; Wed, 17 Apr 2013 07:52:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=352; q=dns/txt; s=iport; t=1366210362; x=1367419962; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Czow/nq+h8P7fturPR6/UIn1xXuAYTZOVb+SESOfgq4=; b=QigNlLWyQ2pnToZHX0G8u8sl/dNsjhd45/kDtTfQBzUm8jYa/ciBQo1x Ix8QrkD8X6hIbHo1znBQ9Pmue8ezbPYIhf9O85vGxTfohwsZF9ZKwL8C7 DK1uQgaYAQJ7xjPdh6sYDcwNMUjR4YlQHaxYsY7Y7nv/OWoHCB7uUxx0y 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnQKAB+2blGQ/khR/2dsb2JhbABQgwaDZ70JBAMBgQMWdIIfAQEBAwEjVQEFCwsODAIFFgsCAgkDAgECASsaBg0BBwEBiAoGqwySTYEjjXcHgjOBEwOXBpEUgw06
X-IronPort-AV: E=Sophos;i="4.87,492,1363132800"; d="scan'208";a="82040981"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 17 Apr 2013 14:52:41 +0000
Received: from mctiny.local ([10.61.194.152]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3HEqdLe005330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Apr 2013 14:52:39 GMT
Message-ID: <516EB736.6060801@cisco.com>
Date: Wed, 17 Apr 2013 16:52:38 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Dan Harkins <dharkins@lounge.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net>
In-Reply-To: <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Wed, 17 Apr 2013 14:52:51 -0000

Dan,

On 4/16/13 2:00 AM, Dan Harkins wrote:

> Under the belief of "garbage in, garbage out", I tend to lie on these
> sorts of repugnant questions. I invite others to join me. The more
> suspect the quality of the data, the less value it has. Dan. 

Please don't.  We are trying to understand who we are.  Is that SO
unreasonable?

Eliot

From hotz@jpl.nasa.gov  Tue Apr 16 18:26:40 2013
Return-Path: <hotz@jpl.nasa.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E159721F972B; Tue, 16 Apr 2013 18:26:40 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5J-wm6mTU34a; Tue, 16 Apr 2013 18:26:40 -0700 (PDT)
Received: from mail.jpl.nasa.gov (mailhost.jpl.nasa.gov [128.149.139.106]) by ietfa.amsl.com (Postfix) with ESMTP id F0CDC21F96FF; Tue, 16 Apr 2013 18:26:39 -0700 (PDT)
Received: from laphotz.jpl.nasa.gov (laphotz.jpl.nasa.gov [128.149.133.44]) (authenticated (0 bits)) by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r3H1QI5Z008226 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Tue, 16 Apr 2013 18:26:19 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
From: "Henry B. Hotz" <hotz@jpl.nasa.gov>
In-Reply-To: <CD8FB284.60CB7%stefan@aaa-sec.com>
Date: Tue, 16 Apr 2013 18:26:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9407FAE5-DB04-4B2A-B621-719E8D278412@jpl.nasa.gov>
References: <CD8FB284.60CB7%stefan@aaa-sec.com>
To: Stefan Santesson <stefan@aaa-sec.com>
X-Mailer: Apple Mail (2.1503)
X-Source-Sender: hotz@jpl.nasa.gov
X-AUTH: Authorized
X-Mailman-Approved-At: Wed, 17 Apr 2013 08:19:15 -0700
Cc: pkix@ietf.org, Piyush Jain <piyush@ditenity.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: Wed, 17 Apr 2013 01:26:41 -0000

On Apr 13, 2013, at 4:24 PM, Stefan Santesson <stefan@aaa-sec.com> =
wrote:

>>> These are the three possible states of a serial number. It must =
always
>>> be in ONE of these states.
>> As long as you assume that a certificate signed by the CA cannot be
>> non-issued i.e. CA knows what certificates it issued.
>> If you break that assumption, you have to deal with the possibility =
of
>> different certificates with same serial numbers (after all =
certificates
>> are
>> getting issued without CA's knowledge). This implies that the same =
serial
>> number can be associated with a good certificate and a non-issued
>> certificate.
>>=20
>> Let me frame it in a different way. If you get a "good" response from =
a
>> responder that issues "revoked" for "non-issued", can you be sure =
that the
>> certificate you are checking is not a non-issued certificate?
>=20
> No, to take it to that level, you need a new white list extension.
> You see this from the wrong angle.
>=20
> This change is not intended to provide the client indisputable =
knowledge
> about whether a certificate is non-issued or not.
> It is intended to give the responder a means of causing the client to
> reject rather than accept something that is known not to be good.

Disagree.

The protocol is intended to provide information ("Status") about an =
identified cert (or serial number if you prefer) so an RP can make the =
best decision possible about how to treat it within the scope if its own =
application.  That means that the OCSP responder SHOULD NOT (IMO) =
conceal the distinction between non-issued and good, nor should it =
conceal the distinction between non-issued and revoked (for exactly the =
same reason).  Doing either one of those effectively prevents the =
information from one of the white- or black-lists from contributing to =
OCSP responses. =20

I don't think it's safe in the first place to assume we know what all =
the current clients do or want.  I likewise don't think it's safe to =
assume we know what they will do, should do, or want in the future.  It =
may be clear how to handle a white-listed or black-listed cert.  =
However, I can think of several different scenarios for how a non-issued =
cert ought to be handled.  All of that is outside the scope of OCSPs =
perview.

>>>> And also the client cannot be sure if
>>>> the CA delegated responder's certificate is good or non-issued. =
This
>>>> renders OCSP completely useless.
>>>=20
>>> I did not talk about responder certificates.
>>=20
>> You did not. But that does not make my statement any less relevant or
>> incorrect and strengthens Henry's point about this spec achieving =
what it
>> is trying to do.

I likewise haven't' addressed responder cert's as a special case. :-/

I need to study the spec more carefully.  IIUC Martin seems to imply =
that you can infer if a cert is white-list/black-list/neither based on =
new extensions, if enough of them are present.  IIUC Stefan seems to =
imply the opposite, though the extensions should tell you where the =
ambiguity is.  My read supported the latter, but I don't want to stake =
my reputation on it.

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

Assuming what Stefan implies, would people be happy if we updated the =
abstract/introduction to say that a "new" OCSP response, combined with =
the CRL would allow an RP to infer which of the three status's a cert =
has?

When I opposed this draft, I had not yet thought of this combination of =
protocols.  I see the combination as unnecessarily high-overhead, but a =
step forward.

------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu


From Johannes.Merkle@secunet.com  Wed Apr 17 05:41:08 2013
Return-Path: <Johannes.Merkle@secunet.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8026E21F8E34; Wed, 17 Apr 2013 05:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=0.930,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q8b3L9zRcEfm; Wed, 17 Apr 2013 05:41:08 -0700 (PDT)
Received: from a.mx.secunet.com (a.mx.secunet.com [195.81.216.161]) by ietfa.amsl.com (Postfix) with ESMTP id CDF6721F8D8D; Wed, 17 Apr 2013 05:41:07 -0700 (PDT)
Received: from localhost (alg1 [127.0.0.1]) by a.mx.secunet.com (Postfix) with ESMTP id F14621A009B; Wed, 17 Apr 2013 14:41:05 +0200 (CEST)
X-Virus-Scanned: by secunet
Received: from a.mx.secunet.com ([127.0.0.1]) by localhost (a.mx.secunet.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1ERd5IOSCR7f; Wed, 17 Apr 2013 14:41:04 +0200 (CEST)
Received: from mail-srv1.secumail.de (unknown [10.53.40.200]) by a.mx.secunet.com (Postfix) with ESMTP id D06841A0066; Wed, 17 Apr 2013 14:41:04 +0200 (CEST)
Received: from [10.208.1.73] ([10.208.1.73]) by mail-srv1.secumail.de with Microsoft SMTPSVC(6.0.3790.4675); Wed, 17 Apr 2013 14:41:05 +0200
Message-ID: <516E9860.2090703@secunet.com>
Date: Wed, 17 Apr 2013 14:41:04 +0200
From: Johannes Merkle <johannes.merkle@secunet.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Piyush Jain <piyush@ditenity.com>
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
References: <008201ce3878$a699c790$f3cd56b0$@ditenity.com> <CD8FB284.60CB7%stefan@aaa-sec.com> <009001ce38ab$8d019fa0$a704dee0$@ditenity.com>
In-Reply-To: <009001ce38ab$8d019fa0$a704dee0$@ditenity.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Apr 2013 12:41:05.0053 (UTC) FILETIME=[D3739CD0:01CE3B68]
X-Mailman-Approved-At: Wed, 17 Apr 2013 08:19:15 -0700
Cc: "'Henry B. Hotz'" <hotz@jpl.nasa.gov>, ietf@ietf.org, pkix@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Apr 2013 12:41:08 -0000

> Limitations
> ~~~~~~~~
> - Works only if attacker fraudulently issued a certificate with a serial
> that is not associated with a good certificate.


This can be remedied by using an extension in which a server providing white-list information conveys a hash of the
(genuine) certificate having this serial number. Note, that such an extension does not only exist but is already used in
the context of qualified certificates in Germany: CertHash (OID 1.3.36.8.3.13), defined in CommonPKI.

Johannes



From dharkins@lounge.org  Wed Apr 17 12:21:34 2013
Return-Path: <dharkins@lounge.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 DD67821F8804 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 12:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-Cl3xU+QgYN for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 12:21:32 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id B504D21F87D1 for <ietf@ietf.org>; Wed, 17 Apr 2013 12:21:28 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 4CF95A888004; Wed, 17 Apr 2013 12:21:28 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Wed, 17 Apr 2013 12:21:28 -0700 (PDT)
Message-ID: <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net>
In-Reply-To: <516EB736.6060801@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com>
Date: Wed, 17 Apr 2013 12:21:28 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: "Eliot Lear" <lear@cisco.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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: Wed, 17 Apr 2013 19:21:34 -0000

  Hi Elliot,

On Wed, April 17, 2013 7:52 am, Eliot Lear wrote:
> Dan,
>
> On 4/16/13 2:00 AM, Dan Harkins wrote:
>
>> Under the belief of "garbage in, garbage out", I tend to lie on these
>> sorts of repugnant questions. I invite others to join me. The more
>> suspect the quality of the data, the less value it has. Dan.
>
> Please don't.  We are trying to understand who we are.  Is that SO
> unreasonable?

  We already know "who we are". This question is trying to decide our
gender make up and nothing good can come of it.

  It will provide more "evidence" for people to make use of logical
fallacies-- "if P implies Q then look we now have evidence of Q
therefore P"-- which really have no place in an organization devoted
to engineering.

  And it will be used as a baseline for doing work towards some goal
that has not been justified, work whose very nature requires treating
people according to what they are instead of who they are.

   Look, bias stinks and when it exists its stench is detectable. I don't
recall seeing any evidence of bias being presented on this list. And I
don't believe there is any problem has been mentioned that we had or
have that is caused by this predominance of white men. It's just been
stated as a problem itself. We must have less white men. Why? Because,
that's why.

  This question is the first step down a path we really should not go
down. If I can't stop the question from being asked then all I can hope
for is that the resulting data are so obviously wrong that they will be
of no use to anyone-- e.g. Berlin registration is 63% female.

  regards,

  Dan.




From sm@resistor.net  Wed Apr 17 12:45:31 2013
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 21A7D21E808F for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 12:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WOZdS0m3MkWX for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 12:45:30 -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 895FE21E8064 for <ietf@ietf.org>; Wed, 17 Apr 2013 12:45:30 -0700 (PDT)
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 r3HJjP28000981 for <ietf@ietf.org>; Wed, 17 Apr 2013 12:45:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1366227930; bh=wBIGF+PhSloUyNAUnSlafMOXW1xQRXxoWtWgKgkFNeg=; h=Date:To:From:Subject:In-Reply-To:References; b=FRc745biI9i/jXgBKKryEG38TU3/MxMJL5POKL+hyb9Q2amaFOXQTZI9FhMSk5XJW YjCE8Oma/5hYKly95u88KSfct9AiMbwBq4Ap/DMhU/f3Qt0FeGhBihuFkdrOgWDp5H MztpPFvJyfSl8zuvo6CjivdW8AJtlNf9bMh5f8VA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1366227930; i=@resistor.net; bh=wBIGF+PhSloUyNAUnSlafMOXW1xQRXxoWtWgKgkFNeg=; h=Date:To:From:Subject:In-Reply-To:References; b=bC54enoKN1Iyp2YyKV7JvFhww5mIfI97rGDaa1mUFAgwPDJWFolC0jTwOknLFhIyS 9beGs959EsW4w70m0PNcZTDbsbwGjrj7VUaGz9Kta2oi9GRxok7ipMNJdE4O1GJhrb kG0jUve4yLlBlK0OB6tAJG9RL76byEuCskrsjZxY=
Message-Id: <6.2.5.6.2.20130417123145.0cb587d8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 17 Apr 2013 12:45:06 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: RE: IETF Diversity Question on Berlin Registration?
In-Reply-To: <0182DEA5604B3A44A2EE61F3EE3ED69E1D4A54A1@BL2PRD0510MB349.n amprd05.prod.outlook.com>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com> <0182DEA5604B3A44A2EE61F3EE3ED69E1D4A54A1@BL2PRD0510MB349.namprd05.prod.outlook.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, 17 Apr 2013 19:45:31 -0000

At 04:54 17-04-2013 it was written:
>Is it true that you are really Professor Irwin Corey?

As I was unfamiliar with the above I looked it up.

 From RFC 3184:

  "The work of the IETF relies on cooperation among a broad cultural
    diversity of peoples, ideas, and communication styles."

The comment may be humorous or something else depending on cultural background.

Regards,
-sm 


From lear@cisco.com  Wed Apr 17 12:48:20 2013
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 7744021F85F5 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 12:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.248
X-Spam-Level: 
X-Spam-Status: No, score=-110.248 tagged_above=-999 required=5 tests=[AWL=0.351, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKXL3u-Cvw0f for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 12:48:19 -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 5BA9621F85EE for <ietf@ietf.org>; Wed, 17 Apr 2013 12:48:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1584; q=dns/txt; s=iport; t=1366228099; x=1367437699; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=57sX2lz+EFCgtQQfzG0hCXRY8l9QqtFhVSCsI7Y3NJE=; b=HQHopF3Evwz290hj3K/vbkCx6Id3qY3VJmnyu32HmdCqky6WRWi6SXf3 bgefor+zYcMNh9I2dxS9f0GLJdFdWJypielPKMZ/LBVTQUDf1hADliDJJ pWxd0+ve/eKXOGZwEpCv164K+Dbwv+ou1b1+K9P6omwsPRuYrLU+voz8B k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAAT8blGQ/khM/2dsb2JhbABQgwaDZ70UgQQWdIIfAQEBAwEjVgULCw4KAgIFIQICDwIsGgYNAQcBAYgKBqp5kl6BI413B4IzgRMDlwaRFIMNOg
X-IronPort-AV: E=Sophos;i="4.87,495,1363132800"; d="scan'208";a="13393912"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 17 Apr 2013 19:48:17 +0000
Received: from mctiny.local ([10.61.194.152]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3HJmEUi007112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Apr 2013 19:48:15 GMT
Message-ID: <516EFC7E.90801@cisco.com>
Date: Wed, 17 Apr 2013 21:48:14 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Dan Harkins <dharkins@lounge.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net>
In-Reply-To: <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Wed, 17 Apr 2013 19:48:20 -0000

Dan,

On 4/17/13 9:21 PM, Dan Harkins wrote:
>   We already know "who we are".

I disagree.  We make a whole lot of assumptions about who we are, but we
don't actually know, and that's why the question is being asked.  I
would clarify that IMHO the only reason this question should be asked is
for demographic purposes, along with others.

>  This question is trying to decide our
> gender make up and nothing good can come of it.
>
>   It will provide more "evidence" for people to make use of logical
> fallacies-- "if P implies Q then look we now have evidence of Q
> therefore P"-- which really have no place in an organization devoted
> to engineering.

This would be putting the cart before the horse.  We first need to
understand facts.  If we don't understand facts, then people will
continue on assumptions.

>
>   And it will be used as a baseline for doing work towards some goal
> that has not been justified, work whose very nature requires treating
> people according to what they are instead of who they are.
>
>    Look, bias stinks and when it exists its stench is detectable. I don't
> recall seeing any evidence of bias being presented on this list. And I
> don't believe there is any problem has been mentioned that we had or
> have that is caused by this predominance of white men. It's just been
> stated as a problem itself. We must have less white men. Why? Because,
> that's why.

Nobody has proposed that, and I think you can put a bit more faith in
your peers to not make important decisions based on "because".

Eliot


From bmanning@isi.edu  Wed Apr 17 13:39:48 2013
Return-Path: <bmanning@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 4456821F86BA for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 13:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.138
X-Spam-Level: 
X-Spam-Status: No, score=-104.138 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_IMAGE_ONLY_12=2.46, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjQ6i--JGJy5 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 13:39:45 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id B874121F86AD for <ietf@ietf.org>; Wed, 17 Apr 2013 13:39:45 -0700 (PDT)
Received: from [192.168.0.3] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r3HKdLfq006915 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 17 Apr 2013 13:39:30 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_83F5CD8C-F062-4B19-A160-2DBF6C636650"
From: manning bill <bmanning@isi.edu>
In-Reply-To: <6.2.5.6.2.20130417123145.0cb587d8@resistor.net>
Date: Wed, 17 Apr 2013 13:39:20 -0700
Message-Id: <B47353DB-218E-4C95-BC00-198CB934BE57@isi.edu>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com> <0182DEA5604B3A44A2EE61F3EE3ED69E1D4A54A1@BL2PRD0510MB349.namprd05.prod.outlook.com> <6.2.5.6.2.20130417123145.0cb587d8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
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, 17 Apr 2013 20:39:48 -0000

--Apple-Mail=_83F5CD8C-F062-4B19-A160-2DBF6C636650
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 17April2013Wednesday, at 12:45, SM wrote:

> At 04:54 17-04-2013 it was written:
>> Is it true that you are really Professor Irwin Corey?
>=20
> As I was unfamiliar with the above I looked it up.
>=20
> =46rom RFC 3184:
>=20
> "The work of the IETF relies on cooperation among a broad cultural
>   diversity of peoples, ideas, and communication styles."
>=20
> The comment may be humorous or something else depending on cultural =
background.
>=20
> Regards,
> -sm=20


The Official Site Of Irwin Corey
www.irwincorey.org/
Official website of Prof. Irwin Corey, the world's foremost authority.=20=




--Apple-Mail=_83F5CD8C-F062-4B19-A160-2DBF6C636650
Content-Type: multipart/related;
	type="text/html";
	boundary="Apple-Mail=_0740F075-8373-40B7-996C-3F3B79300075"


--Apple-Mail=_0740F075-8373-40B7-996C-3F3B79300075
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; =
"><br><div><div>On 17April2013Wednesday, at 12:45, SM wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>At =
04:54 17-04-2013 it was written:<br><blockquote type=3D"cite">Is it true =
that you are really Professor Irwin Corey?<br></blockquote><br>As I was =
unfamiliar with the above I looked it up.<br><br>=46rom RFC =
3184:<br><br> "The work of the IETF relies on cooperation among a broad =
cultural<br> &nbsp;&nbsp;diversity of peoples, ideas, and communication =
styles."<br><br>The comment may be humorous or something else depending =
on cultural background.<br><br>Regards,<br>-sm =
<br></div></blockquote></div><br><div><br></div><div>The Official Site =
Of&nbsp;Irwin Corey<br>www.irwincorey.org/<br>Official website of =
Prof.&nbsp;Irwin Corey, the world's foremost =
authority.&nbsp;</div><div><img =
id=3D"d523c940-8a80-4dda-9d7d-ab9c73dd10c4" height=3D"136" width=3D"113" =
apple-width=3D"yes" apple-height=3D"yes" =
src=3D"cid:E3DE34EF-59B0-4351-8DD5-219C1A5956E1"></div><div><br></div></bo=
dy></html>=

--Apple-Mail=_0740F075-8373-40B7-996C-3F3B79300075
Content-Transfer-Encoding: base64
Content-Disposition: inline;
	filename=imgres.jpeg
Content-Type: image/jpeg;
	x-unix-mode=0600;
	name="imgres.jpeg"
Content-Id: <E3DE34EF-59B0-4351-8DD5-219C1A5956E1>

/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAkGBwgHBgkIBwgKCgkLDRYPDQwMDRsUFRAWIB0iIiAd
Hx8kKDQsJCYxJx8fLT0tMTU3Ojo6Iys/RD84QzQ5OjcBCgoKDQwNGg8PGjclHyU3Nzc3Nzc3Nzc3
Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3N//AABEIAIgAcQMBIgACEQED
EQH/xAAcAAABBAMBAAAAAAAAAAAAAAAAAQUGBwIDBAj/xAA8EAABAwMCAgcGAwcEAwAAAAABAAID
BAUREiEGMQcTIkFRYXEUMoGRobFCUuEVIyRigsHRCEPw8SUmM//EABkBAAIDAQAAAAAAAAAAAAAA
AAABAgMEBf/EACARAAIDAAMBAQEBAQAAAAAAAAABAgMRBBIhMVFBIhP/2gAMAwEAAhEDEQA/ALfw
jCzwjCRIwwkdhrS53IDdbMLluEpjh7PeO9MBtuFwmh0ui6ppGXOD3YGPUqO1XHToMt9kZrBxlsnP
9U18RXBzJ3hzslx2jPd5qFSsqri57gT1Zdgnl6KiVmF8K+xYcPSXaGamy0NVC9u7g4NPlzypNRXy
mrI2yQjVG4ZDg4FVhQWrrdRne3LgG7Nzkeac6anmsrSaJoMf4hpGQPLyUVctwslxWlqLQaQ4AtOc
jKCEy2KsqpYWGRrHRnmA7ttHjyT9hXp6ZWsNeCjC2YSYQIwwlwssJQEAYYSrLCEAdWPJIR5LZhYk
IFpqcSwZA380xcQV88FM7Tod2e4FuPiVISABl2w8VDOIqOariklkcQ1x0tAPvH0Sb8JR9ZW8k89f
WTv3/ePOd8jktrad1K1rH8n74Pl/2nhlBDRxTU8RxK3tOee4f8K4qlolZT42wPXAKxWPUdGj6ddr
qqIHqQ8daTsPBPUsrIIjrYXNOQcZJPoofQiu62ocOwzGItI2znfO3h4JwbJU11JHA+o0vgeHl3IP
A7neSzr6bvWmSex3Nwp42NDpGZLTq2c0j7HkppTvbLEx7SMEKH8P0giiZ1oDmnckO7ie7yU1iiEb
dI8V0anqOLfHrLBCEizISEFWlJijCVGEAJhCXBQgDr5pMYWZSIEa3t1gDmPBR7iiMx0jnR5c/PYa
PqVJO9clfRCraQH6CRpzjOyT9Q08ZUgqjOK2KQFs/Zz4gZB+uybvaCJ3NYMjkQR7pCdeMOH6ynr5
ailfLHpacTt2c523IKKWz2iCSZk7jLK2U9Y8nclYboNLTp8dxl8JU2qMNLNGWgSPZsfyg96bLVdb
bbqjQbpC3SNGlxac+XjlbzO2aJuTg6dLvTmuq12+kc8OMET5CdiYxt8VRDN9N/ueMmHBMPWwudgm
AH92CMaQQDj7qX4A5Jm4UhLKOY4wHS7fABPeF0KI5BHE5Mu1rMcJCN1lhGFcUGCAEqUIATCFkkQB
1ELEhJJI2NhfI9rGNGS5xwB8URyMlY2SN7XscMhzTkFAhQkOEk80NPE6WeWOKNoy573BrQPMlVZx
l00Wq29bS8PRi41Y2E52gafXm74fNMRJekXim08NW5v7QLH1NQ4Nhhxl2M9p+PABVoaB/WTy0rS4
aiXj8zTuHt8QR8iqvvN3uF/u0twuU7p6uZw7WMY8AB3AeC9G8LUEdfYoDKNMkbixr89puMclCyCn
HGXU2up6ivdWcMbg+CkXBdmluVxc6SaT2CH3i046x3eB5DvK4OkF9Jb3QRWxjqu4ukInZTtOjQBl
2o8g703Wyk4+NtoDnhm5w07QGtZFGC1uPzvPzxgLNXxsl6bbeYnD/P0sKx8V2Cvu09ioK2E1dKcd
W33XjG+k9+DkFSLmvG1bVuF1mrKV8kD3SmRjmuw5hJzsR/ZWRwr013W3NZT32nbc4RsJmkMmA8+5
30WzDmnoErFRLhrpI4Y4jkZBTV3s9U7YQVYEbnHwBzg/NS4gJAJhLhI9zYmF8jmsYBkuccAJWuDm
hzCHA7gg5BQMMISoRqFo0cYvp32Gsp55o2PkiJYxzwC4jfAHfyUMtfGEVjtDLfE0TVs73GmifkMY
MDLnHwyeQ3WPSpSzi70k8m9NJpa0j8JbuR8yCo1ForbzTxtjjLaNo7Y5lzgCRv6BZbLHGZ0KaYyq
wg97ufFXGV5qKOsqZauWF7/4dh0xM0k8m8vid1EnHkrJs4Fgtl4vFQW+0OLtAIzl7iQAPiq2fjbC
0Vz7GS2tQz9FY4tcHNOHA5BV1cNcRVN0t/s9E/qqVsAMpZ7xmeMubnwAH1VJKzejCpYbfHTt2f7c
4ux3gx/orCuH0klHTdVfbZStxpk9qkx/RGM/UqSVNHA2SofG3T1oAeByOBkJgL//AG2245shqh67
MTxfq1tBbKqpef8A5tJz8AkS/pQ/FIjHEFe2HHViUhuE0rZNIZZXyO957i4+pOVrwmVsyG24VpdG
/SvV2V7LfxFJJVW4nDJiS6SnH3c3y5qrWjdO9bYKyitlNcOxJTTMDtUZzoJ7nJNpfSSi2tR6I6Sq
109rt1PSSh0VZNrJadnsA2+BJCfKW50VrobbSTyfvZQ2ONjBqOQBnOOQGVTfBddXVNlo6eoOp1BB
IaTO+xOoA/LZS/gq2zXV1sqiAG0+t8rsb9og/HOFk7tWPDoKmP8AwXZ4WjjzCFr0+qFoyf4Yusf0
aOPLcbjw1VNYMyQt61njlv6ZVQ0VSaebrY4xrHI8lbPSFeGWbhaoqJZGsEz2U+onBAe4NcR5hpJ+
CqWFhFY+llBbNGe0MjBHcR5Hms3Jj/TVw5eOIzdI72MsVCyM6OuqHPcwd+B+qrkqa9JoeLnTDrA+
JkRjDQfdcMF30c1QorRSsrRm5EtsYimPRhUuZxRSU34JXl3yY5Q5STo9nFPxjbXuIAL3N382kf3V
pUizJn6eJKB3d/Ej6NP9lw9JldosFVCDhz5Gt5+Yz9lnWSabzTHmWvmdjPdoUT6Q67rSYQc/xLu/
waP8oJMhHMrdIImxRaDl5ade+2c7fRaCss5QQE71MOBrxJG99vnBlpXDUWHfAUO7088KucLvE2Mn
W9rgAPxHGcfRQsjsWXUT6zRa1soYYJ2S0UobC3cMPPHkrP4Pp4YLNG+AM0SuJAZyGDjH0KqSjuQZ
A8UY6+QtJI/DCOZc534WjmpZ0HXuO4WGtt/XF8lFVPcNR3MchLgceGdSy8et72Zr5c11UUWVshY5
b+ZC1aYMKc/1H1+mns1tDjhz5J3N9BpH3Ki9i4mtlztFPBe2uZV0bRGKhgOos8cjyAWrp7qJ5eP5
YpXExw00TYW9wBGT9SVXIeW8iR6FSaT8Yk2nqJNxjX2urFNHapppBDrMjpWbvc47u1bEk4A5bABR
hK5xdzWKa8Btt6wXXbaj2SvpqnJAila848AQVyLIb7IEWHc67/yckgds10hbnwLNvsofxBVOqbhJ
k9kO1D4gf4W6uuGp7HA+9SgH10kJurd5zvvpb9kE2/DmKRKUiCALfRz+zVEU4aHGNwdpJIB+S0Jc
oAkF24suNyo3UZdHBTPdrkZAzQJD/Njmph0AV3UcYz0ruVVSOAxyy0g/bKq9TroWEx6RLaYQSA2U
ybcm9Wd/nhA909N9Z5v+SEZH8yEsQzz5/qDt0sHGFPXkExVdK3B/mZkEfLCq0g+C9acf8IU3GNjd
RSuENTGespp8Z6t+OR8j3/ovON14F4ltl09gntFTJK52mN0MZex/mHDZMiRnCCrjsHQ1NDaqi48S
zNbKymkfHRRHOl4Yca3A42PcPmqcO6AEShIhAGxzy4DPcMIlfrkc7xWCRACpEJUADWlzg1oJJ2AH
es5YZIZHRyscx7Dpc1wwQfAhJFq6xvV515GnHPK9PcZdHVp4sp2TvPsVzDBiriYCXHH427avv5oA
8wtBzuvRXQlwp+xbC+6VkRbXXEAgOGDHED2Rjuzz+S1cKdDtpstU2rutSbpKw5jjdFoiafEjJ1fH
ZWVyAA7kDNn9Tvmha8lCNDTo1JM53ycoQkIZONa1tt4QvFU7/bpH49SMD6leQz9UiEwEQhCABCEI
AEoQhAD1wXRftHi2z0hxiWsjBz4agT9l64PM45IQkMxJRlCE2IMoQhRA/9k=

--Apple-Mail=_0740F075-8373-40B7-996C-3F3B79300075--

--Apple-Mail=_83F5CD8C-F062-4B19-A160-2DBF6C636650--

From worley@shell01.TheWorld.com  Wed Apr 17 13:40:05 2013
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 3A67B21E809F for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 13:40:05 -0700 (PDT)
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.424,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VvJCL5NAXDcJ for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 13:40:04 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id AEE6E21E809D for <ietf@ietf.org>; Wed, 17 Apr 2013 13:40:03 -0700 (PDT)
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 r3HKcNnr000973 for <ietf@ietf.org>; Wed, 17 Apr 2013 16:38:25 -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 r3HKcNgG2872631 for <ietf@ietf.org>; Wed, 17 Apr 2013 16:38:23 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r3HKcMgT2892908; Wed, 17 Apr 2013 16:38:22 -0400 (EDT)
Date: Wed, 17 Apr 2013 16:38:22 -0400 (EDT)
Message-Id: <201304172038.r3HKcMgT2892908@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com> (Ted.Lemon@nominum.com)
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.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: Wed, 17 Apr 2013 20:40:05 -0000

> From: Ted Lemon <Ted.Lemon@nominum.com>
> 
> On Apr 16, 2013, at 11:51 AM, Dale R. Worley <worley@ariadne.com> wrote:
> > I've advocated the equivalent of the following opinion before
> > (http://www.ietf.org/mail-archive/web/ietf/current/msg77479.html), but
> > in the current context it bears repeating:  Here in the IETF we accept
> > that low-status people may argue regarding technical matters, but
> > reserve for high-status people having opinions about our procedures.
> 
> I thought your original message (the one you cite above) was very
> good, but I'm not sure I like the terms "low-status" and
> "high-status," simply because tey could be easily taken to mean
> something other than what I think you intend them to mean.

We do have a status system within the IETF and generally one gains
status within that system by recognized technical work.  And on
certain sorts of issues, particularly changes in processes, we don't
listen well to people who don't have high status within that system.
In that regard, the IETF is far from egalitarian.

In regard to diversity issues, it is important to ask whether position
in the status system is directly affected by factors other than just
technical contribution.

Probably more important for diversity issues is that factors in a
person's life other than their outright technical ability can strongly
affect their ability to contribute to our technical work, and thus
achieve the status needed to be influential.

A more subtle problem is whether technical contribution correlates
well the skills needed for leadership positions -- does being a
quality technical contributor demonstrate the skills needed to be an
effective IAB member?  Although given the discussion around "IESG
review", it seems that the reward for gaining the leadership position
of IESG membership is becoming an extremely busy technical reviewer of
standards...

Dale

From bmanning@isi.edu  Wed Apr 17 13:47:43 2013
Return-Path: <bmanning@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 EAACB21F8700 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 13:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.368
X-Spam-Level: 
X-Spam-Status: No, score=-105.368 tagged_above=-999 required=5 tests=[AWL=1.231, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qSy39ssYjDGv for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 13:47:42 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 57FA521F86EA for <ietf@ietf.org>; Wed, 17 Apr 2013 13:47:42 -0700 (PDT)
Received: from [192.168.0.3] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r3HKkgaj008338 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 17 Apr 2013 13:46:51 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <6.2.5.6.2.20130417123145.0cb587d8@resistor.net>
Date: Wed, 17 Apr 2013 13:46:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <86EF35DE-11F2-473E-A25A-BBA1A5C5E2F6@isi.edu>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com> <0182DEA5604B3A44A2EE61F3EE3ED69E1D4A54A1@BL2PRD0510MB349.namprd05.prod.outlook.com> <6.2.5.6.2.20130417123145.0cb587d8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
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, 17 Apr 2013 20:47:43 -0000

On 17April2013Wednesday, at 12:45, SM wrote:

> At 04:54 17-04-2013 it was written:
>> Is it true that you are really Professor Irwin Corey?
>=20
> As I was unfamiliar with the above I looked it up.
>=20
> =46rom RFC 3184:
>=20
> "The work of the IETF relies on cooperation among a broad cultural
>   diversity of peoples, ideas, and communication styles."
>=20
> The comment may be humorous or something else depending on cultural =
background.
>=20
> Regards,
> -sm=20

I -think- your argument cuts both ways.   much of this thread, and a =
couple others of recent vintage, =20
come from one or two ernest individuals who have a fairly narrow view of =
how things work in the wide=20
world.  They appear to want to stamp out uncomfortable views and =
operational practice that does not
align with their world view.   The Irwin Corey reference might be a =
gentle reminder that one should not
take one's self too seriously, to seek sound, technically grounded =
solutions, and seek to become part=20
of the community instead of trying to force the community to fit your =
view=85. =20

(Irwin is a consummate observer of the human  condition)

/bill


From dcrocker@bbiw.net  Wed Apr 17 17:16:27 2013
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 47C7521E80AD; Wed, 17 Apr 2013 17:16:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id chfsNC5X6OyY; Wed, 17 Apr 2013 17:16:26 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD4821E8043; Wed, 17 Apr 2013 17:16:26 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3I0G70S028172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Apr 2013 17:16:08 -0700
Message-ID: <516F3B35.8020105@bbiw.net>
Date: Wed, 17 Apr 2013 17:15:49 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Alissa Cooper <acooper@cdt.org>, draft-iab-privacy-considerations.all@tools.ietf.org, IAB IAB <iab@iab.org>, IETF Discussion <ietf@ietf.org>
Subject: Re: Fwd: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
References: <BB682B03-F1E3-487D-B56D-7BDBEC4EAA78@cdt.org> <EE9BA586-42C8-4282-BE06-A0BE3B53B702@cdt.org>
In-Reply-To: <EE9BA586-42C8-4282-BE06-A0BE3B53B702@cdt.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Apr 2013 17:16:08 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Apr 2013 00:16:27 -0000

Alissa,


On 4/17/2013 10:23 AM, Alissa Cooper wrote:
> Hi Dave,
>
> Just wanted to make sure you saw this. I plan to submit the document
> to the IAB for publication approval next week.


hmmm.  I did see it, but now I can't find your original response, which
is probably why I didn't followup.  So thanks for the re-probe.

I've left a few snippets from your reply at the end, as basic context,
but I'll just comment in summary, rather than in-line.

The summary of the summary is pretty simple:  I do understand the
history, complexities and even controversy that make it difficult to
document specific choices, such as defining privacy.  But I submit that
due diligence for a document like this obligates the IAB to take some
basic, solid positions, in the service of making its guidance useful.


1. Audience

    We often wind up writing documents that work best for people who are
already relatively familiar with a topic.  As you know better than most,
writing for those new to a topic is a significantly different task.  I
certainly agree that it's challenging but I see it as the essence of
this draft.

    That is, I believe you intend this document primarily for those who
are less familiar with discussion and practice of "privacy"
considerations.  But this must begin with an understanding that they
don't really have a reliable, workable definition of the term.

    There are many different definitions and you note that even on the
IAB, for this draft, it has been challenging to settle on a definition.
  I'll submit that that should alert you to the increased need for this
document to offer a single, useful definition, rather than to cause you
to shy away from it.


2. Definition.

    The alternative that you've left the reader with is to have a basic
lack of comfort with the topic and a certainty of inconsistent
definition.  All the good guidance later in the document will depend
upon an inconsistent sense of when to apply it.

    In addition, the directive that they derive their version of the
definition from the detail later in the document is -- forgive me --
simply unreasonable extra work. It's the sort of thing done for an
academic texbook, not a guidance document.  This draft is an operational
tutorial, as well as a set of guidelines.  Tutoring for application
starts with explaining terms and "privacy" is the most essential term to
define.

    The exemplar definition I provided should be modified to cover
'organization' data as well as personal, but I think it's viable as a
working form.  That said, I don't care whether you use it, as long as
the document provides a meaningful definition that gives the /average/,
uninformed reader a pragmatic sense of what is inside the scope of
privacy and what is outside.


3. Privacy vs. Security

    The fact that the two topics overlap or that one can be viewed as a
subset of the other or that...  The fact that there is so much confusion
here again requires that the document give concrete guidance that
distinguishes what is security, as we use it for RFCs, and what is
privacy, as you intend to scope it for this draft and for future Privacy
Considerations work.

    My own view is that Security is largely a technical and mechanical
topic, while Privacy is primarily a human and social topic.  Within the
IETF, we deal with security issues primarily in terms of algorithms and
component technology.  I believe you intend Privacy to take a larger
view and think that's entirely appropriate, but also quite different.

    That privacy often plays heavily on the techniques of security does
present challenges.  But, for example, I think that 'confidentiality' is
not 'privacy'.  I'll state it differently:  If the IAB cannot agree on a
meaningful and simple statement that distinguishes between privacy and
confidentiality, then it ought to reconsider giving expert advice about
the handling of privacy considerations.

    To repeat:  In practice within the IETF, confidentiality mechanisms
are just that: mechanisms.  They are component techniques for protecting
data against unauthorized viewing.  I'd class privacy as a system-level
concern for protecting against leakage and unauthorized viewing.  The
latter, of course, sounds like confidentiality.  Frankly, I don't know
how to reconcile that.  But then, I'm not writing expert guidance...

d/






>> Privacy is the concern for protecting information of or about an
>> individual person.
>>
>> Tweak this or replace it entirely, but /please/ provide a concrete,
>> pragmatic definition that explicitly defines what is in scope and
>> what is out, for them to focus their considerations on.
>
> This suggestion has been debated at length within the IAB privacy
> program over the life of this document. Our thinking is that trying
> to define "privacy" in one sentence would be as counterproductive as
> trying to define "security" or "extensibility" in one sentence.



>> The typical writer and reader of RFCs is not experienced in the
>> topic of privacy.  They won't know what you mean either:  they
>> need very concrete guidance about the word's meaning.
>>
>> Telling me that different people mean different things with the
>> term merely assures me that I have no idea what /you/ mean unless
>> you tell me.  Having each reader make guesses about the meaning is
>> a way to
ensure non-interoperability of the construct.
>
> Per my note above, the expectation is that the document as a whole
will provide a rich explanation of what is meant by privacy.
...
>> Guidance can't be very helpful if the reader has no idea when to
apply it.
>
> If the reader is unsure about whether to go through the thought
> process outlined in section 7, there is no harm (other than the use
> of
the reader's time) in doing it and then finding out that a particular
specification is already solidly designed when it comes to privacy.



>> I strongly suggest that any explicit privacy discussion be
>> required
to be an entirely separate from the 'security considerations' section.
>>
>> My reasoning is simple:  This community sees 'security' in terms of
>> encryption and signing, traffic analysis, and other such
>> mechanical, relatively low-level components.  Privacy is an
>> entirely different and
broader and more human beast, even when its details devolve to these
familiar mechanics.
>>
>> At the least, making it a separate section will help writers and
readers to distinguish privacy from the security stuff we are used to
seeing discussed.
>
> I think sections 4 and 7 demonstrate that privacy and security are
interrelated at least in some respects.




>> Not sure whether this is a question or a suggestion; if it's the
>> latter, I'm not sure what to suggest:  privacy issues often
>> develop as a combinatorial problem -- 'correlation' as you note
>> farther down -- that
is, developing out of unpredicted integration of information from
discrete services.  While any specific IETF specification might have its
own, direct privacy issues needing consideration, where should
discussion of these combinatorial dangers be discussed?
>
> That is a good question and I'm not sure I know the answer. Of
> course there is nothing to prevent people from writing drafts about
> the
privacy considerations associated with the combination of discrete
services/protocols.






>>> 4.1. Combined Security-Privacy Threats
>>
>> The fact that you have a string like "Combined Security-Privacy"
supports the view that Privacy Considerations is distinct from Security
and should not be in the Security Considerations section…
>
> Actually I think it's the opposite. Section 4 makes concrete
distinctions between privacy threats that are already commonly covered
by security considerations and those that are not.

>>> 5.2. User Participation
>>>
>>>
>>> As explained in Section 4.2.5, data collection and use that
>>> happens "in secret," without the individual's knowledge, is apt
>>> to violate the individual's expectation of privacy and may
>>> create incentives for misuse of data.  As a result, privacy
>>> regimes tend to include provisions to require informing
>>> individuals about data collection and use and involving them in
>>> decisions about the treatment of their data.  In an engineering
>>> context, supporting the goal of user participation usually means
>>> providing ways for users to control the data that is shared about
>>> them.  It may also mean providing ways for users to signal how
>>> they expect their data to be used and shared.
>>
>> There is a serious downside to this.  It presumes that this burden
>> on users is reasonable.  For many scenarios, it isn't.  Rather, the
>> focus on user participation is often used as an alternative to the
>> difficult
work (or research) on mechanisms that require less user participation.
>
> I agree that sole reliance on user participation is undesirable. It's
> listed here as one of several protections, so sole reliance is not
> implied. For protocol design I would actually argue that we tend not
> to
think about user participation enough (whereas I agree that privacy
policy tends to focus on it too much).






>>> privacy impact of a system.  Although most IETF activities do not
>>> involve standardizing user interfaces or user-facing
>>> communications, in some cases understanding expected user
>>> interactions can be important for protocol design.  Unexpected
>>> user behavior may have an adverse impact on security and/or
>>> privacy.
>>
>> While a generically reasonable view, the challenge with its
>> application in the IETF is our general tendency to think that we
understand UI and UX issues, although few in the IETF actually have the
background for it.  For example we tend to think that simply giving
users more information is a universal palliative.  Most discussions here
about "expected user interactions" are simply wrong.  Worse, I've no
idea what to suggest to counter this for the draft.
>
> Yeah, I'm not sure the draft can fix this problem. But agree that
> it's a problem.






-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From l.wood@surrey.ac.uk  Thu Apr 18 01:31:49 2013
Return-Path: <l.wood@surrey.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 02ABB21F8F12 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 01:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.265
X-Spam-Level: 
X-Spam-Status: No, score=-5.265 tagged_above=-999 required=5 tests=[AWL=1.333,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WOcG5S9knNMn for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 01:31:48 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.116]) by ietfa.amsl.com (Postfix) with ESMTP id CCE3F21F8F0F for <ietf@ietf.org>; Thu, 18 Apr 2013 01:31:47 -0700 (PDT)
Received: from [193.109.255.147:39574] by server-12.bemta-14.messagelabs.com id 2F/74-05449-27FAF615; Thu, 18 Apr 2013 08:31:46 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-3.tower-72.messagelabs.com!1366273873!7754815!14
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14319 invoked from network); 18 Apr 2013 08:31:28 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-3.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 18 Apr 2013 08:31:28 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Thu, 18 Apr 2013 09:31:20 +0100
From: <l.wood@surrey.ac.uk>
To: <worley@ariadne.com>, <ietf@ietf.org>
Date: Thu, 18 Apr 2013 09:31:19 +0100
Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: Ac47q+KvFRt5olNJR4GkR48aOn27zAAYjzgu
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com>
In-Reply-To: <201304172038.r3HKcMgT2892908@shell01.TheWorld.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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: Thu, 18 Apr 2013 08:31:49 -0000

Not sure about the recognition for technical work.

To progress technical work, you have to go to meetings. To progress in the =
IETF (chair, AD, IESG) you have to go to meetings.

Keep turning up and don't be too obviously completely abysmal technically, =
and you can get a status dot on your badge.

The IETF is run by goers, and goers like goers.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Dale R. Wo=
rley [worley@ariadne.com]
Sent: 17 April 2013 21:38
To: ietf@ietf.org
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG=
     Review)

> From: Ted Lemon <Ted.Lemon@nominum.com>
>
> On Apr 16, 2013, at 11:51 AM, Dale R. Worley <worley@ariadne.com> wrote:
> > I've advocated the equivalent of the following opinion before
> > (http://www.ietf.org/mail-archive/web/ietf/current/msg77479.html), but
> > in the current context it bears repeating:  Here in the IETF we accept
> > that low-status people may argue regarding technical matters, but
> > reserve for high-status people having opinions about our procedures.
>
> I thought your original message (the one you cite above) was very
> good, but I'm not sure I like the terms "low-status" and
> "high-status," simply because tey could be easily taken to mean
> something other than what I think you intend them to mean.

We do have a status system within the IETF and generally one gains
status within that system by recognized technical work.  And on
certain sorts of issues, particularly changes in processes, we don't
listen well to people who don't have high status within that system.
In that regard, the IETF is far from egalitarian.

In regard to diversity issues, it is important to ask whether position
in the status system is directly affected by factors other than just
technical contribution.

Probably more important for diversity issues is that factors in a
person's life other than their outright technical ability can strongly
affect their ability to contribute to our technical work, and thus
achieve the status needed to be influential.

A more subtle problem is whether technical contribution correlates
well the skills needed for leadership positions -- does being a
quality technical contributor demonstrate the skills needed to be an
effective IAB member?  Although given the discussion around "IESG
review", it seems that the reward for gaining the leadership position
of IESG membership is becoming an extremely busy technical reviewer of
standards...

Dale

From ynir@checkpoint.com  Thu Apr 18 02:02:48 2013
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 A9CB621F8EFD for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 02:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.97
X-Spam-Level: 
X-Spam-Status: No, score=-9.97 tagged_above=-999 required=5 tests=[AWL=-0.629,  BAYES_00=-2.599, FB_YOU_CAN_BECOME=1.258, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vG8IOmEGq8OR for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 02:02:47 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 5153621F8EF7 for <ietf@ietf.org>; Thu, 18 Apr 2013 02:02:47 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r3I92Ksj003394; Thu, 18 Apr 2013 12:02:20 +0300
X-CheckPoint: {516FB609-8-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Thu, 18 Apr 2013 12:02:19 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOO6uAkYNXJKWRyEmIKVS5GuPId5jbdJGAgAAIsIA=
Date: Thu, 18 Apr 2013 09:02:19 +0000
Message-ID: <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.159]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9BD8C42EDFE37F43971D227827A4FE52@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: Thu, 18 Apr 2013 09:02:48 -0000

Not entirely true.

It is true that getting "management positions" (chairs, AD, NomCom) require=
s meeting attendance. But a non-attender can get recognition for quality te=
chnical points, and can even progress technical work. RFC 4478 was publishe=
d long before I attended my first meeting. My own working group (WebSec) ha=
s document authors who never attend meetings. In other areas there are freq=
uent and prolific contributors, who either never attended a meeting or have=
 quit attending them years ago. Even the directorates have such people.

So no, you probably can't get a dot for your badge without actually having =
one, but you can become "prominent" in the sense that people might say "thi=
s document hasn't had enough review. Let's ask so-and-so to read it", or "I=
'm putting together a design team for foo. Let's see if we can get so-and-s=
o to join"

Yoav

On Apr 18, 2013, at 11:31 AM, l.wood@surrey.ac.uk wrote:

>=20
> Not sure about the recognition for technical work.
>=20
> To progress technical work, you have to go to meetings. To progress in th=
e IETF (chair, AD, IESG) you have to go to meetings.
>=20
> Keep turning up and don't be too obviously completely abysmal technically=
, and you can get a status dot on your badge.
>=20
> The IETF is run by goers, and goers like goers.
>=20
> Lloyd Wood
> http://sat-net.com/L.Wood/
>=20
>=20
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Dale R. =
Worley [worley@ariadne.com]
> Sent: 17 April 2013 21:38
> To: ietf@ietf.org
> Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IE=
SG     Review)
>=20
>> From: Ted Lemon <Ted.Lemon@nominum.com>
>>=20
>> On Apr 16, 2013, at 11:51 AM, Dale R. Worley <worley@ariadne.com> wrote:
>>> I've advocated the equivalent of the following opinion before
>>> (http://www.ietf.org/mail-archive/web/ietf/current/msg77479.html), but
>>> in the current context it bears repeating:  Here in the IETF we accept
>>> that low-status people may argue regarding technical matters, but
>>> reserve for high-status people having opinions about our procedures.
>>=20
>> I thought your original message (the one you cite above) was very
>> good, but I'm not sure I like the terms "low-status" and
>> "high-status," simply because tey could be easily taken to mean
>> something other than what I think you intend them to mean.
>=20
> We do have a status system within the IETF and generally one gains
> status within that system by recognized technical work.  And on
> certain sorts of issues, particularly changes in processes, we don't
> listen well to people who don't have high status within that system.
> In that regard, the IETF is far from egalitarian.
>=20
> In regard to diversity issues, it is important to ask whether position
> in the status system is directly affected by factors other than just
> technical contribution.
>=20
> Probably more important for diversity issues is that factors in a
> person's life other than their outright technical ability can strongly
> affect their ability to contribute to our technical work, and thus
> achieve the status needed to be influential.
>=20
> A more subtle problem is whether technical contribution correlates
> well the skills needed for leadership positions -- does being a
> quality technical contributor demonstrate the skills needed to be an
> effective IAB member?  Although given the discussion around "IESG
> review", it seems that the reward for gaining the leadership position
> of IESG membership is becoming an extremely busy technical reviewer of
> standards...
>=20
> Dale
>=20
> Email secured by Check Point


From l.wood@surrey.ac.uk  Thu Apr 18 03:12:24 2013
Return-Path: <l.wood@surrey.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 D8D9D21F8E98 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 03:12:24 -0700 (PDT)
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=[AWL=-1.129, BAYES_00=-2.599, FB_YOU_CAN_BECOME=1.258, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6-qiutvzLfXk for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 03:12:24 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.170]) by ietfa.amsl.com (Postfix) with ESMTP id 3797121F8E99 for <ietf@ietf.org>; Thu, 18 Apr 2013 03:12:23 -0700 (PDT)
Received: from [195.245.230.131:26264] by server-10.bemta-3.messagelabs.com id 69/6D-19664-207CF615; Thu, 18 Apr 2013 10:12:18 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-78.messagelabs.com!1366279937!20320317!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8015 invoked from network); 18 Apr 2013 10:12:18 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-2.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 18 Apr 2013 10:12:18 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Thu, 18 Apr 2013 11:12:17 +0100
From: <l.wood@surrey.ac.uk>
To: <ynir@checkpoint.com>
Date: Thu, 18 Apr 2013 11:12:16 +0100
Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOO6uAkYNXJKWRyEmIKVS5GuPId5jbdJGAgAAIsICAAEJXWg==
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E6C@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>, <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com>
In-Reply-To: <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 18 Apr 2013 10:12:25 -0000

I've written RFCs without attending meetings; easy to do if the work is a a=
ligned with a workgroup.

That's fine if you're happy to be a technical resource with skills to be dr=
awn upon for problems set by others.

However, if you're sufficiently technical that you can set new technical di=
rections that are outside the scope of existing wgs -- well, the political =
enters the technical, and you need to fake being a goer to build interest a=
nd support for the direction, eg by holding a bof. Many existing "managers"=
 have run wgs, but have they even attempted to establish new technical dire=
ctions? If not, they're just bureaucrats. Safe pairs of hands. And probably=
 not that technical.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: Yoav Nir [ynir@checkpoint.com]
Sent: 18 April 2013 10:02
To: Wood L  Dr (Electronic Eng)
Cc: <worley@ariadne.com>; <ietf@ietf.org>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG=
     Review)

Not entirely true.

It is true that getting "management positions" (chairs, AD, NomCom) require=
s meeting attendance. But a non-attender can get recognition for quality te=
chnical points, and can even progress technical work. RFC 4478 was publishe=
d long before I attended my first meeting. My own working group (WebSec) ha=
s document authors who never attend meetings. In other areas there are freq=
uent and prolific contributors, who either never attended a meeting or have=
 quit attending them years ago. Even the directorates have such people.

So no, you probably can't get a dot for your badge without actually having =
one, but you can become "prominent" in the sense that people might say "thi=
s document hasn't had enough review. Let's ask so-and-so to read it", or "I=
'm putting together a design team for foo. Let's see if we can get so-and-s=
o to join"

Yoav

On Apr 18, 2013, at 11:31 AM, l.wood@surrey.ac.uk wrote:

>
> Not sure about the recognition for technical work.
>
> To progress technical work, you have to go to meetings. To progress in th=
e IETF (chair, AD, IESG) you have to go to meetings.
>
> Keep turning up and don't be too obviously completely abysmal technically=
, and you can get a status dot on your badge.
>
> The IETF is run by goers, and goers like goers.
>
> Lloyd Wood
> http://sat-net.com/L.Wood/
>
>
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Dale R. =
Worley [worley@ariadne.com]
> Sent: 17 April 2013 21:38
> To: ietf@ietf.org
> Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IE=
SG     Review)
>
>> From: Ted Lemon <Ted.Lemon@nominum.com>
>>
>> On Apr 16, 2013, at 11:51 AM, Dale R. Worley <worley@ariadne.com> wrote:
>>> I've advocated the equivalent of the following opinion before
>>> (http://www.ietf.org/mail-archive/web/ietf/current/msg77479.html), but
>>> in the current context it bears repeating:  Here in the IETF we accept
>>> that low-status people may argue regarding technical matters, but
>>> reserve for high-status people having opinions about our procedures.
>>
>> I thought your original message (the one you cite above) was very
>> good, but I'm not sure I like the terms "low-status" and
>> "high-status," simply because tey could be easily taken to mean
>> something other than what I think you intend them to mean.
>
> We do have a status system within the IETF and generally one gains
> status within that system by recognized technical work.  And on
> certain sorts of issues, particularly changes in processes, we don't
> listen well to people who don't have high status within that system.
> In that regard, the IETF is far from egalitarian.
>
> In regard to diversity issues, it is important to ask whether position
> in the status system is directly affected by factors other than just
> technical contribution.
>
> Probably more important for diversity issues is that factors in a
> person's life other than their outright technical ability can strongly
> affect their ability to contribute to our technical work, and thus
> achieve the status needed to be influential.
>
> A more subtle problem is whether technical contribution correlates
> well the skills needed for leadership positions -- does being a
> quality technical contributor demonstrate the skills needed to be an
> effective IAB member?  Although given the discussion around "IESG
> review", it seems that the reward for gaining the leadership position
> of IESG membership is becoming an extremely busy technical reviewer of
> standards...
>
> Dale
>
> Email secured by Check Point


From ynir@checkpoint.com  Thu Apr 18 07:30:51 2013
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 F2A1021F8F00 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 07:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.656
X-Spam-Level: 
X-Spam-Status: No, score=-9.656 tagged_above=-999 required=5 tests=[AWL=-0.315, BAYES_00=-2.599, FB_YOU_CAN_BECOME=1.258, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uw2fMgPrpkBV for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 07:30:49 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1E421F8E6B for <ietf@ietf.org>; Thu, 18 Apr 2013 07:30:49 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r3IEOGKo015960; Thu, 18 Apr 2013 17:28:31 +0300
X-CheckPoint: {5170017A-6-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Thu, 18 Apr 2013 17:18:05 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOO6uAkYNXJKWRyEmIKVS5GuPId5jbdJGAgAAIsICAAEJXWoAARRgg
Date: Thu, 18 Apr 2013 14:18:04 +0000
Message-ID: <4613980CFC78314ABFD7F85CC302772111A0F977@IL-EX10.ad.checkpoint.com>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>, <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E6C@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E6C@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.121]
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
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, 18 Apr 2013 14:30:51 -0000

Looking in Jari's statistics site, you have three RFCs. One of those has se=
veral co-authors that I recognize as current "goers". You also have a curre=
nt draft with several co-authors, but I have no idea whether they're "goers=
" or not. Anyway, you are not a hermit. Through the RFCs and drafts that yo=
u have co-authored, you know people who do attend.

You anyway can't get a really new technical direction all by yourself. You =
always need to form a group, whether that group is a "bar BoF" or a formal =
IETF mailing list, or whatever. I don't think you can get a new thing into =
the IETF without a group of 4-7 people, regardless of whether you attend th=
e meeting. The only advantage in attending is that it makes it easy to soci=
alize your idea and "assemble the avengers", but I've seen it done outside =
a meeting. As long as you have a "goer" in your team, you can move things f=
orward.

Yes, I attend because I think that makes me more effective. If for any reas=
on I were no longer able to attend, I think I would still participate meani=
ngfully.=20

-----Original Message-----
From: l.wood@surrey.ac.uk [mailto:l.wood@surrey.ac.uk]=20
Sent: Thursday, April 18, 2013 1:12 PM
To: Yoav Nir
Cc: worley@ariadne.com; ietf@ietf.org
Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IESG=
 Review)

I've written RFCs without attending meetings; easy to do if the work is a a=
ligned with a workgroup.

That's fine if you're happy to be a technical resource with skills to be dr=
awn upon for problems set by others.

However, if you're sufficiently technical that you can set new technical di=
rections that are outside the scope of existing wgs -- well, the political =
enters the technical, and you need to fake being a goer to build interest a=
nd support for the direction, eg by holding a bof. Many existing "managers"=
 have run wgs, but have they even attempted to establish new technical dire=
ctions? If not, they're just bureaucrats. Safe pairs of hands. And probably=
 not that technical.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: Yoav Nir [ynir@checkpoint.com]
Sent: 18 April 2013 10:02
To: Wood L  Dr (Electronic Eng)
Cc: <worley@ariadne.com>; <ietf@ietf.org>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG=
     Review)

Not entirely true.

It is true that getting "management positions" (chairs, AD, NomCom) require=
s meeting attendance. But a non-attender can get recognition for quality te=
chnical points, and can even progress technical work. RFC 4478 was publishe=
d long before I attended my first meeting. My own working group (WebSec) ha=
s document authors who never attend meetings. In other areas there are freq=
uent and prolific contributors, who either never attended a meeting or have=
 quit attending them years ago. Even the directorates have such people.

So no, you probably can't get a dot for your badge without actually having =
one, but you can become "prominent" in the sense that people might say "thi=
s document hasn't had enough review. Let's ask so-and-so to read it", or "I=
'm putting together a design team for foo. Let's see if we can get so-and-s=
o to join"

Yoav

On Apr 18, 2013, at 11:31 AM, l.wood@surrey.ac.uk wrote:

>
> Not sure about the recognition for technical work.
>
> To progress technical work, you have to go to meetings. To progress in th=
e IETF (chair, AD, IESG) you have to go to meetings.
>
> Keep turning up and don't be too obviously completely abysmal technically=
, and you can get a status dot on your badge.
>
> The IETF is run by goers, and goers like goers.
>
> Lloyd Wood
> http://sat-net.com/L.Wood/
>
>
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Dale=20
> R. Worley [worley@ariadne.com]
> Sent: 17 April 2013 21:38
> To: ietf@ietf.org
> Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IE=
SG     Review)
>
>> From: Ted Lemon <Ted.Lemon@nominum.com>
>>
>> On Apr 16, 2013, at 11:51 AM, Dale R. Worley <worley@ariadne.com> wrote:
>>> I've advocated the equivalent of the following opinion before=20
>>> (http://www.ietf.org/mail-archive/web/ietf/current/msg77479.html),=20
>>> but in the current context it bears repeating:  Here in the IETF we=20
>>> accept that low-status people may argue regarding technical matters,=20
>>> but reserve for high-status people having opinions about our procedures=
.
>>
>> I thought your original message (the one you cite above) was very=20
>> good, but I'm not sure I like the terms "low-status" and=20
>> "high-status," simply because tey could be easily taken to mean=20
>> something other than what I think you intend them to mean.
>
> We do have a status system within the IETF and generally one gains=20
> status within that system by recognized technical work.  And on=20
> certain sorts of issues, particularly changes in processes, we don't=20
> listen well to people who don't have high status within that system.
> In that regard, the IETF is far from egalitarian.
>
> In regard to diversity issues, it is important to ask whether position=20
> in the status system is directly affected by factors other than just=20
> technical contribution.
>
> Probably more important for diversity issues is that factors in a=20
> person's life other than their outright technical ability can strongly=20
> affect their ability to contribute to our technical work, and thus=20
> achieve the status needed to be influential.
>
> A more subtle problem is whether technical contribution correlates=20
> well the skills needed for leadership positions -- does being a=20
> quality technical contributor demonstrate the skills needed to be an=20
> effective IAB member?  Although given the discussion around "IESG=20
> review", it seems that the reward for gaining the leadership position=20
> of IESG membership is becoming an extremely busy technical reviewer of=20
> standards...
>
> Dale
>

From Ted.Lemon@nominum.com  Thu Apr 18 07:32:36 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBF6F21F8F22 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 07:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.965
X-Spam-Level: 
X-Spam-Status: No, score=-105.965 tagged_above=-999 required=5 tests=[AWL=-0.624, BAYES_00=-2.599, FB_YOU_CAN_BECOME=1.258, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IiUOeSL70Nai for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 07:32:36 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id F047C21F8F12 for <ietf@ietf.org>; Thu, 18 Apr 2013 07:32:35 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUXAEAzi7ssD2CldmfAPy6SHLxtwId9xS@postini.com; Thu, 18 Apr 2013 07:32:36 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 314DE1B80DC for <ietf@ietf.org>; Thu, 18 Apr 2013 07:32:35 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 27408190061; Thu, 18 Apr 2013 07:32:35 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 18 Apr 2013 07:32:35 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOO6uAwg1p2tWRi02k4zw4onir7JjcHDSAgAAIqYCAAFxHgA==
Date: Thu, 18 Apr 2013 14:32:34 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077514F1F0@mbx-01.win.nominum.com>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk> <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com>
In-Reply-To: <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B73D2B9959CF1A46896EB14D6180FFB0@nominum.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: Thu, 18 Apr 2013 14:32:36 -0000

On Apr 18, 2013, at 5:02 AM, Yoav Nir <ynir@checkpoint.com> wrote:
> but you can become "prominent" in the sense that people might say "this d=
ocument hasn't had enough review. Let's ask so-and-so to read it"

Yes, it's worth noting that working group chairs are often desperate for pe=
ople about whom they can say this, so whether you attend in person or not, =
if you are active on the mailing list and give good reviews and do good wor=
k, you will get asked for this kind of help, and that does mean that you ha=
ve high status.

I agree with Lloyd's criticism that you can't get everything this way, thou=
gh, because we don't give off-site non-attendees an easy turn at the mic.  =
 We do try, but it's not the same if you aren't there in person.


From dharkins@lounge.org  Thu Apr 18 08:17:22 2013
Return-Path: <dharkins@lounge.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 CCB8C21F8F4E for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 08:17:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9mGS1xAXzImE for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 08:17:22 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 2FA6321F8F58 for <ietf@ietf.org>; Thu, 18 Apr 2013 08:17:22 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id AA70DA888008; Thu, 18 Apr 2013 08:17:21 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Thu, 18 Apr 2013 08:17:21 -0700 (PDT)
Message-ID: <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net>
In-Reply-To: <516EFC7E.90801@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com>
Date: Thu, 18 Apr 2013 08:17:21 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: "Eliot Lear" <lear@cisco.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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, 18 Apr 2013 15:17:22 -0000

  Hi Eliot,

On Wed, April 17, 2013 12:48 pm, Eliot Lear wrote:
> Dan,
>
> On 4/17/13 9:21 PM, Dan Harkins wrote:
>>   We already know "who we are".
>
> I disagree.  We make a whole lot of assumptions about who we are, but we
> don't actually know, and that's why the question is being asked.  I
> would clarify that IMHO the only reason this question should be asked is
> for demographic purposes, along with others.

  Pardon me, but that makes no sense. Asking about the gender make-up
of those who elect to register for a future meeting is going to tell us
little
about who we are. It will be a snapshot in time and it will not
representative
of "who we are" because we are more than just the people who register to
go to any particular meeting.

  And "...the only reason...along with others"? So then it's not only for
demographic purposes. Those other purposes aside from the "only" one
are what, exactly?

>>  This question is trying to decide our
>> gender make up and nothing good can come of it.
>>
>>   It will provide more "evidence" for people to make use of logical
>> fallacies-- "if P implies Q then look we now have evidence of Q
>> therefore P"-- which really have no place in an organization devoted
>> to engineering.
>
> This would be putting the cart before the horse.  We first need to
> understand facts.  If we don't understand facts, then people will
> continue on assumptions.

  The facts are already not in dispute. The I* leadership is predominantly
white and male. The fallacy works like this:

    "If there was bias in favor of white males then we would have a
     leadership that is predominantly white and male. We have a
     leadership that is predominantly white and male, therefore we
     have bias."

All this question will do is provide a snapshot in time of just how
predominant it is-- 5% female, oh that's bad, 8% female, oh my look
how skewed the I* leadership is. See, it's skewed therefore we have
bias! If P then Q, and Q (we now have the numbers!) therefore P.

>>   And it will be used as a baseline for doing work towards some goal
>> that has not been justified, work whose very nature requires treating
>> people according to what they are instead of who they are.
>>
>>    Look, bias stinks and when it exists its stench is detectable. I
>> don't
>> recall seeing any evidence of bias being presented on this list. And I
>> don't believe there is any problem has been mentioned that we had or
>> have that is caused by this predominance of white men. It's just been
>> stated as a problem itself. We must have less white men. Why? Because,
>> that's why.
>
> Nobody has proposed that, and I think you can put a bit more faith in
> your peers to not make important decisions based on "because".

  What has been accepted is that "diversity is good". Further, it has been
stated that we cannot remove the race and gender from the problem
statement about our lack of diversity. As Margaret said, "I don't think
it is possible for [sic] remove race and gender from the list of axes,
though, since there is a notable lack of diversity in those areas."

  So a problem statement has been made: there is a notable lack of
diversity in the areas of race and gender. Why is this a problem? What
problem can we point to, now or in the past, that is the result of this
lack of race and gender diversity? Well? Hmmm? Anyone? Bueller? No,
nothing. So in lieu of nothing all we have is "because". If you don't like
"because" as a reason then fine, I will concede the point: decisions will
be made for no reason at all! That hardly seems better.

  And now the only action I see out of this whole diversity discussion on
the list is a plan to ask the gender of registrants for the Berlin meeting.

  If this is just some innocent question to find out "who we are" then why
don't we ask about the size of the organization we work for?  We all
agree that we have a diversity problem on that axis and there is a skew
for large corporations. No, the question is just about gender.

  Sadly, I can't put much faith in my "peers" to make important decisions
because they're asking the wrong questions so they can gather data
"while working on addressing" a non-problem.

  regards,

  Dan.




From presnick@qti.qualcomm.com  Thu Apr 18 08:28:50 2013
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 399E221F8A2A for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 08:28:50 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vvu8vnB-jlCx for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 08:28:39 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 6A59221F8523 for <ietf@ietf.org>; Thu, 18 Apr 2013 08:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1366298919; x=1397834919; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=THqlZJ8pwwBLrUJtnP7X8EUxnoW50Di9uQkWXBxU9WQ=; b=efPRHztbJ/BIix3yqgxv9Q6f9npUapAMOV8Bni1r58u6Xl+OQDJqfAR8 /z5o7ptqJnMG11NJBG5uLh1wSwEUADX470r95O41GPzrEsnFyHyQXej0X mm3usAD/0TxceMwnN9KxC3KNEpml96OY4qFVzJ29f2HspYJE+xByPgaNz c=;
X-IronPort-AV: E=Sophos;i="4.87,502,1363158000"; d="scan'208";a="35579489"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 18 Apr 2013 08:28:38 -0700
X-IronPort-AV: E=Sophos;i="4.87,502,1363158000"; d="scan'208";a="435171914"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 18 Apr 2013 08:28:38 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 18 Apr 2013 08:28:38 -0700
Message-ID: <51701125.1060802@qti.qualcomm.com>
Date: Thu, 18 Apr 2013 10:28:37 -0500
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: James Polk <jmpolk@cisco.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>	<6.2.5.6.2.20130411101504.0c42fed0@resistor.net>	<8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com>	<5167211A.8080807@wonderhamster.org>	<CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com>	<CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>	<20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com>	<20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com>	<13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>	<51685C64.3010803@gmail.com> <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com>
In-Reply-To: <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.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: Thu, 18 Apr 2013 15:28:50 -0000

I noticed this post from a few days ago, but I think instructive to talk 
about. And this is not picking on James; I think it's likely that there 
are many folk who have similar perceptions, and I think it's useful to 
think about.

On 4/12/13 3:37 PM, James Polk wrote:

> Eyeballing the IETF (and I've missed 2 meetings since IETF45, been a 
> WG chair for 8 years, and written or revised over 300 submitted IDs) 
> there is consistently about a 70-to-1 ratio of men to women.

Your "eyeballing" had you put the ratio at about 70:1. I wouldn't be 
surprised if this was a common view. However, when the whole diversity 
conversation started, a few people quickly scanned through attendance 
lists just to do a guesstimate of the actual ratios over the past 10 
years. They were seeing rates somewhere between 10:1 and 18:1 (with so 
much variability due to guessing on the basis of names), and it's seemed 
pretty consistent over the last 10 years. Over the past 5 years, the 
ratio of Nomcom members (randomly selected from the community) is about 
10:1, which is consistent with those numbers.

That's a factor of between 4 and 7 difference between an "eyeball" guess 
and a rough calculation. I think that's likely an unintentional sampling 
bias of your (and many other folks) eyeballs. And I think it's because 
we have a tendency to subconsciously discount the numbers of people who 
do not appear in leadership, or even simply don't behave "the way the 
rest of us do".

This isn't to say that we should spend all of our time on this question 
by collecting statistics; that's just navel gazing. But we do want to 
understand the nature of the problem and not let our guesses and 
subconscious biases get in the way.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From cabo@tzi.org  Thu Apr 18 08:34:10 2013
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 75D1C21F8E99 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 08:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.818
X-Spam-Level: 
X-Spam-Status: No, score=-106.818 tagged_above=-999 required=5 tests=[AWL=-0.569, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DHpHXHsTrMP for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 08:34:09 -0700 (PDT)
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 7A4BB21F8E98 for <ietf@ietf.org>; Thu, 18 Apr 2013 08:34:09 -0700 (PDT)
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.4/8.14.4) with ESMTP id r3IFY5aQ002323; Thu, 18 Apr 2013 17:34:05 +0200 (CEST)
Received: from [192.168.217.105] (p548938F1.dip.t-dialin.net [84.137.56.241]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 50B25314D; Thu, 18 Apr 2013 17:34:05 +0200 (CEST)
Subject: Re: IETF Diversity Question on Berlin Registration?
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
X-Priority: 3 (Normal)
In-Reply-To: <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net>
Date: Thu, 18 Apr 2013 17:34:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B757846-E843-4914-B232-A0E73C5BCDD7@tzi.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net>
To: "Dan Harkins" <dharkins@lounge.org>
X-Mailer: Apple Mail (2.1503)
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, 18 Apr 2013 15:34:10 -0000

On Apr 18, 2013, at 17:17, "Dan Harkins" <dharkins@lounge.org> wrote:

> Why is this a problem?

I think you are more likely to ask this question if you think that if it =
is a "problem", then we *have* to "solve" it, e.g. by shooting enough of =
the white male people in the IETF that the numbers balance.

It is not that kind of "problem".  It is, however, a situation that a =
sizable part of the community have experience with.  The experience =
that, if you find ways to improve diversity where the cure is *not* =
worse than the ailment, the quality of the work actually improves from =
that.

You may simply not have that experience -- it wouldn't surprise me, as =
differences in personal experience are usually the most important reason =
why people incessantly argue.

Gr=FC=DFe, Carsten


From brian.e.carpenter@gmail.com  Thu Apr 18 08:43:05 2013
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 4D5DA21F8E51 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 08:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.813
X-Spam-Level: 
X-Spam-Status: No, score=-102.813 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rjijF9RhCafo for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 08:43:04 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA1E21F8C30 for <ietf@ietf.org>; Thu, 18 Apr 2013 08:43:04 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id c10so2095568wiw.2 for <ietf@ietf.org>; Thu, 18 Apr 2013 08:43:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=t7P4yRp3s8ryzCDnFT94j/WrueSxMguT5Ubiw/EPhjM=; b=AVHAHrFAjxILBWwcaw1+Np+eFxyqY1mCE1hIGMj6cyJJtpxJJ/hLiakzgxtK+SE8Qc Og4n0GFG1NOmZyLgQhl0TlIay6h5l8kIXQS/e4//UR/80LTLZY9/f1fSc+/oxo5zUZPT p0XkEX7cRNW9O3+c45/4c816w/Qt/7RmOHzn3OfvOGlx5fjEsNdchjhr8TVlTFK2YTSN b0f/AN0xvc0VJhCBebKsGDGyie/Dz42BPn354UIJlDscvkb0pyBpglwzjqqZLxIhwYCZ 8sMLXBI5xBfZgv1Cp6rFlyXqJPpO1ZYkbdg/CMwzzr/J2EbztZA8FHl2HuBhEu4O93BJ 1Stw==
X-Received: by 10.180.183.133 with SMTP id em5mr9735628wic.26.1366299783585; Thu, 18 Apr 2013 08:43:03 -0700 (PDT)
Received: from [10.3.2.18] (a2.norwich.yourspac.nsdsl.net. [94.229.131.97]) by mx.google.com with ESMTPS id er1sm32141398wib.5.2013.04.18.08.43.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Apr 2013 08:43:01 -0700 (PDT)
Message-ID: <5170148D.9090204@gmail.com>
Date: Thu, 18 Apr 2013 16:43:09 +0100
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: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>	<6.2.5.6.2.20130411101504.0c42fed0@resistor.net>	<8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com>	<5167211A.8080807@wonderhamster.org>	<CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com>	<CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>	<20130411213835.GA8968@cisco.com>	<51675819.9070302@gmail.com>	<20130412181250.GA14224@cisco.com>	<51685369.4000306@gmail.com>	<13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>	<51685C64.3010803@gmail.com>	<201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com> <51701125.1060802@qti.qualcomm.com>
In-Reply-To: <51701125.1060802@qti.qualcomm.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, 18 Apr 2013 15:43:05 -0000

On 18/04/2013 16:28, Pete Resnick wrote:
...
> That's a factor of between 4 and 7 difference between an "eyeball" guess
> and a rough calculation. I think that's likely an unintentional sampling
> bias of your (and many other folks) eyeballs. And I think it's because
> we have a tendency to subconsciously discount the numbers of people who
> do not appear in leadership, or even simply don't behave "the way the
> rest of us do".
> 
> This isn't to say that we should spend all of our time on this question
> by collecting statistics; that's just navel gazing. But we do want to
> understand the nature of the problem and not let our guesses and
> subconscious biases get in the way.

Indeed. Ideally, though, we need a statistician to look at the
historical ratios (e.g. M/F ratios) in the attendee lists vs the
I* membership, to see whether there is a statistically significant
bias in the selection process over the years.

   Brian

From lear@cisco.com  Thu Apr 18 09:01:33 2013
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 0F6F421F8B5F for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 09:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.318
X-Spam-Level: 
X-Spam-Status: No, score=-110.318 tagged_above=-999 required=5 tests=[AWL=0.281, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I1G+EquEavbW for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 09:01:32 -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 11CCD21F8FFC for <ietf@ietf.org>; Thu, 18 Apr 2013 09:01:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2062; q=dns/txt; s=iport; t=1366300892; x=1367510492; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=U6jaAmGPrJuKEKZb0US6erdWXAp/PH6SrQBZR69NF8U=; b=CNAcpQczD1TnW/JqAlRTlO82YACEkSJXAe1IapnVfW6vFnFiZMLKjZx6 PhFCChbayJXclEAwMgI96g/OfqnlO9Ww4iBVAiENM85VWiv0/FCHMjOWs 88xXlz2heYaabH+dyTN/wc3nu0jKvwsxwepRJDqFqJdXcrFjwf/AChNFw Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFALAXcFGQ/khR/2dsb2JhbABQgwaDZ7pHgmSBAxZ0gh8BAQEEGAtVARALDgoCAgUWCwICCQMCAQIBRQYNAQcBAYgQrA6CA5BpgSONdQeCNIETA5cHkRSDDTo
X-IronPort-AV: E=Sophos;i="4.87,502,1363132800"; d="scan'208";a="12947866"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 18 Apr 2013 16:01:30 +0000
Received: from ams3-vpn-dhcp5391.cisco.com (ams3-vpn-dhcp5391.cisco.com [10.61.85.14]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3IG1S3J011593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Apr 2013 16:01:28 GMT
Message-ID: <517018D7.1000305@cisco.com>
Date: Thu, 18 Apr 2013 18:01:27 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Dan Harkins <dharkins@lounge.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net>
In-Reply-To: <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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, 18 Apr 2013 16:01:33 -0000

Self inflicted confusion.  Please see below:

On 4/18/13 5:17 PM, Dan Harkins wrote:
>   Hi Eliot,
>
> On Wed, April 17, 2013 12:48 pm, Eliot Lear wrote:
> Pardon me, but that makes no sense. Asking about the gender make-up of
> those who elect to register for a future meeting is going to tell us
> little about who we are. It will be a snapshot in time and it will not
> representative of "who we are" because we are more than just the
> people who register to go to any particular meeting. 

And let's stop there.  The point of my originally muddled note was that
we shouldn't just ask about gender.  For that I apologize.  Also, I
wouldn't do this just one time.
>   The facts are already not in dispute. The I* leadership is predominantly
> white and male. The fallacy works like this:

We don't have facts in evidence, and as I wrote above, I'm not even sure
we know which facts we need.  I can say that gender is probably one,
country of residence is something we have, age is something we don't
ask, but we do ask how many meetings you've been to.  We don't ask why
you're at the IETF and we don't ask which groups are important to you. 
We don't ask whether you plan to attend other IETFs and we don't ask
anyone who has attended an IETF but isn't back, why they didn't show. 
We don't ask questions about the experience, in terms of how people are
able to find their way through the process.  There are many questions we
don't ask.  Now granted, some of this is more than who we are, but also
how easy are we to work with.  How does language and location play into
this?

Personally I'd love to survey people going to OTHER standards
organizations and find out why they chose those other organizations to
pursue work, but then I'm not footing the bill for all of this, so...

This is not just about one attribute.  You're ALMOST right in that a lot
of us know each other.  Perhaps that's even a problem, in that others
can't break in.

Much of this is what I would expect the diversity team to explore.

Eliot

From jdrake@juniper.net  Thu Apr 18 09:09:12 2013
Return-Path: <jdrake@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 0251A21F8FD9 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 09:09:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.364
X-Spam-Level: 
X-Spam-Status: No, score=-3.364 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tn1IJMgFySxh for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 09:09:11 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 4002321F8FC6 for <ietf@ietf.org>; Thu, 18 Apr 2013 09:09:11 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUXAappl1IYVbmwZpoN/jLIuE4yQQSmmS@postini.com; Thu, 18 Apr 2013 09:09:11 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 18 Apr 2013 09:06:50 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Thu, 18 Apr 2013 09:06:50 -0700
Received: from ch1outboundpool.messaging.microsoft.com (216.32.181.183) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 18 Apr 2013 09:16:41 -0700
Received: from mail179-ch1-R.bigfish.com (10.43.68.235) by CH1EHSOBE015.bigfish.com (10.43.70.65) with Microsoft SMTP Server id 14.1.225.23; Thu, 18 Apr 2013 16:06:49 +0000
Received: from mail179-ch1 (localhost [127.0.0.1])	by mail179-ch1-R.bigfish.com (Postfix) with ESMTP id 87A251801BB	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 18 Apr 2013 16:06:49 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT004.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -25
X-BigFish: PS-25(zzbb2dI98dI9371I542I1432Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz1033IL8275dhz2dh2a8h668h839h93fhd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1155h)
Received: from mail179-ch1 (localhost.localdomain [127.0.0.1]) by mail179-ch1 (MessageSwitch) id 1366301163351727_11331; Thu, 18 Apr 2013 16:06:03 +0000 (UTC)
Received: from CH1EHSMHS009.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.232])	by mail179-ch1.bigfish.com (Postfix) with ESMTP id 4894CC09DD;	Thu, 18 Apr 2013 16:06:03 +0000 (UTC)
Received: from BL2PRD0510HT004.namprd05.prod.outlook.com (157.56.240.101) by CH1EHSMHS009.bigfish.com (10.43.70.9) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 18 Apr 2013 16:06:01 +0000
Received: from BL2PRD0510MB349.namprd05.prod.outlook.com ([169.254.1.181]) by BL2PRD0510HT004.namprd05.prod.outlook.com ([10.255.100.39]) with mapi id 14.16.0293.003; Thu, 18 Apr 2013 16:06:00 +0000
From: John E Drake <jdrake@juniper.net>
To: Eliot Lear <lear@cisco.com>, Dan Harkins <dharkins@lounge.org>
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbeKuoMqWAFtkmNWH3bnXdwmJjRbDcAgAAKcACAAAcGAIAAATgAgAAEl4CAAADsgIAAAUmAgAAGmICAADL0gIABJeQAgAAFsoCAAAi6gIAAAfsAgAAlvoCAAFKbgIAApDMAgAAKJACAACqHgIADtoYAgAKLlQCAAEscAIAAB3sAgAFGpYCAAAxTgIAAAQig
Date: Thu, 18 Apr 2013 16:05:59 +0000
Message-ID: <0182DEA5604B3A44A2EE61F3EE3ED69E1D4A6E71@BL2PRD0510MB349.namprd05.prod.outlook.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie>	<7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <517018D7.1000305@cisco.com>
In-Reply-To: <517018D7.1000305@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.224.50]
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%CISCO.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%LOUNGE.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
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, 18 Apr 2013 16:09:12 -0000

QWdlLCBJUSwgJiBzaG9lIHNpemU/ICAoSWRlYWxseSwgdGhleSBzaG91bGQgYmUgZXF1YWwuKQ0K
DQpJcnJlc3BlY3RpdmVseSBZb3VycywNCg0KSm9obg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gRnJvbTogaWV0Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86aWV0Zi1ib3Vu
Y2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YNCj4gRWxpb3QgTGVhcg0KPiBTZW50OiBUaHVyc2Rh
eSwgQXByaWwgMTgsIDIwMTMgOTowMSBBTQ0KPiBUbzogRGFuIEhhcmtpbnMNCj4gQ2M6IGlldGZA
aWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IElFVEYgRGl2ZXJzaXR5IFF1ZXN0aW9uIG9uIEJlcmxp
biBSZWdpc3RyYXRpb24/DQo+IA0KPiBTZWxmIGluZmxpY3RlZCBjb25mdXNpb24uICBQbGVhc2Ug
c2VlIGJlbG93Og0KPiANCj4gT24gNC8xOC8xMyA1OjE3IFBNLCBEYW4gSGFya2lucyB3cm90ZToN
Cj4gPiAgIEhpIEVsaW90LA0KPiA+DQo+ID4gT24gV2VkLCBBcHJpbCAxNywgMjAxMyAxMjo0OCBw
bSwgRWxpb3QgTGVhciB3cm90ZToNCj4gPiBQYXJkb24gbWUsIGJ1dCB0aGF0IG1ha2VzIG5vIHNl
bnNlLiBBc2tpbmcgYWJvdXQgdGhlIGdlbmRlciBtYWtlLXVwDQo+IG9mDQo+ID4gdGhvc2Ugd2hv
IGVsZWN0IHRvIHJlZ2lzdGVyIGZvciBhIGZ1dHVyZSBtZWV0aW5nIGlzIGdvaW5nIHRvIHRlbGwg
dXMNCj4gPiBsaXR0bGUgYWJvdXQgd2hvIHdlIGFyZS4gSXQgd2lsbCBiZSBhIHNuYXBzaG90IGlu
IHRpbWUgYW5kIGl0IHdpbGwNCj4gbm90DQo+ID4gcmVwcmVzZW50YXRpdmUgb2YgIndobyB3ZSBh
cmUiIGJlY2F1c2Ugd2UgYXJlIG1vcmUgdGhhbiBqdXN0IHRoZQ0KPiA+IHBlb3BsZSB3aG8gcmVn
aXN0ZXIgdG8gZ28gdG8gYW55IHBhcnRpY3VsYXIgbWVldGluZy4NCj4gDQo+IEFuZCBsZXQncyBz
dG9wIHRoZXJlLiAgVGhlIHBvaW50IG9mIG15IG9yaWdpbmFsbHkgbXVkZGxlZCBub3RlIHdhcyB0
aGF0DQo+IHdlIHNob3VsZG4ndCBqdXN0IGFzayBhYm91dCBnZW5kZXIuICBGb3IgdGhhdCBJIGFw
b2xvZ2l6ZS4gIEFsc28sIEkNCj4gd291bGRuJ3QgZG8gdGhpcyBqdXN0IG9uZSB0aW1lLg0KPiA+
ICAgVGhlIGZhY3RzIGFyZSBhbHJlYWR5IG5vdCBpbiBkaXNwdXRlLiBUaGUgSSogbGVhZGVyc2hp
cCBpcw0KPiA+IHByZWRvbWluYW50bHkgd2hpdGUgYW5kIG1hbGUuIFRoZSBmYWxsYWN5IHdvcmtz
IGxpa2UgdGhpczoNCj4gDQo+IFdlIGRvbid0IGhhdmUgZmFjdHMgaW4gZXZpZGVuY2UsIGFuZCBh
cyBJIHdyb3RlIGFib3ZlLCBJJ20gbm90IGV2ZW4NCj4gc3VyZSB3ZSBrbm93IHdoaWNoIGZhY3Rz
IHdlIG5lZWQuICBJIGNhbiBzYXkgdGhhdCBnZW5kZXIgaXMgcHJvYmFibHkNCj4gb25lLCBjb3Vu
dHJ5IG9mIHJlc2lkZW5jZSBpcyBzb21ldGhpbmcgd2UgaGF2ZSwgYWdlIGlzIHNvbWV0aGluZyB3
ZQ0KPiBkb24ndCBhc2ssIGJ1dCB3ZSBkbyBhc2sgaG93IG1hbnkgbWVldGluZ3MgeW91J3ZlIGJl
ZW4gdG8uICBXZSBkb24ndA0KPiBhc2sgd2h5IHlvdSdyZSBhdCB0aGUgSUVURiBhbmQgd2UgZG9u
J3QgYXNrIHdoaWNoIGdyb3VwcyBhcmUgaW1wb3J0YW50DQo+IHRvIHlvdS4NCj4gV2UgZG9uJ3Qg
YXNrIHdoZXRoZXIgeW91IHBsYW4gdG8gYXR0ZW5kIG90aGVyIElFVEZzIGFuZCB3ZSBkb24ndCBh
c2sNCj4gYW55b25lIHdobyBoYXMgYXR0ZW5kZWQgYW4gSUVURiBidXQgaXNuJ3QgYmFjaywgd2h5
IHRoZXkgZGlkbid0IHNob3cuDQo+IFdlIGRvbid0IGFzayBxdWVzdGlvbnMgYWJvdXQgdGhlIGV4
cGVyaWVuY2UsIGluIHRlcm1zIG9mIGhvdyBwZW9wbGUgYXJlDQo+IGFibGUgdG8gZmluZCB0aGVp
ciB3YXkgdGhyb3VnaCB0aGUgcHJvY2Vzcy4gIFRoZXJlIGFyZSBtYW55IHF1ZXN0aW9ucw0KPiB3
ZSBkb24ndCBhc2suICBOb3cgZ3JhbnRlZCwgc29tZSBvZiB0aGlzIGlzIG1vcmUgdGhhbiB3aG8g
d2UgYXJlLCBidXQNCj4gYWxzbyBob3cgZWFzeSBhcmUgd2UgdG8gd29yayB3aXRoLiAgSG93IGRv
ZXMgbGFuZ3VhZ2UgYW5kIGxvY2F0aW9uIHBsYXkNCj4gaW50byB0aGlzPw0KPiANCj4gUGVyc29u
YWxseSBJJ2QgbG92ZSB0byBzdXJ2ZXkgcGVvcGxlIGdvaW5nIHRvIE9USEVSIHN0YW5kYXJkcw0K
PiBvcmdhbml6YXRpb25zIGFuZCBmaW5kIG91dCB3aHkgdGhleSBjaG9zZSB0aG9zZSBvdGhlciBv
cmdhbml6YXRpb25zIHRvDQo+IHB1cnN1ZSB3b3JrLCBidXQgdGhlbiBJJ20gbm90IGZvb3Rpbmcg
dGhlIGJpbGwgZm9yIGFsbCBvZiB0aGlzLCBzby4uLg0KPiANCj4gVGhpcyBpcyBub3QganVzdCBh
Ym91dCBvbmUgYXR0cmlidXRlLiAgWW91J3JlIEFMTU9TVCByaWdodCBpbiB0aGF0IGENCj4gbG90
IG9mIHVzIGtub3cgZWFjaCBvdGhlci4gIFBlcmhhcHMgdGhhdCdzIGV2ZW4gYSBwcm9ibGVtLCBp
biB0aGF0DQo+IG90aGVycyBjYW4ndCBicmVhayBpbi4NCj4gDQo+IE11Y2ggb2YgdGhpcyBpcyB3
aGF0IEkgd291bGQgZXhwZWN0IHRoZSBkaXZlcnNpdHkgdGVhbSB0byBleHBsb3JlLg0KPiANCj4g
RWxpb3QNCg0K


From andy@yumaworks.com  Wed Apr 17 17:44:35 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0DFE21E8043 for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 17:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pZGuzv85Iohb for <ietf@ietfa.amsl.com>; Wed, 17 Apr 2013 17:44:35 -0700 (PDT)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 2614D21F88CA for <ietf@ietf.org>; Wed, 17 Apr 2013 17:44:35 -0700 (PDT)
Received: by mail-ie0-f171.google.com with SMTP id e11so2718269iej.2 for <ietf@ietf.org>; Wed, 17 Apr 2013 17:44:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=+SZKwzT7drSuQ2daMSZxFqqcPX5RNDX349YdbV3iaO0=; b=aC5ZHmC9TW1y5PxPkcAhhJZCiDVx/CKQvl/yjdnnkNSm56Ez7uUIduho5U7UGJtXoL dbotBngBJ183ayoYMbcRYd1dp6TQgXksz2/4ic3kcX7jETMkd+Rc9S/E1Ud4eLmO4Z7M SVdghvS2V1lhnC/Yx034E1Txx63C9vnIlrKxsqHwiT24iJnPn/nXitbihXpcB+UX5Psk wMGyU2YW8sX2F7nAEbkM61EHqOxXRn08LVpVc7ZWFnqX38sr/vCAD9zV9D1ShOK/z8/n BN6CPDuZD+mf2ZBB3K097RX2Ukf7kjDHDhYZZuoEBJhW0jRZfMnzigJGg9JexijGruW2 U6+w==
MIME-Version: 1.0
X-Received: by 10.50.78.202 with SMTP id d10mr12159466igx.69.1366245874678; Wed, 17 Apr 2013 17:44:34 -0700 (PDT)
Received: by 10.231.125.202 with HTTP; Wed, 17 Apr 2013 17:44:34 -0700 (PDT)
In-Reply-To: <516EB736.6060801@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com>
Date: Wed, 17 Apr 2013 17:44:34 -0700
Message-ID: <CABCOCHQO8v=Sa0RndQLCp-NSAZV-jbrk-x09BKp7RV=gxNiXgg@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Andy Bierman <andy@yumaworks.com>
To: Eliot Lear <lear@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnePFBWnr8mC/Ph7vb/5jWOW7auKViWSyaoR2CNcY84dzIeNbdLLlBosJ7i9Bl7auxYmD6g
X-Mailman-Approved-At: Thu, 18 Apr 2013 09:11:45 -0700
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, 18 Apr 2013 00:44:36 -0000

On Wed, Apr 17, 2013 at 7:52 AM, Eliot Lear <lear@cisco.com> wrote:
> Dan,
>
> On 4/16/13 2:00 AM, Dan Harkins wrote:
>
>> Under the belief of "garbage in, garbage out", I tend to lie on these
>> sorts of repugnant questions. I invite others to join me. The more
>> suspect the quality of the data, the less value it has. Dan.
>
> Please don't.  We are trying to understand who we are.  Is that SO
> unreasonable?
>

I don't object to filling out forms, and I would certainly answer honestly.
Who is "we"?  Just people who go to the Berlin IETF?
   - does it include remote participants via Jabber or other tools
   - does it include people who participate only on WG mailing lists?

The only bias I see is that it takes a lot of employer backing
and funding to participate in the IESG.  It is therefore the
companies that sponsor these participants have the most influence of all
over the selection process.

Hold another IETF in San Jose or San Francisco and I bet we get
way more balanced data than a site that requires a lot of travel,
especially since we have day passes now.

> Eliot

Andy

From dharkins@lounge.org  Thu Apr 18 10:06:53 2013
Return-Path: <dharkins@lounge.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 9BF1921F9104 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 10:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YTKVxiKOHG1K for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 10:06:53 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCAC21F90F6 for <ietf@ietf.org>; Thu, 18 Apr 2013 10:06:53 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 0A49DA888008; Thu, 18 Apr 2013 10:06:51 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Thu, 18 Apr 2013 10:06:51 -0700 (PDT)
Message-ID: <dc89b02b65df2c0962cf4ae052956e64.squirrel@www.trepanning.net>
In-Reply-To: <1B757846-E843-4914-B232-A0E73C5BCDD7@tzi.org>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <1B757846-E843-4914-B232-A0E73C5BCDD7@tzi.org>
Date: Thu, 18 Apr 2013 10:06:51 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: "Carsten Bormann" <cabo@tzi.org>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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, 18 Apr 2013 17:06:53 -0000

On Thu, April 18, 2013 8:34 am, Carsten Bormann wrote:
> On Apr 18, 2013, at 17:17, "Dan Harkins" <dharkins@lounge.org> wrote:
>
>> Why is this a problem?
>
> I think you are more likely to ask this question if you think that if it
> is a "problem", then we *have* to "solve" it, e.g. by shooting enough of
> the white male people in the IETF that the numbers balance.
>
> It is not that kind of "problem".

  Well that's a relief! As a white male (I know, a surprise, right?) I'm
glad to know I am not going to get shot.

>                                                    It is, however, a
situation that a
> sizable part of the community have experience with.

  I have been attended at least 40 IETFs over the past 18 years or so.
I certainly have experience with this situation. What is new, though,
is the statement that this situation is, in fact, a problem.

>                                                                                   The
experience
that,
> if you find ways to improve diversity where the cure is *not* worse than
> the ailment, the quality of the work actually improves from that.

  What is this "cure" of which you speak? This diversity discussion has
included statements like:

  "If the intent is to emphasize diversity (for some metric) over one of
the core skills [technical clue, admin skills, ability to work with others],
that's certainly possible."

and,

  "A small point to watch for, if there is a focus on a defined list of
groups [and there certainly appears to be one-- gender], is the
difference between discriminating /against/, versus ensuring
representation /from/."

  So? Are we going to emphasize diversity over core skills? Say that
one's gender or skin color matters more than their technical clue or
their ability to work with others? By what method are we going to
"ensure" representation? And what do we do if these efforts have not
resulted in the  proportions that are deemed to be acceptable? Use a
little more force? Quotas?

  Nobody has stated what the "cure" is for this situation so we don't
know whether it will be worse than the ailment. There is a huge gap
between "encouraging more women to volunteer" and "shooting
white men". And I really don't think we need to count the gender
make-up of a meeting if our "cure" was going to something close
to "encouraging more women to volunteer."

  regards,

  Dan.



From mstjohns@comcast.net  Thu Apr 18 10:41:58 2013
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 6ECE521F8FAA for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 10:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ku4yVZ6FOsr for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 10:41:56 -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 347D621F8F0E for <ietf@ietf.org>; Thu, 18 Apr 2013 10:41:56 -0700 (PDT)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta05.westchester.pa.mail.comcast.net with comcast id RNK71l0031HzFnQ55Vhu58; Thu, 18 Apr 2013 17:41:54 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta14.westchester.pa.mail.comcast.net with comcast id RVht1l00p2kB7pQ3aVhuMs; Thu, 18 Apr 2013 17:41:54 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 18 Apr 2013 13:41:57 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Pete Resnick <presnick@qti.qualcomm.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <5170148D.9090204@gmail.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com> <51701125.1060802@qti.qualcomm.com> <5170148D.9090204@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1366306914; bh=FK0ou5w0+sWazCQc5+O7RO//5B+mWgcE9Z/8vT+I6QI=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=K0/eld0iTcYnJ/KNO2GMVWskPUWL6NfbUkPT7SMIidIMY+78RMnWOmrUJjGu9hYCU JHsMTd+fC9AlNmcUNDesFqVUp8FqvLV1kI0xuV8RhgiyPMeVM38t+IY+148Xywryrj xEJJjAU7ziIlpu+iK6TwzjHIOdksbkgZlRXELdx2j0fpX1SAEGu02RhrB/iYUIb13D UNObEeb4IzygQWaYqqujPIxCmmeREBSBCHMKhrEr+ThsgsrZsuLSZKvFupPxRF03wB 0JXMLE1py+QVYX6+ZFoHhjdDoKLVG9ch0CE0H4EPdLr3TKJEHPzak3gWS61JUZLAbZ lgS+KsG6ai4Cg==
Message-Id: <20130418174156.347D621F8F0E@ietfa.amsl.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, 18 Apr 2013 17:41:58 -0000

At 11:43 AM 4/18/2013, Brian E Carpenter wrote:
>Indeed. Ideally, though, we need a statistician to look at the
>historical ratios (e.g. M/F ratios) in the attendee lists vs the
>I* membership, to see whether there is a statistically significant
>bias in the selection process over the years.
>
>   Brian 

Yup.

We have:

1) The difference in composition between the world as a whole and the IETF.
2) The difference in composition between the industrialized nations as a whole and the IETF.
3) The difference in composition between the set of small medium and large networking companies as a whole and the IETF.
4) The difference in composition between the IETF (for some measure of that) and the composition of the set of IETF working group chairs.
5) The difference in composition between the set of IETF working group chairs and the set of members of the IAB and IESG.
6) The difference in composition between the IETF and the composition of the IAOC.


All of these are somewhat interesting statistical analysis problems.  My guess (without looking at the numbers) is the (1) is pretty large.  (2) is still large, but substantially less than (1), (3) is quite a bit smaller than (1) or (2) - all of these for pretty much any axis you want to evaluate.  

For your question, I differentiated between the IAOC and the IAB/IESG for one specific reason - an injected bias for the second group that mostly says that paying your dues as a working group chair is a pre and sometimes co requisite for becoming a member of the IAB or IESG.  I'm pretty sure the injected bias for the IAOC is "business experience" of some sort.

I haven't seen anything on the list that suggests there's selection bias for working group chairs - it's possible there is, but I can't actually recall any complaints going back say 10 years where the selection of a working group chair was intimated to be biased based on gender or any other criteria.  Given that the positions are about 90% self-selection and 10% area director approval, I don't know how you could do bias analysis there and get meaningful results.  That's question (4).  We can provide a statistical number for the difference, but the "why" is going to be elusive.

So going forward, what I think we should be more interested in is not so much the composition of the IETF, but the composition of the set of WG chairs and how that population compares to the set of IESG and IAB members.  That's question (5).  That question doesn't need to be asked on the registration forms for Berlin.

I'm not sure we have enough history yet for question (6).

I will note that besides the "must have been a WG chair" bias, we also have a "sell by date" bias, especially for IESG members.  By that I mean that a perfectly qualified candidate for the IESG who has been serving in that position for say 6 years is less desirable than one who has similar qualifications but hasn't yet served and may end up being considered "disqualified" even if fully qualified.  That bias is written into the 3777 considerations as is the WG chair bias.  It may be useful to take the set of current (or last 5 year) chairs, and subtract out any chair who has served at least 2 or 4 years as IAB or IESG and do the comparison with the IAB/IESG again.

Mike



From jari.arkko@piuha.net  Thu Apr 18 11:00:21 2013
Return-Path: <jari.arkko@piuha.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 1611821F9110 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 11:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cOQ2fJ4fU8yf for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 11:00:20 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9DA9821F90EE for <ietf@ietf.org>; Thu, 18 Apr 2013 11:00:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E5FD02CC46; Thu, 18 Apr 2013 21:00:18 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H5Ipxv1QNEsB; Thu, 18 Apr 2013 21:00:18 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id F40A02CC3C; Thu, 18 Apr 2013 21:00:17 +0300 (EEST)
Subject: Re: IETF Diversity Question on Berlin Registration?
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Jari Arkko <jari.arkko@piuha.net>
X-Priority: 3 (Normal)
In-Reply-To: <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net>
Date: Thu, 18 Apr 2013 21:00:17 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <2382547A-B2B3-46BD-8102-D8217A21565C@piuha.net>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net>
To: Dan Harkins <dharkins@lounge.org>
X-Mailer: Apple Mail (2.1503)
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, 18 Apr 2013 18:00:21 -0000

Dan: the original reason for wanting to understand who the meeting =
participants are (as a subset of all IETF participants) was a desire to =
track our participation. Similarly to how we already track where they =
come from, and present that pie chart in the plenary.=20

You raise an issue about making deductions about the leadership bias =
based on these numbers. I agree that such deductions would be highly =
questionable. But enabling such comparisons was not the intent. It truly =
was merely to understand where we are in terms of participation, and how =
it evolves over time.

Jari


From adrian@olddog.co.uk  Thu Apr 18 11:31:27 2013
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 0F85521E803F for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 11:31:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RxrcHTJPjKo0 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 11:31:26 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 4CDEB21F9356 for <ietf@ietf.org>; Thu, 18 Apr 2013 11:31:24 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3IIVC6Y005969;  Thu, 18 Apr 2013 19:31:12 +0100
Received: from 950129200 ([69.38.252.85]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3IIVASc005949 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 18 Apr 2013 19:31:12 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Pete Resnick'" <presnick@qti.qualcomm.com>, "'James Polk'" <jmpolk@cisco.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>	<6.2.5.6.2.20130411101504.0c42fed0@resistor.net>	<8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com>	<5167211A.8080807@wonderhamster.org>	<CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com>	<CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>	<20130411213835.GA8968@cisco.com>	<51675819.9070302@gmail.com>	<20130412181250.GA14224@cisco.com>	<51685369.4000306@gmail.com>	<13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>	<51685C64.3010803@gmail.com>	<201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com> <51701125.1060802@qti.qualcomm.com>
In-Reply-To: <51701125.1060802@qti.qualcomm.com>
Subject: RE: IETF Diversity Question on Berlin Registration?
Date: Thu, 18 Apr 2013 19:31:10 +0100
Message-ID: <021a01ce3c62$e6e93db0$b4bbb910$@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: AQNLX/Kh7B/2DlfI+6RxLNvMWnjAlgG9Z4mVAmq6caACz3DsvgITgwXuAsW8PJ4Bqr+3zwG00Q4BAoXKLJUA6936dQKRKH2kAg0p6aIBc/+dVwHUg5zAAS87nTYC15GAHJTth6Lw
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, 18 Apr 2013 18:31:27 -0000

The perception is important.
It probably shows many things including "attendance is not participation".

Just for the completely unscientific hell of it, I just counted up the mic-sex
in CCAMP's marathon meetings in Orlando. I counted minuted interventions and
presentations. I counted each intervention in a conversation.

I found a ratio of 7 male to 1 female.

This proves nothing.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Pete
> Resnick
> Sent: 18 April 2013 16:29
> To: James Polk
> Cc: ietf@ietf.org
> Subject: Re: IETF Diversity Question on Berlin Registration?
> 
> I noticed this post from a few days ago, but I think instructive to talk
> about. And this is not picking on James; I think it's likely that there
> are many folk who have similar perceptions, and I think it's useful to
> think about.
> 
> On 4/12/13 3:37 PM, James Polk wrote:
> 
> > Eyeballing the IETF (and I've missed 2 meetings since IETF45, been a
> > WG chair for 8 years, and written or revised over 300 submitted IDs)
> > there is consistently about a 70-to-1 ratio of men to women.
> 
> Your "eyeballing" had you put the ratio at about 70:1. I wouldn't be
> surprised if this was a common view. However, when the whole diversity
> conversation started, a few people quickly scanned through attendance
> lists just to do a guesstimate of the actual ratios over the past 10
> years. They were seeing rates somewhere between 10:1 and 18:1 (with so
> much variability due to guessing on the basis of names), and it's seemed
> pretty consistent over the last 10 years. Over the past 5 years, the
> ratio of Nomcom members (randomly selected from the community) is about
> 10:1, which is consistent with those numbers.
> 
> That's a factor of between 4 and 7 difference between an "eyeball" guess
> and a rough calculation. I think that's likely an unintentional sampling
> bias of your (and many other folks) eyeballs. And I think it's because
> we have a tendency to subconsciously discount the numbers of people who
> do not appear in leadership, or even simply don't behave "the way the
> rest of us do".
> 
> This isn't to say that we should spend all of our time on this question
> by collecting statistics; that's just navel gazing. But we do want to
> understand the nature of the problem and not let our guesses and
> subconscious biases get in the way.
> 
> pr
> 
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478


From jmpolk@cisco.com  Thu Apr 18 11:33:49 2013
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 A3F8C21F8FE5 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 11:33: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mx4iyJALATyf for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 11:33:48 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id D10F621F8FD9 for <ietf@ietf.org>; Thu, 18 Apr 2013 11:33:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3220; q=dns/txt; s=iport; t=1366310028; x=1367519628; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=0y/1qNERQFTKDnKx4N3KCSLKkIxqGwYPRq/2YK4neqQ=; b=LIRZs0jofNW/bGLLhOJ4vvQlUuUCNJwYX2bsxUak1aOyrTgs1JI4uaZt Oi3asRbJJpYqTE7eVC+D5fQP89pEuAFAwYo0BgPqI/9pAtIzuI24cvVfM p0UWJIXP8JJgEkU29eKgKi3/Q8ISweMU4YjauxCDpHIGg76ldmf0/mGwi k=;
X-IronPort-AV: E=Sophos;i="4.87,503,1363132800"; d="scan'208";a="200201273"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-1.cisco.com with ESMTP; 18 Apr 2013 18:33:48 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8718.cisco.com [10.99.80.25]) (authenticated bits=0) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r3IIXlrL002592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Apr 2013 18:33:48 GMT
Message-Id: <201304181833.r3IIXlrL002592@rcdn-core2-6.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 18 Apr 2013 13:33:25 -0500
To: Pete Resnick <presnick@qti.qualcomm.com>, James Polk <jmpolk@cisco.com>
From: James Polk <jmpolk@cisco.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <51701125.1060802@qti.qualcomm.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com> <51701125.1060802@qti.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
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, 18 Apr 2013 18:33:49 -0000

At 10:28 AM 4/18/2013, Pete Resnick wrote:
>I noticed this post from a few days ago, but I think instructive to 
>talk about. And this is not picking on James; I think it's likely 
>that there are many folk who have similar perceptions, and I think 
>it's useful to think about.
>
>On 4/12/13 3:37 PM, James Polk wrote:
>
>>Eyeballing the IETF (and I've missed 2 meetings since IETF45, been 
>>a WG chair for 8 years, and written or revised over 300 submitted 
>>IDs) there is consistently about a 70-to-1 ratio of men to women.
>
>Your "eyeballing" had you put the ratio at about 70:1. I wouldn't be 
>surprised if this was a common view. However, when the whole 
>diversity conversation started, a few people quickly scanned through 
>attendance lists just to do a guesstimate of the actual ratios over 
>the past 10 years. They were seeing rates somewhere between 10:1 and 
>18:1 (with so much variability due to guessing on the basis of 
>names), and it's seemed pretty consistent over the last 10 years. 
>Over the past 5 years, the ratio of Nomcom members (randomly 
>selected from the community) is about 10:1, which is consistent with 
>those numbers.

I believe I did myself a disservice in assigning such a high ratio 
without saying it "feels like 70:1", which it does. But I'd truly be 
surprised if it's only 10:1 - and you can't make effective and 
accurate estimates based on guessing the gender of the names of an 
international organization like the IETF is.

Now, and this is purely from a defending myself pov, the feel of a 
70:1 crowd that's right in front of you from a 18:1 crowd isn't that 
much, especially if you're part of that larger number. There is a 
matter of the number of the group you happen to be part of is so 
overwhelming you tend to guess on the high side.


>That's a factor of between 4 and 7 difference between an "eyeball" 
>guess and a rough calculation. I think that's likely an 
>unintentional sampling bias of your (and many other folks) eyeballs. 
>And I think it's because we have a tendency to subconsciously 
>discount the numbers of people who do not appear in leadership, or 
>even simply don't behave "the way the rest of us do".

I have to disagree with you here. In my mind, this "feels like a 70:1 
ratio" has nothing to do with the ratios of leadership to the 
community within the IETF, it's from the gathering places and 
hallways where there are just wave after wave (after wave) of men. 
It's also from sheer lack of numbers of women within the WGs I've 
attended over the years (SIP related, MMUSIC, GEOPRIV, ECRIT, the 
whole TSV area, etc).


>This isn't to say that we should spend all of our time on this 
>question by collecting statistics; that's just navel gazing. But we 
>do want to understand the nature of the problem and not let our 
>guesses and subconscious biases get in the way.

whether it's 70:1 or 18:1 - that's significantly more of one group 
that the other.

Thanks Pete for making this point, and causing me to clarify what I 
originally wrote.

James


>pr
>
>--
>Pete Resnick<http://www.qualcomm.com/~presnick/>
>Qualcomm Technologies, Inc. - +1 (858)651-4478


From Ted.Lemon@nominum.com  Thu Apr 18 12:03:37 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85A7821F8464 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 12:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.579
X-Spam-Level: 
X-Spam-Status: No, score=-106.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ubiya7aIIIOD for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 12:03:36 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 93CDE21F88FB for <ietf@ietf.org>; Thu, 18 Apr 2013 12:03:26 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUXBDfmsXMZlIi9yxB+S0QZFfvynlvQcc@postini.com; Thu, 18 Apr 2013 12:03:26 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 36F9E1B8036 for <ietf@ietf.org>; Thu, 18 Apr 2013 12:03:26 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 31016190061; Thu, 18 Apr 2013 12:03:26 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 18 Apr 2013 12:03:26 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dan Harkins <dharkins@lounge.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbesxw5RhqwwUuIKG4LfyrlCZjR4Y8AgAAKbwCAAAcIAIAAATgAgAAEloCAAADsgIAAAUgAgAAGmYCAADL0gIABJeUAgAAFsoCAAAi6gIAAAfoAgAAlvoCAAFKcgIAApDIAgAAKJQCAACqHgIADtoYAgAKLlQCAAEscAIAAB3oAgAFGpoCAAASsAIAAGeyAgAAgkQA=
Date: Thu, 18 Apr 2013 19:03:25 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077514FC75@mbx-01.win.nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <1B757846-E843-4914-B232-A0E73C5BCDD7@tzi.org> <dc89b02b65df2c0962cf4ae052956e64.squirrel@www.trepanning.net>
In-Reply-To: <dc89b02b65df2c0962cf4ae052956e64.squirrel@www.trepanning.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <63D9A321129CF14B9E81DD8946E51539@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Carsten Bormann <cabo@tzi.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, 18 Apr 2013 19:03:37 -0000

On Apr 18, 2013, at 1:06 PM, Dan Harkins <dharkins@lounge.org> wrote:
>  What is this "cure" of which you speak? This diversity discussion has
> included statements like:

Personally, not wearing an AD hat or attempting to anticipate the conclusio=
ns of the study group, I think the cure is to encourage more talented peopl=
e to participate who do not share the same characteristics as the existing =
members, specifically with respect to age, sex, culture and/or geography.  =
 I think discouraging participation or limiting participation of existing p=
articipants is a bad idea, but encouraging new talented participants is alw=
ays a good idea.

And then I think we need to have a kind of ongoing consciousness-raising ab=
out how cognitive bias works, and how it might be affecting our decisions a=
s participants.   It's not enough to simply get a 50-50 male/female ratio, =
for example; if it were, the U.S. would elect female presidents slightly mo=
re than half the time, but of course we don't.

But fixing either problem without fixing the other will not have much impac=
t on diversity; if we fix the cognitive bias problem (should it even exist,=
 which I am not asserting to be the case), that won't matter if the pool of=
 candidates lacks diversity; if the pool of candidates is diverse, that won=
't matter if we don't correct for cognitive bias.


From Ted.Lemon@nominum.com  Thu Apr 18 12:34:30 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2258721F9079 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 12:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.58
X-Spam-Level: 
X-Spam-Status: No, score=-106.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-tOWb4-0zDE for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 12:34:29 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 7CAD521F9283 for <ietf@ietf.org>; Thu, 18 Apr 2013 12:34:29 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUXBKxWfQNUm2epsZ7UO5NVbAfocsWArD@postini.com; Thu, 18 Apr 2013 12:34:29 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E04F31B8128 for <ietf@ietf.org>; Thu, 18 Apr 2013 12:34:28 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D722C190061; Thu, 18 Apr 2013 12:34:28 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 18 Apr 2013 12:34:28 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: James Polk <jmpolk@cisco.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbesxw5RhqwwUuIKG4LfyrlCZjR4Y8AgAAKbwCAAAcIAIAAATgAgAAEloCAAADsgIAAAUgAgAAGmYCAADL0gIABJeUAgAAFsoCAAAi6gIAAAfoAgAAX5YCACRfQgIAAM6KAgAARDYA=
Date: Thu, 18 Apr 2013 19:34:28 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077514FE4B@mbx-01.win.nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com> <51701125.1060802@qti.qualcomm.com> <201304181833.r3IIXlrL002592@rcdn-core2-6.cisco.com>
In-Reply-To: <201304181833.r3IIXlrL002592@rcdn-core2-6.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B928501499561341820ED41B7F681300@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.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: Thu, 18 Apr 2013 19:34:30 -0000

On Apr 18, 2013, at 2:33 PM, James Polk <jmpolk@cisco.com> wrote:
> I believe I did myself a disservice in assigning such a high ratio withou=
t saying it "feels like 70:1", which it does. But I'd truly be surprised if=
 it's only 10:1 - and you can't make effective and accurate estimates based=
 on guessing the gender of the names of an international organization like =
the IETF is.

Part of the problem here is figuring out what you mean by 70:1.   I think i=
f you try to come up with a single ratio like this, you're oversimplifying =
to the point of uselessness.


From jari.arkko@piuha.net  Thu Apr 18 13:07:21 2013
Return-Path: <jari.arkko@piuha.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 BA69C21F8FEC for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 13:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.615
X-Spam-Level: 
X-Spam-Status: No, score=-102.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n+CDZUguzi74 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 13:07:20 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B96A821F8FE8 for <ietf@ietf.org>; Thu, 18 Apr 2013 13:07:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E1BC02CC46; Thu, 18 Apr 2013 23:07:16 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yck_Y0T-_pw1; Thu, 18 Apr 2013 23:07:16 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 281792CC3C; Thu, 18 Apr 2013 23:07:16 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51701125.1060802@qti.qualcomm.com>
Date: Thu, 18 Apr 2013 23:07:15 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <1ABBBB7F-960D-496F-9673-8840D8889685@piuha.net>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>	<6.2.5.6.2.20130411101504.0c42fed0@resistor.net>	<8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com>	<5167211A.8080807@wonderhamster.org>	<CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com>	<CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>	<20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com>	<20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com>	<13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>	<51685C64.3010803@gmail.com> <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com> <51701125.1060802@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1503)
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, 18 Apr 2013 20:07:21 -0000

Pete:

> Your "eyeballing" had you put the ratio at about (snip)

FWIW, I took a database of first names, added a little piece of code on =
my document statistics page to guess genders to calculate aggregate =
numbers. I get results such as 13% of recent RFCs having female authors. =
Perhaps inline with some of the eyeballing numbers from this thread. =
(Details in http://www.arkko.com/tools/docstats.html - btw it does *not* =
retain per-individual information anywhere). However, there are a number =
of caveats.

To begin with, there's a horrible 20-30% recognised error rate =
(unclassified names). And an unknown unrecognised error rate. And I =
looked at the recognised errors, and was able to tell my computer a few =
more names that it should recognise, but not much. Secondly, the =
situation is getting worse. Early RFCs were often unrecognisable, since =
first names were abbreviated. Then it got better, but now it is getting =
worse, drafts have a >30% recognised error rate. My theory is that our =
participation gets more international, and the databases that we can =
find for this sort of thing tend not to be so good with international =
names. I'm guessing participant lists would be worse than drafts. My =
conclusion is that it is difficult to come up with numbers either by =
eyeballing or data mining. Information from registration (country, =
newcomer/not, gender) might be useful from this perspective. But see =
below.

Anyway, enough with engineering the measurements for now. I think some =
of these numbers are interesting, but only from a trend perspective, not =
in their absolute value or comparison to other numbers. We should get =
back to discussing how we can "encourage more talented people to =
participate", as Ted put it. That is the important thing. Clearly, we =
like engineering. Obviously I went for it as well. But we should =
recognise that measurements are just a tiny detail. The best we could =
hope for is that a couple of years down the road we could pat ourselves =
in the back for making an improvement that is actually visible in the =
measurements. But that's it.

Jari






From presnick@qti.qualcomm.com  Thu Apr 18 13:51:14 2013
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 ED29F21F9387 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 13:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.599
X-Spam-Level: 
X-Spam-Status: No, score=-105.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bqTX3f6xNvzY for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 13:51:12 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 5A97A21F9382 for <ietf@ietf.org>; Thu, 18 Apr 2013 13:51:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1366318272; x=1397854272; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=5azU0UaPlKpQrCzq0pCllcVNsiyoEdOYnhvkLPSpJjI=; b=NqmneZlnuJE9G4OrM3qGQ++4ZddtKi94DC2lzbeREeyrVNzVapqmSRvV 4z6sPjaBM5h9Rs82f/rRPloYTxEjKHd5Cp5NydrR+mE3jpXpCau4oa6AQ pEtNNEMnoHQsogkS2w2DNPwUC7Js2b18+9tugH0egY88+IZVROaCqM1B5 A=;
X-IronPort-AV: E=Sophos;i="4.87,504,1363158000"; d="scan'208";a="39702536"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 18 Apr 2013 13:51:09 -0700
X-IronPort-AV: E=Sophos;i="4.87,503,1363158000"; d="scan'208";a="460916045"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 18 Apr 2013 13:51:09 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 18 Apr 2013 13:51:09 -0700
Message-ID: <51705CB6.9080809@qti.qualcomm.com>
Date: Thu, 18 Apr 2013 15:51:02 -0500
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: Dan Harkins <dharkins@lounge.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>	<8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com>	<5167211A.8080807@wonderhamster.org>	<CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com>	<CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>	<20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com>	<20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com>	<13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>	<51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net>	<5168C159.3050004@gmail.com> <51694B16.4090504@labn.net>	<51695398.3000708@cs.tcd.ie>	<7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org>	<38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net>	<516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net>
In-Reply-To: <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.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" <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, 18 Apr 2013 20:51:14 -0000

On 4/17/13 2:21 PM, Dan Harkins wrote:
> Look, bias stinks and when it exists its stench is detectable.

Dan, leaving aside all of your other comments for the moment (many of 
which are straw men that nobody but you have suggested, speaking of 
fallacies), this one comment is a serious problem since it is so 
demonstrably false. Bias creeps in in all sorts of undetectable ways; if 
it was always detectable, lots of statisticians and psychologists and 
survey designers would be out of jobs. Aside from simple methodological 
data collection problems, bias is often caused by completely unconscious 
(and sometimes well intentioned) behaviors when it comes to human 
endeavors. The literature on this topic is so extensive that I can't 
even imagine why you would even suggest the opposite.

> We already know "who we are".

That's an interesting claim, and at least at first glance given other 
comments on the list, again seemingly false. As Adrian commented, 
perception is important. If it seems to some folks that the ratio of men 
to women throughout the IETF is 70:1, should it turn out that it is 
closer to 10:1 and the numbers in leadership are closer to 30:1, that 
would not only indicate that we don't "already know 'who we are'", but 
it could also be an interesting indication of why there might be 
statistical bias in the selection of leadership. (Or not. But it seems 
worthy of examination.)

That's my two message limit for the day on the IETF list.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From mrex@sap.com  Thu Apr 18 14:22:32 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB48B21F9019; Thu, 18 Apr 2013 14:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.949
X-Spam-Level: 
X-Spam-Status: No, score=-9.949 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ljHjcRAGZTx2; Thu, 18 Apr 2013 14:22:30 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 315C921F8FF3; Thu, 18 Apr 2013 14:22:30 -0700 (PDT)
Received: from mail06.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r3ILMJCM007690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Apr 2013 23:22:19 +0200 (MEST)
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc2560bis-15.txt> (X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP) to Proposed Standard
In-Reply-To: <516E9860.2090703@secunet.com>
To: Johannes Merkle <johannes.merkle@secunet.com>
Date: Thu, 18 Apr 2013 23:22:19 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130418212219.93D0A1A6BD@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Piyush Jain <piyush@ditenity.com>, ietf@ietf.org, pkix@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: Thu, 18 Apr 2013 21:22:32 -0000

Johannes Merkle wrote:
>
>> Limitations
>> ~~~~~~~~
>> - Works only if attacker fraudulently issued a certificate with a serial
>> that is not associated with a good certificate.
> 
> This can be remedied by using an extension in which a server providing
> white-list information conveys a hash of the (genuine) certificate
> having this serial number. Note, that such an extension does not only
> exist but is already used in the context of qualified certificates
> in Germany: CertHash (OID 1.3.36.8.3.13), defined in CommonPKI.

Including URLs for publicly availble specs&infos will be appreciated!
(it is my first encounter with CommonPKI)


Peter Rybar seemed to have suggested inclusion of CertHash in July 2012:
  http://www.ietf.org/mail-archive/web/pkix/current/msg31385.html

but only had a reference to a powerpoint presentation from 2004
with an "experimental" tag.


Google led me here:
  http://www.t7ev.org/ws/T7-en/Common-PKI-V20-Specification

The v2.0 specification PDF document is a concatenation of several documents,

In Common PKI Part 4: Operational Protocols (page 150 of 361) there
is the definition of a CertHash extension to be used in OCSP response
singleExtension:

  3.1.2  Common PKI Private OCSP Extensions

  Table 15: CertHash (Positive Statement)

  id-commonpki-at-certHash OBJECT IDENTIFIER ::= {1 3 36 8 3 13}

  CertHash ::= SEQUENCE {
      hashAlgorithm      AlgorithmIdentifier,
      certificateHash    OCTET STRING }


  certificateHash  -- A hash over the DER-encoding of the entire PKC or
  AC (i.e. NOT a hash over tbsCertificate).

     [...]

  Common PKI Profile: The responder may include this extension in a
  response to send the hash of the requested certificate to the responder.
  This hash is cryptographically bound to the certificate and serves as
  evidence that the certificate is known to the responder (i.e. it has
  been issued and is present in the directory).  Hence, this extension
  is a means to provide a positive statement of availability as described
  in T8.[8].  As explained in T13.[1], clients may rely on this information
  to be able to validate signatures after the expiry of the corresponding
  certificate. Hence, clients MUST support this extension.  If a positive
  statement of availability is to be delivered, this extension syntax
  and OID MUST be used.


CommonPKI seems to be about qualified electronic signatures for the German
Digital Signature Act.  Are there any similar standards published
by other (european or otherwise) countries for an private OCSP extension
with a positive statement about certificate issuance?


I think we should have added this to rfc2560bis!

-Martin

From dharkins@lounge.org  Thu Apr 18 14:47:48 2013
Return-Path: <dharkins@lounge.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 E84B221F8FF3 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 14:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmcEYgDSkCKk for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 14:47:48 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 5D46321F8FC6 for <ietf@ietf.org>; Thu, 18 Apr 2013 14:47:48 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id AF853A888008; Thu, 18 Apr 2013 14:47:44 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Thu, 18 Apr 2013 14:47:44 -0700 (PDT)
Message-ID: <4ea25dd8538b2c5fc54a1a4415dc4ee4.squirrel@www.trepanning.net>
In-Reply-To: <51705CB6.9080809@qti.qualcomm.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <51705CB6.9080809@qti.qualcomm.com>
Date: Thu, 18 Apr 2013 14:47:44 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: "Pete Resnick" <presnick@qti.qualcomm.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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, 18 Apr 2013 21:47:49 -0000

On Thu, April 18, 2013 1:51 pm, Pete Resnick wrote:
> On 4/17/13 2:21 PM, Dan Harkins wrote:
>> Look, bias stinks and when it exists its stench is detectable.
>
> Dan, leaving aside all of your other comments for the moment (many of
> which are straw men that nobody but you have suggested, speaking of
> fallacies), this one comment is a serious problem since it is so
> demonstrably false.

  I'm sure I speak alone when I say that I hope you are only leaving my other
comments aside for a moment and will return to them later. I would actually
like to see a response that doesn't snip a 30-40 line post into 1 sentence.

  If you would like to engage me off-list, I welcome that.

>                                 Bias creeps in in all sorts of
undetectable ways; if
> it was always detectable, lots of statisticians and psychologists and
> survey designers would be out of jobs. Aside from simple methodological
> data collection problems, bias is often caused by completely unconscious
> (and sometimes well intentioned) behaviors when it comes to human
> endeavors. The literature on this topic is so extensive that I can't
> even imagine why you would even suggest the opposite.

  Now we're playing a subtle word game here. A bias that a statistician
might add is demonstrably different than what Melinda Shore has
_repeatedly_ referred to as "gender bias". So when I'm talking about
bias I'm talking about a form of discrimination based on gender. It is
the intentional passing over of a more qualified woman in favor of a
less qualified man. Exactly the same thing that is being referred to
when she says:

  "I'm telling you that I think the numbers are highly suggestive of bias".

What numbers are those? The observable numbers about I* leadership.
What is the bias being suggested? It is a bias against women. Straw
man? I think not.

  A statistician might put bias in his statistical result and a survey
designer might put bias in a question to elicit a favored result,
intentionally or unintentionally. But we both know that is not what
we're talking about here.

>> We already know "who we are".
>
> That's an interesting claim, and at least at first glance given other
> comments on the list, again seemingly false. As Adrian commented,
> perception is important. If it seems to some folks that the ratio of men
> to women throughout the IETF is 70:1, should it turn out that it is
> closer to 10:1 and the numbers in leadership are closer to 30:1, that
> would not only indicate that we don't "already know 'who we are'", but
> it could also be an interesting indication of why there might be
> statistical bias in the selection of leadership. (Or not. But it seems
> worthy of examination.)

  "We" are a volunteer standards organization that operates on a
consensus basis. For the purposes of "who we are" the number of
women that register for a meeting should be as relevant as the number
of people who register that are left handed, flat footed or double jointed
(for the record I am all three). In other words, not at all. There may be
a statistical bias in the selection of leadership that favors left-handedness
or maybe it disfavors left-handedness. Is that interesting? Maybe to
someone. Is it worthwhile in finding out "who we are"? No.

  Dan.



From presnick@qti.qualcomm.com  Thu Apr 18 15:24:36 2013
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 7AB2521F8F2E for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 15:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZ5qPyo-c2Cf for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 15:24:35 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 77EBE21F882A for <ietf@ietf.org>; Thu, 18 Apr 2013 15:24:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1366323875; x=1397859875; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=PCBQ6sXyude+nhLmcXLY21P3NzdfluXNqg2T+VIN8FM=; b=IGoVHYvr374CCDuHVHPNaXeASKy7FSlfvg4HzSp7+Aj/AmZkdftU+ZQT 1ApDO4aN2mi0fbpD7EVBwrq0zWh0hGGSSJCKnXWF9+nLyed9yO4t2yGUV Dfub2bVoY7N5k7bIAmNdsbATqDMNMDDAKYyJSaSiM9QFGdtvC64hZwYEF 0=;
X-IronPort-AV: E=Sophos;i="4.87,504,1363158000"; d="scan'208";a="35723785"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth02.qualcomm.com with ESMTP; 18 Apr 2013 15:24:35 -0700
X-IronPort-AV: E=Sophos;i="4.87,504,1363158000"; d="scan'208";a="435366956"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 18 Apr 2013 15:24:34 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 18 Apr 2013 15:24:34 -0700
Message-ID: <517072A0.1070009@qti.qualcomm.com>
Date: Thu, 18 Apr 2013 17:24:32 -0500
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: Dan Harkins <dharkins@lounge.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org>	<CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com>	<CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com>	<20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com>	<20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com>	<13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>	<51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net>	<5168C159.3050004@gmail.com> <51694B16.4090504@labn.net>	<51695398.3000708@cs.tcd.ie>	<7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org>	<38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net>	<516EB736.6060801@cisco.com>	<8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net>	<51705CB6.9080809@qti.qualcomm.com> <4ea25dd8538b2c5fc54a1a4415dc4ee4.squirrel@www.trepanning.net>
In-Reply-To: <4ea25dd8538b2c5fc54a1a4415dc4ee4.squirrel@www.trepanning.net>
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" <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, 18 Apr 2013 22:24:36 -0000

Damn. Breaking my two message rule.

On 4/18/13 4:47 PM, Dan Harkins wrote:

>    Now we're playing a subtle word game here. A bias that a statistician
> might add is demonstrably different than what Melinda Shore has
> _repeatedly_ referred to as "gender bias". So when I'm talking about
> bias I'm talking about a form of discrimination based on gender. It is
> the intentional passing over of a more qualified woman in favor of a
> less qualified man.

It's so nice when the straw men stand up and say, "Here I am! Look at me!"

"Intentional passing over"? "Intentional"???

I defy you to find anywhere in Melinda's messages.... Strike that: I 
defy you to find anywhere in *anybody's* messages on this topic where it 
says that the problem suspected is *intentional* gender bias.

Overt intentional sexists and other such bigots are never a problem of 
this sort; they're sincere in their beliefs easy to identify. Finding 
and eliminating their sort of bias is a walk in the park. It's the 
*unintentional* and *institutional* and *structural* biases that are the 
ones that creep in all over the place and are the least detectable.

If you think that all of this discussion is about intentional bias, you 
have been talking to yourself.

>    A statistician might put bias in his statistical result and a survey
> designer might put bias in a question to elicit a favored result,
> intentionally or unintentionally. But we both know that is not what
> we're talking about here.
>    

Nonsense. That is exactly what we are talking about, whether it's how we 
ADs choose chairs, or how chairs choose document editors, or how we all 
choose nominees for the IESG or IAB, etc. If any of us thought we were 
talking about intentional bias, we would have packed up and gone home 
long ago.

>    "We" are a volunteer standards organization that operates on a
> consensus basis. For the purposes of "who we are" the number of
> women that register for a meeting should be as relevant as the number
> of people who register that are left handed, flat footed or double jointed
> (for the record I am all three). In other words, not at all.

All of those features *should* be equally relevant (i.e., not at all). 
And if you could design an interesting addition to the Harvard Implicit 
Association Test <https://implicit.harvard.edu/implicit/demo/> that 
showed whether people are or aren't unconsciously biased when it comes 
to left-handedness or flat-footedness or hypermobility (I hate that 
other term), I'm sure the Harvard folks would love to hear from you. But 
there *is* loads of nice evidence about unconscious bias when it comes 
to gender, especially when it comes to leadership roles and roles in 
engineering. I suspect (but until you design that test, can't provide 
evidence) that we *do* ignore (even subconsciously) left-handedness and 
flat-footedness and hypermobility when it comes to leadership positions 
in the IETF. But I also suspect that we are subconsciously influenced 
when it comes to gender bias; indeed, given what I know of the 
literature, it would be hard to imagine that we in the IETF are the 
astounding exception. So I think it's worth examining, especially given 
some of the interesting perceptual anecdotes seen already.

So, do we need to start this entire conversation over, overtly stating 
that we are not interested in looking at *intentional* gender (or 
corporate affiliation or other sorts of) bias?

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From dharkins@lounge.org  Thu Apr 18 16:23:05 2013
Return-Path: <dharkins@lounge.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 0457A21F8DE4 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 16:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.666
X-Spam-Level: 
X-Spam-Status: No, score=-3.666 tagged_above=-999 required=5 tests=[IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pLOKv6eh8sBX for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 16:23:04 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA8F21F8CEE for <ietf@ietf.org>; Thu, 18 Apr 2013 16:23:04 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 0722BA88800E; Thu, 18 Apr 2013 16:23:04 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Thu, 18 Apr 2013 16:23:04 -0700 (PDT)
Message-ID: <78e7849061fe8b25e5669833996639db.squirrel@www.trepanning.net>
In-Reply-To: <517072A0.1070009@qti.qualcomm.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <51705CB6.9080809@qti.qualcomm.com> <4ea25dd8538b2c5fc54a1a4415dc4ee4.squirrel@www.trepanning.net> <517072A0.1070009@qti.qualcomm.com>
Date: Thu, 18 Apr 2013 16:23:04 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: "Pete Resnick" <presnick@qti.qualcomm.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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, 18 Apr 2013 23:23:05 -0000

On Thu, April 18, 2013 3:24 pm, Pete Resnick wrote:
> So, do we need to start this entire conversation over, overtly stating
> that we are not interested in looking at *intentional* gender (or
> corporate affiliation or other sorts of) bias?

  Actually I think it would be better to explicitly state what is intended
to be done. If you think that we are subconsciously influenced when
it comes to gender bias then I'd like to know what is going to be done
about it. And if it's more than "nothing" then I'd like to know what our
goal is vis-a-vis the gender breakdown of leadership positions and
the lengths that we will go to ensure we reach it.

  If we're just gathering data to make a pie chart for the plenary then
it seems like a waste of time.

  Dan.




From dwm@xpasc.com  Thu Apr 18 16:53:57 2013
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 C2A2721F86F2 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 16:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.581
X-Spam-Level: *
X-Spam-Status: No, score=1.581 tagged_above=-999 required=5 tests=[MISSING_HEADERS=1.581]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ShRuA0sAgPqT for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 16:53:57 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 6108C21F86EA for <ietf@ietf.org>; Thu, 18 Apr 2013 16:53:57 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id C57FB40065 for <ietf@ietf.org>; Thu, 18 Apr 2013 23:53:56 +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 r3INruDG004362 for <ietf@ietf.org>; Thu, 18 Apr 2013 16:53:56 -0700
Date: Thu, 18 Apr 2013 16:53:56 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <78e7849061fe8b25e5669833996639db.squirrel@www.trepanning.net>
Message-ID: <alpine.LRH.2.01.1304181644440.1990@egate.xpasc.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <51705CB6.9080809@qti.qualcomm.com> <4ea25dd8538b2c5fc54a1a4415dc4ee4.squirrel@www.trepanning.net> <517072A0.1070009@qti.qualcomm.com> <78e7849061fe8b25e5669833996639db.squirrel@www.trepanning.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: Thu, 18 Apr 2013 23:53:57 -0000

On Thu, 18 Apr 2013, Dan Harkins wrote:

> 
> On Thu, April 18, 2013 3:24 pm, Pete Resnick wrote:
> > So, do we need to start this entire conversation over, overtly stating
> > that we are not interested in looking at *intentional* gender (or
> > corporate affiliation or other sorts of) bias?
> 
>   Actually I think it would be better to explicitly state what is intended
> to be done. If you think that we are subconsciously influenced when
> it comes to gender bias then I'd like to know what is going to be done
> about it. And if it's more than "nothing" then I'd like to know what our
> goal is vis-a-vis the gender breakdown of leadership positions and
> the lengths that we will go to ensure we reach it.
> 
>   If we're just gathering data to make a pie chart for the plenary then
> it seems like a waste of time.

Without gathering a baseline, it makes no sense to postulate mitigations
because there is no way to judge progress.

Others have already noted that there are several different points of
concern. By measurement, it may be possible to establish that IESG
gender membership tracks general meeting attendance (or doesn't
track meeting attendance). If it tracks meeting attendance it
seems reasonable to finds ways to increase participation by
the underrepresented population in the whole IETF. If it doesn't
track the general population, then more detailed analysis is
needed of the process of selecting IESG members.

Collecting population characteristics is the first baby step.

From Ted.Lemon@nominum.com  Thu Apr 18 16:58:06 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E063721F91B2 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 16:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104
X-Spam-Level: 
X-Spam-Status: No, score=-104 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5neE-VrBV9Gr for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 16:58:06 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5F9DF21F8733 for <ietf@ietf.org>; Thu, 18 Apr 2013 16:58:06 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUXCIjsbg/t3k21xXVrVVfjFcmuWbbkrZ@postini.com; Thu, 18 Apr 2013 16:58:06 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 07C631B8136 for <ietf@ietf.org>; Thu, 18 Apr 2013 16:58:06 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F18FF190061; Thu, 18 Apr 2013 16:58:05 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 18 Apr 2013 16:58:06 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Dan Harkins <dharkins@lounge.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHONsbesxw5RhqwwUuIKG4LfyrlCZjR4Y8AgAAKbwCAAAcIAIAAATgAgAAEloCAAADsgIAAAUgAgAAGmYCAADL0gIABJeUAgAAFsoCAAAi6gIAAAfoAgAAlvoCAAFKcgIAApDIAgAAKJQCAACqHgIADtoYAgAKLlQCAAEscAIABq1sAgAAP2ACAAApIAIAAEFoA//+Ucdo=
Date: Thu, 18 Apr 2013 23:58:05 +0000
Message-ID: <BC3F8FFD-9FCA-42D5-ADE2-9AB419BAC6F7@nominum.com>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com> <51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com> <51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie>	<7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <51705CB6.9080809@qti.qualcomm.com> <4ea25dd8538b2c5fc54a1a4415dc4ee4.squirrel@www.trepanning.net> <517072A0.1070009@qti.qualcomm.com>, <78e7849061fe8b25e5669833996639db.squirrel@www.trepanning.net>
In-Reply-To: <78e7849061fe8b25e5669833996639db.squirrel@www.trepanning.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.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: Thu, 18 Apr 2013 23:58:07 -0000

On Apr 18, 2013, at 7:23 PM, "Dan Harkins" <dharkins@lounge.org> wrote:
>  Actually I think it would be better to explicitly state what is intended
> to be done.

This is what we are trying to figure out!

From ajs@anvilwalrusden.com  Thu Apr 18 18:44:50 2013
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 9704021F92BC for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 18:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.759
X-Spam-Level: *
X-Spam-Status: No, score=1.759 tagged_above=-999 required=5 tests=[HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nXRMZ6iG4f-9 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 18:44:50 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 2207021F8CEE for <ietf@ietf.org>; Thu, 18 Apr 2013 18:44:49 -0700 (PDT)
Received: from mx1.yitter.info (c-50-136-77-224.hsd1.nh.comcast.net [50.136.77.224]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E66098A031 for <ietf@ietf.org>; Fri, 19 Apr 2013 01:44:48 +0000 (UTC)
Date: Thu, 18 Apr 2013 21:44:47 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <20130419014446.GC1113@mx1.yitter.info>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.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: Fri, 19 Apr 2013 01:44:50 -0000

On Thu, Apr 18, 2013 at 08:17:21AM -0700, Dan Harkins wrote:
> white and male. The fallacy works like this:
> 
>     "If there was bias in favor of white males then we would have a
>      leadership that is predominantly white and male. We have a
>      leadership that is predominantly white and male, therefore we
>      have bias."

Just for the record, that is not a line of reasoning I am taking.

The line I am taking is something more like the following.  First,
assume that, if there were bias in favour of (we're not testing for
white, so I'm leaving that out) males, there might be an observable
pattern of difference between the percentage of women in "leadership"
positions and the percentage of women in overall participants.  So,
look at the "leadership" and the general participant populations over
time.  If there appears to be a difference, then that is reason to
encourage further inquiry.  If there appears to be no difference, then
we are justified in saying that there is no evidence of an issue.

That approach is just basic empiricism, and not the fallacy of
affirming the consequent that you're claiming people are making.  If
such an approach is controversial, then every modern empirical science
is on a shaky footing.  It's certainly true (Hume makes this point
rather more eloquently than I can) that such empirical argument is
_formally_ false.  But that's the wrong criterion, because empirical
argument is useful.  Even Hume played billiards.
 
>   So a problem statement has been made: there is a notable lack of
> diversity in the areas of race and gender. Why is this a problem? 

Because some people report that they experience a chilly environment,
and we respect those people for their other contributions and would
like more people like them to contribute in similar ways, and
therefore we want to make the environment less chilly.  I'm sort of
surprised that that problem, which has been stated in my view quite
plainly more than once in this thread, isn't evident to anyone
participating.

>   If this is just some innocent question to find out "who we are" then why
> don't we ask about the size of the organization we work for? 

We don't need to.  A large number of participants include an
affiliation, and using by and large public data we could just find
this out using the data we already have.  I agree it would be useful.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dharkins@lounge.org  Thu Apr 18 20:59:33 2013
Return-Path: <dharkins@lounge.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 69DF321F9387 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 20:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.966
X-Spam-Level: 
X-Spam-Status: No, score=-4.966 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08acd556rFBQ for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 20:59:33 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id F0ABD21F9385 for <ietf@ietf.org>; Thu, 18 Apr 2013 20:59:32 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 9129EA88800E; Thu, 18 Apr 2013 20:59:32 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Thu, 18 Apr 2013 20:59:32 -0700 (PDT)
Message-ID: <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net>
In-Reply-To: <20130419014446.GC1113@mx1.yitter.info>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info>
Date: Thu, 18 Apr 2013 20:59:32 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: "Andrew Sullivan" <ajs@anvilwalrusden.com>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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, 19 Apr 2013 03:59:33 -0000

On Thu, April 18, 2013 6:44 pm, Andrew Sullivan wrote:
> On Thu, Apr 18, 2013 at 08:17:21AM -0700, Dan Harkins wrote:
>>   So a problem statement has been made: there is a notable lack of
>> diversity in the areas of race and gender. Why is this a problem?
>
> Because some people report that they experience a chilly environment,
> and we respect those people for their other contributions and would
> like more people like them to contribute in similar ways, and
> therefore we want to make the environment less chilly.  I'm sort of
> surprised that that problem, which has been stated in my view quite
> plainly more than once in this thread, isn't evident to anyone
> participating.

  Well, that is certainly not the message that I read. What I read was
that the I* leadership is 97% male (and 97% white) and that alone
puts into question the legitimacy of the IETF as an International
Standards Development Organization. If people are encountering a
chilly environment then that is a different issue.

  It has been a few IETFs since I've heard someone approach the mic
and say "that is the stupidest idea I've heard in a long time" and a few
more since it was said to me. That kind of brusqueness is part of our
culture but I think it can be off-putting and a barrier to contributing.
New people get intimidated around a bunch of aggressive type-A
personalities and may be reluctant to present or contribute for fear
of being put down.

  If we want to make the IETF a less chilly place that is more inviting
and we want to encourage participation maybe we should address
our cultural tics and idiosyncrasies that represent a barrier to entry
rather than enumerate the women who have registered for a meeting.
(And yes, I am talking about myself).

  regards,

  Dan.



From narten@us.ibm.com  Thu Apr 18 21:53:10 2013
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 D81AE21F93EB for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 21:53:09 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N7gXEdQiZR06 for <ietf@ietfa.amsl.com>; Thu, 18 Apr 2013 21:53:08 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id A1F4121F93CC for <ietf@ietf.org>; Thu, 18 Apr 2013 21:53:07 -0700 (PDT)
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, 19 Apr 2013 00:53:07 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 19 Apr 2013 00:53:06 -0400
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 5FBC238C801A for <ietf@ietf.org>; Fri, 19 Apr 2013 00:53:05 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r3J4r5VY56623354 for <ietf@ietf.org>; Fri, 19 Apr 2013 00:53:05 -0400
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 r3J4r57U022101 for <ietf@ietf.org>; Fri, 19 Apr 2013 01:53:05 -0300
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 r3J4r407022039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 19 Apr 2013 01:53:04 -0300
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 r3J4r3iL025177 for <ietf@ietf.org>; Fri, 19 Apr 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r3J4r32a025131 for ietf@ietf.org; Fri, 19 Apr 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201304190453.r3J4r32a025131@rotala.raleigh.ibm.com>
Date: Fri, 19 Apr 2013 00:53:03 -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-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13041904-9360-0000-0000-000011CE66AE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Apr 2013 04:53:10 -0000

Total of messages in the last 7 days.
 
script run at: Fri Apr 19 00:53:03 EDT 2013
 


From l.wood@surrey.ac.uk  Fri Apr 19 01:29:28 2013
Return-Path: <l.wood@surrey.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 A4EBB21F9026 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 01:29:28 -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, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vVUM9OzlfdBA for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 01:29:27 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.151]) by ietfa.amsl.com (Postfix) with ESMTP id 0015A21F86B2 for <ietf@ietf.org>; Fri, 19 Apr 2013 01:29:26 -0700 (PDT)
Received: from [195.245.231.67:45969] by server-15.bemta-5.messagelabs.com id 59/ED-22815-46001715; Fri, 19 Apr 2013 08:29:24 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-82.messagelabs.com!1366360162!30816417!5
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1073 invoked from network); 19 Apr 2013 08:29:23 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-4.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 19 Apr 2013 08:29:23 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Fri, 19 Apr 2013 09:27:34 +0100
From: <l.wood@surrey.ac.uk>
To: <ynir@checkpoint.com>
Date: Fri, 19 Apr 2013 09:23:45 +0100
Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOO6uAkYNXJKWRyEmIKVS5GuPId5jbdJGAgAAIsICAAEJXWoAARRgggAEyZAA=
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E70@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>, <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E6C@EXMB01CMS.surrey.ac.uk>, <4613980CFC78314ABFD7F85CC302772111A0F977@IL-EX10.ad.checkpoint.com>
In-Reply-To: <4613980CFC78314ABFD7F85CC302772111A0F977@IL-EX10.ad.checkpoint.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 19 Apr 2013 08:29:28 -0000

and the point of your ad-hominem argument is what, exactly?

Lloyd Wood
http://sat-net.com/L.Wood/publications/internet-drafts


________________________________________
From: Yoav Nir [ynir@checkpoint.com]
Sent: 18 April 2013 15:18
To: Wood L  Dr (Electronic Eng)
Cc: worley@ariadne.com; ietf@ietf.org
Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IESG=
     Review)

Looking in Jari's statistics site, you have three RFCs. One of those has se=
veral co-authors that I recognize as current "goers". You also have a curre=
nt draft with several co-authors, but I have no idea whether they're "goers=
" or not. Anyway, you are not a hermit. Through the RFCs and drafts that yo=
u have co-authored, you know people who do attend.

From l.wood@surrey.ac.uk  Fri Apr 19 01:30:38 2013
Return-Path: <l.wood@surrey.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 DEF8E21F93FB for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 01:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LC114sxvIT3A for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 01:30:38 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.118]) by ietfa.amsl.com (Postfix) with ESMTP id EB75021F86B2 for <ietf@ietf.org>; Fri, 19 Apr 2013 01:30:37 -0700 (PDT)
Received: from [193.109.255.147:3065] by server-14.bemta-14.messagelabs.com id B8/33-05867-DA001715; Fri, 19 Apr 2013 08:30:37 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-72.messagelabs.com!1366360236!9407822!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4417 invoked from network); 19 Apr 2013 08:30:36 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-4.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 19 Apr 2013 08:30:36 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Fri, 19 Apr 2013 09:30:36 +0100
From: <l.wood@surrey.ac.uk>
To: <brian.e.carpenter@gmail.com>, <presnick@qti.qualcomm.com>
Date: Fri, 19 Apr 2013 09:29:31 +0100
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: Ac48S3/SCrxCtkklS1e8i1wuxl54QAAjIOtg
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E71@EXMB01CMS.surrey.ac.uk>
References: <A58F3AAE-4910-4603-88F9-CFF333D05E77@isoc.org> <6.2.5.6.2.20130411101504.0c42fed0@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751400CC@mbx-01.win.nominum.com> <5167211A.8080807@wonderhamster.org> <CAHiKxWhii-WXbRGdivZ=Jw-JvvcJd31WKF3qu0cBNOk-rDu1=g@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B6307751412A3@mbx-01.win.nominum.com> <CAHiKxWjSVwwa53qWrydQ6OoUs-X=qZjhqomLB19haLTN_EHJZA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077514133E@mbx-01.win.nominum.com> <20130411213835.GA8968@cisco.com>	<51675819.9070302@gmail.com> <20130412181250.GA14224@cisco.com>	<51685369.4000306@gmail.com> <13dffa24b35.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <51685C64.3010803@gmail.com> <201304122037.r3CKb3IM013046@rcdn-core-2.cisco.com> <51701125.1060802@qti.qualcomm.com>,<5170148D.9090204@gmail.com>
In-Reply-To: <5170148D.9090204@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 19 Apr 2013 08:30:39 -0000

A statistician? This entire thread is basically arguing that the IETF needs=
 a human resources department.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Brian E Ca=
rpenter [brian.e.carpenter@gmail.com]
Sent: 18 April 2013 16:43
To: Pete Resnick
Cc: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?

On 18/04/2013 16:28, Pete Resnick wrote:
...
> That's a factor of between 4 and 7 difference between an "eyeball" guess
> and a rough calculation. I think that's likely an unintentional sampling
> bias of your (and many other folks) eyeballs. And I think it's because
> we have a tendency to subconsciously discount the numbers of people who
> do not appear in leadership, or even simply don't behave "the way the
> rest of us do".
>
> This isn't to say that we should spend all of our time on this question
> by collecting statistics; that's just navel gazing. But we do want to
> understand the nature of the problem and not let our guesses and
> subconscious biases get in the way.

Indeed. Ideally, though, we need a statistician to look at the
historical ratios (e.g. M/F ratios) in the attendee lists vs the
I* membership, to see whether there is a statistically significant
bias in the selection process over the years.

   Brian

From ynir@checkpoint.com  Fri Apr 19 02:08:47 2013
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 2722121F9436 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 02:08:47 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hynZUw0fiT4Z for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 02:08:46 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id EA29921F9434 for <ietf@ietf.org>; Fri, 19 Apr 2013 02:08:45 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r3J92I0O018203; Fri, 19 Apr 2013 12:06:32 +0300
X-CheckPoint: {5171077A-C-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Fri, 19 Apr 2013 12:02:20 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOO6uAkYNXJKWRyEmIKVS5GuPId5jbdJGAgAAIsICAAEJXWoAARRgggAEyZAD//9h6AA==
Date: Fri, 19 Apr 2013 09:02:20 +0000
Message-ID: <E49D2A72-8E1F-472E-B0CC-EF00E86AE526@checkpoint.com>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>, <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E6C@EXMB01CMS.surrey.ac.uk>, <4613980CFC78314ABFD7F85CC302772111A0F977@IL-EX10.ad.checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E70@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E70@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.250]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <093F11151CAE0F40AFA9CE0B49811648@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: Fri, 19 Apr 2013 09:08:47 -0000

Only that you know enough people so that you could push a new technology ev=
en without attending, although you would need to collaborate with some peop=
le who do go. But pushing a new technology requires team building anyway.

The same should apply to other non-attenders who have gained some reputatio=
n.


On Apr 19, 2013, at 11:23 AM, l.wood@surrey.ac.uk wrote:

>=20
> and the point of your ad-hominem argument is what, exactly?
>=20
> Lloyd Wood
> http://sat-net.com/L.Wood/publications/internet-drafts
>=20
>=20
> ________________________________________
> From: Yoav Nir [ynir@checkpoint.com]
> Sent: 18 April 2013 15:18
> To: Wood L  Dr (Electronic Eng)
> Cc: worley@ariadne.com; ietf@ietf.org
> Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IE=
SG     Review)
>=20
> Looking in Jari's statistics site, you have three RFCs. One of those has =
several co-authors that I recognize as current "goers". You also have a cur=
rent draft with several co-authors, but I have no idea whether they're "goe=
rs" or not. Anyway, you are not a hermit. Through the RFCs and drafts that =
you have co-authored, you know people who do attend.


From abdussalambaryun@gmail.com  Fri Apr 19 02:37:51 2013
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 2C33C21F937B for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 02:37:51 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CHbQBs99009U for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 02:37:50 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 9D59A21F902A for <ietf@ietf.org>; Fri, 19 Apr 2013 02:37:50 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id uo1so59215pbc.5 for <ietf@ietf.org>; Fri, 19 Apr 2013 02:37:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=NtqF66W8d/cUe/tZoEp87GL1YG+TbYCC6NIlALAwvYk=; b=mtjkMqndew3wiL8fu1WUu8EcUikhgXwI0suB0WxbHX2I8QTRydG5W06hQTR7xxm98x 1EYemENnJYBSl18ygXAZHCsZcnjaEkIkIX/F2vBLIA8dQYBmFBrYAvhz4cBFdpgxyg0e vFLI0CeLQXlmlqopnHcXXngZQoLVwoizDguZ2oq1DPKUbdeNhP1R5pJRNJpAbZs6xMFC r7KznQYqvbintGBxP4BywQEeUxx2RZIrYeKxfmHmxulcT58XB4hgpYPx8DJGfLX9X0zw L7L1lpO6laTZYC7GVJc5ff+QOSPjYmnqtK4XYtCQFp5IpUDgnhBi9e+2L5Yp+Na1/UNd 4eMg==
MIME-Version: 1.0
X-Received: by 10.68.43.35 with SMTP id t3mr18477157pbl.202.1366364270362; Fri, 19 Apr 2013 02:37:50 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Fri, 19 Apr 2013 02:37:50 -0700 (PDT)
In-Reply-To: <465602F9-A251-475A-9BC3-1AD4DAB5E2E9@piuha.net>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com> <465602F9-A251-475A-9BC3-1AD4DAB5E2E9@piuha.net>
Date: Fri, 19 Apr 2013 11:37:50 +0200
Message-ID: <CADnDZ8_5UqHGK_mGNzpqmrSCQnTf2WEu+QyBeeFrt3CXax=tQQ@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ajs@anvilwalrusden.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: Fri, 19 Apr 2013 09:37:51 -0000

Andrew

>Because some people report that they experience a chilly environment,
and we respect those people for their other contributions and would
like more people like them to contribute in similar ways, and
therefore we want to make the environment less chilly.  I'm sort of
surprised that that problem, which has been stated in my view quite
plainly more than once in this thread, isn't evident to anyone
participating.

The environment may not be chilly, but may be unaware of experience
(did we experience a woman as AD?). The IETF culture can be defined
IMO as a argumental experience (firstly) plus technical (secondly),
mostly men argue for long (may get unsensitive) but women may not
fancy that. The participants' bias is not in technical experience it
is in argumental, which is not true that all discussions on the IETF
lists are technical, most of the time just men arguing and when they
get lost in technical they get backed up with the consensus procedural
argument.

 I don't think women were given a chance to proof their ability to
lead the IETF, so men can be aware of new experience.

AB

From daedulus@btconnect.com  Fri Apr 19 03:09:03 2013
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 E729A21F8A80 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 03:09:03 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id umQmzok263Hq for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 03:09:03 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe002.messaging.microsoft.com [216.32.180.185]) by ietfa.amsl.com (Postfix) with ESMTP id 3355F21F8A08 for <ietf@ietf.org>; Fri, 19 Apr 2013 03:09:02 -0700 (PDT)
Received: from mail1-co1-R.bigfish.com (10.243.78.252) by CO1EHSOBE002.bigfish.com (10.243.66.65) with Microsoft SMTP Server id 14.1.225.23; Fri, 19 Apr 2013 10:09:02 +0000
Received: from mail1-co1 (localhost [127.0.0.1])	by mail1-co1-R.bigfish.com (Postfix) with ESMTP id 57ADE1603B2; Fri, 19 Apr 2013 10:09:02 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371I542I1432I1418Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz8275bh8275dh1033ILz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah304l1155h)
Received: from mail1-co1 (localhost.localdomain [127.0.0.1]) by mail1-co1 (MessageSwitch) id 136636611286102_25792; Fri, 19 Apr 2013 10:08:32 +0000 (UTC)
Received: from CO1EHSMHS026.bigfish.com (unknown [10.243.78.244])	by mail1-co1.bigfish.com (Postfix) with ESMTP id 06B0C6C0048; Fri, 19 Apr 2013 10:08:32 +0000 (UTC)
Received: from AMSPRD0711HT002.eurprd07.prod.outlook.com (157.56.250.181) by CO1EHSMHS026.bigfish.com (10.243.66.36) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 19 Apr 2013 10:08:31 +0000
Received: from DBXPRD0411HT002.eurprd04.prod.outlook.com (157.56.253.165) by pod51017.outlook.com (10.242.14.163) with Microsoft SMTP Server (TLS) id 14.16.293.5; Fri, 19 Apr 2013 10:08:18 +0000
Message-ID: <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Dan Harkins <dharkins@lounge.org>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie><7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org><38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net><516EB736.6060801@cisco.com><8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net><516EFC7E.90801@cisco.com><bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net><20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
Date: Fri, 19 Apr 2013 11:03:15 +0100
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.253.165]
X-FOPE-CRA-SourceIpAddress: 157.56.250.181
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: dharkins@lounge.org
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, 19 Apr 2013 10:09:04 -0000

----- Original Message -----
From: "Dan Harkins" <dharkins@lounge.org>
To: "Andrew Sullivan" <ajs@anvilwalrusden.com>
Cc: <ietf@ietf.org>
Sent: Friday, April 19, 2013 4:59 AM
On Thu, April 18, 2013 6:44 pm, Andrew Sullivan wrote:
> On Thu, Apr 18, 2013 at 08:17:21AM -0700, Dan Harkins wrote:
>>   So a problem statement has been made: there is a notable lack of
>> diversity in the areas of race and gender. Why is this a problem?
>
> Because some people report that they experience a chilly environment,
> and we respect those people for their other contributions and would
> like more people like them to contribute in similar ways, and
> therefore we want to make the environment less chilly.  I'm sort of
> surprised that that problem, which has been stated in my view quite
> plainly more than once in this thread, isn't evident to anyone
> participating.

  Well, that is certainly not the message that I read. What I read was
that the I* leadership is 97% male (and 97% white) and that alone
puts into question the legitimacy of the IETF as an International
Standards Development Organization.

<tp>
Yes, that is the message I am getting from this thread and it seems to
me to be a canard that originates from outside the IETF, perhaps in
groups promoting Diversity and Rights, as opposed to engineering.

I have encountered many network experts in my day job yet within the
IETF, I encounter a large number of seriously talented people, active on
many mailing lists, who are in a different league to the former group.
If we required the IETF to reflect the diversity of people who are,
e.g., IT network professionals, then the IETF would fall apart for lack
of ability.

And the IETF is unusual in its leadership.  Some organisations promote
the technically able, regardless of their lack of management skills, and
suffer as a result.  Leaders need to lead, and manage, and delegate the
technical aspects of the work.  The IETF is different.  WG Chairs and
ADs must have world-class technical skills - if anything, I think that
this comes at the expense of leadership, and sometimes wish that WG
Chairs and ADs had more management skills, but recognise that that must
not be at the expense of the technical skills.  Even so, being the most
brilliant editor of, say, a new security standard does not mean that the
person would make a good AD.

If the ADs of the IETF have to represent the diversity of the world -
which could in extremis be construed as so many Chinese, so many
Indians, so many Africans etc - then the IETF would be a less effective,
probably an ineffective, organisation.

So what's the problem?  And who says so?

Tom Petch

</tp>

If people are encountering a
chilly environment then that is a different issue.

  It has been a few IETFs since I've heard someone approach the mic
and say "that is the stupidest idea I've heard in a long time" and a few
more since it was said to me. That kind of brusqueness is part of our
culture but I think it can be off-putting and a barrier to contributing.
New people get intimidated around a bunch of aggressive type-A
personalities and may be reluctant to present or contribute for fear
of being put down.

  If we want to make the IETF a less chilly place that is more inviting
and we want to encourage participation maybe we should address
our cultural tics and idiosyncrasies that represent a barrier to entry
rather than enumerate the women who have registered for a meeting.
(And yes, I am talking about myself).

  regards,

  Dan.





From l.wood@surrey.ac.uk  Fri Apr 19 03:22:25 2013
Return-Path: <l.wood@surrey.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 6BEA821F91BF for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 03:22:24 -0700 (PDT)
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=[AWL=-1.000, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9T-kAR5B6tzo for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 03:22:21 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.147]) by ietfa.amsl.com (Postfix) with ESMTP id 1C23821F91B2 for <ietf@ietf.org>; Fri, 19 Apr 2013 03:22:19 -0700 (PDT)
Received: from [195.245.231.67:58371] by server-11.bemta-5.messagelabs.com id 6D/AF-27486-ADA11715; Fri, 19 Apr 2013 10:22:18 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-82.messagelabs.com!1366366937!24811909!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23029 invoked from network); 19 Apr 2013 10:22:17 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-5.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 19 Apr 2013 10:22:17 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Fri, 19 Apr 2013 11:22:17 +0100
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>, <ajs@anvilwalrusden.com>
Date: Fri, 19 Apr 2013 11:22:16 +0100
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: Ac484Z9ULfq5LuyHQxm6lmbQ1kx+QQABHKpg
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E72@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com> <465602F9-A251-475A-9BC3-1AD4DAB5E2E9@piuha.net>, <CADnDZ8_5UqHGK_mGNzpqmrSCQnTf2WEu+QyBeeFrt3CXax=tQQ@mail.gmail.com>
In-Reply-To: <CADnDZ8_5UqHGK_mGNzpqmrSCQnTf2WEu+QyBeeFrt3CXax=tQQ@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 19 Apr 2013 10:22:25 -0000

Female ADs include Allison Mankin, whose bio recently appeared on this list=
 in relation to her new appointment.

There's now a diversity discussion list, where this discussion should move =
to.

http://www.ietf.org/blog/2013/04/diversity/

Does what you think matter, when you clearly don't know anything?

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Abdussalam=
 Baryun [abdussalambaryun@gmail.com]
Sent: 19 April 2013 10:37
To: ajs@anvilwalrusden.com
Cc: ietf
Subject: Re: IETF Diversity Question on Berlin Registration?

Andrew

>Because some people report that they experience a chilly environment,
and we respect those people for their other contributions and would
like more people like them to contribute in similar ways, and
therefore we want to make the environment less chilly.  I'm sort of
surprised that that problem, which has been stated in my view quite
plainly more than once in this thread, isn't evident to anyone
participating.

The environment may not be chilly, but may be unaware of experience
(did we experience a woman as AD?). The IETF culture can be defined
IMO as a argumental experience (firstly) plus technical (secondly),
mostly men argue for long (may get unsensitive) but women may not
fancy that. The participants' bias is not in technical experience it
is in argumental, which is not true that all discussions on the IETF
lists are technical, most of the time just men arguing and when they
get lost in technical they get backed up with the consensus procedural
argument.

 I don't think women were given a chance to proof their ability to
lead the IETF, so men can be aware of new experience.

AB=

From narten@us.ibm.com  Fri Apr 19 04:04:00 2013
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 5403E21F867B for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 04:04:00 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BVXzq15scrCR for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 04:03:59 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 6ADF121F8632 for <ietf@ietf.org>; Fri, 19 Apr 2013 04:03:59 -0700 (PDT)
Received: from /spool/local by e9.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, 19 Apr 2013 07:03:58 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 19 Apr 2013 07:03:57 -0400
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id A27C038C801A for <ietf@ietf.org>; Fri, 19 Apr 2013 07:03:56 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r3JB3u0F282288 for <ietf@ietf.org>; Fri, 19 Apr 2013 07:03:56 -0400
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 r3JB3ufu020400 for <ietf@ietf.org>; Fri, 19 Apr 2013 07:03:56 -0400
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 r3JB3twi020357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 19 Apr 2013 07:03:56 -0400
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 r3JB3tU9026350 for <ietf@ietf.org>; Fri, 19 Apr 2013 07:03:55 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r3JB3tAi026318 for ietf@ietf.org; Fri, 19 Apr 2013 07:03:55 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201304191103.r3JB3tAi026318@rotala.raleigh.ibm.com>
Date: Fri, 19 Apr 2013 07:03:54 -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-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13041911-7182-0000-0000-0000064F97B3
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Apr 2013 11:04:00 -0000

Total of 166 messages in the last 7 days.
 
script run at: Fri Apr 19 07:03:54 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.43% |   14 |  7.88% |   102717 | ted.lemon@nominum.com
  5.42% |    9 |  6.32% |    82361 | abdussalambaryun@gmail.com
  4.82% |    8 |  4.51% |    58848 | dharkins@lounge.org
  4.82% |    8 |  4.28% |    55809 | sm@resistor.net
  4.22% |    7 |  4.07% |    53095 | brian.e.carpenter@gmail.com
  4.22% |    7 |  3.69% |    48105 | mrex@sap.com
  3.61% |    6 |  3.55% |    46274 | jari.arkko@piuha.net
  3.01% |    5 |  3.38% |    44125 | daedulus@btconnect.com
  3.01% |    5 |  3.13% |    40787 | l.wood@surrey.ac.uk
  3.01% |    5 |  3.04% |    39685 | lberger@labn.net
  3.01% |    5 |  2.92% |    38047 | lear@cisco.com
  3.01% |    5 |  2.68% |    34928 | arturo.servin@gmail.com
  3.01% |    5 |  2.66% |    34648 | mcr+ietf@sandelman.ca
  3.01% |    5 |  2.65% |    34524 | melinda.shore@gmail.com
  2.41% |    4 |  2.44% |    31868 | stefan@aaa-sec.com
  1.20% |    2 |  3.22% |    42039 | bclaise@cisco.com
  2.41% |    4 |  2.01% |    26265 | ajs@anvilwalrusden.com
  1.81% |    3 |  2.27% |    29558 | piyush@ditenity.com
  1.81% |    3 |  1.99% |    25906 | presnick@qti.qualcomm.com
  1.81% |    3 |  1.89% |    24681 | jmpolk@cisco.com
  1.81% |    3 |  1.82% |    23728 | hotz@jpl.nasa.gov
  1.81% |    3 |  1.73% |    22502 | eckert@cisco.com
  1.81% |    3 |  1.47% |    19149 | stephen.farrell@cs.tcd.ie
  1.20% |    2 |  1.58% |    20620 | ynir@checkpoint.com
  1.20% |    2 |  1.55% |    20220 | jdrake@juniper.net
  1.20% |    2 |  1.34% |    17510 | bmanning@isi.edu
  1.20% |    2 |  1.27% |    16543 | mstjohns@comcast.net
  1.20% |    2 |  1.20% |    15679 | doug.mtview@gmail.com
  1.20% |    2 |  1.16% |    15161 | andy@yumaworks.com
  1.20% |    2 |  1.14% |    14834 | fred@cisco.com
  1.20% |    2 |  1.10% |    14370 | pthaler@broadcom.com
  1.20% |    2 |  1.07% |    13969 | stbryant@cisco.com
  1.20% |    2 |  0.99% |    12953 | spencer@wonderhamster.org
  1.20% |    2 |  0.96% |    12572 | john-ietf@jck.com
  1.20% |    2 |  0.93% |    12070 | touch@isi.edu
  1.20% |    2 |  0.91% |    11908 | worley@ariadne.com
  0.60% |    1 |  1.15% |    15015 | dcrocker@bbiw.net
  0.60% |    1 |  0.80% |    10368 | narten@us.ibm.com
  0.60% |    1 |  0.78% |    10163 | barryleiba@computer.org
  0.60% |    1 |  0.77% |    10025 | farmer@umn.edu
  0.60% |    1 |  0.70% |     9176 | superuser@gmail.com
  0.60% |    1 |  0.70% |     9133 | scott@kitterman.com
  0.60% |    1 |  0.66% |     8599 | elwynd@dial.pipex.com
  0.60% |    1 |  0.62% |     8134 | adrian@olddog.co.uk
  0.60% |    1 |  0.61% |     7946 | huitema@microsoft.com
  0.60% |    1 |  0.60% |     7832 | dhc@dcrocker.net
  0.60% |    1 |  0.54% |     7019 | dwm@xpasc.com
  0.60% |    1 |  0.52% |     6823 | cabo@tzi.org
  0.60% |    1 |  0.52% |     6816 | rpelletier@isoc.org
  0.60% |    1 |  0.47% |     6089 | klaas@wierenga.net
  0.60% |    1 |  0.45% |     5838 | fgont@si6networks.com
  0.60% |    1 |  0.44% |     5798 | klensin@jck.com
  0.60% |    1 |  0.44% |     5796 | johannes.merkle@secunet.com
  0.60% |    1 |  0.42% |     5437 | john@jlc.net
--------+------+--------+----------+------------------------
100.00% |  166 |100.00% |  1304065 | Total


From narten@us.ibm.com  Fri Apr 19 04:07:14 2013
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 CCFB121F8E2C for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 04:07:14 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wQ+kpqa5v-vv for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 04:07:14 -0700 (PDT)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by ietfa.amsl.com (Postfix) with ESMTP id 40DB221F8D94 for <ietf@ietf.org>; Fri, 19 Apr 2013 04:07:14 -0700 (PDT)
Received: from /spool/local by e36.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>; Fri, 19 Apr 2013 05:07:13 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 19 Apr 2013 05:07:11 -0600
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id B868F3E40039 for <ietf@ietf.org>; Fri, 19 Apr 2013 05:06:57 -0600 (MDT)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r3JB7B2L374330 for <ietf@ietf.org>; Fri, 19 Apr 2013 05:07:11 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r3JB7A0E013957 for <ietf@ietf.org>; Fri, 19 Apr 2013 05:07:10 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-148-88.mts.ibm.com [9.65.148.88]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r3JB78kb013789 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 19 Apr 2013 05:07:10 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.6/8.12.5) with ESMTP id r3JB77eb015621 for <ietf@ietf.org>; Fri, 19 Apr 2013 07:07:07 -0400
Received: (from narten@localhost) by cichlid.raleigh.ibm.com (8.14.6/8.14.6/Submit) id r3JB77tV015555 for ietf@ietf.org; Fri, 19 Apr 2013 07:07:07 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201304191107.r3JB77tV015555@cichlid.raleigh.ibm.com>
Date: Fri, 19 Apr 2013 07:07:07 -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-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13041911-7606-0000-0000-00000A9E4920
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Apr 2013 11:07:14 -0000

Total of messages in the last 7 days.
 
script run at: Fri Apr 19 07:07:07 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
--------+------+--------+----------+------------------------


From abdussalambaryun@gmail.com  Fri Apr 19 04:21:58 2013
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 7E66D21F91BF for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 04:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZvg2EkBiqr2 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 04:21:57 -0700 (PDT)
Received: from mail-pa0-f42.google.com (mail-pa0-f42.google.com [209.85.220.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3ED3721F8FAC for <ietf@ietf.org>; Fri, 19 Apr 2013 04:21:57 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id kq13so2228651pab.1 for <ietf@ietf.org>; Fri, 19 Apr 2013 04:21:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dZnTa9Apuegl6bG84XrjvWaYsPxOI0c05FmIlqQu8N8=; b=v4KT73BBsjbaIh7MzJBlnMrr6ul3eZ73hGVHOCY5K43AO/49f0sifV/GIYQmvYjmW2 arQXn6EtXw6c2vv5+kW01G5YOEif80VQ32CGlBd5KVuGzHA8fYctUFG88zbysCNSACsd IL8p6jCYy0nzdwDH7UVXMeuGLjQ7Yr5nSFXq+RrtO3BtFsxHfkGQWfd9mvCNV6L+oDEc q0HOc1fZvohIurJmHuTSJaUn8SV3cUt2Dh+aSlZ2TtqTYs28x7gfJNB58bV96V1An/Iv y7ozKNwVVQ+qKrDKCW/W9O9VRk2BtNQ+DakwSYtW8y4ZkFa8awpLOTHMrenZEthM/KTb pynA==
MIME-Version: 1.0
X-Received: by 10.68.101.226 with SMTP id fj2mr19120275pbb.6.1366370516985; Fri, 19 Apr 2013 04:21:56 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Fri, 19 Apr 2013 04:21:56 -0700 (PDT)
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E72@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com> <465602F9-A251-475A-9BC3-1AD4DAB5E2E9@piuha.net> <CADnDZ8_5UqHGK_mGNzpqmrSCQnTf2WEu+QyBeeFrt3CXax=tQQ@mail.gmail.com> <290E20B455C66743BE178C5C84F12408223F494E72@EXMB01CMS.surrey.ac.uk>
Date: Fri, 19 Apr 2013 13:21:56 +0200
Message-ID: <CADnDZ8-6ga3BVye_eotpE4NsEF8shYLK3HrA-83yvGGMKzeACQ@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: l.wood@surrey.ac.uk
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: Fri, 19 Apr 2013 11:21:58 -0000

No name in the AD list appear so far, but if your the discuss-list is
right then it may be good progress, hoping for more names for
diversity. Your input not helping discussion,

AB

On 4/19/13, l.wood@surrey.ac.uk <l.wood@surrey.ac.uk> wrote:
>
> Female ADs include Allison Mankin, whose bio recently appeared on this list
> in relation to her new appointment.
>
> There's now a diversity discussion list, where this discussion should move
> to.
>
> http://www.ietf.org/blog/2013/04/diversity/
>
> Does what you think matter, when you clearly don't know anything?
>
> Lloyd Wood
> http://sat-net.com/L.Wood/
>
>
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Abdussalam
> Baryun [abdussalambaryun@gmail.com]
> Sent: 19 April 2013 10:37
> To: ajs@anvilwalrusden.com
> Cc: ietf
> Subject: Re: IETF Diversity Question on Berlin Registration?
>
> Andrew
>
>>Because some people report that they experience a chilly environment,
> and we respect those people for their other contributions and would
> like more people like them to contribute in similar ways, and
> therefore we want to make the environment less chilly.  I'm sort of
> surprised that that problem, which has been stated in my view quite
> plainly more than once in this thread, isn't evident to anyone
> participating.
>
> The environment may not be chilly, but may be unaware of experience
> (did we experience a woman as AD?). The IETF culture can be defined
> IMO as a argumental experience (firstly) plus technical (secondly),
> mostly men argue for long (may get unsensitive) but women may not
> fancy that. The participants' bias is not in technical experience it
> is in argumental, which is not true that all discussions on the IETF
> lists are technical, most of the time just men arguing and when they
> get lost in technical they get backed up with the consensus procedural
> argument.
>
>  I don't think women were given a chance to proof their ability to
> lead the IETF, so men can be aware of new experience.
>
> AB

From adrian@olddog.co.uk  Fri Apr 19 06:57:57 2013
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 F1D6521F95F6 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 06:57:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GEP8S2AB6Bsy for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 06:57:56 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 0B92921F9601 for <ietf@ietf.org>; Fri, 19 Apr 2013 06:57:55 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3JDvs4h027098 for <ietf@ietf.org>; Fri, 19 Apr 2013 14:57:54 +0100
Received: from 950129200 (50-76-52-225-ip-static.hfc.comcastbusiness.net [50.76.52.225]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3JDvow6027026 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 19 Apr 2013 14:57:52 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <CADnDZ8_D-HO+je+TXAYiTqu5kRC45V+HjQyifRuybHMrXiQm0A@mail.gmail.com>	<465602F9-A251-475A-9BC3-1AD4DAB5E2E9@piuha.net>	<CADnDZ8_5UqHGK_mGNzpqmrSCQnTf2WEu+QyBeeFrt3CXax=tQQ@mail.gmail.com>	<290E20B455C66743BE178C5C84F12408223F494E72@EXMB01CMS.surrey.ac.uk> <CADnDZ8-6ga3BVye_eotpE4NsEF8shYLK3HrA-83yvGGMKzeACQ@mail.gmail.com>
In-Reply-To: <CADnDZ8-6ga3BVye_eotpE4NsEF8shYLK3HrA-83yvGGMKzeACQ@mail.gmail.com>
Subject: RE: IETF Diversity Question on Berlin Registration?
Date: Fri, 19 Apr 2013 14:57:49 +0100
Message-ID: <031601ce3d05$e3109a50$a931cef0$@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: AQF19d2m7tVgKN/SHFfCHdBf6n/4CgI8bLyuATQYQQcB+o4mRgEjbiawmVmqaYA=
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: Fri, 19 Apr 2013 13:57:57 -0000

On 19 April 2013 at 12:22 Abdussalam Baryun <abdussalambaryun@gmail.com> wrote
on this list:

> No name in the AD list appear so far, but if your the discuss-list is
> right then it may be good progress, hoping for more names for
> diversity. 

I count three ADs on the diversity discussion list at the moment.  Why is my
count different from yours?

Adrian


From ted.ietf@gmail.com  Fri Apr 19 11:13:43 2013
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 74DF121F95F1 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 11:13:43 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C3po1C78RkMe for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 11:13:42 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 1E56421F8F00 for <ietf@ietf.org>; Fri, 19 Apr 2013 11:13:42 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id tp5so2518910ieb.40 for <ietf@ietf.org>; Fri, 19 Apr 2013 11:13:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=XalYxPdyagwn2JdgvpMCUDUWmeF1TRbXDaCs1yX/tS8=; b=K0LV1o5lllNAsca1UuzKy/LfRmLJFt+YFvg4DvXUC5lWKjGQqURQyxdehbnvEdYK9G TFL1F35U1oMX07ZylQ/bNPglvCRp391Be/8oREdIgMgxVN07IPBSBnolsHE1miPpcgx9 sLHgNcp9sy+XzqCCiY+qL1uvulHYyPfQ+QsDRrL48l7AHfWdV5UpT35xZyD5fyHAche0 aiZ3cBk05hR95648QvVuDEzkYbm7Pql/D7xMh6oBTOBOIBN14MCiyjC9PHli6v0wb9z5 Qv3otfbCTAKJk/+88gTWRHxaOxWcC3i2h7uxnhMGndreZr6fHeT9HMPS10VWj9jRq+z1 8JIA==
MIME-Version: 1.0
X-Received: by 10.50.170.102 with SMTP id al6mr2552042igc.20.1366395221635; Fri, 19 Apr 2013 11:13:41 -0700 (PDT)
Received: by 10.43.135.202 with HTTP; Fri, 19 Apr 2013 11:13:41 -0700 (PDT)
Date: Fri, 19 Apr 2013 11:13:41 -0700
Message-ID: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
Subject: Meritocracy, diversity, and leaning on the people you know
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8f3bb067cefa9b04dabaad69
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Apr 2013 18:13:43 -0000

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

Following a number of the threads on diversity and, in particular, on
whether the effort to get a better demographic view of participation will
lead to quotas, I have been increasingly uncomfortable with some of the
arguments which appear to have some presumptions about how diversity and
meritocracy relate.

To describe the issue, I'd like to start with a different situation and
then draw a parallel.  The different situation I'd like to use is a startup
company experiencing growth.  In my experience, startups that succeed tend
to have a very strong core group that comes together early on; they tackle
the hard work and develop a great degree of understanding of and trust in
each others' capabilities.  As the company grows, it's very common for that
core group to continue to rely on each other whenever a difficult problem
arrives.  That can manifest in those folks moving up to be the top of a
hierarchy and individually handling delegation; it can also manifest itself
in severe bottlenecks as the individuals remain critical resources to solve
an increasingly large number of problems.

In both cases, it's common for the individuals to pull in their own
networks of trusted folks as support.  Another way of expressing this is
that a particular human network is the basis of an enterprise, and the
scaling of that human network tends to work by each one of the humans
pulling in additional folks from their personal networks whose skills are
personally known to them.   The result of that is that the start-up *is* a
meritocracy as it grows (because the individuals are chosen based on their
abilities), but its diversity is initially limited to that of the personal
networks of those who end up in critical positions.  As the company grows
and recruiting becomes more formalized, the overall make-up may become more
diverse, but key positions may remain less diverse as the human networks
remain in place or are renewed.  Note that the scope of this diversity may
have nothing to do with race or gender, but may instead be about schools,
disciplines, or ages. (When it's schools, we even get to reuse the phrase "old
boy network"   <http://en.wikipedia.org/wiki/Old_boy_network>in its
original sense).

In the IETF, things are slightly different, in that attendance and
participation are completely open (there's no hiring gate), but many of the
same human networks are in play.  As a working group chair, when I stare
out at a sea of faces looking for a scribe, the chances of my asking
someone I know produces good minutes is much higher than my asking someone
whose work I don't know.  But that also translates into the pool of
candidates being *only those people I know*, because that's the only pool
whose merits I have assessed.  In other words, even though I'm selecting on
merit (good note takers), the way in which merit is determined (personal
knowledge) results in my not using the whole pool.

If there were an objective measure I could use instead, the WG's pool of
potential scribes would go up and the allocation likely would be fairer--if
I could say: "please tell me which potential minute taker (with a score of
70 or above) was tapped for the work least recently" and then tap that
individual, things get better for those who are otherwise tapped too
often.  Note again that the increased diversity in that pool may have
nothing to do with race or gender or even age, but it might instead be in
technical interest area (since I came from APPs into RAI, my background is
focused in certain areas).

The individual impact of my limited human networks may be small (I hope so,
anyway); in the best case, the limitations of mine would be overcome by the
scope of my co-chairs' and  ADs'.  But it can easily be a self-reinforcing
instead; if all the chairs come from the same backgrounds, they may know
and trust the same people.  Those people likely are being selected for
merit--but not from the total available pool.

As folks worry about quotas and its impact on quality, I think we must
recognize that the effort to promote based on merit alone is subject to the
limits by which merits are assessed.  The more human those are, the higher
the likelihood that network limitations or cognitive bias will have an
impact on our best use of the volunteers we have or could attack.

So, given this very human problem, what can we do?  Suresh and I happened
to be at a different SDO meeting yesterday, and we sat down briefly and
discussed this.  Two things emerged as possible concrete actions from that
brainstorming, but they both boil down to this:  institutionalize methods
for getting technical input from newcomers/less well-known participants, so
that technical input can be basis of assessments.  In other words, give
those outside the human networks an institutional method for being part of
the technical community. That should align with chairs' chronic need to
find technical energy to assess and complete work.

The first suggestion is a "Newcomer's directorate".  After an individual
starts participating in the IETF, either by attending a meeting or joining
a mailing list, offer them the opportunity to become part of a review
team.  That review team would have templates (as does AppsDir, the GenArt
team, and others) and example reviews to guide the new participant.  The
newcomers would be assigned last call reviews that would then be sent to
the relevant working group chairs and ADs for review.  Those who produced
good work would then be known to others relatively quickly.  At the end of
their "newcomer" period they might transition to a relevant directorate
based in an Area.

The second suggestion is a simple tool that at WG call time (be it last
call or call for adoption) randomly selects a set number of participants
from the mailing list, and then asks for a review or commentary.  So 5
folks off the mailing list are directly asked for their opinion, without
regard to preconceived notions of the chairs about who would be a good
reviewer.  If someone declines, the tool would select a new random person
to fill out.  The working group as a whole thus gets a chance to understand
someone's technical viewpoint, without that person having to fit within one
of the established human networks.

There are other methods that may well be better than the two Suresh and I
discussed, but I put these forward as a potentially concrete step that may
help those struggling with this to understand that the end result of this
need not be quotas.  It should be a better environment for all of our
volunteers.

best regards,

Ted Hardie

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

Following a number of the threads on diversity and, in particular, on wheth=
er the effort to get a better demographic view of participation will lead t=
o quotas, I have been increasingly uncomfortable with some of the arguments=
 which appear to have some presumptions about how diversity and meritocracy=
 relate.<br>
<br>To describe the issue, I&#39;d like to start with a different situation=
 and then draw a parallel.=A0 The different situation I&#39;d like to use i=
s a startup company experiencing growth.=A0 In my experience, startups that=
 succeed tend to have a very strong core group that comes together early on=
; they tackle the hard work and develop a great degree of understanding of =
and trust in each others&#39; capabilities.=A0 As the company grows, it&#39=
;s very common for that core group to continue to rely on each other whenev=
er a difficult problem arrives.=A0 That can manifest in those folks moving =
up to be the top of a hierarchy and individually handling delegation; it ca=
n also manifest itself in severe bottlenecks as the individuals remain crit=
ical resources to solve an increasingly large number of problems.=A0 <br>
<br>In both cases, it&#39;s common for the individuals to pull in their own=
 networks of trusted folks as support.=A0 Another way of expressing this is=
 that a particular human network is the basis of an enterprise, and the sca=
ling of that human network tends to work by each one of the humans pulling =
in additional folks from their personal networks whose skills are personall=
y known to them.=A0=A0 The result of that is that the start-up *is* a merit=
ocracy as it grows (because the individuals are chosen based on their abili=
ties), but its diversity is initially limited to that of the personal netwo=
rks of those who end up in critical positions.=A0 As the company grows and =
recruiting becomes more formalized, the overall make-up may become more div=
erse, but key positions may remain less diverse as the human networks remai=
n in place or are renewed.=A0 Note that the scope of this diversity may hav=
e nothing to do with race or gender, but may instead be about schools, disc=
iplines, or ages. (When it&#39;s schools, we even get to reuse the phrase <=
a href=3D"http://en.wikipedia.org/wiki/Old_boy_network">&quot;old boy netwo=
rk&quot;=A0=A0 </a>in its original sense).<br>
<br>In the IETF, things are slightly different, in that attendance and part=
icipation are completely open (there&#39;s no hiring gate), but many of the=
 same human networks are in play.=A0 As a working group chair, when I stare=
 out at a sea of faces looking for a scribe, the chances of my asking someo=
ne I know produces good minutes is much higher than my asking someone whose=
 work I don&#39;t know.=A0 But that also translates into the pool of candid=
ates being *only those people I know*, because that&#39;s the only pool who=
se merits I have assessed.=A0 In other words, even though I&#39;m selecting=
 on merit (good note takers),=20
the way in which merit is determined (personal knowledge) results in my=20
not using the whole pool. <br><br>If there were an objective measure I coul=
d use instead, the WG&#39;s pool of potential scribes would go up and the a=
llocation likely would be fairer--if I could say: &quot;please tell me whic=
h potential minute taker (with a score of 70 or above) was tapped for the w=
ork least recently&quot; and then tap that individual, things get better fo=
r those who are otherwise tapped too often.=A0 Note again that the increase=
d diversity in that pool may have nothing to do with race or gender or even=
 age, but it might instead be in technical interest area (since I came from=
 APPs into RAI, my background is focused in certain areas).=A0 <br>
<br>The individual impact of my limited human networks may be small (I hope=
 so, anyway); in the best case, the limitations of mine would be overcome b=
y the scope of my co-chairs&#39; and=A0 ADs&#39;.=A0 But it can easily be a=
 self-reinforcing instead; if all the chairs come from the same backgrounds=
, they may know and trust the same people.=A0 Those people likely are being=
 selected for merit--but not from the total available pool.<br>
<br>As folks worry about quotas and its impact on quality, I think we must =
recognize that the effort to promote based on merit alone is subject to the=
 limits by which merits are assessed.=A0 The more human those are, the high=
er the likelihood that network limitations or cognitive bias will have an i=
mpact on our best use of the volunteers we have or could attack. <br>
<br>So, given this very human problem, what can we do?=A0 Suresh and I happ=
ened to be at a different SDO meeting yesterday, and we sat down briefly an=
d discussed this.=A0 Two things emerged as possible concrete actions from t=
hat brainstorming, but they both boil down to this:=A0 institutionalize met=
hods for getting technical input from newcomers/less well-known participant=
s, so that technical input can be basis of assessments.=A0 In other words, =
give those outside the human networks an institutional method for being par=
t of the technical community. That should align with chairs&#39; chronic ne=
ed to find technical energy to assess and complete work.<br>
<br>The first suggestion is a &quot;Newcomer&#39;s directorate&quot;.=A0 Af=
ter an individual starts participating in the IETF, either by attending a m=
eeting or joining a mailing list, offer them the opportunity to become part=
 of a review team.=A0 That review team would have templates (as does AppsDi=
r, the GenArt team, and others) and example reviews to guide the new partic=
ipant.=A0 The newcomers would be assigned last call reviews that would then=
 be sent to the relevant working group chairs and ADs for review.=A0 Those =
who produced good work would then be known to others relatively quickly.=A0=
 At the end of their &quot;newcomer&quot; period they might transition to a=
 relevant directorate based in an Area.<br>
<br>The second suggestion is a simple tool that at WG call time (be it last=
 call or call for adoption) randomly selects a set number of participants f=
rom the mailing list, and then asks for a review or commentary.=A0 So 5 fol=
ks off the mailing list are directly asked for their opinion, without regar=
d to preconceived notions of the chairs about who would be a good reviewer.=
=A0 If someone declines, the tool would select a new random person to fill =
out.=A0 The working group as a whole thus gets a chance to understand someo=
ne&#39;s technical viewpoint, without that person having to fit within one =
of the established human networks.<br>
<br>There are other methods that may well be better than the two Suresh and=
 I discussed, but I put these forward as a potentially concrete step that m=
ay help those struggling with this to understand that the end result of thi=
s need not be quotas.=A0 It should be a better environment for all of our v=
olunteers.<br>
<br>best regards,<br><br>Ted Hardie<br>

--e89a8f3bb067cefa9b04dabaad69--

From framefritti@gmail.com  Fri Apr 19 11:26:32 2013
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 DD37A21F8630 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 11:26:32 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KpGud7LiC3iY for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 11:26:32 -0700 (PDT)
Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com [209.85.217.169]) by ietfa.amsl.com (Postfix) with ESMTP id 827DC21F8619 for <ietf@ietf.org>; Fri, 19 Apr 2013 11:26:31 -0700 (PDT)
Received: by mail-lb0-f169.google.com with SMTP id p11so4029768lbi.14 for <ietf@ietf.org>; Fri, 19 Apr 2013 11:26:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=Iokkq5n7GBA6teos/9D2UMRhfUjSt3o0RCncuu5J2ao=; b=wtq5RhVxwH05SSnCBhyo11WWnKduIe6+f5YlPq018VqTEsuVU81CCIR4BaLx2Iiv7U oXFOx0V/+vxh/0hXdP64jIpx6GZgJCpPjXZO9reBAQlYfln51aLq2Y9F6NOQbXARwTU2 W/rlo+bs7J8rMKv5uw/woQwbLj8698QkRSXjIlNLEi83Z1jbPWIamfFlmT1tAJH82XWe oy3p/54RLP3tQrtZxLDeXF75El7/ofvcvBWc48AEV6oYhgfV3WWrMnSL2pEggYPORNrt flVZO5QMWLTOcxetb/1yWEKcCicdniCWvQ6kS8Oi4oUoD9fbetCN/NrwRKXkTF4M0m1l cDSg==
MIME-Version: 1.0
X-Received: by 10.112.157.165 with SMTP id wn5mr8492556lbb.29.1366395990478; Fri, 19 Apr 2013 11:26:30 -0700 (PDT)
Received: by 10.112.9.5 with HTTP; Fri, 19 Apr 2013 11:26:30 -0700 (PDT)
In-Reply-To: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
Date: Fri, 19 Apr 2013 20:26:30 +0200
Message-ID: <CABSMSPVR+0-Diihvui6FZsq8DN+Wt=sHpR1woVttCijd1+QkRQ@mail.gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Riccardo Bernardini <framefritti@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, 19 Apr 2013 18:26:33 -0000

I like your analysis.  A comment while I am still "warm"

>
> The first suggestion is a "Newcomer's directorate".
>
> (snip)
>
> The second suggestion is a simple tool that at WG call time (be it last call
> or call for adoption) randomly selects a set number of participants from the
> mailing list, and then asks for a review or commentary.  So 5 folks off the
> mailing list are directly asked for their opinion, without regard to
> preconceived notions of the chairs about who would be a good reviewer.  If
> someone declines, the tool would select a new random person to fill out.
> The working group as a whole thus gets a chance to understand someone's
> technical viewpoint, without that person having to fit within one of the
> established human networks.

I like the second approach since it seems simpler to implement and it
does not involve a new human "structure."  Since we believe in running
code, we could try the second approach and see how it works.  We
should fix the setup in advance (duration, metrics, ...), but you
already know that. It seems to me that it would require just a handful
of line of codes and little more.

I would also suggest that with the second approach the selected
reviewer could have been given a chance to say "no," because sometime
you could not have the time to do that.  Of course, if someone says
"no" too often, that already is a hint... ;-)

Regards,

Riccardo

>
> There are other methods that may well be better than the two Suresh and I
> discussed, but I put these forward as a potentially concrete step that may
> help those struggling with this to understand that the end result of this
> need not be quotas.  It should be a better environment for all of our
> volunteers.
>
> best regards,
>
> Ted Hardie

From spromano@unina.it  Fri Apr 19 11:40:09 2013
Return-Path: <spromano@unina.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 44F3E21F910E for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 11:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.719
X-Spam-Level: 
X-Spam-Status: No, score=-100.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wgYwT3fNH16U for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 11:40:08 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id 02C3921F8FDD for <ietf@ietf.org>; Fri, 19 Apr 2013 11:40:07 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id r3JIcZjn025062 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 19 Apr 2013 20:38:36 +0200
Subject: Re: Meritocracy, diversity, and leaning on the people you know
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
Date: Fri, 19 Apr 2013 20:38:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B302FA6C-7C77-4BF6-B12A-438CAB6CF2BE@unina.it>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.1283)
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, 19 Apr 2013 18:40:09 -0000

Hi Ted,

interesting points indeed. I don't really know whether or not the =
approach you propose might work in practice, though.
My personal experience in the IETF is that it is really hard to gain =
some 'popularity' among the members of this variegated gallery of =
characters, especially if you don't have any official sponsorship from =
one of the big Internet companies. In case you were able to earn some =
credibility with a couple of on-the-field successes, you would not be =
treated as a newcomer anymore, but nonetheless as an outsider, a sort of =
strange entity wandering around meeting corridors and looked at with =
some curiosity by the usual gang of famous IETFfers. It is a matter of =
social attitudes. People are strange when you're a stranger...and there =
is really little you can do about that.

Cheers,

Simon


Il giorno 19/apr/2013, alle ore 20:13, Ted Hardie ha scritto:

> Following a number of the threads on diversity and, in particular, on =
whether the effort to get a better demographic view of participation =
will lead to quotas, I have been increasingly uncomfortable with some of =
the arguments which appear to have some presumptions about how diversity =
and meritocracy relate.
>=20
> To describe the issue, I'd like to start with a different situation =
and then draw a parallel.  The different situation I'd like to use is a =
startup company experiencing growth.  In my experience, startups that =
succeed tend to have a very strong core group that comes together early =
on; they tackle the hard work and develop a great degree of =
understanding of and trust in each others' capabilities.  As the company =
grows, it's very common for that core group to continue to rely on each =
other whenever a difficult problem arrives.  That can manifest in those =
folks moving up to be the top of a hierarchy and individually handling =
delegation; it can also manifest itself in severe bottlenecks as the =
individuals remain critical resources to solve an increasingly large =
number of problems. =20
>=20
> In both cases, it's common for the individuals to pull in their own =
networks of trusted folks as support.  Another way of expressing this is =
that a particular human network is the basis of an enterprise, and the =
scaling of that human network tends to work by each one of the humans =
pulling in additional folks from their personal networks whose skills =
are personally known to them.   The result of that is that the start-up =
*is* a meritocracy as it grows (because the individuals are chosen based =
on their abilities), but its diversity is initially limited to that of =
the personal networks of those who end up in critical positions.  As the =
company grows and recruiting becomes more formalized, the overall =
make-up may become more diverse, but key positions may remain less =
diverse as the human networks remain in place or are renewed.  Note that =
the scope of this diversity may have nothing to do with race or gender, =
but may instead be about schools, disciplines, or ages. (When it's =
schools, we even get to reuse the phrase "old boy network"   in its =
original sense).
>=20
> In the IETF, things are slightly different, in that attendance and =
participation are completely open (there's no hiring gate), but many of =
the same human networks are in play.  As a working group chair, when I =
stare out at a sea of faces looking for a scribe, the chances of my =
asking someone I know produces good minutes is much higher than my =
asking someone whose work I don't know.  But that also translates into =
the pool of candidates being *only those people I know*, because that's =
the only pool whose merits I have assessed.  In other words, even though =
I'm selecting on merit (good note takers), the way in which merit is =
determined (personal knowledge) results in my not using the whole pool.=20=

>=20
> If there were an objective measure I could use instead, the WG's pool =
of potential scribes would go up and the allocation likely would be =
fairer--if I could say: "please tell me which potential minute taker =
(with a score of 70 or above) was tapped for the work least recently" =
and then tap that individual, things get better for those who are =
otherwise tapped too often.  Note again that the increased diversity in =
that pool may have nothing to do with race or gender or even age, but it =
might instead be in technical interest area (since I came from APPs into =
RAI, my background is focused in certain areas). =20
>=20
> The individual impact of my limited human networks may be small (I =
hope so, anyway); in the best case, the limitations of mine would be =
overcome by the scope of my co-chairs' and  ADs'.  But it can easily be =
a self-reinforcing instead; if all the chairs come from the same =
backgrounds, they may know and trust the same people.  Those people =
likely are being selected for merit--but not from the total available =
pool.
>=20
> As folks worry about quotas and its impact on quality, I think we must =
recognize that the effort to promote based on merit alone is subject to =
the limits by which merits are assessed.  The more human those are, the =
higher the likelihood that network limitations or cognitive bias will =
have an impact on our best use of the volunteers we have or could =
attack.=20
>=20
> So, given this very human problem, what can we do?  Suresh and I =
happened to be at a different SDO meeting yesterday, and we sat down =
briefly and discussed this.  Two things emerged as possible concrete =
actions from that brainstorming, but they both boil down to this:  =
institutionalize methods for getting technical input from newcomers/less =
well-known participants, so that technical input can be basis of =
assessments.  In other words, give those outside the human networks an =
institutional method for being part of the technical community. That =
should align with chairs' chronic need to find technical energy to =
assess and complete work.
>=20
> The first suggestion is a "Newcomer's directorate".  After an =
individual starts participating in the IETF, either by attending a =
meeting or joining a mailing list, offer them the opportunity to become =
part of a review team.  That review team would have templates (as does =
AppsDir, the GenArt team, and others) and example reviews to guide the =
new participant.  The newcomers would be assigned last call reviews that =
would then be sent to the relevant working group chairs and ADs for =
review.  Those who produced good work would then be known to others =
relatively quickly.  At the end of their "newcomer" period they might =
transition to a relevant directorate based in an Area.
>=20
> The second suggestion is a simple tool that at WG call time (be it =
last call or call for adoption) randomly selects a set number of =
participants from the mailing list, and then asks for a review or =
commentary.  So 5 folks off the mailing list are directly asked for =
their opinion, without regard to preconceived notions of the chairs =
about who would be a good reviewer.  If someone declines, the tool would =
select a new random person to fill out.  The working group as a whole =
thus gets a chance to understand someone's technical viewpoint, without =
that person having to fit within one of the established human networks.
>=20
> There are other methods that may well be better than the two Suresh =
and I discussed, but I put these forward as a potentially concrete step =
that may help those struggling with this to understand that the end =
result of this need not be quotas.  It should be a better environment =
for all of our volunteers.
>=20
> best regards,
>=20
> Ted Hardie

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






From dave@cridland.net  Fri Apr 19 11:47:02 2013
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 18B7421F92F2 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 11:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WZy+TGxodGQX for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 11:47:01 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 41F2221F925B for <ietf@ietf.org>; Fri, 19 Apr 2013 11:47:01 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so3688677obq.17 for <ietf@ietf.org>; Fri, 19 Apr 2013 11:47:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=hoBarPwK1KS57dNWBsOd+jUCdjEHaTwWmimx2elsBV0=; b=U0TPmey2UaByNVsZ2mu0Z03LWKxT95f99X+9MZspboR8jW5Ex8eU9K1ExwMBZGcsNH XLmQ2NkwfNEQz+QWGRXctsrJfNhEFcJWbKJLAfArlbwSXbZRTii80r/QlKb/GXoS/1eE hgTCSpvd1mGPn7dMUz2TJdfz+4LOLG9zBaJ+g=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=hoBarPwK1KS57dNWBsOd+jUCdjEHaTwWmimx2elsBV0=; b=l9QZk0hbtJL52xALqExAdX7EXXtbqzJZc/+MWPRp6Lm8/vEMS3Y+4Rm/K3GW4muIdG y8ZCsjGttuFqjuyAsbde9PvGHvlHsyaT/Ih87QtzRNMjQBeEE3//BfkyqzfBq6Kn1Zn+ H38w65tkSeIHwyDAShC45lXI6hABNfzooXaJIWpVg5otAWeCQXBwp8DiqepTiXmfPQ7o w7Yfk/kTAm4bYq+EBr5khAh/S0TrMHMzdoajw1QCqc0dzpf+Pm8/XWxhCNqvJBJxpKs2 A+GGNzJc53ZxhhN3Ut2xnQNz3bujCnyuybYWUsfZuZ61GYR3XIUGZrbb5zvggUCJvOfy Jvhw==
MIME-Version: 1.0
X-Received: by 10.182.125.132 with SMTP id mq4mr9649928obb.79.1366397220811; Fri, 19 Apr 2013 11:47:00 -0700 (PDT)
Received: by 10.60.13.200 with HTTP; Fri, 19 Apr 2013 11:47:00 -0700 (PDT)
Received: by 10.60.13.200 with HTTP; Fri, 19 Apr 2013 11:47:00 -0700 (PDT)
In-Reply-To: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
Date: Fri, 19 Apr 2013 19:47:00 +0100
Message-ID: <CAKHUCzxGnZvZX8YtHzCoHb-Oi2MhaWNVP7Oy8+NAP6HrhuooMg@mail.gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Dave Cridland <dave@cridland.net>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=089e013a1edef80b3004dabb24db
X-Gm-Message-State: ALoCoQlVz2TmsTQlL8YIlxjun/V5XaLzKCdveF4OjyiCaiEvcdFBrnzR59TPG9xKopwiJpvlug+I
Cc: "ietf@ietf.org 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: Fri, 19 Apr 2013 18:47:02 -0000

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

Nice post.

I wonder whether a better mechanism for drawing newcomers into the inner
circle - which is what I think you're intent is here - would be to randomly
select people to be involved in a short online meeting to discuss the
draft, rather than review it in isolation.

It'd be a different kind of review, which adds value for us, I think, and
would instantiate new human subnets which could be used to bootstrap other
involvement.

This is, I stress, merely a quick reaction to your much more thoughtful
post, and I reserve the right to backtrack and change my mind.

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

<p dir=3D"ltr">Nice post.</p>
<p dir=3D"ltr">I wonder whether a better mechanism for drawing newcomers in=
to the inner circle - which is what I think you&#39;re intent is here - wou=
ld be to randomly select people to be involved in a short online meeting to=
 discuss the draft, rather than review it in isolation.</p>

<p dir=3D"ltr">It&#39;d be a different kind of review, which adds value for=
 us, I think, and would instantiate new human subnets which could be used t=
o bootstrap other involvement.</p>
<p dir=3D"ltr">This is, I stress, merely a quick reaction to your much more=
 thoughtful post, and I reserve the right to backtrack and change my mind.<=
/p>

--089e013a1edef80b3004dabb24db--

From framefritti@gmail.com  Fri Apr 19 12:14:09 2013
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 F393021F8F5C for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 12:14:08 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4uYJQPDH0vA9 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 12:14:08 -0700 (PDT)
Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) by ietfa.amsl.com (Postfix) with ESMTP id 253C821F8F4F for <ietf@ietf.org>; Fri, 19 Apr 2013 12:14:07 -0700 (PDT)
Received: by mail-lb0-f180.google.com with SMTP id t11so4035775lbi.39 for <ietf@ietf.org>; Fri, 19 Apr 2013 12:14:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=LCPhNX5+VG1v/AI/qLBMe1WYDj3gMenlNSQHzssVrGw=; b=ph9zxpFc/3znWZUJJShNaNZZZtpnpSV3Kbbj0URrKd8ikX9fxWImhv8Ea9YPXKUv0I AkNzkPrOq/f/ja6aYahU2npRPS2wf7+l4Ty/+Hx1vfErYCHn8Kkvz+2bi/QRdvsAXKs/ mm44tau3FlQgVCo5i/H+34B2UcJYQ94pO/3ktE1q0EzPVrWN5HougcHkVfRHxnAAdXEN JrqUfDrwq+7CX70H4Uz9fR6kSUfxnpH095SDm5+C868ne586O/JJZRLIvhuZn5GQxrYH ZuSSRd/BjHIHLnY0QY1zd5dIKK8Brmrty5vCFTFS5G9O3bjKj+Oslt7D4R0sWEeJnKUJ rtRg==
MIME-Version: 1.0
X-Received: by 10.152.1.194 with SMTP id 2mr8760399lao.17.1366398847116; Fri, 19 Apr 2013 12:14:07 -0700 (PDT)
Received: by 10.112.9.5 with HTTP; Fri, 19 Apr 2013 12:14:07 -0700 (PDT)
In-Reply-To: <CAKHUCzxGnZvZX8YtHzCoHb-Oi2MhaWNVP7Oy8+NAP6HrhuooMg@mail.gmail.com>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com> <CAKHUCzxGnZvZX8YtHzCoHb-Oi2MhaWNVP7Oy8+NAP6HrhuooMg@mail.gmail.com>
Date: Fri, 19 Apr 2013 21:14:07 +0200
Message-ID: <CABSMSPVTquav5qbKaiirvKZgfWbiC+PK2DNP3c9Uc4ObFr-xdg@mail.gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Riccardo Bernardini <framefritti@gmail.com>
To: "ietf@ietf.org 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: Fri, 19 Apr 2013 19:14:09 -0000

On Fri, Apr 19, 2013 at 8:47 PM, Dave Cridland <dave@cridland.net> wrote:
> Nice post.
>
> I wonder whether a better mechanism for drawing newcomers into the inner
> circle - which is what I think you're intent is here - would be to randomly
> select people to be involved in a short online meeting to discuss the draft,
> rather than review it in isolation.
>
> It'd be a different kind of review, which adds value for us, I think, and
> would instantiate new human subnets which could be used to bootstrap other
> involvement.
>
> This is, I stress, merely a quick reaction to your much more thoughtful
> post, and I reserve the right to backtrack and change my mind.

Another "quick reaction" or "warm comment:"

Yes, it is a different type of review and maybe not everyone is suited
for that type of interaction.  I speak by personal experience: during
meeting (especially with many people) usually I prefer to listen,
think about the issues and maybe expressing my ideas in a follow-up or
the at next meeting.  I know, I am not a team player (rather, I am a
lonely wolf :-) but it is me and I know that I am not the only one.
I  feel more comfortable in a less interactive setting: reading the
document, taking my time to ponder about it, hunting for holes, etc.
Then, maybe, I can be in a meeting where we express our opinion about
the doc.

Maybe we could have both types of "forced interaction," so you could
see who is more suited for "live meeting" and who for "non-interactive
review."

Riccardo

From ted.ietf@gmail.com  Fri Apr 19 12:29:02 2013
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 76C3421F84DF for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 12:29:02 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbzKmAkQskTn for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 12:29:01 -0700 (PDT)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id CB71F21F918C for <ietf@ietf.org>; Fri, 19 Apr 2013 12:29:00 -0700 (PDT)
Received: by mail-ie0-f171.google.com with SMTP id e11so5152297iej.30 for <ietf@ietf.org>; Fri, 19 Apr 2013 12:29:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=J8mDGMBKQsjyASRN/cd0Bwq3LR34W0HHtHbI+iy65z8=; b=YhWTeIV9IkR6ReZ9hR9e11AP77jIL4d9V8eHauyZJ4ja3dIC5v8hnlCR8tCudtSj5o DXTurRzSCA5pcBlaufnogxEBhk+eA8uvp7Agfv4YYkhTg+hBuEG6PnXwEoDhdjPviCp5 AolXLjqBdleTVHqBsIAuwJCC5o4dg+vQyojQWDfzOrxOcSwQf3gXiRCtlY/lcrKAxJ3r QsJBUIXgbyPO8aMS5kcvrgPgXxz8ELr4+TW6iEnksszBMja/+O/NlKhR+x789fkpFoWm 7JRMxfyLNGRzcCoigmEsZEamh/XNLZuiEidKCSm725tZ1/aqDvEzHQniZ0RN951eOnlr VVEQ==
MIME-Version: 1.0
X-Received: by 10.50.93.3 with SMTP id cq3mr2746350igb.70.1366399740383; Fri, 19 Apr 2013 12:29:00 -0700 (PDT)
Received: by 10.43.135.202 with HTTP; Fri, 19 Apr 2013 12:29:00 -0700 (PDT)
In-Reply-To: <B302FA6C-7C77-4BF6-B12A-438CAB6CF2BE@unina.it>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com> <B302FA6C-7C77-4BF6-B12A-438CAB6CF2BE@unina.it>
Date: Fri, 19 Apr 2013 12:29:00 -0700
Message-ID: <CA+9kkMD3suNCVpU2q-yjgpixXH4zJuqhH=roUzOZPCQT=m2sww@mail.gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Ted Hardie <ted.ietf@gmail.com>
To: Simon Pietro Romano <spromano@unina.it>
Content-Type: multipart/alternative; boundary=047d7b2e3e00259a9d04dabbbbb8
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, 19 Apr 2013 19:29:02 -0000

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

Hi Simon,

On Fri, Apr 19, 2013 at 11:38 AM, Simon Pietro Romano <spromano@unina.it>wr=
ote:

> Hi Ted,
>
> interesting points indeed. I don't really know whether or not the approac=
h
> you propose might work in practice,


There is certainly a risk there, but I hope we can find ways of increasing
the institutional support for opportunities for the less-well-connected
(newcomer or not) to contribute to the technical work. That may not result
immediately in deep social connection, but it should result in better
visibility.  That can help along the longer road.  There are, after all,
many chairs who are constantly looking for new participants and energy, and
adding this tool may help match that to the skills of volunteers they don't
know.

regards,

Ted Hardie




> though.
> My personal experience in the IETF is that it is really hard to gain some
> 'popularity' among the members of this variegated gallery of characters,
> especially if you don't have any official sponsorship from one of the big
> Internet companies. In case you were able to earn some credibility with a
> couple of on-the-field successes, you would not be treated as a newcomer
> anymore, but nonetheless as an outsider, a sort of strange entity wanderi=
ng
> around meeting corridors and looked at with some curiosity by the usual
> gang of famous IETFfers. It is a matter of social attitudes. People are
> strange when you're a stranger...and there is really little you can do
> about that.
>
> Cheers,
>
> Simon
>
>
> Il giorno 19/apr/2013, alle ore 20:13, Ted Hardie ha scritto:
>
> > Following a number of the threads on diversity and, in particular, on
> whether the effort to get a better demographic view of participation will
> lead to quotas, I have been increasingly uncomfortable with some of the
> arguments which appear to have some presumptions about how diversity and
> meritocracy relate.
> >
> > To describe the issue, I'd like to start with a different situation and
> then draw a parallel.  The different situation I'd like to use is a start=
up
> company experiencing growth.  In my experience, startups that succeed ten=
d
> to have a very strong core group that comes together early on; they tackl=
e
> the hard work and develop a great degree of understanding of and trust in
> each others' capabilities.  As the company grows, it's very common for th=
at
> core group to continue to rely on each other whenever a difficult problem
> arrives.  That can manifest in those folks moving up to be the top of a
> hierarchy and individually handling delegation; it can also manifest itse=
lf
> in severe bottlenecks as the individuals remain critical resources to sol=
ve
> an increasingly large number of problems.
> >
> > In both cases, it's common for the individuals to pull in their own
> networks of trusted folks as support.  Another way of expressing this is
> that a particular human network is the basis of an enterprise, and the
> scaling of that human network tends to work by each one of the humans
> pulling in additional folks from their personal networks whose skills are
> personally known to them.   The result of that is that the start-up *is* =
a
> meritocracy as it grows (because the individuals are chosen based on thei=
r
> abilities), but its diversity is initially limited to that of the persona=
l
> networks of those who end up in critical positions.  As the company grows
> and recruiting becomes more formalized, the overall make-up may become mo=
re
> diverse, but key positions may remain less diverse as the human networks
> remain in place or are renewed.  Note that the scope of this diversity ma=
y
> have nothing to do with race or gender, but may instead be about schools,
> disciplines, or ages. (When it's schools, we even get to reuse the phrase
> "old boy network"   in its original sense).
> >
> > In the IETF, things are slightly different, in that attendance and
> participation are completely open (there's no hiring gate), but many of t=
he
> same human networks are in play.  As a working group chair, when I stare
> out at a sea of faces looking for a scribe, the chances of my asking
> someone I know produces good minutes is much higher than my asking someon=
e
> whose work I don't know.  But that also translates into the pool of
> candidates being *only those people I know*, because that's the only pool
> whose merits I have assessed.  In other words, even though I'm selecting =
on
> merit (good note takers), the way in which merit is determined (personal
> knowledge) results in my not using the whole pool.
> >
> > If there were an objective measure I could use instead, the WG's pool o=
f
> potential scribes would go up and the allocation likely would be fairer--=
if
> I could say: "please tell me which potential minute taker (with a score o=
f
> 70 or above) was tapped for the work least recently" and then tap that
> individual, things get better for those who are otherwise tapped too ofte=
n.
>  Note again that the increased diversity in that pool may have nothing to
> do with race or gender or even age, but it might instead be in technical
> interest area (since I came from APPs into RAI, my background is focused =
in
> certain areas).
> >
> > The individual impact of my limited human networks may be small (I hope
> so, anyway); in the best case, the limitations of mine would be overcome =
by
> the scope of my co-chairs' and  ADs'.  But it can easily be a
> self-reinforcing instead; if all the chairs come from the same background=
s,
> they may know and trust the same people.  Those people likely are being
> selected for merit--but not from the total available pool.
> >
> > As folks worry about quotas and its impact on quality, I think we must
> recognize that the effort to promote based on merit alone is subject to t=
he
> limits by which merits are assessed.  The more human those are, the highe=
r
> the likelihood that network limitations or cognitive bias will have an
> impact on our best use of the volunteers we have or could attack.
> >
> > So, given this very human problem, what can we do?  Suresh and I
> happened to be at a different SDO meeting yesterday, and we sat down
> briefly and discussed this.  Two things emerged as possible concrete
> actions from that brainstorming, but they both boil down to this:
>  institutionalize methods for getting technical input from newcomers/less
> well-known participants, so that technical input can be basis of
> assessments.  In other words, give those outside the human networks an
> institutional method for being part of the technical community. That shou=
ld
> align with chairs' chronic need to find technical energy to assess and
> complete work.
> >
> > The first suggestion is a "Newcomer's directorate".  After an individua=
l
> starts participating in the IETF, either by attending a meeting or joinin=
g
> a mailing list, offer them the opportunity to become part of a review tea=
m.
>  That review team would have templates (as does AppsDir, the GenArt team,
> and others) and example reviews to guide the new participant.  The
> newcomers would be assigned last call reviews that would then be sent to
> the relevant working group chairs and ADs for review.  Those who produced
> good work would then be known to others relatively quickly.  At the end o=
f
> their "newcomer" period they might transition to a relevant directorate
> based in an Area.
> >
> > The second suggestion is a simple tool that at WG call time (be it last
> call or call for adoption) randomly selects a set number of participants
> from the mailing list, and then asks for a review or commentary.  So 5
> folks off the mailing list are directly asked for their opinion, without
> regard to preconceived notions of the chairs about who would be a good
> reviewer.  If someone declines, the tool would select a new random person
> to fill out.  The working group as a whole thus gets a chance to understa=
nd
> someone's technical viewpoint, without that person having to fit within o=
ne
> of the established human networks.
> >
> > There are other methods that may well be better than the two Suresh and
> I discussed, but I put these forward as a potentially concrete step that
> may help those struggling with this to understand that the end result of
> this need not be quotas.  It should be a better environment for all of ou=
r
> volunteers.
> >
> > best regards,
> >
> > Ted Hardie
>
>                                                                _\\|//_
>                                                               ( O-O )
>    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
>                                                 Simon Pietro Romano
>                                          Universita' di Napoli Federico I=
I
>                                      Computer Engineering Department
>                      Phone: +39 081 7683823 -- Fax: +39 081 7683816
>                                            e-mail: spromano@unina.it
>
>                     <<Molti mi dicono che lo scoraggiamento =CB l'alibi d=
egli
>                     idioti. Ci rifletto un istante; e mi scoraggio>>.
> Magritte.
>                                                      oooO
>   ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>                                                          \ (            (
>   )
>                                                           \_)          ) =
/
>                                                                        (_=
/
>
>
>
>
>
>

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

Hi Simon,<br><br><div class=3D"gmail_quote">On Fri, Apr 19, 2013 at 11:38 A=
M, Simon Pietro Romano <span dir=3D"ltr">&lt;<a href=3D"mailto:spromano@uni=
na.it" target=3D"_blank">spromano@unina.it</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
Hi Ted,<br>
<br>
interesting points indeed. I don&#39;t really know whether or not the appro=
ach you propose might work in practice, </blockquote><div><br>There is cert=
ainly a risk there, but I hope we can find ways of increasing the instituti=
onal support for opportunities for the less-well-connected (newcomer or not=
) to contribute to the technical work. That may not result immediately in d=
eep social connection, but it should result in better visibility.=A0 That c=
an help along the longer road.=A0 There are, after all, many chairs who are=
 constantly looking for new participants and energy, and adding this tool m=
ay help match that to the skills of volunteers they don&#39;t know.<br>
<br>regards,<br><br>Ted Hardie<br><br><br>=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">though.<br>
My personal experience in the IETF is that it is really hard to gain some &=
#39;popularity&#39; among the members of this variegated gallery of charact=
ers, especially if you don&#39;t have any official sponsorship from one of =
the big Internet companies. In case you were able to earn some credibility =
with a couple of on-the-field successes, you would not be treated as a newc=
omer anymore, but nonetheless as an outsider, a sort of strange entity wand=
ering around meeting corridors and looked at with some curiosity by the usu=
al gang of famous IETFfers. It is a matter of social attitudes. People are =
strange when you&#39;re a stranger...and there is really little you can do =
about that.<br>

<br>
Cheers,<br>
<br>
Simon<br>
<br>
<br>
Il giorno 19/apr/2013, alle ore 20:13, Ted Hardie ha scritto:<br>
<div><div class=3D"h5"><br>
&gt; Following a number of the threads on diversity and, in particular, on =
whether the effort to get a better demographic view of participation will l=
ead to quotas, I have been increasingly uncomfortable with some of the argu=
ments which appear to have some presumptions about how diversity and merito=
cracy relate.<br>

&gt;<br>
&gt; To describe the issue, I&#39;d like to start with a different situatio=
n and then draw a parallel. =A0The different situation I&#39;d like to use =
is a startup company experiencing growth. =A0In my experience, startups tha=
t succeed tend to have a very strong core group that comes together early o=
n; they tackle the hard work and develop a great degree of understanding of=
 and trust in each others&#39; capabilities. =A0As the company grows, it&#3=
9;s very common for that core group to continue to rely on each other whene=
ver a difficult problem arrives. =A0That can manifest in those folks moving=
 up to be the top of a hierarchy and individually handling delegation; it c=
an also manifest itself in severe bottlenecks as the individuals remain cri=
tical resources to solve an increasingly large number of problems.<br>

&gt;<br>
&gt; In both cases, it&#39;s common for the individuals to pull in their ow=
n networks of trusted folks as support. =A0Another way of expressing this i=
s that a particular human network is the basis of an enterprise, and the sc=
aling of that human network tends to work by each one of the humans pulling=
 in additional folks from their personal networks whose skills are personal=
ly known to them. =A0 The result of that is that the start-up *is* a merito=
cracy as it grows (because the individuals are chosen based on their abilit=
ies), but its diversity is initially limited to that of the personal networ=
ks of those who end up in critical positions. =A0As the company grows and r=
ecruiting becomes more formalized, the overall make-up may become more dive=
rse, but key positions may remain less diverse as the human networks remain=
 in place or are renewed. =A0Note that the scope of this diversity may have=
 nothing to do with race or gender, but may instead be about schools, disci=
plines, or ages. (When it&#39;s schools, we even get to reuse the phrase &q=
uot;old boy network&quot; =A0 in its original sense).<br>

&gt;<br>
&gt; In the IETF, things are slightly different, in that attendance and par=
ticipation are completely open (there&#39;s no hiring gate), but many of th=
e same human networks are in play. =A0As a working group chair, when I star=
e out at a sea of faces looking for a scribe, the chances of my asking some=
one I know produces good minutes is much higher than my asking someone whos=
e work I don&#39;t know. =A0But that also translates into the pool of candi=
dates being *only those people I know*, because that&#39;s the only pool wh=
ose merits I have assessed. =A0In other words, even though I&#39;m selectin=
g on merit (good note takers), the way in which merit is determined (person=
al knowledge) results in my not using the whole pool.<br>

&gt;<br>
&gt; If there were an objective measure I could use instead, the WG&#39;s p=
ool of potential scribes would go up and the allocation likely would be fai=
rer--if I could say: &quot;please tell me which potential minute taker (wit=
h a score of 70 or above) was tapped for the work least recently&quot; and =
then tap that individual, things get better for those who are otherwise tap=
ped too often. =A0Note again that the increased diversity in that pool may =
have nothing to do with race or gender or even age, but it might instead be=
 in technical interest area (since I came from APPs into RAI, my background=
 is focused in certain areas).<br>

&gt;<br>
&gt; The individual impact of my limited human networks may be small (I hop=
e so, anyway); in the best case, the limitations of mine would be overcome =
by the scope of my co-chairs&#39; and =A0ADs&#39;. =A0But it can easily be =
a self-reinforcing instead; if all the chairs come from the same background=
s, they may know and trust the same people. =A0Those people likely are bein=
g selected for merit--but not from the total available pool.<br>

&gt;<br>
&gt; As folks worry about quotas and its impact on quality, I think we must=
 recognize that the effort to promote based on merit alone is subject to th=
e limits by which merits are assessed. =A0The more human those are, the hig=
her the likelihood that network limitations or cognitive bias will have an =
impact on our best use of the volunteers we have or could attack.<br>

&gt;<br>
&gt; So, given this very human problem, what can we do? =A0Suresh and I hap=
pened to be at a different SDO meeting yesterday, and we sat down briefly a=
nd discussed this. =A0Two things emerged as possible concrete actions from =
that brainstorming, but they both boil down to this: =A0institutionalize me=
thods for getting technical input from newcomers/less well-known participan=
ts, so that technical input can be basis of assessments. =A0In other words,=
 give those outside the human networks an institutional method for being pa=
rt of the technical community. That should align with chairs&#39; chronic n=
eed to find technical energy to assess and complete work.<br>

&gt;<br>
&gt; The first suggestion is a &quot;Newcomer&#39;s directorate&quot;. =A0A=
fter an individual starts participating in the IETF, either by attending a =
meeting or joining a mailing list, offer them the opportunity to become par=
t of a review team. =A0That review team would have templates (as does AppsD=
ir, the GenArt team, and others) and example reviews to guide the new parti=
cipant. =A0The newcomers would be assigned last call reviews that would the=
n be sent to the relevant working group chairs and ADs for review. =A0Those=
 who produced good work would then be known to others relatively quickly. =
=A0At the end of their &quot;newcomer&quot; period they might transition to=
 a relevant directorate based in an Area.<br>

&gt;<br>
&gt; The second suggestion is a simple tool that at WG call time (be it las=
t call or call for adoption) randomly selects a set number of participants =
from the mailing list, and then asks for a review or commentary. =A0So 5 fo=
lks off the mailing list are directly asked for their opinion, without rega=
rd to preconceived notions of the chairs about who would be a good reviewer=
. =A0If someone declines, the tool would select a new random person to fill=
 out. =A0The working group as a whole thus gets a chance to understand some=
one&#39;s technical viewpoint, without that person having to fit within one=
 of the established human networks.<br>

&gt;<br>
&gt; There are other methods that may well be better than the two Suresh an=
d I discussed, but I put these forward as a potentially concrete step that =
may help those struggling with this to understand that the end result of th=
is need not be quotas. =A0It should be a better environment for all of our =
volunteers.<br>

&gt;<br>
&gt; best regards,<br>
&gt;<br>
&gt; Ted Hardie<br>
<br>
</div></div>=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0_\\|//_<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ( O-O )<br>
=A0 =A0~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 Simon Pietro Romano<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0Universita&#39; di Napoli Federico II<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
Computer Engineering Department<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Phone: <a href=3D"tel:%2B39%2008=
1%207683823" value=3D"+390817683823">+39 081 7683823</a> -- Fax: <a href=3D=
"tel:%2B39%20081%207683816" value=3D"+390817683816">+39 081 7683816</a><br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0e-mail: <a href=3D"mailto:spromano@unina.it">spromano@unina.it<=
/a><br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 &lt;&lt;Molti mi dicono che lo scor=
aggiamento =CB l&#39;alibi degli<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 idioti. Ci rifletto un istante; e m=
i scoraggio&gt;&gt;. Magritte.<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0oooO<br>
=A0 ~~~~~~~~~~~~~~~~~~~~~~~( =A0 )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0\ ( =A0 =A0 =A0 =A0 =A0 =A0( =A0 )<=
br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 \_) =A0 =A0 =A0 =A0 =A0) /<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(_/<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br>

--047d7b2e3e00259a9d04dabbbbb8--

From ted.ietf@gmail.com  Fri Apr 19 12:31:30 2013
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 5749F21F9193 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 12:31:30 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id txhj4nEGksWR for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 12:31:29 -0700 (PDT)
Received: from mail-ia0-x22a.google.com (mail-ia0-x22a.google.com [IPv6:2607:f8b0:4001:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BD35921F86D3 for <ietf@ietf.org>; Fri, 19 Apr 2013 12:31:29 -0700 (PDT)
Received: by mail-ia0-f170.google.com with SMTP id 21so3567450iay.1 for <ietf@ietf.org>; Fri, 19 Apr 2013 12:31:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=p1CxZdWLhNmbN8qRsLX359MmpKVxRNCBYTAq9hL/ZWA=; b=Ktodg8vHlOmuNXXnO8N1P1mhIcj6V8Ule2h25HVDCqgnJDModKv4Ar/VztITA/ACfj MkOjfnQTuJXISHBgALIfBpYJCc4D3WSoM8tbtYz1ybDieUaXfracJkr699CX+kWcYOQE TWeLskwWxofTFmA2L+yoKY738s8jbrnISjIOHxWyRnULSbh8iP89SM6eMJfp63L25Fcf dZMDyz3UhZbdnt5Rrem45Q5vd0iKP0aHc0f1zSWx5VZa9qMVlNe+PK8nqKuVJBta/4af oZoyK3mygwlwrDD0i2xsrY1aQ8A2inZwAPVbitqYVlfKUaTczu+4E0fFxvcaKhKet7QV MJbQ==
MIME-Version: 1.0
X-Received: by 10.50.87.71 with SMTP id v7mr10179137igz.96.1366399889293; Fri, 19 Apr 2013 12:31:29 -0700 (PDT)
Received: by 10.43.135.202 with HTTP; Fri, 19 Apr 2013 12:31:29 -0700 (PDT)
In-Reply-To: <CAKHUCzxGnZvZX8YtHzCoHb-Oi2MhaWNVP7Oy8+NAP6HrhuooMg@mail.gmail.com>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com> <CAKHUCzxGnZvZX8YtHzCoHb-Oi2MhaWNVP7Oy8+NAP6HrhuooMg@mail.gmail.com>
Date: Fri, 19 Apr 2013 12:31:29 -0700
Message-ID: <CA+9kkMCNm4rhVwnRkeMDJ3amx6m4HGqr+b3fHNy=L88QC5QdiA@mail.gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Ted Hardie <ted.ietf@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=089e0103ef5205c7c204dabbc471
Cc: "ietf@ietf.org 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: Fri, 19 Apr 2013 19:31:30 -0000

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

On Fri, Apr 19, 2013 at 11:47 AM, Dave Cridland <dave@cridland.net> wrote:

> Nice post.
>
> I wonder whether a better mechanism for drawing newcomers into the inner
> circle - which is what I think you're intent is here - would be to randomly
> select people to be involved in a short online meeting to discuss the
> draft, rather than review it in isolation.
>
> It'd be a different kind of review, which adds value for us, I think, and
> would instantiate new human subnets which could be used to bootstrap other
> involvement.
>
> I think that would be a useful additional approach (maybe have those
randomly selected meet online before starting the reviews).  I do want to
be sensitive, though, to the language barriers to some extent.  I used to
recommend that folks interested in participating in a working group start
by being a scribe; I realized eventually how hard that was for some
participants whose native language was not English.  It's still useful for
those for whom real-time capture of rapidly moving discussion is feasible,
but we need something that allows folks time to reflect as well.

Just my 2 cents,

regards,

TEd




> This is, I stress, merely a quick reaction to your much more thoughtful
> post, and I reserve the right to backtrack and change my mind.
>

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

On Fri, Apr 19, 2013 at 11:47 AM, Dave Cridland <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt;=
</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<p dir=3D"ltr">Nice post.</p>
<p dir=3D"ltr">I wonder whether a better mechanism for drawing newcomers in=
to the inner circle - which is what I think you&#39;re intent is here - wou=
ld be to randomly select people to be involved in a short online meeting to=
 discuss the draft, rather than review it in isolation.</p>


<p dir=3D"ltr">It&#39;d be a different kind of review, which adds value for=
 us, I think, and would instantiate new human subnets which could be used t=
o bootstrap other involvement.</p>
<p dir=3D"ltr"></p></blockquote><div>I think that would be a useful additio=
nal approach (maybe have those randomly selected meet online before startin=
g the reviews).=A0 I do want to be sensitive, though, to the language barri=
ers to some extent.=A0 I used to recommend that folks interested in partici=
pating in a working group start by being a scribe; I realized eventually ho=
w hard that was for some participants whose native language was not English=
.=A0 It&#39;s still useful for those for whom real-time capture of rapidly =
moving discussion is feasible, but we need something that allows folks time=
 to reflect as well.<br>
<br>Just my 2 cents,<br><br>regards,<br><br>TEd<br><br><br>=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><p dir=3D"ltr">This is, I stress, merely a quick re=
action to your much more thoughtful post, and I reserve the right to backtr=
ack and change my mind.</p>

</blockquote></div><br>

--089e0103ef5205c7c204dabbc471--

From ted.ietf@gmail.com  Fri Apr 19 12:33:07 2013
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 8781921F9227 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 12:33:07 -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=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jrs7CWEbNXfn for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 12:32:55 -0700 (PDT)
Received: from mail-ia0-x22e.google.com (mail-ia0-x22e.google.com [IPv6:2607:f8b0:4001:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 900AE21F86D3 for <ietf@ietf.org>; Fri, 19 Apr 2013 12:32:55 -0700 (PDT)
Received: by mail-ia0-f174.google.com with SMTP id m10so1797750iam.33 for <ietf@ietf.org>; Fri, 19 Apr 2013 12:32:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ZMiabBMdRkbv6UJ7aYKj+Vk76aa3HL0lY9Jtq85NtFE=; b=OVPGW+R/tVBGozKRHGabxnkGYrxVpOrjRA8tq0h22kiDFG3Q6yxEmA5x5Yu6Uz6rGP 8iXFvsfAiXHWUIZYWipU/gpM+UdL6KhZg0lhD5WPscos5DYIuYVXhmRglKfp/kdtsr/6 wL5qKWR2mUY2KVbXT5krSYzz8OR1y/LW5WodcT29NX3kFb4+JXhL3Be+NBsdmcENZpHw s65f4uphYvf8M62r8K+RxTfZC5z9V2ZyaNulDYqpYvjtYvsB7KzT8DEkjpplZz5RmEXF j0SFhPrvwo2jiCBpr03GKNiNg8lpBvCXtlFOezjtOdKrDwsqFy8bgp/MuJPOj2nczJoq GBew==
MIME-Version: 1.0
X-Received: by 10.50.36.169 with SMTP id r9mr2668831igj.96.1366399975163; Fri, 19 Apr 2013 12:32:55 -0700 (PDT)
Received: by 10.43.135.202 with HTTP; Fri, 19 Apr 2013 12:32:55 -0700 (PDT)
In-Reply-To: <CABSMSPVR+0-Diihvui6FZsq8DN+Wt=sHpR1woVttCijd1+QkRQ@mail.gmail.com>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com> <CABSMSPVR+0-Diihvui6FZsq8DN+Wt=sHpR1woVttCijd1+QkRQ@mail.gmail.com>
Date: Fri, 19 Apr 2013 12:32:55 -0700
Message-ID: <CA+9kkMD-zYVzwyfzhtGS4J6_LvDdHuMfmEGr3ymv_p59Ts-iDg@mail.gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Ted Hardie <ted.ietf@gmail.com>
To: Riccardo Bernardini <framefritti@gmail.com>
Content-Type: multipart/alternative; boundary=14dae934032b240cf204dabbc9cf
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, 19 Apr 2013 19:33:08 -0000

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

On Fri, Apr 19, 2013 at 11:26 AM, Riccardo Bernardini
<framefritti@gmail.com> wrote:

> I like your analysis.  A comment while I am still "warm"
>
> >
> > The first suggestion is a "Newcomer's directorate".
> >
> > (snip)
> >
> > The second suggestion is a simple tool that at WG call time (be it last
> call
> > or call for adoption) randomly selects a set number of participants from
> the
> > mailing list, and then asks for a review or commentary.  So 5 folks off
> the
> > mailing list are directly asked for their opinion, without regard to
> > preconceived notions of the chairs about who would be a good reviewer.
>  If
> > someone declines, the tool would select a new random person to fill out.
> > The working group as a whole thus gets a chance to understand someone's
> > technical viewpoint, without that person having to fit within one of the
> > established human networks.
>
> I like the second approach since it seems simpler to implement and it
> does not involve a new human "structure."  Since we believe in running
> code, we could try the second approach and see how it works.  We
> should fix the setup in advance (duration, metrics, ...), but you
> already know that. It seems to me that it would require just a handful
> of line of codes and little more.
>
>
I believe Suresh is going to propose working on it at the next code sprint,
if there is enough support.  If you are interested in contributing to that,
I'm sure he'd welcome it.

regards,

Ted Hardie



> I would also suggest that with the second approach the selected
> reviewer could have been given a chance to say "no," because sometime
> you could not have the time to do that.  Of course, if someone says
> "no" too often, that already is a hint... ;-)
>
> Regards,
>
> Riccardo
>
> >
> > There are other methods that may well be better than the two Suresh and I
> > discussed, but I put these forward as a potentially concrete step that
> may
> > help those struggling with this to understand that the end result of this
> > need not be quotas.  It should be a better environment for all of our
> > volunteers.
> >
> > best regards,
> >
> > Ted Hardie
>

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

<br><br><div class=3D"gmail_quote">On Fri, Apr 19, 2013 at 11:26 AM, Riccar=
do Bernardini<br><span dir=3D"ltr">&lt;<a href=3D"mailto:framefritti@gmail.=
com" target=3D"_blank">framefritti@gmail.com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
I like your analysis. =A0A comment while I am still &quot;warm&quot;<br>
<div class=3D"im"><br>
&gt;<br>
&gt; The first suggestion is a &quot;Newcomer&#39;s directorate&quot;.<br>
&gt;<br>
</div>&gt; (snip)<br>
<div class=3D"im">&gt;<br>
&gt; The second suggestion is a simple tool that at WG call time (be it las=
t call<br>
&gt; or call for adoption) randomly selects a set number of participants fr=
om the<br>
&gt; mailing list, and then asks for a review or commentary. =A0So 5 folks =
off the<br>
&gt; mailing list are directly asked for their opinion, without regard to<b=
r>
&gt; preconceived notions of the chairs about who would be a good reviewer.=
 =A0If<br>
&gt; someone declines, the tool would select a new random person to fill ou=
t.<br>
&gt; The working group as a whole thus gets a chance to understand someone&=
#39;s<br>
&gt; technical viewpoint, without that person having to fit within one of t=
he<br>
&gt; established human networks.<br>
<br>
</div>I like the second approach since it seems simpler to implement and it=
<br>
does not involve a new human &quot;structure.&quot; =A0Since we believe in =
running<br>
code, we could try the second approach and see how it works. =A0We<br>
should fix the setup in advance (duration, metrics, ...), but you<br>
already know that. It seems to me that it would require just a handful<br>
of line of codes and little more.<br>
<br></blockquote><div><br>I believe Suresh is going to propose working on i=
t at the next code sprint, if there is enough support.=A0 If you are intere=
sted in contributing to that, I&#39;m sure he&#39;d welcome it.<br><br>rega=
rds,<br>
<br>Ted Hardie<br><br>=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would also suggest that with the second approach the selected<br>
reviewer could have been given a chance to say &quot;no,&quot; because some=
time<br>
you could not have the time to do that. =A0Of course, if someone says<br>
&quot;no&quot; too often, that already is a hint... ;-)<br>
<br>
Regards,<br>
<br>
Riccardo<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt;<br>
&gt; There are other methods that may well be better than the two Suresh an=
d I<br>
&gt; discussed, but I put these forward as a potentially concrete step that=
 may<br>
&gt; help those struggling with this to understand that the end result of t=
his<br>
&gt; need not be quotas. =A0It should be a better environment for all of ou=
r<br>
&gt; volunteers.<br>
&gt;<br>
&gt; best regards,<br>
&gt;<br>
&gt; Ted Hardie<br>
</div></div></blockquote></div><br>

--14dae934032b240cf204dabbc9cf--

From ynir@checkpoint.com  Fri Apr 19 13:31:14 2013
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 607DB21F8EC7 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 13:31:14 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HHXB5RsN5Iv3 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 13:31:13 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 21D3121F8EC6 for <ietf@ietf.org>; Fri, 19 Apr 2013 13:31:12 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r3JKV0r3030354; Fri, 19 Apr 2013 23:31:00 +0300
X-CheckPoint: {5171A8DD-1-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Fri, 19 Apr 2013 23:30:59 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
Thread-Topic: Meritocracy, diversity, and leaning on the people you know
Thread-Index: AQHOPSmw21pLX9AYm0aoJdi8RyqSu5jdr+4AgAAMboCAABCggA==
Date: Fri, 19 Apr 2013 20:30:58 +0000
Message-ID: <3408046C-FCF3-4F61-9300-B7C9A99D2581@checkpoint.com>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com> <CAKHUCzxGnZvZX8YtHzCoHb-Oi2MhaWNVP7Oy8+NAP6HrhuooMg@mail.gmail.com> <CA+9kkMCNm4rhVwnRkeMDJ3amx6m4HGqr+b3fHNy=L88QC5QdiA@mail.gmail.com>
In-Reply-To: <CA+9kkMCNm4rhVwnRkeMDJ3amx6m4HGqr+b3fHNy=L88QC5QdiA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.242]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: multipart/alternative; boundary="_000_3408046CFCF34F619300B7C9A99D2581checkpointcom_"
MIME-Version: 1.0
Cc: "ietf@ietf.org 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: Fri, 19 Apr 2013 20:31:14 -0000

--_000_3408046CFCF34F619300B7C9A99D2581checkpointcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


On Apr 19, 2013, at 10:31 PM, Ted Hardie <ted.ietf@gmail.com<mailto:ted.iet=
f@gmail.com>>
 wrote:

On Fri, Apr 19, 2013 at 11:47 AM, Dave Cridland <dave@cridland.net<mailto:d=
ave@cridland.net>> wrote:

Nice post.

I wonder whether a better mechanism for drawing newcomers into the inner ci=
rcle - which is what I think you're intent is here - would be to randomly s=
elect people to be involved in a short online meeting to discuss the draft,=
 rather than review it in isolation.

It'd be a different kind of review, which adds value for us, I think, and w=
ould instantiate new human subnets which could be used to bootstrap other i=
nvolvement.

I think that would be a useful additional approach (maybe have those random=
ly selected meet online before starting the reviews).  I do want to be sens=
itive, though, to the language barriers to some extent.  I used to recommen=
d that folks interested in participating in a working group start by being =
a scribe; I realized eventually how hard that was for some participants who=
se native language was not English.  It's still useful for those for whom r=
eal-time capture of rapidly moving discussion is feasible, but we need some=
thing that allows folks time to reflect as well.


I tried that a while back. I found that it's really hard for a newbie to sc=
ribe. First, you have people running to the mike, and no idea who they are.=
 I tried to position myself just in front of the mike so I could see the na=
me tags, but that worked less than half of the times (there was another mik=
e at the back). People saying their names helps very little, because it's v=
ery hard to catch even for English speakers. Add some different accent, and=
 it becomes hopeless.

As chair, I try to pick the ones I know are familiar with those likely to c=
ome to the mike. Otherwise you end up with notes saying things like "someon=
e at the mic says =85"

Yoav


--_000_3408046CFCF34F619300B7C9A99D2581checkpointcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <AC3514CED06B304A8D2ED0B58C26376A@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<br>
<div>
<div>On Apr 19, 2013, at 10:31 PM, Ted Hardie &lt;<a href=3D"mailto:ted.iet=
f@gmail.com">ted.ietf@gmail.com</a>&gt;</div>
<div>&nbsp;wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">On Fri, Apr 19, 2013 at 11:47 AM, Dave Cridland <=
span dir=3D"ltr">
&lt;<a href=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cridland.ne=
t</a>&gt;</span> wrote:<br>
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<p dir=3D"ltr">Nice post.</p>
<p dir=3D"ltr">I wonder whether a better mechanism for drawing newcomers in=
to the inner circle - which is what I think you're intent is here - would b=
e to randomly select people to be involved in a short online meeting to dis=
cuss the draft, rather than review
 it in isolation.</p>
<p dir=3D"ltr">It'd be a different kind of review, which adds value for us,=
 I think, and would instantiate new human subnets which could be used to bo=
otstrap other involvement.</p>
<div><br class=3D"webkit-block-placeholder">
</div>
</blockquote>
<div>I think that would be a useful additional approach (maybe have those r=
andomly selected meet online before starting the reviews).&nbsp; I do want =
to be sensitive, though, to the language barriers to some extent.&nbsp; I u=
sed to recommend that folks interested in
 participating in a working group start by being a scribe; I realized event=
ually how hard that was for some participants whose native language was not=
 English.&nbsp; It's still useful for those for whom real-time capture of r=
apidly moving discussion is feasible,
 but we need something that allows folks time to reflect as well.<br>
<br>
</div>
</div>
</blockquote>
<br>
</div>
<div>I tried that a while back. I found that it's really hard for a newbie =
to scribe. First, you have people running to the mike, and no idea who they=
 are. I tried to position myself just in front of the mike so I could see t=
he name tags, but that worked less
 than half of the times (there was another mike at the back). People saying=
 their names helps very little, because it's very hard to catch even for En=
glish speakers. Add some different accent, and it becomes hopeless.</div>
<div><br>
</div>
<div>As chair, I try to pick the ones I know are familiar with those likely=
 to come to the mike. Otherwise you end up with notes saying things like &q=
uot;someone at the mic says =85&quot;</div>
<div><br>
</div>
<div>Yoav</div>
<br>
</body>
</html>

--_000_3408046CFCF34F619300B7C9A99D2581checkpointcom_--

From jari.arkko@piuha.net  Fri Apr 19 13:33:00 2013
Return-Path: <jari.arkko@piuha.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 5E0B921F8ECA for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 13:33:00 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gjLF97zLO2JT for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2013 13:32:59 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id BB7E421F8EC6 for <ietf@ietf.org>; Fri, 19 Apr 2013 13:32:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 982F92CC50; Fri, 19 Apr 2013 23:32:53 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LWKY19mShQtP; Fri, 19 Apr 2013 23:32:53 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 2F0962CC3C; Fri, 19 Apr 2013 23:32:53 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
Date: Fri, 19 Apr 2013 23:32:53 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <96E29AE1-5FF3-413E-9A5A-B7B0622A2A3E@piuha.net>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
X-Mailer: Apple Mail (2.1503)
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, 19 Apr 2013 20:33:00 -0000

Ted: Very nice post and good ideas. Thanks.

Jari


From ben@nostrum.com  Fri Apr 19 13:51:26 2013
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 9ABE121F8D28; Fri, 19 Apr 2013 13:51:26 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MBwvi9CPW1vl; Fri, 19 Apr 2013 13:51:26 -0700 (PDT)
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 EE24E21F89B0; Fri, 19 Apr 2013 13:51:25 -0700 (PDT)
Received: from [172.20.10.2] (mobile-166-147-077-136.mycingular.net [166.147.77.136]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3JKpN8v086763 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 19 Apr 2013 15:51:24 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Gen-ART Telechat Review of draft-ietf-ospf-ipv4-embedded-ipv6-routing-11 
From: Ben Campbell <ben@nostrum.com>
Date: Fri, 19 Apr 2013 15:51:19 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <27120AB3-75C5-4EB0-898B-FE2D354E59D4@nostrum.com>
References: <FA827D6C-D3C0-4F8A-8FF8-636A93A9646D@nostrum.com>
To: "draft-ietf-ospf-ipv4-embedded-ipv6-routing.all@tools.ietf.org" <draft-ietf-ospf-ipv4-embedded-ipv6-routing.all@tools.ietf.org>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 166.147.77.136 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.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, 19 Apr 2013 20:51:26 -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-ospf-ipv4-embedded-ipv6-routing-11=20
Reviewer: Ben Campbell
Review Date: 2013-04-19
IESG Telechat date: 2013-04-25

Summary: Ready for publication as an informational RFC. All of the =
comments from my previous review of version 07 have been addressed. =
However, there=20

Major issues:

None

Minor issues:

None

Nits/editorial comments:

Note: The online IDNits tool appears to be broken today, so I was unable =
to recheck this version.

There is a new section 12 added since version 07. If there is another =
revision prior to approval, I suggest the authors make another pass at =
proofreading it. If not, the errors are all of the sort that can be =
reasonably fixed by the RFC editor. Some specifics:

-- paragraph 3, 1st sentence: "If one approach is to be deployed, it is =
the operator's decision for the choice."

-- paragraph 4, 1st sentence: "... there requires some configurations."=

From ben@nostrum.com  Fri Apr 19 14:03:01 2013
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 25CA621F919A; Fri, 19 Apr 2013 14:03:01 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7Wq0rmR8JN7; Fri, 19 Apr 2013 14:03:00 -0700 (PDT)
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 9B17521F8B0A; Fri, 19 Apr 2013 14:03:00 -0700 (PDT)
Received: from [172.20.10.2] (mobile-166-147-077-136.mycingular.net [166.147.77.136]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3JL2wHF088041 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 19 Apr 2013 16:02:59 -0500 (CDT) (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-ospf-ospfv3-iid-registry-update-03
Date: Fri, 19 Apr 2013 16:02:55 -0500
Message-Id: <737E8708-A346-42B8-888D-3F551C257239@nostrum.com>
To: "draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 166.147.77.136 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.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, 19 Apr 2013 21:03:01 -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-ospf-ospfv3-iid-registry-update-03
Reviewer: Ben Campbell
Review Date: 2013-04-19
IESG Telechat date: 2013-04-25

Summary: This draft is ready for publication as a proposed standard. All =
of the comments from my review of 00 at last call have been addressed.

Major issues:

None.

Minor issues:

None.

Nits/editorial comments:

-- The abstract should mention that this draft now updates RFC 5838.

-- IDNits has a comment about the lack of pre-5378 work boilerplate that =
I do not think is valid in this case--but it might be worth checking.=

From jmh@joelhalpern.com  Fri Apr 19 15:24:25 2013
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 134A821F8512; Fri, 19 Apr 2013 15:24:25 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52UppMhSmAYj; Fri, 19 Apr 2013 15:24:24 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 86E1C21F8528; Fri, 19 Apr 2013 15:24:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 75C4F1C22147; Fri, 19 Apr 2013 15:24:24 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.155.104.126] (unknown [129.192.170.160]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 521FD1C2212C; Fri, 19 Apr 2013 15:24:24 -0700 (PDT)
Message-ID: <5171C416.5070105@joelhalpern.com>
Date: Fri, 19 Apr 2013 18:24:22 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
Subject: [Gen-art] Review: draft-ietf-netmod-rfc6021-bis-01
References: <5170722E.2070401@nostrum.com>
In-Reply-To: <5170722E.2070401@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.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, 19 Apr 2013 22:24:25 -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-netmod-rfc6021-bis-01
     Common YANG Data Types
Reviewer: Joel M. Halpern
Review Date: 19-April-2013
IETF LC End Date: 1-May-2013
IESG Telechat date: N/A

Summary: This document is nearly ready for publication as a Standards 
Track RFC

Major issues:
     (The following may well be a non-issue.)
     In the revision of the ietf-inet-types, the patterns for the new 
ip4-address-no-zone and ipv6-address-no-zone are drastically simplified 
from the ipv4-address and ipv6-address patterns.  The new 
ipv4-address-no-zone allows any sequence of decimal digits an periods, 
while the original was carefully defined as dotted quads of 0..255. 
Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex 
digits and colons.  The original patterns were very careful to match 
rules for validity.  Is there a reason for the change.

Minor issues:

Nits/editorial comments:

From mnot@mnot.net  Sat Apr 20 00:56:05 2013
Return-Path: <mnot@mnot.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 5115521F8FC0 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 00:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.533
X-Spam-Level: 
X-Spam-Status: No, score=-106.533 tagged_above=-999 required=5 tests=[AWL=-3.934, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GcjPn0fvKYlM for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 00:56:04 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 6521721F8F6C for <ietf@ietf.org>; Sat, 20 Apr 2013 00:56:04 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.190.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 012E4509B6; Sat, 20 Apr 2013 03:56:02 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: p1: Via and gateways
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <alpine.LRH.2.01.1304200017490.18732@egate.xpasc.com>
Date: Sat, 20 Apr 2013 17:55:59 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <37AD85F8-D0E1-4B9D-9BF0-99EBE83ADF8D@mnot.net>
References: <F7810D5C-45A6-4D01-83ED-2A9AB5856813@mnot.net> <alpine.LRH.2.01.1304200017490.18732@egate.xpasc.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1503)
Cc: ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Apr 2013 07:56:05 -0000

On 20/04/2013, at 5:21 PM, David Morris <dwm@xpasc.com> wrote:
>=20
> I don't care about MUST, but I think the Via header can be useful for
> problem determination. A smart content server could also adjust for
> a detected accelerator and/or transcoder ... perhaps by avoiding
> optimizations dependant on a direct connection and byte/byte transfer
> between the client and the server.
>=20
> So I'm very much in favor of keeping the Via: header.


Definitely not talking about getting rid of it. The (only, specific) =
point here is whether a gateway that doesn't add Via to responses should =
be called non-conformant.

Personally, I think it should be a MUST for proxies, in both directions. =
However, for a gateway, it either shouldn't be a requirement at all (for =
responses), or it should be a SHOULD with a get-out clause for reasons =
of security (along with a note that they'll need to accept =
responsibility for any issues caused by omitting Via). Still should =
probable be a MUST for requests from gateways.

Cheers,

--
Mark Nottingham   http://www.mnot.net/




From abdussalambaryun@gmail.com  Sat Apr 20 01:26:58 2013
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 E5DE621F8EB7 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 01:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nkrr7KhY8D+2 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 01:26:56 -0700 (PDT)
Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3FF21F8BE4 for <ietf@ietf.org>; Sat, 20 Apr 2013 01:26:56 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w11so2652843pde.37 for <ietf@ietf.org>; Sat, 20 Apr 2013 01:26:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=fohvU8fM+t1KEw6Uf3ETNVTPa8DQPx1IC/Qg3EQ/8Gc=; b=QnMNmYT0/N0x4KdrUGqPrzbsBf+538d1107RuEzpa0HJsYJK1tbWVmqoYZiJJOUdgX t2Hufxm1nQz0EtB6biaymjcG84OhwSgLx0ENmfnGI2FCk4H84omTGeUj50pCdiS+CY3W ceSok9gdH/Bu7Y57IY9oiqMulxckL5jCQ7Xm9vQJqwboGtSIBtxfuR7qbzWzeB4ti4j6 9WpASqs11yQUAbnhckd8XaT4w/i5YwT4SdeSy0tDUahuIA3IAOVRoPQFuBAIMc4cp1vn WZ9p6K2MUMBNK2a+3e5C7NXh1xKBWQiS0YfRNKABVUzetjdVzgkcDt3nL427ccLXBKq8 fraA==
MIME-Version: 1.0
X-Received: by 10.69.12.37 with SMTP id en5mr22960283pbd.93.1366446416288; Sat, 20 Apr 2013 01:26:56 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Sat, 20 Apr 2013 01:26:56 -0700 (PDT)
Date: Sat, 20 Apr 2013 10:26:56 +0200
Message-ID: <CADnDZ88-FJ5_DC70jRyfZsoZ9QNcAjP1Uuj4Mkdh67r7c+5H4A@mail.gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ted.ietf@gmail.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: Sat, 20 Apr 2013 08:26:58 -0000

Dear Ted,

I agree with you totally, hope that your suggestion is considered for
progress in our participation (me as newcomer feedback). Our choices
in life is all about awareness,

I just wanted to add that any individual while *participation* with
any body/person in or out IETF, s/he will try to evaluation that
relationship and will gain experience/knowledge of such body
reputation, then s/he will think could I trust the system for *my
progress in participating*. For example, I was trying to get a chance
to enter an old WG, but still difficult to be counted/acknowledged, I
now decided to give my review of their work in IESG call by ignoring
WGLC because of their reputation. Thanking you,

Best Regards
Abdussalam

++++++++++++++++++++
From: Ted Hardie <ted.ietf at gmail.com>
To: IETF <ietf at ietf.org>
Date: Fri, 19 Apr 2013 11:13:41 -0700

http://www.ietf.org/mail-archive/web/ietf/current/msg78758.html

From hsantos@isdg.net  Sat Apr 20 07:14:01 2013
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 B2C9A21F8D61 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 07:14:01 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lcrLSvmAkqp7 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 07:14:00 -0700 (PDT)
Received: from ntbbs.winserver.com (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 89E1021F89C3 for <ietf@ietf.org>; Sat, 20 Apr 2013 07:14:00 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3031; t=1366467233; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=15Bu2bY qnMFtAAllCaPEOL9LcTM=; b=ZOJRQSL31X4NNLjE1XZksnHND2aOikneHxzQHgK BD+m8459jNWasZH+jj8OkPNoCIcV1w3jTwW5pDvKVsOhdMW0u2GyvwkGcsPC046H zbscaqEICyfqUXh9TcJWZw/H4BCDj16rZgJTIEjrYDjWrE67eFY7tKttaMRwtJVa O10Q=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 20 Apr 2013 10:13:53 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 965960126.2773.4416; Sat, 20 Apr 2013 10:13:52 -0400
Message-ID: <5172A258.5030104@isdg.net>
Date: Sat, 20 Apr 2013 10:12:40 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
In-Reply-To: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Sat, 20 Apr 2013 14:14:01 -0000

On 4/19/2013 2:13 PM, Ted Hardie wrote:
>
 > ...
 >
> There are other methods that may well be better than the two Suresh and I
> discussed, but I put these forward as a potentially concrete step that may
> help those struggling with this to understand that the end result of this
> need not be quotas.  It should be a better environment for all of our
> volunteers.
>
> best regards,
>
> Ted Hardie
>

I call this improving the Electronic diversity of the IETF.  It has 
communications tools but it needs more.  There is work is in progress 
(MeetEcho and so on), but it still needs more.  The IETF does not have a 
copyright on this problem. Every organizations has to improve its 
communications methods.

Short list of ideas:

  - Better Marketing, Website "Sales."

  - Focus on its products, standards, Publications of ideas, methods
    in a formal format, old and new technology reviews, Global Reviews,
    even legal topics, etc.

  - Online Forums to resolve the device independent issue
    - with continued Offline communications avenues.
    - Device independent Participation.

  - Memberships!!! Get that "Professional Feel" of getting a
    membership "badge", great for resumes,
    - Different levels,
    - Give folks their own @IETF.ORG email address!

  - Offer "Co-op" projects (as opposed to jobs) for students (newcomers),
    - Management of projects,
    - Documentation experience,
    - Programmers for the developers of protocols,
    - Testers,
    - etc.

There is much more that can be done, but we are still holding on to a 
version of the past that is keeping the IETF behind.   We all fall in 
that trap of adhering to safe, conservative, comfortable and for the 
most part, working practices. I know I (my company) did and we are still 
trying to get out of that hole.  In this way, its not a Start Up Plan 
that is needed.  It would a Restructuring Plan.  The IETF is not start 
up because it can't afford or has the leverage to start new things 
without harming others. In this way, it is currently Pareto Efficient 
because it does consider all things diverse.  However, I believe we need 
to improve the Electronic Diversity by blending in the new things to the 
existing methods.  I hope these discussions regarding diversity is not 
just about increasing IETF meetings attendance.

Lastly, I think we need to remember that there are many folks who are 
not in this to be managers, leaders, RFC writers, or even "complete 
Reviewers" but just implementators and followers, including CTOs who 
would like nothing better but to get better abstracts and executive 
summaries from the flow of I-Ds submitted.  They put their trust on 
their peers more involved with IETF to do the "best" engineering job and 
certainly not a result that will hurt them.  This is where the IETF/IESG 
experiences is still and always vital, whatever is done, the IETF can 
not make her end products have a lesser quality.  Its a tough task, but 
one that can be managed with improved Electronic Diversity.


--
HLS


From dwm@xpasc.com  Sat Apr 20 08:17:33 2013
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 01EC221F8E36 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 08:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.908
X-Spam-Level: 
X-Spam-Status: No, score=-2.908 tagged_above=-999 required=5 tests=[AWL=-1.601, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KSFP4h+bufmi for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 08:17:32 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 985AA21F8D6A for <ietf@ietf.org>; Sat, 20 Apr 2013 08:17:32 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 006994059A; Sat, 20 Apr 2013 15:17:31 +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 r3KFHVBm023840; Sat, 20 Apr 2013 08:17:31 -0700
Date: Sat, 20 Apr 2013 08:17:31 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
Subject: Re: p1: Via and gateways
In-Reply-To: <37AD85F8-D0E1-4B9D-9BF0-99EBE83ADF8D@mnot.net>
Message-ID: <alpine.LRH.2.01.1304200808170.18732@egate.xpasc.com>
References: <F7810D5C-45A6-4D01-83ED-2A9AB5856813@mnot.net> <alpine.LRH.2.01.1304200017490.18732@egate.xpasc.com> <37AD85F8-D0E1-4B9D-9BF0-99EBE83ADF8D@mnot.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
Cc: ietf@ietf.org, 'HTTP Working Group' <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 'HTTP Working Group' <ietf-http-wg@w3.org>, 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, 20 Apr 2013 15:17:33 -0000

On Sat, 20 Apr 2013, Mark Nottingham wrote:

> 
> On 20/04/2013, at 5:21 PM, David Morris <dwm@xpasc.com> wrote:
> > 
> > I don't care about MUST, but I think the Via header can be useful for
> > problem determination. A smart content server could also adjust for
> > a detected accelerator and/or transcoder ... perhaps by avoiding
> > optimizations dependant on a direct connection and byte/byte transfer
> > between the client and the server.
> > 
> > So I'm very much in favor of keeping the Via: header.
> 
> Definitely not talking about getting rid of it. The (only, specific)
> point here is whether a gateway that doesn't add Via to responses should
> be called non-conformant.

I didn't think you were making that suggestion, but I see comments about
lack of use turning into suggestions for removal.

> Personally, I think it should be a MUST for proxies, in both directions.
> However, for a gateway, it either shouldn't be a requirement at all (for
> responses), or it should be a SHOULD with a get-out clause for reasons
> of security (along with a note that they'll need to accept
> responsibility for any issues caused by omitting Via). Still should
> probable be a MUST for requests from gateways.

I'm not sure how to express it, but the requirement probably should be
based on whether the traffic leaves the control of the organization that
owns the gateway (or even proxy). I think Willy Tarreau noted a
performance concern for some types of gateways if the requirement is
added to modify the message.

Dave Morris

From melinda.shore@gmail.com  Sat Apr 20 10:21:23 2013
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 4169A21F8A4E for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 10:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.031
X-Spam-Level: 
X-Spam-Status: No, score=0.031 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yzx1OFMwnegZ for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 10:21:21 -0700 (PDT)
Received: from mail-da0-x22c.google.com (mail-da0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 82D6D21F890F for <ietf@ietf.org>; Sat, 20 Apr 2013 10:21:16 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id z20so2414016dae.17 for <ietf@ietf.org>; Sat, 20 Apr 2013 10:21:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=X4mjvWWm1Msm5sC3uQ84Cz18GMvu6qWosHIKlmtcoNg=; b=X/Q8qiUHrZkVnqsH8yr4UZILHEBoCgK810JD+LId/Cips0aUDrTS0VzlSZgrFZ8bk/ h54B4bwzFJ35+BgAF3qOJoRBkTigXz3ZSLXISD2B3ybUvtE0GxSQiiWaExQKxeTwm/iQ uzx/FRWbsmFYSucsrf3c2fKRyIVIdcbX2mLBoDzXOTsmd5N0ykbUnjJskK63aIrlTHwi jZRMbwEXz858QPiY90lcD++rlp5ni03zWq5iCg+rlIUjl8NkqbL5M98dhejSKbAEDMC/ inPRB2E35VFSEFLyC2EpiZgG9/8/ubsRLCRPT+/T04gkJvg8zfow5TUtHeVjXEROEUAf /6dg==
X-Received: by 10.66.234.198 with SMTP id ug6mr20965274pac.43.1366478476288; Sat, 20 Apr 2013 10:21:16 -0700 (PDT)
Received: from spandex.local (66-230-83-205-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.83.205]) by mx.google.com with ESMTPS id be7sm19476542pad.20.2013.04.20.10.21.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 20 Apr 2013 10:21:15 -0700 (PDT)
Message-ID: <5172CE86.2010804@gmail.com>
Date: Sat, 20 Apr 2013 09:21:10 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Meritocracy, diversity, and leaning on the people you know
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com> <5172A258.5030104@isdg.net>
In-Reply-To: <5172A258.5030104@isdg.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: Sat, 20 Apr 2013 17:21:23 -0000

On 4/20/13 6:12 AM, Hector Santos wrote:
> There is much more that can be done, but we are still holding on to a
> version of the past that is keeping the IETF behind. 

Behind what?

Melinda



From abdussalambaryun@gmail.com  Sun Apr 21 02:50:23 2013
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 B72FC21F8503 for <ietf@ietfa.amsl.com>; Sun, 21 Apr 2013 02:50:23 -0700 (PDT)
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.167, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33p9FGzRpLjk for <ietf@ietfa.amsl.com>; Sun, 21 Apr 2013 02:50:23 -0700 (PDT)
Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com [209.85.192.176]) by ietfa.amsl.com (Postfix) with ESMTP id 0C65A21F84F5 for <ietf@ietf.org>; Sun, 21 Apr 2013 02:50:23 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id r11so2975838pdi.35 for <ietf@ietf.org>; Sun, 21 Apr 2013 02:50:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=haSjRjXqhq5T/5R8kEM1wLZPI8i1jsaLlAtfuRJ6G9U=; b=fc8XfaCecPmCSLSzoDNDWkX5vpHALBR8SbqKv3o5duzBXWBWgl+4BHJkV4F9Oa2J6Y hF+3TTuGRLarzILFqny9AgypaZC7SGJ+qtWl56oz8eM6/l/1Yma3JhQGiQY2NHTpt+H1 Mnuph3GAbv9t96gBRlaacQYCoOXfNLC2/exRvZ+wqpvyab79rntjKDb5sgkMieascVWe RoSnJ+YzRU/hJVlKC44oTKd+nmVHq6V9XQlhrzpplbDH+5QtJsJhlIuzQy1gxAh4F2W6 i5agVig1DmWLoTmSm8nRlTokgxOu/BSnF5HR8gZUDEBTcAjkpdOZ+f5J77Q6dY2MNHTQ 2ftw==
MIME-Version: 1.0
X-Received: by 10.68.43.35 with SMTP id t3mr27239700pbl.202.1366537822794; Sun, 21 Apr 2013 02:50:22 -0700 (PDT)
Received: by 10.69.8.2 with HTTP; Sun, 21 Apr 2013 02:50:22 -0700 (PDT)
Date: Sun, 21 Apr 2013 11:50:22 +0200
Message-ID: <CADnDZ8_hQotSCpJRskF9uHMsTMpGNaZpC+-4iFyo_Meu0RzZbw@mail.gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Hector Santos <hsantos@isdg.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: Sun, 21 Apr 2013 09:50:23 -0000

Hi Hector,

Thanks for your input. I add that we/I need to write down these ideas
(related to IETF Structure progress and IETF Diversity) into an I-D,
because if not they can be forgotten. Restructuring is always an
important task for old WGs/bodies. The community changes every day so
organisations follow that change to interact with community. We need
diversity not to increase goers or attendance, we need diversity in
IETF to increase *participation* and *uses of standards* by the world
community of Internet.

AB

From: Hector Santos <hsantos at isdg.net>
To: Ted Hardie <ted.ietf at gmail.com>
Cc: IETF <ietf at ietf.org>
Date: Sat, 20 Apr 2013 10:12:40 -0400

http://www.ietf.org/mail-archive/web/ietf/current/msg78773.html

From spencer@wonderhamster.org  Sun Apr 21 12:03:14 2013
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 189FD21F93AA for <ietf@ietfa.amsl.com>; Sun, 21 Apr 2013 12:03:14 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zxc5uHT0NAWo for <ietf@ietfa.amsl.com>; Sun, 21 Apr 2013 12:03:13 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 1937521F93A5 for <ietf@ietf.org>; Sun, 21 Apr 2013 12:03:13 -0700 (PDT)
Received: from [192.168.1.74] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net [99.108.174.213]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0LevHL-1Us09M0tah-00qmN9; Sun, 21 Apr 2013 15:03:10 -0400
Message-ID: <517437E8.8010206@wonderhamster.org>
Date: Sun, 21 Apr 2013 14:03:04 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com> <CAKHUCzxGnZvZX8YtHzCoHb-Oi2MhaWNVP7Oy8+NAP6HrhuooMg@mail.gmail.com>
In-Reply-To: <CAKHUCzxGnZvZX8YtHzCoHb-Oi2MhaWNVP7Oy8+NAP6HrhuooMg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:yVEJjPONJ7Cgms1+2qWrEa843r9t/ua9VlX++J3P03X qGQYNT+xj6/w2pkev+sDV+kk3Gs+SWdMg3WhONmWhNTOgE54lJ AU/jpJinZHM6nNJySWJrt0xYbvsMgqPBp13fzhaProqUyck/RF FbSZz2j9i35GpSub6OKJOlonfONGFIIsOYNo4RIilnS3mOj9BX O8HudMrGDL94LhT7o3GX500VYENwlyWozMBfL+A4sOAx5N8pkv /q6uNg8rbYc5lB2d2NHGCLicMGG1hVuzVSZLvH44BPaVXbc6yX pbOcHUd56Jc+ZMHkynxT5pVBZ2yCXItfqotzWQCWwZOSQOU16g pKLsDPGbC3zCk83MrsYw/gpK7XOuTTWXM2N3pLfD5
Cc: Ted Hardie <ted.ietf@gmail.com>, "ietf@ietf.org 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: Sun, 21 Apr 2013 19:03:14 -0000

On 4/19/2013 1:47 PM, Dave Cridland wrote:
> Nice post.
>
> I wonder whether a better mechanism for drawing newcomers into the inner
> circle - which is what I think you're intent is here - would be to randomly
> select people to be involved in a short online meeting to discuss the
> draft, rather than review it in isolation.
>
> It'd be a different kind of review, which adds value for us, I think, and
> would instantiate new human subnets which could be used to bootstrap other
> involvement.
>
> This is, I stress, merely a quick reaction to your much more thoughtful
> post, and I reserve the right to backtrack and change my mind.

I'm replying to Dave's note, but read further through the thread.

I'm not seeing the randomly-invite-to-review and 
randomly-invite-to-discuss being mutually exclusive. If I'm reading the 
mail threads on newcomer assimilation correctly, what we're hoping for 
is to identify people who we might not always identify, who can and will 
produce good work. The additional random selection gives people who we 
might not have identified a chance to show whether they can and will 
produce good work.

I note that one of these possibilities places more emphasis on spoken 
English than the other. That's important to keep in mind. Maybe letting 
people self-select for the kind of review is helpful.

Thanks,

Spencer


From mrw@lilacglade.org  Sun Apr 21 12:50:29 2013
Return-Path: <mrw@lilacglade.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 E2D6321F935D for <ietf@ietfa.amsl.com>; Sun, 21 Apr 2013 12:50:29 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AHsDBdm7u9t5 for <ietf@ietfa.amsl.com>; Sun, 21 Apr 2013 12:50:28 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 4C4D521F935B for <ietf@ietf.org>; Sun, 21 Apr 2013 12:50:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id DF6AE20248; Sun, 21 Apr 2013 15:48:38 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UzKkWu_pOBXR; Sun, 21 Apr 2013 15:48:37 -0400 (EDT)
Received: from new-host-4.home (pool-71-184-79-25.bstnma.fios.verizon.net [71.184.79.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: mrw@mail.suchdamage.org) by mail.painless-security.com (Postfix) with ESMTPSA; Sun, 21 Apr 2013 15:48:37 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_51678111-C42C-41E8-BA05-2CFDC5A1BB9C"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
Date: Sun, 21 Apr 2013 15:50:27 -0400
Message-Id: <5C2A82A7-C4C0-402F-9C7C-1A7B23544218@lilacglade.org>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.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: Sun, 21 Apr 2013 19:50:30 -0000

--Apple-Mail=_51678111-C42C-41E8-BA05-2CFDC5A1BB9C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Excellent post, Ted.  I really like your suggestions, and I think these =
are the types of things we should be doing to more widely leverage the =
talents of people who are available to participate in the IETF.=20

Margaret

On Apr 19, 2013, at 2:13 PM, Ted Hardie <ted.ietf@gmail.com> wrote:

> Following a number of the threads on diversity and, in particular, on =
whether the effort to get a better demographic view of participation =
will lead to quotas, I have been increasingly uncomfortable with some of =
the arguments which appear to have some presumptions about how diversity =
and meritocracy relate.
>=20
> To describe the issue, I'd like to start with a different situation =
and then draw a parallel.  The different situation I'd like to use is a =
startup company experiencing growth.  In my experience, startups that =
succeed tend to have a very strong core group that comes together early =
on; they tackle the hard work and develop a great degree of =
understanding of and trust in each others' capabilities.  As the company =
grows, it's very common for that core group to continue to rely on each =
other whenever a difficult problem arrives.  That can manifest in those =
folks moving up to be the top of a hierarchy and individually handling =
delegation; it can also manifest itself in severe bottlenecks as the =
individuals remain critical resources to solve an increasingly large =
number of problems. =20
>=20
> In both cases, it's common for the individuals to pull in their own =
networks of trusted folks as support.  Another way of expressing this is =
that a particular human network is the basis of an enterprise, and the =
scaling of that human network tends to work by each one of the humans =
pulling in additional folks from their personal networks whose skills =
are personally known to them.   The result of that is that the start-up =
*is* a meritocracy as it grows (because the individuals are chosen based =
on their abilities), but its diversity is initially limited to that of =
the personal networks of those who end up in critical positions.  As the =
company grows and recruiting becomes more formalized, the overall =
make-up may become more diverse, but key positions may remain less =
diverse as the human networks remain in place or are renewed.  Note that =
the scope of this diversity may have nothing to do with race or gender, =
but may instead be about schools, disciplines, or ages. (When it's =
schools, we even get to reuse the phrase "old boy network"   in its =
original sense).
>=20
> In the IETF, things are slightly different, in that attendance and =
participation are completely open (there's no hiring gate), but many of =
the same human networks are in play.  As a working group chair, when I =
stare out at a sea of faces looking for a scribe, the chances of my =
asking someone I know produces good minutes is much higher than my =
asking someone whose work I don't know.  But that also translates into =
the pool of candidates being *only those people I know*, because that's =
the only pool whose merits I have assessed.  In other words, even though =
I'm selecting on merit (good note takers), the way in which merit is =
determined (personal knowledge) results in my not using the whole pool.=20=

>=20
> If there were an objective measure I could use instead, the WG's pool =
of potential scribes would go up and the allocation likely would be =
fairer--if I could say: "please tell me which potential minute taker =
(with a score of 70 or above) was tapped for the work least recently" =
and then tap that individual, things get better for those who are =
otherwise tapped too often.  Note again that the increased diversity in =
that pool may have nothing to do with race or gender or even age, but it =
might instead be in technical interest area (since I came from APPs into =
RAI, my background is focused in certain areas). =20
>=20
> The individual impact of my limited human networks may be small (I =
hope so, anyway); in the best case, the limitations of mine would be =
overcome by the scope of my co-chairs' and  ADs'.  But it can easily be =
a self-reinforcing instead; if all the chairs come from the same =
backgrounds, they may know and trust the same people.  Those people =
likely are being selected for merit--but not from the total available =
pool.
>=20
> As folks worry about quotas and its impact on quality, I think we must =
recognize that the effort to promote based on merit alone is subject to =
the limits by which merits are assessed.  The more human those are, the =
higher the likelihood that network limitations or cognitive bias will =
have an impact on our best use of the volunteers we have or could =
attack.=20
>=20
> So, given this very human problem, what can we do?  Suresh and I =
happened to be at a different SDO meeting yesterday, and we sat down =
briefly and discussed this.  Two things emerged as possible concrete =
actions from that brainstorming, but they both boil down to this:  =
institutionalize methods for getting technical input from newcomers/less =
well-known participants, so that technical input can be basis of =
assessments.  In other words, give those outside the human networks an =
institutional method for being part of the technical community. That =
should align with chairs' chronic need to find technical energy to =
assess and complete work.
>=20
> The first suggestion is a "Newcomer's directorate".  After an =
individual starts participating in the IETF, either by attending a =
meeting or joining a mailing list, offer them the opportunity to become =
part of a review team.  That review team would have templates (as does =
AppsDir, the GenArt team, and others) and example reviews to guide the =
new participant.  The newcomers would be assigned last call reviews that =
would then be sent to the relevant working group chairs and ADs for =
review.  Those who produced good work would then be known to others =
relatively quickly.  At the end of their "newcomer" period they might =
transition to a relevant directorate based in an Area.
>=20
> The second suggestion is a simple tool that at WG call time (be it =
last call or call for adoption) randomly selects a set number of =
participants from the mailing list, and then asks for a review or =
commentary.  So 5 folks off the mailing list are directly asked for =
their opinion, without regard to preconceived notions of the chairs =
about who would be a good reviewer.  If someone declines, the tool would =
select a new random person to fill out.  The working group as a whole =
thus gets a chance to understand someone's technical viewpoint, without =
that person having to fit within one of the established human networks.
>=20
> There are other methods that may well be better than the two Suresh =
and I discussed, but I put these forward as a potentially concrete step =
that may help those struggling with this to understand that the end =
result of this need not be quotas.  It should be a better environment =
for all of our volunteers.
>=20
> best regards,
>=20
> Ted Hardie


--Apple-Mail=_51678111-C42C-41E8-BA05-2CFDC5A1BB9C
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; =
"><div><br></div>Excellent post, Ted. &nbsp;I really like your =
suggestions, and I think these are the types of things we should be =
doing to more widely leverage the talents of people who are available to =
participate in the =
IETF.&nbsp;<div><br><div>Margaret</div><div><br><div><div><div>On Apr =
19, 2013, at 2:13 PM, Ted Hardie &lt;<a =
href=3D"mailto:ted.ietf@gmail.com">ted.ietf@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Following a number of the threads on diversity and, in =
particular, on whether the effort to get a better demographic view of =
participation will lead to quotas, I have been increasingly =
uncomfortable with some of the arguments which appear to have some =
presumptions about how diversity and meritocracy relate.<br>
<br>To describe the issue, I'd like to start with a different situation =
and then draw a parallel.&nbsp; The different situation I'd like to use =
is a startup company experiencing growth.&nbsp; In my experience, =
startups that succeed tend to have a very strong core group that comes =
together early on; they tackle the hard work and develop a great degree =
of understanding of and trust in each others' capabilities.&nbsp; As the =
company grows, it's very common for that core group to continue to rely =
on each other whenever a difficult problem arrives.&nbsp; That can =
manifest in those folks moving up to be the top of a hierarchy and =
individually handling delegation; it can also manifest itself in severe =
bottlenecks as the individuals remain critical resources to solve an =
increasingly large number of problems.&nbsp; <br>
<br>In both cases, it's common for the individuals to pull in their own =
networks of trusted folks as support.&nbsp; Another way of expressing =
this is that a particular human network is the basis of an enterprise, =
and the scaling of that human network tends to work by each one of the =
humans pulling in additional folks from their personal networks whose =
skills are personally known to them.&nbsp;&nbsp; The result of that is =
that the start-up *is* a meritocracy as it grows (because the =
individuals are chosen based on their abilities), but its diversity is =
initially limited to that of the personal networks of those who end up =
in critical positions.&nbsp; As the company grows and recruiting becomes =
more formalized, the overall make-up may become more diverse, but key =
positions may remain less diverse as the human networks remain in place =
or are renewed.&nbsp; Note that the scope of this diversity may have =
nothing to do with race or gender, but may instead be about schools, =
disciplines, or ages. (When it's schools, we even get to reuse the =
phrase <a href=3D"http://en.wikipedia.org/wiki/Old_boy_network">"old boy =
network"&nbsp;&nbsp; </a>in its original sense).<br>
<br>In the IETF, things are slightly different, in that attendance and =
participation are completely open (there's no hiring gate), but many of =
the same human networks are in play.&nbsp; As a working group chair, =
when I stare out at a sea of faces looking for a scribe, the chances of =
my asking someone I know produces good minutes is much higher than my =
asking someone whose work I don't know.&nbsp; But that also translates =
into the pool of candidates being *only those people I know*, because =
that's the only pool whose merits I have assessed.&nbsp; In other words, =
even though I'm selecting on merit (good note takers),=20
the way in which merit is determined (personal knowledge) results in my=20=

not using the whole pool. <br><br>If there were an objective measure I =
could use instead, the WG's pool of potential scribes would go up and =
the allocation likely would be fairer--if I could say: "please tell me =
which potential minute taker (with a score of 70 or above) was tapped =
for the work least recently" and then tap that individual, things get =
better for those who are otherwise tapped too often.&nbsp; Note again =
that the increased diversity in that pool may have nothing to do with =
race or gender or even age, but it might instead be in technical =
interest area (since I came from APPs into RAI, my background is focused =
in certain areas).&nbsp; <br>
<br>The individual impact of my limited human networks may be small (I =
hope so, anyway); in the best case, the limitations of mine would be =
overcome by the scope of my co-chairs' and&nbsp; ADs'.&nbsp; But it can =
easily be a self-reinforcing instead; if all the chairs come from the =
same backgrounds, they may know and trust the same people.&nbsp; Those =
people likely are being selected for merit--but not from the total =
available pool.<br>
<br>As folks worry about quotas and its impact on quality, I think we =
must recognize that the effort to promote based on merit alone is =
subject to the limits by which merits are assessed.&nbsp; The more human =
those are, the higher the likelihood that network limitations or =
cognitive bias will have an impact on our best use of the volunteers we =
have or could attack. <br>
<br>So, given this very human problem, what can we do?&nbsp; Suresh and =
I happened to be at a different SDO meeting yesterday, and we sat down =
briefly and discussed this.&nbsp; Two things emerged as possible =
concrete actions from that brainstorming, but they both boil down to =
this:&nbsp; institutionalize methods for getting technical input from =
newcomers/less well-known participants, so that technical input can be =
basis of assessments.&nbsp; In other words, give those outside the human =
networks an institutional method for being part of the technical =
community. That should align with chairs' chronic need to find technical =
energy to assess and complete work.<br>
<br>The first suggestion is a "Newcomer's directorate".&nbsp; After an =
individual starts participating in the IETF, either by attending a =
meeting or joining a mailing list, offer them the opportunity to become =
part of a review team.&nbsp; That review team would have templates (as =
does AppsDir, the GenArt team, and others) and example reviews to guide =
the new participant.&nbsp; The newcomers would be assigned last call =
reviews that would then be sent to the relevant working group chairs and =
ADs for review.&nbsp; Those who produced good work would then be known =
to others relatively quickly.&nbsp; At the end of their "newcomer" =
period they might transition to a relevant directorate based in an =
Area.<br>
<br>The second suggestion is a simple tool that at WG call time (be it =
last call or call for adoption) randomly selects a set number of =
participants from the mailing list, and then asks for a review or =
commentary.&nbsp; So 5 folks off the mailing list are directly asked for =
their opinion, without regard to preconceived notions of the chairs =
about who would be a good reviewer.&nbsp; If someone declines, the tool =
would select a new random person to fill out.&nbsp; The working group as =
a whole thus gets a chance to understand someone's technical viewpoint, =
without that person having to fit within one of the established human =
networks.<br>
<br>There are other methods that may well be better than the two Suresh =
and I discussed, but I put these forward as a potentially concrete step =
that may help those struggling with this to understand that the end =
result of this need not be quotas.&nbsp; It should be a better =
environment for all of our volunteers.<br>
<br>best regards,<br><br>Ted Hardie<br>
</blockquote></div><br></div></div></div></body></html>=

--Apple-Mail=_51678111-C42C-41E8-BA05-2CFDC5A1BB9C--

From lear@cisco.com  Sun Apr 21 23:20:20 2013
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 DB4EA21F863B; Sun, 21 Apr 2013 23:20:20 -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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QoTY3ldtvZkj; Sun, 21 Apr 2013 23:20:20 -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 9455F21F8630; Sun, 21 Apr 2013 23:20:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3556; q=dns/txt; s=iport; t=1366611619; x=1367821219; h=message-id:date:from:mime-version:to:subject; bh=erRVKyMmVdZ0BvYjA1uoZSt2jrb8CRHthL/IJ+0DsI0=; b=f9ePuzyI+H4A6dny9wq7+X0Kq46uneNgd9ycoy9dqVOzWn9COzpFwGv6 FCeZQsTOu64scPEXrLzGMjDZikHLhjYOndh7ZdmxP6xIcCqy5i/QgpXcS cnEsXrWb4XNgs0TvgDntnaam3VP9CE7W5WO7LMVgEoCNe0qI6SvK/BebD g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwGADnWdFGQ/khM/2dsb2JhbAAWOYMGg2eFXrh0FnSCSVUaBh0WCwILAwIBAgFLAQwIAQGIEIwyghGbB5FukXqBEwOXFZEagw46
X-IronPort-AV: E=Sophos;i="4.87,524,1363132800"; d="scan'208,217";a="13468483"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 22 Apr 2013 06:20:17 +0000
Received: from ams3-vpn-dhcp5433.cisco.com (ams3-vpn-dhcp5433.cisco.com [10.61.85.56]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3M6KFGJ022230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Apr 2013 06:20:15 GMT
Message-ID: <5174D69F.6090300@cisco.com>
Date: Mon, 22 Apr 2013 08:20:15 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>, draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, Bob Hinden <bob.hinden@gmail.com>, 6man@ietf.org
Subject: last call comments for draft-ietf-6man-stable-privacy-addresses-06
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative; boundary="------------030704070505080302060200"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Apr 2013 06:20:21 -0000

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

In the process of doing the apps area review, I came across some points
that were not related to applications.  The basis for these comments is
precisely the sentiment that Russ Housley expressed, which is that the
specification is done when there is no more to remove.  With this
document, I wonder if quite a bit could be removed.

Specifically, a great deal of discussion goes into the PRF involving DAD
counters, etc, when all that is needed is a suitable PRF.  The draft in
fact says this in Section 3 after an explanation of the inputs.  Any PRF
that follows the guidelines of RFC 4086 should do fine and not cause
interoperability OR security problems.  Put simply, you are
over-specifying the RID and derive no benefit from doing so.

Also, the following text in section 3 Page 7 is contorted:

      This means that this document does not formally obsolete or
      deprecate any of the existing algorithms to generate Interface IDs
      (e.g. such as that specified in [RFC2464]).  However, those IPv6
      implementations that employ this specification must generate all
      of their "stable" addresses as specified in this document.

My suggestion is to simplify remove it as it is self-evident.

Finally, this algorithm requires that the resultant host portion be 64
bits.  Is that necessary?

Eliot


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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <p>In the process of doing the apps area review, I came across some
      points that were not related to applications.  The basis for these
      comments is precisely the sentiment that Russ Housley expressed,
      which is that the specification is done when there is no more to
      remove.  With this document, I wonder if quite a bit could be
      removed.<br>
    </p>
    <p>Specifically, a great deal of discussion goes into the PRF
      involving DAD counters, etc, when all that is needed is a suitable
      PRF.  The draft in fact says this in Section 3 after an
      explanation of the inputs.  Any PRF that follows the guidelines of
      RFC 4086 should do fine and not cause interoperability OR security
      problems.  Put simply, you are over-specifying the RID and derive
      no benefit from doing so.<br>
    </p>
    <p>Also, the following text in section 3 Page 7 is contorted:<br>
      <br>
            This means that this document does not formally obsolete or<br>
            deprecate any of the existing algorithms to generate
      Interface IDs<br>
            (e.g. such as that specified in [RFC2464]).  However, those
      IPv6<br>
            implementations that employ this specification must generate
      all<br>
            of their "stable" addresses as specified in this document.<br>
    </p>
    <p>My suggestion is to simplify remove it as it is self-evident.<br>
    </p>
    <p>Finally, this algorithm requires that the resultant host portion
      be 64 bits.  Is that necessary?<br>
    </p>
    <p>Eliot<br>
    </p>
  </body>
</html>

--------------030704070505080302060200--

From stbryant@cisco.com  Mon Apr 22 03:04:46 2013
Return-Path: <stbryant@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 5B02621F86C5 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 03:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pQ0yMVJyXGY for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 03:04:45 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA5C21F869A for <ietf@ietf.org>; Mon, 22 Apr 2013 03:04:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3373; q=dns/txt; s=iport; t=1366625085; x=1367834685; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=gvn7KyxgN0zbY8Dw6QcAk3Xy+k5p2TMZByLKqRgJRV4=; b=WoiDnVc4BJyFKTjdIe/H4IRcnxM6FNAZ/adfM+ax5J+u6iUMHUqdyfAx 1BCfOX2SotzZQiMoVJ7yLWPPnlp3gGadG3ehYfPwxzsZWFcAqBwIsWdBP EbnQZlGJ0Ze688uod/n7S1Gegs+6usl8yqz/I6UvgAug4MQ1pcQ9DsBi9 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8GAEoKdVGQ/khN/2dsb2JhbAAWOYMGN4kOtQmCZoEGFnSCHwEBAQR4ARALBBQJFg8JAwIBAgFFBg0BBwEBiBCML68kjX2BQgeDRwOTRoNPhguLD4MNgXI
X-IronPort-AV: E=Sophos;i="4.87,525,1363132800"; d="scan'208,217";a="82125879"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 22 Apr 2013 10:04:42 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3MA4e2k027148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Apr 2013 10:04:40 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3MA4cDV000341; Mon, 22 Apr 2013 11:04:39 +0100 (BST)
Message-ID: <51750B36.2030404@cisco.com>
Date: Mon, 22 Apr 2013 11:04:38 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
In-Reply-To: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000106070309020705020409"
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: Mon, 22 Apr 2013 10:04:46 -0000

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

On 19/04/2013 19:13, Ted Hardie wrote:
> As a working group chair, when I stare out at a sea of faces looking 
> for a scribe, the chances of my asking someone I know produces good 
> minutes is much higher than my asking someone whose work I don't know. 
Think about how this often works in WGs without a
secretary or regular scribe.

Chair says we need a volunteer for a scribe.

Everyone looks away and sits on their hands.

Chair says no scribe, no meeting.

Everyone looks away and hangs their head even lower melting into the floor.

Chair pleads a bit more.

Silence.

Chair asks someone they know since they are less likely to refuse.

There maybe a refusal or two by people who expect to be at the
mic a lot, or need to leave early, or are only there to catch up
with their email.

Eventually someone committed to the WG, and usually well known to the
chairs, frequently a name called by the chair, offers to scribe in order
to the meeting started.

The strong temptation is to just ask one of the well known good
scribes before the meeting in order not to waste time in a tight agenda.

Stewart



--------------000106070309020705020409
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 19/04/2013 19:13, Ted Hardie wrote:<br>
    </div>
    <blockquote
cite="mid:CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      As a working group chair, when I stare out at a sea of faces
      looking for a scribe, the chances of my asking someone I know
      produces good minutes is much higher than my asking someone whose
      work I don't know.&nbsp; </blockquote>
    Think about how this often works in WGs without a <br>
    secretary or regular scribe.<br>
    <br>
    Chair says we need a volunteer for a scribe.<br>
    <br>
    Everyone looks away and sits on their hands.<br>
    <br>
    Chair says no scribe, no meeting.<br>
    <br>
    Everyone looks away and hangs their head even lower melting into the
    floor.<br>
    <br>
    Chair pleads a bit more.<br>
    <br>
    Silence.<br>
    <br>
    Chair asks someone they know since they are less likely to refuse. <br>
    <br>
    There maybe a refusal or two by people who expect to be at the <br>
    mic a lot, or need to leave early, or are only there to catch up <br>
    with their email.<br>
    <br>
    Eventually someone committed to the WG, and usually well known to
    the <br>
    chairs, frequently a name called by the chair, offers to scribe in
    order <br>
    to the meeting started.<br>
    <br>
    The strong temptation is to just ask one of the well known good<br>
    scribes before the meeting in order not to waste time in a tight
    agenda.<br>
    <br>
    Stewart<br>
    <br>
    <br>
  </body>
</html>

--------------000106070309020705020409--

From iad@ietf.org  Mon Apr 22 03:30:36 2013
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 445E821E8045; Mon, 22 Apr 2013 03:30:31 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EmbgQZBsd7ko; Mon, 22 Apr 2013 03:30:28 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A28C21F8EB1; Mon, 22 Apr 2013 03:30:25 -0700 (PDT)
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: IAOC Announces Meeting Registration Gender Data Gathering Decision
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p3
Message-ID: <20130422103024.15473.141.idtracker@ietfa.amsl.com>
Date: Mon, 22 Apr 2013 03:30:24 -0700
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: Mon, 22 Apr 2013 10:30:36 -0000

On 11 April the IAOC announced that it was considering asking for =

gender information during the IETF meeting registration process =

starting with IETF 87, and asked for the community to provide feedback =

by 17 April as the IAOC planned to make a decision on 18 April.

The data is being gathered to benchmark and track gender participation =

at IETF meetings currently, over time, and to inform IETF diversity =

initiatives should any be undertaken.

The IAOC appreciates the feedback provided directly and the thoughtful =

discussion on the list.

After considering the feedback from the community and counsel, the =

IAOC approved the collection of gender data on the IETF meeting =

registration form.

A question about gender will be added to the registration form =

starting with the Berlin meeting (IETF 87).

Answering the gender question will of course be optional and the =

gender data will not be associated with individual registration =

records and only retained and reported in aggregate form.

Thanks again for your input.

Bob Hinden
Chair

From l.wood@surrey.ac.uk  Mon Apr 22 05:12:35 2013
Return-Path: <l.wood@surrey.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 236CD21F8F38 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 05:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.765
X-Spam-Level: 
X-Spam-Status: No, score=-3.765 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ePm7QtHtaa2F for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 05:12:34 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.174]) by ietfa.amsl.com (Postfix) with ESMTP id 0226021F8F2F for <ietf@ietf.org>; Mon, 22 Apr 2013 05:12:33 -0700 (PDT)
Received: from [195.245.230.131:52144] by server-14.bemta-3.messagelabs.com id 27/1D-27076-03925715; Mon, 22 Apr 2013 12:12:32 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-78.messagelabs.com!1366632752!31772633!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24688 invoked from network); 22 Apr 2013 12:12:32 -0000
Received: from unknown (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-6.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 22 Apr 2013 12:12:32 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Mon, 22 Apr 2013 13:12:31 +0100
From: <l.wood@surrey.ac.uk>
To: <ynir@checkpoint.com>
Date: Mon, 22 Apr 2013 13:12:31 +0100
Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOO6uAkYNXJKWRyEmIKVS5GuPId5jbdJGAgAAIsICAAEJXWoAARRgggAEyZAD//9h6AIAFHIg1
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E7F@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>, <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E6C@EXMB01CMS.surrey.ac.uk>, <4613980CFC78314ABFD7F85CC302772111A0F977@IL-EX10.ad.checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E70@EXMB01CMS.surrey.ac.uk>, <E49D2A72-8E1F-472E-B0CC-EF00E86AE526@checkpoint.com>
In-Reply-To: <E49D2A72-8E1F-472E-B0CC-EF00E86AE526@checkpoint.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 22 Apr 2013 12:12:35 -0000

And the technology that my team is pushing would be Saratoga:
http://saratoga.sf.net
which has interoperable implementations that can do 50Mbps in perl, a decad=
e of operational experience in its application domain, and mature drafts.

But this is in the transport area, and TSV has somewhat limited resources, =
so it's outside the span of attention from a wg. But still worth documentin=
g as experimental.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: Yoav Nir [ynir@checkpoint.com]
Sent: 19 April 2013 10:02
To: Wood L  Dr (Electronic Eng)
Cc: <worley@ariadne.com>; <ietf@ietf.org>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG=
     Review)

Only that you know enough people so that you could push a new technology ev=
en without attending, although you would need to collaborate with some peop=
le who do go. But pushing a new technology requires team building anyway.

The same should apply to other non-attenders who have gained some reputatio=
n.


On Apr 19, 2013, at 11:23 AM, l.wood@surrey.ac.uk wrote:

>
> and the point of your ad-hominem argument is what, exactly?
>
> Lloyd Wood
> http://sat-net.com/L.Wood/publications/internet-drafts
>
>
> ________________________________________
> From: Yoav Nir [ynir@checkpoint.com]
> Sent: 18 April 2013 15:18
> To: Wood L  Dr (Electronic Eng)
> Cc: worley@ariadne.com; ietf@ietf.org
> Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IE=
SG     Review)
>
> Looking in Jari's statistics site, you have three RFCs. One of those has =
several co-authors that I recognize as current "goers". You also have a cur=
rent draft with several co-authors, but I have no idea whether they're "goe=
rs" or not. Anyway, you are not a hermit. Through the RFCs and drafts that =
you have co-authored, you know people who do attend.


From kathleen.moriarty@emc.com  Mon Apr 22 06:05:03 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1302F21F8F9D for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 06:05:03 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QP9PJotT45u for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 06:05:02 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4A13A21F8F70 for <ietf@ietf.org>; Mon, 22 Apr 2013 06:05:02 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3MD4ti1012978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Apr 2013 09:04:56 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 22 Apr 2013 09:04:41 -0400
Received: from mxhub07.corp.emc.com (mxhub07.corp.emc.com [128.222.70.204]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3MD4cNq030542; Mon, 22 Apr 2013 09:04:40 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub07.corp.emc.com ([128.222.70.204]) with mapi; Mon, 22 Apr 2013 09:04:40 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 22 Apr 2013 09:04:40 -0400
Subject: RE: Meritocracy, diversity, and leaning on the people you know
Thread-Topic: Meritocracy, diversity, and leaning on the people you know
Thread-Index: Ac4/QPjlFKGfVTC9QUC/Smk3enFE6QAGAKjA
Message-ID: <F5063677821E3B4F81ACFB7905573F24DAA99272@MX15A.corp.emc.com>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com> <51750B36.2030404@cisco.com>
In-Reply-To: <51750B36.2030404@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F5063677821E3B4F81ACFB7905573F24DAA99272MX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 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: Mon, 22 Apr 2013 13:05:03 -0000

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

Being a scribe can be a good way for people to know who you are (the scribe=
).  From reading the thread on this, when you ask someone who is new, how a=
bout having them sit next to someone who is more familiar with the attendee=
s to help with names?   Maybe for those which English is not a first langua=
ge, they could monitor the jabber list for questions.  They may be more com=
fortable with certain aspects of volunteering during a session or reading d=
rafts on their own time.

It would be good to get the message out to newcomers that volunteering is i=
mportant.  You help others and they help you, it is basic networking skills=
 and does work in the IETF.

Thanks,
Kathleen

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ste=
wart Bryant
Sent: Monday, April 22, 2013 6:05 AM
To: Ted Hardie
Cc: IETF
Subject: Re: Meritocracy, diversity, and leaning on the people you know

On 19/04/2013 19:13, Ted Hardie wrote:
As a working group chair, when I stare out at a sea of faces looking for a =
scribe, the chances of my asking someone I know produces good minutes is mu=
ch higher than my asking someone whose work I don't know.
Think about how this often works in WGs without a
secretary or regular scribe.

Chair says we need a volunteer for a scribe.

Everyone looks away and sits on their hands.

Chair says no scribe, no meeting.

Everyone looks away and hangs their head even lower melting into the floor.

Chair pleads a bit more.

Silence.

Chair asks someone they know since they are less likely to refuse.

There maybe a refusal or two by people who expect to be at the
mic a lot, or need to leave early, or are only there to catch up
with their email.

Eventually someone committed to the WG, and usually well known to the
chairs, frequently a name called by the chair, offers to scribe in order
to the meeting started.

The strong temptation is to just ask one of the well known good
scribes before the meeting in order not to waste time in a tight agenda.

Stewart


--_000_F5063677821E3B4F81ACFB7905573F24DAA99272MX15Acorpemccom_
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=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (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";
	color:black;}
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 bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>Being a scribe can be a good way for people to know who you are (the=
 scribe).&nbsp; From reading the thread on this, when you ask someone who i=
s new, how about having them sit next to someone who is more familiar with =
the attendees to help with names? &nbsp;&nbsp;Maybe for those which English=
 is not a first language, they could monitor the jabber list for questions.=
&nbsp; They may be more comfortable with certain aspects of volunteering du=
ring a session or reading drafts on their own time.<o:p></o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>It would be good to get the message out to newcomers that volunteeri=
ng is important.&nbsp; You help others and they help you, it is basic netwo=
rking skills and does work in the IETF.&nbsp; <o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Kathleen<o:p></o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";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=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-famil=
y:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style=3D'fo=
nt-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> ietf-bo=
unces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of </b>Stewart B=
ryant<br><b>Sent:</b> Monday, April 22, 2013 6:05 AM<br><b>To:</b> Ted Hard=
ie<br><b>Cc:</b> IETF<br><b>Subject:</b> Re: Meritocracy, diversity, and le=
aning on the people you know<o:p></o:p></span></p></div></div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On 19/04/2013 19:13,=
 Ted Hardie wrote:<o:p></o:p></p></div><blockquote style=3D'margin-top:5.0p=
t;margin-bottom:5.0pt'><p class=3DMsoNormal>As a working group chair, when =
I stare out at a sea of faces looking for a scribe, the chances of my askin=
g someone I know produces good minutes is much higher than my asking someon=
e whose work I don't know.&nbsp; <o:p></o:p></p></blockquote><p class=3DMso=
Normal style=3D'margin-bottom:12.0pt'>Think about how this often works in W=
Gs without a <br>secretary or regular scribe.<br><br>Chair says we need a v=
olunteer for a scribe.<br><br>Everyone looks away and sits on their hands.<=
br><br>Chair says no scribe, no meeting.<br><br>Everyone looks away and han=
gs their head even lower melting into the floor.<br><br>Chair pleads a bit =
more.<br><br>Silence.<br><br>Chair asks someone they know since they are le=
ss likely to refuse. <br><br>There maybe a refusal or two by people who exp=
ect to be at the <br>mic a lot, or need to leave early, or are only there t=
o catch up <br>with their email.<br><br>Eventually someone committed to the=
 WG, and usually well known to the <br>chairs, frequently a name called by =
the chair, offers to scribe in order <br>to the meeting started.<br><br>The=
 strong temptation is to just ask one of the well known good<br>scribes bef=
ore the meeting in order not to waste time in a tight agenda.<br><br>Stewar=
t<br><br><o:p></o:p></p></div></body></html>=

--_000_F5063677821E3B4F81ACFB7905573F24DAA99272MX15Acorpemccom_--

From rja.lists@gmail.com  Mon Apr 22 06:34:30 2013
Return-Path: <rja.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 2347F21F85EB; Mon, 22 Apr 2013 06:34:30 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWOLa8nslCuq; Mon, 22 Apr 2013 06:34:29 -0700 (PDT)
Received: from mail-qe0-f44.google.com (mail-qe0-f44.google.com [209.85.128.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1823421F85DB; Mon, 22 Apr 2013 06:34:29 -0700 (PDT)
Received: by mail-qe0-f44.google.com with SMTP id w7so677079qeb.17 for <multiple recipients>; Mon, 22 Apr 2013 06:34:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:content-transfer-encoding:date:subject :to:message-id:mime-version:x-mailer; bh=1fmZLISU/2RbJBp90NokR6hruDQFJCVLgEYkCYgfPaE=; b=rj2sFocu6QagHrBYaHOjVyNAEtjQn1+hxsPYrAgEGJHzeWdnXa3PJojUFIW1K6ScKT GZvG5eqUtuX+RL0vBuQorIlLEIpwfXnYEErknBzcoQR0JcsRKkPbhqNQa2LhXlAMs1ar v5rW5Dvuv2/HUL5QVX7SVf2HnlvIKGVfU5pow5zUfKwIJnKdQf2h0JuiBS5fMKv58sZp D3GLS2l5fihxjtJ/S4DpkU4E6z6GlUrnaM9fh1Y5IFd1v+gjLmOqdPe+glV2u5FbG9vt oKkmIyNJgl7C8UQ+3eJ/5PDihB9/zjisZHXPuFxm7pyk5A7LA5sMRDic6BMH8F6I8I4S DLEA==
X-Received: by 10.224.11.200 with SMTP id u8mr22390522qau.76.1366637668604; Mon, 22 Apr 2013 06:34:28 -0700 (PDT)
Received: from [10.30.20.15] (pool-96-255-149-117.washdc.fios.verizon.net. [96.255.149.117]) by mx.google.com with ESMTPS id 10sm28246390qax.13.2013.04.22.06.34.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Apr 2013 06:34:28 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Apr 2013 09:34:26 -0400
Subject: last call comments for draft-ietf-6man-stable-privacy-addresses-06
To: ipv6@ietf.org, ietf@ietf.org
Message-Id: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Apr 2013 13:34:30 -0000

Earlier, Eliot Lear wrote:
% Put simply, you are over-specifying the RID=20
% and derive no benefit from doing so.

There is benefit to implementers in having a specific
example that is known to meet the requirements of
this specification.  This benefit also accrues to users,
as implementers are more likely to correctly implement
when giving a specific example that they may reuse.


% Also, the following text in section 3 Page 7 is contorted:
%
%> This means that this document does not formally obsolete or
%> deprecate any of the existing algorithms to generate Interface IDs
%> (e.g. such as that specified in [RFC2464]).=C2 However, those IPv6
%> implementations that employ this specification must generate all
%> of their "stable" addresses as specified in this document.
%
% My suggestion is to simplify remove it as it is self-evident.

It would reduce consensus within the WG and the IETF as a whole
to remove that text -- as it clarifies that other mechanisms for
generating such IDs are not affected by this specification.

Text to this effect was specifically requested by various WG=20
participants, precisely because it is not "self-evident" and=20
instead was confusing.

% Finally, this algorithm requires that the resultant host=20
% portion be 64 bits.  Is that necessary?

Yes, it is required, for technical reasons relating to multiple
IPv6-related standards-track RFCs.


I oppose Eliot's proposed edits on grounds that they would
reduce the clarity of the specification and also would
reduce IETF and WG consensus about this specification.


Yours,

Ran



From hartmans@mit.edu  Mon Apr 22 06:57:03 2013
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 7248611E80A5; Mon, 22 Apr 2013 06:57:03 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Pv7CpKQ0cgO; Mon, 22 Apr 2013 06:57:02 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 41D9B11E809C; Mon, 22 Apr 2013 06:57:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id C971E20218; Mon, 22 Apr 2013 09:55:10 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A9CT_VbNWm-M; Mon, 22 Apr 2013 09:55:10 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 22 Apr 2013 09:55:10 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2AD8F4499; Mon, 22 Apr 2013 09:56:59 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com>
Date: Mon, 22 Apr 2013 09:56:59 -0400
In-Reply-To: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> (RJ Atkinson's message of "Mon, 22 Apr 2013 09:34:26 -0400")
Message-ID: <tslzjwqoehg.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: ipv6@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, 22 Apr 2013 13:57:03 -0000

>>>>> "RJ" == RJ Atkinson <rja.lists@gmail.com> writes:


    RJ> I oppose Eliot's proposed edits on grounds that they would
    RJ> reduce the clarity of the specification and also would reduce
    RJ> IETF and WG consensus about this specification.

Ran,  I just checked, and you don't seem to be a 6man chair. We
generally ask chairs, not involved participants to judge WG consensus
and ADs to judge IETF consensus.

So, I think  what you're saying boils down to you disagree with Eliot
because you believe his comments would reduce clarity. You believe
others within the WG and outside the WG are likely to agree with you.
That's all fine and is valuable to contribute.

However, I don't think it promotes open and honest technical discussion
when participants try to call consensus. 
Thanks for considering my input.

From framefritti@gmail.com  Mon Apr 22 06:59:43 2013
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 AD87421E8089 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 06:59:43 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKOIzzf1W9rM for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 06:59:43 -0700 (PDT)
Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) by ietfa.amsl.com (Postfix) with ESMTP id B9D1621E803D for <ietf@ietf.org>; Mon, 22 Apr 2013 06:59:42 -0700 (PDT)
Received: by mail-lb0-f180.google.com with SMTP id t11so5582786lbi.25 for <ietf@ietf.org>; Mon, 22 Apr 2013 06:59:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=8EJjwM5V5cijod6TQOSbfGiytbCB2ZM8+z/wV3uV2HA=; b=yEk7uh7sj93MEAVNdJ7GSTZ8Z47leVEPqgMG0z73ES8tSe8oS6A3y9lbZUQcAXYlQt jPQvvYzITgUhbhx7zEJvIx47zDS89N755WDTMzI7QpSCebDM2cBEwaU6t8G9H/KWUGGF c7Qmt+9lwT57+22v+f6zdY2SeIeUzO47/dPD2LESMcqpIN0pPsqNas0vDqy/iRW3p69t RTXDlIh7PfYJaZ5C23G0PzDVdfXOkbY+A7SV2l+FN+sD+i+oIElGsq2lYF3/FgGh/eE/ +x6PSZE9cxd12kxmQd8e2deefYzR1bwTblb99msITjoCzfHXdgXsUPi9Mc5W3r1by9h2 IvAw==
MIME-Version: 1.0
X-Received: by 10.112.129.137 with SMTP id nw9mr13454481lbb.56.1366639181330;  Mon, 22 Apr 2013 06:59:41 -0700 (PDT)
Received: by 10.112.9.5 with HTTP; Mon, 22 Apr 2013 06:59:41 -0700 (PDT)
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24DAA99272@MX15A.corp.emc.com>
References: <CA+9kkMDSdAm_9XEi29aKczmkOC1pNykHe5Gj9TtE9hv5o2NByg@mail.gmail.com> <51750B36.2030404@cisco.com> <F5063677821E3B4F81ACFB7905573F24DAA99272@MX15A.corp.emc.com>
Date: Mon, 22 Apr 2013 15:59:41 +0200
Message-ID: <CABSMSPU-YB3+J5x6vjLxoaVvWxp=EyGbQUifhNdOnez2G+PLHA@mail.gmail.com>
Subject: Re: Meritocracy, diversity, and leaning on the people you know
From: Riccardo Bernardini <framefritti@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: Mon, 22 Apr 2013 13:59:43 -0000

On Mon, Apr 22, 2013 at 3:04 PM, Moriarty, Kathleen
<kathleen.moriarty@emc.com> wrote:
> Being a scribe can be a good way for people to know who you are (the
> scribe).  From reading the thread on this, when you ask someone who is new,
> how about having them sit next to someone who is more familiar with the
> attendees to help with names?   Maybe for those which English is not a first
> language, they could monitor the jabber list for questions.  They may be
> more comfortable with certain aspects of volunteering during a session or
> reading drafts on their own time.
>
>
>
> It would be good to get the message out to newcomers that volunteering is
> important.  You help others and they help you, it is basic networking skills
> and does work in the IETF.
>

I support this.  Maybe some encouragement from the chair could help
the newcomers in winning their natural "shyness."  I talk by personal
experience here: maybe my shyness is a bit above average, but I think
that when it is your first time in a new environment, it is only
natural to be a little afraid of doing something wrong, even in
something like IETF that I, as newcomer, found quite "welcoming."
Adding the "pseudo-mentor" to the scribe could also help and maybe
also having two newcomer-scribes in parallel, so that each one knows
that if s/he misses something or gets something wrong, the redundant
scribe can be used to recover from the error.

>
>
> Thanks,
>
> Kathleen
>
>
>
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Stewart Bryant
> Sent: Monday, April 22, 2013 6:05 AM
> To: Ted Hardie
> Cc: IETF
> Subject: Re: Meritocracy, diversity, and leaning on the people you know
>
>
>
> On 19/04/2013 19:13, Ted Hardie wrote:
>
> As a working group chair, when I stare out at a sea of faces looking for a
> scribe, the chances of my asking someone I know produces good minutes is
> much higher than my asking someone whose work I don't know.
>
> Think about how this often works in WGs without a
> secretary or regular scribe.
>
> Chair says we need a volunteer for a scribe.
>
> Everyone looks away and sits on their hands.
>
> Chair says no scribe, no meeting.
>
> Everyone looks away and hangs their head even lower melting into the floor.
>
> Chair pleads a bit more.
>
> Silence.
>
> Chair asks someone they know since they are less likely to refuse.
>
> There maybe a refusal or two by people who expect to be at the
> mic a lot, or need to leave early, or are only there to catch up
> with their email.
>
> Eventually someone committed to the WG, and usually well known to the
> chairs, frequently a name called by the chair, offers to scribe in order
> to the meeting started.
>
> The strong temptation is to just ask one of the well known good
> scribes before the meeting in order not to waste time in a tight agenda.
>
> Stewart
>

From salvatore.dantonio@uniparthenope.it  Sat Apr 20 17:06:26 2013
Return-Path: <salvatore.dantonio@uniparthenope.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 57DB221F8A00; Sat, 20 Apr 2013 17:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.035
X-Spam-Level: ****
X-Spam-Status: No, score=4.035 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, MSGID_MULTIPLE_AT=1.449, RCVD_ILLEGAL_IP=1.908]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUw3hRp9HRmG; Sat, 20 Apr 2013 17:06:24 -0700 (PDT)
Received: from mail.uniparthenope.it (mail.uniparthenope.it [192.167.9.244]) by ietfa.amsl.com (Postfix) with ESMTP id B657E21F888F; Sat, 20 Apr 2013 17:06:23 -0700 (PDT)
Received: from mail2.uniparthenope.it (unknown [10.1.2.108]) by mail.uniparthenope.it (Postfix) with SMTP id D0D4F42536; Sun, 21 Apr 2013 00:06:22 +0000 (UTC)
Received: from (unknown [192.168.241.108]) by mail2.uniparthenope.it with smtp id 1da8_4bd40ed6_aa17_11e2_9101_001372515a5c; Sun, 21 Apr 2013 02:06:21 +0200
Received: from spamk.uniparthenope.it (localhost [127.0.0.1]) by spamk.uniparthenope.it (Postfix) with ESMTP id 781BFC432C; Sun, 21 Apr 2013 02:06:20 +0200 (CEST)
Received: by spamk.uniparthenope.it (Postfix, from userid 500) id 5D40EC4351; Sun, 21 Apr 2013 02:06:20 +0200 (CEST)
Received: from mail.uniparthenope.it (unknown [192.168.241.109]) by spamk.uniparthenope.it (Postfix) with ESMTP id B34CAC4377; Sun, 21 Apr 2013 02:06:13 +0200 (CEST)
Received: by mail.uniparthenope.it (Postfix, from userid 108) id 9DFC0421AD; Sun, 21 Apr 2013 02:06:13 +0200 (CEST)
Received: from saldantoPC (unknown [2.237.123.176]) (Authenticated sender: salvatore.dantonio@uniparthenope.it) by mail.uniparthenope.it (Postfix) with ESMTPA id ABE80421AD; Sun, 21 Apr 2013 02:06:11 +0200 (CEST)
From: "Salvatore D'Antonio" <salvatore.dantonio@uniparthenope.it>
To: "'Benoit Claise'" <bclaise@cisco.com>
References: <20130401072846.32360.9502.idtracker@ietfa.amsl.com> <5162C44B.5030904@cisco.com> <005701ce3538$8f0b3480$ad219d80$@dantonio@uniparthenope.it> <516BCB97.9040404@cisco.com>
In-Reply-To: <516BCB97.9040404@cisco.com>
Date: Sun, 21 Apr 2013 02:06:14 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac45veJiRHrdfH9cTm69S7sEnZNliAEY1GBQ
Content-Language: it
Message-ID: <001001ce3e24$0a931840$1fb948c0$@dantonio@uniparthenope.it>
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01CE3E34.CE1BE840"
Subject: R: R: Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.42/RELEASE, bases: 20130420 #9915320, check: 20130421 clean
X-Mailman-Approved-At: Mon, 22 Apr 2013 07:00:57 -0700
Cc: rahulp@cisco.com, 'IETF discussion list' <ietf@ietf.org>, draft-ietf-ipfix-flow-selection-tech@tools.ietf.org, apps-discuss@ietf.org, 'General Area Review Team' <gen-art@ietf.org>, 'S Moonesamy' <sm+ietf@elandsys.com>, ipfix-chairs@tools.ietf.org, ipfix@ietf.org, iesg@ietf.org, "'A. Jean Mahoney'" <mahoney@nostrum.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, 21 Apr 2013 00:06:26 -0000

Messaggio multipart in formato MIME.

------=_NextPart_000_0011_01CE3E34.CE1BE840
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Dear Benoit, all

=20

I submitted v16 of the Internet Draft.

=20

I modified section 9.1.1 on the maintenance of the flowSelectorAlgorithm =
registry and fixed the editorial issue in section  6.1.1

=20

I have also used MUST in section 6.1

=20

Best regards,

=20

Salvatore

=20

=20

Da: Benoit Claise [mailto:bclaise@cisco.com]=20
Inviato: luned=C3=AC 15 aprile 2013 11:43
A: Salvatore D'Antonio
Cc: draft-ietf-ipfix-flow-selection-tech@tools.ietf.org; =
ipfix-chairs@tools.ietf.org; 'S Moonesamy'; apps-discuss@ietf.org; =
iesg@ietf.org; 'Joel M. Halpern'; 'A. Jean Mahoney'; 'General Area =
Review Team'; 'IETF discussion list'; rahulp@cisco.com; ipfix@ietf.org
Oggetto: Re: R: Last Call Expired: =
<draft-ietf-ipfix-flow-selection-tech-14.txt>

=20

Salvatore

Dear all,

=20

A new version of the Internet Draft on Flow Selection Techniques has =
been submitted. It contains the following changes:

-          A new section illustrating the difference between =
Intermediate Flow Selection Process and Intermediate Selection Process =
has been added,

-          The sentence "In order to be compliant with this document, at =
least the Property  Match Filtering MUST be implemented." has been =
removed in Section 1,

-          =E2=80=9CMUST=E2=80=9D has been replaced with =
=E2=80=9CSHOULD=E2=80=9D in Section 5.1,

Actually, the feedback was:

In Section 1:=20

  "In order to be compliant with this document, at least the Property=20
   Match Filtering MUST be implemented."=20

The above text is repeated in Section 5.1.  I suggest removing this =
sentence as it does not seem related to scope.=20

My reading of the "MUST" is that it is being used for compliance instead =
of the reasons described in RFC 2119.  I suggest reviewing the usage of =
RFC 2119 key words in Section 5.1.=20

So the solution is not to change MUST to SHOULD.
The question is whether "MUST" versus "must" must be used.
I understand the concern. For compliance reason with the PSAMP RFC 5475 =
(which is closely related) ...


 <http://tools.ietf.org/html/rfc5475#section-7> 7.  Parameters for the =
Description of Selection Techniques

   This section gives an overview of different alternative selection
   schemes and their required parameters.  In order to be compliant with
   PSAMP, at least one of proposed schemes MUST be implemented.
=20

... I would keep the initial "MUST" from the previous draft version.=20

-          =E2=80=9CThe flowSelectorAlgorithm registry is maintained by =
IANA." has been replaced with =E2=80=9CIANA is requested to create the =
flowSelectorAlgorithm registry.=E2=80=9D

-          The sentence "The registry can be updated when specifications =
of the new  technique(s) and any new Information Elements are provided." =
has been removed since it did not clarify how the registry will be =
managed.

-           Section 6.1.1 =E2=80=9CProperty Match Filtering=E2=80=9D has =
been changed by adding some text on how Property Match Filtering can be  =
used by an Intermediate Flow Selection Process in the Metering Process, =
in the  Exporting Process and within an IPFIX Mediator.

When publishing a new version, please correct this editorial issue.

 " ... and Flow duration. in
   the An example is the selection of the largest ..."





=20

Best regards,

=20

Salvatore

=20

Da: Benoit Claise [mailto:bclaise@cisco.com]=20
Inviato: luned=C3=AC 8 aprile 2013 15:21
A: draft-ietf-ipfix-flow-selection-tech@tools.ietf.org
Cc: ipfix-chairs@tools.ietf.org
Oggetto: Fwd: Last Call Expired: =
<draft-ietf-ipfix-flow-selection-tech-14.txt>

=20

Dear authors,

The IETF last call has finished.
Can you please update your draft based on the feedback received.
Then I will progress it.

Regards, Benoit



-------- Original Message --------=20


Subject:=20

Last Call Expired: <draft-ietf-ipfix-flow-selection-tech-14.txt>


Date:=20

Mon, 01 Apr 2013 00:28:46 -0700


From:=20

DraftTracker Mail System  <mailto:iesg-secretary@ietf.org> =
<iesg-secretary@ietf.org>


To:=20

iesg@ietf.org, ipfix-chairs@tools.ietf.org, =
draft-ietf-ipfix-flow-selection-tech@tools.ietf.org


CC:=20

iesg-secretary@ietf.org

=20

Please DO NOT reply to this email.
=20
I-D: <draft-ietf-ipfix-flow-selection-tech-14.txt>
ID Tracker URL: =
http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tech/
=20
IETF Last Call has ended, and the state has been changed to
Waiting for AD Go-Ahead.
=20
=20
=20

=20

=20

  _____ =20

Nessun virus nel messaggio.
Controllato da AVG - www.avg.com
Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di =
rilascio: 07/04/2013





*************************************************************************=
******************************

IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO

=20

Il 5 per mille all'Universit=C3=A0 degli Studi di Napoli =
"Parthenope"incrementa le borse di studio agli studenti - codice fiscale =
80018240632=20

 <http://www.uniparthenope.it/index.php/5xmille> =
http://www.uniparthenope.it/index.php/5xmille=20

=20

 =
<http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-p=
arthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-d=
el-5-per-mille> =
http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-pa=
rthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-de=
l-5-per-mille

=20
Questa informativa =C3=A8 inserita in automatico dal sistema al fine =
esclusivo della realizzazione dei fini istituzionali dell'ente.

=20






*************************************************************************=
******************************

IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO

=20

Il 5 per mille all'Universit=C3=A0 degli Studi di Napoli =
"Parthenope"incrementa le borse di studio agli studenti - codice fiscale =
80018240632=20

 <http://www.uniparthenope.it/index.php/5xmille> =
http://www.uniparthenope.it/index.php/5xmille=20

=20

 =
<http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-p=
arthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-d=
el-5-per-mille> =
http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-pa=
rthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-de=
l-5-per-mille

=20
Questa informativa =C3=A8 inserita in automatico dal sistema al fine =
esclusivo della realizzazione dei fini istituzionali dell'ente.

=20

=20

=20


******************************************************************************=09=0A
IL MERITO DEGLI STUDENTI VIENE RICONOSCIUTO=0A
 =0A
Il 5 per mille all'Universita' degli Studi di Napoli "Parthenope" incrementa le borse di studio agli studenti - codice fiscale 80018240632=0A
http://www.uniparthenope.it/index.php/5xmille =0A
 =0A
http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille=0A
 =0A
Questa informativa e' inserita in automatico dal sistema al fine esclusivo della realizzazione dei fini istituzionali dell'ente.=0A

------=_NextPart_000_0011_01CE3E34.CE1BE840
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-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=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
h2
	{mso-style-priority:9;
	mso-style-link:"Titolo 2 Carattere";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:18.0pt;
	font-family:"Times New Roman","serif";
	color:black;
	font-weight:bold;}
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;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	margin-bottom:5.95pt;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"Preformattato HTML Carattere";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.PreformattatoHTMLCarattere
	{mso-style-name:"Preformattato HTML Carattere";
	mso-style-priority:99;
	mso-style-link:"Preformattato HTML";
	font-family:Consolas;
	color:black;}
span.StileMessaggioDiPostaElettronica20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.h2
	{mso-style-name:h2;}
span.Titolo2Carattere
	{mso-style-name:"Titolo 2 Carattere";
	mso-style-priority:9;
	mso-style-link:"Titolo 2";
	font-family:"Cambria","serif";
	color:#4F81BD;
	font-weight:bold;}
p.western, li.western, div.western
	{mso-style-name:western;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	margin-bottom:5.95pt;
	margin-left:0cm;
	font-size:8.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
p.cjk, li.cjk, div.cjk
	{mso-style-name:cjk;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	margin-bottom:5.95pt;
	margin-left:0cm;
	font-size:8.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
p.ctl, li.ctl, div.ctl
	{mso-style-name:ctl;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	margin-bottom:5.95pt;
	margin-left:0cm;
	font-size:8.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
span.StileMessaggioDiPostaElettronica27
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:217212090;
	mso-list-type:hybrid;
	mso-list-template-ids:308057158 -1513439274 134807555 134807557 =
134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</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 bgcolor=3Dwhite lang=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dear Benoit, all<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I submitted v16 of the Internet =
Draft.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I modified section 9.1.1 on the maintenance of the =
flowSelectorAlgorithm
registry and fixed the editorial issue in section =
=C2=A06.1.1<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have also used MUST in section =
6.1<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Salvatore<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DIT =
style=3D'font-size:10.0pt;font-family:"Segoe UI","sans-serif";
color:windowtext'>Da:</span></b><span lang=3DIT =
style=3D'font-size:10.0pt;
font-family:"Segoe UI","sans-serif";color:windowtext'> Benoit Claise
[mailto:bclaise@cisco.com] <br>
<b>Inviato:</b> luned=C3=AC 15 aprile 2013 11:43<br>
<b>A:</b> Salvatore D'Antonio<br>
<b>Cc:</b> draft-ietf-ipfix-flow-selection-tech@tools.ietf.org;
ipfix-chairs@tools.ietf.org; 'S Moonesamy'; apps-discuss@ietf.org;
iesg@ietf.org; 'Joel M. Halpern'; 'A. Jean Mahoney'; 'General Area =
Review
Team'; 'IETF discussion list'; rahulp@cisco.com; ipfix@ietf.org<br>
<b>Oggetto:</b> Re: R: Last Call Expired:
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></span></p>=


</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=3DMsoNormal>Salvatore<o:p></o:p></p>

</div>

<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Dear all,</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A new version of the Internet Draft on Flow Selection =
Techniques
has been submitted. It contains the following =
changes:</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>A new section illustrating the difference between =
Intermediate Flow
Selection Process and Intermediate Selection Process has been =
added,</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The sentence &quot;In order to be compliant with this =
document,
at least the Property &nbsp;Match Filtering MUST be implemented.&quot; =
has been
removed in Section 1,</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=E2=80=9CMUST=E2=80=9D has been replaced with =
=E2=80=9CSHOULD=E2=80=9D in Section 5.1,</span><o:p></o:p></p>

</blockquote>

<p class=3DMsoNormal>Actually, the feedback was:<o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>In Section 1: <br>
<br>
&nbsp; &quot;In order to be compliant with this document, at least the =
Property
<br>
&nbsp;&nbsp; Match Filtering MUST be implemented.&quot; <br>
<br>
The above text is repeated in Section 5.1.&nbsp; I suggest removing this =
sentence
as it does not seem related to scope. <br>
<br>
My reading of the &quot;MUST&quot; is that it is being used for =
compliance
instead of the reasons described in RFC 2119.&nbsp; I suggest reviewing =
the
usage of RFC 2119 key words in Section 5.1. <o:p></o:p></p>

<p class=3DMsoNormal>So the solution is not to change MUST to =
SHOULD.<br>
The question is whether &quot;MUST&quot; versus &quot;must&quot; must be =
used.<br>
I understand the concern. For compliance reason with the PSAMP RFC 5475 =
(which
is closely related) ...<o:p></o:p></p>

<h2><a name=3Dsection-7></a><a =
href=3D"http://tools.ietf.org/html/rfc5475#section-7"><span
style=3D'font-family:"Courier New"'>7</span></a><span =
style=3D'font-family:"Courier New"'>.=C2=A0
Parameters for the Description of Selection =
Techniques<o:p></o:p></span></h2>

<pre>=C2=A0=C2=A0 This section gives an overview of different =
alternative selection<o:p></o:p></pre><pre>=C2=A0=C2=A0 schemes and =
their required parameters.=C2=A0 In order to be compliant =
with<o:p></o:p></pre><pre>=C2=A0=C2=A0 PSAMP, at least one of proposed =
schemes MUST be =
implemented.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre>

<p class=3DMsoNormal>... I would keep the initial &quot;MUST&quot; from =
the
previous draft version. <o:p></o:p></p>

<blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=E2=80=9CThe flowSelectorAlgorithm registry is maintained =
by IANA.&quot;
has been replaced with =E2=80=9CIANA is requested to create the =
flowSelectorAlgorithm
registry.=E2=80=9D</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The sentence &quot;The registry can be updated when
specifications of the new&nbsp; technique(s) and any new Information =
Elements
are provided.&quot; has been removed since it did not clarify how the =
registry
will be managed.</span><o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 =
level1 lfo2'><![if !supportLists]><span
style=3D'font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>-<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;Section 6.1.1 =E2=80=9CProperty Match =
Filtering=E2=80=9D has been changed
by adding some text on how Property Match Filtering can be &nbsp;used by =
an
Intermediate Flow Selection Process in the Metering Process, in the
&nbsp;Exporting Process and within an IPFIX =
Mediator.</span><o:p></o:p></p>

</blockquote>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>When publishing a =
new version,
please correct this editorial issue.<o:p></o:p></p>

<pre>=C2=A0&quot; ... and Flow duration. =
in<o:p></o:p></pre><pre>=C2=A0=C2=A0 the An example is the selection of =
the largest ...&quot;<o:p></o:p></pre>

<p class=3DMsoNormal><br>
<br>
<o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Best regards,</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Salvatore</span><o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0cm 0cm 0cm'>

<p class=3DMsoNormal><b><span lang=3DIT =
style=3D'font-size:10.0pt'>Da:</span></b><span
lang=3DIT style=3D'font-size:10.0pt'> Benoit Claise [<a
href=3D"mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>] <br>
<b>Inviato:</b> luned=C3=AC 8 aprile 2013 15:21<br>
<b>A:</b> <a =
href=3D"mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft=
-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><br>
<b>Cc:</b> <a =
href=3D"mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</=
a><br>
<b>Oggetto:</b> Fwd: Last Call Expired: =
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;</span><o:p></o:p></p>=


</div>

</div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal>Dear authors,<br>
<br>
The IETF last call has finished.<br>
Can you please update your draft based on the feedback received.<br>
Then I will progress it.<br>
<br>
Regards, Benoit<o:p></o:p></p>

<div>

<p class=3DMsoNormal><br>
<br>
-------- Original Message -------- <o:p></o:p></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 =
cellpadding=3D0>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright =
style=3D'text-align:right'><b>Subject: </b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>Last Call Expired:
  &lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>Date: =
</b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>Mon, 01 Apr 2013 00:28:46 -0700<o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>From: =
</b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal>DraftTracker Mail System <a
  =
href=3D"mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</=
a><o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>To: =
</b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal><a =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>, <a
  =
href=3D"mailto:ipfix-chairs@tools.ietf.org">ipfix-chairs@tools.ietf.org</=
a>, <a
  =
href=3D"mailto:draft-ietf-ipfix-flow-selection-tech@tools.ietf.org">draft=
-ietf-ipfix-flow-selection-tech@tools.ietf.org</a><o:p></o:p></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal align=3Dright style=3D'text-align:right'><b>CC: =
</b><o:p></o:p></p>
  </td>
  <td style=3D'padding:0cm 0cm 0cm 0cm'>
  <p class=3DMsoNormal><a =
href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a><o:p><=
/o:p></p>
  </td>
 </tr>
</table>

<p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>&nbsp;<o:p></o:p></p>

<pre>Please DO NOT reply to this =
email.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>I-D: =
&lt;draft-ietf-ipfix-flow-selection-tech-14.txt&gt;<o:p></o:p></pre><pre>=
ID Tracker URL: <a
href=3D"http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-t=
ech/">http://datatracker.ietf.org/doc/draft-ietf-ipfix-flow-selection-tec=
h/</a><o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>IETF Last Call =
has ended, and the state has been changed =
to<o:p></o:p></pre><pre>Waiting for AD =
Go-Ahead.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>&nbsp;<o:p></o=
:p></pre><pre>&nbsp;<o:p></o:p></pre>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

</div>

<p class=3DMsoNormal>&nbsp;<o:p></o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'>

<hr size=3D1 width=3D"100%" noshade style=3D'color:#A0A0A0' =
align=3Dcenter>

</div>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Nessun
virus nel messaggio.<br>
Controllato da AVG - <a href=3D"http://www.avg.com">www.avg.com</a><br>
Versione: 2013.0.3272 / Database dei virus: 3162/6231 - Data di =
rilascio:
07/04/2013<o:p></o:p></p>

<p class=3DMsoNormal><br>
<br>
<o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>******************************=
*************************************************************************=
</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>IL MERITO DEGLI =
STUDENTI&nbsp;VIENE
RICONOSCIUTO</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>Il 5 per mille =
all'Universit=C3=A0 degli
Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli
studenti - codice fiscale <b>80018240632</b> </span><o:p></o:p></p>

<p class=3Dwestern style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><a
href=3D"http://www.uniparthenope.it/index.php/5xmille"><span =
style=3D'font-family:
"Arial","sans-serif"'>http://www.uniparthenope.it/index.php/5xmille</span=
></a><span
style=3D'font-family:"Arial","sans-serif"'>&nbsp;</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

<p class=3Dwestern style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><a
href=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/29=
43-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-pro=
venti-del-5-per-mille"><span
style=3D'font-family:"Arial","sans-serif"'>http://www.uniparthenope.it/in=
dex.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di=
-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</span></a><o:p><=
/o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<span
style=3D'font-family:"Arial","sans-serif"'><br>
Questa informativa =C3=A8 inserita in automatico dal sistema al fine =
esclusivo della
realizzazione dei fini istituzionali dell'ente.</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><br>
<br>
<br>
<o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>******************************=
*************************************************************************=
</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>IL MERITO DEGLI =
STUDENTI&nbsp;VIENE
RICONOSCIUTO</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><span
style=3D'font-family:"Arial","sans-serif"'>Il 5 per mille =
all'Universit=C3=A0 degli
Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli
studenti - codice fiscale <b>80018240632</b> </span><o:p></o:p></p>

<p class=3Dwestern style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><a
href=3D"http://www.uniparthenope.it/index.php/5xmille"><span =
style=3D'font-family:
"Arial","sans-serif"'>http://www.uniparthenope.it/index.php/5xmille</span=
></a><span
style=3D'font-family:"Arial","sans-serif"'>&nbsp;</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<o:p></o:p></p>

<p class=3Dwestern style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><a
href=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/29=
43-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-pro=
venti-del-5-per-mille"><span
style=3D'font-family:"Arial","sans-serif"'>http://www.uniparthenope.it/in=
dex.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di=
-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</span></a><o:p><=
/o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>&nbsp;<span
style=3D'font-family:"Arial","sans-serif"'><br>
Questa informativa =C3=A8 inserita in automatico dal sistema al fine =
esclusivo della
realizzazione dei fini istituzionali dell'ente.</span><o:p></o:p></p>

<p class=3Dwestern =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>


<br>=
<STYLE TYPE=3D"text/css">=0A
=09<!--=0A
=09=09@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }=0A
=09=09P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }=0A
=09=09P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }=0A
=09=09P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }=0A
=09=09P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }=0A
=09=09A:link { color: #0000ff }=0A
=09-->=0A
=09</STYLE>=0A
<!--</HEAD></BODY>-->=0A
<P LANG=3D"it-IT" TEXT=3D"#000000" LINK=3D"#0000ff" DIR=3D"LTR">=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">*******************************************************************************************************</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">IL=0A
MERITO DEGLI STUDENTI&nbsp;VIENE RICONOSCIUTO</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">Il=0A
5 per mille all'Universit&agrave degli Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli studenti=0A
- codice fiscale </FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif"><B>80018240632</B></FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">=0A
</FONT></FONT>=0A
</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/5xmille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/5xmille</U></FONT></FONT></A><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">&nbsp;</FONT></FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</U></FONT></FONT></A></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;<FONT FACE=3D"Arial, sans-serif"><BR>Questa=0A
informativa &egrave inserita in automatico dal sistema al fine esclusivo=0A
della realizzazione dei fini istituzionali dell&#39;ente.</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><BR>=0A
</P>=0A
<!--</BODY>-->=0A
<!--</HTML>-->=0A
<br>=
</body>

</html>

<br>=
<STYLE TYPE=3D"text/css">=0A
=09<!--=0A
=09=09@page { margin-left: 2cm; margin-right: 2cm; margin-top: 2.5cm; margin-bottom: 2cm }=0A
=09=09P { margin-bottom: 0.21cm; direction: ltr; color: #000000; widows: 2; orphans: 2 }=0A
=09=09P.western { font-family: "Times New Roman", serif; font-size: 8pt; so-language: it-IT }=0A
=09=09P.cjk { font-family: "Times New Roman", serif; font-size: 8pt }=0A
=09=09P.ctl { font-family: "Times New Roman", serif; font-size: 8pt; so-language: ar-SA }=0A
=09=09A:link { color: #0000ff }=0A
=09-->=0A
=09</STYLE>=0A
<!--</HEAD></BODY>-->=0A
<P LANG=3D"it-IT" TEXT=3D"#000000" LINK=3D"#0000ff" DIR=3D"LTR">=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">*******************************************************************************************************</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT FACE=3D"Arial, sans-serif">IL=0A
MERITO DEGLI STUDENTI&nbsp;VIENE RICONOSCIUTO</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">Il=0A
5 per mille all'Universit&agrave degli Studi di Napoli &quot;Parthenope&quot;incrementa le borse di studio agli studenti=0A
- codice fiscale </FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif"><B>80018240632</B></FONT></FONT><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">=0A
</FONT></FONT>=0A
</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/5xmille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/5xmille</U></FONT></FONT></A><FONT COLOR=3D"#000000"><FONT FACE=3D"Arial, sans-serif">&nbsp;</FONT></FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;</P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><A HREF=3D"http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille"><FONT COLOR=3D"#0000ff"><FONT FACE=3D"Arial, sans-serif"><U>http://www.uniparthenope.it/index.php/it/avvisi-sito-di-ateneo/2943-la-parthenope-premia-il-tuo-voto-di-diploma-ed-il-tuo-imegno-con-i-proventi-del-5-per-mille</U></FONT></FONT></A></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm">&nbsp;<FONT FACE=3D"Arial, sans-serif"><BR>Questa=0A
informativa &egrave inserita in automatico dal sistema al fine esclusivo=0A
della realizzazione dei fini istituzionali dell&#39;ente.</FONT></P>=0A
<P CLASS=3D"western" STYLE=3D"margin-bottom: 0cm"><BR>=0A
</P>=0A
<!--</BODY>-->=0A
<!--</HTML>-->=0A
<br>=
------=_NextPart_000_0011_01CE3E34.CE1BE840--

From w@1wt.eu  Sat Apr 20 00:25:36 2013
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79B9221F8F6C for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 00:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.321
X-Spam-Level: 
X-Spam-Status: No, score=-6.321 tagged_above=-999 required=5 tests=[AWL=-4.278, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xYuE36sK9un2 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 00:25:35 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 604FD21F8CDD for <ietf@ietf.org>; Sat, 20 Apr 2013 00:25:16 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id r3K7P9F1028716; Sat, 20 Apr 2013 09:25:09 +0200
Date: Sat, 20 Apr 2013 09:25:09 +0200
From: Willy Tarreau <w@1wt.eu>
To: ietf@ietf.org
Subject: Re: p1: Via and gateways
Message-ID: <20130420072509.GM26517@1wt.eu>
References: <F7810D5C-45A6-4D01-83ED-2A9AB5856813@mnot.net> <alpine.LRH.2.01.1304200017490.18732@egate.xpasc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LRH.2.01.1304200017490.18732@egate.xpasc.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Mon, 22 Apr 2013 07:01:21 -0700
Cc: ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Apr 2013 07:25:36 -0000

On Sat, Apr 20, 2013 at 12:21:52AM -0700, David Morris wrote:
> 
> 
> On Sat, 20 Apr 2013, Mark Nottingham wrote:
> 
> > 
> > p1 Section 2.3 says:
> > 
> > > However, an HTTP-to-HTTP gateway that wishes to interoperate with
> > > third-party HTTP servers must conform to HTTP user agent requirements
> > > on the gateway's inbound connection and must implement the Connection
> > > (Section 6.1) and Via (Section 5.7.1) header fields for both
> > > connections.
> > 
> > This means that accelerators and CDNs MUST generate a Via header on the
> > outbound connection. This isn't widely practiced, and I'm not sure it's
> > necessary. Comments?
> 
> I don't care about MUST, but I think the Via header can be useful for
> problem determination. A smart content server could also adjust for
> a detected accelerator and/or transcoder ... perhaps by avoiding
> optimizations dependant on a direct connection and byte/byte transfer
> between the client and the server.
> 
> So I'm very much in favor of keeping the Via: header.

OK but Mark is not discussing about removing it but keeping the MUST
since a number of existing products already don't add it and will not
for some of the reasons mentionned in this thread.

So I think that based on your feedback this MUST should be turned into
a SHOULD.

Willy


From w@1wt.eu  Sat Apr 20 01:09:29 2013
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 480ED21F848A for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 01:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.992
X-Spam-Level: 
X-Spam-Status: No, score=-5.992 tagged_above=-999 required=5 tests=[AWL=-3.949, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id suyWMgYXH-J1 for <ietf@ietfa.amsl.com>; Sat, 20 Apr 2013 01:09:28 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 68EC221F8481 for <ietf@ietf.org>; Sat, 20 Apr 2013 01:09:28 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id r3K89JUV028903; Sat, 20 Apr 2013 10:09:19 +0200
Date: Sat, 20 Apr 2013 10:09:19 +0200
From: Willy Tarreau <w@1wt.eu>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: p1: Via and gateways
Message-ID: <20130420080919.GP26517@1wt.eu>
References: <F7810D5C-45A6-4D01-83ED-2A9AB5856813@mnot.net> <alpine.LRH.2.01.1304200017490.18732@egate.xpasc.com> <37AD85F8-D0E1-4B9D-9BF0-99EBE83ADF8D@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <37AD85F8-D0E1-4B9D-9BF0-99EBE83ADF8D@mnot.net>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Mon, 22 Apr 2013 07:01:39 -0700
Cc: ietf@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Apr 2013 08:09:29 -0000

On Sat, Apr 20, 2013 at 05:55:59PM +1000, Mark Nottingham wrote:
> 
> On 20/04/2013, at 5:21 PM, David Morris <dwm@xpasc.com> wrote:
> > 
> > I don't care about MUST, but I think the Via header can be useful for
> > problem determination. A smart content server could also adjust for
> > a detected accelerator and/or transcoder ... perhaps by avoiding
> > optimizations dependant on a direct connection and byte/byte transfer
> > between the client and the server.
> > 
> > So I'm very much in favor of keeping the Via: header.
> 
> 
> Definitely not talking about getting rid of it. The (only, specific) point
> here is whether a gateway that doesn't add Via to responses should be called
> non-conformant.
> 
> Personally, I think it should be a MUST for proxies, in both directions.
> However, for a gateway, it either shouldn't be a requirement at all (for
> responses), or it should be a SHOULD with a get-out clause for reasons of
> security (along with a note that they'll need to accept responsibility for
> any issues caused by omitting Via). Still should probable be a MUST for
> requests from gateways.

But then do we want to declare all gateways non-conformant ? The only gateway
I've seen use the Via header was abusing it to put the client's IP address
into it, and none of the hosted servers behind it were ever confused by this
despite being a few tens of various products!

The only use I see with Via is to convey the original message's HTTP version,
but most (all?) gateways do not change this version because it's already
painful to be a gateway, you generally don't want to add more burden by
changing the protocol version between the two sides!

Willy


From mrex@sap.com  Mon Apr 22 07:32:45 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68D7321F90CC; Mon, 22 Apr 2013 07:32:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MqZfd++V91Gx; Mon, 22 Apr 2013 07:32:44 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 9E1F721F90BB; Mon, 22 Apr 2013 07:32:44 -0700 (PDT)
Received: from mail06.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r3MEWgTj022777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 22 Apr 2013 16:32:42 +0200 (MEST)
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
In-Reply-To: <tslzjwqoehg.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Mon, 22 Apr 2013 16:32:42 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130422143242.B6C5E1A6C7@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ipv6@ietf.org, RJ Atkinson <rja.lists@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: Mon, 22 Apr 2013 14:32:45 -0000

Sam Hartman wrote:
>
> RJ Atkinson <rja.lists@gmail.com> writes:
> 
> 
>     RJ> I oppose Eliot's proposed edits on grounds that they would
>     RJ> reduce the clarity of the specification and also would reduce
>     RJ> IETF and WG consensus about this specification.
> 
> Ran,  I just checked, and you don't seem to be a 6man chair. We
> generally ask chairs, not involved participants to judge WG consensus
> and ADs to judge IETF consensus.
> 
> So, I think  what you're saying boils down to you disagree with Eliot
> because you believe his comments would reduce clarity. You believe
> others within the WG and outside the WG are likely to agree with you.
> That's all fine and is valuable to contribute.
> 
> However, I don't think it promotes open and honest technical discussion
> when participants try to call consensus. 
> Thanks for considering my input.


This applies not only to individuals alleging "consensus", but in just
the same way to WG chairs, ADs and the IESG to allege "consensus" for
a change without performing a consensus call that properly lists
options and their tradeoffs.

The only exception is, that IETF leadership (WG chairs, AD, IESG)
could assert their leadership privilege to make a specific choice.
In this case, however, they should label it as such (a leadership
decision).  For resolving issues that individuals have with
leadership decisions, there is the appeals process.


-Martin

From ynir@checkpoint.com  Mon Apr 22 08:15:58 2013
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 8F8D221E8082 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 08:15:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.549
X-Spam-Level: 
X-Spam-Status: No, score=-10.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CE7azdcgePc9 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 08:15:57 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1A98721E8056 for <ietf@ietf.org>; Mon, 22 Apr 2013 08:15:56 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r3MFFV2U015521; Mon, 22 Apr 2013 18:15:32 +0300
X-CheckPoint: {51755349-0-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Mon, 22 Apr 2013 18:15:31 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOO6uAkYNXJKWRyEmIKVS5GuPId5jbdJGAgAAIsICAAEJXWoAARRgggAEyZAD//9h6AIAFHIg1gAACuIA=
Date: Mon, 22 Apr 2013 15:15:29 +0000
Message-ID: <6DA12A55-6063-4E41-98F2-9190A049D15A@checkpoint.com>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>, <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E6C@EXMB01CMS.surrey.ac.uk>, <4613980CFC78314ABFD7F85CC302772111A0F977@IL-EX10.ad.checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E70@EXMB01CMS.surrey.ac.uk>, <E49D2A72-8E1F-472E-B0CC-EF00E86AE526@checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E7F@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E7F@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.226]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 1164e9640314eabbffa6e4f592617f93a53bd924c3
Content-Type: text/plain; charset="us-ascii"
Content-ID: <10B3D65ED3D0B04EB724192605E827F6@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, 22 Apr 2013 15:15:58 -0000

Well, there isn't a delay tolerant networks working group, but the IRTF has=
 a DTNRG ( http://irtf.org/dtnrg ).

At least one of the chairs is a "goer". If you really wanted to standardize=
 this, wouldn't you be able to find 1-2 people on the DTNRG list who would =
be willing to "do the BoF thing"?

I'm not saying this is definitely what you should do. There are plenty of r=
easons to bring something to the IETF and to not bring it. I'm only saying =
that it is possible.

Yoav
=20
On Apr 22, 2013, at 3:12 PM, l.wood@surrey.ac.uk wrote:

> And the technology that my team is pushing would be Saratoga:
> http://saratoga.sf.net
> which has interoperable implementations that can do 50Mbps in perl, a dec=
ade of operational experience in its application domain, and mature drafts.
>=20
> But this is in the transport area, and TSV has somewhat limited resources=
, so it's outside the span of attention from a wg. But still worth document=
ing as experimental.
>=20
> Lloyd Wood
> http://sat-net.com/L.Wood/
>=20
>=20
> ________________________________________
> From: Yoav Nir [ynir@checkpoint.com]
> Sent: 19 April 2013 10:02
> To: Wood L  Dr (Electronic Eng)
> Cc: <worley@ariadne.com>; <ietf@ietf.org>
> Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IE=
SG     Review)
>=20
> Only that you know enough people so that you could push a new technology =
even without attending, although you would need to collaborate with some pe=
ople who do go. But pushing a new technology requires team building anyway.
>=20
> The same should apply to other non-attenders who have gained some reputat=
ion.
>=20
>=20
> On Apr 19, 2013, at 11:23 AM, l.wood@surrey.ac.uk wrote:
>=20
>>=20
>> and the point of your ad-hominem argument is what, exactly?
>>=20
>> Lloyd Wood
>> http://sat-net.com/L.Wood/publications/internet-drafts
>>=20
>>=20
>> ________________________________________
>> From: Yoav Nir [ynir@checkpoint.com]
>> Sent: 18 April 2013 15:18
>> To: Wood L  Dr (Electronic Eng)
>> Cc: worley@ariadne.com; ietf@ietf.org
>> Subject: RE: The Purpose of WG participants Review (was Re: Purpose of I=
ESG     Review)
>>=20
>> Looking in Jari's statistics site, you have three RFCs. One of those has=
 several co-authors that I recognize as current "goers". You also have a cu=
rrent draft with several co-authors, but I have no idea whether they're "go=
ers" or not. Anyway, you are not a hermit. Through the RFCs and drafts that=
 you have co-authored, you know people who do attend.
>=20
>=20
> Email secured by Check Point


From mstjohns@comcast.net  Mon Apr 22 09:03:28 2013
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 9180011E80D1 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 09:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WbQXTxnTW12V for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 09:03:28 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id D3C9C11E80BF for <ietf@ietf.org>; Mon, 22 Apr 2013 09:03:27 -0700 (PDT)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta15.westchester.pa.mail.comcast.net with comcast id Szns1l0081ZXKqc5F43Tq7; Mon, 22 Apr 2013 16:03:27 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta21.westchester.pa.mail.comcast.net with comcast id T43S1l00K2kB7pQ3h43TUU; Mon, 22 Apr 2013 16:03:27 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 22 Apr 2013 12:03:26 -0400
To: Sam Hartman <hartmans-ietf@mit.edu>,RJ Atkinson <rja.lists@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
In-Reply-To: <tslzjwqoehg.fsf@mit.edu>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <tslzjwqoehg.fsf@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1366646607; bh=L/XlzKU4ZMm42Jvw4rHPda4ti69ZrUYXtiulkb0Lx8M=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=A4GOmk2GF2yzYrDWx7pwjZsF8qW1+9qWWYm+3ldqs0pTbWhQI+NsDPNO5iG20Gykt x4UBRoOs28xuw6pQjAIltkZDgvVhiGwcawFtOz1JEJX4WQWwZBRHhFjBLEHhxf5Ko0 ULKYjHCjUiYMnzWcYLEtU6lrkYy6kJuNEL+yiAMuwRaNfeFmZrYQb+oE/gpsPXtD6m BcEggWbrNgO2VojtDb+Ww1AJErcugPyP09to/EEEsflFV8qbnBC8KYt4yH05Vc3TLD GursYLWEqMrc5dpgyV5wiQ6PFXKd3pi5/pPWVRiHjD71xxeS0k0q/Sf+hZlzwIjUA3 2f6KQkAIPpfzQ==
Message-Id: <20130422160327.D3C9C11E80BF@ietfa.amsl.com>
Cc: ipv6@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, 22 Apr 2013 16:03:28 -0000

At 09:56 AM 4/22/2013, Sam Hartman wrote:
>>>>>> "RJ" == RJ Atkinson <rja.lists@gmail.com> writes:
>
>
>    RJ> I oppose Eliot's proposed edits on grounds that they would
>    RJ> reduce the clarity of the specification and also would reduce
>    RJ> IETF and WG consensus about this specification.
>
>Ran,  I just checked, and you don't seem to be a 6man chair. We
>generally ask chairs, not involved participants to judge WG consensus
>and ADs to judge IETF consensus.

Bovine dung.  Or more politely - nonsense.  Participants judge WG consensus all the time.  Occasionally WG chairs will "declare" consensus to more the process forward, but that's rarer than the normal group think.


>So, I think  what you're saying boils down to you disagree with Eliot
>because you believe his comments would reduce clarity. You believe
>others within the WG and outside the WG are likely to agree with you.
>That's all fine and is valuable to contribute.
>
>However, I don't think it promotes open and honest technical discussion
>when participants try to call consensus. 
>Thanks for considering my input.


And I don't think it promotes open and honest technical discussion when you attack "standing" of a participant who *has* participated in the formation of a document to take an action, ask a question, or make a comment, rather than addressing the substance of the comment(s) made by that participant.


It's unclear from what you wrote that you considered the substance of Ran's comment.  

What he wrote was:

>It would reduce consensus within the WG and the IETF as a whole
>to remove that text -- as it clarifies that other mechanisms for
>generating such IDs are not affected by this specification.
>
>Text to this effect was specifically requested by various WG 
>participants, precisely because it is not "self-evident" and 
>instead was confusing.


What *I* heard was:  "Elliot, the section you want to remove was added specifically through working group discussion to gain consensus for the document".   Assuming that I understood that was what he meant, and that it represents the reality of the process, Ran drawing the conclusion that removing that text would tend to "reduce consensus" seems to be a reasonable one and targeted specifically at the edit.


Mike




From fgont@si6networks.com  Mon Apr 22 09:06:17 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F61521F9154; Mon, 22 Apr 2013 09:06:17 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6K+DDE5wmScR; Mon, 22 Apr 2013 09:06:17 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id D4F6521F90A1; Mon, 22 Apr 2013 09:06:13 -0700 (PDT)
Received: from [201.157.17.130] (helo=[172.20.4.229]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UUJFn-0001rG-GZ; Mon, 22 Apr 2013 18:06:09 +0200
Message-ID: <51755FE9.9060809@si6networks.com>
Date: Mon, 22 Apr 2013 11:06:01 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <5174D69F.6090300@cisco.com>
In-Reply-To: <5174D69F.6090300@cisco.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, 6man@ietf.org, Bob Hinden <bob.hinden@gmail.com>, 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, 22 Apr 2013 16:06:17 -0000

Hi, Eliot,

On 04/22/2013 01:20 AM, Eliot Lear wrote:
> In the process of doing the apps area review, I came across some points
> that were not related to applications.  The basis for these comments is
> precisely the sentiment that Russ Housley expressed, which is that the
> specification is done when there is no more to remove.

I'd probaby disagree with such statement. One thing is removing tuff
from the mechanism or algorithm that you're standardizing, in the hopes
of keeping it simple (this one I'd agree with). Another is removing text
from specifications, which essentially means that the gut implementing
the spec has more to figure out by himself, and hence more chances for
failures.


>  With this
> document, I wonder if quite a bit could be removed.
> 
> Specifically, a great deal of discussion goes into the PRF involving DAD
> counters, etc, when all that is needed is a suitable PRF.

Not sure what you mean...What's thetext that you think could/should be
removed?


> The draft in
> fact says this in Section 3 after an explanation of the inputs.  Any PRF
> that follows the guidelines of RFC 4086 should do fine and not cause
> interoperability OR security problems.

If you're referring to the text that explains why we're not mandating
any specific PRF, that text is there because the issue was raisen in the wg,


> Also, the following text in section 3 Page 7 is contorted:
> 
>       This means that this document does not formally obsolete or
>       deprecate any of the existing algorithms to generate Interface IDs
>       (e.g. such as that specified in [RFC2464]).  However, those IPv6
>       implementations that employ this specification must generate all
>       of their "stable" addresses as specified in this document.
> 
> My suggestion is to simplify remove it as it is self-evident.

What's the part that is evident? The one about not deprecating existing
algorithms? -- Because the other ne certainly isn't: if you're going to
use this algorithm for generating addresses *in addition* to those
generated by traditional SLAAC, then this document wouldn't mitigate
address-scanning attacks.



> Finally, this algorithm requires that the resultant host portion be 64
> bits.  Is that necessary?

Well, yes- If the PRF produces a bit string larger than 64 bits,  and
you say nothing about how you grab the IID, then the algorithm is
underspecified.

The easier it is for a developer to go through this document and come up
with an implementation, the better. The more the open questions, the worse.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From lear@cisco.com  Mon Apr 22 09:22:30 2013
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 7771621F8FC7; Mon, 22 Apr 2013 09:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.999
X-Spam-Level: 
X-Spam-Status: No, score=-110.999 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mxvvym8DNJOI; Mon, 22 Apr 2013 09:22:29 -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 A28F021F854E; Mon, 22 Apr 2013 09:22:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4529; q=dns/txt; s=iport; t=1366647749; x=1367857349; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=suwTD0aVilDPZlmCy+liXde/jU0gjKXbBIo+XYm5oaE=; b=I4+iRL/Ce7bQkhI6bFb4/TKEUBoNqxSUMphJ58F0iGpaPk9TUj2iYshs vhMMjaZXuseTHpSB/x5+/AP0Issn2C8CS55pSnJQWdXJHnTVFPhCjgJmN WOOlcTyCi+1k/pfIRkfsg+iLY8irBwuJSBdYXQ5bD7gIHP3AE6vC3CNRk 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAKtidVGQ/khL/2dsb2JhbABPgwaDZ7pngmqBBhZ0gh8BAQEDASNVARALDgoCAgUWCwICCQMCAQIBRQYNAQcBAYgKBqpBkQqBI44cB4I0gRMDlxWRGoMOOg
X-IronPort-AV: E=Sophos;i="4.87,527,1363132800"; d="scan'208";a="153145297"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 22 Apr 2013 16:22:27 +0000
Received: from ams3-vpn-dhcp5433.cisco.com (ams3-vpn-dhcp5433.cisco.com [10.61.85.56]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r3MGMO2s009406 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Apr 2013 16:22:25 GMT
Message-ID: <517563C0.6000508@cisco.com>
Date: Mon, 22 Apr 2013 18:22:24 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <5174D69F.6090300@cisco.com> <51755FE9.9060809@si6networks.com>
In-Reply-To: <51755FE9.9060809@si6networks.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, 6man@ietf.org, Bob Hinden <bob.hinden@gmail.com>, 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, 22 Apr 2013 16:22:30 -0000

Hi Fernando,

Thanks very much for your response.

On 4/22/13 6:06 PM, Fernando Gont wrote:
> Hi, Eliot,
>
> On 04/22/2013 01:20 AM, Eliot Lear wrote:
>> In the process of doing the apps area review, I came across some points
>> that were not related to applications.  The basis for these comments is
>> precisely the sentiment that Russ Housley expressed, which is that the
>> specification is done when there is no more to remove.
> I'd probaby disagree with such statement. One thing is removing tuff
> from the mechanism or algorithm that you're standardizing, in the hopes
> of keeping it simple (this one I'd agree with). Another is removing text
> from specifications, which essentially means that the gut implementing
> the spec has more to figure out by himself, and hence more chances for
> failures.

Fair point, of course.

>
>
>>  With this
>> document, I wonder if quite a bit could be removed.
>>
>> Specifically, a great deal of discussion goes into the PRF involving DAD
>> counters, etc, when all that is needed is a suitable PRF.
> Not sure what you mean...What's thetext that you think could/should be
> removed?

Sorry I wasn't clear: what is the benefit of specifying the algorithm,
when simply popping out another PRF will in just about any instance do
the job (unless you are reinitializing the PRF with the same seed)?

>
>
>> The draft in
>> fact says this in Section 3 after an explanation of the inputs.  Any PRF
>> that follows the guidelines of RFC 4086 should do fine and not cause
>> interoperability OR security problems.
> If you're referring to the text that explains why we're not mandating
> any specific PRF, that text is there because the issue was raisen in the wg,

Ok.  So what I gather is that there was a negotiation within the WG and
that the algorithm is optional.  Ok.  From an outside point of view, I
didn't need to know that, and the question is what was the value of
still specifying the PRF.  I think Ran Atkinson answered that.  He feels
he wants a fully specified algorithm from which to start.  Ok.  My only
response is that I don't understand the need (generating 64 bits that
aren't the same shouldn't be that hard), but if the WG really believes
there is one, okay.


>
>
>> Also, the following text in section 3 Page 7 is contorted:
>>
>>       This means that this document does not formally obsolete or
>>       deprecate any of the existing algorithms to generate Interface IDs
>>       (e.g. such as that specified in [RFC2464]).  However, those IPv6
>>       implementations that employ this specification must generate all
>>       of their "stable" addresses as specified in this document.
>>
>> My suggestion is to simplify remove it as it is self-evident.
> What's the part that is evident? The one about not deprecating existing
> algorithms? -- Because the other ne certainly isn't: if you're going to
> use this algorithm for generating addresses *in addition* to those
> generated by traditional SLAAC, then this document wouldn't mitigate
> address-scanning attacks.

How would an IPv6 implementation employing this specification vary from
this specification in a way you or the working group would find
objectionable?  Also, did you mean "MUST"?  If not, this language is all
the more confusing and I don't know what you mean.

>> Finally, this algorithm requires that the resultant host portion be 64
>> bits.  Is that necessary?
> Well, yes- If the PRF produces a bit string larger than 64 bits,  and
> you say nothing about how you grab the IID, then the algorithm is
> underspecified.
>
> The easier it is for a developer to go through this document and come up
> with an implementation, the better. The more the open questions, the worse.
>

I think we are underestimating our developers but if the working group
feels differently, okay.  I asked the above question because it is at
least conceivable that at some point host portion != 64 bits and this is
the only place in the document where the requirement is stated.  Yes,
screwing with the 64 bit boundary today is bound to cause all sorts of
breakage.  I'm not thinking of today but the future.  And yes, another
argument would be that there isn't enough address space for this to be
effectively private.  Those are two different issues, but fixing the
boundary here reminds me of mistakes we made with IPv4 way back when. 
In this day and age we're talking about a lot more cleanup later.

Eliot

From touch@isi.edu  Mon Apr 22 10:27:06 2013
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 65EA421F912C for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 10:27:06 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5s9pOoFeWXd5 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 10:27:05 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 370B921F9120 for <ietf@ietf.org>; Mon, 22 Apr 2013 10:26:59 -0700 (PDT)
Received: from [192.168.1.96] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r3MHQ0Qt009820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 Apr 2013 10:26:09 -0700 (PDT)
Message-ID: <517572A9.9060209@isi.edu>
Date: Mon, 22 Apr 2013 10:26:01 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>, <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E6C@EXMB01CMS.surrey.ac.uk>, <4613980CFC78314ABFD7F85CC302772111A0F977@IL-EX10.ad.checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E70@EXMB01CMS.surrey.ac.uk> <E49D2A72-8E1F-472E-B0CC-EF00E86AE526@checkpoint.com>
In-Reply-To: <E49D2A72-8E1F-472E-B0CC-EF00E86AE526@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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, 22 Apr 2013 17:27:06 -0000

On 4/19/2013 2:02 AM, Yoav Nir wrote:
> Only that you know enough people so that you could push a new technology even without attending,

IETF work officially happens on IETF lists, not at in-person meetings.

As per the Tao of the IETF: "Any decision made at a face-to-face meeting 
must also gain consensus on the WG mailing list."

Team-building is also useful, but not necessary, and also can happen 
off-list and at other non-IETF meetings.

Joe

From sm@resistor.net  Mon Apr 22 10:55:56 2013
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 C540521F9389 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 10:55:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TSpFA+jZAqHG for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 10:55:55 -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 89BD121F9382 for <ietf@ietf.org>; Mon, 22 Apr 2013 10:55:55 -0700 (PDT)
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 r3MHtjIM001476; Mon, 22 Apr 2013 10:55:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1366653350; bh=XnbEJMXS8e+TdT4LZbCeR+QGMzHv5prWRw9FiM9kuDo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tw66tWClmpCjxkjhO2++D+RR1LFedOG+novPnUpnko0Fmd1XEew/Q965gPQ/WX0VY 1xQuALNX9hXol2ofAwzlLutEMIT+AcyXrxzMt9MboyYSkF7zQQbWEUSCz9aOfL/D2G tj1DDOmWay7VX/cbvL2KCDUlFFt3S3JM0VYzT4mo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1366653350; i=@resistor.net; bh=XnbEJMXS8e+TdT4LZbCeR+QGMzHv5prWRw9FiM9kuDo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iWq0I/3COUpaIcNsEGoVwcccTfabFsV5Jy0EnvrflH4mh6/7JBFvfml/+aDhKAYTB dCkVd3FM+5k/+PtpiiHGTmendkMZPJspKiYKHZ2Tusy2Sv5WmNHKGS7Q/2J4lpgWP2 p2lfPi4N19el+AUuZuZQzKuOSPTYH7M8nsIuEhq0=
Message-Id: <6.2.5.6.2.20130422081720.0db4ca38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 22 Apr 2013 10:53:00 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
In-Reply-To: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: RJ Atkinson <rja.lists@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, 22 Apr 2013 17:55:57 -0000

At 06:34 22-04-2013, RJ Atkinson wrote:
>It would reduce consensus within the WG and the IETF as a whole
>to remove that text -- as it clarifies that other mechanisms for
>generating such IDs are not affected by this specification.

The document shepherd write-up mentioned that there is "Nothing in 
particular" to report about the working group discussions.  There 
were two WG participants discussing about 
draft-ietf-6man-stable-privacy-addresses during the WGLC (excluding 
the listed author and the WG Chairs).

I'll comment on the draft.  The document is well-written.

 From Section 1:

   'The "Privacy Extensions for Stateless Address Autoconfiguration in
    IPv6" [RFC4941] were introduced to complicate the task of
    eavesdroppers and other information collectors to correlate the
    activities of a node, and basically result in temporary (and random)
    Interface Identifiers that are typically more difficult to leverage
    than those based on IEEE identifiers.'

There are some warnings in RFC 4941 about correlation.  I don't see 
any notes about that in this draft.  My reading of this proposal is 
that it is to mitigate address scanning.  I could not find any 
guidance on whether to use RFC 4941 or this draft for "privacy addresses".

 From Section 3:

   "The aforementioned algorithm MUST be employed for generating
    the interface identifiers for all of the IPv6 addresses
    configured with SLAAC for a given interface, including IPv6
    link-local addresses."

The requirement is repeated in the note:

   "This means that this document does not formally obsolete or
    deprecate any of the existing algorithms to generate Interface IDs
    (e.g. such as that specified in [RFC2464]).  However, those IPv6
    implementations that employ this specification must generate all
    of their "stable" addresses as specified in this document."

I read that as meaning that this document informally obsoletes or 
deprecates some of the existing algorithms but it's better not to say 
it formally as it would be controversial.

   "Implementations conforming to this specification SHOULD provide the
    means for a system administrator to enable or disable the use of this
    algorithm for generating Interface Identifiers."

If the implementation does not provide the means for the 
administrator to enable or disable the use of the algorithm, does it 
conform to this specification?

Regards,
-sm



From fgont@si6networks.com  Mon Apr 22 12:23:21 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 418DA11E80ED; Mon, 22 Apr 2013 12:23:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_OFF=2.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1mWnbB-In4Zp; Mon, 22 Apr 2013 12:23:20 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3DE7B21F9193; Mon, 22 Apr 2013 12:23:20 -0700 (PDT)
Received: from [201.157.17.130] (helo=[172.20.4.229]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UUMKY-0006Vt-Vs; Mon, 22 Apr 2013 21:23:15 +0200
Message-ID: <51758E1F.80803@si6networks.com>
Date: Mon, 22 Apr 2013 14:23:11 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <5174D69F.6090300@cisco.com> <51755FE9.9060809@si6networks.com> <517563C0.6000508@cisco.com>
In-Reply-To: <517563C0.6000508@cisco.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, 6man@ietf.org, Bob Hinden <bob.hinden@gmail.com>, 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, 22 Apr 2013 19:23:21 -0000

Hi, Eliot,

On 04/22/2013 11:22 AM, Eliot Lear wrote:
>>>  With this
>>> document, I wonder if quite a bit could be removed.
>>>
>>> Specifically, a great deal of discussion goes into the PRF involving DAD
>>> counters, etc, when all that is needed is a suitable PRF.
>> Not sure what you mean...What's thetext that you think could/should be
>> removed?
> 
> Sorry I wasn't clear: what is the benefit of specifying the algorithm,
> when simply popping out another PRF will in just about any instance do
> the job (unless you are reinitializing the PRF with the same seed)?

There seems to be a disconnect here:

We want an algorithm that, roughly speaking, whenever you connect to the
same network, gives you the same address. But such address should be
different for each network you connect to.

The question here is: How do you achieve that?

You might argue that, clearly, the autoconf prefix needs to be part of
the seed (I'd personally not expect developers to figure this one out).

But there are more issues. e.g., say that my node has to network
interfaces. If I use both of them to connect to the same network, the
address they get should be different (but still have the same properties
stated above). How do you achieve that? -- Well, yu need *something*
that changes from one interface to another. But even if you figure
*something* you mght use for that it might be non-optimal. -- for
example, if you use the MAC address, then your address changes if you
replace the NIC. If you use the interface index, it doesn't.

At the end of the day, the devil lies in the small details.

And I'd argue that if it had all been that obvious, it'd have been done
before.



>>> The draft in
>>> fact says this in Section 3 after an explanation of the inputs.  Any PRF
>>> that follows the guidelines of RFC 4086 should do fine and not cause
>>> interoperability OR security problems.
>> If you're referring to the text that explains why we're not mandating
>> any specific PRF, that text is there because the issue was raisen in the wg,
> 
> Ok.  So what I gather is that there was a negotiation within the WG and
> that the algorithm is optional.

The "negotiation" was that this dspec does not replace the traditional
slaac algorithm that, in the case of Ethernet, embeds IEEE identifers in
the Interface ID.


> Ok.  From an outside point of view, I
> didn't need to know that, and the question is what was the value of
> still specifying the PRF.  I think Ran Atkinson answered that.  He feels
> he wants a fully specified algorithm from which to start.  Ok.  My only
> response is that I don't understand the need (generating 64 bits that
> aren't the same shouldn't be that hard), but if the WG really believes
> there is one, okay.

We're not just "randomizing" the addresses. The are *constant* within
each network, but change across networks.



>>> Also, the following text in section 3 Page 7 is contorted:
>>>
>>>       This means that this document does not formally obsolete or
>>>       deprecate any of the existing algorithms to generate Interface IDs
>>>       (e.g. such as that specified in [RFC2464]).  However, those IPv6
>>>       implementations that employ this specification must generate all
>>>       of their "stable" addresses as specified in this document.
>>>
>>> My suggestion is to simplify remove it as it is self-evident.
>> What's the part that is evident? The one about not deprecating existing
>> algorithms? -- Because the other ne certainly isn't: if you're going to
>> use this algorithm for generating addresses *in addition* to those
>> generated by traditional SLAAC, then this document wouldn't mitigate
>> address-scanning attacks.
> 
> How would an IPv6 implementation employing this specification vary from
> this specification in a way you or the working group would find
> objectionable?  

If, for the same interface you employ this algorithm *and* the
traditional SLAAC algorithm, that's objectionable.


> Also, did you mean "MUST"?  If not, this language is all
> the more confusing and I don't know what you mean.

Yes, I meant "MUST". -- I will fix this.



>>> Finally, this algorithm requires that the resultant host portion be 64
>>> bits.  Is that necessary?
>> Well, yes- If the PRF produces a bit string larger than 64 bits,  and
>> you say nothing about how you grab the IID, then the algorithm is
>> underspecified.
>>
>> The easier it is for a developer to go through this document and come up
>> with an implementation, the better. The more the open questions, the worse.
> 
> I think we are underestimating our developers but if the working group
> feels differently, okay.

I don't think so. Lots of folks code on so many different areas, that
it'd be unrealistic to expect them to figure everything out by themselves.

Yes, there are some smart folks that can figure a lot by themselves...
but that's the exception rather than the rule.

And even if they were all that smart, we want to make their lives
easier: the less they have to figure out by themselves, the better.



> I asked the above question because it is at
> least conceivable that at some point host portion != 64 bits and this is
> the only place in the document where the requirement is stated.  Yes,
> screwing with the 64 bit boundary today is bound to cause all sorts of
> breakage.

My understanding is that we're all set for 64-bit identifiers -- with
the exception of point to point links where subnets < 64 bits are
allowed (fro the most part, as a workaround to buggy implementations
that are vulnerable to NCE attacks).


> I'm not thinking of today but the future.  And yes, another
> argument would be that there isn't enough address space for this to be
> effectively private.  Those are two different issues, but fixing the
> boundary here reminds me of mistakes we made with IPv4 way back when. 
> In this day and age we're talking about a lot more cleanup later.

I guess this raises a more fundamental question with respect to whether
we want 64-bit identifiers to be the standard, or not.

A compromise might be to add a *parenthetical* note such as:

"The current IPv6 Addressing architecture defines Interface-Identifiers
to be 64 bits long, hence the low-order 64-bits of F() are employed for
the Interface-ID. Were the IPv6 Addressing Architecture updated to allow
any arbitrary length for the Interface ID, an implementation would need
to be prepared to select as many bits from F() (rather than the fixed
64-bits specified above) for the Interface ID, such that an Interface ID
of appropriate length is obtained"

I'd personally have no issues with that *if* the wg agrees. But I
wouldn't want to remove the text on grabbing the low-order 64-bits,
since that's makes the spec more clear for the current times.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From fgont@si6networks.com  Mon Apr 22 12:40:53 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56EB621E80BA for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 12:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.216
X-Spam-Level: 
X-Spam-Status: No, score=-2.216 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xk34w4BoZ7Dn for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 12:40:52 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id E16B321F9132 for <ietf@ietf.org>; Mon, 22 Apr 2013 12:40:46 -0700 (PDT)
Received: from [201.157.17.130] (helo=[172.20.4.229]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UUMbS-0006y5-VU; Mon, 22 Apr 2013 21:40:43 +0200
Message-ID: <51759238.8000306@si6networks.com>
Date: Mon, 22 Apr 2013 14:40:40 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net>
In-Reply-To: <6.2.5.6.2.20130422081720.0db4ca38@resistor.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: RJ Atkinson <rja.lists@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: Mon, 22 Apr 2013 19:40:53 -0000

Hi, SM,

On 04/22/2013 12:53 PM, SM wrote:
> 
> From Section 1:
> 
>   'The "Privacy Extensions for Stateless Address Autoconfiguration in
>    IPv6" [RFC4941] were introduced to complicate the task of
>    eavesdroppers and other information collectors to correlate the
>    activities of a node, and basically result in temporary (and random)
>    Interface Identifiers that are typically more difficult to leverage
>    than those based on IEEE identifiers.'
> 
> There are some warnings in RFC 4941 about correlation.  I don't see any
> notes about that in this draft.

PLease see the Appendix.


> My reading of this proposal is that it
> is to mitigate address scanning.  I could not find any guidance on
> whether to use RFC 4941 or this draft for "privacy addresses".

Privacy addresses are employed in addition to traditional SLAAC
addresses -- hence they don't mitigate address scanning. FWIW, this is
all discussed in the I-D.



>   "Implementations conforming to this specification SHOULD provide the
>    means for a system administrator to enable or disable the use of this
>    algorithm for generating Interface Identifiers."
> 
> If the implementation does not provide the means for the administrator
> to enable or disable the use of the algorithm, does it conform to this
> specification?

It'd be "conditionally-compliant", but not fully-compliant.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From l.wood@surrey.ac.uk  Mon Apr 22 12:54:33 2013
Return-Path: <l.wood@surrey.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 8D29921E80B8 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 12:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.223
X-Spam-Level: 
X-Spam-Status: No, score=-3.223 tagged_above=-999 required=5 tests=[AWL=-0.625, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P8+rtpxcxTd1 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 12:54:31 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.142]) by ietfa.amsl.com (Postfix) with ESMTP id CD4B121F8C69 for <ietf@ietf.org>; Mon, 22 Apr 2013 12:54:30 -0700 (PDT)
Received: from [195.245.231.67:52805] by server-6.bemta-5.messagelabs.com id 44/B7-21466-57595715; Mon, 22 Apr 2013 19:54:29 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-82.messagelabs.com!1366660469!32886292!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8011 invoked from network); 22 Apr 2013 19:54:29 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-10.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 22 Apr 2013 19:54:29 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Mon, 22 Apr 2013 20:53:42 +0100
From: <l.wood@surrey.ac.uk>
To: <ynir@checkpoint.com>
Date: Mon, 22 Apr 2013 20:53:42 +0100
Subject: RE: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Topic: The Purpose of WG participants Review (was Re: Purpose of IESG Review)
Thread-Index: AQHOO6uAkYNXJKWRyEmIKVS5GuPId5jbdJGAgAAIsICAAEJXWoAARRgggAEyZAD//9h6AIAFHIg1gAACuICAAHtcUA==
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E80@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ89kMbXCst92gH5mN3tsuV6VR_Yo9ROaiXba8uOOCMG3jw@mail.gmail.com> <1D6E4110-8BE8-4D7D-91F7-3CB1E0F6925A@wierenga.net> <201304161551.r3GFpYgE2798122@shell01.TheWorld.com> <8D23D4052ABE7A4490E77B1A012B63077514BC8F@mbx-01.win.nominum.com>, <201304172038.r3HKcMgT2892908@shell01.TheWorld.com> <290E20B455C66743BE178C5C84F12408223F494E6B@EXMB01CMS.surrey.ac.uk>, <364C575F-3B22-44AD-9CC9-61242C2FEE9B@checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E6C@EXMB01CMS.surrey.ac.uk>, <4613980CFC78314ABFD7F85CC302772111A0F977@IL-EX10.ad.checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E70@EXMB01CMS.surrey.ac.uk>, <E49D2A72-8E1F-472E-B0CC-EF00E86AE526@checkpoint.com> <290E20B455C66743BE178C5C84F12408223F494E7F@EXMB01CMS.surrey.ac.uk>, <6DA12A55-6063-4E41-98F2-9190A049D15A@checkpoint.com>
In-Reply-To: <6DA12A55-6063-4E41-98F2-9190A049D15A@checkpoint.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 22 Apr 2013 19:54:33 -0000

Yoav,

Yes, Saratoga started as a draft in the DTNRG (draft-wood-tsvwg-saratoga). =
We carried the first bundles from space in 2008, and used our experience to=
 analyse failings in the bundle protocol. (See our "A bundle of problems" p=
aper.)

Unfortunately, DTNRG wasn't chartered to do DTN research. It was chartered =
to do only development of the bundle protocol as the one true solution to D=
TNs, whick it wasn't.

In any case, IRTF groups can't standardise anything, just produce experimen=
tal RFCs  (though CCSDS was pushing for standardising bundling for itself l=
ast I looked.)

Lloyd Wood
http://sat-net.com/L.Wood/dtn


________________________________________
From: Yoav Nir [ynir@checkpoint.com]
Sent: 22 April 2013 16:15
To: Wood L  Dr (Electronic Eng)
Cc: <worley@ariadne.com>; <ietf@ietf.org>
Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IESG=
     Review)

Well, there isn't a delay tolerant networks working group, but the IRTF has=
 a DTNRG ( http://irtf.org/dtnrg ).

At least one of the chairs is a "goer". If you really wanted to standardize=
 this, wouldn't you be able to find 1-2 people on the DTNRG list who would =
be willing to "do the BoF thing"?

I'm not saying this is definitely what you should do. There are plenty of r=
easons to bring something to the IETF and to not bring it. I'm only saying =
that it is possible.

Yoav

On Apr 22, 2013, at 3:12 PM, l.wood@surrey.ac.uk wrote:

> And the technology that my team is pushing would be Saratoga:
> http://saratoga.sf.net
> which has interoperable implementations that can do 50Mbps in perl, a dec=
ade of operational experience in its application domain, and mature drafts.
>
> But this is in the transport area, and TSV has somewhat limited resources=
, so it's outside the span of attention from a wg. But still worth document=
ing as experimental.
>
> Lloyd Wood
> http://sat-net.com/L.Wood/
>
>
> ________________________________________
> From: Yoav Nir [ynir@checkpoint.com]
> Sent: 19 April 2013 10:02
> To: Wood L  Dr (Electronic Eng)
> Cc: <worley@ariadne.com>; <ietf@ietf.org>
> Subject: Re: The Purpose of WG participants Review (was Re: Purpose of IE=
SG     Review)
>
> Only that you know enough people so that you could push a new technology =
even without attending, although you would need to collaborate with some pe=
ople who do go. But pushing a new technology requires team building anyway.
>
> The same should apply to other non-attenders who have gained some reputat=
ion.
>
>
> On Apr 19, 2013, at 11:23 AM, l.wood@surrey.ac.uk wrote:
>
>>
>> and the point of your ad-hominem argument is what, exactly?
>>
>> Lloyd Wood
>> http://sat-net.com/L.Wood/publications/internet-drafts
>>
>>
>> ________________________________________
>> From: Yoav Nir [ynir@checkpoint.com]
>> Sent: 18 April 2013 15:18
>> To: Wood L  Dr (Electronic Eng)
>> Cc: worley@ariadne.com; ietf@ietf.org
>> Subject: RE: The Purpose of WG participants Review (was Re: Purpose of I=
ESG     Review)
>>
>> Looking in Jari's statistics site, you have three RFCs. One of those has=
 several co-authors that I recognize as current "goers". You also have a cu=
rrent draft with several co-authors, but I have no idea whether they're "go=
ers" or not. Anyway, you are not a hermit. Through the RFCs and drafts that=
 you have co-authored, you know people who do attend.
>
>
> Email secured by Check Point


From pkern@simplex.0x539.de  Mon Apr 22 11:04:33 2013
Return-Path: <pkern@simplex.0x539.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A607421F8E7B; Mon, 22 Apr 2013 11:04:33 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TS-ObG8-j21m; Mon, 22 Apr 2013 11:04:33 -0700 (PDT)
Received: from stormwind.0x539.de (stormwind.0x539.de [IPv6:2a01:4f8:101:2fff:2:0:fee:1]) by ietfa.amsl.com (Postfix) with ESMTP id 06CC121F8C0C; Mon, 22 Apr 2013 11:04:32 -0700 (PDT)
Received: from hub.kern.lc ([91.143.80.43]) by stormwind.0x539.de with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <pkern@simplex.0x539.de>) id 1UUL6J-0007jS-I3; Mon, 22 Apr 2013 20:04:27 +0200
Received: from f053213015.adsl.alicedsl.de ([78.53.213.15] helo=simplex.lan.home.philkern.de) by hub.kern.lc with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <pkern@simplex.0x539.de>) id 1UUL6K-00073G-Lf; Mon, 22 Apr 2013 20:04:28 +0200
Received: from pkern by simplex.lan.home.philkern.de with local (Exim 4.80) (envelope-from <pkern@simplex.0x539.de>) id 1UUL6J-000362-A9; Mon, 22 Apr 2013 20:04:27 +0200
Date: Mon, 22 Apr 2013 20:04:27 +0200
From: Philipp Kern <phil@philkern.de>
To: Eliot Lear <lear@cisco.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
Message-ID: <20130422180427.GA11207@simplex.0x539.de>
References: <5174D69F.6090300@cisco.com> <51755FE9.9060809@si6networks.com> <517563C0.6000508@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH"
Content-Disposition: inline
In-Reply-To: <517563C0.6000508@cisco.com>
Organization: Fachschaft Mathematik / Informatik am Karlsruher Institut fuer Technologie (KIT)
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Mon, 22 Apr 2013 13:03:16 -0700
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, 6man@ietf.org, 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, 22 Apr 2013 18:04:33 -0000

--7JfCtLOvnd9MIVvH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Eliot,

am Mon, Apr 22, 2013 at 06:22:24PM +0200 hast du folgendes geschrieben:
> I asked the above question because it is at least conceivable that at
> some point host portion != 64 bits and this is the only place in the
> document where the requirement is stated.  Yes, screwing with the 64
> bit boundary today is bound to cause all sorts of breakage.  I'm not
> thinking of today but the future.  And yes, another argument would be
> that there isn't enough address space for this to be effectively
> private.  Those are two different issues, but fixing the boundary here
> reminds me of mistakes we made with IPv4 way back when.  In this day
> and age we're talking about a lot more cleanup later.

especially as there are already existing RFCs that are flexible in the
boundaries. Oddly RFC 4862 IPv6 Stateless Address Autoconfiguration is
one of them (e.g., 5.3, the creation of the link-layer address), which
is pretty much fixed by implementations to operate at the 64 bit
boundary. Granted, that's mostly when dealing with Ethernet-based
infrastructures and the document does explain that the length of the
interface identifier depends on the link type (5.5.3 d).

Kind regards
Philipp Kern

--7JfCtLOvnd9MIVvH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJRdXurAAoJEERuJUU10FbsdRsIAJMl6z/b13cRO8bO3hsow2yB
YY93unNo3RFSpsdSWVlauLTKtzUL8J40Gm/Xmupkpv2pvZxeMH3XHBfDuc1JhH16
/Npy7uTGHs4YYzcILJ71mccMWXMg86pIH52Z3tUjSk+/vu7rhlfT+52P8SUZhMR0
tHbGB6FETkUH9msdrWI6JMxsO4fSPcmedS+Qzm3AYVF9IKcQvHgj/tAT3GqhmWrC
8c/g1tyYGNJI1lSovGuebk5dHO17kLqv+qjp++dlBHQVHWJCK/Rbcgzdou2Y5cjn
khjPP57liZqGPebRUcgUx8093PNWvqmysYdxBr3EEYTFkYtN94nJ80SkNK1HjGQ=
=vPBF
-----END PGP SIGNATURE-----

--7JfCtLOvnd9MIVvH--

From ietfdbh@comcast.net  Mon Apr 22 13:21:46 2013
Return-Path: <ietfdbh@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 39D3721E804E for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 13:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sV-+YRc2iADS for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 13:21:45 -0700 (PDT)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id 381AF21E804C for <ietf@ietf.org>; Mon, 22 Apr 2013 13:21:45 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta09.westchester.pa.mail.comcast.net with comcast id T63F1l00527AodY598MkWh; Mon, 22 Apr 2013 20:21:44 +0000
Received: from [192.168.1.121] ([72.93.151.202]) by omta19.westchester.pa.mail.comcast.net with comcast id T8MF1l0084NFjk83f8MMQy; Mon, 22 Apr 2013 20:21:39 +0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Mon, 22 Apr 2013 16:21:14 -0400
Subject: FW: Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data Model for Interface Management) to Proposed Standard
From: David Harrington <ietfdbh@comcast.net>
To: IETF Discussion List <ietf@ietf.org>
Message-ID: <CD9AEA34.2D304%ietfdbh@comcast.net>
Thread-Topic: Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data Model for Interface Management) to Proposed Standard
In-Reply-To: <20130419132524.1622.39563.idtracker@ietfa.amsl.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1366662104; bh=LKnENRTeYxOvOYrPF9qYfOm+f4etAvef0fh3DNGoVUU=; h=Received:Received:Date:Subject:From:To:Message-ID:Mime-version: Content-type; b=fxj4A9Bs0zFFiB3GPXUSUs3PhyluCjQ0+UXUW+w3RPFMPBS5AzcS0Doo0X/HnTaiD io7Nm19TDeYOMgugSbC4cWfePOthH8tFIZAw8CZJ0xl/CsKXEhFg+72g604eDO/zVA OtZrhJwzR09db4dyFPy/DjL3KElsLZHYcpExaK3Ws7RgVC7BUbf38y2suT8JzsESyB E8sl9GmXX5SQvrjeBzRS1n11o/3BUzpv8IdWRRAsJS49EU2PkVTIr7eIaNdHNUWnzI 2NTxMzTXIUT9lENW4VntEe2qPyJyEYjLIMaP+p9+1JuknJ+bTObT573A2ldBejgYXp yehe9lu6CGypw==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Apr 2013 20:21:46 -0000

Hi,

I have reviewed this document and feel that is almost ready for approval.
This document defines a new data model in YANG format, based on the same
information model as the Interfaces MIB module (IF-MIB).
Effectively, the YANG model is a second (duplicative) standard for much of
the same information.
It is expected that devices may implement both the MIB and the YANG data
models.

My primary concern regards co-existence and synchronization across data
models.
I think this document would benefit from an Operational Considerations
section that discusses synchronization, or an explanation why they might
reasonably be out-of-sync.
Here are a few points to consider:

1) the ifIndex of an interface is used within the YANG model, matching the
ifIndex in IF-MIB. 
RFC2863 discusses the fact that ifIndex numbering might change during
hot-swaps.
This document does not discuss the need to ensure that IF-MIB ifIndex
changes need to be reflected in the YANG model.
The ifIndex in the YANG module must match that in IF-MIB (really, that in
the underlying instrumentation).
Failure to sync the ifIndex could lead NM applications to confuse which
already-retrieved data records are related to which interface.
This could cause an NM application to misinterpret/corrupt gathered
trending information, and possibly to apply changes to the wrong
interfaces.

2) ifType - can an interface be hot-swapped to use a different type? Is
this discussed someplace?

3) ifType - the description says the value of this mandatory object MAY be
initialized. What value should an NM application expect if it is NOT
initialized?

4) enabled - "Systems that implement the IF-MIB use the value of this leaf
to set IF-MIB.ifAdminStatus ..."; should this be a MAY/SHOULD/MUST? How
will this coexist with SNMP-based NM applications? Is there potential for
conflict? What if NETCONF sets this as enabled, then an operator sets it
to disabled via SNMP?
Does NETCONF know that its "enable" value (adminStatus) is out of date?
(does it matter? See note 7).
What if the NETCONF system directky changes the underlying instrumentation
for adminstatus without going through the MIB?

5) is there a reason why "description" value MAY match IF-MIB ifAlias
***and MAY restrict the values***?
Is there a particular use case for this lack of standardization of
restrictions across data models?
The persistence is a pretty important restriction related to the
functionality of ifAlias, and the dynamism of ifIndex.
If NETCONF is used to set the value, ignoring IF-MIB restrictions, what
happens to IF-MIB ifAlias as a persistent "handle" to the interface?

6) What error is returned via NETCONF if YANG attempts to set a value that
violates the SNMP agent implementation restrictions, and the SNMP agent
refuses the requested SET operation to ifAlias?
Is there a simple way for an operator to tell whether the implementation
supports the restrictions (other than deliberately triggering an error)?

7) what should an NM application or operator do if the YANG oper-status
and the IF-MIB operStatus differ?
IF-MIB has substantial discussion of the relationship between
ifAdminStatus and ifOperStatus. The YANG module doesn't have a comparable
discussion.
Given that there could e additional delay incurred between setting enable,
updating ifAdminStatus, the change to ifOperStatus, and the update to
oper-status, I recommend some mention in the description of enable and/or
oper-status of the detailed description in RFC2863, and applicability to
ietf-interfaces.

8) link-up-down-trap-enable: The text says this "indicates" whether traps
should be generated for the interface; shouldn't this be "configures"?

9) persistence isn't discussed in the config object descriptions. Do they
match the IF-MIB object persistences?

10) IF-MIB counters do not typically start at zero; a delta must be
calculated. This is a common misunderstanding for new MIB developers and
users.
I don't see any comparable discussion related to ietf-interfaces counters.
Where should one look for a discussion of YANG counter initialization
values?
Where should one look for a discussion of YANG counter rollover?
It would help to have a discussion of how to utilize discontinuity_time
and counters, especially for implementers not familiar with SNMP (and not
implementing IF-MIB).

11) Is it expected that counters in ietf-interfaces and counters in IF-MIB
are synchronized? Can an NM application reasonably compare two readings -
one of in-octets and one of ifHCInOctets? If not, I think that should be
made clear. (The reference clauses seem to link them)

12) From IF-MIB: "Discontinuities in the value of this counter can occur
at re-initialization of the management system, and at other times as
indicated by the value of ifCounterDiscontinuityTime."
>From ietf-interfaces: "Discontinuities in the value of this counter can
occur at re-initialization of the management system, and at other times as
indicated by the value of 'discontinuity-time'."
I think it is ambiguous as to whether both sets of text refer to the same
"management system". Is the IF-MIB management-system the SNMP agent? And
the YANG management-system the YANG server? Or are both based on the
underlying (e.g, hardware or native) management system?
Are ifCounterDiscontinuityTime and discontinuity-time synchronized or
independent? If they are independent, then the YANG counters and MIB
counters could contain very different values; it might help operators to
have this pointed out. It might help implementers to know whether to try
to synchronize them or not.
Can an operator force restart of both YANG and MIB systems to force
synchronization of counters?

13) Some of the questions about counters might be covered in yang-types;
it would help if the imports clause indicated the relevant RFCs.

14) IF-MIB has both 32-bit and 64-bit counters; YANG only duplicates the
64-bit counters, generally. It might be good to discuss this in an
Operations Considerations section, to explain some potential anomalies at
the NM application side.

15) ietf-interfaces can modify the SNMP trap-enable settings; enabling
lots of traps could impact denial of service, disabling could hide
interface changes made by an attacker; it should probably be mentioned in
security considerations.

16) Many operators/developers may have experience with IF-MIB, and some
applications might be rewritten to utilize ietf-interfaces rather than (or
to supplement) IF-MIB. Not all IF-MIB objects are reflected in
ietf-interfaces; it might be helpful to show which IF-MIB objects are not
mapped to ietf-interfaces, and discuss why, and whether comparable info
can be derived using other YANG approaches.

17) The copyright in the module description clause needs updating.

Hope this helps,
--
David Harrington
Ietfdbh@comcast.net
+1-603-828-1401





On 4/19/13 9:25 AM, "The IESG" <noreply@ietf.org> wrote:

>
>The IESG has received a request from the NETCONF Data Modeling Language
>WG (netmod) to consider the following document:
>- 'A YANG Data Model for Interface Management'
>  <draft-ietf-netmod-interfaces-cfg-10.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 2013-05-03. 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 document defines a YANG data model for the management of network
>   interfaces.  It is expected that interface type specific data models
>   augment the generic interfaces data model defined in this document.
>
>
>
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-ietf-netmod-interfaces-cfg/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-ietf-netmod-interfaces-cfg/ballot/
>
>
>No IPR declarations have been submitted directly on this I-D.
>
>



From lear@cisco.com  Mon Apr 22 13:31:12 2013
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 31FE121E80AF; Mon, 22 Apr 2013 13:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.885
X-Spam-Level: 
X-Spam-Status: No, score=-110.885 tagged_above=-999 required=5 tests=[AWL=-0.285, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3nd8AYzJduxY; Mon, 22 Apr 2013 13:31:11 -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 D21C321E8053; Mon, 22 Apr 2013 13:31:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=942; q=dns/txt; s=iport; t=1366662664; x=1367872264; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mNe8CJ4TRo5UM1CLP3+NilFSACAkaRfZrSKW+BUkiiQ=; b=CrWu3dVKCpm3vnqaFiDuOpiAdvyi4q3L9FE+TuddRscoFWstqIkeV7ao ZwVKWXUuivGVJ7x7/i4pXhZXyJIhZTwImC6RDMdO96628ZV/iLhIJhLbo 8t/V6RWMnmwZgCHcXByDwYkLsaisXsVaD9GtK34toeT0mPXer9ebWMTfz M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAP+cdVGQ/khM/2dsb2JhbABQgwaDZ71agQYWdIIfAQEBAwEjVQEQCw4KAgIFFgsCAgkDAgECAUUGDQEHAQGICgaqW5ElgSOOHAdjgVGBEwOXFZEagn8POg
X-IronPort-AV: E=Sophos;i="4.87,529,1363132800"; d="scan'208";a="13484189"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 22 Apr 2013 20:31:01 +0000
Received: from ams3-vpn-dhcp5433.cisco.com (ams3-vpn-dhcp5433.cisco.com [10.61.85.56]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3MKUxu7025898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Apr 2013 20:30:59 GMT
Message-ID: <51759E03.4030208@cisco.com>
Date: Mon, 22 Apr 2013 22:30:59 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <5174D69F.6090300@cisco.com> <51755FE9.9060809@si6networks.com> <517563C0.6000508@cisco.com> <51758E1F.80803@si6networks.com>
In-Reply-To: <51758E1F.80803@si6networks.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, 6man@ietf.org, Bob Hinden <bob.hinden@gmail.com>, 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, 22 Apr 2013 20:31:12 -0000

H Fernando,

On 4/22/13 9:23 PM, Fernando Gont wrote:
>
> There seems to be a disconnect here:
>
> We want an algorithm that, roughly speaking, whenever you connect to the
> same network, gives you the same address. But such address should be
> different for each network you connect to.

Thank you, and yes there was a disconnect.  Indeed now I get it.  For
some reason I had assumed that you meant for some short period of time,
but the algorithm is clearly aimed at longer periods of time (e.g.,
across reboots).  Given that, the inputs the WG has stated seem
perfectly reasonable.


>> How would an IPv6 implementation employing this specification vary from
>> this specification in a way you or the working group would find
>> objectionable?  
> If, for the same interface you employ this algorithm *and* the
> traditional SLAAC algorithm, that's objectionable.

Right.  With you now.

Thanks again...

Eliot


From clint.chaplin@gmail.com  Mon Apr 22 13:39:15 2013
Return-Path: <clint.chaplin@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 B937121E80C0; Mon, 22 Apr 2013 13:39:15 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17zUaQEcIklY; Mon, 22 Apr 2013 13:39:15 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id C03A221E80BB; Mon, 22 Apr 2013 13:39:14 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id h11so5165282wiv.2 for <multiple recipients>; Mon, 22 Apr 2013 13:39:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=yigrVzXwH1goF8jlYAC6WaqifN25sWSTmRGqBZ0fPiU=; b=Tju9fYPZ0TvpEwrUbW9392ygIP8jL2TIeeUDZBmYHlKKwkHvBe+Xtrv7F2eqkCykXF vq/+/nvxAuCK32jcjAMdGf4LhgZ7hPRt8bS008dxPY34lU/oysiPN/qSUQz4cZVUsBHl x5il6uT2okicpMo4mqXHDSZg7HmNVAsGNxp8R7Igg9EoUQli/UxYpN3f8tNI7ZIVPwTD K2c6vr8x3MoZi8mtjYnL5igj9auWai1AnXnfYSc4nzBf+cc4jN1Su9eti0jqfi19cFm3 hO08m62n8TQsdVSaTipj8QWW+KpQ+21Rl56rCyEChutBYkV2z9h0bgJUoZYS2Ivz4iTM QVKw==
MIME-Version: 1.0
X-Received: by 10.194.109.136 with SMTP id hs8mr56391627wjb.8.1366663153915; Mon, 22 Apr 2013 13:39:13 -0700 (PDT)
Received: by 10.194.90.68 with HTTP; Mon, 22 Apr 2013 13:39:13 -0700 (PDT)
In-Reply-To: <20130419132451.22330.4912.idtracker@ietfa.amsl.com>
References: <20130419132451.22330.4912.idtracker@ietfa.amsl.com>
Date: Mon, 22 Apr 2013 13:39:13 -0700
Message-ID: <CADn-GtjTXTQvXcrbEAyUNNX1qD0Hxc8SfU8=VzMDqn4OMF32iA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-netmod-ip-cfg-09.txt> (A YANG Data Model for IP Management) to Proposed Standard
From: Clint Chaplin <clint.chaplin@gmail.com>
To: IETF Discussion List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e0102e172d11f5904daf90fba
Cc: netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Apr 2013 20:39:15 -0000

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

Why did this (and the other most recent) last call also not go to
IETF-Announce?


On Fri, Apr 19, 2013 at 6:24 AM, The IESG <noreply@ietf.org> wrote:

>
> The IESG has received a request from the NETCONF Data Modeling Language
> WG (netmod) to consider the following document:
> - 'A YANG Data Model for IP Management'
>   <draft-ietf-netmod-ip-cfg-09.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 2013-05-03. 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 document defines a YANG data model for management of IP
>    implementations.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>


-- 
Clint (JOATMON) Chaplin
Principal Engineer
Standards & Technology Enabling
Advanced Technology Lab
Samsung R&D Institute America - Silicon Valley

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

<div dir=3D"ltr">Why did this (and the other most recent) last call also no=
t go to IETF-Announce?</div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Fri, Apr 19, 2013 at 6:24 AM, The IESG <span dir=3D"ltr=
">&lt;<a href=3D"mailto:noreply@ietf.org" target=3D"_blank">noreply@ietf.or=
g</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>
The IESG has received a request from the NETCONF Data Modeling Language<br>
WG (netmod) to consider the following document:<br>
- &#39;A YANG Data Model for IP Management&#39;<br>
=A0 &lt;draft-ietf-netmod-ip-cfg-09.txt&gt; as Proposed Standard<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-05=
-03. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In eith=
er case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=A0 =A0This document defines a YANG data model for management of IP<br>
=A0 =A0implementations.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/" targe=
t=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/</a><=
br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/ballot/=
" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cf=
g/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Clint (JOATM=
ON) Chaplin<br>Principal Engineer<br>Standards &amp; Technology Enabling<br=
>Advanced Technology Lab<br>Samsung R&amp;D Institute America - Silicon Val=
ley
</div>

--089e0102e172d11f5904daf90fba--

From sm@resistor.net  Mon Apr 22 13:40:36 2013
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 9804321E80DA for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 13:40:36 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eUn+5jAwS2my for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 13:40:35 -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 E0BA021E80BB for <ietf@ietf.org>; Mon, 22 Apr 2013 13:40:35 -0700 (PDT)
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 r3MKeQhP020192; Mon, 22 Apr 2013 13:40:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1366663231; bh=GTER9lwPguSbai6KukmiLy8ISk0RB1WuXbKVotxv6cY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=kzUD//SOaWuZf5uuLwxuna2E8//FREGQ/cW09yQbi1fN97Op1XYGxeguDcXulfaS7 6lenZ77X/NmuuOtYmoA5bwiMCXnLsRJHBUV6CNAogypx+nJGIY4FqFusFb7WRJslqp S8+c8kzg9zW1Z8q+FaGQj00b2sJSe8DwiUILg5X8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1366663231; i=@resistor.net; bh=GTER9lwPguSbai6KukmiLy8ISk0RB1WuXbKVotxv6cY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pxldzkb8QWDvl2jaEde0hwm3ueTFqyUWq0+vEXrPZmpIJtd/SMCoO3aJA2fX+br/G L/C2sVerTGQAXi4cipif6Y9TXpWA4D40l6wx/KybGCyA/edxcWz4H+Vk97cDmH/Zg6 iXHRmaHXbgD14/jwWgIisUo1uTU7E2d2joXSbcMY=
Message-Id: <6.2.5.6.2.20130422125704.0d551178@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 22 Apr 2013 13:39:32 -0700
To: Fernando Gont <fgont@si6networks.com>
From: SM <sm@resistor.net>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
In-Reply-To: <51759238.8000306@si6networks.com>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: RJ Atkinson <rja.lists@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: Mon, 22 Apr 2013 20:40:36 -0000

Hi Fernando,

Please note that this is not an objection.

At 12:40 22-04-2013, Fernando Gont wrote:
>PLease see the Appendix.

I read that.  I was confused by the short title (Stable Privacy 
Addresses) at first.  I didn't see much discussion in the draft about 
privacy considerations.  For what it is worth there isn't much in RFC 
4941 either.  I am not sure whether it is worth covering that angle 
in the draft; it may end up being too much work.

>Privacy addresses are employed in addition to traditional SLAAC
>addresses -- hence they don't mitigate address scanning. FWIW, this is
>all discussed in the I-D.

Yes, I read that.  Privacy is a bit more than address scanning.  From 
an implementation perspective the document is good.  It is difficult 
to tell how the document fits in the bigger (IPv6) picture.  I'll 
mention it; I am not suggesting that anything be done about it.

>It'd be "conditionally-compliant", but not fully-compliant.

It would be easier to say:

   It is RECOMMENDED that implementations provide a configuration option to
   enable or disable the use of this algorithm for generating Interface
   Identifiers.

I didn't include an explanation for the recommendation as it seems 
obvious to me.

BTW, you could steal some text from RFC 4941 for the 64-bit comment:

  "Note that an IPv6 identifier does not necessarily have to be 64 bits in
   length, but the algorithm specified in this document is targeted towards
   64-bit interface identifiers."

Regards,
-sm 


From presnick@qti.qualcomm.com  Mon Apr 22 18:44:24 2013
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 EB33121F8A0B; Mon, 22 Apr 2013 18:44:23 -0700 (PDT)
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.271, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CtpmdrNU41XS; Mon, 22 Apr 2013 18:44:23 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id ED19B21F89B0; Mon, 22 Apr 2013 18:44:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1366681462; x=1398217462; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=sAmVaOAhp68ga7BemkkpSGoejCT9iQfAAq2ehg29Jkc=; b=tRGPdXY8/LFNhSFH6gsxTp82a3wJLFCSHNZD7h5RFh+y0aGfdZpEqkjj xl4VVmp3SG0L2Hi3h/pjvfoK72xeCOQHXNqWrl+WBdFvd5a3BZdlNzMmz g2NvhdiwxEg9hebiXLFx1jmG1B9MIRmtIfd/ZigFN7dDdtn046khsEF5e M=;
X-IronPort-AV: E=Sophos;i="4.87,530,1363158000"; d="scan'208,217";a="36207554"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 22 Apr 2013 18:44:22 -0700
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 22 Apr 2013 18:44:22 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 22 Apr 2013 18:44:21 -0700
Message-ID: <5175E773.9050403@qti.qualcomm.com>
Date: Mon, 22 Apr 2013 20:44:19 -0500
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: Clint Chaplin <clint.chaplin@gmail.com>
Subject: Re: Last Call: <draft-ietf-netmod-ip-cfg-09.txt> (A YANG Data Model for IP Management) to Proposed Standard
References: <20130419132451.22330.4912.idtracker@ietfa.amsl.com> <CADn-GtjTXTQvXcrbEAyUNNX1qD0Hxc8SfU8=VzMDqn4OMF32iA@mail.gmail.com>
In-Reply-To: <CADn-GtjTXTQvXcrbEAyUNNX1qD0Hxc8SfU8=VzMDqn4OMF32iA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090305010305050707080401"
X-Originating-IP: [172.30.39.5]
Cc: IETF Discussion List <ietf@ietf.org>, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Apr 2013 01:44:24 -0000

--------------090305010305050707080401
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

It did go to IETF-Announce. It's just no longer in the To: field so 
people stop doing a reply-all and end up sending to it. (Basically, it's 
Bcc'ed. For e-mail geeks like me: An empty group list of 
"IETF-Announce:;" is now in the To: field.)

pr

On 4/22/13 3:39 PM, Clint Chaplin wrote:
> Why did this (and the other most recent) last call also not go to 
> IETF-Announce?
>
>
> On Fri, Apr 19, 2013 at 6:24 AM, The IESG <noreply@ietf.org 
> <mailto:noreply@ietf.org>> wrote:
>
>
>     The IESG has received a request from the NETCONF Data Modeling
>     Language
>     WG (netmod) to consider the following document:
>     - 'A YANG Data Model for IP Management'
>     <draft-ietf-netmod-ip-cfg-09.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 <mailto:ietf@ietf.org> mailing lists by 2013-05-03.
>     Exceptionally, comments may be
>     sent to iesg@ietf.org <mailto:iesg@ietf.org> instead. In either
>     case, please retain the
>     beginning of the Subject line to allow automated sorting.
>
>     Abstract
>
>
>        This document defines a YANG data model for management of IP
>        implementations.
>
>
>
>
>     The file can be obtained via
>     http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/
>
>     IESG discussion can be tracked via
>     http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/ballot/
>
>
>     No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>
> -- 
> Clint (JOATMON) Chaplin
> Principal Engineer
> Standards & Technology Enabling
> Advanced Technology Lab
> Samsung R&D Institute America - Silicon Valley

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
It did go to IETF-Announce. It's just no longer in the To: field so
people stop doing a reply-all and end up sending to it. (Basically,
it's Bcc'ed. For e-mail geeks like me: An empty group list of
"IETF-Announce:;" is now in the To: field.)<br>
<br>
pr<br>
<br>
On 4/22/13 3:39 PM, Clint Chaplin wrote:
<blockquote
 cite="mid:CADn-GtjTXTQvXcrbEAyUNNX1qD0Hxc8SfU8=VzMDqn4OMF32iA@mail.gmail.com"
 type="cite">
  <div dir="ltr">Why did this (and the other most recent) last call
also not go to IETF-Announce?</div>
  <div class="gmail_extra"><br>
  <br>
  <div class="gmail_quote">On Fri, Apr 19, 2013 at 6:24 AM, The IESG <span
 dir="ltr">&lt;<a moz-do-not-send="true" href="mailto:noreply@ietf.org"
 target="_blank">noreply@ietf.org</a>&gt;</span> wrote:<br>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
The IESG has received a request from the NETCONF Data Modeling Language<br>
WG (netmod) to consider the following document:<br>
- 'A YANG Data Model for IP Management'<br>
&nbsp; &lt;draft-ietf-netmod-ip-cfg-09.txt&gt; as Proposed Standard<br>
    <br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
    <a moz-do-not-send="true" href="mailto:ietf@ietf.org">ietf@ietf.org</a>
mailing lists by 2013-05-03. Exceptionally, comments may be<br>
sent to <a moz-do-not-send="true" href="mailto:iesg@ietf.org">iesg@ietf.org</a>
instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
    <br>
Abstract<br>
    <br>
    <br>
&nbsp; &nbsp;This document defines a YANG data model for management of IP<br>
&nbsp; &nbsp;implementations.<br>
    <br>
    <br>
    <br>
    <br>
The file can be obtained via<br>
    <a moz-do-not-send="true"
 href="http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/"
 target="_blank">http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/</a><br>
    <br>
IESG discussion can be tracked via<br>
    <a moz-do-not-send="true"
 href="http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/ballot/"
 target="_blank">http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/ballot/</a><br>
    <br>
    <br>
No IPR declarations have been submitted directly on this I-D.<br>
    <br>
    <br>
  </blockquote>
  </div>
  <br>
  <br clear="all">
  <div><br>
  </div>
-- <br>
Clint (JOATMON) Chaplin<br>
Principal Engineer<br>
Standards &amp; Technology Enabling<br>
Advanced Technology Lab<br>
Samsung R&amp;D Institute America - Silicon Valley
  </div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Pete Resnick <a class="moz-txt-link-rfc2396E" href="http://www.qualcomm.com/~presnick/">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Technologies, Inc. - +1 (858)651-4478</pre>
</body>
</html>

--------------090305010305050707080401--

From sm@resistor.net  Tue Apr 23 01:34:19 2013
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 A1FA921F8721 for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 01:34:19 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sN3gpYrU-4GF for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 01:34:19 -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 08D5921F871C for <ietf@ietf.org>; Tue, 23 Apr 2013 01:34:18 -0700 (PDT)
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 r3N8YB4J020828; Tue, 23 Apr 2013 01:34:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1366706055; bh=kxX4mo8e/zxv7Q+2qaY/0j1MCirmcPwzMgaXz0mUGGY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FRG/g1sPo6TCxG91lD/vzm9zdP8m1dZVLrltdcOSFE3kU1sKPudRgqLHLjq3x2amV MWsHtbnAsl14K7AbTbReVQsgQhrI7Wz/FHDEhry8rNVLpJ7uY2+4ioutBj/ihKzFdR /VmQ37WNh9lP8ow1zz77xe/u8/wzrCJDJHf+edj8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1366706055; i=@resistor.net; bh=kxX4mo8e/zxv7Q+2qaY/0j1MCirmcPwzMgaXz0mUGGY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uT3eAXcmMZl+kYw3aUhEoQS+lhF6hkz9n8mUsQJQO46uACppkRbnepBaFBAsOC3do RxG2VwyAUUDYBaVb1/5FvTJAobEJIerco2D12RyEDedAsAADm2x55GYMN7BBZMztW3 RpPSEkSts91LyszpoMFSkuKIhRjWrMVrUjMRFDD0=
Message-Id: <6.2.5.6.2.20130423005437.0c54f748@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 23 Apr 2013 01:33:01 -0700
To: Clint Chaplin <clint.chaplin@gmail.com>
From: SM <sm@resistor.net>
Subject: Noreply (was: Last Call: <draft-ietf-netmod-ip-cfg-09.txt> (A YANG Data Model for IP Management) to Proposed Standard)
In-Reply-To: <CADn-GtjTXTQvXcrbEAyUNNX1qD0Hxc8SfU8=VzMDqn4OMF32iA@mail.g mail.com>
References: <20130419132451.22330.4912.idtracker@ietfa.amsl.com> <CADn-GtjTXTQvXcrbEAyUNNX1qD0Hxc8SfU8=VzMDqn4OMF32iA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
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: Tue, 23 Apr 2013 08:34:19 -0000

Hi Clint,
At 13:39 22-04-2013, Clint Chaplin wrote:
>Why did this (and the other most recent) last=20
>call also not go to IETF-Announce?

Here are some partial headers:

   From: The IESG <noreply@ietf.org>
   To: IETF-Announce:;
   Subject: Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG=
 Data
         Model for Interface Management) to Proposed Standard
   Message-ID: <20130419132524.1622.39563.idtracker@ietfa.amsl.com>
   Date: Fri, 19 Apr 2013 06:25:24 -0700
   Cc: netmod@ietf.org
   Reply-To: IETF Discussion List <ietf@ietf.org>
   List-Id: "IETF announcement list. No discussions."=
 <ietf-announce.ietf.org>
   List-Post: <mailto:ietf-announce@ietf.org>

I don't know who had the idea [1] to have the=20
IESG use the noreply@ietf.org email address=20
[2].    The List-Post: mailto needs some work. :-)

Regards,
-sm

1. Morni=EB alanti=EB
2. In all cases, the "From:" field REALLY=20
[RFC6919] SHOULD NOT contain any mailbox that=20
does not belong to the author(s) of the message.


From daedulus@btconnect.com  Tue Apr 23 02:06:35 2013
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 40D0A21F964D for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 02:06:35 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEyGH+-sdy6L for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 02:06:34 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe002.messaging.microsoft.com [207.46.163.25]) by ietfa.amsl.com (Postfix) with ESMTP id D7AFE21F9424 for <ietf@ietf.org>; Tue, 23 Apr 2013 02:06:32 -0700 (PDT)
Received: from mail215-co9-R.bigfish.com (10.236.132.245) by CO9EHSOBE040.bigfish.com (10.236.130.103) with Microsoft SMTP Server id 14.1.225.23; Tue, 23 Apr 2013 09:06:24 +0000
Received: from mail215-co9 (localhost [127.0.0.1])	by mail215-co9-R.bigfish.com (Postfix) with ESMTP id 9BC4C220334; Tue, 23 Apr 2013 09:06:24 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.69; KIP:(null); UIP:(null); IPV:NLI; H:AMXPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371I542I1432I1418Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz17326ah8275bh8275dh1033ILz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah304l1155h)
Received: from mail215-co9 (localhost.localdomain [127.0.0.1]) by mail215-co9 (MessageSwitch) id 1366707982921331_29982; Tue, 23 Apr 2013 09:06:22 +0000 (UTC)
Received: from CO9EHSMHS021.bigfish.com (unknown [10.236.132.236])	by mail215-co9.bigfish.com (Postfix) with ESMTP id D4680480047; Tue, 23 Apr 2013 09:06:22 +0000 (UTC)
Received: from AMXPRD0711HT001.eurprd07.prod.outlook.com (157.56.250.69) by CO9EHSMHS021.bigfish.com (10.236.130.31) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 23 Apr 2013 09:06:21 +0000
Received: from DB3PRD0511HT004.eurprd05.prod.outlook.com (157.56.254.213) by pod51017.outlook.com (10.242.9.162) with Microsoft SMTP Server (TLS) id 14.16.293.5; Tue, 23 Apr 2013 09:06:19 +0000
Message-ID: <019d01ce4001$23376160$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Clint Chaplin <clint.chaplin@gmail.com>, IETF Discussion List <ietf@ietf.org>
References: <20130419132451.22330.4912.idtracker@ietfa.amsl.com> <CADn-GtjTXTQvXcrbEAyUNNX1qD0Hxc8SfU8=VzMDqn4OMF32iA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-netmod-ip-cfg-09.txt> (A YANG Data Modelfor IP Management) to Proposed Standard
Date: Tue, 23 Apr 2013 10:00:43 +0100
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.254.213]
X-FOPE-CRA-SourceIpAddress: 157.56.250.69
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: clint.chaplin@gmail.com
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, 23 Apr 2013 09:06:35 -0000

---- Original Message -----
From: "Clint Chaplin" <clint.chaplin@gmail.com>
To: "IETF Discussion List" <ietf@ietf.org>
Cc: <netmod@ietf.org>
Sent: Monday, April 22, 2013 9:39 PM
> Why did this (and the other most recent) last call also not go to
> IETF-Announce?

And I was wondering why I got four copies of it, three on April 20th,
one on April 22nd.  Partly it is having a different address for
ietf-announce as opposed to that for netmod, but it is also because they
come from both 'The IESG' and from the 'IETF Secretary', both to my
ietf-announce address (but none to my ietf-discuss address).

I think that the underlying issue is communication, that changes to a
system that affect how people work are best communicated in advance,
even when the benefits of a change are overwhelmingly beneficial to all
concerned:-)

Tom Petch

 On Fri, Apr 19, 2013 at 6:24 AM, The IESG <noreply@ietf.org> wrote:
>
> >
> > The IESG has received a request from the NETCONF Data Modeling
Language
> > WG (netmod) to consider the following document:
> > - 'A YANG Data Model for IP Management'
> >   <draft-ietf-netmod-ip-cfg-09.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 2013-05-03. 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 document defines a YANG data model for management of IP
> >    implementations.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-netmod-ip-cfg/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> >
>
>
> --
> Clint (JOATMON) Chaplin
> Principal Engineer
> Standards & Technology Enabling
> Advanced Technology Lab
> Samsung R&D Institute America - Silicon Valley
>



From daedulus@btconnect.com  Tue Apr 23 04:25:21 2013
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 0E62021F9654 for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 04:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.349
X-Spam-Level: 
X-Spam-Status: No, score=-4.349 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QW22eyw+CgmY for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 04:25:20 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe004.messaging.microsoft.com [216.32.180.187]) by ietfa.amsl.com (Postfix) with ESMTP id E225921F9627 for <ietf@ietf.org>; Tue, 23 Apr 2013 04:25:18 -0700 (PDT)
Received: from mail126-co1-R.bigfish.com (10.243.78.239) by CO1EHSOBE038.bigfish.com (10.243.66.103) with Microsoft SMTP Server id 14.1.225.23; Tue, 23 Apr 2013 11:25:18 +0000
Received: from mail126-co1 (localhost [127.0.0.1])	by mail126-co1-R.bigfish.com (Postfix) with ESMTP id 3EE30B401C1; Tue, 23 Apr 2013 11:25:18 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -29
X-BigFish: PS-29(zzbb2dI98dI9371I542I1432I1418I328cM168aJzz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz17326ah8275dh8275ch1033ILz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah304l1155h)
Received: from mail126-co1 (localhost.localdomain [127.0.0.1]) by mail126-co1 (MessageSwitch) id 1366716315405529_27940; Tue, 23 Apr 2013 11:25:15 +0000 (UTC)
Received: from CO1EHSMHS005.bigfish.com (unknown [10.243.78.244])	by mail126-co1.bigfish.com (Postfix) with ESMTP id 575E8980043; Tue, 23 Apr 2013 11:25:15 +0000 (UTC)
Received: from AMSPRD0710HT002.eurprd07.prod.outlook.com (157.56.249.85) by CO1EHSMHS005.bigfish.com (10.243.66.15) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 23 Apr 2013 11:25:14 +0000
Received: from DBXPRD0611HT002.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.160.165) with Microsoft SMTP Server (TLS) id 14.16.293.5; Tue, 23 Apr 2013 11:24:46 +0000
Message-ID: <006a01ce4014$7a145700$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: David Harrington <ietfdbh@comcast.net>, IETF Discussion List <ietf@ietf.org>
References: <CD9AEA34.2D304%ietfdbh@comcast.net>
Subject: Re: Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG DataModel for Interface Management) to Proposed Standard
Date: Tue, 23 Apr 2013 12:19:45 +0100
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.254.85]
X-FOPE-CRA-SourceIpAddress: 157.56.249.85
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: ietfdbh@comcast.net
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, 23 Apr 2013 11:25:21 -0000

David

A thoughtful assessment, and what it brings out for me is that we do not
have an Information Model:-(  That is, we could have reverse engineered
an Information Model from the IF-MIB and then produced a data model in
YANG, but that did not happen.  Rather, there is a new and different
(implicit) Information Model underlying the data model in YANG, as
opposed to the one for the IF-MIB, and that has surfaced a number of
times on the netmod list, not just for this module but equally for the
routing, system and ip modules.  The differences are not great, but they
are there.

So the question is, should we have the same Information Model in YANG as
in MIBs, or do we let them diverge?  and if they diverge, then do we
need to record that in some standard way?  I don't know, but think that
it needs discussing.  It may not be a big issue in the IETF but I am
sure that it will be for those who operate networks!

Tom Petch

----- Original Message -----
From: "David Harrington" <ietfdbh@comcast.net>
To: "IETF Discussion List" <ietf@ietf.org>
Sent: Monday, April 22, 2013 9:21 PM

> Hi,
>
> I have reviewed this document and feel that is almost ready for
approval.
> This document defines a new data model in YANG format, based on the
same
> information model as the Interfaces MIB module (IF-MIB).
> Effectively, the YANG model is a second (duplicative) standard for
much of
> the same information.
> It is expected that devices may implement both the MIB and the YANG
data
> models.
>
> My primary concern regards co-existence and synchronization across
data
> models.
> I think this document would benefit from an Operational Considerations
> section that discusses synchronization, or an explanation why they
might
> reasonably be out-of-sync.
> Here are a few points to consider:
>
> 1) the ifIndex of an interface is used within the YANG model, matching
the
> ifIndex in IF-MIB.
> RFC2863 discusses the fact that ifIndex numbering might change during
> hot-swaps.
> This document does not discuss the need to ensure that IF-MIB ifIndex
> changes need to be reflected in the YANG model.
> The ifIndex in the YANG module must match that in IF-MIB (really, that
in
> the underlying instrumentation).
> Failure to sync the ifIndex could lead NM applications to confuse
which
> already-retrieved data records are related to which interface.
> This could cause an NM application to misinterpret/corrupt gathered
> trending information, and possibly to apply changes to the wrong
> interfaces.
>
> 2) ifType - can an interface be hot-swapped to use a different type?
Is
> this discussed someplace?
>
> 3) ifType - the description says the value of this mandatory object
MAY be
> initialized. What value should an NM application expect if it is NOT
> initialized?
>
> 4) enabled - "Systems that implement the IF-MIB use the value of this
leaf
> to set IF-MIB.ifAdminStatus ..."; should this be a MAY/SHOULD/MUST?
How
> will this coexist with SNMP-based NM applications? Is there potential
for
> conflict? What if NETCONF sets this as enabled, then an operator sets
it
> to disabled via SNMP?
> Does NETCONF know that its "enable" value (adminStatus) is out of
date?
> (does it matter? See note 7).
> What if the NETCONF system directky changes the underlying
instrumentation
> for adminstatus without going through the MIB?
>
> 5) is there a reason why "description" value MAY match IF-MIB ifAlias
> ***and MAY restrict the values***?
> Is there a particular use case for this lack of standardization of
> restrictions across data models?
> The persistence is a pretty important restriction related to the
> functionality of ifAlias, and the dynamism of ifIndex.
> If NETCONF is used to set the value, ignoring IF-MIB restrictions,
what
> happens to IF-MIB ifAlias as a persistent "handle" to the interface?
>
> 6) What error is returned via NETCONF if YANG attempts to set a value
that
> violates the SNMP agent implementation restrictions, and the SNMP
agent
> refuses the requested SET operation to ifAlias?
> Is there a simple way for an operator to tell whether the
implementation
> supports the restrictions (other than deliberately triggering an
error)?
>
> 7) what should an NM application or operator do if the YANG
oper-status
> and the IF-MIB operStatus differ?
> IF-MIB has substantial discussion of the relationship between
> ifAdminStatus and ifOperStatus. The YANG module doesn't have a
comparable
> discussion.
> Given that there could e additional delay incurred between setting
enable,
> updating ifAdminStatus, the change to ifOperStatus, and the update to
> oper-status, I recommend some mention in the description of enable
and/or
> oper-status of the detailed description in RFC2863, and applicability
to
> ietf-interfaces.
>
> 8) link-up-down-trap-enable: The text says this "indicates" whether
traps
> should be generated for the interface; shouldn't this be "configures"?
>
> 9) persistence isn't discussed in the config object descriptions. Do
they
> match the IF-MIB object persistences?
>
> 10) IF-MIB counters do not typically start at zero; a delta must be
> calculated. This is a common misunderstanding for new MIB developers
and
> users.
> I don't see any comparable discussion related to ietf-interfaces
counters.
> Where should one look for a discussion of YANG counter initialization
> values?
> Where should one look for a discussion of YANG counter rollover?
> It would help to have a discussion of how to utilize
discontinuity_time
> and counters, especially for implementers not familiar with SNMP (and
not
> implementing IF-MIB).
>
> 11) Is it expected that counters in ietf-interfaces and counters in
IF-MIB
> are synchronized? Can an NM application reasonably compare two
readings -
> one of in-octets and one of ifHCInOctets? If not, I think that should
be
> made clear. (The reference clauses seem to link them)
>
> 12) From IF-MIB: "Discontinuities in the value of this counter can
occur
> at re-initialization of the management system, and at other times as
> indicated by the value of ifCounterDiscontinuityTime."
> From ietf-interfaces: "Discontinuities in the value of this counter
can
> occur at re-initialization of the management system, and at other
times as
> indicated by the value of 'discontinuity-time'."
> I think it is ambiguous as to whether both sets of text refer to the
same
> "management system". Is the IF-MIB management-system the SNMP agent?
And
> the YANG management-system the YANG server? Or are both based on the
> underlying (e.g, hardware or native) management system?
> Are ifCounterDiscontinuityTime and discontinuity-time synchronized or
> independent? If they are independent, then the YANG counters and MIB
> counters could contain very different values; it might help operators
to
> have this pointed out. It might help implementers to know whether to
try
> to synchronize them or not.
> Can an operator force restart of both YANG and MIB systems to force
> synchronization of counters?
>
> 13) Some of the questions about counters might be covered in
yang-types;
> it would help if the imports clause indicated the relevant RFCs.
>
> 14) IF-MIB has both 32-bit and 64-bit counters; YANG only duplicates
the
> 64-bit counters, generally. It might be good to discuss this in an
> Operations Considerations section, to explain some potential anomalies
at
> the NM application side.
>
> 15) ietf-interfaces can modify the SNMP trap-enable settings; enabling
> lots of traps could impact denial of service, disabling could hide
> interface changes made by an attacker; it should probably be mentioned
in
> security considerations.
>
> 16) Many operators/developers may have experience with IF-MIB, and
some
> applications might be rewritten to utilize ietf-interfaces rather than
(or
> to supplement) IF-MIB. Not all IF-MIB objects are reflected in
> ietf-interfaces; it might be helpful to show which IF-MIB objects are
not
> mapped to ietf-interfaces, and discuss why, and whether comparable
info
> can be derived using other YANG approaches.
>
> 17) The copyright in the module description clause needs updating.
>
> Hope this helps,
> --
> David Harrington
> Ietfdbh@comcast.net
> +1-603-828-1401
>
>
>
>
>
> On 4/19/13 9:25 AM, "The IESG" <noreply@ietf.org> wrote:
>
> >
> >The IESG has received a request from the NETCONF Data Modeling
Language
> >WG (netmod) to consider the following document:
> >- 'A YANG Data Model for Interface Management'
> >  <draft-ietf-netmod-interfaces-cfg-10.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 2013-05-03. 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 document defines a YANG data model for the management of
network
> >   interfaces.  It is expected that interface type specific data
models
> >   augment the generic interfaces data model defined in this
document.
> >
> >
> >
> >
> >The file can be obtained via
> >http://datatracker.ietf.org/doc/draft-ietf-netmod-interfaces-cfg/
> >
> >IESG discussion can be tracked via
>
>http://datatracker.ietf.org/doc/draft-ietf-netmod-interfaces-cfg/ballot
/
> >
> >
> >No IPR declarations have been submitted directly on this I-D.
> >
> >
>
>
>



From markzzzsmith@yahoo.com.au  Mon Apr 22 13:07:57 2013
Return-Path: <markzzzsmith@yahoo.com.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 2650B21E80D0 for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 13:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.201
X-Spam-Level: 
X-Spam-Status: No, score=0.201 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, MANGLED_OFF=2.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEqWWaNqCrqU for <ietf@ietfa.amsl.com>; Mon, 22 Apr 2013 13:07:57 -0700 (PDT)
Received: from nm19.bullet.mail.bf1.yahoo.com (nm19.bullet.mail.bf1.yahoo.com [98.139.212.178]) by ietfa.amsl.com (Postfix) with SMTP id 40FA821E80D2 for <ietf@ietf.org>; Mon, 22 Apr 2013 13:07:56 -0700 (PDT)
Received: from [98.139.214.32] by nm19.bullet.mail.bf1.yahoo.com with NNFMP; 22 Apr 2013 20:07:55 -0000
Received: from [98.139.212.219] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 22 Apr 2013 20:07:55 -0000
Received: from [127.0.0.1] by omp1028.mail.bf1.yahoo.com with NNFMP; 22 Apr 2013 20:07:55 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 548271.44182.bm@omp1028.mail.bf1.yahoo.com
Received: (qmail 23424 invoked by uid 60001); 22 Apr 2013 20:07:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1366661275; bh=YyPd6jZbRH2AfgZES2i9SO27DVZr6de+ZveDZJk8D+U=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Xbj9DcfAehdPNAeJ9stWStE11Vd9UPQ1IcU1XPbkMQQwT1FTliIGs/1DXgyym2pw8PGFlflMk0jPLeQtjGgBeiocDUCCO752Qlf22hIz+9UCU5Wb2DBSmjAw7L4mWG9j6/Qt+oGqQrcnvUyXJeXNISHObrFYQQRwnDdxhIZMPYk=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=YbiDl0iQVbUIsok14FGiuLGHG6IJzltnUeYViU42zfdmfX8C9p6ErzQS+Jh6upbVNsy3EobvkPsuSfFrLjBviyxhJqzUXxgwDpEdisgrPI0jloZHjgZWwG9DoHYpsXe3C3kw66LIG01zrGU/nFIvUshjCqlPTkzYTmJlSHiP1qA=;
X-YMail-OSG: VwG2_egVM1ks8XysOM0LAt2Wki2Z9UEnPrj2gyVr.k9B1eP brB53BzEdA.A5iq0-
Received: from [150.101.221.237] by web142506.mail.bf1.yahoo.com via HTTP; Mon, 22 Apr 2013 13:07:54 PDT
X-Rocket-MIMEInfo: 002.001, CgpIaSwKCjxzbmlwPgoKPiAKPj4gIEknbSBub3QgdGhpbmtpbmcgb2YgdG9kYXkgYnV0IHRoZSBmdXR1cmUuwqAgQW5kIHllcywgYW5vdGhlcgo.PiAgYXJndW1lbnQgd291bGQgYmUgdGhhdCB0aGVyZSBpc24ndCBlbm91Z2ggYWRkcmVzcyBzcGFjZSBmb3IgdGhpcyB0byBiZQo.PiAgZWZmZWN0aXZlbHkgcHJpdmF0ZS7CoCBUaG9zZSBhcmUgdHdvIGRpZmZlcmVudCBpc3N1ZXMsIGJ1dCBmaXhpbmcgdGhlCj4.ICBib3VuZGFyeSBoZXJlIHJlbWluZHMgbWUgb2YgbWlzdGFrZXMgd2UgbWFkZSB3aXRoIElQdjQBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.141.536
References: <5174D69F.6090300@cisco.com> <51755FE9.9060809@si6networks.com> <517563C0.6000508@cisco.com> <51758E1F.80803@si6networks.com>
Message-ID: <1366661274.23349.YahooMailNeo@web142506.mail.bf1.yahoo.com>
Date: Mon, 22 Apr 2013 13:07:54 -0700 (PDT)
From: Mark Smith <markzzzsmith@yahoo.com.au>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
To: Fernando Gont <fgont@si6networks.com>, Eliot Lear <lear@cisco.com>
In-Reply-To: <51758E1F.80803@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 23 Apr 2013 09:25:42 -0700
Cc: "draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org" <draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org>, "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Mark Smith <markzzzsmith@yahoo.com.au>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Apr 2013 20:07:57 -0000

=0A=0AHi,=0A=0A<snip>=0A=0A> =0A>>  I'm not thinking of today but the futur=
e.=A0 And yes, another=0A>>  argument would be that there isn't enough addr=
ess space for this to be=0A>>  effectively private.=A0 Those are two differ=
ent issues, but fixing the=0A>>  boundary here reminds me of mistakes we ma=
de with IPv4 way back when. =0A>>  In this day and age we're talking about =
a lot more cleanup later.=0A> =0A> I guess this raises a more fundamental q=
uestion with respect to whether=0A> we want 64-bit identifiers to be the st=
andard, or not.=0A> =0A> A compromise might be to add a *parenthetical* not=
e such as:=0A> =0A> "The current IPv6 Addressing architecture defines Inter=
face-Identifiers=0A> to be 64 bits long, hence the low-order 64-bits of F()=
 are employed for=0A> the Interface-ID. Were the IPv6 Addressing Architectu=
re updated to allow=0A> any arbitrary length for the Interface ID, an imple=
mentation would need=0A> to be prepared to select as many bits from F() (ra=
ther than the fixed=0A> 64-bits specified above) for the Interface ID, such=
 that an Interface ID=0A> of appropriate length is obtained"=0A> =0A> I'd p=
ersonally have no issues with that *if* the wg agrees. But I=0A> wouldn't w=
ant to remove the text on grabbing the low-order 64-bits,=0A> since that's =
makes the spec more clear for the current times.=0A>=A0=0A=0AWhile this par=
t of RFC4291 should make the 64 bit statements safe:=0A=0A"For all unicast =
addresses, except those that start with the binary=0A=A0 =A0value 000, Inte=
rface IDs are required to be 64 bits long and to be=0A=A0 =A0constructed in=
 Modified EUI-64 format."=0A=0AThe /127 prefix length RFC changed that, so =
I'd suggest it might be safer to generalise and say take the number of bits=
 from the hash that correspond to the IID length in use, and then reference=
 64 bit IIDs as an example.=0A=0A=0ARegards,=0AMark.

From fgont@si6networks.com  Tue Apr 23 09:37:08 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A59BB21F971E for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 09:37:08 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a736bLXdVBXI for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 09:37:08 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 12B0421F971C for <ietf@ietf.org>; Tue, 23 Apr 2013 09:37:07 -0700 (PDT)
Received: from [186.134.53.35] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UUgDB-0004ze-69; Tue, 23 Apr 2013 18:36:57 +0200
Message-ID: <5176B8A2.40809@si6networks.com>
Date: Tue, 23 Apr 2013 11:36:50 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net>
In-Reply-To: <6.2.5.6.2.20130422125704.0d551178@resistor.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: RJ Atkinson <rja.lists@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: Tue, 23 Apr 2013 16:37:08 -0000

On 04/22/2013 03:39 PM, SM wrote:
> At 12:40 22-04-2013, Fernando Gont wrote:
>> PLease see the Appendix.
> 
> I read that.  I was confused by the short title (Stable Privacy
> Addresses) at first.  I didn't see much discussion in the draft about
> privacy considerations. 

There's some discussion in the Intro and the Appendix.


> For what it is worth there isn't much in RFC
> 4941 either.  I am not sure whether it is worth covering that angle in
> the draft; it may end up being too much work.

What (specifically) do you have in mind? Both RFC4941 and this document
note that if you use the underlying IEEE identifier for the IID, that
becoames a "super cookie" that allows correlations. Is the much more to
say on the subject than that?



>> Privacy addresses are employed in addition to traditional SLAAC
>> addresses -- hence they don't mitigate address scanning. FWIW, this is
>> all discussed in the I-D.
> 
> Yes, I read that.  Privacy is a bit more than address scanning.  

Agreed.


> From an
> implementation perspective the document is good.  It is difficult to
> tell how the document fits in the bigger (IPv6) picture. 

For (auto-configured) stable addresses you have two choices:
* traditional slacc addresses
* draft-ietf-stable-privacy-addresses



>> It'd be "conditionally-compliant", but not fully-compliant.
> 
> It would be easier to say:
> 
>   It is RECOMMENDED that implementations provide a configuration option to
>   enable or disable the use of this algorithm for generating Interface
>   Identifiers.

Can't "SHOULD" and "RECOMMENDED" be used interchangeably?



> BTW, you could steal some text from RFC 4941 for the 64-bit comment:
> 
>  "Note that an IPv6 identifier does not necessarily have to be 64 bits in
>   length, but the algorithm specified in this document is targeted towards
>   64-bit interface identifiers."

Well this is not that different from the current text -- still ties the
document to 64-bit IIDs.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From huitema@microsoft.com  Tue Apr 23 09:42:51 2013
Return-Path: <huitema@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 D856021F972D; Tue, 23 Apr 2013 09:42:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n7HWCAodo+q1; Tue, 23 Apr 2013 09:42:51 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0205.outbound.protection.outlook.com [207.46.163.205]) by ietfa.amsl.com (Postfix) with ESMTP id B176C21F972B; Tue, 23 Apr 2013 09:42:50 -0700 (PDT)
Received: from BL2FFO11HUB020.protection.gbl (10.173.160.112) by BL2FFO11HUB027.protection.gbl (10.173.161.51) with Microsoft SMTP Server (TLS) id 15.0.675.0; Tue, 23 Apr 2013 16:42:49 +0000
Received: from BL2FFO11FD013.protection.gbl (10.173.161.201) by BL2FFO11HUB020.protection.gbl (10.173.160.112) with Microsoft SMTP Server (TLS) id 15.0.675.0; Tue, 23 Apr 2013 16:42:48 +0000
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD013.mail.protection.outlook.com (10.173.160.221) with Microsoft SMTP Server (TLS) id 15.0.675.0 via Frontend Transport; Tue, 23 Apr 2013 16:42:48 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.175]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.02.0318.003; Tue, 23 Apr 2013 16:41:44 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>, Eliot Lear <lear@cisco.com>
Subject: RE: last call comments for draft-ietf-6man-stable-privacy-addresses-06
Thread-Topic: last call comments for draft-ietf-6man-stable-privacy-addresses-06
Thread-Index: AQHOPyGOslmR5sKVOkuNgHIrtQl435jiaE2AgAAElACAADKDgIABYycg
Date: Tue, 23 Apr 2013 16:41:43 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0C050F0C@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <5174D69F.6090300@cisco.com> <51755FE9.9060809@si6networks.com> <517563C0.6000508@cisco.com> <51758E1F.80803@si6networks.com>
In-Reply-To: <51758E1F.80803@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.74]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(51856001)(56816002)(55846006)(69226001)(44976003)(47976001)(31966008)(65816001)(23676002)(54356001)(63696002)(33656001)(53806001)(4396001)(47446002)(50986001)(74662001)(81542001)(80022001)(621065001)(59766001)(47776003)(74502001)(73894001)(79102001)(20776003)(46102001)(77982001)(16406001)(56776001)(6806003)(76482001)(66066001)(49866001)(47736001)(81342001)(50466001)(54316002); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB020; H:TK5EX14HUBC104.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-Forefront-PRVS: 08252193F3
X-OriginatorOrg: microsoft.onmicrosoft.com
Cc: "draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org" <draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org>, "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, 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: Tue, 23 Apr 2013 16:42:52 -0000

Pj4gU29ycnkgSSB3YXNuJ3QgY2xlYXI6IHdoYXQgaXMgdGhlIGJlbmVmaXQgb2Ygc3BlY2lmeWlu
ZyB0aGUgYWxnb3JpdGhtLCANCj4+IHdoZW4gc2ltcGx5IHBvcHBpbmcgb3V0IGFub3RoZXIgUFJG
IHdpbGwgaW4ganVzdCBhYm91dCBhbnkgaW5zdGFuY2UgZG8gDQo+PiB0aGUgam9iICh1bmxlc3Mg
eW91IGFyZSByZWluaXRpYWxpemluZyB0aGUgUFJGIHdpdGggdGhlIHNhbWUgc2VlZCk/DQo+DQo+
IFRoZXJlIHNlZW1zIHRvIGJlIGEgZGlzY29ubmVjdCBoZXJlOg0KPg0KPiBXZSB3YW50IGFuIGFs
Z29yaXRobSB0aGF0LCByb3VnaGx5IHNwZWFraW5nLCB3aGVuZXZlciB5b3UgY29ubmVjdCB0byB0
aGUgc2FtZSBuZXR3b3JrLCBnaXZlcyB5b3UgdGhlIHNhbWUgYWRkcmVzcy4gQnV0IHN1Y2ggYWRk
cmVzcyBzaG91bGQgYmUgZGlmZmVyZW50IGZvciBlYWNoIG5ldHdvcmsgeW91IGNvbm5lY3QgdG8u
DQo+IA0KPiBUaGUgcXVlc3Rpb24gaGVyZSBpczogSG93IGRvIHlvdSBhY2hpZXZlIHRoYXQ/DQo+
DQo+IFlvdSBtaWdodCBhcmd1ZSB0aGF0LCBjbGVhcmx5LCB0aGUgYXV0b2NvbmYgcHJlZml4IG5l
ZWRzIHRvIGJlIHBhcnQgb2YgdGhlIHNlZWQgKEknZCBwZXJzb25hbGx5IG5vdCBleHBlY3QgZGV2
ZWxvcGVycyB0byBmaWd1cmUgdGhpcyBvbmUgb3V0KS4NCg0KVGhpcyBpcyB0aGUga2luZCBvZiBh
dHRpdHVkZSB0aGF0IHJlYWxseSBkb2VzIG5vdCBnbyB3ZWxsIHdpdGggYWN0dWFsIGRldmVsb3Bl
cnMuIFlvdSBhcmUgYmFzaWNhbGx5IHNheWluZyB0aGF0IHlvdSBleHBlY3QgZGV2ZWxvcGVycyB0
byBiZSB0b28gZHVtYiB0byB1bmRlcnN0YW5kIHdoYXQgdGhleSBhcmUgZG9pbmcsIGFuZCB0aHVz
IHlvdSBmZWVsIGNvbXBlbGxlZCB0byBzcGVjaWZ5IGFuIGFsZ29yaXRobSBpbiBpdHMgbW9zdCBt
aW51dGUgZGV0YWlscywgZXZlbiB0aG91Z2ggdGhlcmUgYXJlIGRvemVucyBvZiBlcXVhbGx5IGdv
b2Qgd2F5cyB0byBhY2hpZXZlIHRoZSBzYW1lIHJlc3VsdC4gVGhlIG5ldCByZXN1bHQgb2Ygc3Vj
aCBvdmVyLXNwZWNpZmljYXRpb24gaXMgdGhhdCBkZXZlbG9wZXJzIHdpbGwgZGlzY2FyZCB0aGUg
c3BlYyBhcyBhcnJvZ2FudCwgYW5kIGltcGxlbWVudCB3aGF0IHRoZXkgZmVsbCBsaWtlIGltcGxl
bWVudGluZy4gDQoNCi0tIENocmlzdGlhbiBIdWl0ZW1hDQoNCg0K

From huitema@microsoft.com  Tue Apr 23 10:02:56 2013
Return-Path: <huitema@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 D3C5E21F9709 for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 10:02:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bciTyxlX9mZr for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 10:02:55 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0210.outbound.protection.outlook.com [207.46.163.210]) by ietfa.amsl.com (Postfix) with ESMTP id 5874121F9703 for <ietf@ietf.org>; Tue, 23 Apr 2013 10:02:55 -0700 (PDT)
Received: from BL2FFO11FD007.protection.gbl (10.173.161.203) by BL2FFO11HUB019.protection.gbl (10.173.160.111) with Microsoft SMTP Server (TLS) id 15.0.675.0; Tue, 23 Apr 2013 17:02:51 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD007.mail.protection.outlook.com (10.173.161.3) with Microsoft SMTP Server (TLS) id 15.0.675.0 via Frontend Transport; Tue, 23 Apr 2013 17:02:50 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.175]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.02.0318.003; Tue, 23 Apr 2013 17:02:14 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>, SM <sm@resistor.net>
Subject: RE: last call comments for draft-ietf-6man-stable-privacy-addresses-06
Thread-Topic: last call comments for draft-ietf-6man-stable-privacy-addresses-06
Thread-Index: AQHOP15AmJeRabuWb0mZCsaFLdinaJjihbgAgAAeFQCAABByAIABToYAgAACAJA=
Date: Tue, 23 Apr 2013 17:02:13 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net> <5176B8A2.40809@si6networks.com>
In-Reply-To: <5176B8A2.40809@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.74]
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:(199002)(189002)(44976003)(63696002)(69226001)(76482001)(49866001)(50466001)(47736001)(51856001)(50986001)(56816002)(33656001)(55846006)(56776001)(47446002)(81542001)(77982001)(54356001)(31966008)(74662001)(79102001)(54316002)(46406003)(20776003)(59766001)(6806003)(53806001)(47776003)(81342001)(74502001)(47976001)(4396001)(65816001)(23726002)(66066001)(16406001)(46102001)(80022001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB019; H:TK5EX14MLTC102.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08252193F3
Cc: RJ Atkinson <rja.lists@gmail.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: Tue, 23 Apr 2013 17:02:56 -0000

After reading the document again, the main issue is that the document speci=
fies a solution to a problem by detailing a specific implementation, but do=
es not explain the design choices behind that solution. As such, we end up =
with an over constrained specification, which at the same time fails to exp=
lain the problems at hand. The specification aims at providing addresses th=
at are "stable and different," so that the same host connecting will have d=
ifferent and uncorrelated addresses when connecting to different networks, =
but will keep the same address when connecting repeatedly to the same netwo=
rk.=20

As Mike St-Johns pointed out, the solution is trivial: create a different r=
andom number each time the host connect to a new network; make sure that th=
e same random number is reused if the host reconnect to the same network. T=
he latter property can be achieved either by keeping of log of previously v=
isited networks and the corresponding address, or by using a "master random=
 number" and combining it with the identification of the visited network. I=
n theory, that's about all what the IETF ought to specify.

Instead, the draft goes into great details on how to actually implement the=
 random number generator. Apart from not being necessary, some of these det=
ails are wrong. For example, the suggested algorithm includes an "interface=
 index," but different operating systems have different ways of enumerating=
 interfaces, and the variations in enumeration could end up violating the "=
stable address" property.=20

I would suggest reworking the draft to separate a normative section, effect=
ively a variation of the 3 lines paragraph above, and an informational sect=
ion, the current specification of the algorithm as  "an example of a way to=
 achieve this result if the operating system meets certain condition, like =
stable interface identifiers."

I would also explain the inherent issues that have to be solved, e.g., swap=
ping interfaces, or enabling multi-homed hosts. And I would observe that th=
e DAD problem cannot be solved ina  reliable way.

-- Christian Huitema



From fgont@si6networks.com  Tue Apr 23 10:40:22 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54E1C21F91B2 for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 10:40:22 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q4KvHqQE834z for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 10:40:21 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 4854021F9157 for <ietf@ietf.org>; Tue, 23 Apr 2013 10:40:20 -0700 (PDT)
Received: from [186.134.53.35] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UUhCN-0006Yb-69; Tue, 23 Apr 2013 19:40:11 +0200
Message-ID: <5176C774.7080300@si6networks.com>
Date: Tue, 23 Apr 2013 12:40:04 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net> <5176B8A2.40809@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, RJ Atkinson <rja.lists@gmail.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: Tue, 23 Apr 2013 17:40:22 -0000

Hi, Christian,

On 04/23/2013 12:02 PM, Christian Huitema wrote:
> After reading the document again, the main issue is that the document
> specifies a solution to a problem by detailing a specific
> implementation,

I personally disagree (see below).


> but does not explain the design choices behind that
> solution. As such, we end up with an over constrained specification,
> which at the same time fails to explain the problems at hand.

Could you please elaborate?



> As Mike St-Johns pointed out, the solution is trivial:

Can you post an URL for such comment? -- Because I've not been able to
find anything sent by Mike along those lines.


[....]
> Instead, the draft goes into great details on how to actually
> implement the random number generator. 

I disagree. In the draft, F() is the PRF. Where in the I-D are we trying
to provide details on how to implement F()?


> Apart from not being
> necessary, some of these details are wrong. For example, the
> suggested algorithm includes an "interface index," but different
> operating systems have different ways of enumerating interfaces, and
> the variations in enumeration could end up violating the "stable
> address" property.

Which vaiations are you referring to?

(FWIW, this I-D does not require any particular namespeace fr the
INterface Index).



> I would also explain the inherent issues that have to be solved,
> e.g., swapping interfaces, or enabling multi-homed hosts.

FWIW, constant addreses when swapping interfaces is not really a goal f
tis dcument, but rather a byproduct of it.


> And I would
> observe that the DAD problem cannot be solved ina  reliable way.

Could you please elaborate?

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From lars@netapp.com  Tue Apr 23 10:40:30 2013
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 D86AB21F9552; Tue, 23 Apr 2013 10:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.111
X-Spam-Level: 
X-Spam-Status: No, score=-10.111 tagged_above=-999 required=5 tests=[AWL=-0.310, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-XBmHisBY-N; Tue, 23 Apr 2013 10:40:28 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id A7B7F21F93F1; Tue, 23 Apr 2013 10:40:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,536,1363158000"; d="scan'208";a="44007502"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 23 Apr 2013 10:40:28 -0700
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 r3NHeS2C012692; Tue, 23 Apr 2013 10:40:28 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.71]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0342.003; Tue, 23 Apr 2013 10:40:28 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "diversity@ietf.org" <diversity@ietf.org>
Subject: "emerging regions" IETF/IRTF discussion list
Thread-Topic: "emerging regions" IETF/IRTF discussion list
Thread-Index: AQHOQEmkRdQ0/GeXdUimBaMiF9S1YA==
Date: Tue, 23 Apr 2013 17:40:27 +0000
Message-ID: <6FFB3524-E59A-41CC-B535-1F977F355142@netapp.com>
References: <F79F3DD5-2313-49EF-AA89-F7EE246349AF@piuha.net> <516F085B.2000602@cs.tcd.ie> <516F1110.60001@gmail.com> <59349D98-BF88-436D-88B4-117E339D2095@netapp.com>
In-Reply-To: <59349D98-BF88-436D-88B4-117E339D2095@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D7298AD9EE0D0448BCF1F7E412B96FDA@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ericas@ietf.org" <ericas@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "ericas@ietf.org" <ericas@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, 23 Apr 2013 17:40:30 -0000

Hi,

On Apr 17, 2013, at 14:50, "Eggert, Lars" <lars@netapp.com> wrote:
> I've been talking to a few folks about whether there would be interest an=
d energy for a new IRTF RG focusing on - for the lack of a better term - "I=
nternet challenges and solutions for emerging regions." Basically, a forum =
where we can discuss the challenges the Internet is facing in those regions=
, and share experiences and proposals to successfully address some of those=
 challenges.
...
> I'd be thrilled to discuss this in more detail with interested folks. Thi=
s list, however, is probably not the place for this. Contact me directly, a=
nd maybe I'll set up a separate list under irtf.org.

I head the secretariat create a discussion list for "Emerging Regions Inter=
net Challenges And Solutions" aka ERICAS. Subscribe at https://www.ietf.org=
/mailman/listinfo/ericas and email the list at ericas@ietf.org.

Please feel free to invite everyone you feel should be involved in this dis=
cussion, IETF attendee or not!

Also, while I'll be on the list and at least initially act as administrator=
 in terms of whitelisting posts, etc., I do believe strongly that in order =
for this discussion/effort to be useful, it needs to be owned by and run by=
 a group of people from those emerging regions. So I encourage everyone to =
step up and actively shape the discussion!

Thanks,
Lars=

From lars@netapp.com  Tue Apr 23 10:44:37 2013
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 BF64121F962E; Tue, 23 Apr 2013 10:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.989
X-Spam-Level: 
X-Spam-Status: No, score=-9.989 tagged_above=-999 required=5 tests=[AWL=-0.189, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qqX607VTIJ0w; Tue, 23 Apr 2013 10:44:37 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 16E9321F9620; Tue, 23 Apr 2013 10:44:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,536,1363158000"; d="scan'208";a="44009222"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 23 Apr 2013 10:44:36 -0700
Received: from vmwexceht03-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.76.241]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r3NHiaYs004651; Tue, 23 Apr 2013 10:44:36 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.71]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.02.0342.003; Tue, 23 Apr 2013 10:44:36 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "<ericas@ietf.org>" <ericas@ietf.org>
Subject: Re: "emerging regions" IETF/IRTF discussion list
Thread-Topic: "emerging regions" IETF/IRTF discussion list
Thread-Index: AQHOQEmkRdQ0/GeXdUimBaMiF9S1YJjkiTYA
Date: Tue, 23 Apr 2013 17:44:36 +0000
Message-ID: <189939FA-7B6D-4ADB-83B9-E0CD8DD209B2@netapp.com>
References: <F79F3DD5-2313-49EF-AA89-F7EE246349AF@piuha.net> <516F085B.2000602@cs.tcd.ie> <516F1110.60001@gmail.com> <59349D98-BF88-436D-88B4-117E339D2095@netapp.com> <6FFB3524-E59A-41CC-B535-1F977F355142@netapp.com>
In-Reply-To: <6FFB3524-E59A-41CC-B535-1F977F355142@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2094F9B94463A64290EE96CB91C8E3C0@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<diversity@ietf.org>" <diversity@ietf.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, 23 Apr 2013 17:44:37 -0000

CORRECTION: The list got created under irtf.org, i.e.:

Subscribe at https://www.irtf.org/mailman/listinfo/ericas and email the lis=
t at ericas@irtf.org.

Lars

(The list creation message I got from the system said it was created under =
both the IETF and IRTF domains, but apparently not.)

On Apr 23, 2013, at 10:40, Lars Eggert <lars@netapp.com> wrote:

> Hi,
>=20
> On Apr 17, 2013, at 14:50, "Eggert, Lars" <lars@netapp.com> wrote:
>> I've been talking to a few folks about whether there would be interest a=
nd energy for a new IRTF RG focusing on - for the lack of a better term - "=
Internet challenges and solutions for emerging regions." Basically, a forum=
 where we can discuss the challenges the Internet is facing in those region=
s, and share experiences and proposals to successfully address some of thos=
e challenges.
> ...
>> I'd be thrilled to discuss this in more detail with interested folks. Th=
is list, however, is probably not the place for this. Contact me directly, =
and maybe I'll set up a separate list under irtf.org.
>=20
> I head the secretariat create a discussion list for "Emerging Regions Int=
ernet Challenges And Solutions" aka ERICAS. Subscribe at https://www.ietf.o=
rg/mailman/listinfo/ericas and email the list at ericas@ietf.org.
>=20
> Please feel free to invite everyone you feel should be involved in this d=
iscussion, IETF attendee or not!
>=20
> Also, while I'll be on the list and at least initially act as administrat=
or in terms of whitelisting posts, etc., I do believe strongly that in orde=
r for this discussion/effort to be useful, it needs to be owned by and run =
by a group of people from those emerging regions. So I encourage everyone t=
o step up and actively shape the discussion!
>=20
> Thanks,
> Lars


From swb@internet2.edu  Tue Apr 23 10:48:15 2013
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 BB67F21F96B3; Tue, 23 Apr 2013 10:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.8
X-Spam-Level: 
X-Spam-Status: No, score=-5.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4A0Umq9dVs4S; Tue, 23 Apr 2013 10:48:15 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id 38C0F21F96B1; Tue, 23 Apr 2013 10:48:15 -0700 (PDT)
Received: from mail145-tx2-R.bigfish.com (10.9.14.249) by TX2EHSOBE002.bigfish.com (10.9.40.22) with Microsoft SMTP Server id 14.1.225.23; Tue, 23 Apr 2013 17:48:14 +0000
Received: from mail145-tx2 (localhost [127.0.0.1])	by mail145-tx2-R.bigfish.com (Postfix) with ESMTP id 62315201CD; Tue, 23 Apr 2013 17:48:14 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.237.101; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0810HT004.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 7
X-BigFish: S7(zzbb2dI98dIda00h1432Idc73hzz1f42h1fc6h1d77h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1082kzz8275dhz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1b1cn1b1bi1155h)
Received: from mail145-tx2 (localhost.localdomain [127.0.0.1]) by mail145-tx2 (MessageSwitch) id 1366739291771813_28920; Tue, 23 Apr 2013 17:48:11 +0000 (UTC)
Received: from TX2EHSMHS005.bigfish.com (unknown [10.9.14.228])	by mail145-tx2.bigfish.com (Postfix) with ESMTP id AEE71120043; Tue, 23 Apr 2013 17:48:11 +0000 (UTC)
Received: from BY2PRD0810HT004.namprd08.prod.outlook.com (157.56.237.101) by TX2EHSMHS005.bigfish.com (10.9.99.105) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 23 Apr 2013 17:48:10 +0000
Received: from internet2-95-45.internet2.edu (192.54.95.45) by pod51019.outlook.com (10.255.94.39) with Microsoft SMTP Server (TLS) id 14.16.299.2; Tue, 23 Apr 2013 17:48:03 +0000
Message-ID: <5176C952.2090602@internet2.edu>
Date: Tue, 23 Apr 2013 13:48:02 -0400
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: "emerging regions" IETF/IRTF discussion list
References: <F79F3DD5-2313-49EF-AA89-F7EE246349AF@piuha.net> <516F085B.2000602@cs.tcd.ie> <516F1110.60001@gmail.com> <59349D98-BF88-436D-88B4-117E339D2095@netapp.com> <6FFB3524-E59A-41CC-B535-1F977F355142@netapp.com> <189939FA-7B6D-4ADB-83B9-E0CD8DD209B2@netapp.com>
In-Reply-To: <189939FA-7B6D-4ADB-83B9-E0CD8DD209B2@netapp.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [192.54.95.45]
X-OriginatorOrg: internet2.edu
Cc: "<diversity@ietf.org>" <diversity@ietf.org>, "<ericas@ietf.org>" <ericas@ietf.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, 23 Apr 2013 17:48:15 -0000

On 04/23/13 13:44, Eggert, Lars allegedly wrote:
> CORRECTION: The list got created under irtf.org, i.e.:
> 
> Subscribe at https://www.irtf.org/mailman/listinfo/ericas and email the list at ericas@irtf.org.

If you subscribe at ietf, you get a confirmation request from irtf. :-)


From fgont@si6networks.com  Tue Apr 23 14:42:12 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D25B021F9349; Tue, 23 Apr 2013 14:42:11 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NHPsLRfp401c; Tue, 23 Apr 2013 14:42:11 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6234E21F933F; Tue, 23 Apr 2013 14:42:10 -0700 (PDT)
Received: from [186.134.53.35] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UUkyQ-0003vl-0b; Tue, 23 Apr 2013 23:42:02 +0200
Message-ID: <51770022.3050401@si6networks.com>
Date: Tue, 23 Apr 2013 16:41:54 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <5174D69F.6090300@cisco.com> <51755FE9.9060809@si6networks.com> <517563C0.6000508@cisco.com> <51758E1F.80803@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050F0C@TK5EX14MBXC273.redmond.corp.microsoft.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0C050F0C@TK5EX14MBXC273.redmond.corp.microsoft.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion <ietf@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org" <draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Apr 2013 21:42:12 -0000

On 04/23/2013 11:41 AM, Christian Huitema wrote:
>> You might argue that, clearly, the autoconf prefix needs to be part
>> of the seed (I'd personally not expect developers to figure this
>> one out).
> 
> This is the kind of attitude that really does not go well with actual
> developers. You are basically saying that you expect developers to be
> too dumb to understand what they are doing, 

You're misreading me.

I'm saying that developers work across across many different areas and
are busy people, and I cannot expect them to figure out stuff what *we*
were lazy or dumb enough to leave unspecified.

If I'm the guy producing a spec, my goal is to produce a spec that is
clear as possible, and only leave open those bits that are necessary to
leave open.


> and thus you feel
> compelled to specify an algorithm in its most minute details, even

That's incorrect. For instance, that's why we don't mandate a specific
PRF: because for that particular case, developers are in a better
position of judging what's the best PRF to use.


> though there are dozens of equally good ways to achieve the same
> result.

So far you have only mentioned one (recording the Prefix/IIDs pairs),
which IMHO is not elegant. Any others?

FWIW, you'll realize that e.g. RFC 4941 has even more detail than this spec.



> The net result of such over-specification is that developers
> will discard the spec as arrogant, and implement what they fell like
> implementing.

I cannot control people's thoughts. However, I'd say that I'm fairly
well-known for socializing stuff among developers, well-before a
document is published as an RFC.

Much of the work that I've done over these years have resulted in
patches from a variety of OSes, because I cared to discuss them with
developers. Of course, documents that I've authored have benefited from
input from developers during that discussion process.

(Not to mention that the contents of the documents I've written have
generally been very influenced by the input of a number of
participants... anyone who has ever sent me feedback on a document I've
authored/co-authored knows I do my best to address all feedback, no
matter whether that implies re-writing large portions of the document in
question.)

Make the spec as clear as possible save time and energy on all sides.

Cheers,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From huitema@microsoft.com  Tue Apr 23 17:46:23 2013
Return-Path: <huitema@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 E5BA721F937B; Tue, 23 Apr 2013 17:46:23 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhNI8O6T2JzK; Tue, 23 Apr 2013 17:46:22 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0205.outbound.protection.outlook.com [207.46.163.205]) by ietfa.amsl.com (Postfix) with ESMTP id A9DDF21F89DB; Tue, 23 Apr 2013 17:46:21 -0700 (PDT)
Received: from BL2FFO11FD028.protection.gbl (10.173.161.204) by BL2FFO11HUB039.protection.gbl (10.173.160.245) with Microsoft SMTP Server (TLS) id 15.0.675.0; Wed, 24 Apr 2013 00:46:20 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD028.mail.protection.outlook.com (10.173.161.107) with Microsoft SMTP Server (TLS) id 15.0.675.0 via Frontend Transport; Wed, 24 Apr 2013 00:46:20 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.175]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.02.0318.003; Wed, 24 Apr 2013 00:45:12 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: last call comments for draft-ietf-6man-stable-privacy-addresses-06
Thread-Topic: last call comments for draft-ietf-6man-stable-privacy-addresses-06
Thread-Index: AQHOPyGOslmR5sKVOkuNgHIrtQl435jiaE2AgAAElACAADKDgIABYycggABV7wCAADE0IA==
Date: Wed, 24 Apr 2013 00:45:12 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0C051AE7@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <5174D69F.6090300@cisco.com> <51755FE9.9060809@si6networks.com> <517563C0.6000508@cisco.com> <51758E1F.80803@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050F0C@TK5EX14MBXC273.redmond.corp.microsoft.com> <51770022.3050401@si6networks.com>
In-Reply-To: <51770022.3050401@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.74]
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:(189002)(199002)(23726002)(49866001)(50986001)(33656001)(6806003)(47736001)(16406001)(4396001)(47976001)(55846006)(56816002)(76482001)(66066001)(50466001)(47776003)(44976003)(53806001)(63696002)(20776003)(81342001)(56776001)(46406003)(74502001)(51856001)(69226001)(79102001)(54356001)(81542001)(80022001)(47446002)(46102001)(74662001)(54316002)(59766001)(77982001)(31966008)(65816001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB039; H:TK5EX14HUBC102.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0826B2F01B
Cc: "draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org" <draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org>, "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, 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: Wed, 24 Apr 2013 00:46:24 -0000

> If I'm the guy producing a spec, my goal is to produce a spec that is cle=
ar as possible, and only leave open those bits that are necessary to leave =
open.

Well, that might work for internal specs when you are managing a project, b=
ut that's probably not the right way to approach standards. A standard, bei=
ng the rules of the network, shall only constrain what must be constrained =
for interoperability.=20

All implementations are tradeoffs. Developers will necessarily make them, b=
ased on the different resource, priorities, usage scenarios. It is much bet=
ter to explain to give clear guidelines than to merely mandate an implement=
ation.

-- Christian Huitema



From fgont@si6networks.com  Tue Apr 23 18:28:56 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98F7821F931E; Tue, 23 Apr 2013 18:28:56 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Igu+3NE-ZqZ; Tue, 23 Apr 2013 18:28:56 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 07C0F21F910E; Tue, 23 Apr 2013 18:28:55 -0700 (PDT)
Received: from [186.134.53.35] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UUoVo-0002ly-A7; Wed, 24 Apr 2013 03:28:44 +0200
Message-ID: <51773526.9010605@si6networks.com>
Date: Tue, 23 Apr 2013 20:28:06 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <5174D69F.6090300@cisco.com> <51755FE9.9060809@si6networks.com> <517563C0.6000508@cisco.com> <51758E1F.80803@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050F0C@TK5EX14MBXC273.redmond.corp.microsoft.com> <51770022.3050401@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C051AE7@TK5EX14MBXC273.redmond.corp.microsoft.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0C051AE7@TK5EX14MBXC273.redmond.corp.microsoft.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org" <draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org>, "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, 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: Wed, 24 Apr 2013 01:28:56 -0000

On 04/23/2013 07:45 PM, Christian Huitema wrote:
>> If I'm the guy producing a spec, my goal is to produce a spec that
>> is clear as possible, and only leave open those bits that are
>> necessary to leave open.
> 
> Well, that might work for internal specs when you are managing a
> project, but that's probably not the right way to approach standards.

That probably depends on *what* you're specifying (please see below).


> A standard, being the rules of the network, shall only constrain what
> must be constrained for interoperability.

This document is not about a rule of the network, but about a local
policy. Therefore, by definition, as long as the address you select is
unique, nothing in this document will affect interoperability.



> All implementations are tradeoffs. Developers will necessarily make
> them, based on the different resource, priorities, usage scenarios.
> It is much better to explain to give clear guidelines than to merely
> mandate an implementation.

We probably have different views here. We're not mandating an
implementation (e.g., we're not mandating any specific PRF for F(), nor
how you store addresses in memory if you do store them).

I see the algorithm in this document as giving more room for tradeoffs
to developers than RFC4941, and the same room for tradeoffs as e.g. RFC6528.

Based on the above, me, I don't find the idea of re-writing the I-D
compelling -- particularly at this point in time.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From sm@resistor.net  Tue Apr 23 22:11:01 2013
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 4FC5221F91A3 for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 22:11:01 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W2+Zw2U-3vEG for <ietf@ietfa.amsl.com>; Tue, 23 Apr 2013 22:11:00 -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 0B7A421F8DDD for <ietf@ietf.org>; Tue, 23 Apr 2013 22:10:59 -0700 (PDT)
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 r3O5AmfS029709; Tue, 23 Apr 2013 22:10:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1366780254; bh=F5LP5ARoWU6x755iWbKwPDVlQtuY+4Ysza98MIIVzck=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=owPVwN5F+3sRpnB8Z/fMvB5n1HEchpYdYaoE4B4LB4YZTgnMaoYMOQlOPN1ucWEiA SFKRGwq1kC2e/tKtuotrbvr41WMWs0mDCZCRUTX8wD7VuuGxIBU+TLnDbgeyv8u05y gkO5UV4NqjO+TjKDQinquXYbDSNqJWQuV/2anQ5A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1366780254; i=@resistor.net; bh=F5LP5ARoWU6x755iWbKwPDVlQtuY+4Ysza98MIIVzck=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qQqTjkOvyxGc6n6Io7fJberv7tqWstCvsdjS8kqWFTd6B2j9SKcroTxfsWmzd/BhE 7VLxpJf9fdJ7AJc+6H/ShMckLBPcM3ON8k7GMmeg46JQJTpX3zmnQSBCDz2oM9ihE2 saoHIwTEjl1zisT5UgKpNT9Dm0ZEjCGdlypoXz74=
Message-Id: <6.2.5.6.2.20130423202702.0ba95de8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 23 Apr 2013 21:59:49 -0700
To: Fernando Gont <fgont@si6networks.com>
From: SM <sm@resistor.net>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
In-Reply-To: <5176B8A2.40809@si6networks.com>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net> <5176B8A2.40809@si6networks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: RJ Atkinson <rja.lists@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: Wed, 24 Apr 2013 05:11:01 -0000

Hi Fernando,
At 09:36 23-04-2013, Fernando Gont wrote:
>What (specifically) do you have in mind? Both RFC4941 and this document
>note that if you use the underlying IEEE identifier for the IID, that
>becoames a "super cookie" that allows correlations. Is the much more to
>say on the subject than that?

I don't have anything in mind at the moment.  I suggest ignoring 
it.  I don't want to give anyone a reason to generate a DISCUSS. :-)

>Can't "SHOULD" and "RECOMMENDED" be used interchangeably?

Please note that this is my opinion only.  The short answer is yes.

I don't use the two interchangeably.  I used "RECOMMENDED" as it was 
to provide advice.  Here are two examples:

  (i)  The person RECOMMENDED that this matter be dropped.

  (ii) The person stated that this matter SHOULD be dropped.

The second example may sound oppressive.

Regards,
-sm 


From peter@akayla.com  Tue Apr 23 22:56:17 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2EDA21F93AB; Tue, 23 Apr 2013 22:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dSoyWZweykaK; Tue, 23 Apr 2013 22:56:17 -0700 (PDT)
Received: from p3plsmtpa09-07.prod.phx3.secureserver.net (p3plsmtpa09-07.prod.phx3.secureserver.net [173.201.193.236]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC5A21F94A9; Tue, 23 Apr 2013 22:56:16 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-07.prod.phx3.secureserver.net with  id ThwE1l00d1huGat01hwF2p; Tue, 23 Apr 2013 22:56:16 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
References: 
In-Reply-To: 
Subject: Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Date: Tue, 23 Apr 2013 22:56:32 -0700
Message-ID: <002c01ce40b0$7951aa60$6bf4ff20$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac409G6BqoWAcV+eTe6M/+710JRlsQLurouw
Content-Language: en-us
Cc: gen-art@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, 24 Apr 2013 05:56:17 -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-pcp-upnp-igd-interworking-08
Reviewer: Peter Yee
Review Date: Apr-23-2013
IETF LC End Date: Apr-08-2013
IESG Telechat date: Apr-25-2013

Summary: This draft is ready for publication as a Standards Track RFC.
[Ready]

This is a well-written draft describing how Universal Plug-and-Play Internet
Gateway Devices interwork with NAT devices that use the Port Control
Protocol.  All of my previous review comments on the draft have been
addressed.

		-Peter



From peter@akayla.com  Tue Apr 23 22:59:54 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B2EF21F8C08; Tue, 23 Apr 2013 22:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 636cr73JGT7P; Tue, 23 Apr 2013 22:59:53 -0700 (PDT)
Received: from p3plsmtpa09-03.prod.phx3.secureserver.net (p3plsmtpa09-03.prod.phx3.secureserver.net [173.201.193.232]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC4121F8C06; Tue, 23 Apr 2013 22:59:53 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-03.prod.phx3.secureserver.net with  id Thzr1l0081huGat01hzrpr; Tue, 23 Apr 2013 22:59:52 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org>
References: <002c01ce40b0$7951aa60$6bf4ff20$@akayla.com>
In-Reply-To: <002c01ce40b0$7951aa60$6bf4ff20$@akayla.com>
Subject: RE: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07
Date: Tue, 23 Apr 2013 22:59:33 -0700
Message-ID: <002d01ce40b0$fa8b7bb0$efa27310$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHywG2QsLxL61oZqQrX4UAYteW4gJib4LIA
Content-Language: en-us
Cc: gen-art@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, 24 Apr 2013 05:59:54 -0000

Grrr, typo in the subject line.  That should be draft version -08, as
correctly
referenced below.  Sigh.

		-Peter

-----Original Message-----
From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behalf
Of Peter Yee
Sent: Tuesday, April 23, 2013 10:57 PM
To: draft-ietf-pcp-upnp-igd-interworking.all@tools.ietf.org
Cc: gen-art@ietf.org; ietf@ietf.org
Subject: [Gen-art] Gen-ART review of draft-ietf-pcp-upnp-igd-interworking-07

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-pcp-upnp-igd-interworking-08
Reviewer: Peter Yee
Review Date: Apr-23-2013
IETF LC End Date: Apr-08-2013
IESG Telechat date: Apr-25-2013

Summary: This draft is ready for publication as a Standards Track RFC.
[Ready]

This is a well-written draft describing how Universal Plug-and-Play Internet
Gateway Devices interwork with NAT devices that use the Port Control
Protocol.  All of my previous review comments on the draft have been
addressed.

		-Peter


_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art


From daedulus@btconnect.com  Thu Apr 25 02:06:59 2013
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 570F121F92C0 for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 02:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level: 
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Xnogo7PlquL for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 02:06:58 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe004.messaging.microsoft.com [216.32.180.187]) by ietfa.amsl.com (Postfix) with ESMTP id BFEED21F8D71 for <ietf@ietf.org>; Thu, 25 Apr 2013 02:06:58 -0700 (PDT)
Received: from mail37-co1-R.bigfish.com (10.243.78.236) by CO1EHSOBE030.bigfish.com (10.243.66.95) with Microsoft SMTP Server id 14.1.225.23; Thu, 25 Apr 2013 09:06:58 +0000
Received: from mail37-co1 (localhost [127.0.0.1])	by mail37-co1-R.bigfish.com (Postfix) with ESMTP id 2DB0DB000FC; Thu, 25 Apr 2013 09:06:58 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.197; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0711HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -13
X-BigFish: PS-13(zz9371I542Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahz97hz8275bh8275dh8275ch1033ILz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch304l1d11m1155h)
Received: from mail37-co1 (localhost.localdomain [127.0.0.1]) by mail37-co1 (MessageSwitch) id 1366880816340769_12389; Thu, 25 Apr 2013 09:06:56 +0000 (UTC)
Received: from CO1EHSMHS002.bigfish.com (unknown [10.243.78.226])	by mail37-co1.bigfish.com (Postfix) with ESMTP id 4BDAF6A0047; Thu, 25 Apr 2013 09:06:56 +0000 (UTC)
Received: from DB3PRD0711HT002.eurprd07.prod.outlook.com (157.56.254.197) by CO1EHSMHS002.bigfish.com (10.243.66.12) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 25 Apr 2013 09:06:54 +0000
Received: from DBXPRD0411HT003.eurprd04.prod.outlook.com (157.56.253.165) by pod51017.outlook.com (10.255.183.35) with Microsoft SMTP Server (TLS) id 14.16.293.5; Thu, 25 Apr 2013 09:06:38 +0000
Message-ID: <023601ce4193$81d5e640$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Christian Huitema <huitema@microsoft.com>, Fernando Gont <fgont@si6networks.com>, SM <sm@resistor.net>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com><6.2.5.6.2.20130422081720.0db4ca38@resistor.net><51759238.8000306@si6networks.com><6.2.5.6.2.20130422125704.0d551178@resistor.net><5176B8A2.40809@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
Date: Thu, 25 Apr 2013 10:00:54 +0100
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.253.165]
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: Thu, 25 Apr 2013 09:06:59 -0000

----- Original Message -----
From: "Christian Huitema" <huitema@microsoft.com>
To: "Fernando Gont" <fgont@si6networks.com>; "SM" <sm@resistor.net>
Cc: "RJ Atkinson" <rja.lists@gmail.com>; <ietf@ietf.org>
Sent: Tuesday, April 23, 2013 6:02 PM

<snip>

Instead, the draft goes into great details on how to actually implement
the random number generator. Apart from not being necessary, some of
these details are wrong. For example, the suggested algorithm includes
an "interface index," but different operating systems have different
ways of enumerating interfaces, and the variations in enumeration could
end up violating the "stable address" property.

<tp>

The ifIndex, as it appears in the IF-MIB is not stable; it can change
on each and every re-boot of a system, depending on the order in which
modules are loaded.  It remains the same only until the next re-boot. I
do not know what impact this has on the ipi6_ifindex as used in the
IPv6 API, whether that in turn is unstable.

(This is a property of the IF-MIB and is a reason why the YANG
equivalent
has used a name to index the interface table and not the index value,
which may give the users of the YANG module, also currently in Last
Call, an interesting migration problem).

So if you want a stable address, perhaps you should not use the
interface index.

Tom Petch

</tp>
I would suggest reworking the draft to separate a normative section,
effectively a variation of the 3 lines paragraph above, and an
informational section, the current specification of the algorithm as
"an example of a way to achieve this result if the operating system
meets certain condition, like stable interface identifiers."

I would also explain the inherent issues that have to be solved, e.g.,
swapping interfaces, or enabling multi-homed hosts. And I would observe
that the DAD problem cannot be solved ina  reliable way.

-- Christian Huitema





From vesely@tana.it  Thu Apr 25 02:38:09 2013
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 8233721F9458 for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 02:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.652
X-Spam-Level: 
X-Spam-Status: No, score=-4.652 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FMgWicWkW3cp for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 02:38:05 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFE621F9452 for <ietf@ietf.org>; Thu, 25 Apr 2013 02:38:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1366882682; bh=6VTTbLMYKBhP0RRmB+DYC7BH8m7KHsm1S0xKCmMqTXo=; l=942; h=Date:From:To; b=SJZNgI7Q9OgzJ0YXMWZRrfFEfaZdkya8djJLQi8ATrVXX1OcTP0ItE05A2yHG7JFv aGFwyj3JHj2HeTP0NJKERKjdLWCMyg1hUu2Jful3Ied3Ko8oVCUfkQonchDTeFzhCJ HpGG8W42BSoK/DYIYApNmYXHPPYGtoC/z/i6Qhyk=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Thu, 25 Apr 2013 11:38:02 +0200 id 00000000005DC039.000000005178F97A.00005488
Message-ID: <5178F97A.5050508@tana.it>
Date: Thu, 25 Apr 2013 11:38:02 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "ietf" <ietf@ietf.org>
Subject: W3C standards and the Hollyweb
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, 25 Apr 2013 09:38:09 -0000

The Encrypted Media Extensions (EME, a.k.a. DRM in HTML5)
specification is not a real DRM itself.  It provides for add-on parts
described as Content Decryption Modules that provide DRM functionality
for one or more Key Systems.  DRMs are obviously designed to be
non-interoperable, and EME is a standard for managing such
non-standard stuff.  That is going to break interoperability, as any
given browser will inevitably miss some decryption modules.

Internet, globalization, and the information age may well entail a
change in the basic principles of economics.  However, IMHO, DRM is
not a solution to copyright infringement, not more than postage is a
solution to spam.  Injecting DRM through EME is a disservice to web
standardization, since the latter is supposed to foster the Internet
revolution.

If you haven't done so already, please sign the FSF petition:
http://www.defectivebydesign.org/no-drm-in-html5

Thank you

From hartmans@mit.edu  Thu Apr 25 12:04:18 2013
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 5ABDA21F8D2E; Thu, 25 Apr 2013 12:04:18 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pFVlPU-ahta; Thu, 25 Apr 2013 12:04:17 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id CA9E821F8BC0; Thu, 25 Apr 2013 12:04:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 90DEE2021D; Thu, 25 Apr 2013 15:02:19 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yitGTgSfVmK3; Thu, 25 Apr 2013 15:02:18 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 25 Apr 2013 15:02:18 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id B935E4499; Thu, 25 Apr 2013 15:04:15 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
Subject: Re: Gen-ART review of draft-ietf-karp-crypto-key-table-07
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> <tsla9omh811.fsf@mit.edu> <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com>
Date: Thu, 25 Apr 2013 15:04:15 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com> (David Black's message of "Thu, 25 Apr 2013 14:49:17 -0400")
Message-ID: <tsl61zah1ow.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" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "<stbryant@cisco.com>" <stbryant@cisco.com>, Sam Hartman <hartmans-ietf@mit.edu>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Apr 2013 19:04:18 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:


I've been there too. I've had a number of recent discussinos with Pete
about what the IESG is and is not happy with .
I'll write something up and I'm sure he and the rest of the IESG will
let us know if we got it wrong:-)

From ben@nostrum.com  Thu Apr 25 13:40:00 2013
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 0BD1521F8DCF; Thu, 25 Apr 2013 13:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.001
X-Spam-Level: 
X-Spam-Status: No, score=-100.001 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uv0Ki38PpqU5; Thu, 25 Apr 2013 13:39:59 -0700 (PDT)
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 7665121F8808; Thu, 25 Apr 2013 13:39:56 -0700 (PDT)
Received: from [10.0.1.12] (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 r3PKdsTU013628 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Apr 2013 15:39:55 -0500 (CDT) (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 LC Review of draft-ietf-6man-stable-privacy-addresses-06
Date: Thu, 25 Apr 2013 15:39:54 -0500
Message-Id: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com>
To: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.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, 25 Apr 2013 20:40:00 -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-6man-stable-privacy-addresses-06

Reviewer: Ben Campbell
Review Date: 2013-04-25
IETF LC End Date: 2013-04-16

Summary: This draft is almost ready for publication as a proposed =
standard. There are a few minor issues which should be considered first, =
described in the review.


Major issues:

None.

Minor issues:

-- section 3, third paragraph from end:

The paragraph suggests that changing the number of network interfaces =
should be rare. I think it's quite common in practice for the sorts of =
hosts likely to move between subnets regularly. For example, my Macbook =
Pro uses an external (Thunderbolt attached) ethernet interface which =
regularly gets disconnected and reconnected. Same might hold true for a =
USB attached wireless modem. And I have any number of VPNs which may be =
active or not at any given time.

-- section 3, 2nd paragraph from end:

You describe the affects of including Network_ID in some detail. It =
would be helpful to note the consequences of _not_ including it.

Nits/editorial comments:

-- section 1, 4th paragraph: "Therefore, it is vital..."

That seems a bit overstated. We're not talking about breaking the =
Internet here, are we?

-- 1, 6th paragraph: "Also, they result in increased complexity..."

What sort of complexity? Implementation complexity? It's a bit confusion =
because the previous sentences already talk about increased complexity =
of specific sorts. It would help to mention what sort of additional =
complexity is referred to here.

-- 1, paragraph 11: "This document does not update..."

How is adding an alternative algorithm _not_ an update?

--1, paragraph 12: "... may already address"

Is the "already addressing" part in question? Or is it a matter of =
addressing it in some circumstances, but not others? If the latter, it =
would help to elaborate.

-- 6, last paragraph: "... may mitigate..."

Not sure? Or only under some circumstances?

-- references:
 RFC1948 is obsoleted by 6528. Is there a reason to reference the =
obsolete version?


From acooper@cdt.org  Thu Apr 25 14:32:49 2013
Return-Path: <acooper@cdt.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 EF73721F96F7 for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 14:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y8CYJEZVSxNl for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 14:32:49 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id F402021F96FD for <ietf@ietf.org>; Thu, 25 Apr 2013 14:32:48 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)) for ietf@ietf.org; Thu, 25 Apr 2013 17:32:47 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-6man-stable-privacy-addresses-06.txt> (A method for Generating Stable Privacy-Enhanced Addresses with IPv6 Stateless Address Autoconfiguration (SLAAC)) to Proposed Standard
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <20130412153453.14361.46272.idtracker@ietfa.amsl.com>
Date: Thu, 25 Apr 2013 17:32:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <72EABFA7-B3E7-4FEF-BABD-4296243AABDC@cdt.org>
References: <20130412153453.14361.46272.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, 25 Apr 2013 21:32:50 -0000

One comment and one nit below.

Comment:

There are two places where it is implied that the algorithm in this spec =
mitigates most of the privacy issues associated with embedding IEEE =
identifiers in addresses. The first is in section 1:

For nodes that currently disable "Privacy extensions" [RFC4941] for
   some of the reasons stated above, this mechanism provides stable
   privacy-enhanced addresses which may already address most of the
   privacy concerns related to addresses that embed IEEE identifiers
   [RFC4291].  On the other hand, in scenarios in which "Privacy
   Extensions" are employed, implementation of the mechanism described
   in this document would mitigate host-scanning attacks and also
   mitigate correlation of host activities.

And the second is in section 6:

Finally, we note that the method described in this document may
   mitigate most of the privacy concerns arising from the use of IPv6
   addresses that embed IEEE identifiers, without the use of temporary
   addresses, thus possibly offering an interesting trade-off for those
   scenarios in which the use of temporary addresses is not feasible.

This implication seems misguided. Providing the ability to track and =
correlate the communications of a device that never leaves a single =
network is a significant concern. It is one concern among several that =
the IEEE-identifier-based mechanism raises, but it is a big one IMO. =
This algorithm does not appear to mitigate that concern, so any =
implication that it does should be avoided. I would suggest using "some =
of the privacy concerns" in place of "most of the privacy concerns" in =
the two sections above.

Nit:

This link in the [Broersma] reference is broken: =
http://www.ipv6.org.au/summit/talks/Ron_Broersma.pdf

Alissa

On Apr 12, 2013, at 11:34 AM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'A method for Generating Stable Privacy-Enhanced Addresses with IPv6
>   Stateless Address Autoconfiguration (SLAAC)'
>  <draft-ietf-6man-stable-privacy-addresses-06.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 2013-04-26. 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 specifies a method for generating IPv6 Interface
>   Identifiers to be used with IPv6 Stateless Address Autoconfiguration
>   (SLAAC), such that addresses configured using this method are stable
>   within each subnet, but the Interface Identifier changes when hosts
>   move from one network to another.  The aforementioned method is =
meant
>   to be an alternative to generating Interface Identifiers based on
>   IEEE identifiers, such that the benefits of stable addresses can be
>   achieved without sacrificing the privacy of users.
>=20
>=20
>=20
>=20
> The file can be obtained via
> =
http://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-addresses/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-addresses/b=
allot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
>=20



From fred@cisco.com  Thu Apr 25 15:09:22 2013
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 9D20F21F9709; Thu, 25 Apr 2013 15:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108
X-Spam-Level: 
X-Spam-Status: No, score=-108 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yq1jBDFD3SyO; Thu, 25 Apr 2013 15:09:22 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id F121921F9708; Thu, 25 Apr 2013 15:09:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2992; q=dns/txt; s=iport; t=1366927761; x=1368137361; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=EGLVCTNVS5Miv52c4j6BGILJgG/ElGFNTPCNfuunfyE=; b=LNWMJ4UYefrVLpiwNZLA+f9y//FTrULXkBEQK4AHZxUCj2RFoTozCKfZ vcIE219EaDjHfs0cQPMFUORStxSzE+1LjXpEspBKdWxwbVUyXJM4YrC0u qScHWo2uZoaKOvZAx7jNGXRj0aXS2EeXWRI+UquGEHA0F9CvIizOr7SYY A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAAGpeVGrRDoG/2dsb2JhbABHCoMGvmeBBBZ0gh8BAQEDATo/BQsLOwtXBhMUBYd1Bb5PigKDdxR1MwcWgldhA4kRjguRIoFYgVYc
X-IronPort-AV: E=Sophos;i="4.87,553,1363132800"; d="scan'208";a="76537596"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 25 Apr 2013 22:09:20 +0000
Received: from sjc-fred-88110.cisco.com (sjc-fred-88110.cisco.com [10.19.64.123]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3PM9JkA027860 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Apr 2013 22:09:20 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness	of Running Code: the Implementation Status Section) to	Experimental RFC
From: Fred Baker <fred@cisco.com>
In-Reply-To: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>
Date: Thu, 25 Apr 2013 15:09:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>
To: <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
Cc: "tools-discuss@ietf.org Discussion" <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Apr 2013 22:09:22 -0000

On Apr 12, 2013, at 2:57 PM, The IESG <iesg-secretary@ietf.org> wrote:

> Abstract
>=20
>=20
>   This document describes a simple process that allows authors of
>   Internet-Drafts to record the status of known implementations by
>   including an Implementation Status section.  This will allow
>   reviewers and working groups to assign due consideration to =
documents
>   that have the benefit of running code, by considering the running
>   code as evidence of valuable experimentation and feedback that has
>   made the implemented protocols more mature.
>=20
>   The process in this document is offered as an experiment.  Authors =
of
>   Internet-Drafts are encouraged to consider using the process for
>   their documents, and working groups are invited to think about
>   applying the process to all of their protocol specifications.  The
>   authors of this document intend to collate experiences with this
>   experiment and to report them to the community.


I have read the draft. I like the concept. It applies primarily to =
protocols and procedures, as opposed to white papers. It, however, puts =
emphasis on the experience behind the usefulness of a protocol or =
procedure, which is good.

BTW, once upon a time we required implementation reports for routing =
protocols, which I thought was a good thing and am concerned about the =
loss of in recent times. That resulted in the publication of sets like =
RFCs 1245, 1246, and 1247, which told about the protocol, its =
operational characteristics, and the testing it went through (and by =
implication, the implementations done of it) on its way to RFC-dom.

In 2013, I personally would accomplish this a little differently, =
however. A section in an internet draft, which gets frozen when the =
draft is published, is perhaps useful for the working group and IESG =
review processes. On the other hand, it requires implementers to =
communicate with the draft author and the draft author to update the =
draft in response to their input, which can be a logistical mess. It =
ceases being useful once the draft is published. If a new implementation =
is done, there is no report. If and old one is abandoned, nobody knows. =
It is dated information, potentially true at a point in time but largely =
irrelevant two minutes later.

I would think we want something associated with the data tracker page - =
another web page, perhaps implemented as a wiki - that enables an =
implementer to identify himself and indicate the current status of the =
implementation. Ideally, that might be coupled with a ticket system in =
which issues are raised and closed, and comments are discussed. Ideally, =
this would continue into the life of an RFC, with implementations being =
identified ("The protocol in RFC 12345 is implemented in Andy Systems =
releases 22.70 and later") and associated with errata ("but we really =
wish that the parameter FOO had been specified").=

From sm@resistor.net  Thu Apr 25 16:24:41 2013
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 B400521F9668; Thu, 25 Apr 2013 16:24:41 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mHmoLQ6DmbGV; Thu, 25 Apr 2013 16:24:41 -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 0044A21F9120; Thu, 25 Apr 2013 16:24:40 -0700 (PDT)
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 r3PNOZjC001664; Thu, 25 Apr 2013 16:24:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1366932280; bh=K8mGdoSCxJnvMEm9erX8Wfoy9YMuaXYTzBpOLqqIQ1s=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=l21VLRcYVxbXiYErLcqG72CCf76GLjkMAltZR4Ca9fVVC5jvWiYbPUjdqVT1rJnDI TYtkNZO14EFwFlVxr1PUdC9fT0ogbRCj0F742vXnSbjSFn/1FcQEyu8WPGL/embZha 9iCqD7NHws+4ZwPYiz+cuYeRjkeyLUY+cs741mDU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1366932280; i=@resistor.net; bh=K8mGdoSCxJnvMEm9erX8Wfoy9YMuaXYTzBpOLqqIQ1s=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=j1tpEgORh2u0edSLic+V8RQLe/qxRx++GT56WcsswLos8l2r6yZCVFCYNumDTbhYt 2eHuopmD8o5uesYkIXE0c3ypvQCtktoric2rwk+ehD+iaL5/4kCELj4fvpoj8wXE01 GcahtAA/XpEiLsQdiI5K2dMuyq0015Pimmok/NFs=
Message-Id: <6.2.5.6.2.20130425152040.0d3fbaa8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 25 Apr 2013 16:19:11 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness of Running Code: the Implementation Status Section) to Experimental RFC
In-Reply-To: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: The IESG <noreply@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Apr 2013 23:24:41 -0000

At 14:57 12-04-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Improving Awareness of Running Code: the Implementation Status
>Section'
>   <draft-sheffer-running-code-04.txt> as Experimental 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 2013-05-10. Exceptionally, comments may be

I have read every word in this document multiple times mainly in the 
order they were written. :-)

In Section 1:

   "The scope of the intended experiment is all Internet-Drafts whether
     produced within IETF working groups, outside working groups but
    intended for IETF consensus, or for publication on the Independent
    Stream."

I don't think that it is up to the IETF to run experiments in the 
Independent Submissions Stream.  I suggest removing the text after 
"IETF consensus".

In Section 2:

   "In addition, this section can contain information about the
    interoperability of any or all of the implementations."

I found information about interoperability helpful in resolving 
issues.  Some arguments [1] are not backed by references.  That makes 
it difficult to make a determination.

A good test would be to get feedback from people who has not 
participated in the working group and who have implemented the 
specification.  It might highlight issues about document clarity, 
whether a protocol is under-specified or over-specified, etc.  I 
understand that it is out of scope for draft-sheffer-running-code-04.

What happens to the status of this document after 18 months?

Regards,
-sm

1. http://www.youtube.com/watch?v=kyE4CLM0QIA   


From fgont@si6networks.com  Thu Apr 25 16:43:12 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7947D21F973C; Thu, 25 Apr 2013 16:43:12 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1LuXdkHb+Veu; Thu, 25 Apr 2013 16:43:11 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 8ADF921F973A; Thu, 25 Apr 2013 16:43:11 -0700 (PDT)
Received: from [186.134.41.225] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UVVoY-00058p-Ta; Fri, 26 Apr 2013 01:42:59 +0200
Message-ID: <5179AEF1.2070306@si6networks.com>
Date: Thu, 25 Apr 2013 17:32:17 -0500
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com>
In-Reply-To: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.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, 25 Apr 2013 23:43:12 -0000

Hi, Ben,

Thanks so much for your feedback! Please find my comments in-line...

On 04/25/2013 03:39 PM, Ben Campbell wrote:
> Minor issues:
> 
> -- section 3, third paragraph from end:
> 
> The paragraph suggests that changing the number of network interfaces
> should be rare. I think it's quite common in practice for the sorts
> of hosts likely to move between subnets regularly. For example, my
> Macbook Pro uses an external (Thunderbolt attached) ethernet
> interface which regularly gets disconnected and reconnected. Same
> might hold true for a USB attached wireless modem. And I have any
> number of VPNs which may be active or not at any given time.

I will tweak the text a bit -- as noted in other threads, I will replace
"Interface Index" with a generic "Interface_ID", and will comment on the
desired properties, and note that two possible options for it are the
Interface Index and the Interface name -- with the interface name
probably being more constant in the scenarios that you describe.



> -- section 3, 2nd paragraph from end:
> 
> You describe the affects of including Network_ID in some detail. It
> would be helpful to note the consequences of _not_ including it.

Well, should we really do it? -- after all, you MUST include it.

> 
> Nits/editorial comments:
> 
> -- section 1, 4th paragraph: "Therefore, it is vital..."
> 
> That seems a bit overstated. We're not talking about breaking the
> Internet here, are we?

Well, that depends... there are scenarios in which privacy is really vital.



> -- 1, 6th paragraph: "Also, they result in increased complexity..."
> 
> What sort of complexity? Implementation complexity? It's a bit
> confusion because the previous sentences already talk about increased
> complexity of specific sorts. It would help to mention what sort of
> additional complexity is referred to here.

Yep, implementation complexity -- I will clarify this.



> -- 1, paragraph 11: "This document does not update..."
> 
> How is adding an alternative algorithm _not_ an update?

Well, you still send an RS, receive an RA, and generate an IID.

Me, I'd probably update RFC 4862, so that we make sure that folks
implementing SLAAC take a look at this document, but....



> --1, paragraph 12: "... may already address"
> 
> Is the "already addressing" part in question? Or is it a matter of
> addressing it in some circumstances, but not others? If the latter,
> it would help to elaborate.

Not sure what you mean. The idea is that, in many scenarios,
draft-ietf-stable-privacy-addresses may be good enough to address your
privacy concerns.



> -- 6, last paragraph: "... may mitigate..."
> 
> Not sure? Or only under some circumstances?

The idea is that the only privacy implication that this doesn't mitigate
is correlation of node activities within the same network.
However, that really depends on the number of active nodes within the
same subnet. For example, if you have only one active node in the
subnet, then no matter whether its changes its addresses, its activities
can be easily correlated.



> -- references: RFC1948 is obsoleted by 6528. Is there a reason to
> reference the obsolete version?

Yes: RFC1948 is only referenced in the Acks section, where I note that
this document was inspired by Bellovin's work on RFC1948. While RFC6528
obsoletes RFC1948, the algorithm in that RFC is the same as that in RFC1948.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From trammell@tik.ee.ethz.ch  Thu Apr 25 16:53:25 2013
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 D3AC921F92C0 for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 16:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level: 
X-Spam-Status: No, score=-4.399 tagged_above=-999 required=5 tests=[AWL=2.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvdKfepapUmn for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 16:53:25 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 7C10121F8EE6 for <ietf@ietf.org>; Thu, 25 Apr 2013 16:53:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 9DF38D9308 for <ietf@ietf.org>; Fri, 26 Apr 2013 01:53:22 +0200 (MEST)
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 rNpYoAZizQ0K for <ietf@ietf.org>; Fri, 26 Apr 2013 01:53:22 +0200 (MEST)
Received: from dhcp-38-14.cs.auckland.ac.nz (dhcp-38-14.cs.auckland.ac.nz [130.216.38.229]) (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 B2F59D9304 for <ietf@ietf.org>; Fri, 26 Apr 2013 01:53:21 +0200 (MEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Last Call: <draft-sheffer-running-code-04.txt>
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <01ca01ce41fc$50b9a1f0$f22ce5d0$@olddog.co.uk>
Date: Fri, 26 Apr 2013 11:53:17 +1200
Content-Transfer-Encoding: quoted-printable
Message-Id: <ACD89192-4A32-4CFE-9DEC-125753094D0E@tik.ee.ethz.ch>
References: <01ca01ce41fc$50b9a1f0$f22ce5d0$@olddog.co.uk>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Apr 2013 23:53:26 -0000

Greetings, all,

The idea put forth in this document seems quite useful, and the scope is =
appropriate for a process experiment, so I support its publication.

I have only one comment on the content. In applying this to my own =
documents and WGs, I'd tend to prefer the "alternate" mechanism =
described in section 3, even without any of the conditions there =
necessarily applying.

A single reference to a more-easily updatable source like a wiki seems, =
in general, to be easier to manage than a section in a document which =
may have an irregular update schedule, especially as revision N of a =
document will necessarily report on the status of non-author =
implementations of the protocol as of revision N-1 or before. As the =
section is designed to be removed before publication anyway, there's no =
issue with references to sources without proper change control in the =
resulting RFC, and some WGs/communities may find it useful to keep the =
implementation status portion of the wiki up and current even after =
publication. So I'd reverse the sense of "preferred" and "alternate" =
here, though that's probably just a matter of personal taste.

In any case, this is an experiment, so we should try out both inline =
implementation status and implementation status by-reference, and see =
which works best in which situations.

Best regards,

Brian


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 12 April 2013 22:57
> To: IETF-Announce
> Subject: Last Call: <draft-sheffer-running-code-04.txt> (Improving =
Awareness of
> Running Code: the Implementation Status Section) to Experimental RFC
>=20
>=20
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'Improving Awareness of Running Code: the Implementation Status
> Section'
>  <draft-sheffer-running-code-04.txt> as Experimental 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 2013-05-10. 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 simple process that allows authors of
>   Internet-Drafts to record the status of known implementations by
>   including an Implementation Status section.  This will allow
>   reviewers and working groups to assign due consideration to =
documents
>   that have the benefit of running code, by considering the running
>   code as evidence of valuable experimentation and feedback that has
>   made the implemented protocols more mature.
>=20
>   The process in this document is offered as an experiment.  Authors =
of
>   Internet-Drafts are encouraged to consider using the process for
>   their documents, and working groups are invited to think about
>   applying the process to all of their protocol specifications.  The
>   authors of this document intend to collate experiences with this
>   experiment and to report them to the community.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-sheffer-running-code/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-sheffer-running-code/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.



From abdussalambaryun@gmail.com  Thu Apr 25 17:35:46 2013
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 C914D21F9605 for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 17:35:46 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iGtXuRQXLPt4 for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 17:35:46 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4ECCB21F955A for <ietf@ietf.org>; Thu, 25 Apr 2013 17:35:46 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id up7so956641pbc.1 for <ietf@ietf.org>; Thu, 25 Apr 2013 17:35:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=C3dRZhh/PMoPyH8rM+6wr3J+zAI1QHrtoJNyzN84cOk=; b=wteDUQXY5yZyAR7/XTmUBY3SXkr/PQh/UNSCcc0w73rtuM47NTaOtANM7klg0t6Qg/ gJvI7hWPlaxLdwuD3u3bSIVyFBiQaYSULhynJNXT0NamR4GLhsCW49uMrBC4aVrqHhHi YeGwRKZu9xBn9lImUEe8IytTyXif0uQFsxerrBuZpX7chVYyQeT81dv6x0RmLhAS/iKr LAiev/WTN2o+zXl4n5Pdlomg7pVLDQGjBN0aegCafkpsz1lMr5gPekj2X9q6R7EDCChd 9WmKVXoyQrWi3TaNi7V3sQTuWBOyuW4KvoGKll6RRQkHW64Pbviio+A0kkWMWk6CbLfc 8UuQ==
MIME-Version: 1.0
X-Received: by 10.68.43.35 with SMTP id t3mr56683894pbl.202.1366936546100; Thu, 25 Apr 2013 17:35:46 -0700 (PDT)
Received: by 10.68.230.35 with HTTP; Thu, 25 Apr 2013 17:35:45 -0700 (PDT)
In-Reply-To: <E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com>
Date: Fri, 26 Apr 2013 02:35:45 +0200
Message-ID: <CADnDZ894VD431dpwG2wNjgAufmu0fDfgmN7vpqcg_r4YB1U=hQ@mail.gmail.com>
Subject: Re: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness of Running Code: the Implementation Status Section) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@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: Fri, 26 Apr 2013 00:35:46 -0000

On 4/26/13, Fred Baker <fred@cisco.com> wrote:
> In 2013, I personally would accomplish this a little differently, however. A
> section in an internet draft, which gets frozen when the draft is published,
> is perhaps useful for the working group and IESG review processes. On the
> other hand, it requires implementers to communicate with the draft author
> and the draft author to update the draft in response to their input, which
> can be a logistical mess. It ceases being useful once the draft is
> published.

I think still useful as long it is documented with dates of
implementations, the reader in future will know about this from
reading the section, like we have historical documents, this can be a
historical section, both are used by community. Implementing codes is
the real use of an IETF standard/document.

> If a new implementation is done, there is no report. If and old
> one is abandoned, nobody knows. It is dated information, potentially true at
> a point in time but largely irrelevant two minutes later.

It is the lack of authors to report such important issues into IETF
system. Why we have historical and informational RFCs, maybe we need
some volunteers to focus on things that may be missing

>
> I would think we want something associated with the data tracker page -
> another web page, perhaps implemented as a wiki - that enables an
> implementer to identify himself and indicate the current status of the
> implementation. Ideally, that might be coupled with a ticket system in which
> issues are raised and closed, and comments are discussed. Ideally, this
> would continue into the life of an RFC, with implementations being
> identified ("The protocol in RFC 12345 is implemented in Andy Systems
> releases 22.70 and later") and associated with errata ("but we really wish
> that the parameter FOO had been specified").

This is great idea, I support, but does not replace documentations, I
think the status section is documenting complished work for use by
community, and tracker is referencing IETF-work for use by
participants in future work in progress.

AB

From ben@nostrum.com  Thu Apr 25 17:44:25 2013
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 A039821F9728; Thu, 25 Apr 2013 17:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.301
X-Spam-Level: 
X-Spam-Status: No, score=-101.301 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KIAf-rEO955Z; Thu, 25 Apr 2013 17:44:24 -0700 (PDT)
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 B7F4021F92C0; Thu, 25 Apr 2013 17:44:24 -0700 (PDT)
Received: from [10.0.1.12] (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 r3Q0iM8o040262 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Apr 2013 19:44:22 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <5179AEF1.2070306@si6networks.com>
Date: Thu, 25 Apr 2013 19:44:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com> <5179AEF1.2070306@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.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, 26 Apr 2013 00:44:25 -0000

On Apr 25, 2013, at 5:32 PM, Fernando Gont <fgont@si6networks.com> =
wrote:

> Hi, Ben,
>=20
> Thanks so much for your feedback! Please find my comments in-line...
>=20
> On 04/25/2013 03:39 PM, Ben Campbell wrote:
>> Minor issues:
>>=20
>> -- section 3, third paragraph from end:
>>=20
>> The paragraph suggests that changing the number of network interfaces
>> should be rare. I think it's quite common in practice for the sorts
>> of hosts likely to move between subnets regularly. For example, my
>> Macbook Pro uses an external (Thunderbolt attached) ethernet
>> interface which regularly gets disconnected and reconnected. Same
>> might hold true for a USB attached wireless modem. And I have any
>> number of VPNs which may be active or not at any given time.
>=20
> I will tweak the text a bit -- as noted in other threads, I will =
replace
> "Interface Index" with a generic "Interface_ID", and will comment on =
the
> desired properties, and note that two possible options for it are the
> Interface Index and the Interface name -- with the interface name
> probably being more constant in the scenarios that you describe.
>=20

Works for me.

>=20
>=20
>> -- section 3, 2nd paragraph from end:
>>=20
>> You describe the affects of including Network_ID in some detail. It
>> would be helpful to note the consequences of _not_ including it.
>=20
> Well, should we really do it? -- after all, you MUST include it.

Hmm. Section 3 says Network_ID is optional.


>=20
>>=20
>> Nits/editorial comments:
>>=20
>> -- section 1, 4th paragraph: "Therefore, it is vital..."
>>=20
>> That seems a bit overstated. We're not talking about breaking the
>> Internet here, are we?
>=20
> Well, that depends... there are scenarios in which privacy is really =
vital.

It's not a big deal, really, but it might be worth mentioning the =
context in which it's "vital". Or maybe tone it down to merely =
"important" :-)

[...]

>=20
>=20
>=20
>> -- 1, paragraph 11: "This document does not update..."
>>=20
>> How is adding an alternative algorithm _not_ an update?
>=20
> Well, you still send an RS, receive an RA, and generate an IID.
>=20
> Me, I'd probably update RFC 4862, so that we make sure that folks
> implementing SLAAC take a look at this document, but....
>=20

...?

(The reason you mention is one of the best reasons I can think of to =
call it an update--but if the working group consciously chose not to =
make it an update, I can live with it.)


>=20
>> --1, paragraph 12: "... may already address"
>>=20
>> Is the "already addressing" part in question? Or is it a matter of
>> addressing it in some circumstances, but not others? If the latter,
>> it would help to elaborate.
>=20
> Not sure what you mean. The idea is that, in many scenarios,
> draft-ietf-stable-privacy-addresses may be good enough to address your
> privacy concerns.

The way it's worded, it looks like you think it might address the =
concerns, but aren't sure. I doubt that's the intent. Simply saying "may =
address certain privacy concerns", or "in some circumstances, will =
address...". OTOH, elaborating on the specific concerns addressed would =
be even better. Do you mean to say it addresses the concerns already =
mentioned in this draft? If so, you could use language stronger than =
"may".

Your answer to my next comment is instructive for this as well.


>=20
>=20
>=20
>> -- 6, last paragraph: "... may mitigate..."
>>=20
>> Not sure? Or only under some circumstances?
>=20
> The idea is that the only privacy implication that this doesn't =
mitigate
> is correlation of node activities within the same network.
> However, that really depends on the number of active nodes within the
> same subnet. For example, if you have only one active node in the
> subnet, then no matter whether its changes its addresses, its =
activities
> can be easily correlated.
>=20

Saying that would be helpful.

>=20
>=20
>> -- references: RFC1948 is obsoleted by 6528. Is there a reason to
>> reference the obsolete version?
>=20
> Yes: RFC1948 is only referenced in the Acks section, where I note that
> this document was inspired by Bellovin's work on RFC1948. While =
RFC6528
> obsoletes RFC1948, the algorithm in that RFC is the same as that in =
RFC1948.

So 6528 equally illustrates Steve Bellovin's  work, and is also more =
current, right? If someone decided to follow up to better understand =
your inspiration, which draft would you prefer them to read?

Thanks!

Ben.



From ben@nostrum.com  Thu Apr 25 17:51:56 2013
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 BCC1921F970F; Thu, 25 Apr 2013 17:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.95
X-Spam-Level: 
X-Spam-Status: No, score=-101.95 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mQsS9RGtKOKt; Thu, 25 Apr 2013 17:51:54 -0700 (PDT)
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 D02D721F96C5; Thu, 25 Apr 2013 17:51:52 -0700 (PDT)
Received: from [10.0.1.12] (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 r3Q0ppVF040997 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Apr 2013 19:51:52 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
Date: Thu, 25 Apr 2013 19:51:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E494549B-DCB0-42CD-99DD-6F11B20756D5@nostrum.com>
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com> <5179AEF1.2070306@si6networks.com> <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.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, 26 Apr 2013 00:51:56 -0000

On Apr 25, 2013, at 7:44 PM, Ben Campbell <ben@nostrum.com> wrote:

> So 6528 equally illustrates Steve Bellovin's  work, and is also more =
current, right? If someone decided to follow up to better understand =
your inspiration, which draft would you prefer them to read?

oops, s/draft/version.




From mnot@mnot.net  Thu Apr 25 17:54:05 2013
Return-Path: <mnot@mnot.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 2AF7721F974D for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 17:54:05 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Rjh3vVARF+F for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 17:54:04 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 6295021F974C for <ietf@ietf.org>; Thu, 25 Apr 2013 17:54:04 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.190.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 195D3509B8; Thu, 25 Apr 2013 20:54:02 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: W3C standards and the Hollyweb
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5178F97A.5050508@tana.it>
Date: Fri, 26 Apr 2013 10:53:58 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A28F7DFA-4259-49FD-96DD-76582830177A@mnot.net>
References: <5178F97A.5050508@tana.it>
To: Alessandro Vesely <vesely@tana.it>
X-Mailer: Apple Mail (2.1503)
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, 26 Apr 2013 00:54:05 -0000

Personally, I don't have a firm position on these issues, but I couldn't =
let this pass by.

On 25/04/2013, at 7:38 PM, Alessandro Vesely <vesely@tana.it> wrote:

> The Encrypted Media Extensions (EME, a.k.a. DRM in HTML5)
> specification is not a real DRM itself.  It provides for add-on parts
> described as Content Decryption Modules that provide DRM functionality
> for one or more Key Systems.  DRMs are obviously designed to be
> non-interoperable, and EME is a standard for managing such
> non-standard stuff.  That is going to break interoperability, as any
> given browser will inevitably miss some decryption modules.

The same could be said about the Content-Type header in HTTP; allowing =
for new, even non-standard formats in browsers is by design, not counter =
to the Web (or Internet) architecture. "All implementations moving in =
lockstep" is not the same as "interoperability," and we have plenty of =
examples of such extension points in our protocols here.

[...]

> Injecting DRM through EME is a disservice to web
> standardization, since the latter is supposed to foster the Internet
> revolution.


What does that *mean*? I'm wary of waving around banners like "the =
Internet revolution", since they can so easily be misused.

If folks want to argue against DRM, or even accommodating DRM in =
standards, that's great, but let's not use bad arguments to do it.

Regards,



--
Mark Nottingham   http://www.mnot.net/




From fgont@si6networks.com  Thu Apr 25 18:12:51 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2619A21F976E; Thu, 25 Apr 2013 18:12:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kgrl8DTN7PQi; Thu, 25 Apr 2013 18:12:50 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 5606E21F976D; Thu, 25 Apr 2013 18:12:49 -0700 (PDT)
Received: from [186.134.41.225] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UVXDJ-0007Fm-6X; Fri, 26 Apr 2013 03:12:37 +0200
Message-ID: <5179D47A.2090202@si6networks.com>
Date: Thu, 25 Apr 2013 22:12:26 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com> <5179AEF1.2070306@si6networks.com> <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
In-Reply-To: <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.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, 26 Apr 2013 01:12:51 -0000

Hi, Ben,

On 04/25/2013 09:44 PM, Ben Campbell wrote:
>>> -- section 3, 2nd paragraph from end:
>>> 
>>> You describe the affects of including Network_ID in some detail. 
>>> It would be helpful to note the consequences of _not_ including 
>>> it.
>> 
>> Well, should we really do it? -- after all, you MUST include it.
> 
> Hmm. Section 3 says Network_ID is optional.

Ooops, sorry -- you're right! I was thinking about the prefix, rather
than the Network_ID. I will address this in the next rev.



>>> -- 1, paragraph 11: "This document does not update..."
>>> 
>>> How is adding an alternative algorithm _not_ an update?
>> 
>> Well, you still send an RS, receive an RA, and generate an IID.
>> 
>> Me, I'd probably update RFC 4862, so that we make sure that folks 
>> implementing SLAAC take a look at this document, but....
> 
> ...?
> 
> (The reason you mention is one of the best reasons I can think of to 
> call it an update--but if the working group consciously chose not to 
> make it an update, I can live with it.)

I'm not sure whether this was "consciously chosen" -- I will check with
a few folks about their thoughts (for the most part, I wouldn't want to
trigger a controversy just because of this).



>>> --1, paragraph 12: "... may already address"
>>> 
>>> Is the "already addressing" part in question? Or is it a matter 
>>> of addressing it in some circumstances, but not others? If the 
>>> latter, it would help to elaborate.
>> 
>> Not sure what you mean. The idea is that, in many scenarios, 
>> draft-ietf-stable-privacy-addresses may be good enough to address 
>> your privacy concerns.
> 
> The way it's worded, it looks like you think it might address the 
> concerns, but aren't sure. I doubt that's the intent. Simply saying 
> "may address certain privacy concerns", or "in some circumstances, 
> will address...". OTOH, elaborating on the specific concerns 
> addressed would be even better. Do you mean to say it addresses the 
> concerns already mentioned in this draft? If so, you could use 
> language stronger than "may".
> 
> Your answer to my next comment is instructive for this as well.

Ok, I will add some text about this.



>>> -- references: RFC1948 is obsoleted by 6528. Is there a reason to
>>> reference the obsolete version?
>> 
>> Yes: RFC1948 is only referenced in the Acks section, where I note 
>> that this document was inspired by Bellovin's work on RFC1948. 
>> While RFC6528 obsoletes RFC1948, the algorithm in that RFC is the 
>> same as that in RFC1948.
> 
> So 6528 equally illustrates Steve Bellovin's  work, and is also more 
> current, right? 

Yes. But I'm a co-author of RFC 6528 -- so it'd be a bit arrogant (and
incorrect) to say that I was inspired by RFC 6528 :-) -- I was inspired
by Bellovin, rather than myself. :-)

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From ben@nostrum.com  Thu Apr 25 20:13:15 2013
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 5E12A21F97B7; Thu, 25 Apr 2013 20:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.167
X-Spam-Level: 
X-Spam-Status: No, score=-102.167 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8AipqpzjSsc; Thu, 25 Apr 2013 20:13:14 -0700 (PDT)
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 9F31B21F8E87; Thu, 25 Apr 2013 20:13:14 -0700 (PDT)
Received: from [10.0.1.12] (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 r3Q3D7Fx056834 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Apr 2013 22:13:08 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Gen-ART LC Review of draft-ietf-6man-stable-privacy-addresses-06
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <5179D47A.2090202@si6networks.com>
Date: Thu, 25 Apr 2013 22:13:06 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <72639A54-C153-4799-B49A-6FAD338205BC@nostrum.com>
References: <A8313BC8-9DC9-4F61-90A5-495E3FB2A984@nostrum.com> <5179AEF1.2070306@si6networks.com> <381B19D2-F750-4CE5-819E-115F6E5C1521@nostrum.com> <5179D47A.2090202@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: draft-ietf-6man-stable-privacy-addresses.all@tools.ietf.org, "gen-art@ietf.org Review Team" <gen-art@ietf.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, 26 Apr 2013 03:13:15 -0000

Hi, deleting sections that seem resolved:

On Apr 25, 2013, at 8:12 PM, Fernando Gont <fgont@si6networks.com> wrote:

[...]

> 
> 
>>>> -- 1, paragraph 11: "This document does not update..."
>>>> 
>>>> How is adding an alternative algorithm _not_ an update?
>>> 
>>> Well, you still send an RS, receive an RA, and generate an IID.
>>> 
>>> Me, I'd probably update RFC 4862, so that we make sure that folks 
>>> implementing SLAAC take a look at this document, but....
>> 
>> ...?
>> 
>> (The reason you mention is one of the best reasons I can think of to 
>> call it an update--but if the working group consciously chose not to 
>> make it an update, I can live with it.)
> 
> I'm not sure whether this was "consciously chosen" -- I will check with
> a few folks about their thoughts (for the most part, I wouldn't want to
> trigger a controversy just because of this).
> 
> 

Point taken.

[...]

> 
> 
>>>> -- references: RFC1948 is obsoleted by 6528. Is there a reason to
>>>> reference the obsolete version?
>>> 
>>> Yes: RFC1948 is only referenced in the Acks section, where I note 
>>> that this document was inspired by Bellovin's work on RFC1948. 
>>> While RFC6528 obsoletes RFC1948, the algorithm in that RFC is the 
>>> same as that in RFC1948.
>> 
>> So 6528 equally illustrates Steve Bellovin's  work, and is also more 
>> current, right? 
> 
> Yes. But I'm a co-author of RFC 6528 -- so it'd be a bit arrogant (and
> incorrect) to say that I was inspired by RFC 6528 :-) -- I was inspired
> by Bellovin, rather than myself. :-)
> 

Ah, I see your point :-)



From andrewmcgr@gmail.com  Thu Apr 25 20:43:19 2013
Return-Path: <andrewmcgr@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 78B2A21F8E5D for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 20:43:19 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7J+qnA8QsxOm for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 20:43:18 -0700 (PDT)
Received: from mail-lb0-f179.google.com (mail-lb0-f179.google.com [209.85.217.179]) by ietfa.amsl.com (Postfix) with ESMTP id 2696021E803D for <ietf@ietf.org>; Thu, 25 Apr 2013 20:43:17 -0700 (PDT)
Received: by mail-lb0-f179.google.com with SMTP id t1so3406610lbd.10 for <ietf@ietf.org>; Thu, 25 Apr 2013 20:43:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=I3WpHb1dzwmD/1iPQzv0UHJpT0Q+qHh8c5oqqt6TvXE=; b=TvCr8z6Gqf7OJUJmW1ev57hCzgqjLTOWwpHfIoaAerinX+cAe8KlOT+9Why5pNhM+L QRk0hpdxTnEgE5O9GHgp3PgTRRYBGwX4W86c0hS2W32iPgc7/yhYsXHvcWjkwUmJ1dUc diCYSpSB3xcUkKF2RqfMM35NccbcMzIWfYsxghSYC+Yo5xTf6D3y2D7xLW8RdB2SkOB8 +kzvBhZ1wLfNDynxw5zDZ94LKA1eBA1Edrb6XJtnF3wgi58OluslgHrRysbK00of1qAm wney0w+6iUfUIbrjQUm8espoLsOBnI/dnQlviOCrNnMY4Hcd4dfu0lys4uIde7qmjeMs /XHg==
MIME-Version: 1.0
X-Received: by 10.112.159.1 with SMTP id wy1mr20838931lbb.80.1366947797118; Thu, 25 Apr 2013 20:43:17 -0700 (PDT)
Received: by 10.112.131.71 with HTTP; Thu, 25 Apr 2013 20:43:17 -0700 (PDT)
In-Reply-To: <023601ce4193$81d5e640$4001a8c0@gateway.2wire.net>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net> <5176B8A2.40809@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com> <023601ce4193$81d5e640$4001a8c0@gateway.2wire.net>
Date: Fri, 26 Apr 2013 13:43:17 +1000
Message-ID: <CAA_e5Z7siAGELG+J9H7t-_ggj6wXFY2M4fK=-n=OwPE08Hx-tQ@mail.gmail.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
From: Andrew McGregor <andrewmcgr@gmail.com>
To: "t.p." <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=001a11c33e64dfb69d04db3b5515
Cc: Christian Huitema <huitema@microsoft.com>, ietf <ietf@ietf.org>, SM <sm@resistor.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, 26 Apr 2013 03:43:19 -0000

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

Further to that, ifindexes of tunnels and PPP sessions can change
dynamically as the bearer connection goes up and down, even if the
interface has the same name and authenticated identity.  That raises the
interesting question of whether even the interface name is stable, as on
many systems it is pure chance if the same name-identity mapping repeats
itself.

If you want a stable address, you want to use something that actually has
the exact stability properties you require, and interface indexes and names
are seldom what you actually need.

Andrew


On Thu, Apr 25, 2013 at 7:00 PM, t.p. <daedulus@btconnect.com> wrote:

> ----- Original Message -----
> From: "Christian Huitema" <huitema@microsoft.com>
> To: "Fernando Gont" <fgont@si6networks.com>; "SM" <sm@resistor.net>
> Cc: "RJ Atkinson" <rja.lists@gmail.com>; <ietf@ietf.org>
> Sent: Tuesday, April 23, 2013 6:02 PM
>
> <snip>
>
> Instead, the draft goes into great details on how to actually implement
> the random number generator. Apart from not being necessary, some of
> these details are wrong. For example, the suggested algorithm includes
> an "interface index," but different operating systems have different
> ways of enumerating interfaces, and the variations in enumeration could
> end up violating the "stable address" property.
>
> <tp>
>
> The ifIndex, as it appears in the IF-MIB is not stable; it can change
> on each and every re-boot of a system, depending on the order in which
> modules are loaded.  It remains the same only until the next re-boot. I
> do not know what impact this has on the ipi6_ifindex as used in the
> IPv6 API, whether that in turn is unstable.
>
> (This is a property of the IF-MIB and is a reason why the YANG
> equivalent
> has used a name to index the interface table and not the index value,
> which may give the users of the YANG module, also currently in Last
> Call, an interesting migration problem).
>
> So if you want a stable address, perhaps you should not use the
> interface index.
>
> Tom Petch
>
> </tp>
> I would suggest reworking the draft to separate a normative section,
> effectively a variation of the 3 lines paragraph above, and an
> informational section, the current specification of the algorithm as
> "an example of a way to achieve this result if the operating system
> meets certain condition, like stable interface identifiers."
>
> I would also explain the inherent issues that have to be solved, e.g.,
> swapping interfaces, or enabling multi-homed hosts. And I would observe
> that the DAD problem cannot be solved ina  reliable way.
>
> -- Christian Huitema
>
>
>
>
>

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

<div dir=3D"ltr">Further to that, ifindexes of tunnels and PPP sessions can=
 change dynamically as the bearer connection goes up and down, even if the =
interface has the same name and authenticated identity. =A0That raises the =
interesting question of whether even the interface name is stable, as on ma=
ny systems it is pure chance if the same name-identity mapping repeats itse=
lf.<div>
<br></div><div>If you want a stable address, you want to use something that=
 actually has the exact stability properties you require, and interface ind=
exes and names are seldom what you actually need.<br><div><br></div><div>
Andrew</div></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gm=
ail_quote">On Thu, Apr 25, 2013 at 7:00 PM, t.p. <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:daedulus@btconnect.com" target=3D"_blank">daedulus@btconnect.=
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">----- Original Message -----<br>
From: &quot;Christian Huitema&quot; &lt;<a href=3D"mailto:huitema@microsoft=
.com">huitema@microsoft.com</a>&gt;<br>
To: &quot;Fernando Gont&quot; &lt;<a href=3D"mailto:fgont@si6networks.com">=
fgont@si6networks.com</a>&gt;; &quot;SM&quot; &lt;<a href=3D"mailto:sm@resi=
stor.net">sm@resistor.net</a>&gt;<br>
Cc: &quot;RJ Atkinson&quot; &lt;<a href=3D"mailto:rja.lists@gmail.com">rja.=
lists@gmail.com</a>&gt;; &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org=
</a>&gt;<br>
Sent: Tuesday, April 23, 2013 6:02 PM<br>
<br>
&lt;snip&gt;<br>
<div class=3D"im"><br>
Instead, the draft goes into great details on how to actually implement<br>
the random number generator. Apart from not being necessary, some of<br>
these details are wrong. For example, the suggested algorithm includes<br>
an &quot;interface index,&quot; but different operating systems have differ=
ent<br>
ways of enumerating interfaces, and the variations in enumeration could<br>
end up violating the &quot;stable address&quot; property.<br>
<br>
</div>&lt;tp&gt;<br>
<br>
The ifIndex, as it appears in the IF-MIB is not stable; it can change<br>
on each and every re-boot of a system, depending on the order in which<br>
modules are loaded. =A0It remains the same only until the next re-boot. I<b=
r>
do not know what impact this has on the ipi6_ifindex as used in the<br>
IPv6 API, whether that in turn is unstable.<br>
<br>
(This is a property of the IF-MIB and is a reason why the YANG<br>
equivalent<br>
has used a name to index the interface table and not the index value,<br>
which may give the users of the YANG module, also currently in Last<br>
Call, an interesting migration problem).<br>
<br>
So if you want a stable address, perhaps you should not use the<br>
interface index.<br>
<br>
Tom Petch<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
&lt;/tp&gt;<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">I would suggest rewor=
king the draft to separate a normative section,<br>
effectively a variation of the 3 lines paragraph above, and an<br>
informational section, the current specification of the algorithm as<br>
&quot;an example of a way to achieve this result if the operating system<br=
>
meets certain condition, like stable interface identifiers.&quot;<br>
<br>
I would also explain the inherent issues that have to be solved, e.g.,<br>
swapping interfaces, or enabling multi-homed hosts. And I would observe<br>
that the DAD problem cannot be solved ina =A0reliable way.<br>
<br>
-- Christian Huitema<br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div>

--001a11c33e64dfb69d04db3b5515--

From narten@us.ibm.com  Thu Apr 25 21:53:14 2013
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 E165421F93C8 for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 21:53:13 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8sozAlDKmY5 for <ietf@ietfa.amsl.com>; Thu, 25 Apr 2013 21:53:10 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id 111B421F9709 for <ietf@ietf.org>; Thu, 25 Apr 2013 21:53:08 -0700 (PDT)
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, 26 Apr 2013 00:53:07 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 26 Apr 2013 00:53:06 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id DE6A138C801A for <ietf@ietf.org>; Fri, 26 Apr 2013 00:53:05 -0400 (EDT)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r3Q4r5dt340794 for <ietf@ietf.org>; Fri, 26 Apr 2013 00:53:06 -0400
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 r3Q4r55S019807 for <ietf@ietf.org>; Thu, 25 Apr 2013 22:53:05 -0600
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 r3Q4r4X6019765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 25 Apr 2013 22:53:05 -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 r3Q4r3Ws014676 for <ietf@ietf.org>; Fri, 26 Apr 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r3Q4r3qp014632 for ietf@ietf.org; Fri, 26 Apr 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201304260453.r3Q4r3qp014632@rotala.raleigh.ibm.com>
Date: Fri, 26 Apr 2013 00:53:03 -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-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13042604-9360-0000-0000-000011E81E49
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 04:53:14 -0000

Total of 96 messages in the last 7 days.
 
script run at: Fri Apr 26 00:53:03 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.38% |    9 |  8.36% |    68598 | fgont@si6networks.com
  4.17% |    4 |  7.84% |    64307 | ted.ietf@gmail.com
  6.25% |    6 |  5.10% |    41853 | sm@resistor.net
  6.25% |    6 |  4.86% |    39849 | ben@nostrum.com
  5.21% |    5 |  4.74% |    38860 | l.wood@surrey.ac.uk
  4.17% |    4 |  5.14% |    42159 | daedulus@btconnect.com
  5.21% |    5 |  3.95% |    32420 | abdussalambaryun@gmail.com
  2.08% |    2 |  4.95% |    40562 | mrw@lilacglade.org
  1.04% |    1 |  5.25% |    43055 | salvatore.dantonio@uniparthenope.it
  3.12% |    3 |  3.12% |    25623 | ynir@checkpoint.com
  3.12% |    3 |  3.09% |    25359 | lear@cisco.com
  3.12% |    3 |  2.80% |    22947 | huitema@microsoft.com
  3.12% |    3 |  2.65% |    21705 | framefritti@gmail.com
  3.12% |    3 |  2.58% |    21128 | narten@us.ibm.com
  2.08% |    2 |  2.93% |    23992 | andrewmcgr@gmail.com
  2.08% |    2 |  1.68% |    13795 | lars@netapp.com
  2.08% |    2 |  1.44% |    11814 | w@1wt.eu
  2.08% |    2 |  1.43% |    11695 | mrex@sap.com
  2.08% |    2 |  1.42% |    11617 | mnot@mnot.net
  2.08% |    2 |  1.40% |    11496 | hartmans-ietf@mit.edu
  2.08% |    2 |  1.32% |    10857 | peter@akayla.com
  1.04% |    1 |  1.64% |    13459 | ietfdbh@comcast.net
  1.04% |    1 |  1.60% |    13103 | kathleen.moriarty@emc.com
  1.04% |    1 |  1.59% |    13002 | spromano@unina.it
  1.04% |    1 |  1.31% |    10705 | presnick@qti.qualcomm.com
  1.04% |    1 |  1.09% |     8902 | stbryant@cisco.com
  1.04% |    1 |  1.06% |     8674 | clint.chaplin@gmail.com
  1.04% |    1 |  1.05% |     8609 | markzzzsmith@yahoo.com.au
  1.04% |    1 |  1.05% |     8584 | trammell@tik.ee.ethz.ch
  1.04% |    1 |  1.03% |     8408 | fred@cisco.com
  1.04% |    1 |  0.99% |     8080 | hsantos@isdg.net
  1.04% |    1 |  0.98% |     8075 | acooper@cdt.org
  1.04% |    1 |  0.93% |     7630 | mstjohns@comcast.net
  1.04% |    1 |  0.90% |     7372 | dave@cridland.net
  1.04% |    1 |  0.86% |     7081 | phil@philkern.de
  1.04% |    1 |  0.83% |     6808 | rja.lists@gmail.com
  1.04% |    1 |  0.80% |     6531 | spencer@wonderhamster.org
  1.04% |    1 |  0.79% |     6441 | swb@internet2.edu
  1.04% |    1 |  0.77% |     6325 | dwm@xpasc.com
  1.04% |    1 |  0.71% |     5859 | jmh@joelhalpern.com
  1.04% |    1 |  0.71% |     5818 | touch@isi.edu
  1.04% |    1 |  0.70% |     5734 | melinda.shore@gmail.com
  1.04% |    1 |  0.69% |     5638 | vesely@tana.it
  1.04% |    1 |  0.67% |     5481 | adrian@olddog.co.uk
  1.04% |    1 |  0.64% |     5272 | iad@ietf.org
  1.04% |    1 |  0.60% |     4948 | jari.arkko@piuha.net
--------+------+--------+----------+------------------------
100.00% |   96 |100.00% |   820230 | Total


From abdussalambaryun@gmail.com  Thu Apr 25 23:26:54 2013
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 DF8CD21F97D9; Thu, 25 Apr 2013 23:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, J_CHICKENPOX_52=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJDPiZzFSwpk; Thu, 25 Apr 2013 23:26:54 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id 0420D21F97D2; Thu, 25 Apr 2013 23:26:53 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id p11so2279675pdj.36 for <multiple recipients>; Thu, 25 Apr 2013 23:26:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=PHw5zATq73J13dlIfYQOH0Roo1vJCCPRKkY44F/oc94=; b=CzGgabYyo7yMNt+/DLXTYnWjiKW8IZiRsL2BAmoF6W3h5CbTl2IUuj6LHATUzcGoWO 7mlpZGBZCTWpyhkRPBsRNe2j9F0X6J+M4IgFxRGJjIMTxl+GMPk/99P10pobj92wHBun dmpd3ewPJMtHHkaFblQscsWxgW2jP7zpYCJy5eDgDH3mzy/ofNzxApjVONid5Zos1HIJ zSjWlTeFClFavd+2bHx+jNzVBiaBaTENwTrNzyawSYqqmR+xI3FCoMIU4F8fP113xeHF XUloq2OU9CKlcdledfvoQtS2UjnDRDCsgkOeC4mP+mhh07Frh5bzXZ6T6g1vG6hn4mQP W1YA==
MIME-Version: 1.0
X-Received: by 10.66.89.199 with SMTP id bq7mr33215948pab.202.1366957613623; Thu, 25 Apr 2013 23:26:53 -0700 (PDT)
Received: by 10.68.230.35 with HTTP; Thu, 25 Apr 2013 23:26:53 -0700 (PDT)
In-Reply-To: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>
Date: Fri, 26 Apr 2013 08:26:53 +0200
Message-ID: <CADnDZ892J5dpGHJyZioHagtwvoj--6pg-v61_n6au5OqPDVYfg@mail.gmail.com>
Subject: Re: Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness of Running Code: the Implementation Status Section) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@ietf.org" <iesg@ietf.org>, draft-sheffer-running-code@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 06:26:55 -0000

Reply to your request 12.04.2013
Reviewer: Abdussalam Baryun (AB),
Date: 26.04.2013

Sub: comments for I-D: draft-sheffer-running-code-04
++++++++++++++++++++++++++++++++++++++

The participant reviewer supports the document, very interesting and
helpful, my recommendations and comments below,

Overall Comment> IMHO, we should not request to delete this proposed
section, but it can be shifted to the Appendix section when published.
Removing the section is like doing some work in IETF and then
destroying it, future reviewers/implementers may not know why it was
accepted to publish or be implemented. If I read a document from the
past/present I would like to know its usefulness to increase my
acceptance.

I-D Introduction>
Some of them may never get implemented.

AB>amend>
Some of them may never get implemented or used.

We implement a specification for a use case or to be used within
another specification, some specification may have available to use
another but never does use the other (was that a waste of running
code, or may that be used by an attacking specification).

I-D Section 2>

AB> I will add points:
o   the date of implementation.
o   the reason for implementation, or use-case targets.

AB>Quest> Why before security consideration? I recommend it to be
after all sections, because implementors consider that security
section within their work and may refer to it.

The security consideration section is for the specification
documented, not including the implementation issue. If you code
something it may be used to test security issues for such
specification use case (so we consider that info in the section
proposed).

Section 3>
AB> Add> the WG may replace it into a historical document that can be
refered to by the current concerned WG document,

Section 5.1>
18 Months

AB> The duration is not understood if it is maximum or minimum
requirement. Please provide the requirement language to be clear. (I
don't know from where the 18 came from, I like to specifying *three
IETF WG meeting* presentations/discussions of such implementations. If
you don't present/discuss the implementation inside IETF then how do
we document such work/activity?

AB>Comment> in one WG it was said that some companies don't want to
discuss their implementations or results. Is it strange to *use* the
IETF specification and not report back to it for future progress of
such document?

Section 5.2>
If this idea is adopted by document authors, a summary I-D will be
written containing the statistics of such adoption, as well as
(necessarily subjective) reports by working group chairs and area
directors who have used this mechanism.

AB> Amend>If this idea is adopted by the document editors and WG (if
was a WG document), a summary I-D will be written containing the
statistics of such adoption, as well as (necessarily subjective)
reports by working group chairs ((if was a WG document) and area
directors who have used this mechanism.

AB> comment> I hope we don't ignore the WG decisions, some day we will
have only chairs and directors discussing in meetings or on the list,

Regards
Abdussaam

On 4/12/13, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Improving Awareness of Running Code: the Implementation Status
> Section'
>   <draft-sheffer-running-code-04.txt> as Experimental 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 2013-05-10. 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 document describes a simple process that allows authors of
>    Internet-Drafts to record the status of known implementations by
>    including an Implementation Status section.  This will allow
>    reviewers and working groups to assign due consideration to documents
>    that have the benefit of running code, by considering the running
>    code as evidence of valuable experimentation and feedback that has
>    made the implemented protocols more mature.
>
>    The process in this document is offered as an experiment.  Authors of
>    Internet-Drafts are encouraged to consider using the process for
>    their documents, and working groups are invited to think about
>    applying the process to all of their protocol specifications.  The
>    authors of this document intend to collate experiences with this
>    experiment and to report them to the community.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-sheffer-running-code/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-sheffer-running-code/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

From adrian@olddog.co.uk  Thu Apr 25 23:43:07 2013
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 013D721F97E3; Thu, 25 Apr 2013 23:43:07 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfPe3psEs2za; Thu, 25 Apr 2013 23:43:05 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 70C5721F97DA; Thu, 25 Apr 2013 23:43:05 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3Q6gsd1018945;  Fri, 26 Apr 2013 07:42:59 +0100
Received: from 950129200 ([31.100.87.72]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3Q6govZ018920 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 26 Apr 2013 07:42:51 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'SM'" <sm@resistor.net>, <ietf@ietf.org>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130425152040.0d3fbaa8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130425152040.0d3fbaa8@resistor.net>
Subject: RE: Last Call: <draft-sheffer-running-code-04.txt> (Improving	Awareness of Running Code: the Implementation Status Section) to	Experimental RFC
Date: Fri, 26 Apr 2013 07:42:49 +0100
Message-ID: <025101ce4249$475483d0$d5fd8b70$@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: AQI+/nXAKV+Un4kRrUVd9ZCgs2LIxwFlGjV6l/trOpA=
Content-Language: en-gb
Cc: 'The IESG' <noreply@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: Fri, 26 Apr 2013 06:43:07 -0000

Hi SM,

> I have read every word in this document multiple times mainly in the
> order they were written. :-)

Hmmm, you can't be sure what order we wrote them. You can only know what order
they are presented in :-)

> In Section 1:
> 
>    "The scope of the intended experiment is all Internet-Drafts whether
>      produced within IETF working groups, outside working groups but
>     intended for IETF consensus, or for publication on the Independent
>     Stream."
> 
> I don't think that it is up to the IETF to run experiments in the
> Independent Submissions Stream.  I suggest removing the text after
> "IETF consensus".

I think you are right. Of course, individuals pushing drafts to the ISE could do
the same thing, but that is probably out of scope for us.

> In Section 2:
> 
>    "In addition, this section can contain information about the
>     interoperability of any or all of the implementations."
> 
> I found information about interoperability helpful in resolving
> issues.  Some arguments [1] are not backed by references.  That makes
> it difficult to make a determination.

Agreed. Some implementations and some interop is undocumented and we have to
take it "on trust".
We should probably say that giving references in support would be highly
desirable.

> A good test would be to get feedback from people who has not
> participated in the working group and who have implemented the
> specification.  It might highlight issues about document clarity,
> whether a protocol is under-specified or over-specified, etc.  I
> understand that it is out of scope for draft-sheffer-running-code-04.

Understood.

> What happens to the status of this document after 18 months?

I think that when we publish our analysis of results, this will either be
replaced with something firmer or moved to historic.

Cheers,
Adrian


From otroan@employees.org  Fri Apr 26 02:11:38 2013
Return-Path: <otroan@employees.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 9D30021F9865 for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 02:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_16=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0AxE61-Ikmk for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 02:11:38 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id D108821F986B for <ietf@ietf.org>; Fri, 26 Apr 2013 02:11:32 -0700 (PDT)
Received: from dhcp-lys02-vla252-10-147-116-60.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id BD2585E9C; Fri, 26 Apr 2013 02:11:30 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAA_e5Z7siAGELG+J9H7t-_ggj6wXFY2M4fK=-n=OwPE08Hx-tQ@mail.gmail.com>
Date: Fri, 26 Apr 2013 11:11:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBA882DC-28D9-46A2-AC7C-55F0958F40CF@employees.org>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net> <5176B8A2.40809@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com> <023601ce4193$81d5e640$4001a8c0@gateway.2wire.net> <CAA_e5Z7siAGELG+J9H7t-_ggj6wXFY2M4fK=-n=OwPE08Hx-tQ@mail.gmail.com>
To: Andrew McGregor <andrewmcgr@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: Christian Huitema <huitema@microsoft.com>, ietf <ietf@ietf.org>, SM <sm@resistor.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, 26 Apr 2013 09:11:38 -0000

> Further to that, ifindexes of tunnels and PPP sessions can change =
dynamically as the bearer connection goes up and down, even if the =
interface has the same name and authenticated identity.  That raises the =
interesting question of whether even the interface name is stable, as on =
many systems it is pure chance if the same name-identity mapping repeats =
itself.
>=20
> If you want a stable address, you want to use something that actually =
has the exact stability properties you require, and interface indexes =
and names are seldom what you actually need.

could we simplify the hash to only include the prefix, cookie and DAD =
counter:

RID =3D F(Prefix, secret_key, DAD_Counter)

an implementation that wants a stable address for cases where =
DAD_Counter > 0,
must keep state. e.g. maintain a table of prefix, dad_counter or list of =
previous addresses.

cheers,
Ole


From yaronf.ietf@gmail.com  Fri Apr 26 02:12:24 2013
Return-Path: <yaronf.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 D879021F986B; Fri, 26 Apr 2013 02:12:24 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gbjNRZaGaAqC; Fri, 26 Apr 2013 02:12:23 -0700 (PDT)
Received: from mail-ee0-f47.google.com (mail-ee0-f47.google.com [74.125.83.47]) by ietfa.amsl.com (Postfix) with ESMTP id D678A21F9878; Fri, 26 Apr 2013 02:12:22 -0700 (PDT)
Received: by mail-ee0-f47.google.com with SMTP id b57so1587374eek.6 for <multiple recipients>; Fri, 26 Apr 2013 02:12:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=aGWPQ+XZ54FVKOvsaAZ4COb7Il2mx6oH5/jYqPLVIJI=; b=w10Lx5fwRuF8dElTFQBMLAvDBJpDJKaCmTFwrlYr+Xjsrhr+2gPT7d6ky9t/o8ntSQ yu1Y/Y9YxPh9ZAC6NFoL2fip4zVcPslNeyqt+dUDDTQaWeIL8dbg+WqUuNdNeDPti5zy hLfnhWzwRUBTT/uFbg1GP0jJ0ESl0LhefaFvJhTDNdKQDGzvF2Qzq4jNER6RyI7D5Pg7 dAtvHAIj21ZH2KrCNijAm49XSXf9BAaF4c1YNyOD59AHAM5ePpOGnrxlMCOU+7GAOeAm ALOsg1BnfyqoXDJYPBVi9M+TpQza2MINghYAcK8eEDFewgb9LXuob8Nr9ySIYwD1bCMF 2NMQ==
X-Received: by 10.14.109.131 with SMTP id s3mr40837187eeg.26.1366967542082; Fri, 26 Apr 2013 02:12:22 -0700 (PDT)
Received: from [10.0.0.2] (bzq-79-183-130-139.red.bezeqint.net. [79.183.130.139]) by mx.google.com with ESMTPSA id w51sm14832390eev.13.2013.04.26.02.12.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Apr 2013 02:12:21 -0700 (PDT)
Message-ID: <517A44F2.9050009@gmail.com>
Date: Fri, 26 Apr 2013 12:12:18 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness	of Running Code: the Implementation Status Section) to Experimental RFC
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com>
In-Reply-To: <E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, "tools-discuss@ietf.org Discussion" <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 09:12:25 -0000

Hi Fred,

Thanks for your review. Responding to you, and to other similar comments 
on the list:

The draft refers to two "styles" of documenting implementation: in-line 
in the Internet draft, and by a reference to (presumably) a database or 
a wiki. The draft is also quite clear that the Implementation Status 
section should be removed from the I-D before publication. We do not 
specify what happens with Implementation wikis that are referenced by 
the I-D, presumably in most cases they will be abandoned.

The in-line style is obviously simpler to set up (no infrastructure is 
needed) and in fact, this was the path taken by the 4 I-Ds that are 
using this option to date.

There are two problems with long-term maintenance of implementation data:

- The technical infrastructure (wiki, registration, etc.) should be set 
up. This is not too difficult, and there are lots of people who'd be 
happy to implement such a thing.

- There should be long-term commitment to maintain the data. I think we 
simply don't have such processes in place, and personally I don't want 
to even try to deal with this problem. I suspect that we'd have to 
eventually use paid help if we are serious about keeping the information 
current, and I don't even think it would be worth the cost.

Thanks,
	Yaron


On 2013-04-26 01:09, Fred Baker wrote:
>
> On Apr 12, 2013, at 2:57 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
>> Abstract
>>
>>
>>    This document describes a simple process that allows authors of
>>    Internet-Drafts to record the status of known implementations by
>>    including an Implementation Status section.  This will allow
>>    reviewers and working groups to assign due consideration to documents
>>    that have the benefit of running code, by considering the running
>>    code as evidence of valuable experimentation and feedback that has
>>    made the implemented protocols more mature.
>>
>>    The process in this document is offered as an experiment.  Authors of
>>    Internet-Drafts are encouraged to consider using the process for
>>    their documents, and working groups are invited to think about
>>    applying the process to all of their protocol specifications.  The
>>    authors of this document intend to collate experiences with this
>>    experiment and to report them to the community.
>
>
> I have read the draft. I like the concept. It applies primarily to protocols and procedures, as opposed to white papers. It, however, puts emphasis on the experience behind the usefulness of a protocol or procedure, which is good.
>
> BTW, once upon a time we required implementation reports for routing protocols, which I thought was a good thing and am concerned about the loss of in recent times. That resulted in the publication of sets like RFCs 1245, 1246, and 1247, which told about the protocol, its operational characteristics, and the testing it went through (and by implication, the implementations done of it) on its way to RFC-dom.
>
> In 2013, I personally would accomplish this a little differently, however. A section in an internet draft, which gets frozen when the draft is published, is perhaps useful for the working group and IESG review processes. On the other hand, it requires implementers to communicate with the draft author and the draft author to update the draft in response to their input, which can be a logistical mess. It ceases being useful once the draft is published. If a new implementation is done, there is no report. If and old one is abandoned, nobody knows. It is dated information, potentially true at a point in time but largely irrelevant two minutes later.
>
> I would think we want something associated with the data tracker page - another web page, perhaps implemented as a wiki - that enables an implementer to identify himself and indicate the current status of the implementation. Ideally, that might be coupled with a ticket system in which issues are raised and closed, and comments are discussed. Ideally, this would continue into the life of an RFC, with implementations being identified ("The protocol in RFC 12345 is implemented in Andy Systems releases 22.70 and later") and associated with errata ("but we really wish that the parameter FOO had been specified").
> _______________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
>

From vesely@tana.it  Fri Apr 26 04:38:37 2013
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 14CB621F97AA for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 04:38:37 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fwOY3E9wvUoe for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 04:38:36 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id F167421F87C5 for <ietf@ietf.org>; Fri, 26 Apr 2013 04:38:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1366976314; bh=9i6CRm2/0coQe2R6J6IpnVvsHwKbtKA/Uhoc5sdhn5U=; l=2158; h=Date:From:To:CC:References:In-Reply-To; b=EA3q9g0btqsAmv2SKFhQE+u5TBel9e7syvUBmicCmrbzggbPiEaStCtfvxrEV/XMz aAZR3M62qHLvpOsGG52Vml3yY9Mq0HSfyOwjzn6EFWwyMtNPFX+/NtVkDIxO/7xpJk AYBbAK2DSlAsXhnWIwcXazUhFmliCmJ8qHxIqNDw=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Fri, 26 Apr 2013 13:38:34 +0200 id 00000000005DC035.00000000517A673A.0000225D
Message-ID: <517A673A.6030906@tana.it>
Date: Fri, 26 Apr 2013 13:38:34 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: W3C standards and the Hollyweb
References: <5178F97A.5050508@tana.it> <A28F7DFA-4259-49FD-96DD-76582830177A@mnot.net>
In-Reply-To: <A28F7DFA-4259-49FD-96DD-76582830177A@mnot.net>
Content-Type: text/plain; charset=us-ascii
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, 26 Apr 2013 11:38:37 -0000

On Fri 26/Apr/2013 02:53:58 +0200 Mark Nottingham wrote:
> Personally, I don't have a firm position on these issues, but I couldn't let this pass by.
> 
> On 25/04/2013, at 7:38 PM, Alessandro Vesely <vesely@tana.it> wrote:
>> DRMs are obviously designed to be non-interoperable, and EME is a
>> standard for managing such non-standard stuff.  That is going to
>> break interoperability, as any given browser will inevitably miss
>> some decryption modules.
> 
> The same could be said about the Content-Type header in HTTP;
> allowing for new, even non-standard formats in browsers is by
> design, not counter to the Web (or Internet) architecture.

Correct, and Content-Type is in mail too.  In that case,
standardization is encouraged for each type and subtype.

> "All implementations moving in lockstep" is not the same as
> "interoperability," and we have plenty of examples of such
> extension points in our protocols here.

Yes.

>> Injecting DRM through EME is a disservice to web standardization,
>> since the latter is supposed to foster the Internet revolution.
> 
> What does that *mean*? I'm wary of waving around banners like "the
> Internet revolution", since they can so easily be misused.

The Internet revolution is the big step after the industrial
revolution.  I didn't mean to misuse that banner:  It is a typical
effect of industrial revolution to bring many workers to some large
factories.  Free-software development, for a counter example, doesn't
fit into that model.  I'd agree that the phenomenon is still young and
that the economics of the new model definitely need to be improved.
However, that cannot be done while sticking to the old production
model.  Which direction is the media industry heading to?

Watch-on-demand could have been implemented on private networks and
proprietary equipment.  However, cables had not been laid until the
Internet took root, and that was pushed by the web.  The direction of
history seems to be clear enough to allow taking a firm position.

-- 
If you haven't done so already, please sign the FSF petition:
http://www.defectivebydesign.org/no-drm-in-html5

From chair@ietf.org  Fri Apr 26 05:03:25 2013
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 8F9F421F856D; Fri, 26 Apr 2013 05:03:25 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SvKeDTB1Jg2C; Fri, 26 Apr 2013 05:03:24 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id E52E021F8551; Fri, 26 Apr 2013 05:03:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id E21B712891A; Fri, 26 Apr 2013 05:03:24 -0700 (PDT)
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 irJIOJ-Fd-r1; Fri, 26 Apr 2013 05:03:24 -0700 (PDT)
Received: from [10.1.6.24] (unknown [37.205.61.203]) by c8a.amsl.com (Postfix) with ESMTPSA id 60346128919; Fri, 26 Apr 2013 05:03:24 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Call for IESG narrative scribe volunteers
Date: Fri, 26 Apr 2013 15:03:22 +0300
Message-Id: <9718996D-08F6-4051-B69C-AAD66034CF54@ietf.org>
To: IETF list <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Cc: IESG 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: Fri, 26 Apr 2013 12:03:25 -0000

The IESG narrative minutes are posted, whenever available, at =
http://www.ietf.org/iesg/minutes.html. Currently, Sue Hares and John =
Leslie are carrying the load of taking these notes. Previously, Richard =
Barnes also served in this role, but he has now other duties. We are =
very happy and grateful for the service the scribes are producing - big =
thank you!=20

The IESG would like to recruit at least one more scribe. Other time =
commitments are not always allowing current volunteers to adequately =
cover all of the IESG meetings, and sharing the load would also be =
useful.

Volunteers should write to iesg@ietf.org by May 10th.  We'll keep names =
confidential, unless people choose to volunteer in public.

The general guidelines are:

- at least one scribe attends the regular IESG telechats (17:30 - 20:00 =
CET / 11:30 - 14:00 EST on alternate Thursdays).

- the scribe(s) will record narrative minutes of the discussions, but =
they will not take part in the discussions except to ask for =
clarifications.

- the narrative minutes will be published after review by the IESG.  The =
intent is to publish the narrative minutes within a month of the =
meeting.

- confidential items (principally personnel discussions) will not be =
reported in detail. The scribe will not take part in any sessions from =
which liaisons are excluded (e.g., nomination and appeal discussions).

The IESG scribes get a first hand opportunity to observe the IESG and =
their decision process, as well many interesting technical and other =
topics.

If we do not receive volunteers, then the narrative minutes service may =
not always be available.  We know how important this service is, =
however, for both the community and the IESG itself, so additional =
volunteers would be appreciated.

Jari Arkko
On behalf of the IESG=

From mcr@sandelman.ca  Fri Apr 26 05:48:29 2013
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 B4BE621F9870 for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 05:48:29 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zo74FZKfw2Br for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 05:48:29 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 9461021F982F for <ietf@ietf.org>; Fri, 26 Apr 2013 05:48:27 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E923E2016E; Fri, 26 Apr 2013 08:58:54 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 662C863A62; Fri, 26 Apr 2013 08:47:50 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 53D6063A61; Fri, 26 Apr 2013 08:47:50 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf <ietf@ietf.org>, Andrew McGregor <andrewmcgr@gmail.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
In-Reply-To: <CAA_e5Z7siAGELG+J9H7t-_ggj6wXFY2M4fK=-n=OwPE08Hx-tQ@mail.gmail.com>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net> <5176B8A2.40809@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com> <023601ce4193$81d5e640$4001a8c0@gateway.2wire.net> <CAA_e5Z7siAGELG+J9H7t-_ggj6wXFY2M4fK=-n=OwPE08Hx-tQ@mail.gmail.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 26 Apr 2013 08:47:50 -0400
Message-ID: <9910.1366980470@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Christian Huitema <huitema@microsoft.com>, SM <sm@resistor.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, 26 Apr 2013 12:48:29 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Andrew" =3D=3D Andrew McGregor <andrewmcgr@gmail.com> writes:
    Andrew> Further to that, ifindexes of tunnels and PPP sessions can chan=
ge
    Andrew> dynamically as the bearer connection goes up and down, even if =
the
    Andrew> interface has the same name and authenticated identity.
    Andrew> That raises the=20
    Andrew> interesting question of whether even the interface name is
    Andrew> stable, as on=20

I agree that this happens, and that it is a problem.
I wonder if this isn't a bug in the OSes involved that the ifindex can
not be more clearly specified by a daemon, or that the order of
interface bringup in the OS couldn't be more deterministic.

I think that non-contiguous ifindexes are a pain in the ass (based upon
my understanding of enumeration of interfaces in the interface MIB), but
are they essentially forbidden?  Having holes would make it easier to
keep things consistent.


=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUXp3doqHRg3pndX9AQL1fAQA1rgFjFI9dsTzGzFdqT7wORsT05B9wkI2
JXc8R8c/V3TKVhrX3vlEIrVf2TLTRT/oVo0w7bH2ZN5vvrewQ0xPV6oHLmlAoCoe
H7fjBj4/nuTPICOnW4E5EriimCW2rIH/H3vVmMwF/QmzLxUBj9/MudFSu9obqhdj
sR6PwwP347U=
=m1gz
-----END PGP SIGNATURE-----
--=-=-=--

From rjsparks@nostrum.com  Fri Apr 26 08:42:11 2013
Return-Path: <rjsparks@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 3560B21F9A16; Fri, 26 Apr 2013 08:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmrnO4NroEmx; Fri, 26 Apr 2013 08:42:10 -0700 (PDT)
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 70EF521F9A0C; Fri, 26 Apr 2013 08:42:10 -0700 (PDT)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3QFg80u049436 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Fri, 26 Apr 2013 10:42:09 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517AA051.8080506@nostrum.com>
Date: Fri, 26 Apr 2013 10:42:09 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dhcwg@ietf.org, ietf@ietf.org, General Area Review Team <gen-art@ietf.org>, draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
Subject: Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Content-Type: multipart/alternative; boundary="------------050301090000090703000601"
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 15:42:11 -0000

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

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-dhc-triggered-reconfigure-05
Reviewer: Robert Sparks
Review Date: April 26, 2013
IETF LC End Date: May 6, 2013
IESG Telechat date: May 16, 2013

Summary: This draft is on the right track but has open issues, described in
       the review.

Major issues:

Overall, this document is solid, but I think there is a bug in section 6.3.
I could be wrong, but If I'm right, this paragraph:

    When retransmission is required, the relay may decide to correct the
    content of RECONFIGURE-REQUEST message it issues (e.g., update the
    Client Identifier list).  This decision is local to the relay (e.g.,
    it may be based on observed events such as one or more clients were
    reconfigured on their own).


introduces a race-condition that could lead to an erroneous state. If a 
relay's first message included client A, then the retransmission 
included clients A and B, but that retransmission crosses with a success 
RECONFIGURE-REPLY to the request that only included client A, the relay 
will think it succeeded in asking A and B to be reconfigured.

Minor issues:

This sentence:

    Furthermore, means to recover state in failure events must be
    supported, but are not discussed in this document.

places a requirement on a relay (even though it's not using a 2119 
MUST). Is there some other document that defines this requirement that 
you can reference? If not, the requirement should be discussed in this 
document. Alternatively, you could change the sentence to talk about the 
consequences of not having a proprietary means for recovering state.

Nits/editorial comments:

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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I am the assigned Gen-ART reviewer for this draft. For background on
    <br>
    Gen-ART, please see the FAQ at
    <br>
    <br>
    <a class="moz-txt-link-rfc2396E"
      href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.
    <br>
    <br>
    Please resolve these comments along with any other Last Call
    comments
    <br>
    you may receive.
    <br>
    <br>
    Document:
    draft-ietf-dhc-triggered-reconfigure-05<br>
    Reviewer:&nbsp;
    Robert Sparks<br>
    Review Date: April 26, 2013<br>
    IETF LC End Date:
    May 6, 2013<br>
    IESG Telechat date: May 16, 2013<br>
    <br>
    Summary:
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    This draft is on the right track but has open issues, described in<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the review.<br>
    <br>
    Major issues:
    <br>
    <br>
    Overall, this document is solid, but I think there is a bug in
    section 6.3. <br>
    I could be wrong, but If I'm right, this paragraph:<br>
    <br>
    <blockquote>When retransmission is required, the relay may decide to
      correct the content of RECONFIGURE-REQUEST message it issues
      (e.g., update the Client Identifier list).&nbsp; This decision is local
      to the relay (e.g., it may be based on observed events such as one
      or more clients were reconfigured on their own).<br>
    </blockquote>
    <br>
    introduces a race-condition that could lead to an erroneous state.
    If a relay's first message included client A, then the
    retransmission included clients A and B, but that retransmission
    crosses with a success RECONFIGURE-REPLY to the request that only
    included client A, the relay will think it succeeded in asking A and
    B to be reconfigured.<br>
    <br>
    Minor issues:
    <br>
    <br>
    This sentence:<br>
    <br>
    <blockquote>Furthermore, means to recover state in failure events
      must be supported, but are not discussed in this document.<br>
    </blockquote>
    places a requirement on a relay (even though it's not using a 2119
    MUST). Is there some other document that defines this requirement
    that you can reference? If not, the requirement should be discussed
    in this document. Alternatively, you could change the sentence to
    talk about the consequences of not having a proprietary means for
    recovering state.<br>
    <br>
    Nits/editorial comments:
  </body>
</html>

--------------050301090000090703000601--

From fred@cisco.com  Fri Apr 26 09:07:40 2013
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 1B12E21F9A6E; Fri, 26 Apr 2013 09:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.485
X-Spam-Level: 
X-Spam-Status: No, score=-110.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HhlN2L-bq9H4; Fri, 26 Apr 2013 09:07:39 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 5D10321F98B8; Fri, 26 Apr 2013 09:07:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=785; q=dns/txt; s=iport; t=1366992459; x=1368202059; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=YRe2hPBddYib1WmjP5BXKWMFpk2YxYYil2wO5xaAj+g=; b=RbiGeRBVZOlfEDIN6PxAE/yzU6F2oTGhJoIPRT5EWkrkGljRT19DgooX FoIcbJR4dLbMy7T/ZzVqau0A+9puZTUz9TOADisJaMrFQi7jqa0IDZQK5 1Oq5zXi0R8yTWJqQ87y7UCGiLPU6BLn9LG7XwHzEvg5CFBucA559A5A/x 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmQFAOCkelGtJXG+/2dsb2JhbABRgweDJrtJgQMWdIIgAQEEOj8QAgEIIhQFCyERJQIEDgUIh3oDD7ZGDYhNjDyCIwIxB4JtYQOVOY1uhR+BWIE2gig
X-IronPort-AV: E=Sophos;i="4.87,559,1363132800"; d="scan'208";a="203526911"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-3.cisco.com with ESMTP; 26 Apr 2013 16:07:39 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3QG7cvH032031 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 26 Apr 2013 16:07:38 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Fri, 26 Apr 2013 11:07:38 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness	of Running Code: the Implementation Status Section) to Experimental RFC
Thread-Topic: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness	of Running Code: the Implementation Status Section) to Experimental RFC
Thread-Index: AQHOQl4w9qDGEiWEcESvIj5fcta465jo/2gA
Date: Fri, 26 Apr 2013 16:07:37 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B8242FA@xmb-rcd-x09.cisco.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com> <517A44F2.9050009@gmail.com>
In-Reply-To: <517A44F2.9050009@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.123]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6E4999E69B65BA43990776CD4F0FAB7B@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, "tools-discuss@ietf.org Discussion" <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 16:07:40 -0000

On Apr 26, 2013, at 2:12 AM, Yaron Sheffer <yaronf.ietf@gmail.com>
 wrote:

> - There should be long-term commitment to maintain the data. I think we s=
imply don't have such processes in place, and personally I don't want to ev=
en try to deal with this problem. I suspect that we'd have to eventually us=
e paid help if we are serious about keeping the information current, and I =
don't even think it would be worth the cost.

Understood. That said, we already have working group wikis and errata. I do=
n't want to trivialize the investment, but it seems like we have at least p=
art of the infrastructure already. I'm asking what will be the best for IET=
F discussion and for maintenance of the information. I suspect it's somethi=
ng we can do if we choose to.=

From dhc@dcrocker.net  Fri Apr 26 09:16:44 2013
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 C1E8C21F9838; Fri, 26 Apr 2013 09:16:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AvJwlkaU0qbp; Fri, 26 Apr 2013 09:16:43 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 42D3721F9831; Fri, 26 Apr 2013 09:16:43 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3QGGdA4004658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 26 Apr 2013 09:16:42 -0700
Message-ID: <517AA859.9060804@dcrocker.net>
Date: Fri, 26 Apr 2013 09:16:25 -0700
From: Dave Crocker <dhc@dcrocker.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness of Running Code: the Implementation Status Section) to Experimental RFC
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <CAC4RtVABudiEa_cqqr9OmcbUsAuWGXftisrjEATRLgNvJubXzw@mail.gmail.com>
In-Reply-To: <CAC4RtVABudiEa_cqqr9OmcbUsAuWGXftisrjEATRLgNvJubXzw@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.66]); Fri, 26 Apr 2013 09:16:43 -0700 (PDT)
Cc: IESG <iesg@ietf.org>, Tools Team Discussion <tools-discuss@ietf.org>, draft-sheffer-running-code@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 16:16:44 -0000

Given this thread on the ietf list, I guess I should forward the 
following, which was done as a solicited Apps Area review for this draft:


-------- Original Message --------
Subject: Review of:  draft-sheffer-running-code
Date: Wed, 24 Apr 2013 06:38:24 -0700
From: Dave Crocker <dcrocker@gmail.com>
To: draft-sheffer-running-code.all@tools.ietf.org,
apps-discuss@ietf.org,  iesg@ietf.org

Howdy.

I have been selected as the Applications Area Review Team reviewer for
this draft (for background on apps-review, please see
http://www.apps.ietf.org/content/applications-area-review-team).

Please resolve these comments along with any other Last Call comments
you may receive. Please wait for direction from your document shepherd
or AD before posting a new version of the draft.


Review
------


Title:    Improving Awareness of Running Code: the Implementation Status
Section

I-D:      draft-sheffer-running-code-04

Reviewer:     D. Crocker
Review Date:  24 April 2013


Summary:

Given an organizational motto of "Rough consensus and running code",
implementation experience has a value built into the IETF's DNA.
However formal IETF reliance on running code for specifications has been
minimal, with its only universal occurrence being in consideration of
advanced standards status; it is notably /not/ an organizational
requirement for entry-level Proposed Standard status, if only for the
very high barrier to publication this imposes on document versions that
were intended to be preliminary.  The current draft proposes an
experiment to optionally include documentation of implementations as
part of document development, prior to issuance of a specification as an
RFC.

Within the broader perspective of pre- and post-standardization efforts,
it is quite common to document available implementations of a
specification.  (As a convenient example, see http://dkim.org/deploy.)
In effect, the current proposal merely seeks to have a common IETF-based
means of recording a type of information that industry has already
frequently formulated.

In their current form, the draft and the proposal seem likely to be
useful.  However, both could be improved.

The draft includes some language and assertions that would benefit from
being a bit more carefully written; questions, comments and suggestions
are in the detailed comments below.

The proposal itself would benefit from directly paying more attention to
existing industry practice, which is implied by the "alternatives"
section; that is, that implementation lists already happen and are
maintained after IETF document processing. The proposal should do a
better job of integrating this fact into its design.

One approach could be a relatively simple document change, to
distinguish between specifying the information to be reported, as
distinct from the means of reporting it -- think of it as payload vs.
mechanism...  Specify them separately.  Then define both how to
incorporate the information directly and the form of an external
citation to it; this would eliminate the document's section on
'alternatives' and treat the original and alternative methods as equal.

d/





Detailed Comments:

> 1.  Introduction
>
> Most IETF participants are familiar with the saying, "rough
> consensus and running code" [Tao], and can identify with its
> pragmatic approach.  However, there are many examples of
> Internet-Drafts containing protocol specification that have gone
> through to publication as Proposed Standard RFCs without
> implementation.  Some of them may never get implemented.

The "however" implies that it is wrong or problematic for Proposed to be
assigned to unimplemented protocols.  It isn't.  I suggest a softer
tone, while still noting the relevantfact. Something like:

      It is not a requirement of Proposed Standard status to have any
implementations; by the time of reaching that status, some
specifications have been implemented and some have not. Indeed, some
never get implemented.


> Over time, a variety of policies have been implemented within the

implemented -> applied


> IETF to consider running code.  In the Routing Area it used to be a
> requirement that one or more implementations must exist before an
> Internet-Draft could be published as a Proposed Standard RFC
> [RFC1264].  That RFC was later obsoleted and the requirement for
> implementation was lifted, but each working group was given the
> authority to impose its own implementation requirements [RFC4794]
> and at least one working group (IDR) continues to require two
> independent implementations.
>
> The hypothesis behind this document is that there are benefits to
> the

this -> the current


> IETF standardization process of producing implementations of
> protocol specifications before publication as RFCs.  These benefits,
> which

I suspect that that isn't its "hypothesis" at all, since the document
does nothing to specify or directly affect policies for requiring or
encouraging implementation.  Perhaps there is a hope that the proposed
notation about implementations will serve as some sort of encouragement,
but that's pretty indirect; success or failure of the proposed
experiment won't validate or invalidate whether there are benefits to
early implementation.  And providing for a notation convention hardly
constitutes an 'incentive'.

Rather, I believe the premise of the document is that the community is
aided by /more widely knowing about/ early implementations.


> include determining that the specification is comprehensible and
> that there is sufficient interest to implement, are further discussed
> in Section 4.
>
> This document describes a simple process that allows authors of

process -> mechanism


> Internet-Drafts to record the status of known implementations, by
> including an Implementation Status section.  The document defines
> (quite informally) the contents of this section, to ensure that the
> relevant information is included.  This will allow reviewers and
> working groups to assign due consideration to documents that have
> the benefit of running code, by considering the running code as
> evidence of valuable experimentation and feedback that has made the
> implemented protocols more mature.

The above last sentence seems to be the actual claimed value proposition
for the experiment.


> This document provides a mechanism to record and publicize the

This sentence seems entirely redundant.


> existence of running code.  It is up to the individual working
> groups to use this information as they see fit, but one result might
> be the preferential treatment of documents resulting in them being
> processed more rapidly.

I think it won't be the working group that 'uses' the information, but
rather IETF management and the broader community?


> The process in this document is offered as an experiment.  Authors
> of Internet-Drafts are encouraged to consider using the process for
> their documents, and working groups are invited to think about
> applying the process to all of their protocol specifications.
>
> The scope of the intended experiment is all Internet-Drafts whether

Probably not all I-Ds, since they do not all contain implementable
specifications.


>
>
> Sheffer & Farrel        Expires October 14, 2013                [Page
> 3]  Internet-Draft                Running Code
> April 2013
>
>
> produced within IETF working groups, outside working groups but

What I-Ds are produced by "outside working groups"?  I can't tell who
this refers to.It's probably just as well to remove the attempted case
analysis for groups and just say that the scope is all specifications
issued as I-Ds.


> intended for IETF consensus, or for publication on the Independent
> Stream.  However, it is expected that most benefit from the

that most benefit from the experiment will
->
the greatest benefit in the experiment will


> experiment will be seen with Standards Track documents developed
> within working groups.

Here's my guess:

1. Those offering comments or making decisions about the status of
document will be aided by this added information.

2. Those deciding about whether to write code or deploy it will be aided.

I think the latter is likely to be the greater benefit.


> The authors of this document intend to collate experiences with this
> experiment and to report them to the community.
>
>
> 2.  The "Implementation Status" Section
>
> Each Internet-Draft may contain a section entitled "Implementation
> Status".  This section, if it appears, should be located just before
> the "Security Considerations" section and contain, for each existing
> implementation:
>
> o  The implementation's name and/or a link to a web page describing
> the implementation. o  A brief general description. o  The
> implementation's level of maturity: research, prototype, alpha, beta,
> production, widely used etc. o  Coverage: which parts of the protocol
> specification are implemented and which versions of the
> Internet-Draft were implemented. o  Licensing: the terms under which
> the implementation can be used. For example: proprietary, royalty
> licensing, freely distributable with acknowledgement (BSD style),
> freely distributable with requirement to redistribute source (GPL
> style), other (specify). o  Contact information: ideally a person's
> name and email address, but possibly just a URL or mailing list.

List the organization that did the implementation and contact
information for the proper place in the organization.


> In addition, this section can contain information about the
> interoperability of any or all of the implementations.
>
> Since this information is necessarily time-dependent, it is
> inappropriate for inclusion in a published RFC.  The authors should

Way to bury the lead.  This stuff won't be in the published document?
It's only for pre-publication?


> include a note to the RFC Editor requesting that the section be
> removed before publication.
>
> 2.1.  Introductory Text
>
> The following boilerplate text is proposed to head the
> Implementation Status section:
>
>
>
>
>
>
>
> Sheffer & Farrel        Expires October 14, 2013                [Page
> 4]  Internet-Draft                Running Code
> April 2013
>
>
> This section records the status of known implementations of the
> protocol defined by this specification at the time of posting of this
> Internet-Draft, and is based on a proposal described in [RFC Editor:
> replace by a reference to this document].  According to [RFC Editor:
> replace by a reference to this document], "this will allow reviewers
> and working groups to assign due consideration to documents that have
> the benefit of running code, by considering the running code as
> evidence of valuable experimentation and feedback that has made the
> implemented protocols more mature.  It is up to the individual
> working groups to use this information as they see fit".
>
> Authors are requested to add a note to the RFC Editor at the top of
> this section, advising the Editor to remove the entire section
> before publication, as well as the reference to [RFC Editor: replace
> by a reference to this document].
>
>
> 3.  Alternative Formats

Yes!


> Sometimes it can be advantageous to publish the implementation
> status separately from the base Internet-Draft, e.g. on the IETF
> wiki:
>
> o  When the Implementation Status section becomes too large to be
> conveniently managed within the document. o  When a working group
> decides to have implementors, rather than authors, keep the status of
> their implementations current. o  When a working group already
> maintains an active wiki and prefers to use it for this purpose.
>
> It is highly desirable for all readers of the Internet-Draft to be
> made aware of this information.  Initially this can be done by
> replacing the Implementation Status section's contents with a URL
> pointing to the wiki.  Later, the IETF Tools may support this
> functionality, e.g. by including such a link from the HTMLized draft
> version, similar to the IPR link.
>
> If the implementation status is published separately from the I-D,
> then this information needs to be openly available without requiring
> authentication, registration or access controls if it is to have any
> useful effects.
>
>
> 4.  Benefits
>
> Publishing the information about implementations provides the
> working group with several benefits:
>
>
>
>
> Sheffer & Farrel        Expires October 14, 2013                [Page
> 5]  Internet-Draft                Running Code
> April 2013
>
>
> o  Participants are motivated to implement protocol proposals, which
> helps in discovering protocol flaws at an early stage.

The psychological premise seems to be that getting cited in this list
will somehow serve as an incentive to implementers. I can imagine that
they'll like being listed, but find it extremely difficult to believe
that it will affect whether they do the work; not that I think it's a
deciding factor, but note that the ego value is further reduced by the
information's being ephemeral, since it it removed prior to RFC publication!


> o  Other participants can use the software, to evaluate the
> usefulness of protocol features, its correctness (to some degree) and
> other properties, such as resilience and scalability.

Efficacy of the spec.


> o  WG members may choose to perform interoperability testing with
> known implementations, especially when they are publicly available.

Interoperability of the spec.


> o  In the case of open source, people may want to study the code to
> better understand the protocol and its limitations, determine if the
> implementation matches the protocol specification, and whether the
> protocol specification has omissions or ambiguities.

Reference implementation as exemplar.


> o  Working group chairs and ADs may use the information provided to
> help prioritize the progress of I-Ds in some way.

What does "prioritize the progress" mean?


> o  Similarly, the information is useful when deciding whether the
> document should be progressed on a different track (individual
> submission, Experimental etc.).
Assess spec maturity.  (This seems redundant with the combination of
Efficacy and Interoperability?)


> o  And lastly, some protocol features may be hard to understand, and
> for such features, the mere assurance that they can be implemented is
> beneficial.

mumble.  Might highlight problems with the spec language. Might
undermine the spec text by causing code to be used in place of it?


> We do not specify here whether and to what degree working groups are
> expected to prefer proposals that have "running code" associated
> with them, over others that do not.
>
>
> 5.  Process Experiment
>
> The current proposal is proposed as an experiment.  The inclusion of
> "Implementation Status" sections in Internet-Drafts is not
> mandatory, but the authors of this document wish to encourage authors
> of other Internet-Drafts to try out this simple process to discover
> whether it is useful.  Working group chairs are invited to suggest
> this process to document editors in their working groups, and to draw
> the attention of their working group participants to "Implementation
> Status" sections where they exist.
>
> Following a community discussion, it was concluded that [RFC3933] is
> not an appropriate framework for this experiment, primarily because
> no change is required to any existing process.

It defines a document meta-data encoding mechanism. That's not really a
"process".


> 7.  Security Considerations
>
> This is a process document and therefore, it does not have a direct
> effect on the security of any particular IETF protocol.  Better

Better -> However, better


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From rjsparks@nostrum.com  Fri Apr 26 09:19:31 2013
Return-Path: <rjsparks@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 7B1B721F9987; Fri, 26 Apr 2013 09:19:31 -0700 (PDT)
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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p94gESGCTazx; Fri, 26 Apr 2013 09:19:30 -0700 (PDT)
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 CCEAA21F9878; Fri, 26 Apr 2013 09:19:30 -0700 (PDT)
Received: from unnumerable.tekelec.com ([4.30.77.1]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3QGJTZr054170 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Fri, 26 Apr 2013 11:19:29 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517AA910.8030608@nostrum.com>
Date: Fri, 26 Apr 2013 11:19:28 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: mohamed.boucadair@orange.com
Subject: Re: RE : [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 4.30.77.1 is authenticated by a trusted mechanism)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 16:19:31 -0000

On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
> Dear Robert,
>
> Thank you for the review.
> Please see inline.
>
> Cheers,
> Med
> ________________________________________
> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de Robert Sparks [rjsparks@nostrum.com]
> Date d'envoi : vendredi 26 avril 2013 17:42
> À : dhcwg@ietf.org; ietf@ietf.org; General Area Review Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
> Objet : [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
>
> 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><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-dhc-triggered-reconfigure-05
> Reviewer:  Robert Sparks
> Review Date: April 26, 2013
> IETF LC End Date: May 6, 2013
> IESG Telechat date: May 16, 2013
>
> Summary: This draft is on the right track but has open issues, described in
>        the review.
>
> Major issues:
>
> Overall, this document is solid, but I think there is a bug in section 6.3.
> I could be wrong, but If I'm right, this paragraph:
>
> When retransmission is required, the relay may decide to correct the content of RECONFIGURE-REQUEST message it issues (e.g., update the Client Identifier list).  This decision is local to the relay (e.g., it may be based on observed events such as one or more clients were reconfigured on their own).
>
> introduces a race-condition that could lead to an erroneous state. If a relay's first message included client A, then the retransmission included clients A and B, but that retransmission crosses with a success RECONFIGURE-REPLY to the request that only included client A, the relay will think it succeeded in asking A and B to be reconfigured.
>
> Med: This example does not apply for that text.
Really? What text constrains how you change what's in the retransmission?
>   In fact, the example should be the other way around. Perhaps, this can be made clearer if we change "(e.g., update the Client Identifier list)" to "(e.g., remove a client from the Client Identifier list)".
If I understand you correctly, you need more than just changing a 
parenthetical e.g.. I think you're saying that you are constraining the 
message changes to be such that if anything earlier in the 
retransmission sequence succeeded, the request in the retransmission 
would also have succeeded. But why do you need that much complexity? Do 
you have it already with any other request?
>
> Minor issues:
>
> This sentence:
>
> Furthermore, means to recover state in failure events must be supported, but are not discussed in this document.
> places a requirement on a relay (even though it's not using a 2119 MUST). Is there some other document that defines this requirement that you can reference?
>
> Med: I'm not aware of any; but if there is one we can cite it.
>
>   If not, the requirement should be discussed in this document. Alternatively, you could change the sentence to talk about the consequences of not having a proprietary means for recovering state.
>
> Med: Will consider that option if you think this is really needed.
>
> Nits/editorial comments:


From john-ietf@jck.com  Fri Apr 26 09:50:53 2013
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 0414421F9A24; Fri, 26 Apr 2013 09:50:53 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nnDx-MeNR3Em; Fri, 26 Apr 2013 09:50:52 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 078BA21F9A23; Fri, 26 Apr 2013 09:50:52 -0700 (PDT)
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 1UVlrF-000HvP-NF; Fri, 26 Apr 2013 12:50:49 -0400
Date: Fri, 26 Apr 2013 12:50:44 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Fred Baker (fred)" <fred@cisco.com>, Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt>	(Improving Awareness	of Running Code: the Implementation Status	Section) to Experimental RFC
Message-ID: <0E1D18E70456E3EEE8A2BEC0@JcK-HP8200.jck.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B8242FA@xmb-rcd-x09.cisco.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com> <517A44F2.9050009@gmail.com> <8C48B86A895913448548E6D15DA7553B8242FA@xmb-rcd-x09.cisco.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@ietf.org>" <ietf@ietf.org>, "tools-discuss@ietf.org Discussion" <tools-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 16:50:53 -0000

--On Friday, April 26, 2013 16:07 +0000 "Fred Baker (fred)"
<fred@cisco.com> wrote:

> 
> On Apr 26, 2013, at 2:12 AM, Yaron Sheffer
> <yaronf.ietf@gmail.com>  wrote:
> 
>> - There should be long-term commitment to maintain the data.
>> I think we simply don't have such processes in place, and
>> personally I don't want to even try to deal with this
>> problem. I suspect that we'd have to eventually use paid help
>> if we are serious about keeping the information current, and
>> I don't even think it would be worth the cost.
> 
> Understood. That said, we already have working group wikis and
> errata. I don't want to trivialize the investment, but it
> seems like we have at least part of the infrastructure
> already. I'm asking what will be the best for IETF discussion
> and for maintenance of the information. I suspect it's
> something we can do if we choose to.

Fred,

First, I agree with both the above and with your prior note
agreeing with the general idea and suggesting something more
"live" than a section of an I-D.  Second, while I certainly see
the value, I would get nervous if we were to move significantly
toward a long-term, IETF-supported, official statement or
compendium of implementation status.  At least unless pursued
with great caution [1], such a thing would raise some of the
same issues that going into the conformance testing business
does in terms of the perception of guarantees that a given
implementation is somehow "IETF approved".

Perhaps the right model would be to keep this material in I-Ds
(as the proposal suggests) to support the evolution and review
of specification documents, then to move it to a wiki or
equivalent that was clearly identified as unofficial and for the
convenience of the community and that was "maintained by the
IETF" only to the extent needed to minimize spam, libel, and
other nonsense.

It also occurs to me that an alternative to part of the
experiment (still consistent with it, IMO) would be to start the
wiki process earlier and use the I-Ds merely to snapshot the
wiki at various points to help in the review process.  That
would give both the advantages of a continually-evolving list
and those of periodic stable snapshots.

Just a thought or two.

   john



[1] Images of dragging along as small pack of lawyers,
albatross-like, are probably in order.

From fgont@si6networks.com  Fri Apr 26 12:06:17 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80A7D21F982B for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 12:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_16=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fO2PVdz6XyN9 for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 12:06:17 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id F39D821F9823 for <ietf@ietf.org>; Fri, 26 Apr 2013 12:06:16 -0700 (PDT)
Received: from [2001:5c0:1000:a::11b] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UVnyA-0008Rm-Mv; Fri, 26 Apr 2013 21:06:07 +0200
Message-ID: <517AD00B.5040601@si6networks.com>
Date: Fri, 26 Apr 2013 16:05:47 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net> <5176B8A2.40809@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com> <023601ce4193$81d5e640$4001a8c0@gateway.2wire.net> <CAA_e5Z7siAGELG+J9H7t-_ggj6wXFY2M4fK=-n=OwPE08Hx-tQ@mail.gmail.com> <DBA882DC-28D9-46A2-AC7C-55F0958F40CF@employees.org>
In-Reply-To: <DBA882DC-28D9-46A2-AC7C-55F0958F40CF@employees.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Christian Huitema <huitema@microsoft.com>, ietf <ietf@ietf.org>, SM <sm@resistor.net>, Andrew McGregor <andrewmcgr@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: Fri, 26 Apr 2013 19:06:17 -0000

Hi, Ole,

On 04/26/2013 06:11 AM, Ole Troan wrote:
>> If you want a stable address, you want to use something that
>> actually has the exact stability properties you require, and
>> interface indexes and names are seldom what you actually need.
> 
> could we simplify the hash to only include the prefix, cookie and DAD
> counter:
> 
> RID = F(Prefix, secret_key, DAD_Counter)
> 
> an implementation that wants a stable address for cases where
> DAD_Counter > 0, must keep state. e.g. maintain a table of prefix,
> dad_counter or list of previous addresses.

You you do not include some sort of "Interface ID", then, when two
interfaces are employed to connect to the same network, you are
guaranteed to get a collision...

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From fgont@si6networks.com  Fri Apr 26 12:14:12 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 282D321F998A for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 12:14:12 -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=0.300, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bnf7UPVgKgoj for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 12:14:11 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id D003A21F997F for <ietf@ietf.org>; Fri, 26 Apr 2013 12:14:10 -0700 (PDT)
Received: from [2001:5c0:1000:a::11b] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UVo5p-00009n-6S; Fri, 26 Apr 2013 21:14:05 +0200
Message-ID: <517AD1F1.4090602@si6networks.com>
Date: Fri, 26 Apr 2013 16:13:53 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Alissa Cooper <acooper@cdt.org>
Subject: Re: Last Call: <draft-ietf-6man-stable-privacy-addresses-06.txt> (A method for Generating Stable Privacy-Enhanced Addresses with IPv6 Stateless Address Autoconfiguration (SLAAC)) to Proposed Standard
References: <20130412153453.14361.46272.idtracker@ietfa.amsl.com> <72EABFA7-B3E7-4FEF-BABD-4296243AABDC@cdt.org>
In-Reply-To: <72EABFA7-B3E7-4FEF-BABD-4296243AABDC@cdt.org>
X-Enigmail-Version: 1.4.6
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, 26 Apr 2013 19:14:12 -0000

Hi, Alissa!

Thanks so much for your feedback! -- Please find my comments in-line...

On 04/25/2013 06:32 PM, Alissa Cooper wrote:
> 
> There are two places where it is implied that the algorithm in this
> spec mitigates most of the privacy issues associated with embedding
> IEEE identifiers in addresses. The first is in section 1:
> 
> For nodes that currently disable "Privacy extensions" [RFC4941] for 
> some of the reasons stated above, this mechanism provides stable 
> privacy-enhanced addresses which may already address most of the 
> privacy concerns related to addresses that embed IEEE identifiers 
> [RFC4291].  On the other hand, in scenarios in which "Privacy 
> Extensions" are employed, implementation of the mechanism described 
> in this document would mitigate host-scanning attacks and also 
> mitigate correlation of host activities.
> 
> And the second is in section 6:
> 
> Finally, we note that the method described in this document may 
> mitigate most of the privacy concerns arising from the use of IPv6 
> addresses that embed IEEE identifiers, without the use of temporary 
> addresses, thus possibly offering an interesting trade-off for those 
> scenarios in which the use of temporary addresses is not feasible.
> 
> This implication seems misguided. Providing the ability to track and
> correlate the communications of a device that never leaves a single
> network is a significant concern.

In some scenarios, that's impossible. Trivial example: If you have a
network with a single host attached to it, no matter whether you change
your address periodically (*), it will be possible to correlate the
hosts' activities.

(*) That of changing your addresses *periodically* actually helps
correlation.



> It is one concern among several
> that the IEEE-identifier-based mechanism raises, but it is a big one
> IMO. This algorithm does not appear to mitigate that concern, so any
> implication that it does should be avoided.

What the text implicitly means is "This algorithm mitigates all concerns
except correlation of a nde's activity within the same network... but in
some scenarios that's impossible to mitigate, then, in those scenarios,
this algorithm mitigates as much as *can* be mitigated".


> I would suggest using
> "some of the privacy concerns" in place of "most of the privacy
> concerns" in the two sections above.

Is there any other one left to be mitigated other than the one I
mentioned above?


> 
> Nit:
> 
> This link in the [Broersma] reference is broken:
> http://www.ipv6.org.au/summit/talks/Ron_Broersma.pdf

Will fix this.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From fgont@si6networks.com  Fri Apr 26 12:19:50 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 576B421F990F for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 12:19:50 -0700 (PDT)
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.150,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sOThT4qtmSTa for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 12:19:50 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id D106421F9909 for <ietf@ietf.org>; Fri, 26 Apr 2013 12:19:49 -0700 (PDT)
Received: from [2001:5c0:1000:a::11b] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UVoBC-0000HT-VK; Fri, 26 Apr 2013 21:19:35 +0200
Message-ID: <517AD33F.1080601@si6networks.com>
Date: Fri, 26 Apr 2013 16:19:27 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Andrew McGregor <andrewmcgr@gmail.com>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com> <6.2.5.6.2.20130422081720.0db4ca38@resistor.net> <51759238.8000306@si6networks.com> <6.2.5.6.2.20130422125704.0d551178@resistor.net> <5176B8A2.40809@si6networks.com> <C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com> <023601ce4193$81d5e640$4001a8c0@gateway.2wire.net> <CAA_e5Z7siAGELG+J9H7t-_ggj6wXFY2M4fK=-n=OwPE08Hx-tQ@mail.gmail.com>
In-Reply-To: <CAA_e5Z7siAGELG+J9H7t-_ggj6wXFY2M4fK=-n=OwPE08Hx-tQ@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Christian Huitema <huitema@microsoft.com>, ietf <ietf@ietf.org>, SM <sm@resistor.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, 26 Apr 2013 19:19:50 -0000

Hi, Andrew,

On 04/26/2013 12:43 AM, Andrew McGregor wrote:
> Further to that, ifindexes of tunnels and PPP sessions can change
> dynamically as the bearer connection goes up and down,

Would we be doing SLAAC for these?


> even if the
> interface has the same name and authenticated identity.  That raises the
> interesting question of whether even the interface name is stable, as on
> many systems it is pure chance if the same name-identity mapping repeats
> itself.

So... how would you set up e.g. firewall rules for those systems? (not
to mention configuration of daemoss such as rtadvd and others...)

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From sm@resistor.net  Fri Apr 26 12:52:22 2013
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 E2D9521F994B; Fri, 26 Apr 2013 12:52:20 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RM+0KTe4qZZL; Fri, 26 Apr 2013 12:52:18 -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 2A72C21F9954; Fri, 26 Apr 2013 12:52:17 -0700 (PDT)
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 r3QJq8Xm021905; Fri, 26 Apr 2013 12:52:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367005934; bh=VwKS6n+6zHm6FxoGh8Gv3sZslQU5A34q1eMGFQ9vsAM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eC+oGHE6uvGAhLwpUT+ueRrJKEzWHzIyT1YcE94fLwHiYrAMacEXT5tYufRvE/eL1 4zbuYZN7HV3A5WR+/Dp82QO7PgQriyGO/ScPERd4ZCOWgtaJZrgJVlnPTb8nTzmALH HIEl6h1EVNp2Ud3RtM6EAZqa/kLLLBYCneqNK2ug=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1367005934; i=@resistor.net; bh=VwKS6n+6zHm6FxoGh8Gv3sZslQU5A34q1eMGFQ9vsAM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dF9dVPjWPmD1Xh2CNTXfphDE+5cX6BS9vAU6UmkI1zFFZ6FrpyhENF1RmiQ6KoU+6 Fe+pj5UOkdw529B0E8qtyRgXeP+YOth36kVXoSNl8Uxur8cfnOJG+Twr9LP2nXLQGR A6QVlurEeVlYXm1sIK4GBFKbIfq+KfajQyZVU56w=
Message-Id: <6.2.5.6.2.20130426121512.0c62c3b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 26 Apr 2013 12:47:41 -0700
To: <adrian@olddog.co.uk>, <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: RE: Last Call: <draft-sheffer-running-code-04.txt> (Improving	Awareness of Running Code: the Implementation Status Section) to	Experimental RFC
In-Reply-To: <025101ce4249$475483d0$d5fd8b70$@olddog.co.uk>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130425152040.0d3fbaa8@resistor.net> <025101ce4249$475483d0$d5fd8b70$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: The IESG <noreply@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 19:52:22 -0000

Hi Adrian,
At 23:42 25-04-2013, Adrian Farrel wrote:
>Hmmm, you can't be sure what order we wrote them. You can only know what order
>they are presented in :-)

I like the finesse of the technical argument. :-)

>I think you are right. Of course, individuals pushing drafts to the 
>ISE could do
>the same thing, but that is probably out of scope for us.

The ISE could even point to your document as useful advice for 
individuals pushing drafts in the Independent Stream.

>Agreed. Some implementations and some interop is undocumented and we have to
>take it "on trust".
>We should probably say that giving references in support would be highly
>desirable.

Yes.  I'll defer to the authors on whether to add text or not.

>I think that when we publish our analysis of results, this will either be
>replaced with something firmer or moved to historic.

Ok.  That should be a simple matter.

Regards,
-sm 


From brian.e.carpenter@gmail.com  Fri Apr 26 12:59:45 2013
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 3F83E21F9949 for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 12:59:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lIgRJXJ8bQuf for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 12:59:44 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id C49F621F9947 for <ietf@ietf.org>; Fri, 26 Apr 2013 12:59:44 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id q10so271975pdj.26 for <ietf@ietf.org>; Fri, 26 Apr 2013 12:59:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=yzuQ43kfTDDiAxAOV2uMKI+djvFwN6fyTaHtC6KL5aY=; b=u+uk0i7zuiaFxkmqwDWd1dhZOdNEg6KR/QiV2VSCHMRqCYtYiQodjK3gxojxKpZCeb eOcDUZjpgv9MWH9Xjnw1rkJUSVV7Rcqm5XE11FM1HXOsEqtLAgUrbZi0aEHYH2UYhjy0 zi+rpo8dzDWnrdZDcLb1AohFdy+6TPSRJh110AmsYZ1rMZyNEqsQA5+1YlZdmXNI4jhw sVRiJTzrUfkK/cIWCoqjWFWGIqLJOuMHvbP4SiCEAsJtkNy3QvbiJeaCPGVAuvYDVdS7 geoupaRhRbTuJVAU82keCAt+8MAQ4DvT6xY/XKN9fMcCP1LsepESfhVXteXcDcBWFSAo cokw==
X-Received: by 10.68.17.8 with SMTP id k8mr34023637pbd.102.1367006384615; Fri, 26 Apr 2013 12:59:44 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id v5sm1382136pbz.4.2013.04.26.12.59.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Apr 2013 12:59:43 -0700 (PDT)
Message-ID: <517ADCB8.4030103@gmail.com>
Date: Sat, 27 Apr 2013 07:59:52 +1200
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: Alessandro Vesely <vesely@tana.it>
Subject: Re: W3C standards and the Hollyweb
References: <5178F97A.5050508@tana.it>	<A28F7DFA-4259-49FD-96DD-76582830177A@mnot.net> <517A673A.6030906@tana.it>
In-Reply-To: <517A673A.6030906@tana.it>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, 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, 26 Apr 2013 19:59:45 -0000

On 26/04/2013 23:38, Alessandro Vesely wrote:
> On Fri 26/Apr/2013 02:53:58 +0200 Mark Nottingham wrote:
>> Personally, I don't have a firm position on these issues, but I couldn't let this pass by.

I've thought about this a bit and looked at some on-line discussions.

In as far as this might be an IETF->W3C liaison issue (and it probably should be),
I would suggest that three points could be made:

1. DRM is a fact of life, and it is therefore better that there should
be a well-formulated standard than a free-for-all. A free-for-all is a
guaranteed route to non-interoperability.

2. DRM should be off by default. That's probably a given (if a content
provider doesn't use EME there will be no DRM) but it needs to be specified.

3. EME should have a very low or zero cost of entry for a content provider.
Quoting from a commenter on The Register:
"The DRM mechanism must allow *individuals* (or small groups) a
low-cost low-hassle way to use it. That's because the way to destroy
the various evil DRM empires is not to steal content - it's to allow
creators to manage the sale of their own creations without needing a
big bad bloodsucker to "help" them. That means a DRM system that anybody
can use to protect their own stuff."

    Brian

From tbray@textuality.com  Fri Apr 26 13:55:25 2013
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3767521F9965 for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 13:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.452
X-Spam-Level: 
X-Spam-Status: No, score=0.452 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPCvolzuzz7a for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 13:55:24 -0700 (PDT)
Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id CC33821F9855 for <ietf@ietf.org>; Fri, 26 Apr 2013 13:55:22 -0700 (PDT)
Received: by mail-vb0-f54.google.com with SMTP id w16so3941003vbf.13 for <ietf@ietf.org>; Fri, 26 Apr 2013 13:55:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=sqbB7V4eTntboUVXUewCX2JgVtQ9PpJ8m0XBQN6TuJg=; b=J1dhu5x4rNntHeanTR4KrrvJzhfdBU6wqOzyT9r2ecDXhGqIKk9GYZgwzq3GcuBVi0 bHHFAPELjhxbE5Ci1Iap8ZYKMowBhbHqmf7yETMfIm7139peJ6BaoDaKZVt4kayyHXQK cA4846+qfzPvos+73/Z45ZwB5gDWrYCyXAMTaKTHpJxVbz2pngiAP/AbHvs8FSldvrqK P4rkyY+kdvn0K9JBYq9/qrLs738An7mMsV+741cml/fpzT88xhUK1qD2QJTQwc2UtiVM uX2+W4O6lIfH/IDU98Xu83bwBawPxSD9FWPLyt8pyMqmKlYlbMZ6NUN+/xfvECinUCyB HPVg==
MIME-Version: 1.0
X-Received: by 10.52.0.147 with SMTP id 19mr24946420vde.97.1367009719568; Fri, 26 Apr 2013 13:55:19 -0700 (PDT)
Received: by 10.220.26.4 with HTTP; Fri, 26 Apr 2013 13:55:19 -0700 (PDT)
X-Originating-IP: [96.49.81.176]
In-Reply-To: <517ADCB8.4030103@gmail.com>
References: <5178F97A.5050508@tana.it> <A28F7DFA-4259-49FD-96DD-76582830177A@mnot.net> <517A673A.6030906@tana.it> <517ADCB8.4030103@gmail.com>
Date: Fri, 26 Apr 2013 13:55:19 -0700
Message-ID: <CAHBU6iu7eWed1MaRcsBjUCXQR8pLRJuPYYRz+vbhpb9-etKO+A@mail.gmail.com>
Subject: Re: W3C standards and the Hollyweb
From: Tim Bray <tbray@textuality.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bacc5d6bd630504db49c082
X-Gm-Message-State: ALoCoQlbYMZHTMeKLsdziFn5oLRtF6Y1A0wxFuchoniI6JtuwvvDfVWffIToiPUm0XkDSyWD0AtP
Cc: Mark Nottingham <mnot@mnot.net>, IETF-Discussion Discussion <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 20:55:25 -0000

--047d7bacc5d6bd630504db49c082
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 26, 2013 at 12:59 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> 1. DRM is a fact of life, and it is therefore better that there should
> be a well-formulated standard than a free-for-all. A free-for-all is a
> guaranteed route to non-interoperability.
>

Crack cocaine, prostitution, and political corruption are also facts of
life.

OK, pardon the cheap shot, but I don=92t think SDOs that have some sort of
stewardship relationship to the Internet should ever play any part
whatsoever in the facilitation of DRM.

I won=92t consume your input bandwidth by backing up this position; the
arguments pro and contra DRM are not exactly secret, and I haven=92t heard
any new ones in some years.  -T

--047d7bacc5d6bd630504db49c082
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Apr 26, 2013 at 12:59 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpent=
er@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">1. DRM is a fact of life, and it is therefor=
e better that there should<br>
be a well-formulated standard than a free-for-all. A free-for-all is a<br>
guaranteed route to non-interoperability.<br></blockquote><div><br></div><d=
iv>Crack cocaine, prostitution, and political corruption are also facts of =
life. <br><br></div><div>OK, pardon the cheap shot, but I don=92t think SDO=
s that have some sort of stewardship relationship to the Internet should ev=
er play any part whatsoever in the facilitation of DRM.=A0 <br>
<br>I won=92t consume your input bandwidth by backing up this position; the=
 arguments pro and contra DRM are not exactly secret, and I haven=92t heard=
 any new ones in some years.=A0 -T<br></div><br></div><br></div></div>

--047d7bacc5d6bd630504db49c082--

From Josh.Howlett@ja.net  Fri Apr 26 14:24:03 2013
Return-Path: <Josh.Howlett@ja.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 AC55321F9A27 for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 14:24:03 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EAB9JJknSeXt for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 14:24:03 -0700 (PDT)
Received: from har003676.ukerna.ac.uk (har003676.ukerna.ac.uk [194.82.140.75]) by ietfa.amsl.com (Postfix) with ESMTP id 63F8321F9952 for <ietf@ietf.org>; Fri, 26 Apr 2013 14:23:59 -0700 (PDT)
Received: from har003676.ukerna.ac.uk (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 3710B4A6B9E_17AF066B; Fri, 26 Apr 2013 21:23:50 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk (exc001.atlas.ukerna.ac.uk [193.62.83.37]) by har003676.ukerna.ac.uk (Sophos Email Appliance) with ESMTP id 68C9A4A6B9C_17AF065F; Fri, 26 Apr 2013 21:23:49 +0000 (GMT)
Received: from EXC001.atlas.ukerna.ac.uk ([193.62.83.37]) by EXC001 ([193.62.83.37]) with mapi id 14.02.0247.003; Fri, 26 Apr 2013 22:23:48 +0100
From: Josh Howlett <Josh.Howlett@ja.net>
To: Tim Bray <tbray@textuality.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: W3C standards and the Hollyweb
Thread-Topic: W3C standards and the Hollyweb
Thread-Index: AQHOQZjMMZfTYoROVEKH+KdDqu/qhpjnnRwAgAC0GQCAAIwQAIAAD36AgAAYsIA=
Date: Fri, 26 Apr 2013 21:23:48 +0000
Message-ID: <CDA0ACDA.2124A%josh.howlett@ja.net>
In-Reply-To: <CAHBU6iu7eWed1MaRcsBjUCXQR8pLRJuPYYRz+vbhpb9-etKO+A@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [194.82.140.76]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8A21775C46D6E547A15F341735391957@ukerna.ac.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Mark Nottingham <mnot@mnot.net>, IETF-Discussion Discussion <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Apr 2013 21:24:04 -0000

>
>OK, pardon the cheap shot, but I don=B9t think SDOs that have some sort of
>stewardship relationship to the Internet should ever play any part
>whatsoever in the facilitation of DRM.

So it's ok to define protocols that manage access to services (e.g., TLS,
GSS, SASL, etc), but not to the content that might be delivered by those
same services? Barring the technicalities around around how authorisation
is enforced, I don't see a distinction.

Josh.


Janet(UK) is a trading name of Jisc Collections and Janet Limited, a=20
not-for-profit company which is registered in England under No. 2881024=20
and whose Registered Office is at Lumen House, Library Avenue,
Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238


From stephen.farrell@cs.tcd.ie  Fri Apr 26 14:41:14 2013
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 680C421F9A1B for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 14:41:14 -0700 (PDT)
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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtufdPDsX9Ls for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 14:41:13 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 2F4A821F911E for <ietf@ietf.org>; Fri, 26 Apr 2013 14:41:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 6F73CBE59; Fri, 26 Apr 2013 22:40:50 +0100 (IST)
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 0iD4FqAC0swl; Fri, 26 Apr 2013 22:40:49 +0100 (IST)
Received: from [10.87.48.4] (unknown [86.41.15.55]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id A2AECBE25; Fri, 26 Apr 2013 22:40:34 +0100 (IST)
Message-ID: <517AF403.8090101@cs.tcd.ie>
Date: Fri, 26 Apr 2013 22:39:15 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Josh Howlett <Josh.Howlett@ja.net>
Subject: Re: W3C standards and the Hollyweb
References: <CDA0ACDA.2124A%josh.howlett@ja.net>
In-Reply-To: <CDA0ACDA.2124A%josh.howlett@ja.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Mark Nottingham <mnot@mnot.net>, Alessandro Vesely <vesely@tana.it>, Tim Bray <tbray@textuality.com>, IETF-Discussion 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: Fri, 26 Apr 2013 21:41:14 -0000

On 04/26/2013 10:23 PM, Josh Howlett wrote:
>>
>> OK, pardon the cheap shot, but I don¹t think SDOs that have some sort of
>> stewardship relationship to the Internet should ever play any part
>> whatsoever in the facilitation of DRM.
> 
> So it's ok to define protocols that manage access to services (e.g., TLS,
> GSS, SASL, etc), but not to the content that might be delivered by those
> same services? Barring the technicalities around around how authorisation
> is enforced, I don't see a distinction.

Some technicalities count: DRM schemes are always easily broken
by anyone who cares. Personally, I think that's a good reason
to discourage work on them.

S.


> 
> Josh.
> 
> 
> Janet(UK) is a trading name of Jisc Collections and Janet Limited, a 
> not-for-profit company which is registered in England under No. 2881024 
> and whose Registered Office is at Lumen House, Library Avenue,
> Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238
> 

From mrex@sap.com  Fri Apr 26 14:54:02 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 827C821F988A for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 14:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id faLEeyOzDtTP for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 14:54:00 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0602E21F98EA for <ietf@ietf.org>; Fri, 26 Apr 2013 14:53:57 -0700 (PDT)
Received: from mail06.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r3QLrtnW011386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Apr 2013 23:53:55 +0200 (MEST)
Subject: Re: W3C standards and the Hollyweb
In-Reply-To: <517ADCB8.4030103@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Fri, 26 Apr 2013 23:53:54 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130426215354.EA0731A6D6@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: Fri, 26 Apr 2013 21:54:02 -0000

Brian E Carpenter wrote:
>
> 3. EME should have a very low or zero cost of entry for a content provider.

DRM system are evil in any way you look at it.

Originally, copyright was a conceived as a temporary (50yrs) monopoly.
The protection period has in recent years been prolonged in many years
to at least 70 years.

When you add DRM into the picture, the monopoly will effectively
*FOREVER*, because there is unlikely going to be someone around
to remove the DRM protection after that time has passed, and
it may also easily happen that the data format is not supported
that long -- and converting the data to a newer format is what
DRM is made to prevent among lots of other things...


-Martin

From sm@resistor.net  Fri Apr 26 16:13:04 2013
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 BB23E21F9D0B for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 16:13:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Siq-el3MLkKo for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 16:13:01 -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 D50FB21F9D0E for <ietf@ietf.org>; Fri, 26 Apr 2013 16:13:01 -0700 (PDT)
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 r3QNCtpI021615; Fri, 26 Apr 2013 16:12:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367017980; bh=UMuNb0yX+Nc7qvEq2SaqxjkjC4/w18hKftIx80R03Ls=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QhAd1tI+QetKN857LLhPhk7FMGXxNSEPLbWz8I+cY0gly8rwZ9EK0zsflXNY+rh74 tQj3B1FgjPvYa6OE8NlswYP4Es6j2w0w5/r3RWqEXrDbEAEbHvApkZNdQ9WcPh/gbw cs7PjvQuWr2bPsachvZo3Z0G9dHpYLn6s5T8ptgE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1367017980; i=@resistor.net; bh=UMuNb0yX+Nc7qvEq2SaqxjkjC4/w18hKftIx80R03Ls=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=n/swhx6dzoY5thNzWGiOacwrpc7dj0COra3Xd6K6jsnkZqD9YAU+WArjKPXULil/w TESGDLgQkKvrbw9/bZJL24uyR7wD+vFPbPa3nBfSXsQV3dVs3EYdKP9FzhWyp0UWYT BQSAYvEeCP90Rr2H/lFXMimCTx4oYlKS6aU4ABvU=
Message-Id: <6.2.5.6.2.20130426145429.0c362230@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 26 Apr 2013 16:03:45 -0700
To: Alessandro Vesely <vesely@tana.it>
From: SM <sm@resistor.net>
Subject: Re: W3C standards and the Hollyweb
In-Reply-To: <5178F97A.5050508@tana.it>
References: <5178F97A.5050508@tana.it>
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, 26 Apr 2013 23:13:04 -0000

At 02:38 25-04-2013, Alessandro Vesely wrote:
>The Encrypted Media Extensions (EME, a.k.a. DRM in HTML5)
>specification is not a real DRM itself.  It provides for add-on parts
>described as Content Decryption Modules that provide DRM functionality
>for one or more Key Systems.  DRMs are obviously designed to be
>non-interoperable, and EME is a standard for managing such
>non-standard stuff.  That is going to break interoperability, as any
>given browser will inevitably miss some decryption modules.

I read 
https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html 
 From what I understand "Digital Rights Management technologies 
attempts to control what I can and can't do with the media and 
hardware I have purchased".  I did some reading [1] and I found that:

   "An open DRM interoperability standard accelerates content consumption in
    the home network and propels device volume growth and thus benefits the
    consumers, the content owners and the device manufacturers"

I found that hard to believe.  There is a paper about "a weakness in 
the High Bandwidth Digital Content Protection (HDCP) scheme which may 
lead to practical attacks" [2].  Someone found a way put the theory 
into practice.

There was a paper about "The Darknet and the Future of Content 
Distribution" [3].  Quoting the Introduction:

   "People have always copied things. In the past, most items of value were
    physical objects. Patent law and economies of scale meant that small scale
    copying of physical objects was usually uneconomic, and large-scale copying
    (if it infringed) was stoppable using policemen and courts."

I suggest reading the paper.

Regards,
-sm

1. http://www.ietf.org/proceedings/60/slides/perm-4.pdf
2. 
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.70.184&rep=rep1&type=pdf
3. http://crypto.stanford.edu/DRM2002/darknet5.doc


From derhoermi@gmx.net  Fri Apr 26 18:01:24 2013
Return-Path: <derhoermi@gmx.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 3F05221F9D00 for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 18:01:24 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gM-AO7lMnw4x for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 18:01:23 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id B379A21F9D07 for <ietf@ietf.org>; Fri, 26 Apr 2013 18:01:22 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.29]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0Lg2uj-1UoziE0f4V-00paqa for <ietf@ietf.org>; Sat, 27 Apr 2013 03:01:21 +0200
Received: (qmail invoked by alias); 27 Apr 2013 01:01:20 -0000
Received: from p5B230B74.dip0.t-ipconnect.de (EHLO netb.Speedport_W_700V) [91.35.11.116] by mail.gmx.net (mp029) with SMTP; 27 Apr 2013 03:01:20 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/ullUnv6ru9tjQoevBuHOtaCWXg3hgq2gpOKRRrs cT8RT+63r0Bls4
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: W3C standards and the Hollyweb
Date: Sat, 27 Apr 2013 03:01:23 +0200
Message-ID: <044mn8ttles7g5gl49lisg2tkel0h5tgs7@hive.bjoern.hoehrmann.de>
References: <5178F97A.5050508@tana.it>
In-Reply-To: <5178F97A.5050508@tana.it>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 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: Sat, 27 Apr 2013 01:01:24 -0000

* Alessandro Vesely wrote:
>If you haven't done so already, please sign the FSF petition:
>http://www.defectivebydesign.org/no-drm-in-html5

The W3C is asking for comments on its "Encrypted Media Extensions" pro-
posal, including on whether W3C should continue work on the document, to
be sent to the publically archived public-html-media@w3.org mailing list
(see the "Status of This Document" section of the proposal).

A few days before I attended my first W3C meeting, hundreds of people
answered a similar call for comments via e-mail. Tim Bray, Alan Cox,
Theo de Raadt, Aaron Swartz, Richard Stallman, Tim O'Reilly, Jeffrey
Zeldman, Eric S. Raymond, Tim Berners-Lee and many others shared their
thoughts on the Patent Policy the W3C was proposing back then on W3C's
list, <http://lists.w3.org/Archives/Public/www-patentpolicy-comment/>.

In contrast, <http://lists.w3.org/Archives/Public/public-html-media/>
has almost no relevant comments. If people have nothing to say, they
will not be heard.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From mnot@mnot.net  Fri Apr 26 23:40:10 2013
Return-Path: <mnot@mnot.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 09A7821F9A1B for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 23:40:10 -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=[AWL=-2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n+6vWx1c-KX0 for <ietf@ietfa.amsl.com>; Fri, 26 Apr 2013 23:40:09 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 44FEC21F99CC for <ietf@ietf.org>; Fri, 26 Apr 2013 23:40:09 -0700 (PDT)
Received: from mnot-mini.mnot.net (unknown [118.209.190.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 74F5E509B5; Sat, 27 Apr 2013 02:40:06 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: W3C standards and the Hollyweb
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <517A673A.6030906@tana.it>
Date: Sat, 27 Apr 2013 16:40:03 +1000
Content-Transfer-Encoding: 7bit
Message-Id: <7F2B5742-573A-49B4-9DD7-B6CC6DBC61F3@mnot.net>
References: <5178F97A.5050508@tana.it> <A28F7DFA-4259-49FD-96DD-76582830177A@mnot.net> <517A673A.6030906@tana.it>
To: Alessandro Vesely <vesely@tana.it>
X-Mailer: Apple Mail (2.1503)
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, 27 Apr 2013 06:40:10 -0000

On 26/04/2013, at 9:38 PM, Alessandro Vesely <vesely@tana.it> wrote:
> 
>>> Injecting DRM through EME is a disservice to web standardization,
>>> since the latter is supposed to foster the Internet revolution.
>> 
>> What does that *mean*? I'm wary of waving around banners like "the
>> Internet revolution", since they can so easily be misused.
> 
> The Internet revolution is the big step after the industrial
> revolution.  I didn't mean to misuse that banner:  It is a typical
> effect of industrial revolution to bring many workers to some large
> factories.  Free-software development, for a counter example, doesn't
> fit into that model.  I'd agree that the phenomenon is still young and
> that the economics of the new model definitely need to be improved.
> However, that cannot be done while sticking to the old production
> model.  Which direction is the media industry heading to?
> 
> Watch-on-demand could have been implemented on private networks and
> proprietary equipment.  However, cables had not been laid until the
> Internet took root, and that was pushed by the web.  The direction of
> history seems to be clear enough to allow taking a firm position.

Well said. 


> If you haven't done so already, please sign the FSF petition:
> http://www.defectivebydesign.org/no-drm-in-html5

--
Mark Nottingham   http://www.mnot.net/




From vesely@tana.it  Sat Apr 27 01:02:36 2013
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 D7CDD21F9DBC for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 01:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.689
X-Spam-Level: 
X-Spam-Status: No, score=-4.689 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FDX3UgUdBeLF for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 01:02:35 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 1009721F9DB9 for <ietf@ietf.org>; Sat, 27 Apr 2013 01:02:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1367049751; bh=u2VBBrbmOihIRIdGdI7gMn5/L3BBVuGjMnOPKFarQTk=; l=1241; h=Date:From:To:CC:References:In-Reply-To; b=Vd2OC0Ya2yyGty8zX00Wru+IH7sM1OpCD6hMahtzjIdPDQ4ZmndbgFQT0Co8fWINE inkWKl7zhmn23qUt7P5p+6WpHtuulw3u7UAkpowuwD6E1CY/NeSblEd0PEgWWnzYau ePclgJBe8y0r3OzFqnRtjMJJJ1fGdtkNfqXPNI2o=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Sat, 27 Apr 2013 10:02:31 +0200 id 00000000005DC035.00000000517B8617.000001C8
Message-ID: <517B8617.4010502@tana.it>
Date: Sat, 27 Apr 2013 10:02:31 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: W3C standards and the Hollyweb
References: <5178F97A.5050508@tana.it>	<A28F7DFA-4259-49FD-96DD-76582830177A@mnot.net> <517A673A.6030906@tana.it> <517ADCB8.4030103@gmail.com>
In-Reply-To: <517ADCB8.4030103@gmail.com>
Content-Type: text/plain; charset=us-ascii
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, 27 Apr 2013 08:02:37 -0000

On Fri 26/Apr/2013 21:59:52 +0200 Brian E Carpenter wrote:
> 
> 3. EME should have a very low or zero cost of entry for a content provider.
> Quoting from a commenter on The Register:
>  "The DRM mechanism must allow *individuals* (or small groups) a
>   low-cost low-hassle way to use it. That's because the way to destroy
>   the various evil DRM empires is not to steal content - it's to allow
>   creators to manage the sale of their own creations without needing a
>   big bad bloodsucker to "help" them. That means a DRM system that anybody
>   can use to protect their own stuff."

A DRM add-on that individuals or small groups use to protect their
stuff seems to be a chimera.  Manu Sporny [1] points out that even
Microsoft is unable to support Silverlight on Internet Explorer 8 on
older versions of their operating system and the latest version of
Chrome on certain versions of Windows and Mac.  Can small groups be
expected to do better?

A comparison with youtube suggests that yet another software barrier
is not what small media producers really need.

[1] http://manu.sporny.org/2013/drm-in-html5/

-- 
If you haven't done so already, please sign the FSF petition:
http://www.defectivebydesign.org/no-drm-in-html5

From john-ietf@jck.com  Sat Apr 27 08:30:10 2013
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 64A7721F9858; Sat, 27 Apr 2013 08:30:10 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fbs7uuHqw+IT; Sat, 27 Apr 2013 08:30:09 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C77B421F93BA; Sat, 27 Apr 2013 08:30:09 -0700 (PDT)
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 1UW74e-000LOU-8U; Sat, 27 Apr 2013 11:30:04 -0400
Date: Sat, 27 Apr 2013 11:29:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>, adrian@olddog.co.uk, ietf@ietf.org
Subject: RE: Last Call: <draft-sheffer-running-code-04.txt>	(Improving	Awareness of Running Code: the Implementation Status	Section) to	Experimental RFC
Message-ID: <6670EF45ECB3407277ED129D@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20130426121512.0c62c3b0@resistor.net>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130425152040.0d3fbaa8@resistor.net> <025101ce4249$475483d0$d5fd8b70$@olddog.co.uk> <6.2.5.6.2.20130426121512.0c62c3b0@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: The IESG <noreply@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Apr 2013 15:30:10 -0000

--On Friday, April 26, 2013 12:47 -0700 SM <sm@resistor.net>
wrote:

>...
>> I think you are right. Of course, individuals pushing drafts
>> to the  ISE could do
>> the same thing, but that is probably out of scope for us.
> 
> The ISE could even point to your document as useful advice for
> individuals pushing drafts in the Independent Stream.

This piece of the discussion interacts with another issue.
There has been pushback from time to time about either
Independent Submissions or Informational documents generally
containing normative statements of any kind.  Personally, I
think that is an excess of caution that leads to convoluted
workarounds that don't help anyone, but others disagree.

We will probably find more out about this as the experiment runs
but my guess is that implementation statements will have much
less value if they say "we implemented something like what is
specified here" rather than "to the best of our understanding,
we have an implementation that conforms to this specification".
It is hard to the do latter, or to talk about conformance at
all, in the absence of normative and/or conformance statements.
Interoperability reports have much the same problem: if a
specification doesn't contain any normative statements, it
becomes difficult to even guess which of a pair of
implementations that don't interoperate is actually operating as
intended.[1]

So I recommend that we continue to concentrate this effort on
Standards Track protocol specification documents (as the I-D now
does) and start worrying about the various other cases after we
see where the current proposed experiment that leads us.

   john



[1] The community has some history of settling that problem by
examining several implementations, figuring out which
interpretation is used by more of them than others, and then
changing the specs to match.  That scenario has certainly not
been the tendency in recent years.



From johnsonhammond2@hushmail.com  Sat Apr 27 09:54:12 2013
Return-Path: <johnsonhammond2@hushmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C25321F9835 for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 09:54:12 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWThxD0Rz+Yt for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 09:54:12 -0700 (PDT)
Received: from smtp5.hushmail.com (smtp5a.hushmail.com [65.39.178.235]) by ietfa.amsl.com (Postfix) with ESMTP id F251B21F8529 for <ietf@ietf.org>; Sat, 27 Apr 2013 09:54:11 -0700 (PDT)
Received: from smtp5.hushmail.com (smtp5a.hushmail.com [65.39.178.235]) by smtp5.hushmail.com (Postfix) with SMTP id AEF90580A5 for <ietf@ietf.org>; Sat, 27 Apr 2013 16:54:11 +0000 (UTC)
Received: from smtp.hushmail.com (w8.hushmail.com [65.39.178.52]) by smtp5.hushmail.com (Postfix) with ESMTP for <ietf@ietf.org>; Sat, 27 Apr 2013 16:54:11 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99) id 787B314DBDE; Sat, 27 Apr 2013 16:54:11 +0000 (UTC)
MIME-Version: 1.0
Date: Sat, 27 Apr 2013 12:54:11 -0400
To: ietf@ietf.org
Subject: Biggest Fake Conference in Computer Science
From: johnsonhammond2@hushmail.com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20130427165411.787B314DBDE@smtp.hushmail.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, 27 Apr 2013 18:22:37 -0000

Biggest Fake Conference in Computer Science


We are researchers from different parts of the world and conducted a study on  
the world’s biggest bogus computer science conference WORLDCOMP 
( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia 
from University of Georgia, USA.


We submitted a fake paper to WORLDCOMP 2011 and again (the same paper 
with a modified title) to WORLDCOMP 2012. This paper had numerous 
fundamental mistakes. Sample statements from that paper include: 

(1). Binary logic is fuzzy logic and vice versa
(2). Pascal developed fuzzy logic
(3). Object oriented languages do not exhibit any polymorphism or inheritance
(4). TCP and IP are synonyms and are part of OSI model 
(5). Distributed systems deal with only one computer
(6). Laptop is an example for a super computer
(7). Operating system is an example for computer hardware


Also, our paper did not express any conceptual meaning.  However, it 
was accepted both the times without any modifications (and without 
any reviews) and we were invited to submit the final paper and a 
payment of $500+ fee to present the paper. We decided to use the 
fee for better purposes than making Prof. Hamid Arabnia (Chairman 
of WORLDCOMP) rich. After that, we received few reminders from 
WORLDCOMP to pay the fee but we never responded. 


We MUST say that you should look at the above website if you have any thoughts 
to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have stopped 
indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See 
http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the 
conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of
http://sites.google.com/site/dumpconf for comments from well-known researchers 
about WORLDCOMP. 


The status of your WORLDCOMP papers can be changed from scientific
to other (i.e., junk or non-technical) at any time. Better not to have a paper than 
having it in WORLDCOMP and spoil the resume and peace of mind forever!


Our study revealed that WORLDCOMP is a money making business, 
using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing 
out a small chunk of that money (around 20 dollars per paper published 
in WORLDCOMP’s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) 
who publicizes WORLDCOMP and also defends it at various forums, using 
fake/anonymous names. The puppet uses fake names and defames other conferences
to divert traffic to WORLDCOMP. He also makes anonymous phone calls and tries to 
threaten the critiques of WORLDCOMP (See Item 7 of Section 5 of above website). 
That is, the puppet does all his best to get a maximum number of papers published 
at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia’s) pockets. 


Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until 2012) has 
refused to provide the venue for WORLDCOMP’13 because of the fears of their image 
being tarnished due to WORLDCOMP’s fraudulent activities. That is why WORLDCOMP’13 
is taking place at a different resort. WORLDCOMP will not be held after 2013. 


The draft paper submission deadline is over but still there are no committee 
members, no reviewers, and there is no conference Chairman. The only contact 
details available on WORLDCOMP’s website is just an email address! 

Let us make a direct request to Prof. Hamid arabnia: publish all reviews for 
all the papers (after blocking identifiable details) since 2000 conference. Reveal 
the names and affiliations of all the reviewers (for each year) and how many 
papers each reviewer had reviewed on average. We also request him to look at 
the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp1 


Sorry for posting to multiple lists. Spreading the word is the only way to stop 
this bogus conference. Please forward this message to other mailing lists and people. 


We are shocked with Prof. Hamid Arabnia and his puppet’s activities 
http://worldcomp-fake-bogus.blogspot.com   Search Google using the 
keyword worldcomp fake for additional links.


From brian.e.carpenter@gmail.com  Sat Apr 27 12:50:53 2013
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 A274B21F98C1 for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 12:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.682
X-Spam-Level: 
X-Spam-Status: No, score=-102.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSrHPg48V+SJ for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 12:50:53 -0700 (PDT)
Received: from mail-da0-x234.google.com (mail-da0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id D70E021F98C8 for <ietf@ietf.org>; Sat, 27 Apr 2013 12:50:52 -0700 (PDT)
Received: by mail-da0-f52.google.com with SMTP id j17so2390143dan.25 for <ietf@ietf.org>; Sat, 27 Apr 2013 12:50:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XZ/fdW6pBWkjL4uj4IR3MhWPzrmg8nwGue2W0eHiYfE=; b=wjO3znzu2aDykGaefrwgBjlXyT8P6GFjG/RoiA12JxyQUn0IFzTa19D8J0Z/h1Ustz buzHzgEGMmKvaxltUxdHDgsmRBoU7Tqhb/lv31Lv0KR5OlUy4kM6R8d2vL79zOZbFzB5 deVe5//kdlAgbHU2Wp0yQSkRL4ODSlYNlezXZmGZZg9oa9mmKDtUtXBS1UD3/2P5pKzZ 9bv1fk0UGRfD8yOS/epu9QZvx9G3SELGtfestEDfR/PlYoFDQXq0r1I8vrM3DnWNeBnF liqnu4TOQ3j9+rsGVtOsjI5ELFR63lfwiPTBH+XRPafG35ipe1cXeZZ88MlOaYmxWqk7 TlPg==
X-Received: by 10.66.233.167 with SMTP id tx7mr36198858pac.110.1367092252672;  Sat, 27 Apr 2013 12:50:52 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id xz4sm17006343pbb.18.2013.04.27.12.50.49 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Apr 2013 12:50:51 -0700 (PDT)
Message-ID: <517C2C17.1060507@gmail.com>
Date: Sun, 28 Apr 2013 07:50:47 +1200
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.org
Subject: Re: Biggest Fake Conference in Computer Science
References: <20130427165411.787B314DBDE@smtp.hushmail.com>
In-Reply-To: <20130427165411.787B314DBDE@smtp.hushmail.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, 27 Apr 2013 19:50:53 -0000

As a list admin, I have (a) instantly unsubscribed the sender
(b) put the sender in the 'forbidden to subscribe' list
(c) sent him a message telling him he can ask to be resubscribed
if he wants to post on-topic.

No, I didn't worry what any process RFC might say.

Regards
   Brian Carpenter

From brian.e.carpenter@gmail.com  Sat Apr 27 12:53:28 2013
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 6C83421F95DB for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 12:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level: 
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[AWL=0.429, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7viq9kdE6PaR for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 12:53:28 -0700 (PDT)
Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) by ietfa.amsl.com (Postfix) with ESMTP id 0556C21F938F for <ietf@ietf.org>; Sat, 27 Apr 2013 12:53:27 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id bg2so405537pad.37 for <ietf@ietf.org>; Sat, 27 Apr 2013 12:53:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=aToyU5G/oa6cTSVoAhdj13nxD4q8ehiwKKcCpASejUs=; b=rDEyjsbqjjoIFYSzlJODRGGH5kpWSYdHiN3L7NcVxfzwSjGezSduOuETxpBJBfL0zY TuPACaPMWYSPUfpWDoBLIX8q1gjz6rcxTOiUPSu72Z6thbksKgwl6J+cZdu8eHIfLaHW 4KVdKwh54X2dgTIbYINUhS5Ogur8fpC/88IaUaaycFhlGAY3ZJ4HMigqSlvcFFucObGk pvPZKhtHBjRfFkfT4reWuu/AUKa4/iHTXYonN/wrD9gqvix2w41bIarukOW90wnDGHyz uU4EV5gTtlmt49Gex9rdUgGqCDiQua57EdDF6T59aAjksJkEciOeW9LumwOcR+/BER69 n8gg==
X-Received: by 10.66.119.5 with SMTP id kq5mr39957110pab.193.1367092407852; Sat, 27 Apr 2013 12:53:27 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id vv6sm18410916pab.6.2013.04.27.12.53.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 27 Apr 2013 12:53:26 -0700 (PDT)
Message-ID: <517C2CB2.6010101@gmail.com>
Date: Sun, 28 Apr 2013 07:53:22 +1200
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: Alessandro Vesely <vesely@tana.it>
Subject: Re: W3C standards and the Hollyweb
References: <5178F97A.5050508@tana.it>	<A28F7DFA-4259-49FD-96DD-76582830177A@mnot.net> <517A673A.6030906@tana.it> <517ADCB8.4030103@gmail.com> <517B8617.4010502@tana.it>
In-Reply-To: <517B8617.4010502@tana.it>
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, 27 Apr 2013 19:53:28 -0000

On 27/04/2013 20:02, Alessandro Vesely wrote:

> A DRM add-on that individuals or small groups use to protect their
> stuff seems to be a chimera.  

Has anybody tried to design one?

   Brian

From sm@resistor.net  Sat Apr 27 16:30:27 2013
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 72F1F21F98C1 for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 16:30:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PuGQwlQTLPtE for <ietf@ietfa.amsl.com>; Sat, 27 Apr 2013 16:30:26 -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 C425521F9822 for <ietf@ietf.org>; Sat, 27 Apr 2013 16:30:26 -0700 (PDT)
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 r3RNULoI002011; Sat, 27 Apr 2013 16:30:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367105426; bh=nmAfQMFRpxl4kFM40ZuzE7R5d8JOsIFALiqeYBge6sU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Syl4YHvT6dwFxrkJBiV+kOSv+gr0drWXX3MqQ7N14yC5SyUFE9ZE8kClRMBf5XyGZ ml6x50qGz7H3Wsfcd8lod7ZLKQIPItBf6NEHTTb0uH9Lomtsz5pwXagca1rE7QJnP/ 3LuB6e/stKS/XCjNnvnLPFCIRTQi3AnXhvtSC9Ko=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1367105426; i=@resistor.net; bh=nmAfQMFRpxl4kFM40ZuzE7R5d8JOsIFALiqeYBge6sU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1AeqQJM8g9JpoHcRVTejsAqvA/3xZudYVPGNdQjo3qLSmCGp6a0r3r8DMwrclTwcs Ov3o/fv+dBtEL7E2hSRbI2CMdXVy30XiYDN5j01cBEPtl9mkxuA+j1lwtl0CwwhVEQ 8WRH/PG5IzPhIWgyP/qk9FvvpZF5wQC9IvmPzlrU=
Message-Id: <6.2.5.6.2.20130427143130.0b7fe488@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 27 Apr 2013 15:37:22 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-saintandre-impp-call-info-02.txt> (Instant Messaging and Presence Purpose for the Call-Info Header Field in the Session Initiation Protocol (SIP)) to Proposed Standard
In-Reply-To: <20130416200759.31647.61662.idtracker@ietfa.amsl.com>
References: <20130416200759.31647.61662.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-saintandre-impp-call-info.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Apr 2013 23:30:27 -0000

At 13:07 16-04-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Instant Messaging and Presence Purpose for the Call-Info Header Field
>    in the Session Initiation Protocol (SIP)'
>   <draft-saintandre-impp-call-info-02.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 2013-05-14. Exceptionally, comments may be

This is the shortest soon-to-be Proposed Standard I have seen so 
far.  I had to read the other 541 pages though.  There is a nice 
write-up for the draft.  I see that Jitsi [1] is working on CUSAX [2].

Regards,
-sm

1. https://jitsi.org
2. http://www.kamailio.org/events/2013-KamailioWorld/14-Emil.Ivov-Jitsi.pdf 


From ron.even.tlv@gmail.com  Sun Apr 28 01:31:47 2013
Return-Path: <ron.even.tlv@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 7FBEC21F97CD; Sun, 28 Apr 2013 01:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Pce2SyBr52Y; Sun, 28 Apr 2013 01:31:46 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 8A50D21F97BF; Sun, 28 Apr 2013 01:31:45 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id m6so1836655wiv.7 for <multiple recipients>; Sun, 28 Apr 2013 01:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=DvMD5USsMxsZhydlsJx+28zMSphGwnuBytv27U8h4r0=; b=epILJ/TXQI1bxzWzg1T1cJOhE68/8lmckrZGf207d5nyIxhBdaKEhx1Yppy65GGA0Y DHi5hzHK1WB+uKlpOc7CZ5XpV4UTwhcqtDcMBn+6r5cckWBzvj1vJ1rw+PlQRlhUrXa/ WuWVFc4yMx0KLilINSg25DPKN52Nu1bWMS7M9Y2f7ac0cqzKxpdc5EAlINERsuD1ZFbm ZohGYbR7frzMlIyVBIaibef1Sfju5p1oy29yiGn/vRK6xOZOdszXJSLSMn4Al543VSBN ubU26fQamZHh/cTJit1cWVyjO0ax5UIP78LrrNnblEUXlxfQYxkSRWyGJnsubGRYQSPC K1TQ==
X-Received: by 10.194.93.231 with SMTP id cx7mr28998781wjb.33.1367137904755; Sun, 28 Apr 2013 01:31:44 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPSA id j4sm12971665wiz.10.2013.04.28.01.31.41 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 28 Apr 2013 01:31:43 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org>, <ietf@ietf.org>
Subject: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
Date: Sun, 28 Apr 2013 11:31:05 +0300
Message-ID: <019901ce43ea$bbd575a0$338060e0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_019A_01CE4403.E1239800"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5D6pKryX0MWBh9SKaAMkeLEbN6Nw==
Content-Language: en-us
Cc: gen-art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Apr 2013 08:31:47 -0000

This is a multipart message in MIME format.

------=_NextPart_000_019A_01CE4403.E1239800
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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-netmod-interfaces-cfg-10

Reviewer: Roni Even

Review Date:2013-4-28

IETF LC End Date: 2013-5-3

IESG Telechat date: 2013-5-16

 

Summary: This draft is almost ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

 

1.       I had some problem understanding the "location" leaf. Section 3.2
has it as a string and says that "The device uses the location string to
identify the physical or logical entity that the configuration applies to".
I am not sure how you identify physical location having no definition of the
mapping. I saw the examples in Appendix E and it looked more to me as
logical mapping but not physical since it attaches a name to something in
the device but I am not clear how you know what it is physically in the
device. If the name 0-n or n/m are real physical entities, I think that it
should be specified some place. 

 

 

Nits/editorial comments:

1.	In the introduction section maybe add to the first sentence a
reference to RFC6244 with some text.
2.	In section 2 are the" must" and "should"  used as described in
RFC2119, if yes need capital letters
3.	In section 3.1 "It is optional in the data model,  but if the type
represents a physical interface, it is mandatory", suggest having RFC2119
language "It is OPTIONAL in the data model,  but if the type represents a
physical interface, it is MUST be specified"

 


------=_NextPart_000_019A_01CE4403.E1239800
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-microsoft-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=3DGenerator 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:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1169102253;
	mso-list-type:hybrid;
	mso-list-template-ids:876275048 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1947733698;
	mso-list-type:hybrid;
	mso-list-template-ids:91134052 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-netmod-interfaces-cfg-10</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;4&#8211;28<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-5&#8211;3<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: 2013-5-16<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I had some =
problem understanding the &#8220;location&#8221; leaf. Section 3.2 has =
it as a string and says that </span>&#8220;<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The device =
uses the location string to identify the physical or logical entity that =
the configuration applies to&#8221;. I am not sure how you identify =
physical location having no definition of the mapping. I saw the =
examples in Appendix E and it looked more to me as logical mapping but =
not physical since it attaches a name to something in the device but I =
am not clear how you know what it is physically in the device. If the =
name 0-n or n/m are real physical entities, I think that it should be =
specified some place. <o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l1 level1 lfo2'>In the =
introduction section maybe add to the first sentence a reference to =
RFC6244 with some text.<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo2'>In section 2 are the&#8221; =
must&#8221; and &#8220;should&#8221;&nbsp; used as described in RFC2119, =
if yes need capital letters<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo2'>In section 3.1 &#8220;It is optional =
in the data model,&nbsp; but if the type represents a physical =
interface, it is mandatory&#8221;, suggest having RFC2119 language =
&#8220;It is OPTIONAL in the data model,&nbsp; but if the type =
represents a physical interface, it is MUST be =
specified&#8221;<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_019A_01CE4403.E1239800--


From abdussalambaryun@gmail.com  Sun Apr 28 04:00:57 2013
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 51D3521F99CC; Sun, 28 Apr 2013 04:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.919
X-Spam-Level: 
X-Spam-Status: No, score=-2.919 tagged_above=-999 required=5 tests=[AWL=0.680,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bxmXFwz+I1cz; Sun, 28 Apr 2013 04:00:56 -0700 (PDT)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by ietfa.amsl.com (Postfix) with ESMTP id 1A05721F99D1; Sun, 28 Apr 2013 04:00:56 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id ld11so907744pab.5 for <multiple recipients>; Sun, 28 Apr 2013 04:00:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=OnnPLPlg9BaVVDpUADjrrbhByecxIa783FfGvbMr/xo=; b=ozJf8X2akEXuvuUazSWJtBzscQ1O7tGwSVelL/r102G2IMOvVyJxNuE8OrolqG+LVJ VJDcL0pXK8a1Nmbu2bsWLKcMmoyf1htCpM+3RTrUpDEQ38nTffbe61chV5kIcU+BQ61P kO8890kJwyDOCzltr/AsaeiGM64JWt7f7W2c0GgaqsJ+ZsZcjpneD+ciyEwvY5Zl5O1e 5UFAAmlRb0qbC2+b2rZZmd3ekptrkOd5f0KtbgmVdWmzgRfV63X7n+mbgqg+2A1vKbhh zBD9b9trsjxr1CkPcb5y6Crzr4J4BTq3Zb+e8net4WzUqTeu7GOmqfQN7mMZnyIhnFFl h6pA==
MIME-Version: 1.0
X-Received: by 10.66.74.170 with SMTP id u10mr3436175pav.202.1367146855809; Sun, 28 Apr 2013 04:00:55 -0700 (PDT)
Received: by 10.68.230.35 with HTTP; Sun, 28 Apr 2013 04:00:55 -0700 (PDT)
In-Reply-To: <20130427180421.D4337E6739@smtp.hushmail.com>
References: <20130427180421.D4337E6739@smtp.hushmail.com>
Date: Sun, 28 Apr 2013 13:00:55 +0200
Message-ID: <CADnDZ8_e+4AbVDQOuTJOK6tNGSC67hRzWSuSpvd+vkpyRJ4DLw@mail.gmail.com>
Subject: Re: Biggest Fake Conference in Computer Science
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: hammondjohnson@hushmail.com
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: ietf <ietf@ietf.org>, routing-discussion@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Apr 2013 11:00:57 -0000

Hi

Thanks for your input, and I comment on your post that it is always
important to listen to reviews, and try to understand reviewers (even
if they may be stupid, or have wrong comments), any world/community
editor or author should be careful to listen and understand to
comments, to make their work clarified, true and up to date. A
conference or document maybe noticed as a fake/humerous/joky only if
it gets reviewed by the world and commented on in public, in that way
the world can be aware. That is why I like the IETF that its documents
are Request For Comment (RFC), different from other world published
documents. If I am a chairman of a conference I will name its
publications RFC as well :)

I got once a reply on my review in an IETF WG that it was academic not
practical (I never distiguish them because I beleive they are
married), which I think we need all kinds of reviews, I like to
include comments as was this implemented or measured its performance
(by questioning authors). Reviewing any document in the world (which
will be published in the world) is not an easy task and also important
for authors to respect and acknowledge such review because it
increases reputation and saves them the worlds confusion after
publish.

I recommend all world WGs do more reviews and discussion on their
documents to get better reputation.

Regards
Abdussalam Baryun

On 4/27/13, hammondjohnson@hushmail.com <hammondjohnson@hushmail.com> wrote=
:
> We are researchers from different parts of the world and conducted a stud=
y
> on
> the world=92s biggest bogus computer science conference WORLDCOMP
> ( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arab=
nia
> from University of Georgia, USA.
>
>
> We submitted a fake paper to WORLDCOMP 2011 and again (the same paper
> with a modified title) to WORLDCOMP 2012. This paper had numerous
> fundamental mistakes. Sample statements from that paper include:
>
> (1). Binary logic is fuzzy logic and vice versa
> (2). Pascal developed fuzzy logic
> (3). Object oriented languages do not exhibit any polymorphism or
> inheritance
> (4). TCP and IP are synonyms and are part of OSI model
> (5). Distributed systems deal with only one computer
> (6). Laptop is an example for a super computer
> (7). Operating system is an example for computer hardware
>
>
> Also, our paper did not express any conceptual meaning.  However, it
> was accepted both the times without any modifications (and without
> any reviews) and we were invited to submit the final paper and a
> payment of $500+ fee to present the paper. We decided to use the
> fee for better purposes than making Prof. Hamid Arabnia (Chairman
> of WORLDCOMP) rich. After that, we received few reminders from
> WORLDCOMP to pay the fee but we never responded.
>
>
> We MUST say that you should look at the above website if you have any
> thoughts
> to submit a paper to WORLDCOMP.  DBLP and other indexing agencies have
> stopped
> indexing WORLDCOMP=92s proceedings since 2011 due to its fakeness. See
> http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of on=
e
> of the
> conferences of WORLDCOMP and notice that there is no listing after 2010. =
See
> Section 2 of
> http://sites.google.com/site/dumpconf for comments from well-known
> researchers
> about WORLDCOMP.
>
>
> The status of your WORLDCOMP papers can be changed from scientific
> to other (i.e., junk or non-technical) at any time. Better not to have a
> paper than
> having it in WORLDCOMP and spoil the resume and peace of mind forever!
>
>
> Our study revealed that WORLDCOMP is a money making business,
> using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing
> out a small chunk of that money (around 20 dollars per paper published
> in WORLDCOMP=92s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo=
)
> who publicizes WORLDCOMP and also defends it at various forums, using
> fake/anonymous names. The puppet uses fake names and defames other
> conferences
> to divert traffic to WORLDCOMP. He also makes anonymous phone calls and
> tries to
> threaten the critiques of WORLDCOMP (See Item 7 of Section 5 of above
> website).
> That is, the puppet does all his best to get a maximum number of papers
> published
> at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia=92s) poc=
kets.
>
>
> Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until
> 2012) has
> refused to provide the venue for WORLDCOMP=9213 because of the fears of t=
heir
> image
> being tarnished due to WORLDCOMP=92s fraudulent activities. That is why
> WORLDCOMP=9213
> is taking place at a different resort. WORLDCOMP will not be held after
> 2013.
>
>
> The draft paper submission deadline is over but still there are no commit=
tee
> members, no reviewers, and there is no conference Chairman. The only cont=
act
> details available on WORLDCOMP=92s website is just an email address!
>
> Let us make a direct request to Prof. Hamid arabnia: publish all reviews =
for
> all the papers (after blocking identifiable details) since 2000 conferenc=
e.
> Reveal
> the names and affiliations of all the reviewers (for each year) and how m=
any
> papers each reviewer had reviewed on average. We also request him to look=
 at
> the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp=
1
>
>
> Sorry for posting to multiple lists. Spreading the word is the only way t=
o
> stop
> this bogus conference. Please forward this message to other mailing lists
> and people.
>
>
> We are shocked with Prof. Hamid Arabnia and his puppet=92s activities
> http://worldcomp-fake-bogus.blogspot.com   Search Google using the
> keyword worldcomp fake for additional links.
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>

From adrian@olddog.co.uk  Sun Apr 28 04:22:15 2013
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 91CA221F99D2; Sun, 28 Apr 2013 04:22:15 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V4138AhzrO+F; Sun, 28 Apr 2013 04:22:14 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id CBDF421F9965; Sun, 28 Apr 2013 04:22:13 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3SBMA1K015263;  Sun, 28 Apr 2013 12:22:10 +0100
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 r3SBM8AN015247 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 28 Apr 2013 12:22:09 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Fred Baker \(fred\)'" <fred@cisco.com>, "'Yaron Sheffer'" <yaronf.ietf@gmail.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>	<E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com>	<517A44F2.9050009@gmail.com> <8C48B86A895913448548E6D15DA7553B8242FA@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B8242FA@xmb-rcd-x09.cisco.com>
Subject: RE: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt>	(Improving Awareness	of Running Code: the Implementation Status	Section) to Experimental RFC
Date: Sun, 28 Apr 2013 12:22:08 +0100
Message-ID: <014001ce4402$9fa4e3d0$deeeab70$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-index: AQI+/nXAKV+Un4kRrUVd9ZCgs2LIxwID6x0NAQwM5vIBJAljXpfoZmGQ
Cc: ietf@ietf.org, tools-discuss@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: Sun, 28 Apr 2013 11:22:15 -0000

Hi Fred,

I'm in complete agreement with you, but... :-)

Before investing in a common set of tools to archive implementation information,
I wanted to see whether there was *any* intention to make that information
available. 

Thus, this is a baby-step towards the end result that you and I wold like to
see. If, after our 18 month experiment, it turns out that no-one wants to record
implementation information, we will know where we stand (or sit). OTOH, if there
is good support for the idea, we can move to the next stage.

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Fred
> Baker (fred)
> Sent: 26 April 2013 17:08
> To: Yaron Sheffer
> Cc: <ietf@ietf.org>; tools-discuss@ietf.org Discussion
> Subject: Re: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt>
> (Improving Awareness of Running Code: the Implementation Status Section) to
> Experimental RFC
> 
> 
> On Apr 26, 2013, at 2:12 AM, Yaron Sheffer <yaronf.ietf@gmail.com>
>  wrote:
> 
> > - There should be long-term commitment to maintain the data. I think we
> simply don't have such processes in place, and personally I don't want to even
try
> to deal with this problem. I suspect that we'd have to eventually use paid
help if
> we are serious about keeping the information current, and I don't even think
it
> would be worth the cost.
> 
> Understood. That said, we already have working group wikis and errata. I don't
> want to trivialize the investment, but it seems like we have at least part of
the
> infrastructure already. I'm asking what will be the best for IETF discussion
and for
> maintenance of the information. I suspect it's something we can do if we
choose
> to.=


From adrian@olddog.co.uk  Sun Apr 28 04:22:15 2013
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 C7F8921F99D5; Sun, 28 Apr 2013 04:22:15 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0iwOUXYJYevL; Sun, 28 Apr 2013 04:22:14 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id CE5D221F99CB; Sun, 28 Apr 2013 04:22:13 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3SBM9IW015258;  Sun, 28 Apr 2013 12:22:09 +0100
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 r3SBM8AM015247 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 28 Apr 2013 12:22:09 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'John C Klensin'" <john-ietf@jck.com>, "'Fred Baker \(fred\)'" <fred@cisco.com>, "'Yaron Sheffer'" <yaronf.ietf@gmail.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com>	<E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com>	<517A44F2.9050009@gmail.com>	<8C48B86A895913448548E6D15DA7553B8242FA@xmb-rcd-x09.cisco.com> <0E1D18E70456E3EEE8A2BEC0@JcK-HP8200.jck.com>
In-Reply-To: <0E1D18E70456E3EEE8A2BEC0@JcK-HP8200.jck.com>
Subject: RE: [Tools-discuss] Last Call:	<draft-sheffer-running-code-04.txt>	(Improving Awareness	of	Running Code: the Implementation Status	Section) to Experimental RFC
Date: Sun, 28 Apr 2013 12:22:08 +0100
Message-ID: <013f01ce4402$9f5a9460$de0fbd20$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-index: AQI+/nXAKV+Un4kRrUVd9ZCgs2LIxwID6x0NAQwM5vIBJAljXgJx6SBNl9TYUZA=
Cc: ietf@ietf.org, tools-discuss@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: Sun, 28 Apr 2013 11:22:16 -0000

Hi John,

Seems consistent with what is in the I-D at the moment. See section 3.

Thus,  those who want to record the info in the I-D can do that, while those who
want to go straight to a wiki can do that (although we ask that the I-D has a
pointer to the wiki).

Cheers,
Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of John C
> Klensin
> Sent: 26 April 2013 17:51
> To: Fred Baker (fred); Yaron Sheffer
> Cc: <ietf@ietf.org>; tools-discuss@ietf.org Discussion
> Subject: Re: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt>
> (Improving Awareness of Running Code: the Implementation Status Section) to
> Experimental RFC
> 
> 
> 
> --On Friday, April 26, 2013 16:07 +0000 "Fred Baker (fred)"
> <fred@cisco.com> wrote:
> 
> >
> > On Apr 26, 2013, at 2:12 AM, Yaron Sheffer
> > <yaronf.ietf@gmail.com>  wrote:
> >
> >> - There should be long-term commitment to maintain the data.
> >> I think we simply don't have such processes in place, and
> >> personally I don't want to even try to deal with this
> >> problem. I suspect that we'd have to eventually use paid help
> >> if we are serious about keeping the information current, and
> >> I don't even think it would be worth the cost.
> >
> > Understood. That said, we already have working group wikis and
> > errata. I don't want to trivialize the investment, but it
> > seems like we have at least part of the infrastructure
> > already. I'm asking what will be the best for IETF discussion
> > and for maintenance of the information. I suspect it's
> > something we can do if we choose to.
> 
> Fred,
> 
> First, I agree with both the above and with your prior note
> agreeing with the general idea and suggesting something more
> "live" than a section of an I-D.  Second, while I certainly see
> the value, I would get nervous if we were to move significantly
> toward a long-term, IETF-supported, official statement or
> compendium of implementation status.  At least unless pursued
> with great caution [1], such a thing would raise some of the
> same issues that going into the conformance testing business
> does in terms of the perception of guarantees that a given
> implementation is somehow "IETF approved".
> 
> Perhaps the right model would be to keep this material in I-Ds
> (as the proposal suggests) to support the evolution and review
> of specification documents, then to move it to a wiki or
> equivalent that was clearly identified as unofficial and for the
> convenience of the community and that was "maintained by the
> IETF" only to the extent needed to minimize spam, libel, and
> other nonsense.
> 
> It also occurs to me that an alternative to part of the
> experiment (still consistent with it, IMO) would be to start the
> wiki process earlier and use the I-Ds merely to snapshot the
> wiki at various points to help in the review process.  That
> would give both the advantages of a continually-evolving list
> and those of periodic stable snapshots.
> 
> Just a thought or two.
> 
>    john
> 
> 
> 
> [1] Images of dragging along as small pack of lawyers,
> albatross-like, are probably in order.


From adrian@olddog.co.uk  Sun Apr 28 04:43:46 2013
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 2B36421F8B98; Sun, 28 Apr 2013 04:43:46 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hGkTGTr59d8o; Sun, 28 Apr 2013 04:43:45 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6F621F8A48; Sun, 28 Apr 2013 04:43:44 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r3SBheHO006004;  Sun, 28 Apr 2013 12:43:41 +0100
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 r3SBhcbt005998 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 28 Apr 2013 12:43:39 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>, <ietf@ietf.org>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <CADnDZ892J5dpGHJyZioHagtwvoj--6pg-v61_n6au5OqPDVYfg@mail.gmail.com>
In-Reply-To: <CADnDZ892J5dpGHJyZioHagtwvoj--6pg-v61_n6au5OqPDVYfg@mail.gmail.com>
Subject: RE: Last Call: <draft-sheffer-running-code-04.txt> (Improving	Awareness of Running Code: the Implementation Status Section) to	Experimental RFC
Date: Sun, 28 Apr 2013 12:43:38 +0100
Message-ID: <014201ce4405$a0741350$e15c39f0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-index: AQI+/nXAKV+Un4kRrUVd9ZCgs2LIxwJ6WIKal/Y3obA=
Cc: iesg@ietf.org, draft-sheffer-running-code@tools.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: Sun, 28 Apr 2013 11:43:46 -0000

Hi AB,

Thanks for your review.

> IMHO, we should not request to delete this proposed
> section, but it can be shifted to the Appendix section when published.
> Removing the section is like doing some work in IETF and then
> destroying it, future reviewers/implementers may not know why it was
> accepted to publish or be implemented. If I read a document from the
> past/present I would like to know its usefulness to increase my
> acceptance.

There are two points related to this.
The first is that the intent of the information is to enable the
WG/community/IESG make a better assessment of the maturity and stability of the
specification while advancing it through WG last call to RFC publication. Thus,
once publication has been agreed, the information has served its purpose and can
be dropped.
The second point is that the information is likely to become obsolete very
quickly. So, while there *is* marginal value in retaining the information that
was true at the time of publication of an RFC, it is unclear that it provides
great value. If the authors/WG consider that a living record of implementation
of RFCs is valuable, if would be better to move this to a wiki. That, however,
is beyond the scope of our I-D.

> I-D Introduction>
> Some of them may never get implemented.
> 
> AB>amend>
> Some of them may never get implemented or used.
> 
> We implement a specification for a use case or to be used within
> another specification, some specification may have available to use
> another but never does use the other (was that a waste of running
> code, or may that be used by an attacking specification).

I take your point, although I think it is rare for people to implement code
without intending to execute it.

> I-D Section 2>
> 
> AB> I will add points:
> o   the date of implementation.
> o   the reason for implementation, or use-case targets.

Would be useful information if people are willing to state it.

> AB>Quest> Why before security consideration? I recommend it to be
> after all sections, because implementors consider that security
> section within their work and may refer to it.

Funny!
Got to put the section somewhere.
My preference is for it to be in the same place in all documents.
Have had several responses suggesting different places to put the section.
I can't get excited about where it should go. Yaron and I will discuss moving
it.

> Section 3>
> AB> Add> the WG may replace it into a historical document that can be
> refered to by the current concerned WG document,

Do you mean a historical RFC?
I suppose this option is open to the WG if they want to go that way. for the
reasons stated above, I would think that a poor idea.

> Section 5.1>
> 18 Months
> 
> AB> The duration is not understood if it is maximum or minimum
> requirement. Please provide the requirement language to be clear. (I
> don't know from where the 18 came from, I like to specifying *three
> IETF WG meeting* presentations/discussions of such implementations. If
> you don't present/discuss the implementation inside IETF then how do
> we document such work/activity?

This is the period during which the authors will conduct the experiment.
At the end of this period the authors will report to the community.

Why 18 months? Because that is what we think feels right given how long it takes
to advance I-Ds.

Should implementation status be presented at IETF meetings? That is entirely up
to the WGs and the individuals involved. I am entirely uninterested in sitting
through marketing presentations at IETF meetings. I have no objection to seeing
a slide that reports on the current implementations status per the latest
revision of an I-D - but I can't understand why people wouldn't just read the
I-D to find out this information.

> AB>Comment> in one WG it was said that some companies don't want to
> discuss their implementations or results. Is it strange to *use* the
> IETF specification and not report back to it for future progress of
> such document?

Such is the world of business.

Adrian


From ron.even.tlv@gmail.com  Sun Apr 28 05:31:51 2013
Return-Path: <ron.even.tlv@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 26D2321F9917; Sun, 28 Apr 2013 05:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A4+UUSiIAT7H; Sun, 28 Apr 2013 05:31:50 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 4B4E621F98DA; Sun, 28 Apr 2013 05:31:41 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id s47so3953144wey.22 for <multiple recipients>; Sun, 28 Apr 2013 05:31:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received: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=AvGl41968ax6N4oGf0iGDisRbb+k9EtUYssccTvI+Bk=; b=J+by7LoRUsrgMAFzxA+mGAJ86KCPqQUsBCFqO1rFKjub3D6qJCHwAwTq7E5O9wMe8N stWHRVJKScTM8a4dUkYLIcTZT6jne0dDKdeNo3owl3SEDWbbbVK/ImWp5gmwuInPZ4Ph 6woQw7/5h+wSk0bbRFUUT0CKamcT9u8+v3zstSolEUQKPg10h9yHojm2n6Lrp7Z3CFCt SNfVYHyOczAqIHcTRm5++5eBJpdStPOVhq3VX4QPnQGp5cf5gwKRKVVcTcMoqGifPM+X U0v9xgfe4ArIsHVIztbm1yhKh8kHxC/xIHA8ntp4o/A4A0y7pnJkUeVT8YxsQxZSPvjt 6h2w==
X-Received: by 10.194.62.233 with SMTP id b9mr31042601wjs.37.1367152300381; Sun, 28 Apr 2013 05:31:40 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPSA id e8sm8398599wic.5.2013.04.28.05.31.37 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 28 Apr 2013 05:31:39 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Martin Bjorklund'" <mbj@tail-f.com>
References: <019901ce43ea$bbd575a0$338060e0$@gmail.com> <20130428.115010.513224826.mbj@tail-f.com>
In-Reply-To: <20130428.115010.513224826.mbj@tail-f.com>
Subject: RE: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
Date: Sun, 28 Apr 2013 15:31:01 +0300
Message-ID: <01ba01ce440c$408d4720$c1a7d560$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFWiDTvx1wg5jy+XbNDGWkbCL4PFgG0N6f1mc1j5KA=
Content-Language: en-us
Cc: gen-art@ietf.org, draft-ietf-netmod-interfaces-cfg.all@tools.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: Sun, 28 Apr 2013 12:31:51 -0000

Martin,
Thanks for the response. I am OK with your responses to the nits.

As for the comment on location I think I understand but what got me thinking
was the examples.
In E.1 

"An operator can configure a new interface by sending an <edit-config>
   containing:

     <interface nc:operation="create">
       <name>fastethernet-1/0</name>
     </interface>

   When the server processes this request, it will set the leaf "type"
   to "ethernetCsmacd" and "location" to "1/0".  Thus, if the client
   performs a <get-config> right after the <edit-config> above, it will
   get:

     <interface>
       <name>fastethernet-1/0</name>
       <type>ethernetCsmacd</type>
       <location>1/0</location>
     </interface>"

I can see how the linkage between the location and name is done. I am not
sure how the operator knows from the response what is the physical location
without knowing the device type and manufacturer but at least the linkage is
there and this is why I thought of it more as a logical device and not
physical one.

When looking at E2.2 example
  " An operator can configure a new interface by sending an <edit-config>
   containing:

     <interface nc:operation="create">
       <name>acme-interface</name>
       <type>ethernetCsmacd</type>
       <location>1/0</location>
     </interface>"

Here the operator need to know the device to configure a specific interface
and know how many interface exist and how they are named. So you assume that
for this case this is known to the configuration.

Roni




-----Original Message-----
From: Martin Bjorklund [mailto:mbj@tail-f.com] 
Sent: 28 April, 2013 12:50 PM
To: ron.even.tlv@gmail.com
Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org; ietf@ietf.org;
gen-art@ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10

Hi,

Thank you for your review.  Comments inline.

"Roni Even" <ron.even.tlv@gmail.com> wrote:
> 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-netmod-interfaces-cfg-10
> 
> Reviewer: Roni Even
> 
> Review Date:2013-4-28
> 
> IETF LC End Date: 2013-5-3
> 
> IESG Telechat date: 2013-5-16
> 
>  
> 
> Summary: This draft is almost ready for publication as Standard track RFC.
> 
>  
> 
>  
> 
> Major issues:
> 
>  
> 
> Minor issues:
> 
>  
> 
> 1.       I had some problem understanding the "location" leaf. Section 3.2
> has it as a string and says that "The device uses the location string 
> to identify the physical or logical entity that the configuration applies
to".
> I am not sure how you identify physical location having no definition 
> of the mapping.

The sentence just before the quoted one above says:

  "The format of this string is device- and type-dependent."

and then the text says:

  "How a client can learn which types and locations are present on a
  certain device is outside the scope of this document."

So the exact procedure is currently left to the vendors, but may be
standardized in a future document (if possible...)

> I saw the examples in Appendix E and it looked more to me as logical 
> mapping but not physical since it attaches a name to something in the 
> device but I am not clear how you know what it is physically in the 
> device. If the name 0-n or n/m are real physical entities, I think 
> that it should be specified some place.
> 
>  
> 
>  
> 
> Nits/editorial comments:
> 
> 1.	In the introduction section maybe add to the first sentence a
> reference to RFC6244 with some text.

Ok, this probably makes sense.  I will check w/ the WG and other documents.



> 2.	In section 2 are the" must" and "should"  used as described in
> RFC2119, if yes need capital letters

Seciton 2 is more of a background, non-normative section.  It lists some of
the design objectives.

> 3.	In section 3.1 "It is optional in the data model,  but if the type
> represents a physical interface, it is mandatory", suggest having 
> RFC2119 language "It is OPTIONAL in the data model,  but if the type 
> represents a physical interface, it is MUST be specified"

I think the first one should not be OPTIONAL, but the second one is correct.
So I suggest this:

  It is defined as being optional in the data model, but if the type
  represents a physical interface, it MUST be specified.


/martin


From john-ietf@jck.com  Sun Apr 28 07:35:56 2013
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 9865E21F99BB; Sun, 28 Apr 2013 07:35:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fMeVmnaWdrHS; Sun, 28 Apr 2013 07:35:56 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA7921F99B3; Sun, 28 Apr 2013 07:35:55 -0700 (PDT)
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 1UWShk-000Ofn-RF; Sun, 28 Apr 2013 10:35:52 -0400
Date: Sun, 28 Apr 2013 10:35:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk, "'Fred Baker (fred)'" <fred@cisco.com>, 'Yaron Sheffer' <yaronf.ietf@gmail.com>
Subject: RE: [Tools-discuss] Last Call:	<draft-sheffer-running-code-04.txt>	(Improving Awareness	of	Running Code: the Implementation Status	Section) to Experimental RFC
Message-ID: <08093B669F43658F8972DD91@JcK-HP8200.jck.com>
In-Reply-To: <013f01ce4402$9f5a9460$de0fbd20$@olddog.co.uk>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <E4356150-81CF-4CAB-A1E4-E7983ACD2083@cisco.com> <517A44F2.9050009@gmail.com> <8C48B86A895913448548E6D15DA7553B8242FA@xmb-rcd-x09.cisco.com> <0E1D18E70456E3EEE8A2BEC0@JcK-HP8200.jck.com> <013f01ce4402$9f5a9460$de0fbd20$@olddog.co.uk>
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, tools-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Apr 2013 14:35:56 -0000

--On Sunday, April 28, 2013 12:22 +0100 Adrian Farrel
<adrian@olddog.co.uk> wrote:

> Hi John,
> 
> Seems consistent with what is in the I-D at the moment. See
> section 3.
> 
> Thus,  those who want to record the info in the I-D can do
> that, while those who want to go straight to a wiki can do
> that (although we ask that the I-D has a pointer to the wiki).

Indeed.  I was trying to make that point in a different way.  To
be more explicit, I think the I-D is fine, precisely because it
allows some reasonable flexibility about that sort of option.
I'd encourage the experimental evaluation process to compare
those two options in practice (e.g., by including statistics
about which method is used in the Summary Report (Section 5.2)
and commenting on relative utility if there is anything to say).
But there is nothing in the I-D that would prevent that and I'm
not convinced that more specifics in this I-D would be worth the
trouble.

   john


From yaronf.ietf@gmail.com  Sun Apr 28 08:04:02 2013
Return-Path: <yaronf.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 8D16521F9387; Sun, 28 Apr 2013 08:04:02 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hF7W89Hw94ff; Sun, 28 Apr 2013 08:04:01 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 134E021F9851; Sun, 28 Apr 2013 08:03:59 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id f11so3006302wgh.3 for <multiple recipients>; Sun, 28 Apr 2013 08:03:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=f4sA2JhBGbEEibjVVubCwY2GcoDTiVsr9qkzMabMZig=; b=diIqM1UFdO1w3fqJOMljMjnuQYVnqIk2jgX57sjNQnQOD2aZYhg0g/0ZKtvWcpRIur OY+l8dRpscnk18sQTjUHJPdBi/r20H49nGObAnugVYqWa44kq8Re/x5Ly0zbeCUU6+0t 5c3nREDeNnhNBAdU8r3AwJezRVukjv0hvJVAJPw837ZrSlkhvNP9dAl0pUv2mXPag2HY fobXwBkih1WU8ht5nQ0GnJiywj1ZdFLy1MWW/D8igaMIVM11KN0/PHdxvOpdm9EQuKQ7 BlSxWLPfXE+A1gGgkGqV6Mh010f+9vHO1OVZ1g8eiHutnvEdHVRXBCWBUOf6B5pMkSm2 68yA==
X-Received: by 10.194.108.165 with SMTP id hl5mr41127617wjb.22.1367161439261;  Sun, 28 Apr 2013 08:03:59 -0700 (PDT)
Received: from [10.0.0.23] (bzq-79-177-180-167.red.bezeqint.net. [79.177.180.167]) by mx.google.com with ESMTPSA id q20sm16284450wiv.7.2013.04.28.08.03.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Apr 2013 08:03:58 -0700 (PDT)
Message-ID: <517D3A5C.4070009@gmail.com>
Date: Sun, 28 Apr 2013 18:03:56 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Dave Crocker <dhc@dcrocker.net>
Subject: Re: Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness of Running Code: the Implementation Status Section) to Experimental RFC
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <CAC4RtVABudiEa_cqqr9OmcbUsAuWGXftisrjEATRLgNvJubXzw@mail.gmail.com> <517AA859.9060804@dcrocker.net>
In-Reply-To: <517AA859.9060804@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-sheffer-running-code@tools.ietf.org, "ietf@ietf.org" <ietf@ietf.org>, Tools Team Discussion <tools-discuss@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: Sun, 28 Apr 2013 15:04:02 -0000

Hi Dave,

Thank you for your thorough review. While I accept many of your
comments, I must say I disagree with you on a few points, which together
go to the core of our motivation in writing this document. Thank you for
helping me clarify these points to myself :-)

- Our goal is much *less* ambitious than defining a framework for
documenting implementations for long-term protocol projects. Our primary
goal is to aid working group members in making informed decisions about
the quality of specifications. I believe this narrow focus is much more
realistic.

- As a result of the above: 1. We define the information as pre-RFC
only; 2. The main medium is the I-D, as opposed to Web pages/wikis/CMS
(although we see them as valid alternatives); 3. We focus on WG
documents, as opposed to "all" IETF documents.

- Despite the glowing counterexample of DKIM, it is rarely practical to
maintain implementation status information, keeping it current for years 
(put bluntly, you need to pay someone to do that). The IETF certainly 
does not have the processes or mechanisms to do so. And we do not try to 
establish such processes here.

Please see my detailed comments below.

Thanks,
	Yaron

On 2013-04-26 19:16, Dave Crocker wrote:
> Given this thread on the ietf list, I guess I should forward the
> following, which was done as a solicited Apps Area review for this draft:
>
>
> -------- Original Message --------
> Subject: Review of:  draft-sheffer-running-code
> Date: Wed, 24 Apr 2013 06:38:24 -0700
> From: Dave Crocker <dcrocker@gmail.com>
> To: draft-sheffer-running-code.all@tools.ietf.org,
> apps-discuss@ietf.org,  iesg@ietf.org
>
> Howdy.
>
> I have been selected as the Applications Area Review Team reviewer for
> this draft (for background on apps-review, please see
> http://www.apps.ietf.org/content/applications-area-review-team).
>
> Please resolve these comments along with any other Last Call comments
> you may receive. Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
>
> Review
> ------
>
>
> Title:    Improving Awareness of Running Code: the Implementation Status
> Section
>
> I-D:      draft-sheffer-running-code-04
>
> Reviewer:     D. Crocker
> Review Date:  24 April 2013
>
>
> Summary:
>
> Given an organizational motto of "Rough consensus and running code",
> implementation experience has a value built into the IETF's DNA.
> However formal IETF reliance on running code for specifications has been
> minimal, with its only universal occurrence being in consideration of
> advanced standards status; it is notably /not/ an organizational
> requirement for entry-level Proposed Standard status, if only for the
> very high barrier to publication this imposes on document versions that
> were intended to be preliminary.  The current draft proposes an
> experiment to optionally include documentation of implementations as
> part of document development, prior to issuance of a specification as an
> RFC.
>
> Within the broader perspective of pre- and post-standardization efforts,
> it is quite common to document available implementations of a
> specification.  (As a convenient example, see http://dkim.org/deploy.)
> In effect, the current proposal merely seeks to have a common IETF-based
> means of recording a type of information that industry has already
> frequently formulated.
>
> In their current form, the draft and the proposal seem likely to be
> useful.  However, both could be improved.
>
> The draft includes some language and assertions that would benefit from
> being a bit more carefully written; questions, comments and suggestions
> are in the detailed comments below.
>
> The proposal itself would benefit from directly paying more attention to
> existing industry practice, which is implied by the "alternatives"
> section; that is, that implementation lists already happen and are
> maintained after IETF document processing. The proposal should do a
> better job of integrating this fact into its design.
>
> One approach could be a relatively simple document change, to
> distinguish between specifying the information to be reported, as
> distinct from the means of reporting it -- think of it as payload vs.
> mechanism...  Specify them separately.  Then define both how to
> incorporate the information directly and the form of an external
> citation to it; this would eliminate the document's section on
> 'alternatives' and treat the original and alternative methods as equal.
>
> d/
>
>
>
>
>
> Detailed Comments:
>
>> 1.  Introduction
>>
>> Most IETF participants are familiar with the saying, "rough
>> consensus and running code" [Tao], and can identify with its
>> pragmatic approach.  However, there are many examples of
>> Internet-Drafts containing protocol specification that have gone
>> through to publication as Proposed Standard RFCs without
>> implementation.  Some of them may never get implemented.
>
> The "however" implies that it is wrong or problematic for Proposed to be
> assigned to unimplemented protocols.  It isn't.  I suggest a softer
> tone, while still noting the relevantfact. Something like:
>
>       It is not a requirement of Proposed Standard status to have any
> implementations; by the time of reaching that status, some
> specifications have been implemented and some have not. Indeed, some
> never get implemented.
>
>
>> Over time, a variety of policies have been implemented within the
>
> implemented -> applied
>
>
>> IETF to consider running code.  In the Routing Area it used to be a
>> requirement that one or more implementations must exist before an
>> Internet-Draft could be published as a Proposed Standard RFC
>> [RFC1264].  That RFC was later obsoleted and the requirement for
>> implementation was lifted, but each working group was given the
>> authority to impose its own implementation requirements [RFC4794]
>> and at least one working group (IDR) continues to require two
>> independent implementations.
>>
>> The hypothesis behind this document is that there are benefits to
>> the
>
> this -> the current
>
>
>> IETF standardization process of producing implementations of
>> protocol specifications before publication as RFCs.  These benefits,
>> which
>
> I suspect that that isn't its "hypothesis" at all, since the document
> does nothing to specify or directly affect policies for requiring or
> encouraging implementation.  Perhaps there is a hope that the proposed
> notation about implementations will serve as some sort of encouragement,
> but that's pretty indirect; success or failure of the proposed
> experiment won't validate or invalidate whether there are benefits to
> early implementation.  And providing for a notation convention hardly
> constitutes an 'incentive'.
>
> Rather, I believe the premise of the document is that the community is
> aided by /more widely knowing about/ early implementations.

This is splitting hairs: there would be no benefit in informing the 
community if there wasn't any benefit in the actual early 
implementations. But fine.

>
>
>> include determining that the specification is comprehensible and
>> that there is sufficient interest to implement, are further discussed
>> in Section 4.
>>
>> This document describes a simple process that allows authors of
>
> process -> mechanism
>
>
>> Internet-Drafts to record the status of known implementations, by
>> including an Implementation Status section.  The document defines
>> (quite informally) the contents of this section, to ensure that the
>> relevant information is included.  This will allow reviewers and
>> working groups to assign due consideration to documents that have
>> the benefit of running code, by considering the running code as
>> evidence of valuable experimentation and feedback that has made the
>> implemented protocols more mature.
>
> The above last sentence seems to be the actual claimed value proposition
> for the experiment.
>

I agree.

>
>> This document provides a mechanism to record and publicize the
>
> This sentence seems entirely redundant.
>
>
>> existence of running code.  It is up to the individual working
>> groups to use this information as they see fit, but one result might
>> be the preferential treatment of documents resulting in them being
>> processed more rapidly.
>
> I think it won't be the working group that 'uses' the information, but
> rather IETF management and the broader community?
>

For most documents, AFAIK, most work is done by the WG, and a lot less 
by the rest of the community. Hence the above.

>
>> The process in this document is offered as an experiment.  Authors
>> of Internet-Drafts are encouraged to consider using the process for
>> their documents, and working groups are invited to think about
>> applying the process to all of their protocol specifications.
>>
>> The scope of the intended experiment is all Internet-Drafts whether
>
> Probably not all I-Ds, since they do not all contain implementable
> specifications.
>
>
>>
>>
>> Sheffer & Farrel        Expires October 14, 2013                [Page
>> 3]  Internet-Draft                Running Code
>> April 2013
>>
>>
>> produced within IETF working groups, outside working groups but
>
> What I-Ds are produced by "outside working groups"?  I can't tell who
> this refers to.It's probably just as well to remove the attempted case
> analysis for groups and just say that the scope is all specifications
> issued as I-Ds.

In fact others have commented that we should exclude individual 
submissions for process reasons.

>
>
>> intended for IETF consensus, or for publication on the Independent
>> Stream.  However, it is expected that most benefit from the
>
> that most benefit from the experiment will
> ->
> the greatest benefit in the experiment will
>
>
>> experiment will be seen with Standards Track documents developed
>> within working groups.
>
> Here's my guess:
>
> 1. Those offering comments or making decisions about the status of
> document will be aided by this added information.
>
> 2. Those deciding about whether to write code or deploy it will be aided.
>
> I think the latter is likely to be the greater benefit.
>
>
>> The authors of this document intend to collate experiences with this
>> experiment and to report them to the community.
>>
>>
>> 2.  The "Implementation Status" Section
>>
>> Each Internet-Draft may contain a section entitled "Implementation
>> Status".  This section, if it appears, should be located just before
>> the "Security Considerations" section and contain, for each existing
>> implementation:
>>
>> o  The implementation's name and/or a link to a web page describing
>> the implementation. o  A brief general description. o  The
>> implementation's level of maturity: research, prototype, alpha, beta,
>> production, widely used etc. o  Coverage: which parts of the protocol
>> specification are implemented and which versions of the
>> Internet-Draft were implemented. o  Licensing: the terms under which
>> the implementation can be used. For example: proprietary, royalty
>> licensing, freely distributable with acknowledgement (BSD style),
>> freely distributable with requirement to redistribute source (GPL
>> style), other (specify). o  Contact information: ideally a person's
>> name and email address, but possibly just a URL or mailing list.
>
> List the organization that did the implementation and contact
> information for the proper place in the organization.
>
>
>> In addition, this section can contain information about the
>> interoperability of any or all of the implementations.
>>
>> Since this information is necessarily time-dependent, it is
>> inappropriate for inclusion in a published RFC.  The authors should
>
> Way to bury the lead.  This stuff won't be in the published document?
> It's only for pre-publication?

Very clearly YES.

>
>
>> include a note to the RFC Editor requesting that the section be
>> removed before publication.
>>
>> 2.1.  Introductory Text
>>
>> The following boilerplate text is proposed to head the
>> Implementation Status section:
>>
>>
>>
>>
>>
>>
>>
>> Sheffer & Farrel        Expires October 14, 2013                [Page
>> 4]  Internet-Draft                Running Code
>> April 2013
>>
>>
>> This section records the status of known implementations of the
>> protocol defined by this specification at the time of posting of this
>> Internet-Draft, and is based on a proposal described in [RFC Editor:
>> replace by a reference to this document].  According to [RFC Editor:
>> replace by a reference to this document], "this will allow reviewers
>> and working groups to assign due consideration to documents that have
>> the benefit of running code, by considering the running code as
>> evidence of valuable experimentation and feedback that has made the
>> implemented protocols more mature.  It is up to the individual
>> working groups to use this information as they see fit".
>>
>> Authors are requested to add a note to the RFC Editor at the top of
>> this section, advising the Editor to remove the entire section
>> before publication, as well as the reference to [RFC Editor: replace
>> by a reference to this document].
>>
>>
>> 3.  Alternative Formats
>
> Yes!
>
>
>> Sometimes it can be advantageous to publish the implementation
>> status separately from the base Internet-Draft, e.g. on the IETF
>> wiki:
>>
>> o  When the Implementation Status section becomes too large to be
>> conveniently managed within the document. o  When a working group
>> decides to have implementors, rather than authors, keep the status of
>> their implementations current. o  When a working group already
>> maintains an active wiki and prefers to use it for this purpose.
>>
>> It is highly desirable for all readers of the Internet-Draft to be
>> made aware of this information.  Initially this can be done by
>> replacing the Implementation Status section's contents with a URL
>> pointing to the wiki.  Later, the IETF Tools may support this
>> functionality, e.g. by including such a link from the HTMLized draft
>> version, similar to the IPR link.
>>
>> If the implementation status is published separately from the I-D,
>> then this information needs to be openly available without requiring
>> authentication, registration or access controls if it is to have any
>> useful effects.
>>
>>
>> 4.  Benefits
>>
>> Publishing the information about implementations provides the
>> working group with several benefits:
>>
>>
>>
>>
>> Sheffer & Farrel        Expires October 14, 2013                [Page
>> 5]  Internet-Draft                Running Code
>> April 2013
>>
>>
>> o  Participants are motivated to implement protocol proposals, which
>> helps in discovering protocol flaws at an early stage.
>
> The psychological premise seems to be that getting cited in this list
> will somehow serve as an incentive to implementers. I can imagine that
> they'll like being listed, but find it extremely difficult to believe
> that it will affect whether they do the work; not that I think it's a
> deciding factor, but note that the ego value is further reduced by the
> information's being ephemeral, since it it removed prior to RFC
> publication!

Actually not (subtly so). The premise is making this information public 
and an explicit part of WG deliberations will incentivize 
implementations (i.e. not the ego factor at all).

>
>
>> o  Other participants can use the software, to evaluate the
>> usefulness of protocol features, its correctness (to some degree) and
>> other properties, such as resilience and scalability.
>
> Efficacy of the spec.
>
>
>> o  WG members may choose to perform interoperability testing with
>> known implementations, especially when they are publicly available.
>
> Interoperability of the spec.
>
>
>> o  In the case of open source, people may want to study the code to
>> better understand the protocol and its limitations, determine if the
>> implementation matches the protocol specification, and whether the
>> protocol specification has omissions or ambiguities.
>
> Reference implementation as exemplar.
>
>
>> o  Working group chairs and ADs may use the information provided to
>> help prioritize the progress of I-Ds in some way.
>
> What does "prioritize the progress" mean?

When there are multiple competing proposals to solve some problem.

>
>
>> o  Similarly, the information is useful when deciding whether the
>> document should be progressed on a different track (individual
>> submission, Experimental etc.).
> Assess spec maturity.  (This seems redundant with the combination of
> Efficacy and Interoperability?)
>
>
>> o  And lastly, some protocol features may be hard to understand, and
>> for such features, the mere assurance that they can be implemented is
>> beneficial.
>
> mumble.  Might highlight problems with the spec language. Might
> undermine the spec text by causing code to be used in place of it?

I'm with you on both mumbles.

>
>
>> We do not specify here whether and to what degree working groups are
>> expected to prefer proposals that have "running code" associated
>> with them, over others that do not.
>>
>>
>> 5.  Process Experiment
>>
>> The current proposal is proposed as an experiment.  The inclusion of
>> "Implementation Status" sections in Internet-Drafts is not
>> mandatory, but the authors of this document wish to encourage authors
>> of other Internet-Drafts to try out this simple process to discover
>> whether it is useful.  Working group chairs are invited to suggest
>> this process to document editors in their working groups, and to draw
>> the attention of their working group participants to "Implementation
>> Status" sections where they exist.
>>
>> Following a community discussion, it was concluded that [RFC3933] is
>> not an appropriate framework for this experiment, primarily because
>> no change is required to any existing process.
>
> It defines a document meta-data encoding mechanism. That's not really a
> "process".
>
>
>> 7.  Security Considerations
>>
>> This is a process document and therefore, it does not have a direct
>> effect on the security of any particular IETF protocol.  Better
>
> Better -> However, better
>
>
> d/
>

From dhc@dcrocker.net  Sun Apr 28 15:06:19 2013
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 B3EAD21F984E; Sun, 28 Apr 2013 15:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbkP8V4qFq6t; Sun, 28 Apr 2013 15:06:18 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C0C4621F9832; Sun, 28 Apr 2013 15:06:18 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3SM69Zt004595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 28 Apr 2013 15:06:15 -0700
Message-ID: <517D9D50.9010408@dcrocker.net>
Date: Sun, 28 Apr 2013 15:06:08 -0700
From: Dave Crocker <dhc@dcrocker.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness of Running Code: the Implementation Status Section) to Experimental RFC
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <CAC4RtVABudiEa_cqqr9OmcbUsAuWGXftisrjEATRLgNvJubXzw@mail.gmail.com> <517AA859.9060804@dcrocker.net> <517D3A5C.4070009@gmail.com>
In-Reply-To: <517D3A5C.4070009@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.66]); Sun, 28 Apr 2013 15:06:17 -0700 (PDT)
Cc: IESG <iesg@ietf.org>, draft-sheffer-running-code@tools.ietf.org, Tools Team Discussion <tools-discuss@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: Sun, 28 Apr 2013 22:06:19 -0000

On 4/28/2013 8:03 AM, Yaron Sheffer wrote:
> Hi Dave,
>
> Thank you for your thorough review. While I accept many of your
> comments, I must say I disagree with you on a few points, which together
> go to the core of our motivation in writing this document. Thank you for
> helping me clarify these points to myself :-)
>
> - Our goal is much *less* ambitious than defining a framework for
> documenting implementations for long-term protocol projects. Our primary
> goal is to aid working group members in making informed decisions about
> the quality of specifications.

Forgive me, but working group members seem like the /least/ interesting 
target audience, since it is already the most-informed group, by virtue 
of its direct activity over the course of developing the specification.

The people who are most likely to benefit from pointers to 
implementation details are:

    1.  Reviewers, who want a sense of implementation history to 
'season' their analysis;

    2.  IESG members, who are deciding whether to vote approval for the 
specification; and

    3.  Those considering adoption of the technology for use, such as 
other implementers and service operators.

That said, what you propose certainly accommodates #1 and #2, without 
needing to agree on their being a target audience...

[However the small discussion, farther down, about being better able to 
evaluate competing proposals, does provide an example of benefit 
/within/ the working group...]



> - As a result of the above: 1. We define the information as pre-RFC
> only; 2. The main medium is the I-D, as opposed to Web pages/wikis/CMS
> (although we see them as valid alternatives); 3. We focus on WG
> documents, as opposed to "all" IETF documents.

Right.  And here my suggestions were merely to clarify this earlier in 
the proposal document.


> - Despite the glowing counterexample of DKIM, it is rarely practical to
> maintain implementation status information, keeping it current for years
> (put bluntly, you need to pay someone to do that).

Would that I'd been getting paid...  But yeah,it  takes continuing 
effort.  (On the other hand, there isn't much on-going work, after 
initial bursts of development activity.)

At any rate, rather than insisting that the list be external and 
on-going, my intention was to suggest designing it to comfortably 
/allow/ the wg to make the choice of either, gracefully, including an 
easy transition from one to the other.

  - - - - -

>>> existence of running code.  It is up to the individual working
>>> groups to use this information as they see fit, but one result might
>>> be the preferential treatment of documents resulting in them being
>>> processed more rapidly.
>>
>> I think it won't be the working group that 'uses' the information, but
>> rather IETF management and the broader community?
>>
>
> For most documents, AFAIK, most work is done by the WG, and a lot less
> by the rest of the community. Hence the above.

IETF Working groups do not create market demand and do not do develop or 
deployment.  All of that is quite explicitly outside the scope of the 
IETF, and at industry-scale, they represent more aggregate effort than 
is put in by the IETF working group...



>>> The scope of the intended experiment is all Internet-Drafts whether
>>
>> Probably not all I-Ds, since they do not all contain implementable
>> specifications.
>>
>>
>>>
>>>
>>> Sheffer & Farrel        Expires October 14, 2013                [Page
>>> 3]  Internet-Draft                Running Code
>>> April 2013
>>>
>>>
>>> produced within IETF working groups, outside working groups but
>>
>> What I-Ds are produced by "outside working groups"?  I can't tell who
>> this refers to.It's probably just as well to remove the attempted case
>> analysis for groups and just say that the scope is all specifications
>> issued as I-Ds.
>
> In fact others have commented that we should exclude individual
> submissions for process reasons.

Right.  That suggests writing the scoping text a bit more tightly.


>>> o  Participants are motivated to implement protocol proposals, which
>>> helps in discovering protocol flaws at an early stage.
>>
>> The psychological premise seems to be that getting cited in this list
>> will somehow serve as an incentive to implementers. I can imagine that
>> they'll like being listed, but find it extremely difficult to believe
>> that it will affect whether they do the work; not that I think it's a
>> deciding factor, but note that the ego value is further reduced by the
>> information's being ephemeral, since it it removed prior to RFC
>> publication!
>
> Actually not (subtly so). The premise is making this information public
> and an explicit part of WG deliberations will incentivize
> implementations (i.e. not the ego factor at all).

The statements you are making about "incentives" to implementers really 
are in terms of their ego, since you have not stated any other benefit 
that will accrue to /them/.  There will be benefits to the community at 
large, but the question in this section of text is what the motivation 
of the implementer will be.



>>> o  Working group chairs and ADs may use the information provided to
>>> help prioritize the progress of I-Ds in some way.
>>
>> What does "prioritize the progress" mean?
>
> When there are multiple competing proposals to solve some problem.

I think you are trying to say something like:

    By having early implementation examples for competing proposals, the 
working group can better evaluate choices among them.



d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From margaretw42@gmail.com  Sun Apr 28 17:53:07 2013
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 ABCC921F9603 for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 17:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XdoCzs3bUWoN for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 17:53:07 -0700 (PDT)
Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9CB21F93EC for <ietf@ietf.org>; Sun, 28 Apr 2013 17:53:06 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id b25so2915972qca.17 for <ietf@ietf.org>; Sun, 28 Apr 2013 17:53:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:subject:mime-version:content-type:from:x-priority :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=8jaMD4TDER7uLBR9eRikL9lQRV0eKKEWuSqCOMIFuzw=; b=nS2TJFKNxfMbSLOUWR3XrJfuP1i1dCOhmDk5L7Fszj4kLnzZf6ilphNwr305UZGDC5 OBIvJM9LMkFA9bZensBYuWeRZm0IRWrFEHV5s6iXf2vIzIFwnO4PrBsV13djtdFFue02 2l35BVfpuy0uJqLbDddhjIXG3dbrNWzB7QNt6wbfdOEGgicwdvxU4I4EbhzDpWpDboa6 Z8CnBwPlL7cF9CTOrAy7kEfVxMvu0yfCG6ureONRb3zydxRJcL23qRVbMs8YlnEHXnxC 6z0LHN0YOlBEBGCjfyma3bOyQ+yHNgVxexuoFcHL+4/kWz0YVw2U1qcQJ/Y/HYNCUpOf w2Wg==
X-Received: by 10.224.147.83 with SMTP id k19mr31424468qav.72.1367196786438; Sun, 28 Apr 2013 17:53:06 -0700 (PDT)
Received: from new-host-3.home (pool-71-184-79-25.bstnma.fios.verizon.net. [71.184.79.25]) by mx.google.com with ESMTPSA id j9sm22875748qas.3.2013.04.28.17.53.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Apr 2013 17:53:05 -0700 (PDT)
Sender: Margaret Wasserman <margaretw42@gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=windows-1252
From: Margaret Wasserman <mrw@lilacglade.org>
X-Priority: 3
In-Reply-To: <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net>
Date: Sun, 28 Apr 2013 20:53:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie><7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org><38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net><516EB736.6060801@cisco.com><8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net><516EFC7E.90801@cisco.com><bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net><20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net>
To: t.p. <daedulus@btconnect.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, 29 Apr 2013 00:53:07 -0000

Hi Tom,

On Apr 19, 2013, at 6:03 AM, t.p. <daedulus@btconnect.com> wrote:
> If we required the IETF to reflect the diversity of people who are,
> e.g., IT network professionals, then the IETF would fall apart for =
lack
> of ability.
[=85]
> If the ADs of the IETF have to represent the diversity of the world -
> which could in extremes..

Has anyone even suggested that IESG should reflect the diversity of =
these groups?  Where is this coming from?  You are putting up strawmen, =
so that you can tear them down=85

The question that people are asking is why the diversity of the IETF =
leadership doesn't reflect the diversity of _the IETF_.

There is no inherent reason why 40+-year-old, white, western males who =
work at large networking equipment vendors are inherently more capable =
of serving on the IESG than people from other groups within the IETF, =
and there would be _considerable internal benefit_ to having an IESG =
that was more diverse, because diverse groups make better decisions and =
better represent the needs of the whole organization.  Therefore, if =
there is something about our culture, our structure, our selection =
process, or the way we run our meetings that is causing us to =
predominantly select our leadership from a restricted group, we would =
have _more capable_ and _better_ leadership if we could find a way to =
broaden that pool.

_That_ is what this discussion is about.  This is not an effort to meet =
some externally imposed notion of diversity.

Margaret







From glenzorn@gmail.com  Sun Apr 28 18:20:35 2013
Return-Path: <glenzorn@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 6EFED21F98E9 for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 18:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ee-XqljihZ7s for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 18:20:35 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id EAF6121F8B98 for <ietf@ietf.org>; Sun, 28 Apr 2013 18:20:34 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id p11so3293808pdj.8 for <ietf@ietf.org>; Sun, 28 Apr 2013 18:20:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=d53MLKS3pXuIrFVgifIy4fWl8RBxUmOHrJUZZPW+Jns=; b=VQTMFMxMwLOB5gE0589Nw/9phjrn9d25QOY0el5U4smQtiZFcG3zrnGtSlbPTd8CDZ n5Omvxc63Babk+f6zeP+pd5C/sVW7CO5L2uaHsJRngjarA56ctwpwRHcHpmi9WrXP1al sG3FRmHovA2xAuReexDjpQ7FtIZWtA3S68Klsk0FsK5cPpW1lCRDuLTcZjxvwPDZ2TxP V030g+2XD1hl4CNqUiyk5IzbcNepeTllsHOu6ZlRUuTkqO/9q17LqPegCyO8eMo/Cq52 45qXwrcqMjgmiFVLCl+UUIudklxAlTnuJw4cwCjYqoZXTYLWyZWM98iONksqsWF5R4El Yurw==
X-Received: by 10.68.170.66 with SMTP id ak2mr68192907pbc.123.1367198434663; Sun, 28 Apr 2013 18:20:34 -0700 (PDT)
Received: from [192.168.0.104] (ppp-115-87-126-227.revip4.asianet.co.th. [115.87.126.227]) by mx.google.com with ESMTPSA id ba10sm21700564pbd.21.2013.04.28.18.20.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 28 Apr 2013 18:20:33 -0700 (PDT)
Message-ID: <517DCADE.1070308@gmail.com>
Date: Mon, 29 Apr 2013 08:20:30 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Margaret Wasserman <mrw@lilacglade.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie><7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org><38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net><516EB736.6060801@cisco.com><8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net><516EFC7E.90801@cisco.com><bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net><20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org>
In-Reply-To: <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
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: Mon, 29 Apr 2013 01:20:35 -0000

On 04/29/2013 07:53 AM, Margaret Wasserman wrote:

>
 > Hi Tom,
 >
 > On Apr 19, 2013, at 6:03 AM, t.p. <daedulus@btconnect.com> wrote:
 >> If we required the IETF to reflect the diversity of people who
 >> are, e.g., IT network professionals, then the IETF would fall apart
 >> for lack of ability.
 > […]
 >> If the ADs of the IETF have to represent the diversity of the world
 >> - which could in extremes..
 >
 > Has anyone even suggested that IESG should reflect the diversity of
 > these groups?  Where is this coming from?  You are putting up
 > strawmen, so that you can tear them down…
 >
 > The question that people are asking is why the diversity of the IETF
 > leadership doesn't reflect the diversity of _the IETF_.
 >
 > There is no inherent reason why 40+-year-old, white, western males
 > who work at large networking equipment vendors are inherently more
 > capable of serving on the IESG than people from other groups within
 > the IETF, and there would be _considerable internal benefit_ to
 > having an IESG that was more diverse, because diverse groups make
 > better decisions and better represent the needs of the whole
 > organization.  Therefore, if there is something about our culture,
 > our structure, our selection process, or the way we run our meetings
 > that is causing us to predominantly select our leadership from a
 > restricted group, we would have _more capable_ and _better_
 > leadership if we could find a way to broaden that pool.

It seems like everybody in the IETF is already in that pool.  After all, 
any participant can self-nominate for an AD position; how can the pool 
get any bigger?

>
 >
 > _That_ is what this discussion is about.

Really?  It appeared to me that the discussion arose because some people 
were unhappy about the makeup of the IESG, not the selection pool.  
However, if what you're saying is true, that's great: since the 
selection pool is already universally inclusive, problem solved & we can 
turn our seemingly limitless capacity for bickering to other purposes ;-) .

> This is not an effort to meet  some externally imposed notion of
 > diversity.
 >
 > Margaret
 >
 >
 >
 >
 >
 >


From johnl@iecc.com  Sun Apr 28 20:15:14 2013
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 827BE21F99BB for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 20:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.45
X-Spam-Level: 
X-Spam-Status: No, score=-106.45 tagged_above=-999 required=5 tests=[AWL=2.150, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DhwkPX9LaFC3 for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 20:15:13 -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 5379921F99BA for <ietf@ietf.org>; Sun, 28 Apr 2013 20:15:13 -0700 (PDT)
Received: (qmail 72168 invoked from network); 29 Apr 2013 03:15:12 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 29 Apr 2013 03:15:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=517de5c0.xn--i8sz2z.k1304; i=johnl@user.iecc.com; bh=mpxhdOfoPNsVtV/Cz+aK63hYi1fJcemRlzHrZs0XR0k=; b=cqKEENehWKAt7fvNfYyFxfByye96XCWtFuJxmY9keM7xIFp0IumW2Hal0qPT+CAZWgTTmvgYwTZaDt5tRiIz/Lew7tAwQoUYQxr5i1IkBynypktsxmkFaIyeXgyiBtZgeJTAGJmg5ajFRAI8rs5+3/j27v+YjQCpG3o1Ws4yO6I=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=517de5c0.xn--i8sz2z.k1304; olt=johnl@user.iecc.com; bh=mpxhdOfoPNsVtV/Cz+aK63hYi1fJcemRlzHrZs0XR0k=; b=iSmvqut58DmDHsy6vjOfBhtoqWoMOd23IvyDhgc9GrbWwsQtdyyP03s8XBEvb4mT/iM1e6krcZRbDEMy8gUVrZNDl761Jt7saymQs9qjQ8y6l+fOLaelRoZsVyUwcmrB4Fio/jWf+xmvdRcEvdS/kAip0pf0YQBxSGhVxGfZB+A=
Date: 29 Apr 2013 03:14:50 -0000
Message-ID: <20130429031450.99734.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: What's a reasonable and non-discriminatory patent license?
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, 29 Apr 2013 03:15:14 -0000

The Patently-O blog has a new guest post by Jorge Contreras, who among
other things is the IETF's lawyer, on a recent court decision about
how to determine what's an appropriate RAND royalty rate for
standard-essential patents.  The patents and standards in question
aren't from the IETF (they're ITU H.264 and IEEE 801.11) but the
article is highly relevant to the patent issues that crop up here.

Jorge writes well and it's quite readable.

http://www.patentlyo.com/patent/2013/04/so-thats-what-rand-means-a-brief-report-on-the-findings-of-fact-and-conclusions-of-law-in-microsoft-v-motorola.html

-- 
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 mstjohns@comcast.net  Sun Apr 28 21:05:40 2013
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 106DC21F9633 for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 21:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.838
X-Spam-Level: 
X-Spam-Status: No, score=-92.838 tagged_above=-999 required=5 tests=[FH_RELAY_NODNS=1.451, GB_SUMOF=5, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DfA1+Ew1BsWz for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 21:05:39 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 5657221F93BA for <ietf@ietf.org>; Sun, 28 Apr 2013 21:05:39 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta03.westchester.pa.mail.comcast.net with comcast id Vg3J1l0050bG4ec53g5eKl; Mon, 29 Apr 2013 04:05:38 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta03.westchester.pa.mail.comcast.net with comcast id Vg5d1l00V2kB7pQ3Pg5eRG; Mon, 29 Apr 2013 04:05:38 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 29 Apr 2013 00:05:37 -0400
To: Margaret Wasserman <mrw@lilacglade.org>,t.p. <daedulus@btconnect.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1367208338; bh=mmdYwXsX1u0/5JnJF5hbc9/aLsUR9S/JpGShP7LjvEk=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=KzTLi55CXWei/n/OQhOj8X+jL103KyZki4e/gc+S5NjziKzh/qVFJSg2o7HJOIlDa DT+DKPqsT8fPt+6S6hgM9+mIltoz/6gdwywB2gqe0qBeHfgvKxCUgydD6fL5JEiSNY Y5g7hVgfOjLag4HjNsW4Htu3I5Q/17ArVAko8+owKq7UHU6HgdoknzmZ1PkYDMoKJi EQ0Qw+shwablwU3IKEDUIKIP6Qho0jcawZrCb7wXq1EMrpx1m5F1jtswjU9SBtTPXx 6Ry5G2uVnM3uNr0gipXdgy+5MJTJnk14Q4Ma7Tg5Acx4P9PD7mPmGnFhGM1VFP0sTz 4tkvhf9T3M9Cg==
Message-Id: <20130429040539.5657221F93BA@ietfa.amsl.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: Mon, 29 Apr 2013 04:05:40 -0000

At 08:53 PM 4/28/2013, Margaret Wasserman wrote:



>The question that people are asking is why the diversity of the IETF leadership doesn't reflect the diversity of _the IETF_.

Let's consider for a moment that this may not actually be the correct question.  Instead, consider "Why the diversity of the IETF leadership doesn't reflect the diversity of the set of the IETF WG chairs"?  I believe this is a more representative candidate population for the IAB and IESG.  

By my count (using the WG chairs picture page), there are 202 current working group chairs. Of these 15 are female  - or 7.4% of the population [It would be more reliable to do this for any WG chair in the last 5-10 years, but the above was readily available and I think provides at least the basis for discussion.  Anticipating the argument, I would assume for the sake of discussion a fairly similar percentage of ex-working group chairs per gender unless there is evidence to the contrary]

There are 14 (current area directors plus the chair) members of the IESG, of which none are currently female.

There are 12 current IAB members of which 1 member is female.

Assuming perfect distribution, that would suggest that 14 * (15/202) or 1.03 IESG members should be female.

Assuming perfect distribution, that would suggest that 12 * (15/202) or .89 IAB members should be female.

Assuming perfect distribution, that would suggest that 26 * (15/202) or 1.93 IAB + IESG members should be female. 

And pretending for a moment that picks for the IAB and IESG are completely random from the candidate set of Working group chairs, the binomial distribution for 7.4% for 27 positions is:

0 - 12.5%, 1 - 27.0%, 2 - 28.1%, 3 or more - 32.5%.  (e.g. about 40% of the time, the IAB and IESG  combined will have 0 or 1 female members).

for 7.4% for 15 positions  (IESG) is: 
0 - 31.4%, 1 - 37.8%, 2 - 21.2%, 3 or more - 9.5%

for 7.4% for 12 positions (IAB) is: 
0 - 39.6%, 1 - 38.1%, 2 - 16.8%, 3 or more - 5.4%


But the actual one you should consider is 7.4% for 14 positions (annual replacement):
0 - 34%, 1 - 38.1%, 2 - 19.9%, 3 or more - 8%.    

This last one says that for any given nomcom selection, assuming strict random selection, 72% of the time 0 or 1 females will be selected across both the IAB and IESG.  You should use this one as the actual compositions of the IAB/IESG are the sum of all the nomcom actions that have happened before.

There are statistical tests to determine whether there is a statistically significant difference in populations, but my admittedly ancient memories of statistics suggest that the population size of the IAB/IESG is too small for a statistically valid comparison with either the WG chair population or the IETF population.

Of course, the nomcom doesn't select and the confirming bodies do not confirm based on a roll of the dice.  
But looking at this analysis, it's unclear - for this one axis of gender - that the question "why the diversity of the IETF leadership does not reflect the diversity of the set of IETF WG chairs" has a more correct answer than "the luck of the draw".

My base premise may be incorrect:  That you need to have been a WG chair prior to service as an IAB or IESG member.  I hope it isn't as I think this level of expertise is useful for success in these bodies.    

Assuming it is correct, then the next question is whether or not there is a significant difference in percentage of female attendees vs percentage of female working group chairs and is there a root cause for that difference that the IETF can address in a useful manner.

Mike

 










From randy_presuhn@mindspring.com  Sun Apr 28 21:05:53 2013
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 5D2F721F99D8 for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 21:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xc40XmFnqJF7 for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 21:05:52 -0700 (PDT)
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 B318921F99BA for <ietf@ietf.org>; Sun, 28 Apr 2013 21:05:52 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=N23Csl9f31LpnYylZhPI806a3pNaRglOo9dLzJ0Us+G1zbBnMCzYPaBDfQqCpi9J; 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 [76.254.50.20] (helo=oemcomputer) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1UWfLb-0000dJ-US for ietf@ietf.org; Mon, 29 Apr 2013 00:05:52 -0400
Message-ID: <00c301ce448f$336210c0$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "ietf" <ietf@ietf.org>
References: <C5E21A29-4336-469A-B799-3E9BCDFBF3B5@gmail.com><6.2.5.6.2.20130422081720.0db4ca38@resistor.net><51759238.8000306@si6networks.com><6.2.5.6.2.20130422125704.0d551178@resistor.net><5176B8A2.40809@si6networks.com><C91E67751B1EFF41B857DE2FE1F68ABA0C050FCB@TK5EX14MBXC273.redmond.corp.microsoft.com><023601ce4193$81d5e640$4001a8c0@gateway.2wire.net><CAA_e5Z7siAGELG+J9H7t-_ggj6wXFY2M4fK=-n=OwPE08Hx-tQ@mail.gmail.com> <9910.1366980470@sandelman.ca>
Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
Date: Sun, 28 Apr 2013 21:08:25 -0700
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.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88880ff2f3e23ebe946dfab7345e27698fa6136006aeffd25a1350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.254.50.20
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 04:05:53 -0000

Hi -

> From: "Michael Richardson" <mcr+ietf@sandelman.ca>
> To: "ietf" <ietf@ietf.org>; "Andrew McGregor" <andrewmcgr@gmail.com>
> Cc: "Christian Huitema" <huitema@microsoft.com>; "SM" <sm@resistor.net>
> Sent: Friday, April 26, 2013 5:47 AM
> Subject: Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06
...
> I think that non-contiguous ifindexes are a pain in the ass (based upon
> my understanding of enumeration of interfaces in the interface MIB), but
> are they essentially forbidden?  Having holes would make it easier to
> keep things consistent.

This is exactly what RFC 2863 (The Interfaces Group MIB)
specifies.  Non-contiguous ifIndex values are permitted.

This issue was considered at some length in the development
of RFC 2863.  Section 3.1.5 explains in detail why the semantics
of ifIndex were changed (from their original MIB-II definition)
to permit "holes", while the semantics of ifNumber were left
untouched.

Randy



From abdussalambaryun@gmail.com  Sun Apr 28 22:31:05 2013
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 849CE21F99AB for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 22:31:05 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7i6BHhbI7FHD for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 22:31:05 -0700 (PDT)
Received: from mail-da0-x230.google.com (mail-da0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCC221F999F for <ietf@ietf.org>; Sun, 28 Apr 2013 22:31:05 -0700 (PDT)
Received: by mail-da0-f48.google.com with SMTP id f10so2757693dak.7 for <ietf@ietf.org>; Sun, 28 Apr 2013 22:31:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=S4I88WbGnEvfOZ+fUAT9+5cKsebumbUOTOCh5zbllZo=; b=he08WQwIQ+qjG+bG9yafQurZHSi9+og3kbG3IvBettbTUgT8AOndcqsteL1tjKzxo6 kzKMQ/PgCEC0KEWTljSbPtnh0uWy4OSKFPlv0EIhs5STlic7lGTTfibhaw+bZG9c98vi S9FOUgJVq3FU3vWKkpMbccsUmk/qgI2vHwt/A36fhxQGPyEFdpn6ruHuwGpSUT3CaQD2 UK5rebEgByX3CmUoQ2jc3wv1T4XdyzyWs7oUAaPUoFFqgwBwLa5kNf+ukgLtxiFCGc3g 7QEEqdpTYPlJ6b3exlPNsAGv+rcHKm9RtSjpBGmYYJfbtn6r/Yc7mJBHUooXVLoYZxNy /6CA==
MIME-Version: 1.0
X-Received: by 10.68.43.35 with SMTP id t3mr70127120pbl.202.1367213464798; Sun, 28 Apr 2013 22:31:04 -0700 (PDT)
Received: by 10.68.230.35 with HTTP; Sun, 28 Apr 2013 22:31:04 -0700 (PDT)
In-Reply-To: <517D3A5C.4070009@gmail.com>
References: <20130412215712.8482.32099.idtracker@ietfa.amsl.com> <CAC4RtVABudiEa_cqqr9OmcbUsAuWGXftisrjEATRLgNvJubXzw@mail.gmail.com> <517AA859.9060804@dcrocker.net> <517D3A5C.4070009@gmail.com>
Date: Mon, 29 Apr 2013 07:31:04 +0200
Message-ID: <CADnDZ8-RJF0jLBFwtPY93NmMGgO-Xp=ZNFdBj-pLH97Jz0gQfg@mail.gmail.com>
Subject: Re: [Tools-discuss] Last Call: <draft-sheffer-running-code-04.txt> (Improving Awareness of Running Code: the Implementation Status Section) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-sheffer-running-code@tools.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, 29 Apr 2013 05:31:05 -0000

On 4/28/13, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
> Hi Dave,
>
> Thank you for your thorough review. While I accept many of your
> comments, I must say I disagree with you on a few points, which together
> go to the core of our motivation in writing this document. Thank you for
> helping me clarify these points to myself :-)
>
> - Our goal is much *less* ambitious than defining a framework for
> documenting implementations for long-term protocol projects. Our primary
> goal is to aid working group members in making informed decisions about
> the quality of specifications. I believe this narrow focus is much more
> realistic.

Was this goal/point mentioned in the I-D if not, it will be nice to
clarify this point to future readers,

>
> - As a result of the above: 1. We define the information as pre-RFC
> only; 2. The main medium is the I-D, as opposed to Web pages/wikis/CMS
> (although we see them as valid alternatives); 3. We focus on WG
> documents, as opposed to "all" IETF documents.

If not mentioned in I-D, please clarify this point in the I-D,

From dhc@dcrocker.net  Sun Apr 28 22:34:21 2013
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 95AC021F9CEE for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 22:34:21 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wSzTV43DjHOQ for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 22:34:20 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AFA9A21F9CED for <ietf@ietf.org>; Sun, 28 Apr 2013 22:34:20 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3T5YEJa019321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 28 Apr 2013 22:34:17 -0700
Message-ID: <517E0656.1000803@dcrocker.net>
Date: Sun, 28 Apr 2013 22:34:14 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com>
In-Reply-To: <20130429040539.5657221F93BA@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.66]); Sun, 28 Apr 2013 22:34:18 -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: Mon, 29 Apr 2013 05:34:21 -0000

On 4/28/2013 9:05 PM, Michael StJohns wrote:
> Let's consider for a moment that this may not actually be the correct question.  Instead, consider "Why the diversity of the IETF leadership doesn't reflect the diversity of the set of the IETF WG chairs"?  I believe this is a more representative candidate population for the IAB and IESG.


Except that the IESG members select the wg chairs, which makes your 
baseline stastistic suspect; it's too easy for all sorts of biasing 
factors to sway the allocation of wg chair positions.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From huitema@microsoft.com  Sun Apr 28 22:55:29 2013
Return-Path: <huitema@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 2BFBB21F9D21 for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 22:55:29 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WRFh3py-0iPK for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 22:55:28 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0204.outbound.protection.outlook.com [207.46.163.204]) by ietfa.amsl.com (Postfix) with ESMTP id 86F1321F9D20 for <ietf@ietf.org>; Sun, 28 Apr 2013 22:55:28 -0700 (PDT)
Received: from BN1AFFO11FD028.protection.gbl (10.58.52.201) by BN1AFFO11HUB010.protection.gbl (10.58.52.120) with Microsoft SMTP Server (TLS) id 15.0.675.0; Mon, 29 Apr 2013 05:52:16 +0000
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.37) by BN1AFFO11FD028.mail.protection.outlook.com (10.58.52.88) with Microsoft SMTP Server (TLS) id 15.0.675.0 via Frontend Transport; Mon, 29 Apr 2013 05:52:16 +0000
Received: from TK5EX14MBXC272.redmond.corp.microsoft.com ([169.254.2.184]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.02.0318.003; Mon, 29 Apr 2013 05:52:15 +0000
From: Christian Huitema <huitema@microsoft.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Michael StJohns <mstjohns@comcast.net>
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHOPOUbwl2LLJoxmkeCMXsLhpVRxJjsbgIAgAA1z4CAABjCAIAAAtPA
Date: Mon, 29 Apr 2013 05:52:14 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net>
In-Reply-To: <517E0656.1000803@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.37]
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:(189002)(199002)(69226001)(47776003)(20776003)(74366001)(56816002)(63696002)(51856001)(80022001)(46102001)(81542001)(53806001)(50986001)(54316002)(31966008)(47446002)(47976001)(74662001)(46406003)(66066001)(74502001)(4396001)(47736001)(33656001)(49866001)(6806003)(76482001)(79102001)(16406001)(77982001)(59766001)(81342001)(65816001)(50466002)(23726002)(55846006)(54356001)(56776001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB010; H:TK5EX14HUBC106.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0831C25939
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, 29 Apr 2013 05:55:29 -0000

> Except that the IESG members select the wg chairs, which makes your basel=
ine stastistic suspect; it's too easy for all sorts of biasing factors to s=
way the
> allocation of wg chair positions.

Mike actually mentioned that. Let's assume a simplified curriculum of parti=
cipant -> author/editor -> WG chair -> IESG, which more or less reflects in=
creasing seniority in the IETF. We may suspect that there is bias that, at =
each step, privileges some candidates over others. However, the mechanisms =
are different at each step. Self-selection, selection by WG chair, selectio=
n by the nom com. It makes sense to assess the filtering effect of each ste=
p independently, and in particular to assess the nomcom by comparing the po=
ol of WG chairs to the selected nominees.

-- Christian Huitema



From dhc@dcrocker.net  Sun Apr 28 22:57:08 2013
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 665F321F9606 for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 22:57:08 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r-kX-rpnVxUL for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 22:57:07 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C5D9C21F95EE for <ietf@ietf.org>; Sun, 28 Apr 2013 22:57:07 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3T5v33o019491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 28 Apr 2013 22:57:06 -0700
Message-ID: <517E0BAF.2000207@dcrocker.net>
Date: Sun, 28 Apr 2013 22:57:03 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.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.66]); Sun, 28 Apr 2013 22:57:06 -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: Mon, 29 Apr 2013 05:57:08 -0000

On 4/28/2013 10:52 PM, Christian Huitema wrote:
>> Except that the IESG members select the wg chairs, which makes your
>> baseline stastistic suspect; it's too easy for all sorts of biasing
>> factors to sway the allocation of wg chair positions.
>
> Mike actually mentioned that. Let's assume a simplified curriculum of
> participant -> author/editor -> WG chair -> IESG, which more or less
> reflects increasing seniority in the IETF. We may suspect that there
> is bias that, at each step, privileges some candidates over others.
> However, the mechanisms are different at each step.


Exactly.  Complicated processes, needing high quality data that gets 
complicated analysis, that we aren't well-enough trained to do well and 
aren't going to be doing.

All of which is why we should limit our attempts to do numerical
analysis for this topic, and worry far more about the basics, including 
such things as interaction (in)sensitivities, group tone and style, and 
observable misbehaviors, all of which are likely to produce biasing results.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From huitema@microsoft.com  Sun Apr 28 23:19:12 2013
Return-Path: <huitema@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 CE2F721F9CE6 for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 23:19:12 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pw4GOQj2iRiF for <ietf@ietfa.amsl.com>; Sun, 28 Apr 2013 23:19:12 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by ietfa.amsl.com (Postfix) with ESMTP id 23A2721F9A00 for <ietf@ietf.org>; Sun, 28 Apr 2013 23:19:11 -0700 (PDT)
Received: from BN1AFFO11HUB030.protection.gbl (10.58.52.140) by BN1BFFO11HUB016.protection.gbl (10.58.53.126) with Microsoft SMTP Server (TLS) id 15.0.675.0; Mon, 29 Apr 2013 06:15:00 +0000
Received: from BN1BFFO11FD015.protection.gbl (10.58.52.202) by BN1AFFO11HUB030.protection.gbl (10.58.52.140) with Microsoft SMTP Server (TLS) id 15.0.675.0; Mon, 29 Apr 2013 06:15:00 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD015.mail.protection.outlook.com (10.58.53.75) with Microsoft SMTP Server (TLS) id 15.0.675.0 via Frontend Transport; Mon, 29 Apr 2013 06:14:59 +0000
Received: from TK5EX14MBXC272.redmond.corp.microsoft.com ([169.254.2.184]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.02.0318.003; Mon, 29 Apr 2013 06:14:58 +0000
From: Christian Huitema <huitema@microsoft.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHOPOUbwl2LLJoxmkeCMXsLhpVRxJjsbgIAgAA1z4CAABjCAIAAAtPAgAADjYCAAAK8UA==
Date: Mon, 29 Apr 2013 06:14:57 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0C0672CC@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.com> <517E0BAF.2000207@dcrocker.net>
In-Reply-To: <517E0BAF.2000207@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.35]
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:(199002)(189002)(74662001)(47446002)(74502001)(23726002)(31966008)(46406003)(6806003)(53806001)(51856001)(56816002)(56776001)(54316002)(59766001)(69226001)(54356001)(76482001)(20776003)(47776003)(63696002)(81542001)(65816001)(55846006)(81342001)(80022001)(46102001)(16406001)(74366001)(50986001)(33656001)(77982001)(50466002)(4396001)(47736001)(49866001)(47976001)(79102001)(66066001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB030; H:TK5EX14MLTC103.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-Forefront-PRVS: 0831C25939
X-OriginatorOrg: microsoft.onmicrosoft.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: Mon, 29 Apr 2013 06:19:12 -0000

> All of which is why we should limit our attempts to do numerical analysis=
 for this topic, and worry far more about the basics,=20
> including such things as interaction (in)sensitivities, group tone and st=
yle, and observable misbehaviors, all of which are likely to produce biasin=
g results.

Certainly useful, but it is easy to inject one's own bias into such process=
es, and to overlook other factors. I may be biased, but I have the impressi=
on that the largest source of bias in IESG selection is the need to secure =
funding for the job, which effectively self-select people working for large=
 companies making networking products. Gender may be the least of the probl=
ems there; there are other dimensions of diversity, e.g. academic vs. indus=
try, network equipment versus internet service providers, software versus h=
ardware, etc. Only a fraction of these segments can afford to have someone =
working full-time on the IESG. Now, having to work full time is a bit much =
for a volunteer position, and we may want to consider ways to remedy that.

-- Christian Huitema

=20

From stbryant@cisco.com  Mon Apr 29 01:55:52 2013
Return-Path: <stbryant@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 DB3C221F9A49 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 01:55:52 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0ePJDMujLkq for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 01:55:52 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id EAB0B21F9A36 for <ietf@ietf.org>; Mon, 29 Apr 2013 01:55:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1743; q=dns/txt; s=iport; t=1367225752; x=1368435352; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=oZAf6rNw7jIOp8vvnc6dnhcOSoKyQqqeZL/l/hwT0IY=; b=EQ5+7gRCGOCKQv2caJZnzsDgYlEJryuHM75hz2Bv23ezSB4JfDYvlUSy S5PCMVSAJtWr8LgFEgLp7gFzY2HMtQk2FJ6+vzuoz5UE+Cnor3SW5yna5 j2mlor8QvxqV/HBfL1il5VY5AeXYghyJZCqcx9+1Ur/flULajQxdNA6zd k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFAHs0flGQ/khL/2dsb2JhbABSgwe+fn8WdIIfAQEBBDIBBUABEAsOCgkWDwkDAgECAUUGDQEFAgEBiBK8QI8aB4NPA5cekSqDEg
X-IronPort-AV: E=Sophos;i="4.87,572,1363132800"; d="scan'208";a="82275569"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 29 Apr 2013 08:55:48 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r3T8tjHN002507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Apr 2013 08:55:46 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3T8tjMA016919; Mon, 29 Apr 2013 09:55:45 +0100 (BST)
Message-ID: <517E3590.4000902@cisco.com>
Date: Mon, 29 Apr 2013 09:55:44 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Margaret Wasserman <mrw@lilacglade.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie><7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org><38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net><516EB736.6060801@cisco.com><8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net><516EFC7E.90801@cisco.com><bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net><20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org>
In-Reply-To: <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: Mon, 29 Apr 2013 08:55:53 -0000

On 29/04/2013 01:53, Margaret Wasserman wrote:
> Hi Tom,
>
> On Apr 19, 2013, at 6:03 AM, t.p. <daedulus@btconnect.com> wrote:
>> If we required the IETF to reflect the diversity of people who are,
>> e.g., IT network professionals, then the IETF would fall apart for lack
>> of ability.
> […]
>> If the ADs of the IETF have to represent the diversity of the world -
>> which could in extremes..
> Has anyone even suggested that IESG should reflect the diversity of these groups?  Where is this coming from?  You are putting up strawmen, so that you can tear them down…
>
> The question that people are asking is why the diversity of the IETF leadership doesn't reflect the diversity of _the IETF_.
>
The evidence seems to be that human's are terrible at "guessing"
statistics, and the only statistics that are reliable as those
objectively gathered and subjected to rigorous statistical analysis.
You can often see this in human assessments of risk. It is
also in the nature of statistics that you get long runs of outliers, and
that only when you take a long view to you see the averages you
would expect. Again Humans are terrible with this, assuming
for example that a coin that comes up heads 10 times in a row
the assumption is that this is bias, and not a normal statistical
variation that you would expect in an infinite number of throws.

Given the diversity ratios that we see, it is unclear to me whether
we are observing a systematic effect or a statistical effect.

It would be useful to the discussion if we could see data on diversity
that was the output of a rigorous  statistical analysis. i.e. one that
included a confidence analysis and not a simple average in a few
spot years.

- Stewart



From stbryant@cisco.com  Mon Apr 29 02:11:27 2013
Return-Path: <stbryant@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 6007221F98CF for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 02:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.099
X-Spam-Level: 
X-Spam-Status: No, score=-108.099 tagged_above=-999 required=5 tests=[AWL=-2.500, BAYES_00=-2.599, GB_SUMOF=5, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IWyGsNy25Aec for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 02:11:26 -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 F387B21F97C5 for <ietf@ietf.org>; Mon, 29 Apr 2013 02:11:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4624; q=dns/txt; s=iport; t=1367226686; x=1368436286; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=KJqvCAb/p9lk6H0v3KRcYIyyXeFUQFAcWnLsj4TRNaA=; b=OhYkC68SORMTjBp+3bYpsw3md9Bis9pWfGzoOx86ZSIo/252eYItONJE 1UVzstiFMewfo7LtBmhctgx6f+LslRX8EimZzgWj25hHu4umqQ60Zo8Nf Sq400RfMbQHrxR8k+QSyX+90P9VmENTY9zTstL7snc/43izTyizJlOLy5 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAOI4flGQ/khM/2dsb2JhbABSgwe8GYJlgQAWdIIfAQEBBDgzDQEQCxgJFg8JAwIBAgFFBg0BBwEBiBK8NY1XgUMHg08Dlx6RKoMS
X-IronPort-AV: E=Sophos;i="4.87,572,1363132800"; d="scan'208";a="153440605"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 29 Apr 2013 09:11:20 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r3T9BI70007913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Apr 2013 09:11:19 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3T9BEYg017938; Mon, 29 Apr 2013 10:11:16 +0100 (BST)
Message-ID: <517E3932.9060006@cisco.com>
Date: Mon, 29 Apr 2013 10:11:14 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com>
In-Reply-To: <20130429040539.5657221F93BA@ietfa.amsl.com>
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
Reply-To: stbryant@cisco.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: Mon, 29 Apr 2013 09:11:27 -0000

On 29/04/2013 05:05, Michael StJohns wrote:
> At 08:53 PM 4/28/2013, Margaret Wasserman wrote:
>
>
>
>> The question that people are asking is why the diversity of the IETF leadership doesn't reflect the diversity of _the IETF_.
> Let's consider for a moment that this may not actually be the correct question.  Instead, consider "Why the diversity of the IETF leadership doesn't reflect the diversity of the set of the IETF WG chairs"?  I believe this is a more representative candidate population for the IAB and IESG.
>
> By my count (using the WG chairs picture page), there are 202 current working group chairs. Of these 15 are female  - or 7.4% of the population [It would be more reliable to do this for any WG chair in the last 5-10 years, but the above was readily available and I think provides at least the basis for discussion.  Anticipating the argument, I would assume for the sake of discussion a fairly similar percentage of ex-working group chairs per gender unless there is evidence to the contrary]
>
> There are 14 (current area directors plus the chair) members of the IESG, of which none are currently female.
>
> There are 12 current IAB members of which 1 member is female.
>
> Assuming perfect distribution, that would suggest that 14 * (15/202) or 1.03 IESG members should be female.
>
> Assuming perfect distribution, that would suggest that 12 * (15/202) or .89 IAB members should be female.
>
> Assuming perfect distribution, that would suggest that 26 * (15/202) or 1.93 IAB + IESG members should be female.
>
> And pretending for a moment that picks for the IAB and IESG are completely random from the candidate set of Working group chairs, the binomial distribution for 7.4% for 27 positions is:
>
> 0 - 12.5%, 1 - 27.0%, 2 - 28.1%, 3 or more - 32.5%.  (e.g. about 40% of the time, the IAB and IESG  combined will have 0 or 1 female members).
>
> for 7.4% for 15 positions  (IESG) is:
> 0 - 31.4%, 1 - 37.8%, 2 - 21.2%, 3 or more - 9.5%
>
> for 7.4% for 12 positions (IAB) is:
> 0 - 39.6%, 1 - 38.1%, 2 - 16.8%, 3 or more - 5.4%
>
>
> But the actual one you should consider is 7.4% for 14 positions (annual replacement):
> 0 - 34%, 1 - 38.1%, 2 - 19.9%, 3 or more - 8%.
>
> This last one says that for any given nomcom selection, assuming strict random selection, 72% of the time 0 or 1 females will be selected across both the IAB and IESG.  You should use this one as the actual compositions of the IAB/IESG are the sum of all the nomcom actions that have happened before.
>
> There are statistical tests to determine whether there is a statistically significant difference in populations, but my admittedly ancient memories of statistics suggest that the population size of the IAB/IESG is too small for a statistically valid comparison with either the WG chair population or the IETF population.
>
> Of course, the nomcom doesn't select and the confirming bodies do not confirm based on a roll of the dice.
> But looking at this analysis, it's unclear - for this one axis of gender - that the question "why the diversity of the IETF leadership does not reflect the diversity of the set of IETF WG chairs" has a more correct answer than "the luck of the draw".
>
> My base premise may be incorrect:  That you need to have been a WG chair prior to service as an IAB or IESG member.  I hope it isn't as I think this level of expertise is useful for success in these bodies.
>
> Assuming it is correct, then the next question is whether or not there is a significant difference in percentage of female attendees vs percentage of female working group chairs and is there a root cause for that difference that the IETF can address in a useful manner.
>
> Mike
>
This is in line with my own estimate based on an approximation of 1:10 
which with random selection gives an error approximation of sqrt(1)=1

The other thing to remember is that whilst your proportional estimates 
are likely to be correct, in a random process you will get long runs of 
"bias" that only average out in the long run. So you will get long runs 
of 0. Very infrequently you will also get long runs of 27. In both cases 
it is in human nature to  would assume something is wrong, when it is an 
artifact of random numbers. Humans have considerable difficulty 
discriminating between systematic and statistical problems, and taking 
the long view rather than the short view.

For that reason, as I noted in my previous post, we need a rigorous 
statistical analysis with proper confidence intervals, rather than 
simple averages on spot years.

- Stewart


From stbryant@cisco.com  Mon Apr 29 02:15:31 2013
Return-Path: <stbryant@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 6133521F9D47 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 02:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.349
X-Spam-Level: 
X-Spam-Status: No, score=-109.349 tagged_above=-999 required=5 tests=[AWL=1.250, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C+-uEgBgJ-gx for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 02:15:30 -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 7643E21F9CE6 for <ietf@ietf.org>; Mon, 29 Apr 2013 02:15:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=983; q=dns/txt; s=iport; t=1367226930; x=1368436530; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Sv11c32GrG0Ds7M8vMFtE45fH4E8aYjz5MAJPQQF0l4=; b=XwD62PZKbJCatGeHuoj1zE6FFI2thXcRyNnlUDpp3ghx7B952HVRzO80 gztGvgdrGzL3AXOpxUMo2JVPnikV94fBhTfO0wpBllnymxHj60fAHQVX8 fjB/zETQ5hoemQs51LGLhJ8v1xxa6mtAyUNAp6tBvdUiBBWrDbgALBYjN k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAO44flGQ/khN/2dsb2JhbABSgwe8GYJlgQAWdIIfAQEBBCcRQAEQCxgJFg8JAwIBAgFFEwEHAQGIErw1jxoHFoM5A5cekSqDEg
X-IronPort-AV: E=Sophos;i="4.87,572,1363132800"; d="scan'208";a="13159583"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 29 Apr 2013 09:15:25 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3T9FNAH014113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Apr 2013 09:15:23 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3T9FLNq018105; Mon, 29 Apr 2013 10:15:22 +0100 (BST)
Message-ID: <517E3A29.7080603@cisco.com>
Date: Mon, 29 Apr 2013 10:15:21 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.com> <517E0BAF.2000207@dcrocker.net>
In-Reply-To: <517E0BAF.2000207@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Christian Huitema <huitema@microsoft.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: Mon, 29 Apr 2013 09:15:31 -0000

On 29/04/2013 06:57, Dave Crocker wrote:
> On 4/28/2013 10:52 PM, Christian Huitema wrote:
>>> Except that the IESG members select the wg chairs, which makes your
>>> baseline stastistic suspect; it's too easy for all sorts of biasing
>>> factors to sway the allocation of wg chair positions.
>>
>> Mike actually mentioned that. Let's assume a simplified curriculum of
>> participant -> author/editor -> WG chair -> IESG, which more or less
>> reflects increasing seniority in the IETF. We may suspect that there
>> is bias that, at each step, privileges some candidates over others.
>> However, the mechanisms are different at each step.
>
>
> Exactly.  Complicated processes, needing high quality data that gets 
> complicated analysis, that we aren't well-enough trained to do well 
> and aren't going to be doing.
>
>
Dave

Of all the social mixes  you would anticipate the IETF to be in the 
likely to do it, likely to do it correctly quadrant.

Stewart

From ron.even.tlv@gmail.com  Mon Apr 29 02:42:33 2013
Return-Path: <ron.even.tlv@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 231EC21F9CED; Mon, 29 Apr 2013 02:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lgDPWDG0dwc7; Mon, 29 Apr 2013 02:42:32 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC3921F9CE3; Mon, 29 Apr 2013 02:42:17 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id c10so2529665wiw.0 for <multiple recipients>; Mon, 29 Apr 2013 02:42:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received: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=9ZdZw8l4tDtl82FECtFoX1vKZV+jKx3CIptivd3Cs8s=; b=vyiBqu4xT9SAEq/FISmohpFfz5b8JZ74v5mIcNf7go3LpyUcPbZGaSAwgv4RxSgcmt YsEF3MW3gDJFLI0EK8SLEmEyMB/bmIFHatjaMrFMpbrqkeIMUSZfA0mjofY2a3bNwLuu 6/5EuxrYjT96Ujs4fZCkZ6nfJbbXCSaFILTGjlGs5ixoEmYxVMwt7KXFWEJ4RcV91G1N cm58LMWWLl3jDkojfODPY8P20bqtReVuuOLew5zdPvWy2rIVa1x5ehrMrWjBzr9Qr3vR bb2LBi0moCtTE9urnB5/jTDywrfHNY4gzEWyTO2SFGROLNnSLYrdv+FyCJKYZQUN+jI1 lOwg==
X-Received: by 10.194.10.129 with SMTP id i1mr1574693wjb.21.1367228536716; Mon, 29 Apr 2013 02:42:16 -0700 (PDT)
Received: from RoniE (bzq-79-181-177-28.red.bezeqint.net. [79.181.177.28]) by mx.google.com with ESMTPSA id e8sm13430147wic.5.2013.04.29.02.42.13 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 29 Apr 2013 02:42:15 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Martin Bjorklund'" <mbj@tail-f.com>
References: <019901ce43ea$bbd575a0$338060e0$@gmail.com>	<20130428.115010.513224826.mbj@tail-f.com>	<01ba01ce440c$408d4720$c1a7d560$@gmail.com> <20130429.102542.1993240684524912340.mbj@tail-f.com>
In-Reply-To: <20130429.102542.1993240684524912340.mbj@tail-f.com>
Subject: RE: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
Date: Mon, 29 Apr 2013 12:41:37 +0300
Message-ID: <020b01ce44bd$c0ba0fd0$422e2f70$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFWiDTvx1wg5jy+XbNDGWkbCL4PFgG0N6f1AovlA7wBcSt+GJmu4G7A
Content-Language: en-us
Cc: gen-art@ietf.org, draft-ietf-netmod-interfaces-cfg.all@tools.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, 29 Apr 2013 09:42:33 -0000

Hi,
This new text is OK.
Thanks
Roni

-----Original Message-----
From: Martin Bjorklund [mailto:mbj@tail-f.com] 
Sent: 29 April, 2013 11:26 AM
To: ron.even.tlv@gmail.com
Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org; ietf@ietf.org;
gen-art@ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10

Hi,

"Roni Even" <ron.even.tlv@gmail.com> wrote:
> Martin,
> Thanks for the response. I am OK with your responses to the nits.
> 
> As for the comment on location I think I understand but what got me 
> thinking was the examples.
> In E.1
> 
> "An operator can configure a new interface by sending an <edit-config>
>    containing:
> 
>      <interface nc:operation="create">
>        <name>fastethernet-1/0</name>
>      </interface>
> 
>    When the server processes this request, it will set the leaf "type"
>    to "ethernetCsmacd" and "location" to "1/0".  Thus, if the client
>    performs a <get-config> right after the <edit-config> above, it will
>    get:
> 
>      <interface>
>        <name>fastethernet-1/0</name>
>        <type>ethernetCsmacd</type>
>        <location>1/0</location>
>      </interface>"
> 
> I can see how the linkage between the location and name is done. I am 
> not sure how the operator knows from the response what is the physical 
> location without knowing the device type and manufacturer but at least 
> the linkage is there and this is why I thought of it more as a logical 
> device and not physical one.

Ok.  Since this is an example of a configuration of a physical interface, it
is assumed that the operator somehow knows which physical port is being
reconfigured -- somehow the operator must be able to know what the port
where the new cable was inserted is called in the config.

But it makes sense to be more clear about this.  How about this
change:


OLD:

  The implementation restricts the names of the interfaces to one of
  "fastethernet-N/M" or "gigabitethernet-N/M".  The "location" of an
  interface is a string on the form "N/M".  The implementation
  auto-initializes the values for "type" and "location" based on the
  interface name.

NEW:

  The implementation restricts the names of the interfaces to one of
  "fastethernet-N/M" or "gigabitethernet-N/M".  The "location" of an
  interface is a string on the form "N/M".  It is assumed that the
  operator is aware of this naming scheme.  The implementation
  auto-initializes the values for "type" and "location" based on the
  interface name.

> When looking at E2.2 example

(ditto for this example.)


/martin



>   " An operator can configure a new interface by sending an <edit-config>
>    containing:
> 
>      <interface nc:operation="create">
>        <name>acme-interface</name>
>        <type>ethernetCsmacd</type>
>        <location>1/0</location>
>      </interface>"
> 
> Here the operator need to know the device to configure a specific 
> interface and know how many interface exist and how they are named. So 
> you assume that for this case this is known to the configuration.
> 
> Roni
> 
> 
> 
> 
> -----Original Message-----
> From: Martin Bjorklund [mailto:mbj@tail-f.com]
> Sent: 28 April, 2013 12:50 PM
> To: ron.even.tlv@gmail.com
> Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org; 
> ietf@ietf.org; gen-art@ietf.org
> Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
> 
> Hi,
> 
> Thank you for your review.  Comments inline.
> 
> "Roni Even" <ron.even.tlv@gmail.com> wrote:
> > 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-netmod-interfaces-cfg-10
> > 
> > Reviewer: Roni Even
> > 
> > Review Date:2013-4-28
> > 
> > IETF LC End Date: 2013-5-3
> > 
> > IESG Telechat date: 2013-5-16
> > 
> >  
> > 
> > Summary: This draft is almost ready for publication as Standard track
RFC.
> > 
> >  
> > 
> >  
> > 
> > Major issues:
> > 
> >  
> > 
> > Minor issues:
> > 
> >  
> > 
> > 1.       I had some problem understanding the "location" leaf. Section
3.2
> > has it as a string and says that "The device uses the location 
> > string to identify the physical or logical entity that the 
> > configuration applies
> to".
> > I am not sure how you identify physical location having no 
> > definition of the mapping.
> 
> The sentence just before the quoted one above says:
> 
>   "The format of this string is device- and type-dependent."
> 
> and then the text says:
> 
>   "How a client can learn which types and locations are present on a
>   certain device is outside the scope of this document."
> 
> So the exact procedure is currently left to the vendors, but may be 
> standardized in a future document (if possible...)
> 
> > I saw the examples in Appendix E and it looked more to me as logical 
> > mapping but not physical since it attaches a name to something in 
> > the device but I am not clear how you know what it is physically in 
> > the device. If the name 0-n or n/m are real physical entities, I 
> > think that it should be specified some place.
> > 
> >  
> > 
> >  
> > 
> > Nits/editorial comments:
> > 
> > 1.	In the introduction section maybe add to the first sentence a
> > reference to RFC6244 with some text.
> 
> Ok, this probably makes sense.  I will check w/ the WG and other
documents.
> 
> 
> 
> > 2.	In section 2 are the" must" and "should"  used as described in
> > RFC2119, if yes need capital letters
> 
> Seciton 2 is more of a background, non-normative section.  It lists 
> some of the design objectives.
> 
> > 3.	In section 3.1 "It is optional in the data model,  but if the type
> > represents a physical interface, it is mandatory", suggest having
> > RFC2119 language "It is OPTIONAL in the data model,  but if the type 
> > represents a physical interface, it is MUST be specified"
> 
> I think the first one should not be OPTIONAL, but the second one is
correct.
> So I suggest this:
> 
>   It is defined as being optional in the data model, but if the type
>   represents a physical interface, it MUST be specified.
> 
> 
> /martin
> 


From rjsparks@nostrum.com  Mon Apr 29 06:45:19 2013
Return-Path: <rjsparks@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 EFF1621F9DAC; Mon, 29 Apr 2013 06:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.393
X-Spam-Level: 
X-Spam-Status: No, score=-101.393 tagged_above=-999 required=5 tests=[AWL=1.208, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jErcWkT5NVVT; Mon, 29 Apr 2013 06:45:16 -0700 (PDT)
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 C838C21F9DAD; Mon, 29 Apr 2013 06:45:15 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3TDjB1R056419 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Mon, 29 Apr 2013 08:45:11 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517E796E.6040402@nostrum.com>
Date: Mon, 29 Apr 2013 08:45:18 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: mohamed.boucadair@orange.com
Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Received-SPF: pass (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.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, 29 Apr 2013 13:45:19 -0000

On 4/29/13 12:59 AM, mohamed.boucadair@orange.com wrote:
> Robert,
>
> Ted suggested a wording which is better than the one I proposed. I made the following changes my local copy:
>
> (1)
>
> OLD:
>     When retransmission is required, the relay may decide to correct the
>     content of RECONFIGURE-REQUEST message it issues (e.g., update the
>     Client Identifier list).
>
> NEW:
>     The relay MAY remove clients from the client identifier list in
>     subsequent retransmissions, but MUST NOT add clients to the client
>     identifier list.
>
> (2)
>
> OLD:
>     Furthermore, means to recover state in failure events must be
>     supported, but are not discussed in this document.
>
> NEW:
>     Furthermore, means to recover state in failure events (e.g.,
>     [RFC5460]) must be supported, but are not discussed in this document.
>
> Is this better?
1 is better.

2 is an improvement, I might say "such as" instead of e.g. to even more
strongly avoid someone thinking you are _requiring_ implementation of
RFC5460.  Even then, it's still not clear whether you're trying to say

"Something that doesn't do this is does not conform to this specification"

or

"Something that doesn't do this isn't as good a tool as it can be and 
may create a condition that operators and users will not like much."

You chose not to use MUST in that sentence. Can you make it less likely 
that someone will assume you meant to?
>
> Cheers,
> Med
>
>
>> -----Message d'origine-----
>> De : Bernie Volz (volz) [mailto:volz@cisco.com]
>> Envoyé : samedi 27 avril 2013 06:24
>> À : Robert Sparks; BOUCADAIR Mohamed OLNC/OLN
>> Cc : dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-
>> dhc-triggered-reconfigure@tools.ietf.org
>> Objet : RE: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>> reconfigure-05
>>
>> Robert:
>>
>> The reason to allow this is that otherwise client A will be unnecessarily
>> reconfigured many times. (It is also possible that a client might Renew on
>> its own just as this is happening and thus it can also be removed from the
>> Reconfigure.)
>>
>> I think the text should be cleaned up to indicate that allowing removal of
>> already reconfigured clients is recommended (to prevent unnecessary
>> reconfigures) when retransmitting the Reconfigure-Request.
>>
>> Note that if clients are added, that is not a retransmission but requires a
>> "new" message (new XID).
>>
>> - Bernie
>>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
>> Robert Sparks
>> Sent: Friday, April 26, 2013 12:19 PM
>> To: mohamed.boucadair@orange.com
>> Cc: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-
>> dhc-triggered-reconfigure@tools.ietf.org
>> Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>> reconfigure-05
>>
>> On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
>>> Dear Robert,
>>>
>>> Thank you for the review.
>>> Please see inline.
>>>
>>> Cheers,
>>> Med
>>> ________________________________________
>>> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de
>>> Robert Sparks [rjsparks@nostrum.com] Date d'envoi : vendredi 26 avril
>>> 2013 17:42 À : dhcwg@ietf.org; ietf@ietf.org; General Area Review
>>> Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
>>> Objet : [dhcwg] Gen-art review:
>>> draft-ietf-dhc-triggered-reconfigure-05
>>>
>>> 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><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-dhc-triggered-reconfigure-05
>>> Reviewer:  Robert Sparks
>>> Review Date: April 26, 2013
>>> IETF LC End Date: May 6, 2013
>>> IESG Telechat date: May 16, 2013
>>>
>>> Summary: This draft is on the right track but has open issues, described
>> in
>>>         the review.
>>>
>>> Major issues:
>>>
>>> Overall, this document is solid, but I think there is a bug in section
>> 6.3.
>>> I could be wrong, but If I'm right, this paragraph:
>>>
>>> When retransmission is required, the relay may decide to correct the
>> content of RECONFIGURE-REQUEST message it issues (e.g., update the Client
>> Identifier list).  This decision is local to the relay (e.g., it may be
>> based on observed events such as one or more clients were reconfigured on
>> their own).
>>> introduces a race-condition that could lead to an erroneous state. If a
>> relay's first message included client A, then the retransmission included
>> clients A and B, but that retransmission crosses with a success
>> RECONFIGURE-REPLY to the request that only included client A, the relay
>> will think it succeeded in asking A and B to be reconfigured.
>>> Med: This example does not apply for that text.
>> Really? What text constrains how you change what's in the retransmission?
>>>    In fact, the example should be the other way around. Perhaps, this can
>> be made clearer if we change "(e.g., update the Client Identifier list)" to
>> "(e.g., remove a client from the Client Identifier list)".
>> If I understand you correctly, you need more than just changing a
>> parenthetical e.g.. I think you're saying that you are constraining the
>> message changes to be such that if anything earlier in the retransmission
>> sequence succeeded, the request in the retransmission would also have
>> succeeded. But why do you need that much complexity? Do you have it already
>> with any other request?
>>> Minor issues:
>>>
>>> This sentence:
>>>
>>> Furthermore, means to recover state in failure events must be supported,
>> but are not discussed in this document.
>>> places a requirement on a relay (even though it's not using a 2119 MUST).
>> Is there some other document that defines this requirement that you can
>> reference?
>>> Med: I'm not aware of any; but if there is one we can cite it.
>>>
>>>    If not, the requirement should be discussed in this document.
>> Alternatively, you could change the sentence to talk about the consequences
>> of not having a proprietary means for recovering state.
>>> Med: Will consider that option if you think this is really needed.
>>>
>>> Nits/editorial comments:
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg


From david.black@emc.com  Thu Apr 25 08:22:25 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5E5F21F93B1; Thu, 25 Apr 2013 08:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.847
X-Spam-Level: 
X-Spam-Status: No, score=-99.847 tagged_above=-999 required=5 tests=[AWL=2.752, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eybJpJaj9I7w; Thu, 25 Apr 2013 08:22:16 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3D46121F92C0; Thu, 25 Apr 2013 08:22:10 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3PFLt1U020302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Apr 2013 11:21:56 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 25 Apr 2013 11:21:42 -0400
Received: from mxhub23.corp.emc.com (mxhub23.corp.emc.com [128.222.70.135]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3PFLcj8012731; Thu, 25 Apr 2013 11:21:38 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Thu, 25 Apr 2013 11:21:37 -0400
From: "Black, David" <david.black@emc.com>
To: Russ Housley <housley@vigilsec.com>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "hartmans@painless-security.com" <hartmans@painless-security.com>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Thu, 25 Apr 2013 11:21:36 -0400
Subject: Gen-ART review of draft-ietf-karp-crypto-key-table-07
Thread-Topic: Gen-ART review of draft-ietf-karp-crypto-key-table-07
Thread-Index: Ac5ByJPFxMQV0ntvRsGIbN7yaluElA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 29 Apr 2013 07:06:00 -0700
Cc: "Black, David" <david.black@emc.com>, "<stbryant@cisco.com>" <stbryant@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Apr 2013 15:22:26 -0000

Document: draft-ietf-karp-crypto-key-table-07
Reviewer: David L. Black
Review Date: April 25, 2013
IETF LC End Date: April 29, 2013

Summary: This draft is on the right track, but has open issues
described in the review.

This draft describes a conceptual key database for use by protocols.
It's definitely useful and valuable work, as key management is often
an afterthought in protocol design, even when security functionality
is actively worked on in the design process.

The draft text is in good shape and reads cleanly, but the draft is
short on precision in specifying a number of the fields for the database,
and the IANA registries; most of the open issues are requests for the
level of precision needed for interoperability and reuse of database
implementation across different protocol implementations.

Major issues:=20

(Section 2)

[1] LocalKeyName and PeerKeyName are strings.  What character set?
If Unicode (e.g., UTF-8?), add text on Unicode considerations (e.g.,
normalization).  Finding a Unicode expert will help in getting this
done quickly.  I have similar concerns for other strings, and in
particular, IANA should be told what a "string" is for any registry
field that contains one.

[2] I'm not sure that I understand what a KDF really is from its high
level description in this draft.  At the least, I'm surprised that the
importance of non-invertibility of a KDF is not mentioned - beyond that,
a functional description of inputs and outputs would help, including
a strong recommendation to inject unpredictable nonce material.  This
could be handled by referencing material on what a KDF is that exists
elsewhere.

(Section 4)

[3] It's important that this section cover all the fields involved in
the database lookups in Section 3 whose format may be protocol-specific
(the Direction and various time fields aren't).  Protocol should be
covered by the IANA registry, peers and key names are covered here,
but interface appears to be missing - item (9) covers presence vs.
absence of interface information, but not its format.

--- Lots of issues with the IANA Considerations (Section 8)

(Section 8.1.1)

[5] No field format information for the fields in a registry entry.
IANA should be told what formats to expect/use.

[6] "Protocol Specific Values" is not the same as "ProtocolSpecificInfo"
in section 2; the same name should be used, but whitespace differences
are ok.

[7] Should some sort of formats for Peers and Interfaces be included in
registering a Protocol?  If not, the lookups in section 3 may be
implementation-dependent (strings that work w/one implementation may
not work w/other implementations of the same protocol).  The specification
reference may suffice based on the requirements in section 4
for what has to be in each referenced specification.

(Sections 8.2 and 8.3)

[8] No registry entry content descriptions.  Need to supply information
on what to register and the formats of the elements of a registry entry.

[9] I suggest Expert Review for these registries, not just=20
First Come First Served, so that someone with a security "clue" can
check that the proposed registrations are reasonable.

Minor issues:

[A] Overall - I would like to see a paragraph added on how this database
conceptually relates to the IPsec Peer Authorization Database (PAD) -
see RFC 4301, section 4.4.3.

[B] (Section 2) Where is key size recorded?  Is that an implicit attribute
of Key?

[C] (Section 3) Where does key selection occur?  I would suggest that the
database return all possible keys and let the protocol figure out what to
use.  This is particularly important for inbound traffic for obvious reason=
s.

Nits/editorial comments:

I suggest dividing section 3 into
- 3.1 Outgoing Traffic
- 3.2 Incoming Traffic

idnits 2.12.16 found a truly trivial nit -
  =3D=3D Line 76 has weird spacing: '...strains  where...'

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From hartmans@painless-security.com  Thu Apr 25 09:47:26 2013
Return-Path: <hartmans@painless-security.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2144A21F9638; Thu, 25 Apr 2013 09:47:26 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Cy5XcuK+CL6; Thu, 25 Apr 2013 09:47:25 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 46EA421F94B1; Thu, 25 Apr 2013 09:47:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 8D2722021D; Thu, 25 Apr 2013 12:45:26 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2RIwvD-7_Bfx; Thu, 25 Apr 2013 12:45:25 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 25 Apr 2013 12:45:25 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 8FB744499; Thu, 25 Apr 2013 12:47:22 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
Subject: Re: Gen-ART review of draft-ietf-karp-crypto-key-table-07
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com>
Date: Thu, 25 Apr 2013 12:47:22 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> (David Black's message of "Thu, 25 Apr 2013 11:21:36 -0400")
Message-ID: <tsla9omh811.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
X-Mailman-Approved-At: Mon, 29 Apr 2013 07:06:00 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "<stbryant@cisco.com>" <stbryant@cisco.com>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Apr 2013 16:47:26 -0000

Here are some quick initial responses to your comments.

Thanks much for the review and I'll follow up with more detail in a
while.

>>>>> "Black," == Black, David <david.black@emc.com> writes:


    Black,> Major issues:

    Black,> (Section 2)

    Black,> [1] LocalKeyName and PeerKeyName are strings.  What
    Black,> character set?  If Unicode (e.g., UTF-8?), add text on
    Black,> Unicode considerations (e.g., normalization).  Finding a
    Black,> Unicode expert will help in getting this done quickly.  I
    Black,> have similar concerns for other strings, and in particular,
    Black,> IANA should be told what a "string" is for any registry
    Black,> field that contains one.

They are strings that can be compared using binary comparison.
I agree we need to state that in the draft.
Character set, to the extent it is specified will be specified by the
individual protocol.
In practice the protocol will say  that it's an integer represented as
an ASCII string.

We needed to add the entire complexity of making these fields be strings
    not integers because of some non-IETF protocols that use key names.

I'm reasonably confident I can sell Pete on the concept of a binary
    identifier for this field from an i18n standpoint.

But issues, of length, format, etc are all specified by the protocol
spec.

    Black,> [2] I'm not sure that I understand what a KDF really is from
    Black,> its high level description in this draft.  At the least, I'm
    Black,> surprised that the importance of non-invertibility of a KDF
    Black,> is not mentioned - beyond that, a functional description of
    Black,> inputs and outputs would help, including a strong
    Black,> recommendation to inject unpredictable nonce material.  This
    Black,> could be handled by referencing material on what a KDF is
    Black,> that exists elsewhere.

I'm open to text either proposed on the IETF list from one of the other
authors.
Some protocols have a KDF input some do not.
If they do, it will be drawn from a set of allowable valuable for that
protocol.

    Black,> (Section 4)

    Black,> [3] It's important that this section cover all the fields
    Black,> involved in the database lookups in Section 3 whose format
    Black,> may be protocol-specific (the Direction and various time
    Black,> fields aren't).  Protocol should be covered by the IANA
    Black,> registry, peers and key names are covered here, but
    Black,> interface appears to be missing - item (9) covers presence
    Black,> vs.  absence of interface information, but not its format.

The interface is implementation-specific not protocol specific.  We
mandate that you must be able to tie things to interface. However the
format of an interface is quite specific to the routing platform in
questino.  I don't think there's a way that an IETF document can go into
useful detail on that.  SNMP and Netconf have models of how interfaces
are represented.  If we ever put together a Netconf schema for this
database, we'd specify the interface there.

    Black,> --- Lots of issues with the IANA Considerations (Section 8)

    Black,> (Section 8.1.1)

    Black,> [5] No field format information for the fields in a registry
    Black,> entry.  IANA should be told what formats to expect/use.

Thanks, agreed.


    Black,> [6] "Protocol Specific Values" is not the same as
    Black,> "ProtocolSpecificInfo" in section 2; the same name should be
    Black,> used, but whitespace differences are ok.
Good catch.

    Black,> [7] Should some sort of formats for Peers and Interfaces be
    Black,> included in registering a Protocol?  If not, the lookups in
    Black,> section 3 may be implementation-dependent (strings that work
    Black,> w/one implementation may not work w/other implementations of
    Black,> the same protocol).  The specification reference may suffice
    Black,> based on the requirements in section 4 for what has to be in
    Black,> each referenced specification.

When you register a protocol you need to point to a specification that
    gives details on this sort of thing.

    Black,> (Sections 8.2 and 8.3)

    Black,> [8] No registry entry content descriptions.  Need to supply
    Black,> information on what to register and the formats of the
    Black,> elements of a registry entry.

Thanks.

    Black,> [9] I suggest Expert Review for these registries, not just
    Black,> First Come First Served, so that someone with a security
    Black,> "clue" can check that the proposed registrations are
    Black,> reasonable.

As an individual, I support FCFS, because I think getting expert
    approval for some of the uses that have been proposed for these
    registries will be challenging.



From mohamed.boucadair@orange.com  Fri Apr 26 09:02:47 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9967721F9A5D; Fri, 26 Apr 2013 09:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.948
X-Spam-Level: 
X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hr8Zjd1yoUAg; Fri, 26 Apr 2013 09:02:47 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id C5E9221F9A5B; Fri, 26 Apr 2013 09:02:46 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 8D0832645A1; Fri, 26 Apr 2013 18:02:45 +0200 (CEST)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 69E8535C048; Fri, 26 Apr 2013 18:02:45 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Fri, 26 Apr 2013 18:02:45 +0200
From: <mohamed.boucadair@orange.com>
To: Robert Sparks <rjsparks@nostrum.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>,  "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
Date: Fri, 26 Apr 2013 17:58:38 +0200
Subject: RE : [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Topic: [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: Ac5ClKF6HmqJ6RojQf+w5CK04H/aHwAAkkJb
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr>
References: <517AA051.8080506@nostrum.com>
In-Reply-To: <517AA051.8080506@nostrum.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.25.35414
X-Mailman-Approved-At: Mon, 29 Apr 2013 07:06:00 -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: Fri, 26 Apr 2013 16:02:47 -0000

Dear Robert,

Thank you for the review.
Please see inline.

Cheers,
Med
________________________________________
De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de Robert S=
parks [rjsparks@nostrum.com]
Date d'envoi : vendredi 26 avril 2013 17:42
=C0 : dhcwg@ietf.org; ietf@ietf.org; General Area Review Team; draft-ietf-d=
hc-triggered-reconfigure@tools.ietf.org
Objet : [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05

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><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-dhc-triggered-reconfigure-05
Reviewer:  Robert Sparks
Review Date: April 26, 2013
IETF LC End Date: May 6, 2013
IESG Telechat date: May 16, 2013

Summary: This draft is on the right track but has open issues, described in
      the review.

Major issues:

Overall, this document is solid, but I think there is a bug in section 6.3.
I could be wrong, but If I'm right, this paragraph:

When retransmission is required, the relay may decide to correct the conten=
t of RECONFIGURE-REQUEST message it issues (e.g., update the Client Identif=
ier list).  This decision is local to the relay (e.g., it may be based on o=
bserved events such as one or more clients were reconfigured on their own).

introduces a race-condition that could lead to an erroneous state. If a rel=
ay's first message included client A, then the retransmission included clie=
nts A and B, but that retransmission crosses with a success RECONFIGURE-REP=
LY to the request that only included client A, the relay will think it succ=
eeded in asking A and B to be reconfigured.

Med: This example does not apply for that text. In fact, the example should=
 be the other way around. Perhaps, this can be made clearer if we change "(=
e.g., update the Client Identifier list)" to "(e.g., remove a client from t=
he Client Identifier list)".

Minor issues:

This sentence:

Furthermore, means to recover state in failure events must be supported, bu=
t are not discussed in this document.
places a requirement on a relay (even though it's not using a 2119 MUST). I=
s there some other document that defines this requirement that you can refe=
rence?

Med: I'm not aware of any; but if there is one we can cite it.

 If not, the requirement should be discussed in this document. Alternativel=
y, you could change the sentence to talk about the consequences of not havi=
ng a proprietary means for recovering state.

Med: Will consider that option if you think this is really needed.

Nits/editorial comments:

From volz@cisco.com  Fri Apr 26 21:23:43 2013
Return-Path: <volz@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 1EC5C21F988D; Fri, 26 Apr 2013 21:23:43 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Li2P7zNg8Mf; Fri, 26 Apr 2013 21:23:42 -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 0054F21F988A; Fri, 26 Apr 2013 21:23:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4601; q=dns/txt; s=iport; t=1367036622; x=1368246222; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ocoessXB2ZCDisMmRfUCZNp1/RWstXWXI9AVwd/qPao=; b=Dk6BCwR7kSu4yNeLFxo6KN5wdiXeG959fGc3IjK36MSJ7s8uVRphMlbD ZG8izJPgUjRO1zaEBhS8i1JnRQ44R9lPBD2hyNi1nqxzMHzgpGlMBr+tt 8f4XVWbmKmGrug+pWVs6+s56R41ClYcTPCM8Fi8hUeSJ+4QpTZxoSx9SX U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAN5Re1GtJV2Z/2dsb2JhbABRgwc2vkOBBBZ0gh8BAQEDAQEBAWsLBQcEAgEIDgMDAQEBAQodBycLFAkIAgQBDQUIiAYGDL8UjmExBwaCZ2EDiFqDRYwjhV+KJYMOgig
X-IronPort-AV: E=Sophos;i="4.87,562,1363132800"; d="scan'208";a="203704341"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 27 Apr 2013 04:23:41 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r3R4NeIb030738 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 27 Apr 2013 04:23:40 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.31]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Fri, 26 Apr 2013 23:23:40 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Subject: RE: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Topic: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: AQHOQpnwLrlO/DVOGkmT6MAmTnOo8Zjpd9oA
Date: Sat, 27 Apr 2013 04:23:39 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com>
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com>
In-Reply-To: <517AA910.8030608@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.247.178]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 29 Apr 2013 07:06:00 -0700
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Apr 2013 04:23:43 -0000

Robert:

The reason to allow this is that otherwise client A will be unnecessarily r=
econfigured many times. (It is also possible that a client might Renew on i=
ts own just as this is happening and thus it can also be removed from the R=
econfigure.)

I think the text should be cleaned up to indicate that allowing removal of =
already reconfigured clients is recommended (to prevent unnecessary reconfi=
gures) when retransmitting the Reconfigure-Request.

Note that if clients are added, that is not a retransmission but requires a=
 "new" message (new XID).

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of R=
obert Sparks
Sent: Friday, April 26, 2013 12:19 PM
To: mohamed.boucadair@orange.com
Cc: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-dhc=
-triggered-reconfigure@tools.ietf.org
Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfig=
ure-05

On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
> Dear Robert,
>
> Thank you for the review.
> Please see inline.
>
> Cheers,
> Med
> ________________________________________
> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de=20
> Robert Sparks [rjsparks@nostrum.com] Date d'envoi : vendredi 26 avril=20
> 2013 17:42 =C0 : dhcwg@ietf.org; ietf@ietf.org; General Area Review=20
> Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
> Objet : [dhcwg] Gen-art review:=20
> draft-ietf-dhc-triggered-reconfigure-05
>
> I am the assigned Gen-ART reviewer for this draft. For background on=20
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq><http://wiki.too=
ls.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments=20
> you may receive.
>
> Document: draft-ietf-dhc-triggered-reconfigure-05
> Reviewer:  Robert Sparks
> Review Date: April 26, 2013
> IETF LC End Date: May 6, 2013
> IESG Telechat date: May 16, 2013
>
> Summary: This draft is on the right track but has open issues, described =
in
>        the review.
>
> Major issues:
>
> Overall, this document is solid, but I think there is a bug in section 6.=
3.
> I could be wrong, but If I'm right, this paragraph:
>
> When retransmission is required, the relay may decide to correct the cont=
ent of RECONFIGURE-REQUEST message it issues (e.g., update the Client Ident=
ifier list).  This decision is local to the relay (e.g., it may be based on=
 observed events such as one or more clients were reconfigured on their own=
).
>
> introduces a race-condition that could lead to an erroneous state. If a r=
elay's first message included client A, then the retransmission included cl=
ients A and B, but that retransmission crosses with a success RECONFIGURE-R=
EPLY to the request that only included client A, the relay will think it su=
cceeded in asking A and B to be reconfigured.
>
> Med: This example does not apply for that text.
Really? What text constrains how you change what's in the retransmission?
>   In fact, the example should be the other way around. Perhaps, this can =
be made clearer if we change "(e.g., update the Client Identifier list)" to=
 "(e.g., remove a client from the Client Identifier list)".
If I understand you correctly, you need more than just changing a parenthet=
ical e.g.. I think you're saying that you are constraining the message chan=
ges to be such that if anything earlier in the retransmission sequence succ=
eeded, the request in the retransmission would also have succeeded. But why=
 do you need that much complexity? Do you have it already with any other re=
quest?
>
> Minor issues:
>
> This sentence:
>
> Furthermore, means to recover state in failure events must be supported, =
but are not discussed in this document.
> places a requirement on a relay (even though it's not using a 2119 MUST).=
 Is there some other document that defines this requirement that you can re=
ference?
>
> Med: I'm not aware of any; but if there is one we can cite it.
>
>   If not, the requirement should be discussed in this document. Alternati=
vely, you could change the sentence to talk about the consequences of not h=
aving a proprietary means for recovering state.
>
> Med: Will consider that option if you think this is really needed.
>
> Nits/editorial comments:

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

From mbj@tail-f.com  Sun Apr 28 02:50:15 2013
Return-Path: <mbj@tail-f.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CCE221F980B; Sun, 28 Apr 2013 02:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.046
X-Spam-Level: 
X-Spam-Status: No, score=-4.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SwRmQdrJRmVM; Sun, 28 Apr 2013 02:50:14 -0700 (PDT)
Received: from mail.tail-f.com (de-2007.d.ipeer.se [213.180.74.102]) by ietfa.amsl.com (Postfix) with ESMTP id 9F81821F97FB; Sun, 28 Apr 2013 02:50:14 -0700 (PDT)
Received: from localhost (unknown [192.36.80.8]) by mail.tail-f.com (Postfix) with ESMTPSA id 61F831200AE5; Sun, 28 Apr 2013 11:50:12 +0200 (CEST)
Date: Sun, 28 Apr 2013 11:50:10 +0200 (CEST)
Message-Id: <20130428.115010.513224826.mbj@tail-f.com>
To: ron.even.tlv@gmail.com
Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <019901ce43ea$bbd575a0$338060e0$@gmail.com>
References: <019901ce43ea$bbd575a0$338060e0$@gmail.com>
X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 29 Apr 2013 07:06:00 -0700
Cc: gen-art@ietf.org, draft-ietf-netmod-interfaces-cfg.all@tools.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: Sun, 28 Apr 2013 09:50:15 -0000

Hi,

Thank you for your review.  Comments inline.

"Roni Even" <ron.even.tlv@gmail.com> wrote:
> 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-netmod-interfaces-cfg-10
> 
> Reviewer: Roni Even
> 
> Review Date:2013-4-28
> 
> IETF LC End Date: 2013-5-3
> 
> IESG Telechat date: 2013-5-16
> 
>  
> 
> Summary: This draft is almost ready for publication as Standard track RFC.
> 
>  
> 
>  
> 
> Major issues:
> 
>  
> 
> Minor issues:
> 
>  
> 
> 1.       I had some problem understanding the "location" leaf. Section 3.2
> has it as a string and says that "The device uses the location string to
> identify the physical or logical entity that the configuration applies to".
> I am not sure how you identify physical location having no definition of the
> mapping.

The sentence just before the quoted one above says:

  "The format of this string is device- and type-dependent."

and then the text says:

  "How a client can learn which types and locations are present on a
  certain device is outside the scope of this document."

So the exact procedure is currently left to the vendors, but may be
standardized in a future document (if possible...)

> I saw the examples in Appendix E and it looked more to me as
> logical mapping but not physical since it attaches a name to something in
> the device but I am not clear how you know what it is physically in the
> device. If the name 0-n or n/m are real physical entities, I think that it
> should be specified some place. 
> 
>  
> 
>  
> 
> Nits/editorial comments:
> 
> 1.	In the introduction section maybe add to the first sentence a
> reference to RFC6244 with some text.

Ok, this probably makes sense.  I will check w/ the WG and other
documents.

> 2.	In section 2 are the" must" and "should"  used as described in
> RFC2119, if yes need capital letters

Seciton 2 is more of a background, non-normative section.  It lists
some of the design objectives.

> 3.	In section 3.1 "It is optional in the data model,  but if the type
> represents a physical interface, it is mandatory", suggest having RFC2119
> language "It is OPTIONAL in the data model,  but if the type represents a
> physical interface, it is MUST be specified"

I think the first one should not be OPTIONAL, but the second one is
correct.  So I suggest this:

  It is defined as being optional in the data model, but if the type
  represents a physical interface, it MUST be specified.


/martin

From mbj@tail-f.com  Mon Apr 29 01:25:45 2013
Return-Path: <mbj@tail-f.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E41921F9487; Mon, 29 Apr 2013 01:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.046
X-Spam-Level: 
X-Spam-Status: No, score=-3.046 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WThuJnsDzXnU; Mon, 29 Apr 2013 01:25:44 -0700 (PDT)
Received: from mail.tail-f.com (de-2007.d.ipeer.se [213.180.74.102]) by ietfa.amsl.com (Postfix) with ESMTP id 43C3321F9389; Mon, 29 Apr 2013 01:25:43 -0700 (PDT)
Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id 6A8A212008D2; Mon, 29 Apr 2013 10:25:42 +0200 (CEST)
Date: Mon, 29 Apr 2013 10:25:42 +0200 (CEST)
Message-Id: <20130429.102542.1993240684524912340.mbj@tail-f.com>
To: ron.even.tlv@gmail.com
Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <01ba01ce440c$408d4720$c1a7d560$@gmail.com>
References: <019901ce43ea$bbd575a0$338060e0$@gmail.com> <20130428.115010.513224826.mbj@tail-f.com> <01ba01ce440c$408d4720$c1a7d560$@gmail.com>
X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 29 Apr 2013 07:06:00 -0700
Cc: gen-art@ietf.org, draft-ietf-netmod-interfaces-cfg.all@tools.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, 29 Apr 2013 08:25:45 -0000

Hi,

"Roni Even" <ron.even.tlv@gmail.com> wrote:
> Martin,
> Thanks for the response. I am OK with your responses to the nits.
> 
> As for the comment on location I think I understand but what got me thinking
> was the examples.
> In E.1 
> 
> "An operator can configure a new interface by sending an <edit-config>
>    containing:
> 
>      <interface nc:operation="create">
>        <name>fastethernet-1/0</name>
>      </interface>
> 
>    When the server processes this request, it will set the leaf "type"
>    to "ethernetCsmacd" and "location" to "1/0".  Thus, if the client
>    performs a <get-config> right after the <edit-config> above, it will
>    get:
> 
>      <interface>
>        <name>fastethernet-1/0</name>
>        <type>ethernetCsmacd</type>
>        <location>1/0</location>
>      </interface>"
> 
> I can see how the linkage between the location and name is done. I am not
> sure how the operator knows from the response what is the physical location
> without knowing the device type and manufacturer but at least the linkage is
> there and this is why I thought of it more as a logical device and not
> physical one.

Ok.  Since this is an example of a configuration of a physical
interface, it is assumed that the operator somehow knows which
physical port is being reconfigured -- somehow the operator must be
able to know what the port where the new cable was inserted is called
in the config.

But it makes sense to be more clear about this.  How about this
change:


OLD:

  The implementation restricts the names of the interfaces to one of
  "fastethernet-N/M" or "gigabitethernet-N/M".  The "location" of an
  interface is a string on the form "N/M".  The implementation
  auto-initializes the values for "type" and "location" based on the
  interface name.

NEW:

  The implementation restricts the names of the interfaces to one of
  "fastethernet-N/M" or "gigabitethernet-N/M".  The "location" of an
  interface is a string on the form "N/M".  It is assumed that the
  operator is aware of this naming scheme.  The implementation
  auto-initializes the values for "type" and "location" based on the
  interface name.

> When looking at E2.2 example

(ditto for this example.)


/martin



>   " An operator can configure a new interface by sending an <edit-config>
>    containing:
> 
>      <interface nc:operation="create">
>        <name>acme-interface</name>
>        <type>ethernetCsmacd</type>
>        <location>1/0</location>
>      </interface>"
> 
> Here the operator need to know the device to configure a specific interface
> and know how many interface exist and how they are named. So you assume that
> for this case this is known to the configuration.
> 
> Roni
> 
> 
> 
> 
> -----Original Message-----
> From: Martin Bjorklund [mailto:mbj@tail-f.com] 
> Sent: 28 April, 2013 12:50 PM
> To: ron.even.tlv@gmail.com
> Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org; ietf@ietf.org;
> gen-art@ietf.org
> Subject: Re: Gen-ART LC review of draft-ietf-netmod-interfaces-cfg-10
> 
> Hi,
> 
> Thank you for your review.  Comments inline.
> 
> "Roni Even" <ron.even.tlv@gmail.com> wrote:
> > 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-netmod-interfaces-cfg-10
> > 
> > Reviewer: Roni Even
> > 
> > Review Date:2013-4-28
> > 
> > IETF LC End Date: 2013-5-3
> > 
> > IESG Telechat date: 2013-5-16
> > 
> >  
> > 
> > Summary: This draft is almost ready for publication as Standard track RFC.
> > 
> >  
> > 
> >  
> > 
> > Major issues:
> > 
> >  
> > 
> > Minor issues:
> > 
> >  
> > 
> > 1.       I had some problem understanding the "location" leaf. Section 3.2
> > has it as a string and says that "The device uses the location string 
> > to identify the physical or logical entity that the configuration applies
> to".
> > I am not sure how you identify physical location having no definition 
> > of the mapping.
> 
> The sentence just before the quoted one above says:
> 
>   "The format of this string is device- and type-dependent."
> 
> and then the text says:
> 
>   "How a client can learn which types and locations are present on a
>   certain device is outside the scope of this document."
> 
> So the exact procedure is currently left to the vendors, but may be
> standardized in a future document (if possible...)
> 
> > I saw the examples in Appendix E and it looked more to me as logical 
> > mapping but not physical since it attaches a name to something in the 
> > device but I am not clear how you know what it is physically in the 
> > device. If the name 0-n or n/m are real physical entities, I think 
> > that it should be specified some place.
> > 
> >  
> > 
> >  
> > 
> > Nits/editorial comments:
> > 
> > 1.	In the introduction section maybe add to the first sentence a
> > reference to RFC6244 with some text.
> 
> Ok, this probably makes sense.  I will check w/ the WG and other documents.
> 
> 
> 
> > 2.	In section 2 are the" must" and "should"  used as described in
> > RFC2119, if yes need capital letters
> 
> Seciton 2 is more of a background, non-normative section.  It lists some of
> the design objectives.
> 
> > 3.	In section 3.1 "It is optional in the data model,  but if the type
> > represents a physical interface, it is mandatory", suggest having 
> > RFC2119 language "It is OPTIONAL in the data model,  but if the type 
> > represents a physical interface, it is MUST be specified"
> 
> I think the first one should not be OPTIONAL, but the second one is correct.
> So I suggest this:
> 
>   It is defined as being optional in the data model, but if the type
>   represents a physical interface, it MUST be specified.
> 
> 
> /martin
> 

From david.black@emc.com  Thu Apr 25 11:50:01 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A70AE21F9647; Thu, 25 Apr 2013 11:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.24
X-Spam-Level: 
X-Spam-Status: No, score=-100.24 tagged_above=-999 required=5 tests=[AWL=2.359, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wqiw+LVwUHSc; Thu, 25 Apr 2013 11:50:00 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 460C221F9644; Thu, 25 Apr 2013 11:49:59 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3PInX2v020434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Apr 2013 14:49:33 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Thu, 25 Apr 2013 14:49:21 -0400
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r3PInKnE019433; Thu, 25 Apr 2013 14:49:20 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Thu, 25 Apr 2013 14:49:19 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 25 Apr 2013 14:49:17 -0400
Subject: RE: Gen-ART review of draft-ietf-karp-crypto-key-table-07
Thread-Topic: Gen-ART review of draft-ietf-karp-crypto-key-table-07
Thread-Index: Ac5B1KJBGTDzkf65QPacxtWgnCr6KgADLoOg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> <tsla9omh811.fsf@mit.edu>
In-Reply-To: <tsla9omh811.fsf@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-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 29 Apr 2013 07:06:00 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "<stbryant@cisco.com>" <stbryant@cisco.com>, "Black, David" <david.black@emc.com>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Apr 2013 18:50:01 -0000

Thanks for the quick response - most of your message looks reasonable to me=
.

I have a few additional comments.

[1] Character set for key names, etc.

> They are strings that can be compared using binary comparison.
> I agree we need to state that in the draft.

That's certainly a reasonable goal, and there are plenty of examples of
protocols that do that.  OTOH, when the character set is Unicode, generatin=
g
strings for which that binary comparison for equality works as expected has
a number of subtleties when the strings are input by humans.  Pete Resnick
and yours truly are among the people familiar with the "dragons" that lurk
here (and the precis WG is grappling with).

> We needed to add the entire complexity of making these fields be strings
>     not integers because of some non-IETF protocols that use key names.
>=20
> I'm reasonably confident I can sell Pete on the concept of a binary
>     identifier for this field from an i18n standpoint.

I have no problem with the field being a binary identifier, but I think
implementers should be put on notice that binary comparison of human input
Unicode strings doesn't work as expected unless some things are done to
make it work (this used to be known as string preparation).  A warning
to that effect, perhaps citing a reference for details on what can go awry,
accompanied by making the protocol spec responsible for getting this right
ought to suffice.

[3] Protocol responsibility to specify interface format

> We
> mandate that you must be able to tie things to interface. However the
> format of an interface is quite specific to the routing platform in
> question.

Ok, I suggest explaining that as part of a statement that a protocol cannot
in general be expected to specify interface formats that apply across all
implementations due to implementation diversity.

[7] Additional format information in registry

>     Black,> [7] Should some sort of formats for Peers and Interfaces be
>     Black,> included in registering a Protocol?  If not, the lookups in
>     Black,> section 3 may be implementation-dependent (strings that work
>     Black,> w/one implementation may not work w/other implementations of
>     Black,> the same protocol).  The specification reference may suffice
>     Black,> based on the requirements in section 4 for what has to be in
>     Black,> each referenced specification.
>=20
> When you register a protocol you need to point to a specification that
>     gives details on this sort of thing.

That makes sense, and section 4's requirements on the specifications=20
cover this area, but I thought I'd ask.

[9] Registry policy

> As an individual, I support FCFS, because I think getting expert
>     approval for some of the uses that have been proposed for these
>     registries will be challenging.

The two registries involved are for KDFs and cryptographic algorithm identi=
fiers.

This feels like something that the security area ought to weigh in on, as i=
t
looks like it includes the "vanity crypto" discussion tarpit ;-).  At a min=
imum,
I would think that there ought to be some means of prohibiting registration
of a crypto algorithm like ROT13 (http://en.wikipedia.org/wiki/ROT13).

Thanks,
--David

> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> Sent: Thursday, April 25, 2013 12:47 PM
> To: Black, David
> Cc: Russ Housley; tim.polk@nist.gov; zhangdacheng@huawei.com; gen-
> art@ietf.org; karp@ietf.org; ietf@ietf.org; <stbryant@cisco.com>
> Subject: Re: Gen-ART review of draft-ietf-karp-crypto-key-table-07
>=20
> Here are some quick initial responses to your comments.
>=20
> Thanks much for the review and I'll follow up with more detail in a
> while.
>=20
> >>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>=20
>     Black,> Major issues:
>=20
>     Black,> (Section 2)
>=20
>     Black,> [1] LocalKeyName and PeerKeyName are strings.  What
>     Black,> character set?  If Unicode (e.g., UTF-8?), add text on
>     Black,> Unicode considerations (e.g., normalization).  Finding a
>     Black,> Unicode expert will help in getting this done quickly.  I
>     Black,> have similar concerns for other strings, and in particular,
>     Black,> IANA should be told what a "string" is for any registry
>     Black,> field that contains one.
>=20
> They are strings that can be compared using binary comparison.
> I agree we need to state that in the draft.
> Character set, to the extent it is specified will be specified by the
> individual protocol.
> In practice the protocol will say  that it's an integer represented as
> an ASCII string.
>=20
> We needed to add the entire complexity of making these fields be strings
>     not integers because of some non-IETF protocols that use key names.
>=20
> I'm reasonably confident I can sell Pete on the concept of a binary
>     identifier for this field from an i18n standpoint.
>=20
> But issues, of length, format, etc are all specified by the protocol
> spec.
>=20
>     Black,> [2] I'm not sure that I understand what a KDF really is from
>     Black,> its high level description in this draft.  At the least, I'm
>     Black,> surprised that the importance of non-invertibility of a KDF
>     Black,> is not mentioned - beyond that, a functional description of
>     Black,> inputs and outputs would help, including a strong
>     Black,> recommendation to inject unpredictable nonce material.  This
>     Black,> could be handled by referencing material on what a KDF is
>     Black,> that exists elsewhere.
>=20
> I'm open to text either proposed on the IETF list from one of the other
> authors.
> Some protocols have a KDF input some do not.
> If they do, it will be drawn from a set of allowable valuable for that
> protocol.
>=20
>     Black,> (Section 4)
>=20
>     Black,> [3] It's important that this section cover all the fields
>     Black,> involved in the database lookups in Section 3 whose format
>     Black,> may be protocol-specific (the Direction and various time
>     Black,> fields aren't).  Protocol should be covered by the IANA
>     Black,> registry, peers and key names are covered here, but
>     Black,> interface appears to be missing - item (9) covers presence
>     Black,> vs.  absence of interface information, but not its format.
>=20
> The interface is implementation-specific not protocol specific.  We
> mandate that you must be able to tie things to interface. However the
> format of an interface is quite specific to the routing platform in
> questino.  I don't think there's a way that an IETF document can go into
> useful detail on that.  SNMP and Netconf have models of how interfaces
> are represented.  If we ever put together a Netconf schema for this
> database, we'd specify the interface there.
>=20
>     Black,> --- Lots of issues with the IANA Considerations (Section 8)
>=20
>     Black,> (Section 8.1.1)
>=20
>     Black,> [5] No field format information for the fields in a registry
>     Black,> entry.  IANA should be told what formats to expect/use.
>=20
> Thanks, agreed.
>=20
>=20
>     Black,> [6] "Protocol Specific Values" is not the same as
>     Black,> "ProtocolSpecificInfo" in section 2; the same name should be
>     Black,> used, but whitespace differences are ok.
> Good catch.
>=20
>     Black,> [7] Should some sort of formats for Peers and Interfaces be
>     Black,> included in registering a Protocol?  If not, the lookups in
>     Black,> section 3 may be implementation-dependent (strings that work
>     Black,> w/one implementation may not work w/other implementations of
>     Black,> the same protocol).  The specification reference may suffice
>     Black,> based on the requirements in section 4 for what has to be in
>     Black,> each referenced specification.
>=20
> When you register a protocol you need to point to a specification that
>     gives details on this sort of thing.
>=20
>     Black,> (Sections 8.2 and 8.3)
>=20
>     Black,> [8] No registry entry content descriptions.  Need to supply
>     Black,> information on what to register and the formats of the
>     Black,> elements of a registry entry.
>=20
> Thanks.
>=20
>     Black,> [9] I suggest Expert Review for these registries, not just
>     Black,> First Come First Served, so that someone with a security
>     Black,> "clue" can check that the proposed registrations are
>     Black,> reasonable.
>=20
> As an individual, I support FCFS, because I think getting expert
>     approval for some of the uses that have been proposed for these
>     registries will be challenging.
>=20
>=20


From mohamed.boucadair@orange.com  Sun Apr 28 22:59:57 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C74221F9D31; Sun, 28 Apr 2013 22:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mbd+JyNPPzUc; Sun, 28 Apr 2013 22:59:56 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 768FB21F9D2F; Sun, 28 Apr 2013 22:59:53 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 26CC222C2FA; Mon, 29 Apr 2013 07:59:52 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id ED23C35C07A; Mon, 29 Apr 2013 07:59:51 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Mon, 29 Apr 2013 07:59:51 +0200
From: <mohamed.boucadair@orange.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Robert Sparks <rjsparks@nostrum.com>
Date: Mon, 29 Apr 2013 07:59:50 +0200
Subject: RE: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Topic: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: AQHOQpnwLrlO/DVOGkmT6MAmTnOo8Zjpd9oAgAM8HYA=
Message-ID: <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr>
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.4.28.223919
X-Mailman-Approved-At: Mon, 29 Apr 2013 07:06:00 -0700
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 05:59:57 -0000

Robert,

Ted suggested a wording which is better than the one I proposed. I made the=
 following changes my local copy:

(1)

OLD:
   When retransmission is required, the relay may decide to correct the
   content of RECONFIGURE-REQUEST message it issues (e.g., update the
   Client Identifier list).

NEW:
   The relay MAY remove clients from the client identifier list in
   subsequent retransmissions, but MUST NOT add clients to the client
   identifier list.

(2)

OLD:
   Furthermore, means to recover state in failure events must be
   supported, but are not discussed in this document.

NEW:
   Furthermore, means to recover state in failure events (e.g.,
   [RFC5460]) must be supported, but are not discussed in this document.

Is this better?

Cheers,
Med


>-----Message d'origine-----
>De=A0: Bernie Volz (volz) [mailto:volz@cisco.com]
>Envoy=E9=A0: samedi 27 avril 2013 06:24
>=C0=A0: Robert Sparks; BOUCADAIR Mohamed OLNC/OLN
>Cc=A0: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf=
-
>dhc-triggered-reconfigure@tools.ietf.org
>Objet=A0: RE: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>reconfigure-05
>
>Robert:
>
>The reason to allow this is that otherwise client A will be unnecessarily
>reconfigured many times. (It is also possible that a client might Renew on
>its own just as this is happening and thus it can also be removed from the
>Reconfigure.)
>
>I think the text should be cleaned up to indicate that allowing removal of
>already reconfigured clients is recommended (to prevent unnecessary
>reconfigures) when retransmitting the Reconfigure-Request.
>
>Note that if clients are added, that is not a retransmission but requires =
a
>"new" message (new XID).
>
>- Bernie
>
>-----Original Message-----
>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
>Robert Sparks
>Sent: Friday, April 26, 2013 12:19 PM
>To: mohamed.boucadair@orange.com
>Cc: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-
>dhc-triggered-reconfigure@tools.ietf.org
>Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>reconfigure-05
>
>On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
>> Dear Robert,
>>
>> Thank you for the review.
>> Please see inline.
>>
>> Cheers,
>> Med
>> ________________________________________
>> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de
>> Robert Sparks [rjsparks@nostrum.com] Date d'envoi : vendredi 26 avril
>> 2013 17:42 =C0 : dhcwg@ietf.org; ietf@ietf.org; General Area Review
>> Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
>> Objet : [dhcwg] Gen-art review:
>> draft-ietf-dhc-triggered-reconfigure-05
>>
>> 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><http://wiki.tool=
s
>.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-dhc-triggered-reconfigure-05
>> Reviewer:  Robert Sparks
>> Review Date: April 26, 2013
>> IETF LC End Date: May 6, 2013
>> IESG Telechat date: May 16, 2013
>>
>> Summary: This draft is on the right track but has open issues, described
>in
>>        the review.
>>
>> Major issues:
>>
>> Overall, this document is solid, but I think there is a bug in section
>6.3.
>> I could be wrong, but If I'm right, this paragraph:
>>
>> When retransmission is required, the relay may decide to correct the
>content of RECONFIGURE-REQUEST message it issues (e.g., update the Client
>Identifier list).  This decision is local to the relay (e.g., it may be
>based on observed events such as one or more clients were reconfigured on
>their own).
>>
>> introduces a race-condition that could lead to an erroneous state. If a
>relay's first message included client A, then the retransmission included
>clients A and B, but that retransmission crosses with a success
>RECONFIGURE-REPLY to the request that only included client A, the relay
>will think it succeeded in asking A and B to be reconfigured.
>>
>> Med: This example does not apply for that text.
>Really? What text constrains how you change what's in the retransmission?
>>   In fact, the example should be the other way around. Perhaps, this can
>be made clearer if we change "(e.g., update the Client Identifier list)" t=
o
>"(e.g., remove a client from the Client Identifier list)".
>If I understand you correctly, you need more than just changing a
>parenthetical e.g.. I think you're saying that you are constraining the
>message changes to be such that if anything earlier in the retransmission
>sequence succeeded, the request in the retransmission would also have
>succeeded. But why do you need that much complexity? Do you have it alread=
y
>with any other request?
>>
>> Minor issues:
>>
>> This sentence:
>>
>> Furthermore, means to recover state in failure events must be supported,
>but are not discussed in this document.
>> places a requirement on a relay (even though it's not using a 2119 MUST)=
.
>Is there some other document that defines this requirement that you can
>reference?
>>
>> Med: I'm not aware of any; but if there is one we can cite it.
>>
>>   If not, the requirement should be discussed in this document.
>Alternatively, you could change the sentence to talk about the consequence=
s
>of not having a proprietary means for recovering state.
>>
>> Med: Will consider that option if you think this is really needed.
>>
>> Nits/editorial comments:
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg

From dhc@dcrocker.net  Mon Apr 29 07:09:07 2013
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 27A3321F9402 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 07:09:07 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M3for7SH+t4U for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 07:09:06 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9749921F930A for <ietf@ietf.org>; Mon, 29 Apr 2013 07:09:05 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3TE90IW028339 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Apr 2013 07:09:04 -0700
Message-ID: <517E7EFC.4010706@dcrocker.net>
Date: Mon, 29 Apr 2013 07:09:00 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: stbryant@cisco.com
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.com> <517E0BAF.2000207@dcrocker.net> <517E3A29.7080603@cisco.com>
In-Reply-To: <517E3A29.7080603@cisco.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.66]); Mon, 29 Apr 2013 07:09:04 -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: Mon, 29 Apr 2013 14:09:07 -0000

On 4/29/2013 2:15 AM, Stewart Bryant wrote:
> On 29/04/2013 06:57, Dave Crocker wrote:
>> Exactly.  Complicated processes, needing high quality data that gets
>> complicated analysis, that we aren't well-enough trained to do well
>> and aren't going to be doing.
>>
>>
> Dave
>
> Of all the social mixes  you would anticipate the IETF to be in the
> likely to do it, likely to do it correctly quadrant.


If by 'it', you mean statistical analysis of human behavior, no.  I'd 
expect our group methodology to be exactly as poor at it as we are...

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From Ted.Lemon@nominum.com  Mon Apr 29 07:37:45 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 742D221F9E4C; Mon, 29 Apr 2013 07:37:45 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nH7-+zp8Gqi1; Mon, 29 Apr 2013 07:37:44 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 66C6521F9E4B; Mon, 29 Apr 2013 07:37:44 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUX6FuHVrwVi3MoijUi9NKPyAb/1Bzlfv@postini.com; Mon, 29 Apr 2013 07:37:44 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0DE851B813F; Mon, 29 Apr 2013 07:37:44 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 017B2190061; Mon, 29 Apr 2013 07:37:44 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 29 Apr 2013 07:37:44 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Black, David" <david.black@emc.com>
Subject: Re: Gen-ART review of draft-ietf-karp-crypto-key-table-07
Thread-Topic: Gen-ART review of draft-ietf-karp-crypto-key-table-07
Thread-Index: Ac5ByJPFxMQV0ntvRsGIbN7yaluElADGrB/i//p5/YCABgMJAA==
Date: Mon, 29 Apr 2013 14:37:43 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751666F9@mbx-01.win.nominum.com>
References: <8D3D17ACE214DC429325B2B98F3AE71293F3BD27@MX15A.corp.emc.com> <tsla9omh811.fsf@mit.edu> <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71293F3BDB0@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EA362B2EEBE8244F8BD734E09226EE7D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "zhangdacheng@huawei.com" <zhangdacheng@huawei.com>, "<stbryant@cisco.com>" <stbryant@cisco.com>, Sam Hartman <hartmans-ietf@mit.edu>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 14:37:45 -0000

On Apr 25, 2013, at 2:49 PM, "Black, David" <david.black@emc.com> wrote:
> I have no problem with the field being a binary identifier, but I think
> implementers should be put on notice that binary comparison of human inpu=
t
> Unicode strings doesn't work as expected unless some things are done to
> make it work (this used to be known as string preparation).

+1.


From volz@cisco.com  Mon Apr 29 07:18:36 2013
Return-Path: <volz@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 85A3121F9D80; Mon, 29 Apr 2013 07:18:36 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id donM72n4hjJv; Mon, 29 Apr 2013 07:18:35 -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 3C0A921F9D8C; Mon, 29 Apr 2013 07:18:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8804; q=dns/txt; s=iport; t=1367245115; x=1368454715; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=79UA9FLZu0g3FxXvLo4Lkql6GqmmOh0mD/nUOcM1nj8=; b=WofcX8Csqxt7HQophfHOch7vXGgkL+Fi4pD18TI3tOkhKCrl/nEHZSBB 7ykO45ILrIviQE5OM5vpv+BfCcnuZeCcr87wqChEIFN1agthDP7zZR+CN LL+X7b4pq9WWkydEQjz854u4GYqH2l0WaX/rM9geXmMfXdg5VOGwJXDcv U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFALCAflGtJXG8/2dsb2JhbABTgwc2vkCBAxZ0gh8BAQEEAQEBawsMBAIBCA4DAwEBAQEKHQcnCxQJCAIEAQ0FCBOHewy7RI1uezEHBoJoYQOIWoNFhzCEdYVfiiWDEYFrPQ
X-IronPort-AV: E=Sophos;i="4.87,574,1363132800"; d="scan'208";a="204307575"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 29 Apr 2013 14:18:34 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3TEIY57002491 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 29 Apr 2013 14:18:34 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.31]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Mon, 29 Apr 2013 09:18:34 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Subject: RE: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Topic: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: AQHORN/GDK4q6qizh0K41HkFQ0/z/ZjtOjmg
Date: Mon, 29 Apr 2013 14:18:33 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1851F76A@xmb-rcd-x04.cisco.com>
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr> <517E796E.6040402@nostrum.com>
In-Reply-To: <517E796E.6040402@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.247.178]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 29 Apr 2013 08:49:44 -0700
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 14:18:36 -0000

FYI - Stable storage or some kind of redundancy solution may be another way=
 to recover state. So, I don't think there is a hard requirement for RFC 54=
60.

I don't think there is a strong reason to avoid e.g., it is "for example" s=
o it is only one of many possible. And "such as" is basically saying the sa=
me thing.

---

But then we come to why this is even important ... The original text was:

   This setup assumes the relay has a record of the client, so that it
   has enough information to send the Reconfigure-Request message to the
   server.  How the state is recorded in the relay is out of scope.
   Furthermore, means to recover state in failure events must be
   supported, but are not discussed in this document.

I'm a bit skeptical why this draft even brings the 'recover state' up. Yes,=
 the relay does need to record the client in order to initiate a Reconfigur=
e-Request. But I think the sentence "Furthermore, means to recover state in=
 failure events must be supported, but are not discussed in this document."=
 is not needed. Sure, if the relay has no way of recovering this state, tra=
ffic to/from clients will likely not work and certainly if the relay is rec=
onfigured, it will be unable to generate a Reconfigure-Request. But I don't=
 really see this draft needing this requirement. Reconfigure-request could =
still work until the state is lost. And if the state is lost, there is a lo=
t more than is potentially broken.

But I don't really see this as a big issue and the "must" is the lower-case=
 variant anyway.

- Bernie

-----Original Message-----
From: Robert Sparks [mailto:rjsparks@nostrum.com]=20
Sent: Monday, April 29, 2013 9:45 AM
To: mohamed.boucadair@orange.com
Cc: Bernie Volz (volz); dhcwg@ietf.org; General Area Review Team; ietf@ietf=
.org; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfig=
ure-05

On 4/29/13 12:59 AM, mohamed.boucadair@orange.com wrote:
> Robert,
>
> Ted suggested a wording which is better than the one I proposed. I made t=
he following changes my local copy:
>
> (1)
>
> OLD:
>     When retransmission is required, the relay may decide to correct the
>     content of RECONFIGURE-REQUEST message it issues (e.g., update the
>     Client Identifier list).
>
> NEW:
>     The relay MAY remove clients from the client identifier list in
>     subsequent retransmissions, but MUST NOT add clients to the client
>     identifier list.
>
> (2)
>
> OLD:
>     Furthermore, means to recover state in failure events must be
>     supported, but are not discussed in this document.
>
> NEW:
>     Furthermore, means to recover state in failure events (e.g.,
>     [RFC5460]) must be supported, but are not discussed in this document.
>
> Is this better?
1 is better.

2 is an improvement, I might say "such as" instead of e.g. to even more str=
ongly avoid someone thinking you are _requiring_ implementation of RFC5460.=
  Even then, it's still not clear whether you're trying to say

"Something that doesn't do this is does not conform to this specification"

or

"Something that doesn't do this isn't as good a tool as it can be and may c=
reate a condition that operators and users will not like much."

You chose not to use MUST in that sentence. Can you make it less likely tha=
t someone will assume you meant to?
>
> Cheers,
> Med
>
>
>> -----Message d'origine-----
>> De : Bernie Volz (volz) [mailto:volz@cisco.com] Envoy=E9 : samedi 27=20
>> avril 2013 06:24 =C0 : Robert Sparks; BOUCADAIR Mohamed OLNC/OLN Cc :=20
>> dhcwg@ietf.org; General Area Review Team; ietf@ietf.org; draft-ietf-=20
>> dhc-triggered-reconfigure@tools.ietf.org
>> Objet : RE: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>> reconfigure-05
>>
>> Robert:
>>
>> The reason to allow this is that otherwise client A will be=20
>> unnecessarily reconfigured many times. (It is also possible that a=20
>> client might Renew on its own just as this is happening and thus it=20
>> can also be removed from the
>> Reconfigure.)
>>
>> I think the text should be cleaned up to indicate that allowing=20
>> removal of already reconfigured clients is recommended (to prevent=20
>> unnecessary
>> reconfigures) when retransmitting the Reconfigure-Request.
>>
>> Note that if clients are added, that is not a retransmission but=20
>> requires a "new" message (new XID).
>>
>> - Bernie
>>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On=20
>> Behalf Of Robert Sparks
>> Sent: Friday, April 26, 2013 12:19 PM
>> To: mohamed.boucadair@orange.com
>> Cc: dhcwg@ietf.org; General Area Review Team; ietf@ietf.org;=20
>> draft-ietf- dhc-triggered-reconfigure@tools.ietf.org
>> Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-
>> reconfigure-05
>>
>> On 4/26/13 10:58 AM, mohamed.boucadair@orange.com wrote:
>>> Dear Robert,
>>>
>>> Thank you for the review.
>>> Please see inline.
>>>
>>> Cheers,
>>> Med
>>> ________________________________________
>>> De : dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] de la part de=20
>>> Robert Sparks [rjsparks@nostrum.com] Date d'envoi : vendredi 26=20
>>> avril
>>> 2013 17:42 =C0 : dhcwg@ietf.org; ietf@ietf.org; General Area Review=20
>>> Team; draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
>>> Objet : [dhcwg] Gen-art review:
>>> draft-ietf-dhc-triggered-reconfigure-05
>>>
>>> I am the assigned Gen-ART reviewer for this draft. For background on=20
>>> Gen-ART, please see the FAQ at
>>>
>>>
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq><http://wiki
>> .tools .ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>> Please resolve these comments along with any other Last Call=20
>>> comments you may receive.
>>>
>>> Document: draft-ietf-dhc-triggered-reconfigure-05
>>> Reviewer:  Robert Sparks
>>> Review Date: April 26, 2013
>>> IETF LC End Date: May 6, 2013
>>> IESG Telechat date: May 16, 2013
>>>
>>> Summary: This draft is on the right track but has open issues,=20
>>> described
>> in
>>>         the review.
>>>
>>> Major issues:
>>>
>>> Overall, this document is solid, but I think there is a bug in=20
>>> section
>> 6.3.
>>> I could be wrong, but If I'm right, this paragraph:
>>>
>>> When retransmission is required, the relay may decide to correct the
>> content of RECONFIGURE-REQUEST message it issues (e.g., update the=20
>> Client Identifier list).  This decision is local to the relay (e.g.,=20
>> it may be based on observed events such as one or more clients were=20
>> reconfigured on their own).
>>> introduces a race-condition that could lead to an erroneous state.=20
>>> If a
>> relay's first message included client A, then the retransmission=20
>> included clients A and B, but that retransmission crosses with a=20
>> success RECONFIGURE-REPLY to the request that only included client A,=20
>> the relay will think it succeeded in asking A and B to be reconfigured.
>>> Med: This example does not apply for that text.
>> Really? What text constrains how you change what's in the retransmission=
?
>>>    In fact, the example should be the other way around. Perhaps,=20
>>> this can
>> be made clearer if we change "(e.g., update the Client Identifier=20
>> list)" to "(e.g., remove a client from the Client Identifier list)".
>> If I understand you correctly, you need more than just changing a=20
>> parenthetical e.g.. I think you're saying that you are constraining=20
>> the message changes to be such that if anything earlier in the=20
>> retransmission sequence succeeded, the request in the retransmission=20
>> would also have succeeded. But why do you need that much complexity?=20
>> Do you have it already with any other request?
>>> Minor issues:
>>>
>>> This sentence:
>>>
>>> Furthermore, means to recover state in failure events must be=20
>>> supported,
>> but are not discussed in this document.
>>> places a requirement on a relay (even though it's not using a 2119 MUST=
).
>> Is there some other document that defines this requirement that you=20
>> can reference?
>>> Med: I'm not aware of any; but if there is one we can cite it.
>>>
>>>    If not, the requirement should be discussed in this document.
>> Alternatively, you could change the sentence to talk about the=20
>> consequences of not having a proprietary means for recovering state.
>>> Med: Will consider that option if you think this is really needed.
>>>
>>> Nits/editorial comments:
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg


From Ted.Lemon@nominum.com  Mon Apr 29 09:38:06 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3735621F9E07; Mon, 29 Apr 2013 09:38:06 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VDlHR718wayO; Mon, 29 Apr 2013 09:38:05 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 0CEDA21F9E01; Mon, 29 Apr 2013 09:38:05 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUX6h7C8MLrDsUSNolbSkLQEXAJXa3/MR@postini.com; Mon, 29 Apr 2013 09:38:05 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 8A57D1B815E; Mon, 29 Apr 2013 09:38:04 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7BE84190061; Mon, 29 Apr 2013 09:38:04 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 29 Apr 2013 09:38:04 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Topic: [dhcwg] RE : Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: AQHORORy+jlCE9D1eEC77pV047+J55jt22OA
Date: Mon, 29 Apr 2013 16:38:03 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775166969@mbx-01.win.nominum.com>
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36EC9D2A2BD@PUEXCB1B.nanterre.francetelecom.fr> <517AA910.8030608@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851CFD5@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EC9B49B02@PUEXCB1B.nanterre.francetelecom.fr> <517E796E.6040402@nostrum.com> <489D13FBFA9B3E41812EA89F188F018E1851F76A@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1851F76A@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <0EEDAECDCBFCE341849C5B85D1C939EA@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.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, 29 Apr 2013 16:38:06 -0000

On Apr 29, 2013, at 10:18 AM, "Bernie Volz (volz)" <volz@cisco.com> wrote:
> But I don't really see this as a big issue and the "must" is the lower-ca=
se variant anyway.

There's a big debate about whether this makes any difference.   It's genera=
lly thought to be better not to say must if you don't mean MUST.

I think the idea of just saying e.g. is the right thing, and stable storage=
 and bulk leasequery would be two really great examples to use.


From john-ietf@jck.com  Mon Apr 29 09:38:59 2013
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 ABBEF21F9E50 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 09:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.185
X-Spam-Level: 
X-Spam-Status: No, score=-100.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vd7u9i24j3Ut for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 09:38:58 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 37AE621F9E01 for <ietf@ietf.org>; Mon, 29 Apr 2013 09:38:50 -0700 (PDT)
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 1UWr6F-0001Aw-6X; Mon, 29 Apr 2013 12:38:47 -0400
Date: Mon, 29 Apr 2013 12:38:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: stbryant@cisco.com, Margaret Wasserman <mrw@lilacglade.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <7A380D3C6BC8AE5618D58E20@JcK-HP8200.jck.com>
In-Reply-To: <517E3590.4000902@cisco.com>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <517E3590.4000902@cisco.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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 16:38:59 -0000

--On Monday, April 29, 2013 09:55 +0100 Stewart Bryant
<stbryant@cisco.com> wrote:

>> The question that people are asking is why the diversity of
>> the IETF leadership doesn't reflect the diversity of _the
>> IETF_.
>> 
> The evidence seems to be that human's are terrible at
> "guessing"
> statistics, and the only statistics that are reliable as those
> objectively gathered and subjected to rigorous statistical
> analysis.

I mostly agree with this, but it means that attempts at
statistical measurement of populations we can't really
characterize are irrelevant.  In particular, as soon as one
talks about the "diversity of _the IETF_", one is talking about
the participant population.  There is no evidence at all, and
some evidences to the contrary, that the attendee population is
a good surrogate (approximation to a random sample, if you
prefer) for the participant population.   Making that assumption
by polling or measuring the attendee function and assuming it is
representative of the IETF may introduce far more biases than
most of what we are talking about.

> You can often see this in human assessments of risk. It is
> also in the nature of statistics that you get long runs of
> outliers, and
> that only when you take a long view to you see the averages you
> would expect. Again Humans are terrible with this, assuming
> for example that a coin that comes up heads 10 times in a row
> the assumption is that this is bias, and not a normal
> statistical
> variation that you would expect in an infinite number of
> throws.

On the other hand, as a loyal empirical Bayesian, I suggest
that, if I observe a run of 10 heads and, as a result, bet on
the next toss being heads, I am somewhat more likely to carry
home my winnings at the end of the day that you are if you
continue to bet on a 50-50 chance no matter how long the run
gets... _even_ if the rules are normal statistical variation.
Now, after an infinite number of coin tosses occur, you may be
proven correct, but part of the reason for that Bayesian
judgment (or a judgment based on moving average properties of
the time series) is that few of us are going to be able to wait
for that infinite number of tosses. 

> It would be useful to the discussion if we could see data on
> diversity
> that was the output of a rigorous  statistical analysis. i.e.
> one that
> included a confidence analysis and not a simple average in a
> few spot years.

I agree.  But I also suggest that humans are pretty good at
binary comparisons and some longitudinal relationships that do
not involve population samples.  For example, with no effort to
compare the population statistics of the IESG with the
population statistics of the IETF (the precise comparison that
is most susceptible to the statistical problems both of us are
concerned about), it is easy to look at IESG membership
longitudinally and observe that, between the early 1990s and
2010, there were always at least one, and often two or three,
women on the IESG.  Since then, zero.    Now, based on around 17
years of moving average, I feel somewhat justified statistically
in believing that something odd is happening.  

I would feel much more justified if we went a couple years more
with no change in our procedures and how we think about things
and the "zero women" trend continued, but that illustrates the
other problems with this sort of analysis and an attempt to base
it on population statistics, especially the population
statistics of experimental design.  First, our having these
discussions have, I believe, already increased sensitivities to
the issues and maybe even how the community thinks about it.  If
we end up with a woman or three on the IESG a year from now, it
will basically be impossible to know whether that was 

	-- simply a return to normal behavior after a period of
	deviation that could be attributed to statistical
	variation or 
	
	-- whether it was because this discussion was
	effectively a consciousness-raising exercise that
	changed how decisions are made.

The second issue is that, as in a clinical trial in which it
becomes obvious (with all of those subjective human judgments as
well as strict statistical ones) that one of the treatment
groups is doing much better than others, it may be socially and
morally unacceptable to continue the experiment in order to get
cleaner statistical results.


--On Monday, April 29, 2013 06:14 +0000 Christian Huitema
<huitema@microsoft.com> wrote:

> Certainly useful, but it is easy to inject one's own bias into
> such processes, and to overlook other factors. I may be
> biased, but I have the impression that the largest source of
> bias in IESG selection is the need to secure funding for the
> job, which effectively self-select people working for large
> companies making networking products.

Or at least large companies and mostly those with a significant
stake in the Internet.  I agree with this impression.   In
principle, we could separate gender (or other) bias from this by
comparing those who are willing to be candidates with those who
are selected.  I don't think that works in practice unless we
require people to get binding company approval before agreeing
to be candidates.  We have never done that.  Ignoring the other
bad effects it might have, it is a rational strategy for many
people to agree to be candidates after only a minimal discussion
with their organizations and then to have the serious discussion
only after the Nomcom's "please confirm that you are still
really available" note arrives.

> Gender may be the least
> of the problems there; there are other dimensions of
> diversity, e.g. academic vs. industry, network equipment
> versus internet service providers, software versus hardware,
> etc. Only a fraction of these segments can afford to have
> someone working full-time on the IESG. Now, having to work
> full time is a bit much for a volunteer position, and we may
> want to consider ways to remedy that.

Even within a company, there may be biases about who gets the
approval.  On the gender issue, we might be seeing symptoms of
something that is actually positive for the women engineers
although bad for the IETF.  A series of analyses[1] suggest
that, in standards bodies that are mostly working on mature
technologies, few companies consider it a good investment to
send design-capable people with good management skills to
standards meetings, much less to have them commit to standards
management activities.  When the technologies are less mature,
it makes more sense for organizations to commit design and
implementation talent for standards development and even for
standards management.  Marshall Rose memorably suggested that
those trends and others led to SDOs that contain a lot of
"Goers" rather than a lot of designer-implementer "Doers".  

If one were to hypothesize (I have no idea whether this is true)
that many of the women with design engineer capabilities who
attend IETF early in their careers have those talents recognized
by their companies and end up in positions that make it
unattractive to send them to the IETF --much to contribute all
of their time for a minimum of two to four years-- then we just
don't see them on the IETF.  Even if an exactly equal number of
incoming men have the same talents and the same recognition and
promotion pattern, the smaller number of incoming women would
predict an IESG that was largely or entirely men.

Another possible corollary to Marshall's analysis and the
earlier studies is that the leadership of any SDO will gradually
converge on entirely Go-ers or "professional standardizers",
simply because they are less expensive --in terms of loss of
skilled time for an extended period as well as more direct
costs-- than design or development talent.   That particular
issue isn't related to most of what we've been discussing as
"diversity" but it may be another very important and related
issue.  I don't think the IETF is there yet but I've wondered if
we are on the downhill slope.

best,
  john

[1] These analyses go back long before Rose contributed the much
more colorful interpretation and vocabulary to the discussion
that I've invoked above.


From dhc@dcrocker.net  Mon Apr 29 09:46:17 2013
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 D7B3321F9D77 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 09:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNXqztyuXpkZ for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 09:46:17 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 58A3B21F9D6B for <ietf@ietf.org>; Mon, 29 Apr 2013 09:46:17 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3TGkCZe032225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Apr 2013 09:46:16 -0700
Message-ID: <517EA3CF.1050703@dcrocker.net>
Date: Mon, 29 Apr 2013 09:46:07 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <517E3590.4000902@cisco.com> <7A380D3C6BC8AE5618D58E20@JcK-HP8200.jck.com>
In-Reply-To: <7A380D3C6BC8AE5618D58E20@JcK-HP8200.jck.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.66]); Mon, 29 Apr 2013 09:46:16 -0700 (PDT)
Cc: ietf@ietf.org, stbryant@cisco.com
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, 29 Apr 2013 16:46:17 -0000

On 4/29/2013 9:38 AM, John C Klensin wrote:
> First, our having these
> discussions have, I believe, already increased sensitivities to
> the issues and maybe even how the community thinks about it.


Actually, it probably hasn't.

It has raised awareness that there are people who are sensitive to the 
topic.  It probably has raised some people's awareness that there are 
serious issues here and that the IETF ought to pay attention to them 
(better).

I seriously doubt it has afforded many folk a sense of how to behave 
differently, and how to evaluate community and management choices in 
terms of diversity concerns.

Let's not confuse activity with progress.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From melinda.shore@gmail.com  Mon Apr 29 09:52:12 2013
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 791C221F9E15 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 09:52:12 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m54rVOKWGf2e for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 09:52:12 -0700 (PDT)
Received: from mail-da0-x22d.google.com (mail-da0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 0D60C21F9E14 for <ietf@ietf.org>; Mon, 29 Apr 2013 09:52:12 -0700 (PDT)
Received: by mail-da0-f45.google.com with SMTP id v40so1041256dad.18 for <ietf@ietf.org>; Mon, 29 Apr 2013 09:52:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=8LHr13U9CIaWkf3NgnXtvAhaCukjVvJ8UWXi/6dX/Q4=; b=Mk1M5ZLkDjXRJ+MjOcWmemET8G3HRJqW2tYHcy76g1gJF3b1lnDk2dvWHeeOqEYB9P HSktmbNka/lsCX7mk1dtEHvdqnRZzpF9tJ3NLMFOhSkdVUKbug+V5sMhkDN8666W18wa mrhtcnUh8nJBIRmf92Azr8Kkqr6HoteDwHhuDayEaifwnsfN9dQmurttzCNU89MEqOqT zo5qcnFZAiRczMSg8KGaJ4yl1OuP2CDIlXSjCAvZhI1LmeihcEE4i3T7ZbkpUjj+RFKF 5iZO3e+h4wPSnkZbY2mh4q3usvI3mYA9VwgumVmjXnQc0HoOo2RERA4QvJ9dazUT5wvg mIhA==
X-Received: by 10.68.209.193 with SMTP id mo1mr70508673pbc.191.1367254323274;  Mon, 29 Apr 2013 09:52:03 -0700 (PDT)
Received: from spandex.local (66-230-87-94-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.87.94]) by mx.google.com with ESMTPSA id mt13sm24755963pbc.15.2013.04.29.09.52.01 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 29 Apr 2013 09:52:02 -0700 (PDT)
Message-ID: <517EA52F.9040900@gmail.com>
Date: Mon, 29 Apr 2013 08:51:59 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com>
In-Reply-To: <517E3932.9060006@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: Mon, 29 Apr 2013 16:52:12 -0000

On 4/29/13 1:11 AM, Stewart Bryant wrote:
> The other thing to remember is that whilst your proportional estimates
> are likely to be correct, in a random process you will get long runs of
> "bias" that only average out in the long run. 

Right, although if "normal" statistical fluctuation gives us
a long period of woman-free leadership, somewhere in your long
run we might expect the same statistical fluctuation
to deliver unto us a stretch in which women are overrepresented
in the leadership.

Melinda



From acooper@cdt.org  Mon Apr 29 10:05:14 2013
Return-Path: <acooper@cdt.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 72BDD21F9E24 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 10:05:14 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHWGjStxOwpG for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 10:05:11 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 6F09321F9E43 for <ietf@ietf.org>; Mon, 29 Apr 2013 10:05:02 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Mon, 29 Apr 2013 13:04:55 -0400
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <516F3B35.8020105@bbiw.net>
Date: Mon, 29 Apr 2013 13:04:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4ECABEA0-83A8-43A8-B50F-BB0AACC8B718@cdt.org>
References: <BB682B03-F1E3-487D-B56D-7BDBEC4EAA78@cdt.org> <EE9BA586-42C8-4282-BE06-A0BE3B53B702@cdt.org> <516F3B35.8020105@bbiw.net>
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1499)
Cc: draft-iab-privacy-considerations.all@tools.ietf.org, IETF Discussion <ietf@ietf.org>, IAB IAB <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 17:05:14 -0000

Hi Dave,

Thanks for your response. We discussed it within the privacy program and =
the full IAB. I've added the following sentence to the end of the intro =
in section 3 in the pre-publication -09 version:

"Examples of several different brief definitions are provided in RFC =
4949."

I realize this may not fully assuage your concerns, but we thought it =
might help to point out the brief(er) definitions in 4949. Notably, even =
that document gives three different definitions of "privacy" and none of =
them are a single sentence long, reflecting the difficulty of trying to =
boil down the multiple facets of the concept.

To your point about privacy versus security, I'm not sure there is more =
we can say beyond what is in sections 4 and 7.

Thanks for your thorough review. Although we have a few differences of =
opinion, I'm glad that you seem to think the document has value.

Best,
Alissa


On Apr 17, 2013, at 8:15 PM, Dave Crocker <dcrocker@bbiw.net> wrote:

> Alissa,
>=20
>=20
> On 4/17/2013 10:23 AM, Alissa Cooper wrote:
>> Hi Dave,
>>=20
>> Just wanted to make sure you saw this. I plan to submit the document
>> to the IAB for publication approval next week.
>=20
>=20
> hmmm.  I did see it, but now I can't find your original response, =
which
> is probably why I didn't followup.  So thanks for the re-probe.
>=20
> I've left a few snippets from your reply at the end, as basic context,
> but I'll just comment in summary, rather than in-line.
>=20
> The summary of the summary is pretty simple:  I do understand the
> history, complexities and even controversy that make it difficult to
> document specific choices, such as defining privacy.  But I submit =
that
> due diligence for a document like this obligates the IAB to take some
> basic, solid positions, in the service of making its guidance useful.
>=20
>=20
> 1. Audience
>=20
>   We often wind up writing documents that work best for people who are
> already relatively familiar with a topic.  As you know better than =
most,
> writing for those new to a topic is a significantly different task.  I
> certainly agree that it's challenging but I see it as the essence of
> this draft.
>=20
>   That is, I believe you intend this document primarily for those who
> are less familiar with discussion and practice of "privacy"
> considerations.  But this must begin with an understanding that they
> don't really have a reliable, workable definition of the term.
>=20
>   There are many different definitions and you note that even on the
> IAB, for this draft, it has been challenging to settle on a =
definition.
> I'll submit that that should alert you to the increased need for this
> document to offer a single, useful definition, rather than to cause =
you
> to shy away from it.
>=20
>=20
> 2. Definition.
>=20
>   The alternative that you've left the reader with is to have a basic
> lack of comfort with the topic and a certainty of inconsistent
> definition.  All the good guidance later in the document will depend
> upon an inconsistent sense of when to apply it.
>=20
>   In addition, the directive that they derive their version of the
> definition from the detail later in the document is -- forgive me --
> simply unreasonable extra work. It's the sort of thing done for an
> academic texbook, not a guidance document.  This draft is an =
operational
> tutorial, as well as a set of guidelines.  Tutoring for application
> starts with explaining terms and "privacy" is the most essential term =
to
> define.
>=20
>   The exemplar definition I provided should be modified to cover
> 'organization' data as well as personal, but I think it's viable as a
> working form.  That said, I don't care whether you use it, as long as
> the document provides a meaningful definition that gives the =
/average/,
> uninformed reader a pragmatic sense of what is inside the scope of
> privacy and what is outside.
>=20
>=20
> 3. Privacy vs. Security
>=20
>   The fact that the two topics overlap or that one can be viewed as a
> subset of the other or that...  The fact that there is so much =
confusion
> here again requires that the document give concrete guidance that
> distinguishes what is security, as we use it for RFCs, and what is
> privacy, as you intend to scope it for this draft and for future =
Privacy
> Considerations work.
>=20
>   My own view is that Security is largely a technical and mechanical
> topic, while Privacy is primarily a human and social topic.  Within =
the
> IETF, we deal with security issues primarily in terms of algorithms =
and
> component technology.  I believe you intend Privacy to take a larger
> view and think that's entirely appropriate, but also quite different.
>=20
>   That privacy often plays heavily on the techniques of security does
> present challenges.  But, for example, I think that 'confidentiality' =
is
> not 'privacy'.  I'll state it differently:  If the IAB cannot agree on =
a
> meaningful and simple statement that distinguishes between privacy and
> confidentiality, then it ought to reconsider giving expert advice =
about
> the handling of privacy considerations.
>=20
>   To repeat:  In practice within the IETF, confidentiality mechanisms
> are just that: mechanisms.  They are component techniques for =
protecting
> data against unauthorized viewing.  I'd class privacy as a =
system-level
> concern for protecting against leakage and unauthorized viewing.  The
> latter, of course, sounds like confidentiality.  Frankly, I don't know
> how to reconcile that.  But then, I'm not writing expert guidance...
>=20
> d/
>=20
>=20
>=20
>=20
>=20
>=20
>>> Privacy is the concern for protecting information of or about an
>>> individual person.
>>>=20
>>> Tweak this or replace it entirely, but /please/ provide a concrete,
>>> pragmatic definition that explicitly defines what is in scope and
>>> what is out, for them to focus their considerations on.
>>=20
>> This suggestion has been debated at length within the IAB privacy
>> program over the life of this document. Our thinking is that trying
>> to define "privacy" in one sentence would be as counterproductive as
>> trying to define "security" or "extensibility" in one sentence.
>=20
>=20
>=20
>>> The typical writer and reader of RFCs is not experienced in the
>>> topic of privacy.  They won't know what you mean either:  they
>>> need very concrete guidance about the word's meaning.
>>>=20
>>> Telling me that different people mean different things with the
>>> term merely assures me that I have no idea what /you/ mean unless
>>> you tell me.  Having each reader make guesses about the meaning is
>>> a way to
> ensure non-interoperability of the construct.
>>=20
>> Per my note above, the expectation is that the document as a whole
> will provide a rich explanation of what is meant by privacy.
> ...
>>> Guidance can't be very helpful if the reader has no idea when to
> apply it.
>>=20
>> If the reader is unsure about whether to go through the thought
>> process outlined in section 7, there is no harm (other than the use
>> of
> the reader's time) in doing it and then finding out that a particular
> specification is already solidly designed when it comes to privacy.
>=20
>=20
>=20
>>> I strongly suggest that any explicit privacy discussion be
>>> required
> to be an entirely separate from the 'security considerations' section.
>>>=20
>>> My reasoning is simple:  This community sees 'security' in terms of
>>> encryption and signing, traffic analysis, and other such
>>> mechanical, relatively low-level components.  Privacy is an
>>> entirely different and
> broader and more human beast, even when its details devolve to these
> familiar mechanics.
>>>=20
>>> At the least, making it a separate section will help writers and
> readers to distinguish privacy from the security stuff we are used to
> seeing discussed.
>>=20
>> I think sections 4 and 7 demonstrate that privacy and security are
> interrelated at least in some respects.
>=20
>=20
>=20
>=20
>>> Not sure whether this is a question or a suggestion; if it's the
>>> latter, I'm not sure what to suggest:  privacy issues often
>>> develop as a combinatorial problem -- 'correlation' as you note
>>> farther down -- that
> is, developing out of unpredicted integration of information from
> discrete services.  While any specific IETF specification might have =
its
> own, direct privacy issues needing consideration, where should
> discussion of these combinatorial dangers be discussed?
>>=20
>> That is a good question and I'm not sure I know the answer. Of
>> course there is nothing to prevent people from writing drafts about
>> the
> privacy considerations associated with the combination of discrete
> services/protocols.
>=20
>=20
>=20
>=20
>=20
>=20
>>>> 4.1. Combined Security-Privacy Threats
>>>=20
>>> The fact that you have a string like "Combined Security-Privacy"
> supports the view that Privacy Considerations is distinct from =
Security
> and should not be in the Security Considerations section=85
>>=20
>> Actually I think it's the opposite. Section 4 makes concrete
> distinctions between privacy threats that are already commonly covered
> by security considerations and those that are not.
>=20
>>>> 5.2. User Participation
>>>>=20
>>>>=20
>>>> As explained in Section 4.2.5, data collection and use that
>>>> happens "in secret," without the individual's knowledge, is apt
>>>> to violate the individual's expectation of privacy and may
>>>> create incentives for misuse of data.  As a result, privacy
>>>> regimes tend to include provisions to require informing
>>>> individuals about data collection and use and involving them in
>>>> decisions about the treatment of their data.  In an engineering
>>>> context, supporting the goal of user participation usually means
>>>> providing ways for users to control the data that is shared about
>>>> them.  It may also mean providing ways for users to signal how
>>>> they expect their data to be used and shared.
>>>=20
>>> There is a serious downside to this.  It presumes that this burden
>>> on users is reasonable.  For many scenarios, it isn't.  Rather, the
>>> focus on user participation is often used as an alternative to the
>>> difficult
> work (or research) on mechanisms that require less user participation.
>>=20
>> I agree that sole reliance on user participation is undesirable. It's
>> listed here as one of several protections, so sole reliance is not
>> implied. For protocol design I would actually argue that we tend not
>> to
> think about user participation enough (whereas I agree that privacy
> policy tends to focus on it too much).
>=20
>=20
>=20
>=20
>=20
>=20
>>>> privacy impact of a system.  Although most IETF activities do not
>>>> involve standardizing user interfaces or user-facing
>>>> communications, in some cases understanding expected user
>>>> interactions can be important for protocol design.  Unexpected
>>>> user behavior may have an adverse impact on security and/or
>>>> privacy.
>>>=20
>>> While a generically reasonable view, the challenge with its
>>> application in the IETF is our general tendency to think that we
> understand UI and UX issues, although few in the IETF actually have =
the
> background for it.  For example we tend to think that simply giving
> users more information is a universal palliative.  Most discussions =
here
> about "expected user interactions" are simply wrong.  Worse, I've no
> idea what to suggest to counter this for the draft.
>>=20
>> Yeah, I'm not sure the draft can fix this problem. But agree that
>> it's a problem.
>=20
>=20
>=20
>=20
>=20
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>=20



From john-ietf@jck.com  Mon Apr 29 10:08:50 2013
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 7D8B521F9E74 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 10:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level: 
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JDyUc21ZEJ0G for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 10:08:44 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5302B21F9E73 for <ietf@ietf.org>; Mon, 29 Apr 2013 10:08:44 -0700 (PDT)
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 1UWrZB-0001Gq-Dj; Mon, 29 Apr 2013 13:08:41 -0400
Date: Mon, 29 Apr 2013 13:08:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: IETF Diversity Question on Berlin Registration?
Message-ID: <2EB83F4807D9437A7C1E779A@JcK-HP8200.jck.com>
In-Reply-To: <517EA3CF.1050703@dcrocker.net>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <517E3590.4000902@cisco.com> <7A380D3C6BC8AE5618D58E20@JcK-HP8200.jck.com> <517EA3CF.1050703@dcrocker.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@ietf.org, stbryant@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: Mon, 29 Apr 2013 17:08:50 -0000

--On Monday, April 29, 2013 09:46 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

> On 4/29/2013 9:38 AM, John C Klensin wrote:
>> First, our having these
>> discussions have, I believe, already increased sensitivities
>> to the issues and maybe even how the community thinks about
>> it.
> 
> 
> Actually, it probably hasn't.
> 
> It has raised awareness that there are people who are
> sensitive to the topic.  It probably has raised some people's
> awareness that there are serious issues here and that the IETF
> ought to pay attention to them (better).
> 
> I seriously doubt it has afforded many folk a sense of how to
> behave differently, and how to evaluate community and
> management choices in terms of diversity concerns.

I am trying (temporarily) to be more optimistic than that, but I
fear that you may be correct.  

If so, we may be in big trouble and/or wasting our time by even
having this discussion.  If raising awareness and sensitivity
isn't enough to get people to think about and make decisions
differently and the only criteria the community will accept for
either the existence of a problem or evidence that progress is
being made is hard, frequency-based, statistical (or statistical
analyses of experimental) data then,

 -- we can quibble endlessly about what should be
	measured and what the measurements mean and probably
	will, and
	
 -- we will never agree on quantitative criteria for
	progress or adequate diversity because such criteria
	will have the odor of preferential treatment and quotas
	(whether they are or not).

And that applies not just to selections by the Nomcom but to all
of the selections that are affected by the "select people whom
you know and know can do the job" behavior that has been
discussed at length in another thread.
 
> Let's not confuse activity with progress.

Indeed.  Let's also try to avoid defining progress in a way that
makes even useful activity impossible.   But, again, I fear you
are correct about all of this.

   john




From jdrake@juniper.net  Mon Apr 29 10:19:19 2013
Return-Path: <jdrake@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 A8F2321F9DDD for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 10:19:19 -0700 (PDT)
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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id izwUtDwLBgRP for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 10:19:12 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id C998721F9DD4 for <ietf@ietf.org>; Mon, 29 Apr 2013 10:19:07 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUX6ri0z3LfbAb6SCklwJYX4iX2+hgHAD@postini.com; Mon, 29 Apr 2013 10:19:07 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; Mon, 29 Apr 2013 10:16:45 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Mon, 29 Apr 2013 10:16:45 -0700
Received: from tx2outboundpool.messaging.microsoft.com (65.55.88.13) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 29 Apr 2013 10:27:28 -0700
Received: from mail34-tx2-R.bigfish.com (10.9.14.242) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.23; Mon, 29 Apr 2013 17:16:44 +0000
Received: from mail34-tx2 (localhost [127.0.0.1])	by mail34-tx2-R.bigfish.com (Postfix) with ESMTP id 82EE32C00C8	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Mon, 29 Apr 2013 17:16:44 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT005.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -25
X-BigFish: PS-25(zzbb2dI98dI9371I542I1432Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz8275dh1033ILz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1155h)
Received: from mail34-tx2 (localhost.localdomain [127.0.0.1]) by mail34-tx2 (MessageSwitch) id 1367255801950198_31657; Mon, 29 Apr 2013 17:16:41 +0000 (UTC)
Received: from TX2EHSMHS014.bigfish.com (unknown [10.9.14.252])	by mail34-tx2.bigfish.com (Postfix) with ESMTP id E453B3A0049; Mon, 29 Apr 2013 17:16:41 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS014.bigfish.com (10.9.99.114) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 29 Apr 2013 17:16:38 +0000
Received: from BL2PRD0510MB349.namprd05.prod.outlook.com ([169.254.1.151]) by BL2PRD0510HT005.namprd05.prod.outlook.com ([10.255.100.40]) with mapi id 14.16.0299.002; Mon, 29 Apr 2013 17:16:33 +0000
From: John E Drake <jdrake@juniper.net>
To: Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHOPOUbKuoMqWAFtkmNWH3bnXdwmJjsbgIAgAA1z4CAAFVjAIAAgLyAgAAGynA=
Date: Mon, 29 Apr 2013 17:16:32 +0000
Message-ID: <0182DEA5604B3A44A2EE61F3EE3ED69E1D4C6EA5@BL2PRD0510MB349.namprd05.prod.outlook.com>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com>	<517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com>
In-Reply-To: <517EA52F.9040900@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.224.51]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%GMAIL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
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: Mon, 29 Apr 2013 17:19:19 -0000

What a concept.

Irrespectively Yours,

John


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Melinda Shore
> Sent: Monday, April 29, 2013 9:52 AM
> To: ietf@ietf.org
> Subject: Re: IETF Diversity Question on Berlin Registration?
>=20
> On 4/29/13 1:11 AM, Stewart Bryant wrote:
> > The other thing to remember is that whilst your proportional
> estimates
> > are likely to be correct, in a random process you will get long runs
> > of "bias" that only average out in the long run.
>=20
> Right, although if "normal" statistical fluctuation gives us a long
> period of woman-free leadership, somewhere in your long run we might
> expect the same statistical fluctuation to deliver unto us a stretch in
> which women are overrepresented in the leadership.
>=20
> Melinda
>=20
>=20



From Ted.Lemon@nominum.com  Mon Apr 29 10:38:15 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C69E21F9A6A for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 10:38:15 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76fGbYgdeE6U for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 10:38:08 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 93C7921F9A62 for <ietf@ietf.org>; Mon, 29 Apr 2013 10:38:08 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUX6wAPvtp8v2Ck7QpG0upJch1cuW/Elq@postini.com; Mon, 29 Apr 2013 10:38:08 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 444A51B815E for <ietf@ietf.org>; Mon, 29 Apr 2013 10:38:08 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 3BE80190061; Mon, 29 Apr 2013 10:38:08 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 29 Apr 2013 10:38:08 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
Thread-Topic: IETF Diversity Question on Berlin Registration?
Thread-Index: AQHOPOUbsxw5RhqwwUuIKG4LfyrlCZjs41sAgACG3QCAAIFXgIAAAhaAgAAGRICAAAhCAA==
Date: Mon, 29 Apr 2013 17:38:07 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775166C26@mbx-01.win.nominum.com>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <517E3590.4000902@cisco.com> <7A380D3C6BC8AE5618D58E20@JcK-HP8200.jck.com> <517EA3CF.1050703@dcrocker.net> <2EB83F4807D9437A7C1E779A@JcK-HP8200.jck.com>
In-Reply-To: <2EB83F4807D9437A7C1E779A@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B6F07329F000B14C9396B1BC3758E84E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<stbryant@cisco.com>" <stbryant@cisco.com>, "<dcrocker@bbiw.net>" <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: Mon, 29 Apr 2013 17:38:15 -0000

On Apr 29, 2013, at 1:08 PM, John C Klensin <john-ietf@jck.com> wrote:
> If raising awareness and sensitivity
> isn't enough to get people to think about and make decisions
> differently=20

Statistical analysis shows that even when peoples' awareness is raised, bia=
ses continue to exist, not because the people are bad people, but because c=
ognitive biases are simply not affected by "consciousness raising" alone.  =
 So IMHO at least, what we are looking for here is not consciousness-raisin=
g, but some method of determining if we are indeed suffering from cognitive=
 biases here, and if so, some method for actually addressing the problem.


From lberger@labn.net  Mon Apr 29 11:31:16 2013
Return-Path: <lberger@labn.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 7B2A921F95EE for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 11:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.305
X-Spam-Level: 
X-Spam-Status: No, score=-100.305 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_BL_SPAMCOP_NET=1.96, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id prMcm3t3coeQ for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 11:31:12 -0700 (PDT)
Received: from oproxy5-pub.bluehost.com (oproxy5-pub.bluehost.com [67.222.38.55]) by ietfa.amsl.com (Postfix) with SMTP id 552FE21F8443 for <ietf@ietf.org>; Mon, 29 Apr 2013 11:31:08 -0700 (PDT)
Received: (qmail 32132 invoked by uid 0); 29 Apr 2013 18:30:39 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy2.bluehost.com with SMTP; 29 Apr 2013 18:30:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=Ax7IJdytr3Goo+bJR59J9K/8Bi/j+2IHQggIiqK3JeM=;  b=nyffI47KX8qQm4SbWGZ4qRLJl7gIPo8q9jUnn7riYlNqLZtHNrsfEJRVcFEumxAdMjQ1wtcGssnKfkFmOM6dpUk+K0AudCQx1LcYUdMv3Dohf6TeGD4WkFLt3k7yF8NR;
Received: from box313.bluehost.com ([69.89.31.113]:50510 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1UWsqU-0000wl-TV; Mon, 29 Apr 2013 12:30:39 -0600
Message-ID: <517EBC4C.2040201@labn.net>
Date: Mon, 29 Apr 2013 14:30:36 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <517E3590.4000902@cisco.com> <7A380D3C6BC8AE5618D58E20@JcK-HP8200.jck.com> <517EA3CF.1050703@dcrocker.net>
In-Reply-To: <517EA3CF.1050703@dcrocker.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, stbryant@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: Mon, 29 Apr 2013 18:31:16 -0000

Did anyone notice the NPR piece this AM?

http://www.npr.org/blogs/alltechconsidered/2013/04/29/178810467/blazing-the-trail-for-female-programmers

Perhaps it's time for an IETF equivalent/chapter of
http://railsbridge.org/, http://blackfounders.com/,
http://wisecampaign.org.uk/, etc. ...

Lou

On 4/29/2013 12:46 PM, Dave Crocker wrote:
> Let's not confuse activity with progress.
> 

From mstjohns@comcast.net  Mon Apr 29 11:47:42 2013
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 E619E21F9A56 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 11:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.637
X-Spam-Level: 
X-Spam-Status: No, score=-96.637 tagged_above=-999 required=5 tests=[AWL=3.799, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PhbX4Y4OKhIW for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 11:47:37 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 8EAA221F9A55 for <ietf@ietf.org>; Mon, 29 Apr 2013 11:47:37 -0700 (PDT)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta03.westchester.pa.mail.comcast.net with comcast id Vnn11l00A1swQuc53uncLX; Mon, 29 Apr 2013 18:47:36 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta15.westchester.pa.mail.comcast.net with comcast id Vunb1l00J2kB7pQ3bunc5g; Mon, 29 Apr 2013 18:47:36 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 29 Apr 2013 14:47:35 -0400
To: Ted Lemon <Ted.Lemon@nominum.com>,John C Klensin <john-ietf@jck.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775166C26@mbx-01.win.nominu m.com>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <517E3590.4000902@cisco.com> <7A380D3C6BC8AE5618D58E20@JcK-HP8200.jck.com> <517EA3CF.1050703@dcrocker.net> <2EB83F4807D9437A7C1E779A@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B630775166C26@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_61850387==.ALT"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1367261256; bh=R2346eOIuGec+szLVhiNXQQBAg3rdZs8fRjAuAblIxg=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=P1LGYh4x80O0WdjSy1wLqR7zt2jBV85cjIJXJcUvqtpzTQACxemtInCuqJfMWejAB 88mY9dM50wp2c9pcLQhJc0H+cR+IyR+T7ztR+R4fFYWY5RBhi5x7Bw/Dc3mDjl9H7s K9UGYoRvUObyzgxi6k/ORfYvxq69c0lshZtimm5PHP0h8JnUlsk9i2wKgcQ0PqmrWG Ut4h0sVrWX3k+5/cGPuNoqhdZUgoa/+kYW6SI+JGis91mkHU62fXglRSZia2Svzrnx f4bUS0Xrn0mHPpFieiAQ52WlEoChlb+RUaMwB8WLisCCnRGV5Gek1OWG0Gi7IAQ8hD kdhLaNs00LVlA==
Message-Id: <20130429184737.8EAA221F9A55@ietfa.amsl.com>
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, "<stbryant@cisco.com>" <stbryant@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: Mon, 29 Apr 2013 18:47:43 -0000

--=====================_61850387==.ALT
Content-Type: text/plain; charset="us-ascii"

At 01:38 PM 4/29/2013, Ted Lemon wrote:
>On Apr 29, 2013, at 1:08 PM, John C Klensin <john-ietf@jck.com> wrote:
>> If raising awareness and sensitivity
>> isn't enough to get people to think about and make decisions
>> differently 
>
>Statistical analysis shows that even when peoples' awareness is raised, biases continue to exist, not because the people are bad people, but because cognitive biases are simply not affected by "consciousness raising" alone.   So IMHO at least, what we are looking for here is not consciousness-raising, but some method of determining if we are indeed suffering from cognitive biases here, and if so, some method for actually addressing the problem.


Yup.  The problem here is that the sample set of "leadership" positions is so small its difficult to get any reasonable measure one way or the other.   When you start mixing and matching gender, race, citizenship etc into the pot as possible determiners it just gets worse.

The normal measure for determining whether one population is distinct from another appears to be the Chi Squared test.  

Throwing in a matrix of 

            WG Chairs     IAB/IESG Members
Male         187             25
Female        15             1

And running the calculation (http://www.quantpsy.org/chisq/chisq.htm) using the Yates' values (because the sample size is so small), there is a 79.13% chance that any observed differences in the composition of the two groups is solely due to statistical variations.

And playing off of John's message, if you look around 2005 when there were 4 female members of the IAB and IESG (and assuming the same composition of WG chairs), that calculation yields  something 31.4% - or 2 chances in 3 that the differences were due to something other than statistical variations.

When I look at this as a pure numbers problem, I'm unable to say there is a cognitive bias in the selection process and in fact the numbers would argue against being able to say that without a much larger set of IAB/IESG members.

Mike
 


--=====================_61850387==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
At 01:38 PM 4/29/2013, Ted Lemon wrote:<br>
<blockquote type=cite class=cite cite="">On Apr 29, 2013, at 1:08 PM,
John C Klensin &lt;john-ietf@jck.com&gt; wrote:<br>
&gt; If raising awareness and sensitivity<br>
&gt; isn't enough to get people to think about and make decisions<br>
&gt; differently <br><br>
Statistical analysis shows that even when peoples' awareness is raised,
biases continue to exist, not because the people are bad people, but
because cognitive biases are simply not affected by &quot;consciousness
raising&quot; alone.&nbsp;&nbsp; So IMHO at least, what we are looking
for here is not consciousness-raising, but some method of determining if
we are indeed suffering from cognitive biases here, and if so, some
method for actually addressing the problem.</blockquote><br><br>
Yup.&nbsp; The problem here is that the sample set of
&quot;leadership&quot; positions is so small its difficult to get any
reasonable measure one way or the other.&nbsp;&nbsp; When you start
mixing and matching gender, race, citizenship etc into the pot as
possible determiners it just gets worse.<br><br>
The normal measure for determining whether one population is distinct
from another appears to be the Chi Squared test.&nbsp; <br><br>
Throwing in a matrix of <br><br>
<font face="Courier New, Courier">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WG
Chairs&nbsp;&nbsp;&nbsp;&nbsp; IAB/IESG Members<br>
Male&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
187&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
25<br>
Female&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1<br><br>
And running the calculation
(<a href="http://www.quantpsy.org/chisq/chisq.htm" eudora="autourl">
http://www.quantpsy.org/chisq/chisq.htm</a>) using the Yates' values
(because the sample size is so small), there is a 79.13% chance that any
observed differences in the composition of the two groups is solely due
to statistical variations.<br><br>
And playing off of John's message, if you look around 2005 when there
were 4 female members of the IAB and IESG (and assuming the same
composition of WG chairs), that calculation yields&nbsp; something 31.4%
- or 2 chances in 3 that the differences were due to something other than
statistical variations.<br><br>
When I look at this as a pure numbers problem, I'm unable to say there is
a cognitive bias in the selection process and in fact the numbers would
argue against being able to say that without a much larger set of
IAB/IESG members.<br><br>
Mike<br>
&nbsp;<br>
</font></body>
<br>
</html>

--=====================_61850387==.ALT--


From mstjohns@comcast.net  Mon Apr 29 12:04:42 2013
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 76E7021F9B61 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.537
X-Spam-Level: 
X-Spam-Status: No, score=-98.537 tagged_above=-999 required=5 tests=[AWL=1.900, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6c1GmrVC2WgE for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:04:37 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 5669821F9AD6 for <ietf@ietf.org>; Mon, 29 Apr 2013 12:04:37 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta03.westchester.pa.mail.comcast.net with comcast id VnNi1l00A1vXlb853v4cKa; Mon, 29 Apr 2013 19:04:36 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta17.westchester.pa.mail.comcast.net with comcast id Vv4b1l00S2kB7pQ3dv4cqq; Mon, 29 Apr 2013 19:04:36 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 29 Apr 2013 15:04:35 -0400
To: dcrocker@bbiw.net
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <517E0656.1000803@dcrocker.net>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1367262276; bh=SZiH39yqlyI4MnVSAgQr4UdRC72uD1oktoLzL4/yThk=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=koDc7GzXebZHwswIHNUeObl0Xgnl/P89gvFsBrSRI9Kw+wKIHgSvIL8JNbWpgcB/u jn88oYhwXf9/MMU3TJvS2ugjpAOGS3c70twSBF8Eo51hf9VYmR4jLZNEQQAuGWPDC1 Wki3byf2stnOrXc/kVudpuqoPq+Q0e0DHEj0PHebjfRqHOLFm13glsCH4OrA+Ykpo/ lzsGX9InymZr+pNj4kTo0CmHd6yQzg9N1eMogMyetlA0TLDIKBAO+cW5vfFDcxrwMC 1DKyGXx/rg18mIQPVvUStk6ZnLvxlcfbtk6jD7NKcMyMnvQoESzUiEBSMXiU6wb5WZ TTtcKO4o9/aSA==
Message-Id: <20130429190437.5669821F9AD6@ietfa.amsl.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: Mon, 29 Apr 2013 19:04:42 -0000

At 01:34 AM 4/29/2013, Dave Crocker wrote:
>On 4/28/2013 9:05 PM, Michael StJohns wrote:
>>Let's consider for a moment that this may not actually be the correct question.  Instead, consider "Why the diversity of the IETF leadership doesn't reflect the diversity of the set of the IETF WG chairs"?  I believe this is a more representative candidate population for the IAB and IESG.
>
>
>Except that the IESG members select the wg chairs, which makes your baseline stastistic suspect; it's too easy for all sorts of biasing factors to sway the allocation of wg chair positions.


A couple of points: 

Actually, I don't think this is even a mostly correct statement - that AD select chairs.  I believe that most chairs are self-selected [e.g. hey AD, I want to run a BOF on this topic with the idea of forming a working group - here's the other person who might chair, what do you think?  Sure - go ahead, we may twiddle with things a bit at charter formation, but you look like you know what you're doing].  With one exception (where I was asked to chair an evaluation panel), that's been my experience.

Would you have evidence to the contrary? 

Second point: 

You ignored most of the post and went directly to my last question - 'If there is no statistical difference between the IAB/IESG and the WG chair set, should we then consider the relationship between the IETF attending constituency and the WG chair set?"    Say the average meeting had 1500 attendees.  7.4% would suggest that there are 111 female attendees.  If the actual number is higher or lower it MAY represent a  statistically significant difference in the composition of the two groups.  Or it may not.   And even then, may only have a very indirect impact in the composition of the IAB/IESG.  Care to do the analysis?

Later, Mike



>d/
>
>-- 
>Dave Crocker
>Brandenburg InternetWorking
>bbiw.net



From mstjohns@comcast.net  Mon Apr 29 12:16:12 2013
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 363E021F9AE5 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.17
X-Spam-Level: 
X-Spam-Status: No, score=-99.17 tagged_above=-999 required=5 tests=[AWL=1.267,  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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EAQhnqEL9QbL for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:16:06 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 02DBF21F9BDE for <ietf@ietf.org>; Mon, 29 Apr 2013 12:16:02 -0700 (PDT)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta03.westchester.pa.mail.comcast.net with comcast id VmVg1l00C1ZXKqc53vFzzL; Mon, 29 Apr 2013 19:15:59 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta21.westchester.pa.mail.comcast.net with comcast id VvFy1l00B2kB7pQ3hvFyEQ; Mon, 29 Apr 2013 19:15:59 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 29 Apr 2013 15:15:58 -0400
To: dcrocker@bbiw.net,Christian Huitema <huitema@microsoft.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <517E0BAF.2000207@dcrocker.net>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.com> <517E0BAF.2000207@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1367262959; bh=EK18IAG9cFJ8cmyYza3Nk0C5BMdeSiCNTa1Eu69IxKQ=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=k1UCaBWC2yhfmPBNTIj5+vYqlId+NofD3UVpNUdFF2u72GwddzZpWLgfjNpf2ZKEp IS7nieejb7fmqiHaJOT5pSmnoPPeu5LFtUgC6Wy7wh00H0IAocI9kLH+3rYVzuknXF MQUUk1L83nvat3lyqIZgbqF8Gio8FOQ78z7xwkz49OPYHsAKRq1VvJvMRcBsJy2XYa 7qPmj+lb2EBBXL6N6jmCXBa8xPtnLrwTBufkj7AoNJudD8LxlUdBZ6H1Q7susxKRm4 AtPyC7fihttdFvEx2MuWPTQja+cW1cYUqmywsdI7a6bc7Vbc4C/D84Om1AZCqhej5C mlzj8xyAemVgw==
Message-Id: <20130429191603.02DBF21F9BDE@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: Mon, 29 Apr 2013 19:16:12 -0000

At 01:57 AM 4/29/2013, Dave Crocker wrote:
>including such things as interaction (in)sensitivities, group tone and style, and observable misbehaviors, all of which are likely to produce biasing results.

But in which direction?

The same thing could be said of pushing personal or cultural biases into the interpretation of group tone, style, and taking offense at behaviors which one culture might construe as offensive but for 50 other cultures is just the way things work.  

We have an IETF culture - like it or not.  It changes over time, as the population changes.  We can't and shouldn't expect to be able to change it by fiat, or to adopt as whole cloth a bias free culture (for some values of bias).

Mike



From mstjohns@comcast.net  Mon Apr 29 12:28:54 2013
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 506E521F9B38 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.487
X-Spam-Level: 
X-Spam-Status: No, score=-99.487 tagged_above=-999 required=5 tests=[AWL=0.950, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DG9EeaeD27qL for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:28:48 -0700 (PDT)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB4F21F9B35 for <ietf@ietf.org>; Mon, 29 Apr 2013 12:28:48 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta09.westchester.pa.mail.comcast.net with comcast id Vo0F1l0040Fqzac59vUn2l; Mon, 29 Apr 2013 19:28:47 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta08.westchester.pa.mail.comcast.net with comcast id VvUm1l01M2kB7pQ3UvUnhc; Mon, 29 Apr 2013 19:28:47 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 29 Apr 2013 15:28:47 -0400
To: Melinda Shore <melinda.shore@gmail.com>,ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <517EA52F.9040900@gmail.com>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1367263727; bh=bPKuJ3tXYhqtcQYG7PIeMphcm2Q2DKBrCG9O05JSjVk=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=MfA+xnKnILDveGi8iWqH11jsGlCQdIQI0zgQMhO9IN7b6uZ9InOURh75dcXsQJyOd 8GI5VmaM23t4dGDjy2TQo3pzdLHPE8HK8tbHRhzu9Y3+opA8XXv4wxG17x+IxDPtH5 q80huyV1Woh4Xod4ndzXqPKFk5jyfKgqi7MRDSJG1q2wZytk5ZG3m/wctflywHDDPM 3y+snjTsHH9T/0FxgRRAihsJdT3LZXdMpirb5/0j+V27wtH95+78lTJhQfCatzIP95 F4eeYbLOW2at+2wgR0NfcViEq0XMrGLnM8RWlHZvRf0mZG/hWCzjLxSTStf79bRbiU zs98xHoCfmdlw==
Message-Id: <20130429192848.5FB4F21F9B35@ietfa.amsl.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, 29 Apr 2013 19:28:54 -0000

At 12:51 PM 4/29/2013, Melinda Shore wrote:
>On 4/29/13 1:11 AM, Stewart Bryant wrote:
>> The other thing to remember is that whilst your proportional estimates
>> are likely to be correct, in a random process you will get long runs of
>> "bias" that only average out in the long run. 
>
>Right, although if "normal" statistical fluctuation gives us
>a long period of woman-free leadership, somewhere in your long
>run we might expect the same statistical fluctuation
>to deliver unto us a stretch in which women are overrepresented
>in the leadership.

Hi Melinda - 

Actually, look at the time frame around 2004-5.  Multiple women on the IAB and multiple women on the IESG.  Almost double the expected value of "2" given the WG proportions.  

One of the things I saw, but didn't comment on elsewhere, was that I had noted that a number of the women who had participated as IESG or IAB members have since stopped participating (attending actually) IETF meetings.  I didn't comment on it because I didn't have a good feel for whether that proportion was higher or lower than the men who have been IESG/IAB members and are now not participating.  Analysis of this might yield some data on whether or not we're losing long term female participants at a higher rate than long term male participants - if so, it may be worthwhile to ask former members the "why" question to see if there's anything we can do to mitigate.  Long term participants appear (my opinion) to be more attractive candidates for IAB/IESG positions.

Mike



>Melinda



From margaretw42@gmail.com  Mon Apr 29 12:30:24 2013
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 F006121F9B83 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:30:24 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2xTy3MzgPDlW for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:30:24 -0700 (PDT)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 756B221F9B7F for <ietf@ietf.org>; Mon, 29 Apr 2013 12:30:24 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id d42so3351257qca.15 for <ietf@ietf.org>; Mon, 29 Apr 2013 12:30:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=htcYHLm+0lFoz9LF1tlSQUjMbmsFl4K+h+dYksUzg2s=; b=nrs2yda0ye4q3mfpBN1MYb1NiI+drewJSqvge9ahTUufZD1ME3jNqw7Vt9gE5ipSgO E06TL53eqLm5UTrbcTYAK+fK/U1WqobIuKsmtm+mWI7t2aJjXC5eFRj4V3U9ljJLrSK1 +L/bvWgcD8712JrKbvwjah/DN/eE87emXDbH7rIAK3SGYNl4iVZ2EJ94bb722V19Kavt jGIS0X0DgCKnvUQsAkEBSPBgcUDzuWWh6jWHqVcfUOqmMSmTAR21gNLC6O4WDZmgj0dH 34yJu5CyHivHS/lR3kXVrHeYAk6FQdmC9TN3y+1fBdzpya60E1rVlAhxdQI3T4+MUg7i JAtw==
X-Received: by 10.49.119.138 with SMTP id ku10mr61193436qeb.13.1367263823961;  Mon, 29 Apr 2013 12:30:23 -0700 (PDT)
Received: from [10.1.10.101] ([23.30.188.246]) by mx.google.com with ESMTPSA id kf2sm35256287qeb.4.2013.04.29.12.30.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 29 Apr 2013 12:30:23 -0700 (PDT)
Sender: Margaret Wasserman <margaretw42@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <20130429191603.02DBF21F9BDE@ietfa.amsl.com>
Date: Mon, 29 Apr 2013 15:30:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <52E44A75-A6A9-4778-A8E0-DDBDDCE7EB38@lilacglade.org>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.com> <517E0BAF.2000207@dcrocker.net> <20130429191603.02DBF21F9BDE@ietfa.amsl.com>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.1499)
Cc: Christian Huitema <huitema@microsoft.com>, 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: Mon, 29 Apr 2013 19:30:25 -0000

Hi Mike,

On Apr 29, 2013, at 3:15 PM, Michael StJohns <mstjohns@comcast.net> =
wrote:
> We have an IETF culture - like it or not.  It changes over time, as =
the population changes.  We can't and shouldn't expect to be able to =
change it by fiat, or to adopt as whole cloth a bias free culture (for =
some values of bias).


How you do you think a culture evolves to be more inclusive?  Might that =
start with discussions like these?

Margaret



From hartmans@mit.edu  Mon Apr 29 12:39:35 2013
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 767A121F9B21 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:39:35 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8M0+VwGAywUq for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 12:39:29 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 895EE21F9B15 for <ietf@ietf.org>; Mon, 29 Apr 2013 12:39:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 7E7B82027D; Mon, 29 Apr 2013 15:37:21 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tgw2VErlSYiJ; Mon, 29 Apr 2013 15:37:21 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 29 Apr 2013 15:37:21 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id A9AD54499; Mon, 29 Apr 2013 15:39:18 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Melinda Shore <melinda.shore@gmail.com>,  ietf@ietf.org
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com>
Date: Mon, 29 Apr 2013 15:39:18 -0400
In-Reply-To: <20130429192848.5FB4F21F9B35@ietfa.amsl.com> (Michael StJohns's message of "Mon, 29 Apr 2013 15:28:47 -0400")
Message-ID: <tslli816s9l.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 19:39:35 -0000

For what it's worth, I'm not finding the current discussion is providing
me useful information for making decisions.  It doesn't really matter to
me whether the problem is selection of WG chairs or selection of
IAB/IESG/IAOC after WG chairs are selected.  I think it is valuable to
attempt to improve both situations in parallel, and the sorts of
conclusions being drawn from the statistical discussion we're currently
having cannot possibly change my opinion on that issue.

I'm not saying that my mind is closed to being changed; simply that I've
considered all the possible conclusions that I think could be drawn from
the analysis being considered and from my standpoint they don't affect
how I'd feel about various proposals that could be brought forward.

Which I guess speaks to John's point that I at least am a member of the
community who doesn't think the hard statistical analysis is useful
here.

From stbryant@cisco.com  Mon Apr 29 13:04:15 2013
Return-Path: <stbryant@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 A3F3E21F9BE7 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.974
X-Spam-Level: 
X-Spam-Status: No, score=-109.974 tagged_above=-999 required=5 tests=[AWL=0.625, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9dneJia4wPqn for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:04:10 -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 E54D221F9BC0 for <ietf@ietf.org>; Mon, 29 Apr 2013 13:04:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1144; q=dns/txt; s=iport; t=1367265850; x=1368475450; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=pnn/FicgHJKW2/8CqkJAnJqP1LfWCDl67Qr4gbWz+Dg=; b=Slpj+7rnQ91dcsxNUYKoFfHYrq7Lpk+oFV3eGCZhCGu4kL+xgLrAVVp5 7uRhP90ZEC8Bkgp4gWINlCFi0F686g9HDZboRRmmOSo65AiT5SF5jWEHs rkhH4qxSf2eePN0vQ0FO7WKBbQ0L4jWZrTqPLZH5g79Pptu2km82ceFW+ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAHzRflGQ/khN/2dsb2JhbABSDoJ5vCGCXoEHFnSCHwEBAQQ4QAEQCxgJFg8JAwIBAgFFBg0BBwEBEIgCvWaNV4FDB4NPA5cekSqCUkA
X-IronPort-AV: E=Sophos;i="4.87,575,1363132800"; d="scan'208";a="153463736"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 29 Apr 2013 20:04:08 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3TK46lT001864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Apr 2013 20:04:07 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r3TK45ju028628; Mon, 29 Apr 2013 21:04:06 +0100 (BST)
Message-ID: <517ED235.9070202@cisco.com>
Date: Mon, 29 Apr 2013 21:04:05 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu>
In-Reply-To: <tslli816s9l.fsf@mit.edu>
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
Reply-To: stbryant@cisco.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: Mon, 29 Apr 2013 20:04:15 -0000

On 29/04/2013 20:39, Sam Hartman wrote:
> For what it's worth, I'm not finding the current discussion is providing
> me useful information for making decisions.  It doesn't really matter to
> me whether the problem is selection of WG chairs or selection of
> IAB/IESG/IAOC after WG chairs are selected.  I think it is valuable to
> attempt to improve both situations in parallel, and the sorts of
> conclusions being drawn from the statistical discussion we're currently
> having cannot possibly change my opinion on that issue.
>
> I'm not saying that my mind is closed to being changed; simply that I've
> considered all the possible conclusions that I think could be drawn from
> the analysis being considered and from my standpoint they don't affect
> how I'd feel about various proposals that could be brought forward.
>
> Which I guess speaks to John's point that I at least am a member of the
> community who doesn't think the hard statistical analysis is useful
> here.
>
Sam,

Why would you disregard a statistical analysis? That seems akin to
disregarding the fundamentals of science and engineering.

Stewart

From mstjohns@comcast.net  Mon Apr 29 13:16:11 2013
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 A788721F9C01 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.677
X-Spam-Level: 
X-Spam-Status: No, score=-99.677 tagged_above=-999 required=5 tests=[AWL=0.760, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VTQlchHLse4z for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:16:05 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDFB21F9C03 for <ietf@ietf.org>; Mon, 29 Apr 2013 13:16:05 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta03.westchester.pa.mail.comcast.net with comcast id Vnxy1l0081GhbT853wFqXf; Mon, 29 Apr 2013 20:15:50 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta07.westchester.pa.mail.comcast.net with comcast id VwFp1l01Z2kB7pQ3TwFqK8; Mon, 29 Apr 2013 20:15:50 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 29 Apr 2013 16:15:46 -0400
To: Margaret Wasserman <mrw@lilacglade.org>
From: Michael StJohns <mstjohns@comcast.net>
Subject: How does the IETF evolve to continue to be an effective, efficient, and relevant source of high quality Internet standards? Was: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <52E44A75-A6A9-4778-A8E0-DDBDDCE7EB38@lilacglade.org>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.com> <517E0BAF.2000207@dcrocker.net> <20130429191603.02DBF21F9BDE@ietfa.amsl.com> <52E44A75-A6A9-4778-A8E0-DDBDDCE7EB38@lilacglade.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1367266550; bh=lkVmpzjKRhBfQ1wr3CTOJ60g038WFJv8EVftag4hC+I=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=J2RtdLxXnDyTAshSW8W/J2qbuWkhwDpzWsBlbBF0pdxXflek7A/6CIH14PCTzF4y2 w6TIcTodsz4IHzj0hbSZKE6/g8H93uIQDd2dzFZIV6zVmzKkZnAl5lgmUiOSlrg+/9 i682enrM3dk7iz/8LcAEf1S/QNeQjRvY3QhYw3xYnmOXQiAhhagKqLBCBnWsElCcHT dzMv220Zd6dcmWJMttyx/MsPrCkxsbgfpdwZuGjC8Y6mwrhyi3JedGWO0s6aHvS2zJ AcnGR09EFIvpEyk64W3O76mtA7jQ6Kq+R8IyfropitmjNQPrP0SMoY8C7CSXmA+Ubg zJXFoHsgc2pVg==
Message-Id: <20130429201605.7BDFB21F9C03@ietfa.amsl.com>
Cc: Christian Huitema <huitema@microsoft.com>, 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: Mon, 29 Apr 2013 20:16:11 -0000

At 03:30 PM 4/29/2013, Margaret Wasserman wrote:

>Hi Mike,
>
>On Apr 29, 2013, at 3:15 PM, Michael StJohns <mstjohns@comcast.net> wrote:
>> We have an IETF culture - like it or not.  It changes over time, as the population changes.  We can't and shouldn't expect to be able to change it by fiat, or to adopt as whole cloth a bias free culture (for some values of bias).
>
>
>How you do you think a culture evolves to be more inclusive?  Might that start with discussions like these?

I believe your statement implies some preconceptions - that you believe the IETF culture is not inclusive enough and that more inclusiveness will benefit the IETF.  I'm not sure there's evidence to support the first - hence the numerical analysis.   It may be the case that "we're not inclusive enough" is a correct evaluation, but see Stewart's note on the human tendency to impute patterns into random results.

I would ask this instead - "How does the IETF evolve to continue to be an effective, efficient, and relevant source of high quality Internet standards?"

If one of the answers to that question necessarily involves inclusiveness, then the conversation should go forward on that topic, but preferably not in isolation, not as the "fix this now" knee jerk (my perception) type of activity that seems to be going on.

Let me ask a couple of specific questions of you.  

Who have you mentored in the past 5 years?  Have  they ended up as working group chairs, or ADs or IAB members?   Do they mostly represent under-represented groups?  How many of them were employed by your employer (e.g. was this a work related task?)?

During your time as an AD, how many women did you arm twist/recruit specifically  (or ask nicely) to take WG positions in your area (as opposed to them coming to you or your co-AD)?  

How many non-employee, under-represented population attendees is your current employer supporting to go to the IETF?  Have you addressed this with your employer?

Why is the inclusiveness question more of an IETF question, as opposed to one of personal actions?

I'm asking the above, because I'm trying to get a calibration on what you mean by inclusiveness and how important it actually is for you, and possibly for your employer.

Mike



>Margaret



From dhc@dcrocker.net  Mon Apr 29 13:40:31 2013
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 D328421F9B36 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:40:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCGgP3l5OHY4 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:40:26 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id EE90D21F9B2F for <ietf@ietf.org>; Mon, 29 Apr 2013 13:40:26 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3TKeLWY007730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Apr 2013 13:40:24 -0700
Message-ID: <517EDAB0.5020904@dcrocker.net>
Date: Mon, 29 Apr 2013 13:40:16 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <20130429190437.5669821F9AD6@ietfa.amsl.com>
In-Reply-To: <20130429190437.5669821F9AD6@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.66]); Mon, 29 Apr 2013 13:40:24 -0700 (PDT)
Cc: dcrocker@bbiw.net, 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, 29 Apr 2013 20:40:31 -0000

On 4/29/2013 12:04 PM, Michael StJohns wrote:
> At 01:34 AM 4/29/2013, Dave Crocker wrote:
> Actually, I don't think this is even a mostly correct statement -
> that AD select chairs.

It is a long-standing, simple, objective, unvarying management fact of 
IETF procedure:  ADs hire and fire wg chairs.



> Second point:
>
> You ignored most of the post and went directly to my last question

I went to the meta-point that the line of discussion isn't 
methodologically meaningful or educationally useful.  Possibly you 
noticed one or two additional postings in this sub-thread asserting the 
same thing.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dharkins@lounge.org  Mon Apr 29 13:41:23 2013
Return-Path: <dharkins@lounge.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 E460621F9B39 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6yY-fLIz5PTk for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:41:18 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id E0A2F21F9A46 for <ietf@ietf.org>; Mon, 29 Apr 2013 13:41:18 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 73E1E10224008; Mon, 29 Apr 2013 13:41:18 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Mon, 29 Apr 2013 13:41:18 -0700 (PDT)
Message-ID: <7425f4bc8a7fb30f123e68bc60b341f2.squirrel@www.trepanning.net>
In-Reply-To: <tslli816s9l.fsf@mit.edu>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu>
Date: Mon, 29 Apr 2013 13:41:18 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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, 29 Apr 2013 20:41:24 -0000

On Mon, April 29, 2013 12:39 pm, Sam Hartman wrote:
> For what it's worth, I'm not finding the current discussion is providing
> me useful information for making decisions.  It doesn't really matter to
> me whether the problem is selection of WG chairs or selection of
> IAB/IESG/IAOC after WG chairs are selected.  I think it is valuable to
> attempt to improve both situations in parallel, and the sorts of
> conclusions being drawn from the statistical discussion we're currently
> having cannot possibly change my opinion on that issue.
>
> I'm not saying that my mind is closed to being changed; simply that I've
> considered all the possible conclusions that I think could be drawn from
> the analysis being considered and from my standpoint they don't affect
> how I'd feel about various proposals that could be brought forward.

  Sounds to me like you have the cart in front of the horse. You already
have in mind various proposals (interestingly left unstated) and are looking
for data that can justify them being brought forward. Apparently, this data
does not help you justify these proposals so you find no use discussing in
it. Maybe we should let the data drive the proposals instead of the other
way around.

  Dan.



From hartmans@mit.edu  Mon Apr 29 13:49:29 2013
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 AD3CA21F9B7A for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:49:29 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zYzjf6GEEboN for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:49:23 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id CEA4521F9A58 for <ietf@ietf.org>; Mon, 29 Apr 2013 13:49:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 785C92027D; Mon, 29 Apr 2013 16:47:16 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KzdBwUPD_9xS; Mon, 29 Apr 2013 16:47:16 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 29 Apr 2013 16:47:16 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 72B734499; Mon, 29 Apr 2013 16:49:13 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: stbryant@cisco.com
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com>
Date: Mon, 29 Apr 2013 16:49:13 -0400
In-Reply-To: <517ED235.9070202@cisco.com> (Stewart Bryant's message of "Mon, 29 Apr 2013 21:04:05 +0100")
Message-ID: <tsl61z56p12.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.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 20:49:29 -0000

>>>>> "Stewart" == Stewart Bryant <stbryant@cisco.com> writes:


    Stewart> Why would you disregard a statistical analysis? That seems
    Stewart> akin to disregarding the fundamentals of science and

Statistical analysis is only useful if it's going to tell you something
that matters for your decision criteria.

Let's take Mike's most recent messages here.  It doesn't actually matter
to me whether the problem in gender diversity is at the nomcom level or
at the wg chair selection level.
So, a statistical discussion of whether there's bias in nomcom choosing
leaders from the wg chairs does not provide input that matters in my
decision criteria, so I disregard that particular analysis.

I certainly did not mean to imply that I disregard statistics, or even
disregard statistics in diversity discussions.  Simply, I don't find the
statistical discussion here pointful, and I think it's a sufficient
distraction that I felt a need to speak out about it.

From jabley@hopcount.ca  Mon Apr 29 13:55:33 2013
Return-Path: <jabley@hopcount.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 B09A921F99C3 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:55:33 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P8PCaEQIxy0X for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 13:55:32 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A2B2621F97CD for <ietf@ietf.org>; Mon, 29 Apr 2013 13:55:32 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id uo1so1250557pbc.20 for <ietf@ietf.org>; Mon, 29 Apr 2013 13:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=eH5V97EZ13pAu1/TLFLdwaJ2owlgENPJ3Qkl6ceK0To=; b=JsgzgnMkSeuQZn2zWfNdBoXbARFWj34wSJKCnpgB9yAE76Wf9UXzP8IiwE9k0cuYlE rpapELB+BFCKziyTUIN7AqMt+X5jpUrV+gCCWQkt9Qg7zqE3TFiqhe58h4aUfQrfLWXy p98TH7QF7UWac0mzjtWFZbjFM5W6DbTtvfkEM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received: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=eH5V97EZ13pAu1/TLFLdwaJ2owlgENPJ3Qkl6ceK0To=; b=CJCKQytBlnlHCV/uOu9IGd/HtjdF4/xCAHua40yYYiMkxISFxeMUR8ry+ZYlj7beRw rSIEdT98NSEcTBNW0vOkYqKk4XG5jKNtXZZksNjvzgSBSIqKZcD4Y4XETDp56UYL8qZ0 gpjCBICBrmgcyCcLaPVispzhZPPEniLePWQmG9V8fHwD8tVHiIWOXqGtREU2EL2wjaMT chwUPd320ek0uEZ5zbmsOFcpeBILQOhPDtDQOgO3wQw2qbFP7WG0FMIQgHbCTaEQPsja oZDeWG6ZGXtvfujNVIwIMzr5vM64aKS0aVBI2U3UjbNqQxEPLfLwT3D08QEE0MwIHLGX BgiA==
X-Received: by 10.68.189.67 with SMTP id gg3mr72822291pbc.141.1367268924594; Mon, 29 Apr 2013 13:55:24 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:6581:47d:dfb3:afa9? ([2001:4900:1042:100:6581:47d:dfb3:afa9]) by mx.google.com with ESMTPSA id ya4sm25407686pbb.24.2013.04.29.13.55.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 29 Apr 2013 13:55:23 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <tsl61z56p12.fsf@mit.edu>
Date: Mon, 29 Apr 2013 16:55:20 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <4CA9ACF2-4728-4BDD-A94B-570E1533F4A1@hopcount.ca>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com> <tsl61z56p12.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQkB5srTEnLqxItbFkIVVjRC1qckC4GTs9DTogvQi92bnMTKk11KHsRxDih0hCJuPlSRCWiH
Cc: ietf@ietf.org, stbryant@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: Mon, 29 Apr 2013 20:55:33 -0000

On 2013-04-29, at 16:49, Sam Hartman <hartmans-ietf@mit.edu> wrote:

>>>>>> "Stewart" == Stewart Bryant <stbryant@cisco.com> writes:
> 
> 
>    Stewart> Why would you disregard a statistical analysis? That seems
>    Stewart> akin to disregarding the fundamentals of science and
> 
> Statistical analysis is only useful if it's going to tell you something
> that matters for your decision criteria.

http://i.imgur.com/47D7zGq.png


Joe


From warren@kumari.net  Mon Apr 29 14:01:39 2013
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 3E75321F9977 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 14:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.064
X-Spam-Level: 
X-Spam-Status: No, score=-101.064 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_STRONG2=1.535, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r+kBe3DsGEqD for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 14:01:34 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99B5B21F997D for <ietf@ietf.org>; Mon, 29 Apr 2013 14:01:34 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.37]) by vimes.kumari.net (Postfix) with ESMTPSA id B5DE81B400B5; Mon, 29 Apr 2013 17:01:33 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Re: IETF Diversity Question on Berlin Registration?
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <4CA9ACF2-4728-4BDD-A94B-570E1533F4A1@hopcount.ca>
Date: Mon, 29 Apr 2013 17:01:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2D2CA6C-E141-430D-B095-0F22BF91E645@kumari.net>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com> <tsl61z56p12.fsf@mit.edu> <4CA9ACF2-4728-4BDD-A94B-570E1533F4A1@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1503)
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org, stbryant@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: Mon, 29 Apr 2013 21:01:39 -0000

On Apr 29, 2013, at 4:55 PM, Joe Abley <jabley@hopcount.ca> wrote:

>=20
> On 2013-04-29, at 16:49, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>=20
>>>>>>> "Stewart" =3D=3D Stewart Bryant <stbryant@cisco.com> writes:
>>=20
>>=20
>>   Stewart> Why would you disregard a statistical analysis? That seems
>>   Stewart> akin to disregarding the fundamentals of science and
>>=20
>> Statistical analysis is only useful if it's going to tell you =
something
>> that matters for your decision criteria.
>=20
> http://i.imgur.com/47D7zGq.png

Wow, that *was* useful, and has helped reinforce my belief that I chose =
the right browser -- "Think of the children, don't use IE."

Couldn't resist: http://xkcd.com/552/

W



>=20
>=20
> Joe
>=20

--
There were such things as dwarf gods. Dwarfs were not a naturally =
religious species, but in a world where pit props could crack without =
warning and pockets of fire damp could suddenly explode they'd seen the =
need for gods as the sort of supernatural equivalent of a hard hat. =
Besides, when you hit your thumb with an eight-pound hammer it's nice to =
be able to blaspheme. It takes a very special and straong-minded kind of =
atheist to jump up and down with their hand clasped under their other =
armpit and shout, "Oh, random-fluctuations-in-the-space-time-continuum!" =
or "Aaargh, primitive-and-outmoded-concept on a crutch!"
  -- Terry Pratchett



From hsantos@isdg.net  Mon Apr 29 14:17:12 2013
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 6E16221F9C3C for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 14:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.059
X-Spam-Level: 
X-Spam-Status: No, score=-102.059 tagged_above=-999 required=5 tests=[AWL=-0.324, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DhjNYX0h4WHv for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 14:17:07 -0700 (PDT)
Received: from groups.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 117DE21F9C37 for <ietf@ietf.org>; Mon, 29 Apr 2013 14:16:45 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1106; t=1367270201; h=Received:Received: Message-ID:Date:From:Subject:To:Organization:List-ID; bh=G2qWFFw d0MYW8LsdAUcGtLTHrLU=; b=rWvgy1tcTg0r6tzA6OpPUQuNPd4i3tlP3h0iROn davbL1nj/5qo76VXNV5kNGqOS9urA4x+kgPRoWd7p7V1g353dlfUzuIcEc0Jsild 3wfZcK7gtJcGOsrfyE4+6wR4wmtbRfMsSguEZE61E/byp4bETdmpBX1mXuBT1fuI gvJk=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 29 Apr 2013 17:16:41 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1768918925.5068.3308; Mon, 29 Apr 2013 17:16:40 -0400
Message-ID: <517EE2E3.3010003@isdg.net>
Date: Mon, 29 Apr 2013 17:15:15 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net>
In-Reply-To: <517EE00D.8050401@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Comment: Missing recipient address appended by wcSMTP router.
To: ietf@ietf.org
Cc: "<spfbis@ietf.org>" <spfbis@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, 29 Apr 2013 21:17:13 -0000

If anyone wishes to see one aspect of what is wrong with IETF Diversity, 
then see whats going on in SPF BIS WG where a key IETF cog essentially 
attempts to shutdown discussions and communications, attacks posters 
which by my estimate were making progress.

Progress is a status quo - DON'T CHANGE THE RFC4408 SPECIFICATION in 
SPFBIS.

Many in DNS community do not agree with the change of removing a long 
term migration path to a SPF RRTYPE.  In fact, not changing the existing 
specification would end the issue and hopefully satisfy all principles.

--
HLS

On 4/29/2013 5:03 PM, Dave Crocker wrote:
> Folks,
>
> This is one of those threads that will go on for as long as people seem
> to think they need to keep posting, but it won't make any "progress" or
> resolve any issues.
>
> For that matter, I have no idea what anyone thinks they are
> accomplishing by continuing to post on it, which raises the question of
> why they keep bothering.
>
> And 'bothering' is what this thread mostly /is/ doing, in reducing the
> S/N ratio.
>
> Please shut the thread down.
>
> d/


From mstjohns@comcast.net  Mon Apr 29 14:21:05 2013
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 543E421F9C50 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 14:21:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.804
X-Spam-Level: 
X-Spam-Status: No, score=-99.804 tagged_above=-999 required=5 tests=[AWL=0.633, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5i6ecUPs2Erw for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 14:21:00 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 16B3A21F9C2C for <ietf@ietf.org>; Mon, 29 Apr 2013 14:20:46 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta03.westchester.pa.mail.comcast.net with comcast id Vmhn1l0081c6gX853xLmnR; Mon, 29 Apr 2013 21:20:46 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta23.westchester.pa.mail.comcast.net with comcast id VxLl1l01J2kB7pQ3jxLmE3; Mon, 29 Apr 2013 21:20:46 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 29 Apr 2013 17:20:45 -0400
To: dcrocker@bbiw.net
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <517EDAB0.5020904@dcrocker.net>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <20130429190437.5669821F9AD6@ietfa.amsl.com> <517EDAB0.5020904@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1367270446; bh=dDNanSbRt/Jg7NkN/bakfuJ2MU2QEzhcoX8cK74dpN0=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=eSFjDYJbsIizSvuKTMiSm1RkCx6FSjUpaoLA3YHwebhGMAUR75Y8HBvssyzTgFmyy 1AMhYU4V6vFbucCQNsxYlrbNjlew1obYZMce51wiFfG9w/ipZ0dV67IOa92eYOMFcE QQKbbsf/mJ1kUVbwi2zZkZQdHS4LyYAEA/BzWgJcfEPUIwoamQd+yZlYWnNh9j4EFj w7qX87gG8ydK3hiAoWIk804SP5BaE/0/6xdNbbLhxcFDxYn7RaYyZDHRX9n7gsGXqQ cKvk72oph7bVinHlxkQY1MBl/RsIY7gILPIpNYpVlu3EqnKNuCaCFY1GHIHbnJ0cLm 2sGlQtNFFTfIQ==
Message-Id: <20130429212047.16B3A21F9C2C@ietfa.amsl.com>
Cc: dcrocker@bbiw.net, 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, 29 Apr 2013 21:21:05 -0000

At 04:40 PM 4/29/2013, Dave Crocker wrote:
>On 4/29/2013 12:04 PM, Michael StJohns wrote:
>>At 01:34 AM 4/29/2013, Dave Crocker wrote:
>>Actually, I don't think this is even a mostly correct statement -
>>that AD select chairs.
>
>It is a long-standing, simple, objective, unvarying management fact of IETF procedure:  ADs hire and fire wg chairs.

The AD's do have the final say.  No question.  But  "select" implies that the own the entire process of creating and staffing a WG. Nope.



>>Second point:
>>
>>You ignored most of the post and went directly to my last question
>
>I went to the meta-point that 

[Dave Crocker believes that]

>the line of discussion isn't methodologically meaningful or educationally useful.  Possibly you noticed one or two additional postings in this sub-thread asserting the same thing.

And one or two actually considering whether or not there was something to be gleaned from such data.

I'll take your opinion under advisement.  Thanks.

Mike



>d/
>
>-- 
>Dave Crocker
>Brandenburg InternetWorking
>bbiw.net



From dhc@dcrocker.net  Mon Apr 29 14:28:41 2013
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 1D74921F9C06 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 14:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level: 
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yXTX6+L4dIFH for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 14:28:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B4CDD21F9BFF for <ietf@ietf.org>; Mon, 29 Apr 2013 14:28:34 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3TLSUwZ008934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Apr 2013 14:28:34 -0700
Message-ID: <517EE5FA.7040203@dcrocker.net>
Date: Mon, 29 Apr 2013 14:28:26 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <20130429190437.5669821F9AD6@ietfa.amsl.com> <517EDAB0.5020904@dcrocker.net> <20130429212047.16B3A21F9C2C@ietfa.amsl.com>
In-Reply-To: <20130429212047.16B3A21F9C2C@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.66]); Mon, 29 Apr 2013 14:28:34 -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: Mon, 29 Apr 2013 21:28:41 -0000

On 4/29/2013 2:20 PM, Michael StJohns wrote:
> At 04:40 PM 4/29/2013, Dave Crocker wrote:
>>> Actually, I don't think this is even a mostly correct statement -
>>> that AD select chairs.
>>
>> It is a long-standing, simple, objective, unvarying management fact of IETF procedure:  ADs hire and fire wg chairs.
>
> The AD's do have the final say.  No question.  But  "select" implies that the own the entire process of creating and staffing a WG. Nope.


They do "own" it; that's a formal truth.

That they often delegate details and concur with self-organizing choices 
means nothing, in terms of their authority.

Don't confuse efficiency hacks with formal authority.


d/

ps. I'm sure this was really quite an important point to debate, 
relative to problems with IETF diversity and culture.

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From worley@shell01.TheWorld.com  Mon Apr 29 15:01:12 2013
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 C52CD21F9AF0 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 15:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.905
X-Spam-Level: 
X-Spam-Status: No, score=-2.905 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFBlXYE7Zuzj for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 15:01:07 -0700 (PDT)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id D519A21F9C37 for <ietf@ietf.org>; Mon, 29 Apr 2013 15:01:06 -0700 (PDT)
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 r3TM0Xwi025117 for <ietf@ietf.org>; Mon, 29 Apr 2013 18:00:35 -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 r3TM0WFU3760105 for <ietf@ietf.org>; Mon, 29 Apr 2013 18:00:32 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r3TM0Wn83733936; Mon, 29 Apr 2013 18:00:32 -0400 (EDT)
Date: Mon, 29 Apr 2013 18:00:32 -0400 (EDT)
Message-Id: <201304292200.r3TM0Wn83733936@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <20130426215354.EA0731A6D6@ld9781.wdf.sap.corp> (mrex@sap.com)
Subject: Re: W3C standards and the Hollyweb
References: <20130426215354.EA0731A6D6@ld9781.wdf.sap.corp>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 22:01:12 -0000

> From: mrex@sap.com (Martin Rex)
> 
> DRM system are evil in any way you look at it.
> 
> Originally, copyright was a conceived as a temporary (50yrs) monopoly.
> The protection period has in recent years been prolonged in many years
> to at least 70 years.
> [...]

I read an analysis somewhere that pointed out that DRM is evil in
considerably different ways than one naively thinks.  You tend to
think of DRM as a way of enforcing copyright.  But the real power of
DRM is in effectively eliminating the "right of first sale".

Currently, once you've bought a copy of a copyrighted work, you have
bought a physical object, the "copy", and that ownership gives you a
bundle containing a considerable number of rights, including the right
to sell the copy to someone else.

The real economic purpose of DRM is to be able to subdivide the bundle
of rights traditionally associated with the "copy" so that they can be
sold and priced individually.  Even better, since the "copy" may no
longer be transferrable between customers, different customers can be
charged different prices for the same thing.

The net effect is that the work creators can get larger aggregate
sales for the creation than before.  Which may or may not be a good
thing.  Wikipedia has a long article, "Price discrimination", on this.

Dale

From dharkins@lounge.org  Mon Apr 29 15:44:13 2013
Return-Path: <dharkins@lounge.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 876E921F9AF0 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 15:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wJM+AagN9x-e for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 15:44:06 -0700 (PDT)
Received: from colo.trepanning.net (colo.trepanning.net [69.55.226.174]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD2421F9BD8 for <ietf@ietf.org>; Mon, 29 Apr 2013 15:44:05 -0700 (PDT)
Received: from www.trepanning.net (localhost [127.0.0.1]) by colo.trepanning.net (Postfix) with ESMTP id 09D2C10224008; Mon, 29 Apr 2013 15:44:05 -0700 (PDT)
Received: from 69.12.173.8 (SquirrelMail authenticated user dharkins@lounge.org) by www.trepanning.net with HTTP; Mon, 29 Apr 2013 15:44:05 -0700 (PDT)
Message-ID: <7808af4e45c61ec0a4ac95c00dc986ae.squirrel@www.trepanning.net>
In-Reply-To: <517EE5FA.7040203@dcrocker.net>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <20130429190437.5669821F9AD6@ietfa.amsl.com> <517EDAB0.5020904@dcrocker.net> <20130429212047.16B3A21F9C2C@ietfa.amsl.com> <517EE5FA.7040203@dcrocker.net>
Date: Mon, 29 Apr 2013 15:44:05 -0700 (PDT)
Subject: Re: IETF Diversity Question on Berlin Registration?
From: "Dan Harkins" <dharkins@lounge.org>
To: dcrocker@bbiw.net
User-Agent: SquirrelMail/1.4.14 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
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, 29 Apr 2013 22:44:14 -0000

On Mon, April 29, 2013 2:28 pm, Dave Crocker wrote:
> On 4/29/2013 2:20 PM, Michael StJohns wrote:
>> At 04:40 PM 4/29/2013, Dave Crocker wrote:
>>>> Actually, I don't think this is even a mostly correct statement -
>>>> that AD select chairs.
>>>
>>> It is a long-standing, simple, objective, unvarying management fact of
>>> IETF procedure:  ADs hire and fire wg chairs.
>>
>> The AD's do have the final say.  No question.  But  "select" implies
>> that the own the entire process of creating and staffing a WG. Nope.
>
> They do "own" it; that's a formal truth.
>
> That they often delegate details and concur with self-organizing choices
> means nothing, in terms of their authority.

  But it might mean something in terms of the discussion at hand. If the
ADs are concurring with self-organizing choices as opposed to selecting
WG chairs, then they aren't really imposing a "looks like me" bias into
the selection process.

  Dan.



From marka@isc.org  Mon Apr 29 16:08:30 2013
Return-Path: <marka@isc.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 DF4E121F9B57; Mon, 29 Apr 2013 16:08:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.362
X-Spam-Level: 
X-Spam-Status: No, score=-1.362 tagged_above=-999 required=5 tests=[AWL=1.237,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gfBgoxfluPsp; Mon, 29 Apr 2013 16:08:26 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id D7E8621F9B7E; Mon, 29 Apr 2013 16:08:02 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id A4E4B5F9908; Mon, 29 Apr 2013 23:07:50 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367276879; bh=PgwmfzM8Id6Palz0ACxrhZ38ve5sdVEp1uvtHpx20Fk=; h=To:From:References:Subject:In-reply-to:Date; b=PsdBBhR7BHz0Xq8g4xcJSXfQ4EUtg6WihO0SpVB9Ux9LiiMNX0nxZQVODIvSj8gTR 24Z9ORdfn8a5Qt35vbEZATEpjm/DSGEe4+m3aESQGUzNrRDzTpG+Wmrv3DHlH/Qi/Z vXU6OfqxINrijk3vAkr+dlboDpz0H+SBoYRwKSVE=
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id E8513216C47; Mon, 29 Apr 2013 23:07:48 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 3D2833339511; Tue, 30 Apr 2013 09:07:42 +1000 (EST)
To: ietf@ietf.org, "<spfbis@ietf.org>" <spfbis@ietf.org>
From: Mark Andrews <marka@isc.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
In-reply-to: Your message of "Mon, 29 Apr 2013 17:15:15 -0400." <517EE2E3.3010003@isdg.net>
Date: Tue, 30 Apr 2013 09:07:42 +1000
Message-Id: <20130429230742.3D2833339511@drugs.dv.isc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 23:08:30 -0000

	The really annoying thing is that SPF is techically superior
	to TXT is lots of ways.

	1. It uniquely identifies the roll of the record.

	2. As SPF records are singletons you don't need to identify
	   and remove the old record when updating.  You can just
	   remove all SPF record and add the replacement.

	   For TXT you need to lookup the existing RRset, extract
	   the v=spf1 record from it.  You then need to create a
	   UPDATE message to delete just that record as well as add
	   the new TXT record.   You then have to hope that no one
	   else is performing a simultanious update as you may get
	   two TXT v=spf1 records in the RRset.

	The complains about using SPF is that there are broken
	firewalls and some servers drop queries for it, some registars
	don't support it.

	For firewalls, fix/replace the firewall if you intend to
	deploy SPF and it doesn't support it.  It is total !@##@#
	that firewall are incapable of handling new DNS record
	types.  New records we exected to occur from the very
	beginning and have been coming out regularly ever since the
	DNS was invented.  Firewall vendors that are incapable of
	handling new DNS types are incompetent and do not deserve
	repeat business.

	For servers than drop SPF queries they really are at the
	noise level.  When you identify one you complain to the
	owners of it.  Yes, that does work.  We needed to do that
	for AAAA records.

	For registrars, change registrar to one that does.

	Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From ted.ietf@gmail.com  Mon Apr 29 16:19:50 2013
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 3C59621F9BA6 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 16:19:50 -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, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C8TJ0Ih2HNQV for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 16:19:49 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id B21FE21F9B89 for <ietf@ietf.org>; Mon, 29 Apr 2013 16:19:49 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id ar20so8201889iec.0 for <ietf@ietf.org>; Mon, 29 Apr 2013 16:19:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=OMliIJ2H+SuDvvoey+qV3iHCv02iuSzlTVdNzSid0LM=; b=N+gafjOHwuEh3Bw0ZcAES5cLKqAORfqvlPhmHJ8HSLfSTa2ys3TNJUTeIYFXZcQkQ4 3Ee9+WuryE4rHEu/MjVFuoniSUyouoVhyGaZSKt6oqCBrKsNEEIGgHPSR33bpBPGsEkp OR7yF+JZYnjxnmuxT46G1U3kuyzmKyxOJ8Fgjc1HrYbgkBlBRFUbUUwGoE38bOqVIh+y sL4UlX15rrzmG4EFI4EHMkWRWKxae+CUD3HyYJ3CI0bz3BgEPJ4PYLY4CllxW8vZloVC jdr3A08HbLJqvk5jz/yMP8SXk6wXLmXRk4qzYvDIUx+/w5tlrcMBECTCzQ9iTVavOv7n N5zA==
MIME-Version: 1.0
X-Received: by 10.50.44.82 with SMTP id c18mr8718044igm.70.1367277589341; Mon, 29 Apr 2013 16:19:49 -0700 (PDT)
Received: by 10.42.211.16 with HTTP; Mon, 29 Apr 2013 16:19:49 -0700 (PDT)
Date: Mon, 29 Apr 2013 16:19:49 -0700
Message-ID: <CA+9kkMDLprWdE3P3DHbkdn3_isTyu6xuaizcnghaKcsEZuE=_g@mail.gmail.com>
Subject: Do we have an estimated date for completing the IESG selection process for this year?
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8f839caf05fdf004db881f5c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Apr 2013 23:19:50 -0000

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

So, this page: http://www.ietf.org/iesg/members.html still has TBD listed
for one of the transport ADs.  Is there a projected date for appointment at
this point?

Forgive the broad distribution of the question, but it's not clear whether
this question is solely directed at the nomcom, the IESG, the IAB or the
community at large.

regards,

Ted Hardie

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

So, this page: <a href=3D"http://www.ietf.org/iesg/members.html">http://www=
.ietf.org/iesg/members.html</a> still has TBD listed for one of the transpo=
rt ADs.=A0 Is there a projected date for appointment at this point?<br><br>=
Forgive the broad distribution of the question, but it&#39;s not clear whet=
her this question is solely directed at the nomcom, the IESG, the IAB or th=
e community at large.<br>
<br>regards,<br><br>Ted Hardie<br>

--e89a8f839caf05fdf004db881f5c--

From barryleiba.mailing.lists@gmail.com  Mon Apr 29 16:51:44 2013
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 A20BC21F9AED for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 16:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bTuJb9z71DAO for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 16:51:44 -0700 (PDT)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id E762621F9AE9 for <ietf@ietf.org>; Mon, 29 Apr 2013 16:51:43 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id cz11so3413823veb.21 for <ietf@ietf.org>; Mon, 29 Apr 2013 16:51:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8yxtRPxa2rpHQ5L5Zk1FU0yw3lunktl/jDTyX7MoAJU=; b=LRYWiJHGjXbweA2H9OwQNXcGdE38hcbuLTaM/onENbzTPyAcGhXoAA9cnhd0B8Yrqv sjgDBI7ytMMTMcIZJa6LuUhoa4k1LjYWrncvOiaKQ8ntlv9dcmLvX7Ejh+iD5izLoUke ESMDMoAzPzm3x7ggOafrWToccLVDl1u4WPI4QzpgYv62Op9uQbD+LZY1JJ3GGgWTY7ym xVcMR3+5FpX4fdrEdsQ44FdnNDQSoEIn0WAX8m+HA0cRC4o+y95g4TqIHQlD42DUovmn O37Z1uwV7vgHEBZ+h3R2zg0uAAfqw++bmErEI6HYhrKYmfXG3PjKyK9L0Ozg1eDbjekB 1+eg==
MIME-Version: 1.0
X-Received: by 10.52.233.34 with SMTP id tt2mr1584223vdc.70.1367279503331; Mon, 29 Apr 2013 16:51:43 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 29 Apr 2013 16:51:42 -0700 (PDT)
In-Reply-To: <7808af4e45c61ec0a4ac95c00dc986ae.squirrel@www.trepanning.net>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <20130429190437.5669821F9AD6@ietfa.amsl.com> <517EDAB0.5020904@dcrocker.net> <20130429212047.16B3A21F9C2C@ietfa.amsl.com> <517EE5FA.7040203@dcrocker.net> <7808af4e45c61ec0a4ac95c00dc986ae.squirrel@www.trepanning.net>
Date: Mon, 29 Apr 2013 19:51:42 -0400
X-Google-Sender-Auth: j0MAWkzl3ZO6lgmtxa7Cns4FYYU
Message-ID: <CAC4RtVBWU6t=AgXH+vuwzYLONxwi=teKwE2NnxuOtQU=-SWkXg@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Barry Leiba <barryleiba@computer.org>
To: Dan Harkins <dharkins@lounge.org>, Michael StJohns <mstjohns@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Dave Crocker <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: Mon, 29 Apr 2013 23:51:44 -0000

Mike:
>>>>> Actually, I don't think this is even a mostly correct statement -
>>>>> that AD select chairs.

Dave:
>>>> It is a long-standing, simple, objective, unvarying management fact of
>>>> IETF procedure:  ADs hire and fire wg chairs.

Mike:
>>> The AD's do have the final say.  No question.  But  "select" implies
>>> that the own the entire process of creating and staffing a WG. Nope.

Dave:
>> They do "own" it; that's a formal truth.
>>
>> That they often delegate details and concur with self-organizing choices
>> means nothing, in terms of their authority.

Dan:
> But it might mean something in terms of the discussion at hand. If the
> ADs are concurring with self-organizing choices as opposed to selecting
> WG chairs, then they aren't really imposing a "looks like me" bias into
> the selection process.

OK, here: I have to step in now.
Let me look at the new working group chairs and BoF chairs in the App
Area (as that's my area) since I've been an AD (one year, so far).

Chair changes:
APPSAWG: added Murray Kucherawy and Salvatore Loreto
CORE: added Andrew McGregor
IRI: added Peter Saint-Andre

New working groups
WEIRDS: Olaf Kolkman and Murray Kucherawy
SCIM: Morteza Ansari and Leif Johansson
SPFBIS: SM and Andrew Sullivan
IMAPMOVE: Ned Freed and Alexey Melnikov
JCARDCAL: Bert Greevenbosch and Peter Saint-Andre
QRESYNC: Dave Cridland and Eliot Lear

BoFs at IETF 83:
SCIM: Eliot Lear and Steve Bellovin
WEIRDS: Andrew Sullivan

BoFs at IETF 84:
DSII: Beth Pale and Ted Hardie

BoFs at IETF 86:
AGGSRV: Peter Saint-Andre
JSON: Joe Hildebrand

In all but one of these cases, we (the ADs) contacted people and
*asked* them to chair.  The exception was DSII and Beth Pale, but this
was not a working-group-forming BoF (and Ted was the one we
solicited).  For the SCIM working group, Morteza was one of the
proponents of the IETF 83 BoF, but he did not ask to be chair, and *I
asked him* only after consulting with folks and getting opinions that
suggested that he would be a good choice.  That has generally been my
approach and Pete's to finding chairs: getting opinions other than our
own.

We have a couple of other new chartering efforts in process, and we'll
be handling those similarly: selecting people we think will be
appropriate to chair those working groups.

Of course, if someone comes to us and says that they'd like to chair a
working group, we will take that into consideration.  But we most
certainly do NOT simply appoint people because they're technology
proponents, nor because they ask us to.  My sense of the rest of the
IESG is that they behave similarly.

I can tell you unequivocally that the ADs appoint the chairs, and "own
the entire process of [...] staffing a WG".  We are not just taking
the people who come to us and saying, "Yeah, sure, you'll do."  We
also want to find new chairs -- in the working-group chairs list
above, Andrew, Morteza, SM, Bert, and Dave are all first-time chairs.

Pete and I are also actively looking to increase the diversity in App
Area chairs -- perhaps you'll notice that we have *no* female chairs
in the App Area, at least partly because we have no women who are
active in the App Area just now.  We're working on that (and on other
diversity aspects) -- see, for example, the first item here:
http://www.ietf.org/proceedings/85/slides/slides-85-apparea-0.pdf

We're always eager for suggestions for people to be on our list of
potential chairs; please send such to <app-ads@tools.ietf.org>.  And,
yes, we *do* own the staffing process.

Barry, Applications AD

From sm@elandsys.com  Mon Apr 29 17:43:49 2013
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 4BCC821F9B65; Mon, 29 Apr 2013 17:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ubopfs4LF9XS; Mon, 29 Apr 2013 17:43:48 -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 7547221F9B63; Mon, 29 Apr 2013 17:43:48 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.145]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r3U0hYqO016663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Apr 2013 17:43:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367282626; bh=SlqggNBlhP8Zg8uSuIq/win+XpI83FvkNkls5U//OAA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=IjkVxojJxZDa/wGmycdU4MXeCSgq/bxU7q+1gHqAT/0BmbCZyj/iL5s018ah77+fG SLtkilJ1vWRYDq2cyLGJzZjR1UvNB0KYpEBOHZrMZshLJTtS+c4Pfxp9e6YMHl3YiG OlV/RuybPyk9XbSytC3UkLNDis5iTO1HS9sOlG5Y=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367282626; i=@elandsys.com; bh=SlqggNBlhP8Zg8uSuIq/win+XpI83FvkNkls5U//OAA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hn/FFST3VRDoJaXsjdcARqc0dR6WTH1WjHrzIMkem+Xa0KS8QcVlwXRnCK6cHVeTw YNKikbHhRlLlTVF9tIjwM2Z3goaHICTJO2I0QAAiK0uNU5fFUGgYRngDeLZCWzvNaD PCU5sYoWI54ybB0f/Jyt+9VXA5cgtaoantPxzGW0=
Message-Id: <6.2.5.6.2.20130429173928.0e94f6a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 29 Apr 2013 17:43:17 -0700
To: Hector Santos <hsantos@isdg.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
In-Reply-To: <517EE2E3.3010003@isdg.net>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: spfbis@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, 30 Apr 2013 00:43:49 -0000

Hi Hector,
At 14:15 29-04-2013, Hector Santos wrote:
>If anyone wishes to see one aspect of what is wrong with IETF 
>Diversity, then see whats going on in SPF BIS WG where a key IETF 
>cog essentially attempts to shutdown discussions and communications, 
>attacks posters which by my estimate were making progress.
>
>Progress is a status quo - DON'T CHANGE THE RFC4408 SPECIFICATION in SPFBIS.
>
>Many in DNS community do not agree with the change of removing a 
>long term migration path to a SPF RRTYPE.  In fact, not changing the 
>existing specification would end the issue and hopefully satisfy all 
>principles.

The following messages were posted to the SPFBIS mailing list:

http://www.ietf.org/mail-archive/web/spfbis/current/msg03593.html
http://www.ietf.org/mail-archive/web/spfbis/current/msg03598.html

It has also been mentioned that there are two long threads at:

http://www.ietf.org/mail-archive/web/spfbis/current/msg03412.html
http://www.ietf.org/mail-archive/web/dnsext/current/msg13025.html

Regards,
S. Moonesamy 


From brian.e.carpenter@gmail.com  Mon Apr 29 18:02:41 2013
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 0630521F9B53 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 18:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.8
X-Spam-Level: 
X-Spam-Status: No, score=-101.8 tagged_above=-999 required=5 tests=[AWL=1.800,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id li-yxC8muEdj for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 18:02:31 -0700 (PDT)
Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by ietfa.amsl.com (Postfix) with ESMTP id 11EF621F9AE0 for <ietf@ietf.org>; Mon, 29 Apr 2013 18:02:31 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id bj3so44870pad.6 for <ietf@ietf.org>; Mon, 29 Apr 2013 18:02:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=xsXSMC6SPq4DlkJFRn1vSJVBEgzU4ZyKXyG8gjN9ns4=; b=QbPDPCtY0dAcOC39F/Aa03FVnlnWJJwvN77W590RYYcIc+O6JrwpFboLVoWC1Fn1lX D14Y4jdGDJ1lKpcPza0EVHpZdDUG6740B2MyA2RzVS/B+nQbTwYbdJEBsBfzfci5teNH CB9sCK8B4IxkGqZI7/ykMo2b7gZ54Q7I96SUjMLW6v+8ipHTeUVpSzVVyPYrUhjvIisl 2HjISsf5SAGf4xR99u9re599xWmlYFjIp3RpHZJfdpGQB4GHK6WylAn0Squsfm53Nua1 UCVvAea5S9Q1We1V0796uKvPY0Z5hiN+d4jw5mp/+Z3OrKm8cHd5lRIUXBkLQj9Ka3Iz 0ryw==
X-Received: by 10.66.250.161 with SMTP id zd1mr45458979pac.141.1367283750838;  Mon, 29 Apr 2013 18:02:30 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id ya4sm26084155pbb.24.2013.04.29.18.02.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 29 Apr 2013 18:02:29 -0700 (PDT)
Message-ID: <517F1823.4070502@gmail.com>
Date: Tue, 30 Apr 2013 13:02:27 +1200
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: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com>	<51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie>	<7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org>	<38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net>	<516EB736.6060801@cisco.com>	<8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net>	<516EFC7E.90801@cisco.com>	<bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net>	<20130419014446.GC1113@mx1.yitter.info>	<1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net>	<005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net>	<5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org>	<20130429040539.5657221F93BA@ietfa.amsl.com>	<517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com>	<20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu>	<517ED235.9070202@cisco.com> <tsl61z56p12.fsf@mit.edu>
In-Reply-To: <tsl61z56p12.fsf@mit.edu>
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, 30 Apr 2013 01:02:41 -0000

On 30/04/2013 08:49, Sam Hartman wrote:
...
> Statistical analysis is only useful if it's going to tell you something
> that matters for your decision criteria.

Yes. And I would like to know, in statistical terms, whether
there are significant differences between (for example) the
M/F ratios among (a) IETF registrants, (b) active participants,
(c) WG chairs & secretaries and (d) I* members.

[Discussion on the objective definition of active participation
is deferred for now.]

The null hypothesis would be that no significant differences exist.
If that turns out to be true, we know that our problem is only lack of
diversity among registrants. If it turns out to be false, we know
that we have an internal problem of some kind as well.

   Brian

From hartmans@mit.edu  Mon Apr 29 19:33:28 2013
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 9C34A21F8B98 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 19:33:28 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJFN1Bt-bx1H for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 19:33:22 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 196CF21F9BD4 for <ietf@ietf.org>; Mon, 29 Apr 2013 19:33:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 8CA1E2027D; Mon, 29 Apr 2013 22:31:09 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VPcSSC6KzdFJ; Mon, 29 Apr 2013 22:31:08 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 29 Apr 2013 22:31:08 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id B02644499; Mon, 29 Apr 2013 22:33:01 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
References: <51687C0D.8090804@labn.net> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com> <tsl61z56p12.fsf@mit.edu> <517F1823.4070502@gmail.com>
Date: Mon, 29 Apr 2013 22:33:01 -0400
In-Reply-To: <517F1823.4070502@gmail.com> (Brian E. Carpenter's message of "Tue, 30 Apr 2013 13:02:27 +1200")
Message-ID: <tslzjwg4ujm.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.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 02:33:28 -0000

>>>>> "Brian" == Brian E Carpenter <brian.e.carpenter@gmail.com> writes:


    Brian> The null hypothesis would be that no significant differences
    Brian> exist.  If that turns out to be true, we know that our
    Brian> problem is only lack of diversity among registrants. If it
    Brian> turns out to be false, we know that we have an internal
    Brian> problem of some kind as well.

Yes.
I'll admit that that particular question--which is far more involved
than the numbers I've seen thrown around to date--is somewhat
interesting.

Although while it influences how I'd think about deciding on proposals,
there's no answer to that question that has a clear set of decisions for
me, even ignoring questions about methodology, definitions of
participants, etc, etc.

1) I may believe that increasing diversity among leadership so that the
leadership is more diverse than the population as a whole will help
increase diversity of the population.

2) I may believe that the diversity of the leadership  is more of a
problem in terms of either quality of spec or credibility of
organization than diversity of the participants/registrants.

But you've definitely started to get into a realm where the statistics
are more interesting to me.
And i'll drop this now, because I realize I'm only one participant and I
discussion that doesn't provide helpful information for me may well
provide useful information for others.

From abdussalambaryun@gmail.com  Mon Apr 29 22:19:51 2013
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 5CE5021F9C61 for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 22:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[AWL=-2.500,  BAYES_00=-2.599, GB_SUMOF=5, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 56A7M4wvuYDM for <ietf@ietfa.amsl.com>; Mon, 29 Apr 2013 22:19:49 -0700 (PDT)
Received: from mail-da0-x22a.google.com (mail-da0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2937921F9C5D for <ietf@ietf.org>; Mon, 29 Apr 2013 22:19:49 -0700 (PDT)
Received: by mail-da0-f42.google.com with SMTP id n15so80618dad.29 for <ietf@ietf.org>; Mon, 29 Apr 2013 22:19:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=EG2/tJkZ46x5CvlRK+7MwPXYWXs8KLpjnDNBM4TQTIQ=; b=JC3puhPLqNHNfO+FbNXEW1xd8nGtGZMDCib3R2zZUwGb33jrINId8qoyBQBVlH4Lkh 8mFpczrFiGxVcacMa4XE2tA0+WFH8WNY3GbwZpTvxQ0AiSh+U8JDLd7SAGQz1XtRVWJb h1ndGdoUG0+jMiogqudEplRbZjE1TSPOeeaR0OO+pUGXxnXEPnXrKVlezKS3y9cVr7KF R8UdWCQm8MkFnlk42mB3qFUX6CtXg2cG2nnjF/+61AAgrWXI/ZfZd2qQsuyPLZUPQ5sc 0tpMWgOJR7s6W68VP6Ir63gtCRoyVecdh6OXigHkdTYrn0Frk6al8GbPB8Q9Dl9DrgQw 5rjg==
MIME-Version: 1.0
X-Received: by 10.66.163.129 with SMTP id yi1mr28607720pab.93.1367299188866; Mon, 29 Apr 2013 22:19:48 -0700 (PDT)
Received: by 10.68.230.35 with HTTP; Mon, 29 Apr 2013 22:19:48 -0700 (PDT)
In-Reply-To: <CADnDZ89y6thHJOUVYDOzYxY2P=FUO0683s_hvz2GwQiZUmkMQg@mail.gmail.com>
References: <CADnDZ89y6thHJOUVYDOzYxY2P=FUO0683s_hvz2GwQiZUmkMQg@mail.gmail.com>
Date: Tue, 30 Apr 2013 07:19:48 +0200
Message-ID: <CADnDZ8_4TDZJr=_xY-JXyXujLnoWrdZs=iNnrVCw7PLR_LcDrA@mail.gmail.com>
Subject: Re: User Culture or Management (was Re: IETF Diversity Question on Berlin Registration?)
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: Tue, 30 Apr 2013 05:19:51 -0000

retransmited (not received at IETF or published)

On 4/29/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> Hi Mike,
>
> (sorry for my long message, will try to improve)
>
> I like the concept and reasoning of your message, and would like to
> add, is there other reasons for the results and conclusion your
> message got to? Is there something we can fix in the ietf-culture or
> ietf-procedures to make the diversity more established? I think that
> female managers/leaders are important to any world-organisation to get
> successful, and to be specific, I will recommend all world NPOs
> (Non-Profit Org.) need gender diversity (male or female, which one may
> be minority) at *least* 10-20 percent of management teams. An NPO with
> all male or all female management is not successful for the world of
> diverse *gender* and *users*. Management skills if gender-diversed
> will reflect better community involvement, choices, culture, and
> decisions.
>
>  IMHO, Organisation Management objectives are to make 1) *users*
> increase in numbers, 2) increase in diverse, and 3) increase in
> satisfaction. If only present/current users select the management
> there is no dought that their decisions reflect users-culture and
> awareness, but do they increase the three objectives.
>
> My concerns in the diversity issue is to focus on the diversity of
> *management-gender* and *ietf-users* to benefit future decisions and
> make *awareness* into the ietf-culture. Your message discussed both
> but for the diversity of ietf-users not in similar depth compared with
> gender, which I think you may help me understand/evaluate its diverse
> in ietf.
>
> Regards,
> AB
>
> ++++++++++++++++++++++++++++++++++
> From: Michael StJohns <mstjohns at comcast.net>
> To: Margaret Wasserman <mrw at lilacglade.org>,t.p. <daedulus at
> btconnect.com>
> Cc: ietf at ietf.org
> Date: Mon, 29 Apr 2013 00:05:37 -0400
>
>>Let's consider for a moment that this may not actually be the correct
>> question.  Instead, consider "Why the diversity of the IETF leadership
>> doesn't reflect the diversity of the set of the IETF WG chairs"?  I
>> believe this is a more representative candidate population for the IAB and
>> IESG.
>
> By my count (using the WG chairs picture page), there are 202 current
> working group chairs. Of these 15 are female  - or 7.4% of the
> population [It would be more reliable to do this for any WG chair in
> the last 5-10 years, but the above was readily available and I think
> provides at least the basis for discussion.  Anticipating the
> argument, I would assume for the sake of discussion a fairly similar
> percentage of ex-working group chairs per gender unless there is
> evidence to the contrary]
>
> There are 14 (current area directors plus the chair) members of the
> IESG, of which none are currently female.
>
> There are 12 current IAB members of which 1 member is female.
>
> Assuming perfect distribution, that would suggest that 14 * (15/202)
> or 1.03 IESG members should be female.
>
> Assuming perfect distribution, that would suggest that 12 * (15/202)
> or .89 IAB members should be female.
>
> Assuming perfect distribution, that would suggest that 26 * (15/202)
> or 1.93 IAB + IESG members should be female.
>
> And pretending for a moment that picks for the IAB and IESG are
> completely random from the candidate set of Working group chairs, the
> binomial distribution for 7.4% for 27 positions is:
>
> 0 - 12.5%, 1 - 27.0%, 2 - 28.1%, 3 or more - 32.5%.  (e.g. about 40%
> of the time, the IAB and IESG  combined will have 0 or 1 female
> members).
>
> for 7.4% for 15 positions  (IESG) is:
> 0 - 31.4%, 1 - 37.8%, 2 - 21.2%, 3 or more - 9.5%
>
> for 7.4% for 12 positions (IAB) is:
> 0 - 39.6%, 1 - 38.1%, 2 - 16.8%, 3 or more - 5.4%
>
>
> But the actual one you should consider is 7.4% for 14 positions
> (annual replacement):
> 0 - 34%, 1 - 38.1%, 2 - 19.9%, 3 or more - 8%.
>
> This last one says that for any given nomcom selection, assuming
> strict random selection, 72% of the time 0 or 1 females will be
> selected across both the IAB and IESG.  You should use this one as the
> actual compositions of the IAB/IESG are the sum of all the nomcom
> actions that have happened before.
>
> There are statistical tests to determine whether there is a
> statistically significant difference in populations, but my admittedly
> ancient memories of statistics suggest that the population size of the
> IAB/IESG is too small for a statistically valid comparison with either
> the WG chair population or the IETF population.
>
> Of course, the nomcom doesn't select and the confirming bodies do not
> confirm based on a roll of the dice.
> But looking at this analysis, it's unclear - for this one axis of
> gender - that the question "why the diversity of the IETF leadership
> does not reflect the diversity of the set of IETF WG chairs" has a
> more correct answer than "the luck of the draw".
>
> My base premise may be incorrect:  That you need to have been a WG
> chair prior to service as an IAB or IESG member.  I hope it isn't as I
> think this level of expertise is useful for success in these bodies.
>
> Assuming it is correct, then the next question is whether or not there
> is a significant difference in percentage of female attendees vs
> percentage of female working group chairs and is there a root cause
> for that difference that the IETF can address in a useful manner.
>
> Mike
>

From sm@elandsys.com  Tue Apr 30 02:03:40 2013
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 43E5D21F9B90 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 02:03:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XLOnLfITYFuB for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 02:03:39 -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 9391C21F9B85 for <ietf@ietf.org>; Tue, 30 Apr 2013 02:03:39 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.145]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r3U93LNt005685 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Apr 2013 02:03:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367312612; bh=w8bgOwtACfc5vB19id23GhP40UMuxpBmhNGfsXYZwPA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Kavx4MwH4Xnd86h3Zjhq9q9vzxsMQvRRMJejqkdI7P4aiokLz2Dwo63eJVON/Tmvk 8T+1oufkxCkE201zSl3b+ooPohDi2RUc+5vfxG/rGTIbZc93ApYTs6WtiFD2AIruSr GF+S6Dv1DTpEooVdraOBb9KlZm2DryvCI0e+pqdU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367312612; i=@elandsys.com; bh=w8bgOwtACfc5vB19id23GhP40UMuxpBmhNGfsXYZwPA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MqIJdof6ELF0jK4g/eP56pnuMQguW86qvbuaLKJgDa+gOXTGFdN/f/45HX28Xh10Y aVTyCst84vJ6D+aM8uDer3vjFiP5SkbRhUjeNfrQtvx8cfQEWm7K7tnBoUFju/Q1hO giHMl4q/y447DH9KFw/e1JQJbHT9vT41srp9tboE=
Message-Id: <6.2.5.6.2.20130430002217.074d4e00@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 30 Apr 2013 01:31:15 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: How does the IETF evolve to continue to be an effective, efficient, and relevant source of high quality Internet standards? Was: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <20130429201605.7BDFB21F9C03@ietfa.amsl.com>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E0656.1000803@dcrocker.net> <C91E67751B1EFF41B857DE2FE1F68ABA0C067236@tk5ex14mbxc272.redmond.corp.microsoft.com> <517E0BAF.2000207@dcrocker.net> <20130429191603.02DBF21F9BDE@ietfa.amsl.com> <52E44A75-A6A9-4778-A8E0-DDBDDCE7EB38@lilacglade.org> <20130429201605.7BDFB21F9C03@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: Tue, 30 Apr 2013 09:03:40 -0000

At 13:15 29-04-2013, Michael StJohns wrote:
>Let me ask a couple of specific questions of you.

I think that these are good questions.

>Who have you mentored in the past 5 years?  Have  they ended up as 
>working group chairs, or ADs or IAB members?   Do they mostly 
>represent under-represented groups?  How many of them were employed 
>by your employer (e.g. was this a work related task?)?

I don't mentor IETF participants as I consider everyone who does not 
have a title as a peer.  None of the peers I have interacted with 
ended up as working group chair, Area Director or IAB member.  I have 
not given much thought about whether most of the peers I have 
interacted with represent under-represented groups.  My guess is that 
it is a significant number.

>During your time as an AD, how many women did you arm twist/recruit 
>specifically  (or ask nicely) to take WG positions in your area (as 
>opposed to them coming to you or your co-AD)?

I do some things on behalf of the Applications Area directorate.  At 
the last IETF meeting I asked four women whether they would like to 
do some reviews.  There was one positive answer.  There are people of 
different ages.  There are people who work for a range of vendors on 
the directorate.  There are a few people who work for 
universities.  There are people who come from different parts of the 
world.  The list of reviewers and the work they perform is published 
on an IETF web site [1].  If anyone has questions about 
under-represented groups in relation to the directorate please post a 
message to this mailing list and I will reply.

Regards,
S. Moonesamy

1. http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate 


From bclaise@cisco.com  Tue Apr 30 03:48:23 2013
Return-Path: <bclaise@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 2460B21F9AF0; Tue, 30 Apr 2013 03:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.406
X-Spam-Level: 
X-Spam-Status: No, score=-10.406 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lxSTlJ2NK8Lq; Tue, 30 Apr 2013 03:48:19 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id B142C21F9AE4; Tue, 30 Apr 2013 03:48:18 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3UAm9wJ002917; Tue, 30 Apr 2013 12:48:09 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3UAlbwe007738; Tue, 30 Apr 2013 12:47:53 +0200 (CEST)
Message-ID: <517FA149.6050804@cisco.com>
Date: Tue, 30 Apr 2013 12:47:37 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: FW: Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data Model for Interface Management) to Proposed Standard
References: <CD9AEA34.2D304%ietfdbh@comcast.net>
In-Reply-To: <CD9AEA34.2D304%ietfdbh@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-netmod-interfaces-cfg.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>, NETMOD Working Group <netmod@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 10:48:23 -0000

Thanks Dave for your thorough review.
You have some very valid points.

I've not seen any replies from the author. Maybe he doesn't monitor this 
list. So, including some extra mailing lists.
Martin, NETMOD WG, can you please address David's points.

Note: there is also a reply from Tom Petch on this email. See 
http://www.ietf.org/mail-archive/web/ietf/current/msg78808.html

Regards, Benoit
> Hi,
>
> I have reviewed this document and feel that is almost ready for approval.
> This document defines a new data model in YANG format, based on the same
> information model as the Interfaces MIB module (IF-MIB).
> Effectively, the YANG model is a second (duplicative) standard for much of
> the same information.
> It is expected that devices may implement both the MIB and the YANG data
> models.
>
> My primary concern regards co-existence and synchronization across data
> models.
> I think this document would benefit from an Operational Considerations
> section that discusses synchronization, or an explanation why they might
> reasonably be out-of-sync.
> Here are a few points to consider:
>
> 1) the ifIndex of an interface is used within the YANG model, matching the
> ifIndex in IF-MIB.
> RFC2863 discusses the fact that ifIndex numbering might change during
> hot-swaps.
> This document does not discuss the need to ensure that IF-MIB ifIndex
> changes need to be reflected in the YANG model.
> The ifIndex in the YANG module must match that in IF-MIB (really, that in
> the underlying instrumentation).
> Failure to sync the ifIndex could lead NM applications to confuse which
> already-retrieved data records are related to which interface.
> This could cause an NM application to misinterpret/corrupt gathered
> trending information, and possibly to apply changes to the wrong
> interfaces.
>
> 2) ifType - can an interface be hot-swapped to use a different type? Is
> this discussed someplace?
>
> 3) ifType - the description says the value of this mandatory object MAY be
> initialized. What value should an NM application expect if it is NOT
> initialized?
>
> 4) enabled - "Systems that implement the IF-MIB use the value of this leaf
> to set IF-MIB.ifAdminStatus ..."; should this be a MAY/SHOULD/MUST? How
> will this coexist with SNMP-based NM applications? Is there potential for
> conflict? What if NETCONF sets this as enabled, then an operator sets it
> to disabled via SNMP?
> Does NETCONF know that its "enable" value (adminStatus) is out of date?
> (does it matter? See note 7).
> What if the NETCONF system directky changes the underlying instrumentation
> for adminstatus without going through the MIB?
>
> 5) is there a reason why "description" value MAY match IF-MIB ifAlias
> ***and MAY restrict the values***?
> Is there a particular use case for this lack of standardization of
> restrictions across data models?
> The persistence is a pretty important restriction related to the
> functionality of ifAlias, and the dynamism of ifIndex.
> If NETCONF is used to set the value, ignoring IF-MIB restrictions, what
> happens to IF-MIB ifAlias as a persistent "handle" to the interface?
>
> 6) What error is returned via NETCONF if YANG attempts to set a value that
> violates the SNMP agent implementation restrictions, and the SNMP agent
> refuses the requested SET operation to ifAlias?
> Is there a simple way for an operator to tell whether the implementation
> supports the restrictions (other than deliberately triggering an error)?
>
> 7) what should an NM application or operator do if the YANG oper-status
> and the IF-MIB operStatus differ?
> IF-MIB has substantial discussion of the relationship between
> ifAdminStatus and ifOperStatus. The YANG module doesn't have a comparable
> discussion.
> Given that there could e additional delay incurred between setting enable,
> updating ifAdminStatus, the change to ifOperStatus, and the update to
> oper-status, I recommend some mention in the description of enable and/or
> oper-status of the detailed description in RFC2863, and applicability to
> ietf-interfaces.
>
> 8) link-up-down-trap-enable: The text says this "indicates" whether traps
> should be generated for the interface; shouldn't this be "configures"?
>
> 9) persistence isn't discussed in the config object descriptions. Do they
> match the IF-MIB object persistences?
>
> 10) IF-MIB counters do not typically start at zero; a delta must be
> calculated. This is a common misunderstanding for new MIB developers and
> users.
> I don't see any comparable discussion related to ietf-interfaces counters.
> Where should one look for a discussion of YANG counter initialization
> values?
> Where should one look for a discussion of YANG counter rollover?
> It would help to have a discussion of how to utilize discontinuity_time
> and counters, especially for implementers not familiar with SNMP (and not
> implementing IF-MIB).
>
> 11) Is it expected that counters in ietf-interfaces and counters in IF-MIB
> are synchronized? Can an NM application reasonably compare two readings -
> one of in-octets and one of ifHCInOctets? If not, I think that should be
> made clear. (The reference clauses seem to link them)
>
> 12) From IF-MIB: "Discontinuities in the value of this counter can occur
> at re-initialization of the management system, and at other times as
> indicated by the value of ifCounterDiscontinuityTime."
> >From ietf-interfaces: "Discontinuities in the value of this counter can
> occur at re-initialization of the management system, and at other times as
> indicated by the value of 'discontinuity-time'."
> I think it is ambiguous as to whether both sets of text refer to the same
> "management system". Is the IF-MIB management-system the SNMP agent? And
> the YANG management-system the YANG server? Or are both based on the
> underlying (e.g, hardware or native) management system?
> Are ifCounterDiscontinuityTime and discontinuity-time synchronized or
> independent? If they are independent, then the YANG counters and MIB
> counters could contain very different values; it might help operators to
> have this pointed out. It might help implementers to know whether to try
> to synchronize them or not.
> Can an operator force restart of both YANG and MIB systems to force
> synchronization of counters?
>
> 13) Some of the questions about counters might be covered in yang-types;
> it would help if the imports clause indicated the relevant RFCs.
>
> 14) IF-MIB has both 32-bit and 64-bit counters; YANG only duplicates the
> 64-bit counters, generally. It might be good to discuss this in an
> Operations Considerations section, to explain some potential anomalies at
> the NM application side.
>
> 15) ietf-interfaces can modify the SNMP trap-enable settings; enabling
> lots of traps could impact denial of service, disabling could hide
> interface changes made by an attacker; it should probably be mentioned in
> security considerations.
>
> 16) Many operators/developers may have experience with IF-MIB, and some
> applications might be rewritten to utilize ietf-interfaces rather than (or
> to supplement) IF-MIB. Not all IF-MIB objects are reflected in
> ietf-interfaces; it might be helpful to show which IF-MIB objects are not
> mapped to ietf-interfaces, and discuss why, and whether comparable info
> can be derived using other YANG approaches.
>
> 17) The copyright in the module description clause needs updating.
>
> Hope this helps,
> --
> David Harrington
> Ietfdbh@comcast.net
> +1-603-828-1401
>
>
>
>
>
> On 4/19/13 9:25 AM, "The IESG" <noreply@ietf.org> wrote:
>
>> The IESG has received a request from the NETCONF Data Modeling Language
>> WG (netmod) to consider the following document:
>> - 'A YANG Data Model for Interface Management'
>>   <draft-ietf-netmod-interfaces-cfg-10.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 2013-05-03. 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 document defines a YANG data model for the management of network
>>    interfaces.  It is expected that interface type specific data models
>>    augment the generic interfaces data model defined in this document.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-netmod-interfaces-cfg/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-netmod-interfaces-cfg/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>
>


From abdussalambaryun@gmail.com  Tue Apr 30 03:55:29 2013
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 0CEAB21F9AF8 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 03:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.35
X-Spam-Level: 
X-Spam-Status: No, score=-1.35 tagged_above=-999 required=5 tests=[AWL=1.250,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bdd9pSV8CLu for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 03:55:28 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id A135321F9BCA for <ietf@ietf.org>; Tue, 30 Apr 2013 03:55:27 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id jt11so205207pbb.27 for <ietf@ietf.org>; Tue, 30 Apr 2013 03:55:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=zjt8yyfwZda5lPJz2Hsod6GGiRhXjXSf9CMtRJW91R0=; b=BAMqzONtb6xEJZo747LznhYEI0eKt0LT06P34kpISez0gNtp5dIc2rSZCF3oVbaY8t rb2WkYsbdCdDCky0H8raACjTlSwAddB70iZjBMwJqTNJi36KnNVislfKl846gyPLl4cW varnQX/VznWbmg0zcAXGnSYsOOJhJUnZiczJfgbhNY6c76LpbpsxwYsX8WIJtsr5F5hH PBiojttvtPxg1IG8q+hYYhgDmU6WPmHdrQQBeOiIGt59VokijpE3vAOHarIJobZVWHOg Tf46kBFmatJMr//9sqLPIP9AhOJheeKQd8diCGAr18MwjJ1hSicuQzTruwNIWPv7xeXN 2JbQ==
MIME-Version: 1.0
X-Received: by 10.68.213.1 with SMTP id no1mr75656667pbc.163.1367319327423; Tue, 30 Apr 2013 03:55:27 -0700 (PDT)
Received: by 10.68.230.35 with HTTP; Tue, 30 Apr 2013 03:55:27 -0700 (PDT)
Date: Tue, 30 Apr 2013 11:55:27 +0100
Message-ID: <CADnDZ89B=MOao1gCLu3CtwCC+epcjMPJUpjXi6CELXuL2gAxPQ@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8ff1c6bace42f604db91d650
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 10:55:29 -0000

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

I was counting femal ADs. I ment no female names in the AD list apears (in
my understandning I mybe wrong because in my culture some families name
their memebrs with names that we cannot notice gender). As I am a remote
participant I am not aware and may never notice difference. But I can refer
now for better than my count [1].

http://www.ietf.org/mail-archive/web/ietf/current/msg78882.html

AB

>On 19 April 2013 at 12:22 Abdussalam Baryun <abdussalambaryun at gmail.com>
wrote
on this list:

>> No name in the AD list appear so far, but if your the discuss-list is
>> right then it may be good progress, hoping for more names for
>> diversity.

>I count three ADs on the diversity discussion list at the moment.  Why is
my
count different from yours?

Adrian

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

<div dir=3D"ltr"><div>I was counting femal ADs. I ment no female names in t=
he AD list apears (in my understandning I mybe wrong because in my culture =
some families name their memebrs with names that we cannot notice gender). =
As I am a remote participant I am not aware and may never notice difference=
. But I can refer now for better than my count=A0[1].</div>
<div>=A0</div><div><a href=3D"http://www.ietf.org/mail-archive/web/ietf/cur=
rent/msg78882.html">http://www.ietf.org/mail-archive/web/ietf/current/msg78=
882.html</a></div><div>=A0</div><div>AB</div><div></div><div>&gt;On 19 Apri=
l 2013 at 12:22 Abdussalam Baryun &lt;abdussalambaryun at <a href=3D"http:/=
/gmail.com">gmail.com</a>&gt; wrote<br>
on this list:<br><br>&gt;&gt; No name in the AD list appear so far, but if =
your the discuss-list is<br>&gt;&gt; right then it may be good progress, ho=
ping for more names for<br>&gt;&gt; diversity. <br><br>&gt;I count three AD=
s on the diversity discussion list at the moment.=A0 Why is my<br>
count different from yours?<br><br>Adrian<br></div></div>

--e89a8ff1c6bace42f604db91d650--

From bclaise@cisco.com  Tue Apr 30 04:08:15 2013
Return-Path: <bclaise@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 19C0D21F9B2F; Tue, 30 Apr 2013 04:08:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.423
X-Spam-Level: 
X-Spam-Status: No, score=-10.423 tagged_above=-999 required=5 tests=[AWL=0.176, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id imQ3eK93HZaG; Tue, 30 Apr 2013 04:08:10 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 9C73721F9AF0; Tue, 30 Apr 2013 04:08:10 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3UB86hR005203; Tue, 30 Apr 2013 13:08:06 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3UB7Fm7023462; Tue, 30 Apr 2013 13:07:31 +0200 (CEST)
Message-ID: <517FA5E3.2010604@cisco.com>
Date: Tue, 30 Apr 2013 13:07:15 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Martin Bjorklund <mbj@tail-f.com>
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data Model for Interface Management) to Proposed Standard
References: <20130427.093659.369612374.mbj@tail-f.com> <20130430.122049.1111664509032933339.mbj@tail-f.com>
In-Reply-To: <20130430.122049.1111664509032933339.mbj@tail-f.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietfdbh@comcast.net, ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 11:08:15 -0000

Martin,

It's interesting to note that Dave came up with similar feedback as I 
had during my AD review.
And you had to re-explain this again, via email. This leads me to think 
that we need some more background information, typically in "Operational 
Considerations" section.
http://tools.ietf.org/html/draft-ietf-netmod-interfaces-cfg-10#section-4 
could be part of that new section, but other topics could/should be 
addressed:
- Failure to sync the ifIndex
- is there a reason why "description" value MAY match IF-MIB ifAlias 
***and MAY restrict the values***?
-  what should an NM application or operator do if the YANG oper-status 
and the IF-MIB operStatus differ?
- persistence
- Is it expected that counters in ietf-interfaces and counters in IF-MIB 
are synchronized?
- etc...

Basically addressing many points made by Dave

Regards, Benoit
> Hi David,
>
> Thank you for your detailed review!  Comments inline.
>
> David Harrington <ietfdbh@comcast.net> wrote:
>> Hi,
>>   
>> I have reviewed this document and feel that is almost ready for approval.
>> This document defines a new data model in YANG format, based on the same
>> information model as the Interfaces MIB module (IF-MIB).
>> Effectively, the YANG model is a second (duplicative) standard for much of
>> the same information.
>> It is expected that devices may implement both the MIB and the YANG data
>> models.
>>   
>> My primary concern regards co-existence and synchronization across data
>> models.
>> I think this document would benefit from an Operational Considerations
>> section that discusses synchronization, or an explanation why they might
>> reasonably be out-of-sync.
>> Here are a few points to consider:
>>   
>> 1) the ifIndex of an interface is used within the YANG model, matching the
>> ifIndex in IF-MIB.
>> RFC2863 discusses the fact that ifIndex numbering might change during
>> hot-swaps.
> Actually, RFC 2863 points out that a ifIndex must not be reused until
> after the following re-initialization of the network management
> system.
>
>> This document does not discuss the need to ensure that IF-MIB ifIndex
>> changes need to be reflected in the YANG model.
>> The ifIndex in the YANG module must match that in IF-MIB (really, that in
>> the underlying instrumentation).
> Absolutely!  That's the intention.  The description for the read-only
> leaf if-index says:
>
>             The ifIndex value for the ifEntry represented by this
>             interface.
>
>
>> Failure to sync the ifIndex could lead NM applications to confuse which
>> already-retrieved data records are related to which interface.
>> This could cause an NM application to misinterpret/corrupt gathered
>> trending information, and possibly to apply changes to the wrong
>> interfaces.
> Fully agree - this is why the if-index is present; to facilitate the
> mapping between the models.
>
>> 2) ifType - can an interface be hot-swapped to use a different type? Is
>> this discussed someplace?
> Hot-swapping sounds like a physical property.  The data model in this
> document can handle this -- provided the system physically supports
> it, of course.  Note that the type is a writable leaf just like
> others.  You can change it, but as with any other leaf a device that
> cannot support a particular change will reject it.
>
>> 3) ifType - the description says the value of this mandatory object MAY be
>> initialized. What value should an NM application expect if it is NOT
>> initialized?
> None.  And since it is mandatory, in this case the NM application has
> to explicitly provide the type.  If you write a completely generic NM
> application you would probably always provide the type, since you
> cannot count on the server auto-initializing it.  But if you *know*
> that the server auto-initialize the type, you don't have to provide
> it.
>
>> 4) enabled - "Systems that implement the IF-MIB use the value of this leaf
>> to set IF-MIB.ifAdminStatus ..."; should this be a MAY/SHOULD/MUST? How
>> will this coexist with SNMP-based NM applications? Is there potential for
>> conflict? What if NETCONF sets this as enabled, then an operator sets it
>> to disabled via SNMP?
>> Does NETCONF know that its "enable" value (adminStatus) is out of date?
>> (does it matter? See note 7).
>> What if the NETCONF system directky changes the underlying instrumentation
>> for adminstatus without going through the MIB?
> It is not clear to me if we can / want to require that these objects
> share the same instrumentation.
>
> Some of this might be b/c ifAdminStatus is a a bit unclear in some
> regards.  For example, it talks about how
>
>              per configuration information
>              retained by the managed system, ifAdminStatus is then
>              changed [...]
>
> I would assume (but this might be incorrect) that the "configuration
> information" could be things configured through the CLI for example,
> and this "configuration information" could thus also be the data
> defined in this YANG model.
>
> So it seems RFC 2863 makes a distinction between ifAdminStatus and
> what is actually configured.
>
> Also, the description of ifAdminStatus doesn't say anything about
> persistence, so it might be impossible to map this to the persistently
> stored configuration.
>
>
>> 5) is there a reason why "description" value MAY match IF-MIB ifAlias
>> ***and MAY restrict the values***?
>> Is there a particular use case for this lack of standardization of
>> restrictions across data models?
>> The persistence is a pretty important restriction related to the
>> functionality of ifAlias, and the dynamism of ifIndex.
>> If NETCONF is used to set the value, ignoring IF-MIB restrictions, what
>> happens to IF-MIB ifAlias as a persistent "handle" to the interface?
> The only reason the "description" leaf is mapped to ifAlias is b/c
> this is what many implementations do.  So we wanted to point out the
> differences in the value space for these objects so that implementers
> are aware of this.
>
> And of course it is not possible to actually set *ifAlias* and ignore
> its syntax constraints.  However, you can use non 7-bit ascii in
> "description", and in this case the "description" value cannot be used
> unmodified as ifAlias.
>
>> 6) What error is returned via NETCONF if YANG attempts to set a value that
>> violates the SNMP agent implementation restrictions, and the SNMP agent
>> refuses the requested SET operation to ifAlias?
> The draft says:
>
>             If a NETCONF server that implements this restriction is
>             sent a value that doesn't match the restriction, it MUST
>             reply with an rpc-error with the error-tag
>             'invalid-value'.
>
>> Is there a simple way for an operator to tell whether the implementation
>> supports the restrictions (other than deliberately triggering an error)?
> No.
>
>> 7) what should an NM application or operator do if the YANG oper-status
>> and the IF-MIB operStatus differ?
> The intention is that they share the same instrumentation.
>
>> IF-MIB has substantial discussion of the relationship between
>> ifAdminStatus and ifOperStatus. The YANG module doesn't have a comparable
>> discussion.
> Which text in the MIB do you mean?  There is some text in the
> description of "oper-status".
>
>> Given that there could e additional delay incurred between setting enable,
>> updating ifAdminStatus, the change to ifOperStatus, and the update to
>> oper-status, I recommend some mention in the description of enable and/or
>> oper-status of the detailed description in RFC2863, and applicability to
>> ietf-interfaces.
>>   
>> 8) link-up-down-trap-enable: The text says this "indicates" whether traps
>> should be generated for the interface; shouldn't this be "configures"?
> Or maybe "Controls ..."?
>
>> 9) persistence isn't discussed in the config object descriptions. Do they
>> match the IF-MIB object persistences?
> Persistence in NETCONF is different from SNMP, in general.  In NETCONF,
> the persistence is defined by the data store where you write the data.
>
>
>> 10) IF-MIB counters do not typically start at zero; a delta must be
>> calculated. This is a common misunderstanding for new MIB developers and
>> users.
>> I don't see any comparable discussion related to ietf-interfaces counters.
>> Where should one look for a discussion of YANG counter initialization
>> values?
>> Where should one look for a discussion of YANG counter rollover?
> The couters are defined as yang:counter32 and yang:counter64.  The
> "yang" prefix means module "ietf-yang-types".  This module is defined
> in RFC 6021.  This RFC discusses initial values and discontinuities.
>
> (ok, this was also suggested by yourself further below!)
>
>> It would help to have a discussion of how to utilize discontinuity_time
>> and counters, especially for implementers not familiar with SNMP (and not
>> implementing IF-MIB).
>>   
>> 11) Is it expected that counters in ietf-interfaces and counters in IF-MIB
>> are synchronized? Can an NM application reasonably compare two readings -
>> one of in-octets and one of ifHCInOctets? If not, I think that should be
>> made clear. (The reference clauses seem to link them)
> I think the intention is that the instrumentation is shared.  There is
> most probably a single hw register / kernel counter for these objects,
> and this is what will be used for these counters.
>
>> 12) From IF-MIB: "Discontinuities in the value of this counter can occur
>> at re-initialization of the management system, and at other times as
>> indicated by the value of ifCounterDiscontinuityTime."
>>  From ietf-interfaces: "Discontinuities in the value of this counter can
>> occur at re-initialization of the management system, and at other times as
>> indicated by the value of 'discontinuity-time'."
>> I think it is ambiguous as to whether both sets of text refer to the same
>> "management system". Is the IF-MIB management-system the SNMP agent? And
>> the YANG management-system the YANG server? Or are both based on the
>> underlying (e.g, hardware or native) management system?
> Good question!  The term is not defined anywhere (as far as I know),
> and thus there is some liberty in the interpretation of it.  But I
> don't think it matters.  It seems unlikely that a
> NM application sometimes reads a counter over SNMP and sometimes the
> same counter from the same device over NETCONF and then compare the
> values.
>
>> Are ifCounterDiscontinuityTime and discontinuity-time synchronized or
>> independent? If they are independent, then the YANG counters and MIB
>> counters could contain very different values; it might help operators to
>> have this pointed out.
> See above.  There is no requirement that they MUST be synchronized,
> but they surely can be.
>
>> It might help implementers to know whether to try
>> to synchronize them or not.
>> Can an operator force restart of both YANG and MIB systems to force
>> synchronization of counters?
> No.  Is there a way to force a restart of the "MIB system"?
>
>> 13) Some of the questions about counters might be covered in yang-types;
>> it would help if the imports clause indicated the relevant RFCs.
> As a comment?  I will raise this issue in the WG.
>
>> 14) IF-MIB has both 32-bit and 64-bit counters; YANG only duplicates the
>> 64-bit counters, generally. It might be good to discuss this in an
>> Operations Considerations section, to explain some potential anomalies at
>> the NM application side.
> In practice I don't think this is a problem.  It seems unlikely that a
> NM application sometimes reads a counter over SNMP and sometimes the
> same counter from the same device over NETCONF and then compare the
> values.
>
>> 15) ietf-interfaces can modify the SNMP trap-enable settings; enabling
>> lots of traps could impact denial of service, disabling could hide
>> interface changes made by an attacker; it should probably be mentioned in
>> security considerations.
> I was thinking we could simply reference the Security Considerations
> section in RFC 2863 for this, but it doesn't discuss this.
>
>> 16) Many operators/developers may have experience with IF-MIB, and some
>> applications might be rewritten to utilize ietf-interfaces rather than (or
>> to supplement) IF-MIB. Not all IF-MIB objects are reflected in
>> ietf-interfaces; it might be helpful to show which IF-MIB objects are not
>> mapped to ietf-interfaces, and discuss why, and whether comparable info
>> can be derived using other YANG approaches.
>>   
>> 17) The copyright in the module description clause needs updating.
> Ok.
>
>
>
> /martin
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>
>


From bclaise@cisco.com  Tue Apr 30 04:26:50 2013
Return-Path: <bclaise@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 3DE6D21F9ADF; Tue, 30 Apr 2013 04:26:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.438
X-Spam-Level: 
X-Spam-Status: No, score=-10.438 tagged_above=-999 required=5 tests=[AWL=0.161, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8zdKZOAgCCG; Tue, 30 Apr 2013 04:26:46 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id C3C8B21F9ADB; Tue, 30 Apr 2013 04:26:45 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3UBQcAt007230; Tue, 30 Apr 2013 13:26:38 +0200 (CEST)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3UBPkZw010198; Tue, 30 Apr 2013 13:26:01 +0200 (CEST)
Message-ID: <517FAA3A.4080904@cisco.com>
Date: Tue, 30 Apr 2013 13:25:46 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Martin Bjorklund <mbj@tail-f.com>
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data Model for Interface Management) to Proposed Standard
References: <20130427.093659.369612374.mbj@tail-f.com> <20130430.122049.1111664509032933339.mbj@tail-f.com> <517FA5E3.2010604@cisco.com>
In-Reply-To: <517FA5E3.2010604@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietfdbh@comcast.net, ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 11:26:50 -0000

On 30/04/2013 13:07, Benoit Claise wrote:
> Martin,
>
> It's interesting to note that Dave came up with similar feedback as I 
> had during my AD review.
> And you had to re-explain this again, via email. This leads me to 
> think that we need some more background information, typically in 
> "Operational Considerations" section.
> http://tools.ietf.org/html/draft-ietf-netmod-interfaces-cfg-10#section-4 
> could be part of that new section, but other topics could/should be 
> addressed:
> - Failure to sync the ifIndex
> - is there a reason why "description" value MAY match IF-MIB ifAlias 
> ***and MAY restrict the values***?
> -  what should an NM application or operator do if the YANG 
> oper-status and the IF-MIB operStatus differ?
> - persistence
> - Is it expected that counters in ietf-interfaces and counters in 
> IF-MIB are synchronized?
> - etc...
>
> Basically addressing many points made by Dave
And I see that Carlos, part of the "Re: RtgDir review: 
draft-ietf-netmod-interfaces-cfg-10.txt" feedback has got some similar  
points.
- physical versus virtual interfaces
- location
- counter32 and counter64, and mapping to the MIB OIDs
- etc...

That reinforces in my thinking that we need an "operational 
considerations" section.

Regards, Benoit
>
> Regards, Benoit
>> Hi David,
>>
>> Thank you for your detailed review!  Comments inline.
>>
>> David Harrington <ietfdbh@comcast.net> wrote:
>>> Hi,
>>>   I have reviewed this document and feel that is almost ready for 
>>> approval.
>>> This document defines a new data model in YANG format, based on the 
>>> same
>>> information model as the Interfaces MIB module (IF-MIB).
>>> Effectively, the YANG model is a second (duplicative) standard for 
>>> much of
>>> the same information.
>>> It is expected that devices may implement both the MIB and the YANG 
>>> data
>>> models.
>>>   My primary concern regards co-existence and synchronization across 
>>> data
>>> models.
>>> I think this document would benefit from an Operational Considerations
>>> section that discusses synchronization, or an explanation why they 
>>> might
>>> reasonably be out-of-sync.
>>> Here are a few points to consider:
>>>   1) the ifIndex of an interface is used within the YANG model, 
>>> matching the
>>> ifIndex in IF-MIB.
>>> RFC2863 discusses the fact that ifIndex numbering might change during
>>> hot-swaps.
>> Actually, RFC 2863 points out that a ifIndex must not be reused until
>> after the following re-initialization of the network management
>> system.
>>
>>> This document does not discuss the need to ensure that IF-MIB ifIndex
>>> changes need to be reflected in the YANG model.
>>> The ifIndex in the YANG module must match that in IF-MIB (really, 
>>> that in
>>> the underlying instrumentation).
>> Absolutely!  That's the intention.  The description for the read-only
>> leaf if-index says:
>>
>>             The ifIndex value for the ifEntry represented by this
>>             interface.
>>
>>
>>> Failure to sync the ifIndex could lead NM applications to confuse which
>>> already-retrieved data records are related to which interface.
>>> This could cause an NM application to misinterpret/corrupt gathered
>>> trending information, and possibly to apply changes to the wrong
>>> interfaces.
>> Fully agree - this is why the if-index is present; to facilitate the
>> mapping between the models.
>>
>>> 2) ifType - can an interface be hot-swapped to use a different type? Is
>>> this discussed someplace?
>> Hot-swapping sounds like a physical property.  The data model in this
>> document can handle this -- provided the system physically supports
>> it, of course.  Note that the type is a writable leaf just like
>> others.  You can change it, but as with any other leaf a device that
>> cannot support a particular change will reject it.
>>
>>> 3) ifType - the description says the value of this mandatory object 
>>> MAY be
>>> initialized. What value should an NM application expect if it is NOT
>>> initialized?
>> None.  And since it is mandatory, in this case the NM application has
>> to explicitly provide the type.  If you write a completely generic NM
>> application you would probably always provide the type, since you
>> cannot count on the server auto-initializing it.  But if you *know*
>> that the server auto-initialize the type, you don't have to provide
>> it.
>>
>>> 4) enabled - "Systems that implement the IF-MIB use the value of 
>>> this leaf
>>> to set IF-MIB.ifAdminStatus ..."; should this be a MAY/SHOULD/MUST? How
>>> will this coexist with SNMP-based NM applications? Is there 
>>> potential for
>>> conflict? What if NETCONF sets this as enabled, then an operator 
>>> sets it
>>> to disabled via SNMP?
>>> Does NETCONF know that its "enable" value (adminStatus) is out of date?
>>> (does it matter? See note 7).
>>> What if the NETCONF system directky changes the underlying 
>>> instrumentation
>>> for adminstatus without going through the MIB?
>> It is not clear to me if we can / want to require that these objects
>> share the same instrumentation.
>>
>> Some of this might be b/c ifAdminStatus is a a bit unclear in some
>> regards.  For example, it talks about how
>>
>>              per configuration information
>>              retained by the managed system, ifAdminStatus is then
>>              changed [...]
>>
>> I would assume (but this might be incorrect) that the "configuration
>> information" could be things configured through the CLI for example,
>> and this "configuration information" could thus also be the data
>> defined in this YANG model.
>>
>> So it seems RFC 2863 makes a distinction between ifAdminStatus and
>> what is actually configured.
>>
>> Also, the description of ifAdminStatus doesn't say anything about
>> persistence, so it might be impossible to map this to the persistently
>> stored configuration.
>>
>>
>>> 5) is there a reason why "description" value MAY match IF-MIB ifAlias
>>> ***and MAY restrict the values***?
>>> Is there a particular use case for this lack of standardization of
>>> restrictions across data models?
>>> The persistence is a pretty important restriction related to the
>>> functionality of ifAlias, and the dynamism of ifIndex.
>>> If NETCONF is used to set the value, ignoring IF-MIB restrictions, what
>>> happens to IF-MIB ifAlias as a persistent "handle" to the interface?
>> The only reason the "description" leaf is mapped to ifAlias is b/c
>> this is what many implementations do.  So we wanted to point out the
>> differences in the value space for these objects so that implementers
>> are aware of this.
>>
>> And of course it is not possible to actually set *ifAlias* and ignore
>> its syntax constraints.  However, you can use non 7-bit ascii in
>> "description", and in this case the "description" value cannot be used
>> unmodified as ifAlias.
>>
>>> 6) What error is returned via NETCONF if YANG attempts to set a 
>>> value that
>>> violates the SNMP agent implementation restrictions, and the SNMP agent
>>> refuses the requested SET operation to ifAlias?
>> The draft says:
>>
>>             If a NETCONF server that implements this restriction is
>>             sent a value that doesn't match the restriction, it MUST
>>             reply with an rpc-error with the error-tag
>>             'invalid-value'.
>>
>>> Is there a simple way for an operator to tell whether the 
>>> implementation
>>> supports the restrictions (other than deliberately triggering an 
>>> error)?
>> No.
>>
>>> 7) what should an NM application or operator do if the YANG oper-status
>>> and the IF-MIB operStatus differ?
>> The intention is that they share the same instrumentation.
>>
>>> IF-MIB has substantial discussion of the relationship between
>>> ifAdminStatus and ifOperStatus. The YANG module doesn't have a 
>>> comparable
>>> discussion.
>> Which text in the MIB do you mean?  There is some text in the
>> description of "oper-status".
>>
>>> Given that there could e additional delay incurred between setting 
>>> enable,
>>> updating ifAdminStatus, the change to ifOperStatus, and the update to
>>> oper-status, I recommend some mention in the description of enable 
>>> and/or
>>> oper-status of the detailed description in RFC2863, and 
>>> applicability to
>>> ietf-interfaces.
>>>   8) link-up-down-trap-enable: The text says this "indicates" 
>>> whether traps
>>> should be generated for the interface; shouldn't this be "configures"?
>> Or maybe "Controls ..."?
>>
>>> 9) persistence isn't discussed in the config object descriptions. Do 
>>> they
>>> match the IF-MIB object persistences?
>> Persistence in NETCONF is different from SNMP, in general.  In NETCONF,
>> the persistence is defined by the data store where you write the data.
>>
>>
>>> 10) IF-MIB counters do not typically start at zero; a delta must be
>>> calculated. This is a common misunderstanding for new MIB developers 
>>> and
>>> users.
>>> I don't see any comparable discussion related to ietf-interfaces 
>>> counters.
>>> Where should one look for a discussion of YANG counter initialization
>>> values?
>>> Where should one look for a discussion of YANG counter rollover?
>> The couters are defined as yang:counter32 and yang:counter64. The
>> "yang" prefix means module "ietf-yang-types".  This module is defined
>> in RFC 6021.  This RFC discusses initial values and discontinuities.
>>
>> (ok, this was also suggested by yourself further below!)
>>
>>> It would help to have a discussion of how to utilize discontinuity_time
>>> and counters, especially for implementers not familiar with SNMP 
>>> (and not
>>> implementing IF-MIB).
>>>   11) Is it expected that counters in ietf-interfaces and counters 
>>> in IF-MIB
>>> are synchronized? Can an NM application reasonably compare two 
>>> readings -
>>> one of in-octets and one of ifHCInOctets? If not, I think that 
>>> should be
>>> made clear. (The reference clauses seem to link them)
>> I think the intention is that the instrumentation is shared. There is
>> most probably a single hw register / kernel counter for these objects,
>> and this is what will be used for these counters.
>>
>>> 12) From IF-MIB: "Discontinuities in the value of this counter can 
>>> occur
>>> at re-initialization of the management system, and at other times as
>>> indicated by the value of ifCounterDiscontinuityTime."
>>>  From ietf-interfaces: "Discontinuities in the value of this counter 
>>> can
>>> occur at re-initialization of the management system, and at other 
>>> times as
>>> indicated by the value of 'discontinuity-time'."
>>> I think it is ambiguous as to whether both sets of text refer to the 
>>> same
>>> "management system". Is the IF-MIB management-system the SNMP agent? 
>>> And
>>> the YANG management-system the YANG server? Or are both based on the
>>> underlying (e.g, hardware or native) management system?
>> Good question!  The term is not defined anywhere (as far as I know),
>> and thus there is some liberty in the interpretation of it.  But I
>> don't think it matters.  It seems unlikely that a
>> NM application sometimes reads a counter over SNMP and sometimes the
>> same counter from the same device over NETCONF and then compare the
>> values.
>>
>>> Are ifCounterDiscontinuityTime and discontinuity-time synchronized or
>>> independent? If they are independent, then the YANG counters and MIB
>>> counters could contain very different values; it might help 
>>> operators to
>>> have this pointed out.
>> See above.  There is no requirement that they MUST be synchronized,
>> but they surely can be.
>>
>>> It might help implementers to know whether to try
>>> to synchronize them or not.
>>> Can an operator force restart of both YANG and MIB systems to force
>>> synchronization of counters?
>> No.  Is there a way to force a restart of the "MIB system"?
>>
>>> 13) Some of the questions about counters might be covered in 
>>> yang-types;
>>> it would help if the imports clause indicated the relevant RFCs.
>> As a comment?  I will raise this issue in the WG.
>>
>>> 14) IF-MIB has both 32-bit and 64-bit counters; YANG only duplicates 
>>> the
>>> 64-bit counters, generally. It might be good to discuss this in an
>>> Operations Considerations section, to explain some potential 
>>> anomalies at
>>> the NM application side.
>> In practice I don't think this is a problem.  It seems unlikely that a
>> NM application sometimes reads a counter over SNMP and sometimes the
>> same counter from the same device over NETCONF and then compare the
>> values.
>>
>>> 15) ietf-interfaces can modify the SNMP trap-enable settings; enabling
>>> lots of traps could impact denial of service, disabling could hide
>>> interface changes made by an attacker; it should probably be 
>>> mentioned in
>>> security considerations.
>> I was thinking we could simply reference the Security Considerations
>> section in RFC 2863 for this, but it doesn't discuss this.
>>
>>> 16) Many operators/developers may have experience with IF-MIB, and some
>>> applications might be rewritten to utilize ietf-interfaces rather 
>>> than (or
>>> to supplement) IF-MIB. Not all IF-MIB objects are reflected in
>>> ietf-interfaces; it might be helpful to show which IF-MIB objects 
>>> are not
>>> mapped to ietf-interfaces, and discuss why, and whether comparable info
>>> can be derived using other YANG approaches.
>>>   17) The copyright in the module description clause needs updating.
>> Ok.
>>
>>
>>
>> /martin
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>>
>>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>
>


From cpignata@cisco.com  Tue Apr 30 07:33:36 2013
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 5F12521F9AAF; Tue, 30 Apr 2013 07:33:36 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e4Fd4ppuS5Il; Tue, 30 Apr 2013 07:33:31 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 3D90021F9AA5; Tue, 30 Apr 2013 07:33:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14735; q=dns/txt; s=iport; t=1367332411; x=1368542011; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=mPRG20mYryJ6tnGpXhzRcVhP0KDkw5/tjhlNHsbMYe8=; b=kzQ4zoFAPX1h+WmhAJlWHGiFUXvkB2X+hM8H6EWWMQY6pKFWgAXuHqVN fs+mRRwV7jym94m5zx+bPL6zo+9wROzF70wKPrlh0bVncwtfKgcq3Fua/ DXu/9eLEmjktLO1q8LkmkEQu8GjOXSf4uvNpgv6CDAPm298wG+cY7x0T2 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAATVf1GtJV2Z/2dsb2JhbABSgwc2vlx+FnSCHwEBAQMBAQEBRCcEBwULAgEIGAoZCycLJQIEDgUIAYdxAwkGDLE9gTyFFwiHZI1XEH8CMQIFgm9hA4hdj2+QB4FVgTiBcjU
X-IronPort-AV: E=Sophos;i="4.87,582,1363132800"; d="scan'208";a="201816906"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 30 Apr 2013 14:33:30 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r3UEXURl015248 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 30 Apr 2013 14:33:30 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.192]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Tue, 30 Apr 2013 09:33:29 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Benoit Claise (bclaise)" <bclaise@cisco.com>
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data Model for Interface Management) to Proposed Standard
Thread-Topic: [netmod] Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data Model for Interface Management) to Proposed Standard
Thread-Index: AQHORa+u8LmgzJGA90uA8V28u5gtcA==
Date: Tue, 30 Apr 2013 14:33:29 +0000
Message-ID: <95067C434CE250468B77282634C96ED322AF8E8F@xmb-aln-x02.cisco.com>
References: <20130427.093659.369612374.mbj@tail-f.com> <20130430.122049.1111664509032933339.mbj@tail-f.com> <517FA5E3.2010604@cisco.com> <517FAA3A.4080904@cisco.com>
In-Reply-To: <517FAA3A.4080904@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.150.44.101]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <A4B6E537D90F824694614BD19A0CCAAB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Martin Bjorklund <mbj@tail-f.com>, "ietfdbh@comcast.net" <ietfdbh@comcast.net>, "ietf@ietf.org" <ietf@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 14:33:36 -0000

On Apr 30, 2013, at 7:25 AM, Benoit Claise <bclaise@cisco.com> wrote:

> On 30/04/2013 13:07, Benoit Claise wrote:
>> Martin,
>>=20
>> It's interesting to note that Dave came up with similar feedback as I ha=
d during my AD review.
>> And you had to re-explain this again, via email. This leads me to think =
that we need some more background information, typically in "Operational Co=
nsiderations" section.
>> http://tools.ietf.org/html/draft-ietf-netmod-interfaces-cfg-10#section-4=
 could be part of that new section, but other topics could/should be addres=
sed:
>> - Failure to sync the ifIndex
>> - is there a reason why "description" value MAY match IF-MIB ifAlias ***=
and MAY restrict the values***?
>> -  what should an NM application or operator do if the YANG oper-status =
and the IF-MIB operStatus differ?
>> - persistence
>> - Is it expected that counters in ietf-interfaces and counters in IF-MIB=
 are synchronized?
>> - etc...
>>=20
>> Basically addressing many points made by Dave
> And I see that Carlos, part of the "Re: RtgDir review: draft-ietf-netmod-=
interfaces-cfg-10.txt" feedback has got some similar  points.
> - physical versus virtual interfaces
> - location
> - counter32 and counter64, and mapping to the MIB OIDs
> - etc...
>=20
> That reinforces in my thinking that we need an "operational consideration=
s" section.

+1.

I think that an "Operational Considerations" addressing these issues would =
be a most useful addition to this document.

For context, full review at http://www.ietf.org/mail-archive/web/netmod/cur=
rent/msg08035.html

Thanks,

-- Carlos.

>=20
> Regards, Benoit
>>=20
>> Regards, Benoit
>>> Hi David,
>>>=20
>>> Thank you for your detailed review!  Comments inline.
>>>=20
>>> David Harrington <ietfdbh@comcast.net> wrote:
>>>> Hi,
>>>>  I have reviewed this document and feel that is almost ready for appro=
val.
>>>> This document defines a new data model in YANG format, based on the sa=
me
>>>> information model as the Interfaces MIB module (IF-MIB).
>>>> Effectively, the YANG model is a second (duplicative) standard for muc=
h of
>>>> the same information.
>>>> It is expected that devices may implement both the MIB and the YANG da=
ta
>>>> models.
>>>>  My primary concern regards co-existence and synchronization across da=
ta
>>>> models.
>>>> I think this document would benefit from an Operational Considerations
>>>> section that discusses synchronization, or an explanation why they mig=
ht
>>>> reasonably be out-of-sync.
>>>> Here are a few points to consider:
>>>>  1) the ifIndex of an interface is used within the YANG model, matchin=
g the
>>>> ifIndex in IF-MIB.
>>>> RFC2863 discusses the fact that ifIndex numbering might change during
>>>> hot-swaps.
>>> Actually, RFC 2863 points out that a ifIndex must not be reused until
>>> after the following re-initialization of the network management
>>> system.
>>>=20
>>>> This document does not discuss the need to ensure that IF-MIB ifIndex
>>>> changes need to be reflected in the YANG model.
>>>> The ifIndex in the YANG module must match that in IF-MIB (really, that=
 in
>>>> the underlying instrumentation).
>>> Absolutely!  That's the intention.  The description for the read-only
>>> leaf if-index says:
>>>=20
>>>            The ifIndex value for the ifEntry represented by this
>>>            interface.
>>>=20
>>>=20
>>>> Failure to sync the ifIndex could lead NM applications to confuse whic=
h
>>>> already-retrieved data records are related to which interface.
>>>> This could cause an NM application to misinterpret/corrupt gathered
>>>> trending information, and possibly to apply changes to the wrong
>>>> interfaces.
>>> Fully agree - this is why the if-index is present; to facilitate the
>>> mapping between the models.
>>>=20
>>>> 2) ifType - can an interface be hot-swapped to use a different type? I=
s
>>>> this discussed someplace?
>>> Hot-swapping sounds like a physical property.  The data model in this
>>> document can handle this -- provided the system physically supports
>>> it, of course.  Note that the type is a writable leaf just like
>>> others.  You can change it, but as with any other leaf a device that
>>> cannot support a particular change will reject it.
>>>=20
>>>> 3) ifType - the description says the value of this mandatory object MA=
Y be
>>>> initialized. What value should an NM application expect if it is NOT
>>>> initialized?
>>> None.  And since it is mandatory, in this case the NM application has
>>> to explicitly provide the type.  If you write a completely generic NM
>>> application you would probably always provide the type, since you
>>> cannot count on the server auto-initializing it.  But if you *know*
>>> that the server auto-initialize the type, you don't have to provide
>>> it.
>>>=20
>>>> 4) enabled - "Systems that implement the IF-MIB use the value of this =
leaf
>>>> to set IF-MIB.ifAdminStatus ..."; should this be a MAY/SHOULD/MUST? Ho=
w
>>>> will this coexist with SNMP-based NM applications? Is there potential =
for
>>>> conflict? What if NETCONF sets this as enabled, then an operator sets =
it
>>>> to disabled via SNMP?
>>>> Does NETCONF know that its "enable" value (adminStatus) is out of date=
?
>>>> (does it matter? See note 7).
>>>> What if the NETCONF system directky changes the underlying instrumenta=
tion
>>>> for adminstatus without going through the MIB?
>>> It is not clear to me if we can / want to require that these objects
>>> share the same instrumentation.
>>>=20
>>> Some of this might be b/c ifAdminStatus is a a bit unclear in some
>>> regards.  For example, it talks about how
>>>=20
>>>             per configuration information
>>>             retained by the managed system, ifAdminStatus is then
>>>             changed [...]
>>>=20
>>> I would assume (but this might be incorrect) that the "configuration
>>> information" could be things configured through the CLI for example,
>>> and this "configuration information" could thus also be the data
>>> defined in this YANG model.
>>>=20
>>> So it seems RFC 2863 makes a distinction between ifAdminStatus and
>>> what is actually configured.
>>>=20
>>> Also, the description of ifAdminStatus doesn't say anything about
>>> persistence, so it might be impossible to map this to the persistently
>>> stored configuration.
>>>=20
>>>=20
>>>> 5) is there a reason why "description" value MAY match IF-MIB ifAlias
>>>> ***and MAY restrict the values***?
>>>> Is there a particular use case for this lack of standardization of
>>>> restrictions across data models?
>>>> The persistence is a pretty important restriction related to the
>>>> functionality of ifAlias, and the dynamism of ifIndex.
>>>> If NETCONF is used to set the value, ignoring IF-MIB restrictions, wha=
t
>>>> happens to IF-MIB ifAlias as a persistent "handle" to the interface?
>>> The only reason the "description" leaf is mapped to ifAlias is b/c
>>> this is what many implementations do.  So we wanted to point out the
>>> differences in the value space for these objects so that implementers
>>> are aware of this.
>>>=20
>>> And of course it is not possible to actually set *ifAlias* and ignore
>>> its syntax constraints.  However, you can use non 7-bit ascii in
>>> "description", and in this case the "description" value cannot be used
>>> unmodified as ifAlias.
>>>=20
>>>> 6) What error is returned via NETCONF if YANG attempts to set a value =
that
>>>> violates the SNMP agent implementation restrictions, and the SNMP agen=
t
>>>> refuses the requested SET operation to ifAlias?
>>> The draft says:
>>>=20
>>>            If a NETCONF server that implements this restriction is
>>>            sent a value that doesn't match the restriction, it MUST
>>>            reply with an rpc-error with the error-tag
>>>            'invalid-value'.
>>>=20
>>>> Is there a simple way for an operator to tell whether the implementati=
on
>>>> supports the restrictions (other than deliberately triggering an error=
)?
>>> No.
>>>=20
>>>> 7) what should an NM application or operator do if the YANG oper-statu=
s
>>>> and the IF-MIB operStatus differ?
>>> The intention is that they share the same instrumentation.
>>>=20
>>>> IF-MIB has substantial discussion of the relationship between
>>>> ifAdminStatus and ifOperStatus. The YANG module doesn't have a compara=
ble
>>>> discussion.
>>> Which text in the MIB do you mean?  There is some text in the
>>> description of "oper-status".
>>>=20
>>>> Given that there could e additional delay incurred between setting ena=
ble,
>>>> updating ifAdminStatus, the change to ifOperStatus, and the update to
>>>> oper-status, I recommend some mention in the description of enable and=
/or
>>>> oper-status of the detailed description in RFC2863, and applicability =
to
>>>> ietf-interfaces.
>>>>  8) link-up-down-trap-enable: The text says this "indicates" whether t=
raps
>>>> should be generated for the interface; shouldn't this be "configures"?
>>> Or maybe "Controls ..."?
>>>=20
>>>> 9) persistence isn't discussed in the config object descriptions. Do t=
hey
>>>> match the IF-MIB object persistences?
>>> Persistence in NETCONF is different from SNMP, in general.  In NETCONF,
>>> the persistence is defined by the data store where you write the data.
>>>=20
>>>=20
>>>> 10) IF-MIB counters do not typically start at zero; a delta must be
>>>> calculated. This is a common misunderstanding for new MIB developers a=
nd
>>>> users.
>>>> I don't see any comparable discussion related to ietf-interfaces count=
ers.
>>>> Where should one look for a discussion of YANG counter initialization
>>>> values?
>>>> Where should one look for a discussion of YANG counter rollover?
>>> The couters are defined as yang:counter32 and yang:counter64. The
>>> "yang" prefix means module "ietf-yang-types".  This module is defined
>>> in RFC 6021.  This RFC discusses initial values and discontinuities.
>>>=20
>>> (ok, this was also suggested by yourself further below!)
>>>=20
>>>> It would help to have a discussion of how to utilize discontinuity_tim=
e
>>>> and counters, especially for implementers not familiar with SNMP (and =
not
>>>> implementing IF-MIB).
>>>>  11) Is it expected that counters in ietf-interfaces and counters in I=
F-MIB
>>>> are synchronized? Can an NM application reasonably compare two reading=
s -
>>>> one of in-octets and one of ifHCInOctets? If not, I think that should =
be
>>>> made clear. (The reference clauses seem to link them)
>>> I think the intention is that the instrumentation is shared. There is
>>> most probably a single hw register / kernel counter for these objects,
>>> and this is what will be used for these counters.
>>>=20
>>>> 12) From IF-MIB: "Discontinuities in the value of this counter can occ=
ur
>>>> at re-initialization of the management system, and at other times as
>>>> indicated by the value of ifCounterDiscontinuityTime."
>>>> From ietf-interfaces: "Discontinuities in the value of this counter ca=
n
>>>> occur at re-initialization of the management system, and at other time=
s as
>>>> indicated by the value of 'discontinuity-time'."
>>>> I think it is ambiguous as to whether both sets of text refer to the s=
ame
>>>> "management system". Is the IF-MIB management-system the SNMP agent? A=
nd
>>>> the YANG management-system the YANG server? Or are both based on the
>>>> underlying (e.g, hardware or native) management system?
>>> Good question!  The term is not defined anywhere (as far as I know),
>>> and thus there is some liberty in the interpretation of it.  But I
>>> don't think it matters.  It seems unlikely that a
>>> NM application sometimes reads a counter over SNMP and sometimes the
>>> same counter from the same device over NETCONF and then compare the
>>> values.
>>>=20
>>>> Are ifCounterDiscontinuityTime and discontinuity-time synchronized or
>>>> independent? If they are independent, then the YANG counters and MIB
>>>> counters could contain very different values; it might help operators =
to
>>>> have this pointed out.
>>> See above.  There is no requirement that they MUST be synchronized,
>>> but they surely can be.
>>>=20
>>>> It might help implementers to know whether to try
>>>> to synchronize them or not.
>>>> Can an operator force restart of both YANG and MIB systems to force
>>>> synchronization of counters?
>>> No.  Is there a way to force a restart of the "MIB system"?
>>>=20
>>>> 13) Some of the questions about counters might be covered in yang-type=
s;
>>>> it would help if the imports clause indicated the relevant RFCs.
>>> As a comment?  I will raise this issue in the WG.
>>>=20
>>>> 14) IF-MIB has both 32-bit and 64-bit counters; YANG only duplicates t=
he
>>>> 64-bit counters, generally. It might be good to discuss this in an
>>>> Operations Considerations section, to explain some potential anomalies=
 at
>>>> the NM application side.
>>> In practice I don't think this is a problem.  It seems unlikely that a
>>> NM application sometimes reads a counter over SNMP and sometimes the
>>> same counter from the same device over NETCONF and then compare the
>>> values.
>>>=20
>>>> 15) ietf-interfaces can modify the SNMP trap-enable settings; enabling
>>>> lots of traps could impact denial of service, disabling could hide
>>>> interface changes made by an attacker; it should probably be mentioned=
 in
>>>> security considerations.
>>> I was thinking we could simply reference the Security Considerations
>>> section in RFC 2863 for this, but it doesn't discuss this.
>>>=20
>>>> 16) Many operators/developers may have experience with IF-MIB, and som=
e
>>>> applications might be rewritten to utilize ietf-interfaces rather than=
 (or
>>>> to supplement) IF-MIB. Not all IF-MIB objects are reflected in
>>>> ietf-interfaces; it might be helpful to show which IF-MIB objects are =
not
>>>> mapped to ietf-interfaces, and discuss why, and whether comparable inf=
o
>>>> can be derived using other YANG approaches.
>>>>  17) The copyright in the module description clause needs updating.
>>> Ok.
>>>=20
>>>=20
>>>=20
>>> /martin
>>> _______________________________________________
>>> netmod mailing list
>>> netmod@ietf.org
>>> https://www.ietf.org/mailman/listinfo/netmod
>>>=20
>>>=20
>>=20
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod
>>=20
>>=20
>=20


From mbj@tail-f.com  Tue Apr 30 03:21:01 2013
Return-Path: <mbj@tail-f.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F418021F9BAD; Tue, 30 Apr 2013 03:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.157
X-Spam-Level: 
X-Spam-Status: No, score=-2.157 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m33qcGnNHNz8; Tue, 30 Apr 2013 03:20:53 -0700 (PDT)
Received: from mail.tail-f.com (de-2007.d.ipeer.se [213.180.74.102]) by ietfa.amsl.com (Postfix) with ESMTP id CB82D21F9BA3; Tue, 30 Apr 2013 03:20:51 -0700 (PDT)
Received: from localhost (138.162.241.83.in-addr.dgcsystems.net [83.241.162.138]) by mail.tail-f.com (Postfix) with ESMTPSA id D5E0F1200045; Tue, 30 Apr 2013 12:20:49 +0200 (CEST)
Date: Tue, 30 Apr 2013 12:20:49 +0200 (CEST)
Message-Id: <20130430.122049.1111664509032933339.mbj@tail-f.com>
To: ietfdbh@comcast.net
Subject: Re: Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data Model for Interface Management) to Proposed Standard
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20130427.093659.369612374.mbj@tail-f.com>
References: <20130427.093659.369612374.mbj@tail-f.com>
X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 30 Apr 2013 08:03:20 -0700
Cc: ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 10:21:01 -0000

Hi David,

Thank you for your detailed review!  Comments inline.

David Harrington <ietfdbh@comcast.net> wrote:
> Hi, 
>  
> I have reviewed this document and feel that is almost ready for approval. 
> This document defines a new data model in YANG format, based on the same 
> information model as the Interfaces MIB module (IF-MIB). 
> Effectively, the YANG model is a second (duplicative) standard for much of 
> the same information. 
> It is expected that devices may implement both the MIB and the YANG data 
> models. 
>  
> My primary concern regards co-existence and synchronization across data 
> models. 
> I think this document would benefit from an Operational Considerations 
> section that discusses synchronization, or an explanation why they might 
> reasonably be out-of-sync. 
> Here are a few points to consider: 
>  
> 1) the ifIndex of an interface is used within the YANG model, matching the 
> ifIndex in IF-MIB.  
> RFC2863 discusses the fact that ifIndex numbering might change during 
> hot-swaps. 

Actually, RFC 2863 points out that a ifIndex must not be reused until
after the following re-initialization of the network management
system.

> This document does not discuss the need to ensure that IF-MIB ifIndex 
> changes need to be reflected in the YANG model. 
> The ifIndex in the YANG module must match that in IF-MIB (really, that in 
> the underlying instrumentation). 

Absolutely!  That's the intention.  The description for the read-only
leaf if-index says:

           The ifIndex value for the ifEntry represented by this
           interface.


> Failure to sync the ifIndex could lead NM applications to confuse which 
> already-retrieved data records are related to which interface. 
> This could cause an NM application to misinterpret/corrupt gathered 
> trending information, and possibly to apply changes to the wrong 
> interfaces. 

Fully agree - this is why the if-index is present; to facilitate the
mapping between the models.

> 2) ifType - can an interface be hot-swapped to use a different type? Is 
> this discussed someplace? 

Hot-swapping sounds like a physical property.  The data model in this
document can handle this -- provided the system physically supports
it, of course.  Note that the type is a writable leaf just like
others.  You can change it, but as with any other leaf a device that
cannot support a particular change will reject it.

> 3) ifType - the description says the value of this mandatory object MAY be 
> initialized. What value should an NM application expect if it is NOT 
> initialized? 

None.  And since it is mandatory, in this case the NM application has
to explicitly provide the type.  If you write a completely generic NM
application you would probably always provide the type, since you
cannot count on the server auto-initializing it.  But if you *know*
that the server auto-initialize the type, you don't have to provide
it.

> 4) enabled - "Systems that implement the IF-MIB use the value of this leaf 
> to set IF-MIB.ifAdminStatus ..."; should this be a MAY/SHOULD/MUST? How 
> will this coexist with SNMP-based NM applications? Is there potential for 
> conflict? What if NETCONF sets this as enabled, then an operator sets it 
> to disabled via SNMP? 
> Does NETCONF know that its "enable" value (adminStatus) is out of date? 
> (does it matter? See note 7). 
> What if the NETCONF system directky changes the underlying instrumentation 
> for adminstatus without going through the MIB? 

It is not clear to me if we can / want to require that these objects
share the same instrumentation.

Some of this might be b/c ifAdminStatus is a a bit unclear in some
regards.  For example, it talks about how

            per configuration information
            retained by the managed system, ifAdminStatus is then
            changed [...]

I would assume (but this might be incorrect) that the "configuration
information" could be things configured through the CLI for example,
and this "configuration information" could thus also be the data
defined in this YANG model.

So it seems RFC 2863 makes a distinction between ifAdminStatus and
what is actually configured.

Also, the description of ifAdminStatus doesn't say anything about
persistence, so it might be impossible to map this to the persistently
stored configuration.


> 5) is there a reason why "description" value MAY match IF-MIB ifAlias 
> ***and MAY restrict the values***? 
> Is there a particular use case for this lack of standardization of 
> restrictions across data models? 
> The persistence is a pretty important restriction related to the 
> functionality of ifAlias, and the dynamism of ifIndex. 
> If NETCONF is used to set the value, ignoring IF-MIB restrictions, what 
> happens to IF-MIB ifAlias as a persistent "handle" to the interface? 

The only reason the "description" leaf is mapped to ifAlias is b/c
this is what many implementations do.  So we wanted to point out the
differences in the value space for these objects so that implementers
are aware of this.

And of course it is not possible to actually set *ifAlias* and ignore
its syntax constraints.  However, you can use non 7-bit ascii in
"description", and in this case the "description" value cannot be used
unmodified as ifAlias.

> 6) What error is returned via NETCONF if YANG attempts to set a value that 
> violates the SNMP agent implementation restrictions, and the SNMP agent 
> refuses the requested SET operation to ifAlias? 

The draft says:

           If a NETCONF server that implements this restriction is
           sent a value that doesn't match the restriction, it MUST
           reply with an rpc-error with the error-tag
           'invalid-value'.

> Is there a simple way for an operator to tell whether the implementation 
> supports the restrictions (other than deliberately triggering an error)? 

No.

> 7) what should an NM application or operator do if the YANG oper-status 
> and the IF-MIB operStatus differ? 

The intention is that they share the same instrumentation.

> IF-MIB has substantial discussion of the relationship between 
> ifAdminStatus and ifOperStatus. The YANG module doesn't have a comparable 
> discussion. 

Which text in the MIB do you mean?  There is some text in the
description of "oper-status".

> Given that there could e additional delay incurred between setting enable, 
> updating ifAdminStatus, the change to ifOperStatus, and the update to 
> oper-status, I recommend some mention in the description of enable and/or 
> oper-status of the detailed description in RFC2863, and applicability to 
> ietf-interfaces. 
>  
> 8) link-up-down-trap-enable: The text says this "indicates" whether traps 
> should be generated for the interface; shouldn't this be "configures"? 

Or maybe "Controls ..."?

> 9) persistence isn't discussed in the config object descriptions. Do they 
> match the IF-MIB object persistences? 

Persistence in NETCONF is different from SNMP, in general.  In NETCONF,
the persistence is defined by the data store where you write the data.


> 10) IF-MIB counters do not typically start at zero; a delta must be 
> calculated. This is a common misunderstanding for new MIB developers and 
> users. 
> I don't see any comparable discussion related to ietf-interfaces counters. 
> Where should one look for a discussion of YANG counter initialization 
> values? 
> Where should one look for a discussion of YANG counter rollover? 

The couters are defined as yang:counter32 and yang:counter64.  The
"yang" prefix means module "ietf-yang-types".  This module is defined
in RFC 6021.  This RFC discusses initial values and discontinuities.

(ok, this was also suggested by yourself further below!)

> It would help to have a discussion of how to utilize discontinuity_time 
> and counters, especially for implementers not familiar with SNMP (and not 
> implementing IF-MIB). 
>  
> 11) Is it expected that counters in ietf-interfaces and counters in IF-MIB 
> are synchronized? Can an NM application reasonably compare two readings - 
> one of in-octets and one of ifHCInOctets? If not, I think that should be 
> made clear. (The reference clauses seem to link them) 

I think the intention is that the instrumentation is shared.  There is
most probably a single hw register / kernel counter for these objects,
and this is what will be used for these counters.

> 12) From IF-MIB: "Discontinuities in the value of this counter can occur 
> at re-initialization of the management system, and at other times as 
> indicated by the value of ifCounterDiscontinuityTime." 
> From ietf-interfaces: "Discontinuities in the value of this counter can 
> occur at re-initialization of the management system, and at other times as 
> indicated by the value of 'discontinuity-time'." 
> I think it is ambiguous as to whether both sets of text refer to the same 
> "management system". Is the IF-MIB management-system the SNMP agent? And 
> the YANG management-system the YANG server? Or are both based on the 
> underlying (e.g, hardware or native) management system? 

Good question!  The term is not defined anywhere (as far as I know),
and thus there is some liberty in the interpretation of it.  But I
don't think it matters.  It seems unlikely that a
NM application sometimes reads a counter over SNMP and sometimes the
same counter from the same device over NETCONF and then compare the
values.

> Are ifCounterDiscontinuityTime and discontinuity-time synchronized or 
> independent? If they are independent, then the YANG counters and MIB 
> counters could contain very different values; it might help operators to 
> have this pointed out.

See above.  There is no requirement that they MUST be synchronized,
but they surely can be.

> It might help implementers to know whether to try 
> to synchronize them or not. 
> Can an operator force restart of both YANG and MIB systems to force 
> synchronization of counters? 

No.  Is there a way to force a restart of the "MIB system"?

> 13) Some of the questions about counters might be covered in yang-types; 
> it would help if the imports clause indicated the relevant RFCs. 

As a comment?  I will raise this issue in the WG.

> 14) IF-MIB has both 32-bit and 64-bit counters; YANG only duplicates the 
> 64-bit counters, generally. It might be good to discuss this in an 
> Operations Considerations section, to explain some potential anomalies at 
> the NM application side. 

In practice I don't think this is a problem.  It seems unlikely that a
NM application sometimes reads a counter over SNMP and sometimes the
same counter from the same device over NETCONF and then compare the
values.

> 15) ietf-interfaces can modify the SNMP trap-enable settings; enabling 
> lots of traps could impact denial of service, disabling could hide 
> interface changes made by an attacker; it should probably be mentioned in 
> security considerations. 

I was thinking we could simply reference the Security Considerations
section in RFC 2863 for this, but it doesn't discuss this.

> 16) Many operators/developers may have experience with IF-MIB, and some 
> applications might be rewritten to utilize ietf-interfaces rather than (or 
> to supplement) IF-MIB. Not all IF-MIB objects are reflected in 
> ietf-interfaces; it might be helpful to show which IF-MIB objects are not 
> mapped to ietf-interfaces, and discuss why, and whether comparable info 
> can be derived using other YANG approaches. 
>  
> 17) The copyright in the module description clause needs updating. 

Ok.



/martin

From lhotka@nic.cz  Tue Apr 30 04:41:59 2013
Return-Path: <lhotka@nic.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A33D21F9B61; Tue, 30 Apr 2013 04:41:59 -0700 (PDT)
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.300, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, J_CHICKENPOX_65=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i4K0gPKW4WW1; Tue, 30 Apr 2013 04:41:58 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) by ietfa.amsl.com (Postfix) with ESMTP id A938E21F99A2; Tue, 30 Apr 2013 04:41:58 -0700 (PDT)
Received: from [172.29.2.201] (nat-5.bravonet.cz [77.48.224.5]) by mail.nic.cz (Postfix) with ESMTPSA id D2E3E13FCB8; Tue, 30 Apr 2013 13:41:57 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1367322117; bh=nWFAnvatfzsadZmcDwSzWOjNBgqz34N95M0PAIF65Gc=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=iwjx6JrPVtkQLN3MEl5bbikO9xs+yb7xWI4L0Ac4DsVB1nHjCBB8PHa29YuzBBZls 9N6DtHo+T6pDXYUw0SLE0isXOpxHw4v2sAIY455wQif0v3XMnBoPRx1SF0R2R/U1f5 N7N0iFPXcuqCla+qBs3b4q3pSin8s7EWFrg7MXuo=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [netmod] Last Call: <draft-ietf-netmod-interfaces-cfg-10.txt> (A YANG Data Model for Interface Management) to Proposed Standard
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <20130430.122049.1111664509032933339.mbj@tail-f.com>
Date: Tue, 30 Apr 2013 13:41:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8BE80629-8A71-4AB1-B008-35DEF750E4FB@nic.cz>
References: <20130427.093659.369612374.mbj@tail-f.com> <20130430.122049.1111664509032933339.mbj@tail-f.com>
To: Martin Bjorklund <mbj@tail-f.com>
X-Mailer: Apple Mail (2.1503)
X-Virus-Scanned: clamav-milter 0.97.7 at mail
X-Virus-Status: Clean
X-Mailman-Approved-At: Tue, 30 Apr 2013 08:03:21 -0700
Cc: ietfdbh@comcast.net, ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 11:41:59 -0000

On Apr 30, 2013, at 12:20 PM, Martin Bjorklund <mbj@tail-f.com> wrote:

>>=20
>> 5) is there a reason why "description" value MAY match IF-MIB ifAlias=20=

>> ***and MAY restrict the values***?=20
>> Is there a particular use case for this lack of standardization of=20
>> restrictions across data models?=20
>> The persistence is a pretty important restriction related to the=20
>> functionality of ifAlias, and the dynamism of ifIndex.=20
>> If NETCONF is used to set the value, ignoring IF-MIB restrictions, =
what=20
>> happens to IF-MIB ifAlias as a persistent "handle" to the interface?=20=

>=20
> The only reason the "description" leaf is mapped to ifAlias is b/c
> this is what many implementations do.  So we wanted to point out the

I think it is a dubious practice.

> differences in the value space for these objects so that implementers
> are aware of this.
>=20
> And of course it is not possible to actually set *ifAlias* and ignore
> its syntax constraints.  However, you can use non 7-bit ascii in
> "description", and in this case the "description" value cannot be used
> unmodified as ifAlias.

If I correctly understand IF-MIB, a natural mapping would be

       +----------------------------------+------------------------+
       | YANG data node                   | IF-MIB object          |
       +----------------------------------+------------------------+
       | name                             | ifAlias                |
       | local-name                       | ifName                 |
       +----------------------------------+------------------------+

with "local-name" being a new config=3Dfalse leaf. The "location" leaf =
then could be removed.
The lack of correspondence between "name" and "ifName" is somewhat =
confusing, so perhaps an alternative could be to follow suit of IF-MIB =
and use "alias" (=3D=3D ifAlias) as the key of interface list, and =
"name" (=3D=3D ifName) as the config=3Dfalse local name.=20

Lada


--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C





From Martin.Stiemerling@neclab.eu  Tue Apr 30 08:21:19 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95A4921F98E6 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 08:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.509
X-Spam-Level: 
X-Spam-Status: No, score=-103.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XN5hzMDWogpW for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 08:21:15 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7E821F841D for <ietf@ietf.org>; Tue, 30 Apr 2013 08:21:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 9A03D103F19; Tue, 30 Apr 2013 17:21:14 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mzl98b70WxQ0; Tue, 30 Apr 2013 17:21:14 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 8260F103F17; Tue, 30 Apr 2013 17:21:04 +0200 (CEST)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 30 Apr 2013 17:21:04 +0200
Message-ID: <517FE160.4090909@neclab.eu>
Date: Tue, 30 Apr 2013 17:21:04 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Do we have an estimated date for completing the IESG selection process for this year?
References: <CA+9kkMDLprWdE3P3DHbkdn3_isTyu6xuaizcnghaKcsEZuE=_g@mail.gmail.com>
In-Reply-To: <CA+9kkMDLprWdE3P3DHbkdn3_isTyu6xuaizcnghaKcsEZuE=_g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
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, 30 Apr 2013 15:21:19 -0000

Hi Ted,

On 04/30/2013 01:19 AM, Ted Hardie wrote:
> So, this page: http://www.ietf.org/iesg/members.html still has TBD
> listed for one of the transport ADs.  Is there a projected date for
> appointment at this point?
>
> Forgive the broad distribution of the question, but it's not clear
> whether this question is solely directed at the nomcom, the IESG, the
> IAB or the community at large.

It is the NOMCOM and the IAB as confirming body.

   Martin

-- 
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From rjsparks@nostrum.com  Tue Apr 30 08:34:35 2013
Return-Path: <rjsparks@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 655E221F9900; Tue, 30 Apr 2013 08:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.996
X-Spam-Level: 
X-Spam-Status: No, score=-101.996 tagged_above=-999 required=5 tests=[AWL=0.604, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vzeiUHvTRxKw; Tue, 30 Apr 2013 08:34:35 -0700 (PDT)
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 BDA9721F98B9; Tue, 30 Apr 2013 08:34:34 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3UFXWuF036166 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Tue, 30 Apr 2013 10:33:33 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517FE44C.7000609@nostrum.com>
Date: Tue, 30 Apr 2013 10:33:32 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
References: <5159F239.1060001@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com> <515AABB5.5050202@gmail.com>
In-Reply-To: <515AABB5.5050202@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "Liubing \(Leo\)" <leo.liubing@huawei.com>, "renum@ietf.org" <renum@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 15:34:35 -0000

On 4/2/13 4:58 AM, Brian E Carpenter wrote:
> Just picking a couple of points for further comment:
>
> On 02/04/2013 08:46, Liubing (Leo) wrote:
>> Hi, Robert
> ...
>
>>> -----Original Message-----
>>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> ...
>>> The document currently references
>>> draft-chown-v6ops-renumber-thinkabout
>>> several times.
>>> That document is long expired (2006). It would be better to simply
>>> restate what is
>>> important from that document here and reference it only once in the
>>> acknowlegements
>>> rather than send the reader off to read it.
>> [Bing] draft-chown-v6ops-renumber-thinkabout is an important input for the gap analysis. Although the draft is expired, most of the content are still valid.
>> draft-chown is a more comprehensive analysis, while the gap draft is focusing on gaps in enterprise renumbering. So it might not easy to abstract several points as important from draft-chown to this draft. We actually encourage people to read it.
> Robert is right, though, sending people to a long-expired draft is a bad idea.
> Of course we have to acknowledge it, but maybe we should pull some of its text
> into an Appendix.
>
> Tim Chown, any opinion?
The most recent version (and the one slated for the next telechat) still 
has this long-expired draft referenced.

RjS


From joelja@bogus.com  Tue Apr 30 08:43:21 2013
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 F313321F9AD3 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 08:43:20 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5db-3DREBkEt for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 08:43:20 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF7621F9810 for <ietf@ietf.org>; Tue, 30 Apr 2013 08:43:20 -0700 (PDT)
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 r3UFhIpf077060 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 30 Apr 2013 15:43:18 GMT (envelope-from joelja@bogus.com)
Message-ID: <517FE691.2070707@bogus.com>
Date: Tue, 30 Apr 2013 08:43:13 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
References: <5159F239.1060001@nostrum.com>	<8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>	<515AABB5.5050202@gmail.com> <517FE44C.7000609@nostrum.com>
In-Reply-To: <517FE44C.7000609@nostrum.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]); Tue, 30 Apr 2013 15:43:19 +0000 (UTC)
Cc: "Liubing \(Leo\)" <leo.liubing@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "renum@ietf.org" <renum@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 15:43:21 -0000

On 4/30/13 8:33 AM, Robert Sparks wrote:
> On 4/2/13 4:58 AM, Brian E Carpenter wrote:
>> Just picking a couple of points for further comment:
>>
>> On 02/04/2013 08:46, Liubing (Leo) wrote:
>>> Hi, Robert
>> ...
>>
>>>> -----Original Message-----
>>>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>> ...
>>>> The document currently references
>>>> draft-chown-v6ops-renumber-thinkabout
>>>> several times.
>>>> That document is long expired (2006). It would be better to simply
>>>> restate what is
>>>> important from that document here and reference it only once in the
>>>> acknowlegements
>>>> rather than send the reader off to read it.
>>> [Bing] draft-chown-v6ops-renumber-thinkabout is an important input 
>>> for the gap analysis. Although the draft is expired, most of the 
>>> content are still valid.
>>> draft-chown is a more comprehensive analysis, while the gap draft is 
>>> focusing on gaps in enterprise renumbering. So it might not easy to 
>>> abstract several points as important from draft-chown to this draft. 
>>> We actually encourage people to read it.
>> Robert is right, though, sending people to a long-expired draft is a 
>> bad idea.
I'm not sure I see that as worse than referring to Wikipedia, an expired 
draft has the property that it's not going to change. I have no problem 
with the idea that it would be an informative reference.   but yes it's 
a bit much to say go read this.
>> Of course we have to acknowledge it, but maybe we should pull some of 
>> its text
>> into an Appendix.
>>
>> Tim Chown, any opinion?
> The most recent version (and the one slated for the next telechat) 
> still has this long-expired draft referenced.
>
> RjS
>


From daedulus@btconnect.com  Tue Apr 30 08:49:31 2013
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 4810821F9BDF for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 08:49:31 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLc8a341Llo5 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 08:49:25 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0186.outbound.messaging.microsoft.com [213.199.154.186]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9D521F97D5 for <ietf@ietf.org>; Tue, 30 Apr 2013 08:49:24 -0700 (PDT)
Received: from mail60-db8-R.bigfish.com (10.174.8.246) by DB8EHSOBE040.bigfish.com (10.174.4.103) with Microsoft SMTP Server id 14.1.225.23; Tue, 30 Apr 2013 15:49:23 +0000
Received: from mail60-db8 (localhost [127.0.0.1])	by mail60-db8-R.bigfish.com (Postfix) with ESMTP id 77C36402AB; Tue, 30 Apr 2013 15:49:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(zz98dI9371I542Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz8275bh8275dh1033ILz2dh2a8h5a9h668h839h946hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh304l1d11m1155h)
Received: from mail60-db8 (localhost.localdomain [127.0.0.1]) by mail60-db8 (MessageSwitch) id 1367336961985770_5519; Tue, 30 Apr 2013 15:49:21 +0000 (UTC)
Received: from DB8EHSMHS025.bigfish.com (unknown [10.174.8.249])	by mail60-db8.bigfish.com (Postfix) with ESMTP id D095B10004F; Tue, 30 Apr 2013 15:49:21 +0000 (UTC)
Received: from AM2PRD0710HT001.eurprd07.prod.outlook.com (157.56.249.213) by DB8EHSMHS025.bigfish.com (10.174.4.35) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 30 Apr 2013 15:49:21 +0000
Received: from DBXPRD0411HT001.eurprd04.prod.outlook.com (157.56.253.165) by pod51017.outlook.com (10.255.165.36) with Microsoft SMTP Server (TLS) id 14.16.305.3; Tue, 30 Apr 2013 15:49:14 +0000
Message-ID: <000b01ce45b9$9002ec20$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Margaret Wasserman <mrw@lilacglade.org>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie><7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org><38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net><516EB736.6060801@cisco.com><8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net><516EFC7E.90801@cisco.com><bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net><20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org>
Subject: Re: IETF Diversity Question on Berlin Registration?
Date: Tue, 30 Apr 2013 16:11:22 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
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.253.165]
X-FOPE-CRA-SourceIpAddress: 157.56.249.213
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: dharkins@lounge.org
X-FOPE-BFA-RECEIVER: mrw@lilacglade.org
Content-Transfer-Encoding: quoted-printable
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: Tue, 30 Apr 2013 15:49:31 -0000

----- Original Message -----
From: "Margaret Wasserman" <mrw@lilacglade.org>
To: "t.p." <daedulus@btconnect.com>
Cc: "Dan Harkins" <dharkins@lounge.org>; <ietf@ietf.org>
Sent: Monday, April 29, 2013 1:53 AM

Hi Tom,

On Apr 19, 2013, at 6:03 AM, t.p. <daedulus@btconnect.com> wrote:
> If we required the IETF to reflect the diversity of people who are,
> e.g., IT network professionals, then the IETF would fall apart for
lack
> of ability.
[=85]
> If the ADs of the IETF have to represent the diversity of the world -
> which could in extremes..

Has anyone even suggested that IESG should reflect the diversity of
these groups?  Where is this coming from?  You are putting up strawmen,
so that you can tear them down=85

The question that people are asking is why the diversity of the IETF
leadership doesn't reflect the diversity of _the IETF_.

There is no inherent reason why 40+-year-old, white, western males who
work at large networking equipment vendors are inherently more capable
of serving on the IESG than people from other groups within the IETF,
and there would be _considerable internal benefit_ to having an IESG
that was more diverse, because diverse groups make better decisions and
better represent the needs of the whole organization.  Therefore, if
there is something about our culture, our structure, our selection
process, or the way we run our meetings that is causing us to
predominantly select our leadership from a restricted group, we would
have _more capable_ and _better_ leadership if we could find a way to
broaden that pool.

_That_ is what this discussion is about.  This is not an effort to meet
some externally imposed notion of diversity.

<tp>
Margaret

The first I saw of this idea was the post by Ray, which said

> "The IETF is concerned about diversity.  As good engineers, we would
like
> to attempt to measure diversity while working on addressing and
increasing
> it.  To that end, we are considering adding some possibly sensitive
> questions to the registration process, for example, gender.

For me, this came out of the blue.  I have no idea why it is considered
that the IETF - note, IETF not IAB or IESG or IAOC - has become
concerned nor what evidence there is of concern.

And note, 'for example, gender' which seems to have become the only
measure under consideration; was that Ray's intent, or was he being coy
and leaving out other frequent lacks of diversity which are more
delicate to discuss? I immediately assumed the latter, based on no
evidence at all!  Given the way the discussion has gone, perhaps he
meant
'only and exclusively gender but I could not possibly say that':-)

As Michael StJohns has said,
"How does the IETF evolve to continue to be an effective, efficient, and
relevant source of high quality Internet standards?"
which I think is spot on.  I do not see diversity (lack of) as being
part of that until it is shown to be.  I do see the IESG as key to the
work of the IETF and see
filling positions there as challenging, perhaps a risk to the long term
existence of the IETF.  The requirements - technical knowledge,
experience,
time to spend on IETF business, e.g. - make the candidate pool rather
small
and I believe that any more constraints will weaken that pool and could
hazard
the IETF.

There are workshops for (potential?) WG Chairs; I would see merit in
more such sessions on how to work effectively within the IETF, at any
level, with a subtext of it is possible to do more, to 'advance', it is
really not (quite) impossible.  Diversity would have no place in such
workshops but it could increase the candidate pool for a variety of
posts.

Tom Petch
</tp>

Margaret









From daedulus@btconnect.com  Tue Apr 30 09:00:00 2013
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 0F7B421F9ADF for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 09:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.681
X-Spam-Level: 
X-Spam-Status: No, score=-1.681 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599, FRT_STRONG2=1.535, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kh4XOLjbC+tk for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 08:59:54 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) by ietfa.amsl.com (Postfix) with ESMTP id 2B0D321F9900 for <ietf@ietf.org>; Tue, 30 Apr 2013 08:59:27 -0700 (PDT)
Received: from mail187-ch1-R.bigfish.com (10.43.68.241) by CH1EHSOBE011.bigfish.com (10.43.70.61) with Microsoft SMTP Server id 14.1.225.23; Tue, 30 Apr 2013 15:59:18 +0000
Received: from mail187-ch1 (localhost [127.0.0.1])	by mail187-ch1-R.bigfish.com (Postfix) with ESMTP id 4F696202B6; Tue, 30 Apr 2013 15:59:18 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -3
X-BigFish: PS-3(zz98dI9371I936eI542I1432Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz177df4h17326ah8275bh8275dh8275ch1033IL17ae73uz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah1d0ch1d2eh304l1d11m1155h)
Received: from mail187-ch1 (localhost.localdomain [127.0.0.1]) by mail187-ch1 (MessageSwitch) id 1367337557168607_4593; Tue, 30 Apr 2013 15:59:17 +0000 (UTC)
Received: from CH1EHSMHS008.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.236])	by mail187-ch1.bigfish.com (Postfix) with ESMTP id 1D57946004E;	Tue, 30 Apr 2013 15:59:17 +0000 (UTC)
Received: from DB3PRD0710HT001.eurprd07.prod.outlook.com (157.56.253.85) by CH1EHSMHS008.bigfish.com (10.43.70.8) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 30 Apr 2013 15:59:15 +0000
Received: from DBXPRD0411HT003.eurprd04.prod.outlook.com (157.56.253.165) by pod51017.outlook.com (10.255.75.36) with Microsoft SMTP Server (TLS) id 14.16.305.3; Tue, 30 Apr 2013 15:59:01 +0000
Message-ID: <005a01ce45ba$eda6faa0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Warren Kumari <warren@kumari.net>, Joe Abley <jabley@hopcount.ca>
References: <51687C0D.8090804@labn.net> <5168C159.3050004@gmail.com><51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie><7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org><38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net><516EB736.6060801@cisco.com><8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net><516EFC7E.90801@cisco.com><bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net><20130419014446.GC1113@mx1.yitter.info><1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net><005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net><5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org><20130429040539.5657221F93BA@ietfa.amsl.com><517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com><20130429192848.5FB4F21F9B35@ietfa.amsl.com><tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com><tsl61z56p12.fsf@mit.edu><4CA9ACF2-4728-4BDD-A94B-570E1533F4A1@hopcount.ca> <A2D2CA6C-E141-430D-B095-0F22BF91E645@kumari.net>
Subject: Re: [IETF] Re: IETF Diversity Question on Berlin Registration?
Date: Tue, 30 Apr 2013 16:53:49 +0100
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.253.165]
X-FOPE-CRA-SourceIpAddress: 157.56.253.85
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: jabley@hopcount.ca
X-FOPE-BFA-RECEIVER: warren@kumari.net
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: Tue, 30 Apr 2013 16:00:01 -0000

----- Original Message -----
From: "Warren Kumari" <warren@kumari.net>
To: "Joe Abley" <jabley@hopcount.ca>
Cc: "Sam Hartman" <hartmans-ietf@mit.edu>; <ietf@ietf.org>;
<stbryant@cisco.com>
Sent: Monday, April 29, 2013 10:01 PM
On Apr 29, 2013, at 4:55 PM, Joe Abley <jabley@hopcount.ca> wrote:

>
> On 2013-04-29, at 16:49, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>
>>>>>>> "Stewart" == Stewart Bryant <stbryant@cisco.com> writes:
>>
>>
>>   Stewart> Why would you disregard a statistical analysis? That seems
>>   Stewart> akin to disregarding the fundamentals of science and
>>
>> Statistical analysis is only useful if it's going to tell you
something
>> that matters for your decision criteria.
>
> http://i.imgur.com/47D7zGq.png

Wow, that *was* useful, and has helped reinforce my belief that I chose
the right browser -- "Think of the children, don't use IE."

<tp>
Warren

The correlation that has attracted attention near me is the marked drop
in crime rates compared with a reduction in the use of leaded petrol;
here, you can make a comparison with countries that have or have not
reduced the use of leaded petrol at different times, and the correlation
stands up, so perhaps Microsoft is not implicated in this one.

Tom Petch


Couldn't resist: http://xkcd.com/552/

W



>
>
> Joe
>

--
There were such things as dwarf gods. Dwarfs were not a naturally
religious species, but in a world where pit props could crack without
warning and pockets of fire damp could suddenly explode they'd seen the
need for gods as the sort of supernatural equivalent of a hard hat.
Besides, when you hit your thumb with an eight-pound hammer it's nice to
be able to blaspheme. It takes a very special and straong-minded kind of
atheist to jump up and down with their hand clasped under their other
armpit and shout, "Oh, random-fluctuations-in-the-space-time-continuum!"
or "Aaargh, primitive-and-outmoded-concept on a crutch!"
  -- Terry Pratchett





From vesely@tana.it  Tue Apr 30 09:28:58 2013
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 30B8021F9BF8; Tue, 30 Apr 2013 09:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.761
X-Spam-Level: 
X-Spam-Status: No, score=-4.761 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uRdUFi8P40TT; Tue, 30 Apr 2013 09:28:53 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id A3DDA21F9AD4; Tue, 30 Apr 2013 09:28:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1367339332; bh=wXfRTlSijDSqw++4AYOALJ9Sy8VQMl66XbXN+puR5y0=; l=1863; h=Date:From:To:CC:References:In-Reply-To; b=ZTR9HjKLfnU15nYG/F9Ut3WO3BBuGL6thyZk/qPfgSzOkc6PzLOG/Jfx+j4grA3bu NfmeIQyHkawhh62tEEX6hdQG7OKSL7nXBgSo8FIw/j+Ucwj7p7TMCR6hv1bUsxzut3 cC1PMLqpo7IwDoAtl+MoSE6fsxCZSaWXAJ58hIrw=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Tue, 30 Apr 2013 18:28:52 +0200 id 00000000005DC02B.00000000517FF144.00003FC4
Message-ID: <517FF144.5040600@tana.it>
Date: Tue, 30 Apr 2013 18:28:52 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org>
In-Reply-To: <20130429230742.3D2833339511@drugs.dv.isc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: "<spfbis@ietf.org>" <spfbis@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, 30 Apr 2013 16:28:58 -0000

On Tue 30/Apr/2013 01:07:42 +0200 Mark Andrews wrote:
> 
> 	The really annoying thing is that SPF is techically superior
> 	to TXT is lots of ways.
> 
> 	1. It uniquely identifies the roll of the record.
> 
> 	2. As SPF records are singletons you don't need to identify
> 	   and remove the old record when updating.  You can just
> 	   remove all SPF record and add the replacement.
> 
> 	   For TXT you need to lookup the existing RRset, extract
> 	   the v=spf1 record from it.  You then need to create a
> 	   UPDATE message to delete just that record as well as add
> 	   the new TXT record.   You then have to hope that no one
> 	   else is performing a simultanious update as you may get
> 	   two TXT v=spf1 records in the RRset.

That's true, except that one has TXT records anyway.

> 	The complains about using SPF is that there are broken
> 	firewalls and some servers drop queries for it, some registars
> 	don't support it.

Nits, as explained below.  The basic fact that killed the SPF type is
the ability to use TXT as a replacement.  There must be an analogous
of Gresham's law:  "Bad types drive out good ones."

> 	For firewalls, fix/replace the firewall if you intend to
> 	deploy SPF and it doesn't support it.  It is total !@##@#
> 	that firewall are incapable of handling new DNS record
> 	types.  New records we exected to occur from the very
> 	beginning and have been coming out regularly ever since the
> 	DNS was invented.  Firewall vendors that are incapable of
> 	handling new DNS types are incompetent and do not deserve
> 	repeat business.
> 
> 	For servers than drop SPF queries they really are at the
> 	noise level.  When you identify one you complain to the
> 	owners of it.  Yes, that does work.  We needed to do that
> 	for AAAA records.
> 
> 	For registrars, change registrar to one that does.

While it's too late for SPF, we can learn this lesson.

From rjsparks@nostrum.com  Tue Apr 30 09:32:50 2013
Return-Path: <rjsparks@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 9F74321F9BA3; Tue, 30 Apr 2013 09:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.198
X-Spam-Level: 
X-Spam-Status: No, score=-102.198 tagged_above=-999 required=5 tests=[AWL=0.403, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6hD3nUno+zXG; Tue, 30 Apr 2013 09:32:50 -0700 (PDT)
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 BC5FE21F9ADF; Tue, 30 Apr 2013 09:32:49 -0700 (PDT)
Received: from unnumerable.local (pool-173-57-99-236.dllstx.fios.verizon.net [173.57.99.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r3UGWnxl042939 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Tue, 30 Apr 2013 11:32:49 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <517FF231.3080700@nostrum.com>
Date: Tue, 30 Apr 2013 11:32:49 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "renum@ietf.org" <renum@ietf.org>, draft-ietf-6renum-gap-analysis@tools.ietf.org
Subject: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt
References: <5159F239.1060001@nostrum.com>
In-Reply-To: <5159F239.1060001@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.57.99.236 is authenticated by a trusted mechanism)
Cc: gen-art@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, 30 Apr 2013 16:32:50 -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-6renum-gap-analysis-05.txt
Reviewer: Robert Sparks
Review Date: April 1, 2013
IETF LC End Date: April 10, 2013
IESG Telechat date: May 16, 2013

Summary: Ready with nits (that border on minor issues)

This update improved the readability significantly, and addressed my 
major concern about being able to build a list of the gaps. Thank you.

There are a few issues from my last call review that are still not 
addressed.
I have left the classification of minor issue vs nits the same as the 
original review to make referring to the earlier review easier,
but please consider all of these Nits. The IESG will need to decide 
whether to escalate them.

I've trimmed away the points that were addressed.

On 4/1/13 3:46 PM, Robert Sparks wrote:
> ----------------------
> Minor issues:
>
> The document currently references 
> draft-chown-v6ops-renumber-thinkabout several times.
> That document is long expired (2006). It would be better to simply 
> restate what is
> important from that document here and reference it only once in the 
> acknowlegements
> rather than send the reader off to read it.
This version still references that long expired draft. There was also 
conversation on apps-discuss
about making that reference normative. IMHO, this is not the right way 
to treat the RFC series, and
strongly encourage moving the text that you want to reference into 
something that will
become an RFC.
>
>
> Should section 8 belong to some other document? It looks like 
> operational renumbering
> advice/considerations, but doesn't seem to be exploring renumbering 
> gaps, except for
> the very short section 8.2 which says "we need a better mechanism" 
> without much explanation.
Afaict, this wasn't addressed at all. In particular, "we need a better 
mechanism" is still all that
section 8.2 says.

>
> Section 5.1, first bullet. The list below "the impact of ambiguous M/O 
> flags" says things like
> "there is no standard" and "it is unspecified". I think you are trying 
> to say that there is
> ambiguity in what's written, not that nothing's written. This entire 
> list would benefit from
> being recast in terms of what needs to be done (what are the gaps?).
This text remains unmodified.
>
> ----------------------
> Nits/editorial comments:
>
> There are a few sentences ending with "etc." in the document. Please 
> consider deleting the
> word from the list - it doesn't help each sentence make its point.
There were some changes, but mostly these still exist. I'll leave 
pressing this point further to the RFC Editor.
>
>
> Seciton 7.1: The first bullet does not parse. If I guess its meaning 
> correctly
> (that it would be benificial to tell hosts that local DNS has been 
> updated and
> they may want to make fresh queries), please be careful with the 
> wording. The
> hosts don't know which names are likely to resolve locally.
This text remained unchanged, and when coming back to the document for a 
re-review
(which is somewhat like coming back to an RFC you've read before just 
for reference),
it's even harder to understand what it's trying to say than it was when 
reading the document
linearly.

I think you are trying to say
"A notification mechanism may be needed to indicate _to_ hosts that a 
renumbering event has _changed how local recursive DNS servers will 
respond_. That mechanism may also need to indicate that such a change 
will happen at a specific time in the future."

>
> Section 7.1, third bullet - This isn't obviously about notification. 
> Why is it
> in this section? What's the gap this is trying to identify?
This text was unchanged.
>
> Section 9.4 - what is it about these that make them gaps, much less 
> unsolvable gaps.
> Is this discussion in the wrong section of the document?
This is now section 10.3 and is mostly unchanged. It's still not clear 
why this discussion is in the "unsolvable gaps" section.


From iab-chair@iab.org  Tue Apr 30 09:36:09 2013
Return-Path: <iab-chair@iab.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 D580921F9C57; Tue, 30 Apr 2013 09:36:09 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t-8nSRlSvOFU; Tue, 30 Apr 2013 09:36:09 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 1C6D021F9C56; Tue, 30 Apr 2013 09:36:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 14F1B127563; Tue, 30 Apr 2013 09:36:09 -0700 (PDT)
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 zeBrs_zgQJ7z; Tue, 30 Apr 2013 09:36:08 -0700 (PDT)
Received: from v150.vpn.iad.rg.net (v150.vpn.iad.rg.net [198.180.150.150]) by c8a.amsl.com (Postfix) with ESMTPSA id 5A9781245AA; Tue, 30 Apr 2013 09:36:08 -0700 (PDT)
From: IAB Chair <iab-chair@iab.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Call for Technical Plenary Topics
Date: Tue, 30 Apr 2013 12:36:06 -0400
Message-Id: <A7D055DB-A72D-4B50-B835-8104B724365A@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.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, 30 Apr 2013 16:36:10 -0000

The plenary topic for IETF 86, The End of POTS, was proposed by an IETF =
participant.  That plenary topic was well received.  As the IAB prepares =
for IETF 87, we want to reach out to the IETF community for technical =
plenary topics.  Please send suggestions to iab at iab.org.

The IAB is interested in hearing suggestions that could be presented by =
invited speakers, panels, or lightning talks.  In other words, please do =
not let the format of past plenary presentations narrow your =
suggestions.

Thank you,
 Russ Housley
 IAB Chair


From dougb@dougbarton.us  Tue Apr 30 10:11:22 2013
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 34D2121F9763 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 10:11:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.113
X-Spam-Level: 
X-Spam-Status: No, score=-1.113 tagged_above=-999 required=5 tests=[AWL=0.246,  BAYES_00=-2.599, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nmd0jYNtEscd for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 10:11:16 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 73C4D21F9AC6 for <ietf@ietf.org>; Tue, 30 Apr 2013 10:11:16 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id CE53822B3F for <ietf@ietf.org>; Tue, 30 Apr 2013 17:11:15 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1367341875; bh=KyG4GJsqRu5PVTIC7oi17Wz8m/Wy7nHZQwSVpmzTlVU=; h=Date:From:To:Subject:References:In-Reply-To; b=i9IWqTVt+aqicqBni5HRXyajLpMQbWbk42yMX9LbmHBjB4PTwCErguQLFD6tTr/ZF C2LXfWello2DScWqIbsnl1GzPj4M2xJMK4S+ynCDND5+TYdChdomlflYArALEWtRll HPb3+CPyT5nIKV+oB6TAbreOAfsEwr/6MjuLHU78=
Message-ID: <517FFB33.30902@dougbarton.us>
Date: Tue, 30 Apr 2013 10:11:15 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it>
In-Reply-To: <517FF144.5040600@tana.it>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
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: Tue, 30 Apr 2013 17:11:22 -0000

On 04/30/2013 09:28 AM, Alessandro Vesely wrote:
> While it's too late for SPF, we can learn this lesson.

As has been repeatedly pointed out in the discussion on both dnsext and 
spfbis, it is NOT too late for SPF. The way forward is simple:

1. Publish the bis draft which says for senders to publish both SPF and 
TXT versions, and receivers to query first for the SPF RRtype.

2. Update the HOW-TO docs to reflect this change.

3. Update the software to query SPF first (Note, Perl's NET::SPF, used 
by SpamAssassin, already made this change).

4. Let time pass.

5. When the next version of the SPF protocol (v=spf{>1}) comes out make 
it SPF/99 only.

The discussion about this on the spfbis list all revolved around the 
fact that TXT is widespread, SPF/99 is rarely used, so let's just stick 
with TXT. In a pre-3597 world there _were_ problems with querying for 
SPF first, so the fact that historically querying for SPF/99 first was 
painful is a valid data point. However the problems encountered in the 
early days of SPF deployment with servers not handing unknown types 
gracefully haven't been relevant for many years now. Yet, the SPF 
community has continued to push TXT only, in spite of the advice of 
4408. Almost like a self-fulfilling prophecy ...

The reasons brought forward by participants in the spfbis group to not 
make this change all revolve around the fact that it would involve 
additional work. Personally I don't find those arguments compelling. 
First, some of the arguments about the extra work are just plain silly 
(ala, "cut and paste of the same data for 2 RRtypes is too difficult"). 
Second, there are not that many implementations that query SPF, and the 
change is not difficult. Third, most of the "work" to be done is to wait 
for time to pass and for people to upgrade to the new versions of 
software. This is a bog-simple "long tail" problem that we deal with in 
the DNS world all the time.

There was one objection that made some sense, which is that right now, 
because the SPF world has steadfastly distributed the advice to use TXT 
only, querying for SPF/99 first gives you what is likely to be 1 
spurious DNS lookup per e-mail message. The obvious answer to that is to 
do a better job of encouraging folks to publish SPF records. Meanwhile, 
I have a fairly traditional mail server implementation that does a 
variety of anti-spam checks. By rough count it generates about 8 DNS 
queries for every message already. Generating 1 more is "in the noise" 
in the short term, and as shown above goes away in the long term.

Not only is this a case where doing the right thing is good for SPF, the 
SPF example of "let's just go with TXT because using a new RRtype is 
hard" has spread like wildfire, especially in the mail authentication 
world (DKIM, DMARC, etc.). The slippery slope has been well-greased at 
this point, and it would be nice to move things back in the right 
direction (see 5507 for example).

To be fair, there was one other objection raised, which is that DNS 
provisioning systems haven't caught up with the need for new RRtypes. So 
some can't go to their registrar's/web hoster's/etc. web interface and 
enter a proper SPF record. That's a problem, sure. But it's a problem 
that has to be solved, assuming we're actually going to take the advice 
in 5507 seriously. Personally I'm not willing to allow all progress 
forward in DNS to be stymied by those unwilling to make an investment in 
their own infrastructure.

In case Dave is still wondering what all the fuss is about, and because 
the folks in spfbis seem completely unwilling to deal with this issue in 
the group, consider this my first draft of an IETF last call objection 
to the fact that 4408bis wants to deprecate use of the SPF RRtype.

Doug


From dhc@dcrocker.net  Tue Apr 30 10:13:40 2013
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 8E5F221F9A89 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 10:13:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.574
X-Spam-Level: 
X-Spam-Status: No, score=-6.574 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpHsEeNPPzyf for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 10:13:34 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 287F521F9763 for <ietf@ietf.org>; Tue, 30 Apr 2013 10:13:27 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3UHDMBu032074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Apr 2013 10:13:26 -0700
Message-ID: <517FFBAB.3030107@dcrocker.net>
Date: Tue, 30 Apr 2013 10:13:15 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us>
In-Reply-To: <517FFB33.30902@dougbarton.us>
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.66]); Tue, 30 Apr 2013 10:13:26 -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: Tue, 30 Apr 2013 17:13:40 -0000

On 4/30/2013 10:11 AM, Doug Barton wrote:
> As has been repeatedly pointed out in the discussion on both dnsext and
> spfbis, it is NOT too late for SPF.


As has repeatedly been pointed out, the market has already had plenty of 
time to adopt the RR and has overwhelmingly rejected it.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From iab-chair@iab.org  Tue Apr 30 10:38:31 2013
Return-Path: <iab-chair@iab.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 47C3621F9A89; Tue, 30 Apr 2013 10:38:31 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Hk7cnfGHSL3; Tue, 30 Apr 2013 10:38:30 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id C6C8921F9A6A; Tue, 30 Apr 2013 10:38:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id C07261276A0; Tue, 30 Apr 2013 10:38:30 -0700 (PDT)
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 5SgzjEbCaXxl; Tue, 30 Apr 2013 10:38:30 -0700 (PDT)
Received: from v150.vpn.iad.rg.net (v150.vpn.iad.rg.net [198.180.150.150]) by c8a.amsl.com (Postfix) with ESMTPSA id D5A891275B6; Tue, 30 Apr 2013 10:38:29 -0700 (PDT)
Subject: Appointment of Deborah Brungard as new IETF Liaison Manager to the ITU-T for MPLS
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: IAB Chair <iab-chair@iab.org>
Date: Tue, 30 Apr 2013 13:38:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F683063-3398-4210-B791-6C0CDB51D33F@iab.org>
References: <EF6D847B-6D0D-4A28-BA67-3F5CD3C6863D@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@ietf.org>, IAB <iab@iab.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, 30 Apr 2013 17:38:31 -0000

The IAB has just notified the ITU-T that Deborah Brungard will be the =
new IETF Liaison Manager to the ITU-T for MPLS. Deborah was appointed =
following an open call for volunteers (see email from Scott Mansfield to =
the IETF list on Fri 3/29/2013 4:32 PM EDT). Please congratulate Deborah =
when you see her.=20

Please thank Scott Mansfield for his past service in this role.  Scott =
is now the overall liaison manager to ITU-T, and as such I am confident =
that he will provide valuable support for Deborah.

Thanks,
Russ



> From: IAB Chair <iab-chair@iab.org>
> Date: April 30, 2013 1:35:53 PM EDT
> To: tsbsg15@itu.int, ITU-T TSAG <tsbtsag@itu.int>
> Cc: ITU TSBDir <tsbdir@itu.int>, IAB <iab@iab.org>, IESG =
<iesg@ietf.org>, IETF Liaison Statements <statements@ietf.org>
> Subject: Appointment of Deborah Brungard as new IETF Liaison Manager =
to the ITU-T for MPLS
>=20
>=20
> The IAB would like to bring to the ITU-T's attention the appointment =
of Ms Deborah Brungard as the new IETF Liaison Manager to the ITU-T for =
MPLS.
>=20
> The IETF-ITU-T MPLS liaison role helps facilitate communication =
between the IETF and the ITU-T on matters of MPLS.  The MPLS liaison =
manager is responsible for ensuring the liaisons from the IETF on MPLS =
are routed to the correct study group(s) in the ITU-T and any incoming =
liaison from the ITU-T on MPLS is communicated to the proper working =
groups, usually MPLS, CCAMP, and PWE3 working groups.
>=20
> Deborah Brungard has been with AT&T for more than 28 years with =
experience in network and service management. She is a Lead Member of =
Technical Staff in AT&T's Network Technologies Unit. She is IETF Routing =
Area's CCAMP Co-Chair, she has co-chaired CCAMP for more than 6 years. =
CCAMP (Common Control and Measurement Plane) is responsible for GMPLS =
and works cooperatively with MPLS, L2VPN, PWE3, OSPF, PCE, IDR, and =
ISIS. She is also the Routing Area Directorate Coordinator and Routing =
Area Secretary. Deborah has actively contributed in SG15 for more than =
15 years, including as an Editor (in the early 2000's). She is very =
familiar with the ITU-T process, she was Chair of ANSI (American =
National Standards) T1X1.5 (Optical Standards) for several years in the =
early 2000's.
>=20
> For the IAB,
> Russ Housley
> IAB Chair
>=20


From ed.lewis@neustar.biz  Tue Apr 30 11:02:18 2013
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 1AECE21F9A79 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.202
X-Spam-Level: 
X-Spam-Status: No, score=-101.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hOLrMT7zxTDZ for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:02:14 -0700 (PDT)
Received: from smtp102.ord1c.emailsrvr.com (smtp102.ord1c.emailsrvr.com [108.166.43.102]) by ietfa.amsl.com (Postfix) with ESMTP id EDA9621F9A77 for <ietf@ietf.org>; Tue, 30 Apr 2013 11:02:13 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 71EEE1B0331; Tue, 30 Apr 2013 14:02:13 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: edlewis-AT-ogud.com) with ESMTPSA id E05581B02ED;  Tue, 30 Apr 2013 14:02:12 -0400 (EDT)
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_582D1173-D935-4FFB-90E1-1148AE7A2A23"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <517FF144.5040600@tana.it>
Date: Tue, 30 Apr 2013 14:02:11 -0400
Message-Id: <C83D1AA8-4F8E-4304-8A7A-3EE3ED2B1F9F@neustar.biz>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it>
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: Tue, 30 Apr 2013 18:02:18 -0000

--Apple-Mail=_582D1173-D935-4FFB-90E1-1148AE7A2A23
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Apr 30, 2013, at 12:28, Alessandro Vesely wrote:
> ...The basic fact that killed the SPF type is
> the ability to use TXT as a replacement.  There must be an analogous
> of Gresham's law:  "Bad types drive out good ones."


I disagree with the assertion that what killed SPF is "the ability to =
use TXT as a replacement."   It has nothing to do with one option being =
superior to the other, it was the lack of technical incentive to switch =
from one to the other.  I post this in the sense that if the root cause =
is not understood, no solution will stick.  Here is a message with my =
recounting of what led us to this point:

http://www.ietf.org/mail-archive/web/dnsext/current/msg12681.html

I don't see the death of SPF has a harbinger of things to come.  There's =
a strong case to be made the failure happened before 2004 and the root =
cause has since been corrected by changing the RRTYPE type allocation =
policies.  Still that fix was too late to ever let SPF sprout wings.

=
-=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=_582D1173-D935-4FFB-90E1-1148AE7A2A23
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>On Apr 30, 2013, at 12:28, Alessandro Vesely =
wrote:</div><blockquote type=3D"cite"><div>...The basic fact that killed =
the SPF type is</div><div>the ability to use TXT as a replacement. =
&nbsp;There must be an analogous<br>of Gresham's law: &nbsp;"Bad types =
drive out good ones."<br></div></blockquote></div><div =
apple-content-edited=3D"true"><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; =
"><br></span></div><div apple-content-edited=3D"true">I disagree with =
the assertion that what killed SPF is "the ability to use TXT as a =
replacement." &nbsp; It has nothing to do with one option being superior =
to the other, it was the lack of technical incentive to switch from one =
to the other. &nbsp;I post this in the sense that if the root cause is =
not understood, no solution will stick. &nbsp;Here is a message with my =
recounting of what led us to this point:</div><div =
apple-content-edited=3D"true"><br></div><div =
apple-content-edited=3D"true"><a =
href=3D"http://www.ietf.org/mail-archive/web/dnsext/current/msg12681.html"=
>http://www.ietf.org/mail-archive/web/dnsext/current/msg12681.html</a></di=
v><div apple-content-edited=3D"true"><br></div><div =
apple-content-edited=3D"true">I don't see the death of SPF has a =
harbinger of things to come. &nbsp;There's a strong case to be made the =
failure happened before 2004 and the root cause has since been corrected =
by changing the RRTYPE type allocation policies. &nbsp;Still that fix =
was too late to ever let SPF sprout wings.</div><div =
apple-content-edited=3D"true"><br></div><div =
apple-content-edited=3D"true">-=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></span>-=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>
</div>
<br></body></html>=

--Apple-Mail=_582D1173-D935-4FFB-90E1-1148AE7A2A23--

From drc@virtualized.org  Tue Apr 30 11:08:27 2013
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 8A46921F97FB for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:08:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JgsAEk0U4bPq for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:08:21 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id B908321F9763 for <ietf@ietf.org>; Tue, 30 Apr 2013 11:08:21 -0700 (PDT)
Received: from [10.0.1.4] (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 DB89417184; Tue, 30 Apr 2013 18:08:20 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
From: David Conrad <drc@virtualized.org>
In-Reply-To: <517FFBAB.3030107@dcrocker.net>
Date: Tue, 30 Apr 2013 11:08:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6317B91-E7EB-499F-BBBF-A78CB44569F9@virtualized.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <517FFBAB.3030107@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1503)
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, 30 Apr 2013 18:08:27 -0000

Dave,

On Apr 30, 2013, at 10:13 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> On 4/30/2013 10:11 AM, Doug Barton wrote:
>> As has been repeatedly pointed out in the discussion on both dnsext =
and spfbis, it is NOT too late for SPF.
>=20
> As has repeatedly been pointed out, the market has already had plenty =
of time to adopt the RR and has overwhelmingly rejected it.

What is the IETF-approved timeframe in which "the market" is allowed to =
accept/reject a particular technology?

Given no one appears to be making the argument that using the TXT RR and =
the MAIL FROM/HELO identity is the optimal solution (to put it mildly), =
I'm a bit confused why deprecating the SPF RR is being pushed so hard at =
this point in time. Is there some forcing function here?

Regards,
-drc


From ynir@checkpoint.com  Tue Apr 30 11:09:47 2013
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 D0AB721F9C7C for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:09:47 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iMuy0Vx4p1iY for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:09:43 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id ADE2721F9C7B for <ietf@ietf.org>; Tue, 30 Apr 2013 11:09:26 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r3UI9N8o024009; Tue, 30 Apr 2013 21:09:23 +0300
X-CheckPoint: {518007A0-0-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Tue, 30 Apr 2013 21:09:23 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>
Subject: Re: Do we have an estimated date for completing the IESG selection process for this year?
Thread-Topic: Do we have an estimated date for completing the IESG selection process for this year?
Thread-Index: AQHORTAhzXDujd4G7Eiqac2d60bCpJjur/0AgAAvBgA=
Date: Tue, 30 Apr 2013 18:09:23 +0000
Message-ID: <8C7F42A8-9E8F-4953-866D-8D268EF9C52B@checkpoint.com>
References: <CA+9kkMDLprWdE3P3DHbkdn3_isTyu6xuaizcnghaKcsEZuE=_g@mail.gmail.com> <517FE160.4090909@neclab.eu>
In-Reply-To: <517FE160.4090909@neclab.eu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.79]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 114dad8fa8243728d438e526b358fdb427ee52f37f
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <ECF5E64518164740AA596634CAA656D5@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Ted Hardie <ted.ietf@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: Tue, 30 Apr 2013 18:09:47 -0000

Hi Martin,

On Apr 30, 2013, at 6:21 PM, Martin Stiemerling <martin.stiemerling@neclab.=
eu> wrote:

> Hi Ted,
>=20
> On 04/30/2013 01:19 AM, Ted Hardie wrote:
>> So, this page: http://www.ietf.org/iesg/members.html still has TBD
>> listed for one of the transport ADs.  Is there a projected date for
>> appointment at this point?
>>=20
>> Forgive the broad distribution of the question, but it's not clear
>> whether this question is solely directed at the nomcom, the IESG, the
>> IAB or the community at large.
>=20
> It is the NOMCOM and the IAB as confirming body.
>=20

While this is true, we've been aware of a problem for three months now, and=
 we're not aware of any resolution or of any attempt to resolve the issue. =
We know that there are several candidates (Still listed on the NomCom websi=
te) and for some reason (which we can only guess at) none of them is being =
appointed.

Will that seat remain vacant for a year? Two years? Is there some flaw in t=
he process that prevents this issue from being resolved?

Inquiring minds want to know

Yoav=

From dhc@dcrocker.net  Tue Apr 30 11:12:58 2013
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 2E49921F95EA for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.576
X-Spam-Level: 
X-Spam-Status: No, score=-6.576 tagged_above=-999 required=5 tests=[AWL=0.023,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kL7Zi-nGRfl0 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:12:52 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6F30021F95EE for <ietf@ietf.org>; Tue, 30 Apr 2013 11:12:52 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3UICmBl000626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Apr 2013 11:12:52 -0700
Message-ID: <5180099A.8010405@dcrocker.net>
Date: Tue, 30 Apr 2013 11:12:42 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <517FFBAB.3030107@dcrocker.net> <D6317B91-E7EB-499F-BBBF-A78CB44569F9@virtualized.org>
In-Reply-To: <D6317B91-E7EB-499F-BBBF-A78CB44569F9@virtualized.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.66]); Tue, 30 Apr 2013 11:12:52 -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: Tue, 30 Apr 2013 18:12:58 -0000

On 4/30/2013 11:08 AM, David Conrad wrote:
>> As has repeatedly been pointed out, the market has already had
>> plenty of time to adopt the RR and has overwhelmingly rejected it.
>
> What is the IETF-approved timeframe in which "the market" is allowed
> to accept/reject a particular technology?

I've no idea what the lower limit is or should be, but I'm quite sure 
that 7 years exceeds it by a very comfortable margin.


> Given no one appears to be making the argument that using the TXT RR
> and the MAIL FROM/HELO identity is the optimal solution (to put it
> mildly), I'm a bit confused why deprecating the SPF RR is being
> pushed so hard at this point in time. Is there some forcing function
> here?

Surely this has been amply covered, multiple times.  Rehashing it won't 
be productive.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From superuser@gmail.com  Tue Apr 30 11:29:19 2013
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 0313A21F9C3A for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.145
X-Spam-Level: 
X-Spam-Status: No, score=-2.145 tagged_above=-999 required=5 tests=[AWL=0.454,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NwXp4kiPnPEq for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 11:29:17 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id E760521F9AF5 for <ietf@ietf.org>; Tue, 30 Apr 2013 11:29:05 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hm14so4253338wib.11 for <ietf@ietf.org>; Tue, 30 Apr 2013 11:29:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=awMqsRk75M/92X4LUb2huGzVaVtiPM2Q6FxND/Kj1ic=; b=vm7UH/wSHdtnN7WZGNG651+RXB1ws/XNGXaoN7lh6V4Y+r+g7j31om6R6mbDvr+qDN XNs3NDyENS/PO2nz0tSUM+iq6uyW8sxaDoie6TFBQuGRfFUiQbf91w1VWWKm5i5Ay5Oy Y8ChKlpfgAnl7HFA6knCynS0gjozWpjzMwOhBoEDMiNjwzH2Z6T/OJR68nHgEZlXPhgc Q8qw5/wWMepMFwHQAtTHb/3GUEX+trRbDZzbnMT4u8mAXPAJp8JIb2HABwVLtFMv9Qf/ ROFSqcMSwJI7TpjJRiZFDmz4yBOWjOsHPQoUJx0HaGEeo1xWKc2dqObSlhPcOg6tB7Do IL9w==
MIME-Version: 1.0
X-Received: by 10.180.79.69 with SMTP id h5mr26301569wix.14.1367346544642; Tue, 30 Apr 2013 11:29:04 -0700 (PDT)
Received: by 10.180.14.34 with HTTP; Tue, 30 Apr 2013 11:29:04 -0700 (PDT)
In-Reply-To: <517FFB33.30902@dougbarton.us>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us>
Date: Tue, 30 Apr 2013 11:29:04 -0700
Message-ID: <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: multipart/alternative; boundary=f46d043c062e14103804db982d7a
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, 30 Apr 2013 18:29:19 -0000

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

Doug,

Aren't you tired of repeatedly pointing out your half of the argument?  I
am of ours.  The Monty Python argument clinic sketch comes to mind.

On Tue, Apr 30, 2013 at 10:11 AM, Doug Barton <dougb@dougbarton.us> wrote:

> The discussion about this on the spfbis list all revolved around the fact
> that TXT is widespread, SPF/99 is rarely used, so let's just stick with
> TXT. In a pre-3597 world there _were_ problems with querying for SPF first,
> so the fact that historically querying for SPF/99 first was painful is a
> valid data point. However the problems encountered in the early days of SPF
> deployment with servers not handing unknown types gracefully haven't been
> relevant for many years now. Yet, the SPF community has continued to push
> TXT only, in spite of the advice of 4408. Almost like a self-fulfilling
> prophecy ...
>

As has been repeatedly pointed out, the "haven't been relevant for many
years now" conclusion you've reached is contradicted by both anecdotal and
empirical data.

I assure you that I hear all of the points you are making.  I also assure
you that none of them resolve any of the points being made on the other
side.  There's no dialog happening here.


>
> The reasons brought forward by participants in the spfbis group to not
> make this change all revolve around the fact that it would involve
> additional work. Personally I don't find those arguments compelling.


Sure, because you don't have to do the work, nor are you confronted with
the weight of the long tail in this case.  I submit that it is presumptuous
to assert that the properties of one community's long tail problems are the
same as they are in others.


> First, some of the arguments about the extra work are just plain silly
> (ala, "cut and paste of the same data for 2 RRtypes is too difficult").


I don't think anyone said that's difficult.  I would also point out that
it's not difficult, given a jumble of TXT RRs in a reply, to find any that
start with a particular identifying substring which would mean "this is an
SPF record", so let's nip that one in the bud right now.

These are all distractions from the real points being made.


> Second, there are not that many implementations that query SPF, and the
> change is not difficult.


Nobody said that's a problem either.


> Third, most of the "work" to be done is to wait for time to pass and for
> people to upgrade to the new versions of software. This is a bog-simple
> "long tail" problem that we deal with in the DNS world all the time.
>

...during which time the service arguably operates in a degraded state.

The assertion that "You should just fix your DNS infrastructure!" ignores
the fact that the interfering piece of the infrastructure may not be under
the control of the operator who can't complete an SPF operation, or, worse,
that the owner of the problem lacks the resources or interest to get it
fixed for a long while, if at all.

Do we just have SPF operators call you for emotional support during this
protracted transition time?


>
> Not only is this a case where doing the right thing is good for SPF, the
> SPF example of "let's just go with TXT because using a new RRtype is hard"
> has spread like wildfire, especially in the mail authentication world
> (DKIM, DMARC, etc.). The slippery slope has been well-greased at this
> point, and it would be nice to move things back in the right direction (see
> 5507 for example).
>

This is also a separate argument given the underscore prefix debate.


>
> To be fair, there was one other objection raised, which is that DNS
> provisioning systems haven't caught up with the need for new RRtypes. So
> some can't go to their registrar's/web hoster's/etc. web interface and
> enter a proper SPF record. That's a problem, sure. But it's a problem that
> has to be solved, assuming we're actually going to take the advice in 5507
> seriously. Personally I'm not willing to allow all progress forward in DNS
> to be stymied by those unwilling to make an investment in their own
> infrastructure.
>

What are you prepared to do to help address the broken infrastructure?
It's all well and good to lob directives over the wall, but I'd like to
hear some advice about how to compel inattentive infrastructure operators
to make these changes, especially when those operators aren't necessarily
the ones affected.

-MSK

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

<div dir=3D"ltr">Doug,<br><br>Aren&#39;t you tired of repeatedly pointing o=
ut your half of the=20
argument?=A0 I am of ours.=A0 The Monty Python argument clinic sketch comes=
=20
to mind.<br><br>On Tue, Apr 30, 2013 at 10:11 AM, Doug Barton <span dir=3D"=
ltr">&lt;<a href=3D"mailto:dougb@dougbarton.us" target=3D"_blank">dougb@dou=
gbarton.us</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">The discussion about this=
 on the spfbis list all revolved around the fact that TXT is widespread, SP=
F/99 is rarely used, so let&#39;s just stick with TXT. In a pre-3597 world =
there _were_ problems with querying for SPF first, so the fact that histori=
cally querying for SPF/99 first was painful is a valid data point. However =
the problems encountered in the early days of SPF deployment with servers n=
ot handing unknown types gracefully haven&#39;t been relevant for many year=
s now. Yet, the SPF community has continued to push TXT only, in spite of t=
he advice of 4408. Almost like a self-fulfilling prophecy ...<br>
</blockquote><div><br></div><div>As has been repeatedly pointed out, the &q=
uot;haven&#39;t been relevant for many years now&quot; conclusion you&#39;v=
e reached is contradicted by both anecdotal and empirical data.<br><br>
I assure you that I hear all of the points you are making.=A0 I also assure=
 you that none of them resolve any of the points being made on the other si=
de.=A0 There&#39;s no dialog happening here.<br></div><div>=A0<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">

<br>
The reasons brought forward by participants in the spfbis group to not make=
 this change all revolve around the fact that it would involve additional w=
ork. Personally I don&#39;t find those arguments compelling.</blockquote>
<div><br></div><div>Sure, because you don&#39;t have to do the work, nor ar=
e you confronted with the weight of the long tail in this case.=A0 I submit=
 that it is presumptuous to assert that the properties of one community&#39=
;s long tail problems are the same as they are in others.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> First, some=
 of the arguments about the extra work are just plain silly (ala, &quot;cut=
 and paste of the same data for 2 RRtypes is too difficult&quot;).</blockqu=
ote>
<div><br></div><div>I don&#39;t think anyone said that&#39;s difficult.=A0 =
I would also point out that it&#39;s not difficult, given a jumble of TXT R=
Rs in a reply, to find any that start with a particular identifying substri=
ng which would mean &quot;this is an SPF record&quot;, so let&#39;s nip tha=
t one in the bud right now.<br>
<br></div><div>These are all distractions from the real points being made.<=
br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Second, =
there are not that many implementations that query SPF, and the change is n=
ot difficult.</blockquote>
<div><br></div><div>Nobody said that&#39;s a problem either.<br>=A0<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"> Third, most of the &qu=
ot;work&quot; to be done is to wait for time to pass and for people to upgr=
ade to the new versions of software. This is a bog-simple &quot;long tail&q=
uot; problem that we deal with in the DNS world all the time.<br>
</blockquote><div><br></div><div>...during which time the service arguably =
operates in a degraded state.<br><br></div><div>The assertion that &quot;Yo=
u should just fix your DNS infrastructure!&quot; ignores the fact that the =
interfering piece of the infrastructure may not be under the control of the=
 operator who can&#39;t complete an SPF operation, or, worse, that the owne=
r of the problem lacks the resources or interest to get it fixed for a long=
 while, if at all.<br>
</div><div><br>Do we just have SPF operators call you for emotional support=
 during this protracted transition time?<br>=A0<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">

<br>
Not only is this a case where doing the right thing is good for SPF, the SP=
F example of &quot;let&#39;s just go with TXT because using a new RRtype is=
 hard&quot; has spread like wildfire, especially in the mail authentication=
 world (DKIM, DMARC, etc.). The slippery slope has been well-greased at thi=
s point, and it would be nice to move things back in the right direction (s=
ee 5507 for example).<br>
</blockquote><div><br></div><div>This is also a separate argument given the=
 underscore prefix debate.<br>=A0<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">

<br>
To be fair, there was one other objection raised, which is that DNS provisi=
oning systems haven&#39;t caught up with the need for new RRtypes. So some =
can&#39;t go to their registrar&#39;s/web hoster&#39;s/etc. web interface a=
nd enter a proper SPF record. That&#39;s a problem, sure. But it&#39;s a pr=
oblem that has to be solved, assuming we&#39;re actually going to take the =
advice in 5507 seriously. Personally I&#39;m not willing to allow all progr=
ess forward in DNS to be stymied by those unwilling to make an investment i=
n their own infrastructure.<br>
</blockquote><div><br></div><div>What are you prepared to do to help addres=
s the broken infrastructure?=A0 It&#39;s all well and good to lob directive=
s over the wall, but I&#39;d like to hear some advice about how to compel i=
nattentive infrastructure operators to make these changes, especially when =
those operators aren&#39;t necessarily the ones affected.<br>
<br></div><div>-MSK<br></div></div></div></div>

--f46d043c062e14103804db982d7a--

From drc@virtualized.org  Tue Apr 30 12:53:49 2013
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 7238421F9A83 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 12:53:45 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WsJsbyN4oZVw for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 12:53:36 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3C6F021F9A81 for <ietf@ietf.org>; Tue, 30 Apr 2013 12:53:23 -0700 (PDT)
Received: from [10.0.1.4] (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 D397E17184; Tue, 30 Apr 2013 19:52:57 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
From: David Conrad <drc@virtualized.org>
In-Reply-To: <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com>
Date: Tue, 30 Apr 2013 12:52:56 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com>
To: Murray S. Kucherawy <superuser@gmail.com>
X-Mailer: Apple Mail (2.1503)
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, 30 Apr 2013 19:53:49 -0000

Murray,

On Apr 30, 2013, at 11:29 AM, Murray S. Kucherawy <superuser@gmail.com> =
wrote:
> I would also point out that it's not difficult, given a jumble of TXT =
RRs in a reply, to find any that start with a particular identifying =
substring which would mean "this is an SPF record", so let's nip that =
one in the bud right now.

SPF using TXT and hence, SPFBIS forces the uniquification of the DNS =
response into the application instead of in the DNS library. Given the =
ordering of individual TXT RRs within an RRset is not guaranteed, I =
suspect the chances that every application is going to do that parsing =
correctly is relatively low (btw, the example in 3.3 in spfbis-14 is a =
bit misleading: assuming "second string" is in a separate TXT RR (which =
is implied), the concatenation might be "second stringv=3Dspf1 ..... =
first").  The more interesting bit is if/when another protocol uses TXT =
at the same ownername.

> What are you prepared to do to help address the broken infrastructure?

Argue against deprecating the SPF RR :).

The RR has been allocated and it is supported in most DNS servers and =
resolver libraries in one form or another.  Provisioning systems take =
much longer, but that isn't surprising and shouldn't be an argument to =
deprecate (if it is, we might as well close the RRtype registry for new =
entries).

In the past, the IETF used to make decisions based on long-term =
technical/architectural correctness, even in the face of pragmatic =
complications (e.g., the choice to mandate strong crypto despite real =
world challenges some companies faced in exporting that crypto in =
products). In this particular case, there seems to be an argument to =
explicitly disallow the long-term technically/architecturally correct =
approach because some folks choose not to add an RR to their zone files =
or support that RR in their provisioning systems.  As I said in DNSEXT, =
this seems like the wrong approach to me.

Regards,
-drc




From drc@virtualized.org  Tue Apr 30 12:55:02 2013
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 42C6A21F9AD9 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 12:55:02 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fYs87uxFIvM5 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 12:54:40 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id AC56621F9A8A for <ietf@ietf.org>; Tue, 30 Apr 2013 12:54:35 -0700 (PDT)
Received: from [10.0.1.4] (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 36B0117184; Tue, 30 Apr 2013 19:54:12 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
From: David Conrad <drc@virtualized.org>
In-Reply-To: <5180099A.8010405@dcrocker.net>
Date: Tue, 30 Apr 2013 12:54:11 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA2545BD-3060-462B-95CE-36DB5DA3511D@virtualized.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <517FFBAB.3030107@dcrocker.net> <D6317B91-E7EB-499F-BBBF-A78CB44569F9@virtualized.org> <5180099A.8010405@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1503)
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, 30 Apr 2013 19:55:02 -0000

On Apr 30, 2013, at 11:12 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>> What is the IETF-approved timeframe in which "the market" is allowed =
to accept/reject a particular technology?
> I've no idea what the lower limit is or should be, but I'm quite sure =
that 7 years exceeds it by a very comfortable margin.

By that logic we should abandon IPv6, DNSSEC, EDNS0, etc.

Thanks,
-drc



From dhc@dcrocker.net  Tue Apr 30 13:21:02 2013
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 109BC21F9B03 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 13:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.579
X-Spam-Level: 
X-Spam-Status: No, score=-6.579 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q0w2E679-s-R for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 13:20:57 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 84FB821F9B2B for <ietf@ietf.org>; Tue, 30 Apr 2013 13:20:47 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3UKKfw5002729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Apr 2013 13:20:45 -0700
Message-ID: <51802793.3010003@dcrocker.net>
Date: Tue, 30 Apr 2013 13:20:35 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <517FFBAB.3030107@dcrocker.net> <D6317B91-E7EB-499F-BBBF-A78CB44569F9@virtualized.org> <5180099A.8010405@dcrocker.net> <EA2545BD-3060-462B-95CE-36DB5DA3511D@virtualized.org>
In-Reply-To: <EA2545BD-3060-462B-95CE-36DB5DA3511D@virtualized.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.66]); Tue, 30 Apr 2013 13:20:45 -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: Tue, 30 Apr 2013 20:21:02 -0000

On 4/30/2013 12:54 PM, David Conrad wrote:
> On Apr 30, 2013, at 11:12 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>>> What is the IETF-approved timeframe in which "the market" is allowed to accept/reject a particular technology?
>> I've no idea what the lower limit is or should be, but I'm quite sure that 7 years exceeds it by a very comfortable margin.
>
> By that logic we should abandon IPv6, DNSSEC, EDNS0, etc.


Gosh, David.  I guess you win.


d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jari.arkko@piuha.net  Tue Apr 30 13:32:01 2013
Return-Path: <jari.arkko@piuha.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 8999121F934C for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 13:32:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.342
X-Spam-Level: 
X-Spam-Status: No, score=-102.342 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hD0fd8hd6NXv for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 13:31:56 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 035F721F9B37 for <ietf@ietf.org>; Tue, 30 Apr 2013 13:31:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 820242CC63 for <ietf@ietf.org>; Tue, 30 Apr 2013 23:31:14 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q9-5J61JBVnZ for <ietf@ietf.org>; Tue, 30 Apr 2013 23:31:13 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 760E82CC53 for <ietf@ietf.org>; Tue, 30 Apr 2013 23:31:13 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <tslzjwg4ujm.fsf@mit.edu>
Date: Tue, 30 Apr 2013 13:31:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FD89A1B-F1D4-450F-BF38-61250F9A1D83@piuha.net>
References: <51687C0D.8090804@labn.net> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com> <tsl61z56p12.fsf@mit.edu> <517F1823.4070502@gmail.com> <tslzjwg4ujm.fsf@mit.edu>
To: IETF list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Apr 2013 20:32:01 -0000

I think the statistics are very interesting and we should continue =
developing them, but we should also not be driven by them. I'll repeat =
again what I've said before: I can see increasing both participation =
diversity and leadership diversity being useful for the IETF. We are =
limited by various constraints, type of people who are in our field, =
where the industry is located in the world, funding resources, expertise =
gained by various participants, etc. But within those constraints, I'd =
see plenty of benefits to increasing diversity along many axes. (Or =
indeed even relaxing some of the constraints, such lowering =
participation costs by remote participation, or lowering leadership =
costs by requiring less than 100% time commitments.)

Jari


From randy@psg.com  Tue Apr 30 13:41:59 2013
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 5BCEE21F867B for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 13:41:59 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhYf6lYqXdRn for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 13:41:58 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 8D39A21F83DF for <ietf@ietf.org>; Tue, 30 Apr 2013 13:41:58 -0700 (PDT)
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 1UXHN1-000FRX-QJ; Tue, 30 Apr 2013 20:41:51 +0000
Date: Tue, 30 Apr 2013 13:41:51 -0700
Message-ID: <m2fvy7sqcw.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IETF Diversity Question on Berlin Registration?
In-Reply-To: <3FD89A1B-F1D4-450F-BF38-61250F9A1D83@piuha.net>
References: <51687C0D.8090804@labn.net> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com> <tsl61z56p12.fsf@mit.edu> <517F1823.4070502@gmail.com> <tslzjwg4ujm.fsf@mit.edu> <3FD89A1B-F1D4-450F-BF38-61250F9A1D83@piuha.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 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, 30 Apr 2013 20:41:59 -0000

you don't need a weatherman to know which way the wind blows.
-- bob dylan

we do not need measurements to know the ietf is embarrassingly
non-diverse.  it is derived from and embedded in an embarrassingly
non-diverse culture.

we need to do what we can to remedy this.  progress not perfection is
our goal.

measurement may be useful to see if we are having effect and/or what
things have effect (meeting locales, size of cookies, ...).

we should be asking the minorities and those struggling to particiate
what we can do to help.

randy

From dmm@1-4-5.net  Tue Apr 30 13:57:06 2013
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 9AED121F8AF8 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 13:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BL7FOAC4PEad for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 13:56:54 -0700 (PDT)
Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) by ietfa.amsl.com (Postfix) with ESMTP id 3F20021F9AC0 for <ietf@ietf.org>; Tue, 30 Apr 2013 13:53:07 -0700 (PDT)
Received: by mail-lb0-f177.google.com with SMTP id x10so929681lbi.22 for <ietf@ietf.org>; Tue, 30 Apr 2013 13:53:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=2tgR3n+6HZC0u+5dRVrS3eNjM3Fsz2P1LMYftK3y2n4=; b=CVyrCYtxMJeKffia51auC0kfuidB/eHv8aGIYKk05RBb6NiGk2pjhWFC8CbsJjdARg Nm2wK7JEBaZVRf4nWyCYsZif3yQaIvV3vD4kOo3cz6sm13ubOQxfNuAL0tM3fK/xl4W2 /uLKqVUk4zK2qhIxnRjpxZht/eciMgxzUuCGOG8au2TaYFFvneYEU82eZyr/flLPRUGX sODLY3Ed76qbahDcxTSCes9/f/Nd5H2JdwM2OT9P45TlQp7kN0j+b3/s4WwqJsQHGJ2p LeBa+tqQtEDZ6bIeU/7A1o20WprIDBydZxOfxAWKP7VNcQK3oBHt7c7z8dP39y/avrQG mDPQ==
MIME-Version: 1.0
X-Received: by 10.112.167.168 with SMTP id zp8mr227289lbb.58.1367355186086; Tue, 30 Apr 2013 13:53:06 -0700 (PDT)
Received: by 10.112.209.8 with HTTP; Tue, 30 Apr 2013 13:53:05 -0700 (PDT)
X-Originating-IP: [24.21.216.213]
In-Reply-To: <m2fvy7sqcw.wl%randy@psg.com>
References: <51687C0D.8090804@labn.net> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com> <tsl61z56p12.fsf@mit.edu> <517F1823.4070502@gmail.com> <tslzjwg4ujm.fsf@mit.edu> <3FD89A1B-F1D4-450F-BF38-61250F9A1D83@piuha.net> <m2fvy7sqcw.wl%randy@psg.com>
Date: Tue, 30 Apr 2013 13:53:05 -0700
Message-ID: <CAHiKxWi+n5RuODKQSiLooi3V9RH+iWttK4xZZJShyr=hhU-z0Q@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: David Meyer <dmm@1-4-5.net>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=001a11c2a88426165504db9a30db
X-Gm-Message-State: ALoCoQk/luW7+iPWYugD25yjvxS9Yk7APkpxBcK0+Mm45FMMcXHcXKJvpBDeS2XqmKgwFGE25EaH
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, 30 Apr 2013 20:57:06 -0000

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

On Tue, Apr 30, 2013 at 1:41 PM, Randy Bush <randy@psg.com> wrote:

> you don't need a weatherman to know which way the wind blows.
> -- bob dylan
>
> we do not need measurements to know the ietf is embarrassingly
> non-diverse.  it is derived from and embedded in an embarrassingly
> non-diverse culture.
>
> we need to do what we can to remedy this.  progress not perfection is
> our goal.
>
> measurement may be useful to see if we are having effect and/or what
> things have effect (meeting locales, size of cookies, ...).
>
> we should be asking the minorities and those struggling to particiate
> what we can do to help.
>
> randy
>

Nicely said Randy. --dmm

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

<br><br><div class=3D"gmail_quote">On Tue, Apr 30, 2013 at 1:41 PM, Randy B=
ush <span dir=3D"ltr">&lt;<a href=3D"mailto:randy@psg.com" target=3D"_blank=
">randy@psg.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
you don&#39;t need a weatherman to know which way the wind blows.<br>
-- bob dylan<br>
<br>
we do not need measurements to know the ietf is embarrassingly<br>
non-diverse. =A0it is derived from and embedded in an embarrassingly<br>
non-diverse culture.<br>
<br>
we need to do what we can to remedy this. =A0progress not perfection is<br>
our goal.<br>
<br>
measurement may be useful to see if we are having effect and/or what<br>
things have effect (meeting locales, size of cookies, ...).<br>
<br>
we should be asking the minorities and those struggling to particiate<br>
what we can do to help.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
randy<br></font></span></blockquote><div><br></div><div>Nicely said Randy. =
--dmm</div><div>=A0</div></div><br>

--001a11c2a88426165504db9a30db--

From drc@virtualized.org  Tue Apr 30 14:37:10 2013
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 DA15E21F9A98 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 14:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.602
X-Spam-Level: 
X-Spam-Status: No, score=-0.602 tagged_above=-999 required=5 tests=[AWL=0.602,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qarsw24AOYMU for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 14:37:04 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 1277421F9A82 for <ietf@ietf.org>; Tue, 30 Apr 2013 14:37:03 -0700 (PDT)
Received: from [10.2.170.191] (mobile-166-137-187-112.mycingular.net [166.137.187.112]) (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 2BE7C17184; Tue, 30 Apr 2013 21:37:02 +0000 (UTC)
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <517FFBAB.3030107@dcrocker.net> <D6317B91-E7EB-499F-BBBF-A78CB44569F9@virtualized.org> <5180099A.8010405@dcrocker.net> <EA2545BD-3060-462B-95CE-36DB5DA3511D@virtualized.org> <51802793.3010003@dcrocker.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51802793.3010003@dcrocker.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <642FECFB-14A1-43C8-81EE-C19A1A0DA80B@virtualized.org>
X-Mailer: iPad Mail (10B329)
From: David Conrad <drc@virtualized.org>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
Date: Tue, 30 Apr 2013 14:37:05 -0700
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
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, 30 Apr 2013 21:37:10 -0000

On Apr 30, 2013, at 1:20 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>>> I've no idea what the lower limit is or should be, but I'm quite sure th=
at 7 years exceeds it by a very comfortable margin.
>> By that logic we should abandon IPv6, DNSSEC, EDNS0, etc.
> Gosh, David.  I guess you win.

Gee Dave, great way to elevate the discussion.

*plonk*



From rdroms.ietf@gmail.com  Tue Apr 30 14:40:45 2013
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 67FF321F9A9A for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 14:40:45 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jdw4gRlzKaEK for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 14:40:45 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id C301421F9A8F for <ietf@ietf.org>; Tue, 30 Apr 2013 14:40:44 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id z24so457686qcq.33 for <ietf@ietf.org>; Tue, 30 Apr 2013 14:40:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=DurBs6u+F30XZ60pB2wO8xolmB3C30KT0FlW867QlGw=; b=fke+AekbqzEH4kWAAHfjWh3xHGTeBljupJoGo+kgtf3KmeMucW/TWlUTidr5IgG95p jTKa8BPw+JYsSyXlbOAHsUtI23ffZYEStlHmcSlPfaYITpnkQuEMq7+BHxOTu071YGUD leuUvZnzO/nYl3+oKUvC8emIUtZVBhoKEnlKPBhG1dI80rZHfovFZ43WU0L1IrRCrA0R 6Qd8qPRVMIC2HJuLyzMznP3UhGXl6Tdpj993VueZqAC8Xxyyfz3Kpr6/K2wNkLswqzmu CDdJMiLPu3mTZ6gSob6qXVWyyQLlXyoN0rs1UiZtyuqgShx81PX5+eSxKFaG8tTlAMIt JZFg==
X-Received: by 10.49.25.112 with SMTP id b16mr220187qeg.21.1367358044083; Tue, 30 Apr 2013 14:40:44 -0700 (PDT)
Received: from ?IPv6:2001:420:2481:20:c402:4f7b:98a8:2177? ([2001:420:2481:20:c402:4f7b:98a8:2177]) by mx.google.com with ESMTPSA id j9sm1185718qas.3.2013.04.30.14.40.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Apr 2013 14:40:42 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Diversity Question on Berlin Registration?
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CAHiKxWi+n5RuODKQSiLooi3V9RH+iWttK4xZZJShyr=hhU-z0Q@mail.gmail.com>
Date: Tue, 30 Apr 2013 17:40:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AB4A673-A4D3-4E8F-B1F0-1791465058F4@gmail.com>
References: <51687C0D.8090804@labn.net> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com> <tsl61z56p12.fsf@mit.edu> <517F1823.4070502@gmail.com> <tslzjwg4ujm.fsf@mit.edu> <3FD89A1B-F1D4-450F-BF38-61250F9A1D83@piuha.net> <m2fvy7sqcw.wl%randy@psg.com> <CAHiKxWi+n5RuODKQSiLooi3V9RH +iWttK4xZZJShyr=hhU-z0Q@mail.gmail.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1503)
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, 30 Apr 2013 21:40:45 -0000

On Apr 30, 2013, at 4:53 PM 4/30/13, David Meyer <dmm@1-4-5.net> wrote:

>=20
>=20
> On Tue, Apr 30, 2013 at 1:41 PM, Randy Bush <randy@psg.com> wrote:
> you don't need a weatherman to know which way the wind blows.
> -- bob dylan
>=20
> we do not need measurements to know the ietf is embarrassingly
> non-diverse.  it is derived from and embedded in an embarrassingly
> non-diverse culture.
>=20
> we need to do what we can to remedy this.  progress not perfection is
> our goal.
>=20
> measurement may be useful to see if we are having effect and/or what
> things have effect (meeting locales, size of cookies, ...).
>=20
> we should be asking the minorities and those struggling to particiate
> what we can do to help.
>=20
> randy
>=20
> Nicely said Randy. --dmm

Agreed - without consulting a weatherman, we've been having a discussion =
(among a rather un-diverse group of participants) about where we are, as =
opposed to asking the questions Randy suggests.

- Ralph

> =20
>=20


From dhc@dcrocker.net  Tue Apr 30 14:42:06 2013
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 6397A21F93E9 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 14:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.58
X-Spam-Level: 
X-Spam-Status: No, score=-6.58 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOrt3G-4AsFF for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 14:42:01 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 98A9721F8AF8 for <ietf@ietf.org>; Tue, 30 Apr 2013 14:41:54 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r3ULfoJY004582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Apr 2013 14:41:53 -0700
Message-ID: <51803A98.6010907@dcrocker.net>
Date: Tue, 30 Apr 2013 14:41:44 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <517FFBAB.3030107@dcrocker.net> <D6317B91-E7EB-499F-BBBF-A78CB44569F9@virtualized.org> <5180099A.8010405@dcrocker.net> <EA2545BD-3060-462B-95CE-36DB5DA3511D@virtualized.org> <51802793.3010003@dcrocker.net> <642FECFB-14A1-43C8-81EE-C19A1A0DA80B@virtualized.org>
In-Reply-To: <642FECFB-14A1-43C8-81EE-C19A1A0DA80B@virtualized.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.66]); Tue, 30 Apr 2013 14:41:53 -0700 (PDT)
Cc: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "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: Tue, 30 Apr 2013 21:42:06 -0000

On 4/30/2013 2:37 PM, David Conrad wrote:
> On Apr 30, 2013, at 1:20 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>>>> I've no idea what the lower limit is or should be, but I'm quite sure that 7 years exceeds it by a very comfortable margin.
>>> By that logic we should abandon IPv6, DNSSEC, EDNS0, etc.
>> Gosh, David.  I guess you win.
>
> Gee Dave, great way to elevate the discussion.


You were discussing?

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From marka@isc.org  Tue Apr 30 14:55:18 2013
Return-Path: <marka@isc.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 50C4721F9A8C for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 14:55:18 -0700 (PDT)
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]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bYXfTEwxgr2t for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 14:55:17 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 90B5A21F9A83 for <ietf@ietf.org>; Tue, 30 Apr 2013 14:55:17 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 8B65AC94CA; Tue, 30 Apr 2013 21:55:10 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367358917; bh=2oHtsE5N+HqBnOzl73Ml1HXftdnodGHZsN9V1DQi9aY=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=fJKEoM4cVE63BxMXI+qAisZZjnq2YCm2y2KoFZghQRm0FQMyb3cCl+wllA/mNLOVr IyBf7xK7HCZZqZ/FNioRva4c0H3IpX7GBvM7T8rdHaFxQvRYNyRkt9+icMGJBDEpKA MCIg50nhCOAkZLjcZut03AE9jMAX4Jtd0qGygSXc=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Tue, 30 Apr 2013 21:55:10 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:9565:f4f6:719e:3954]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 4EAB8216C47; Tue, 30 Apr 2013 21:55:10 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 1B558335F68D; Wed,  1 May 2013 07:54:47 +1000 (EST)
To: dcrocker@bbiw.net
From: Mark Andrews <marka@isc.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <517FFBAB.3030107@dcrocker.net> <D6317B91-E7EB-499F-BBBF-A78CB44569F9@virtualized.org> <5180099A.8010405@dcrocker.net> <EA2545BD-3060-462B-95CE-36DB5DA3511D@virtualized.org> <51802793.3010003@dcrocker.net>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
In-reply-to: Your message of "Tue, 30 Apr 2013 13:20:35 -0700." <51802793.3010003@dcrocker.net>
Date: Wed, 01 May 2013 07:54:46 +1000
Message-Id: <20130430215447.1B558335F68D@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
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, 30 Apr 2013 21:55:18 -0000

In message <51802793.3010003@dcrocker.net>, Dave Crocker writes:
> On 4/30/2013 12:54 PM, David Conrad wrote:
> > On Apr 30, 2013, at 11:12 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> >>> What is the IETF-approved timeframe in which "the market" is allowed to a
> ccept/reject a particular technology?
> >> I've no idea what the lower limit is or should be, but I'm quite sure that
>  7 years exceeds it by a very comfortable margin.
> >
> > By that logic we should abandon IPv6, DNSSEC, EDNS0, etc.
> 
> 
> Gosh, David.  I guess you win.

When just about none of the documentation mentions the SPF record type
nor has examples with both SPF and TXT records it isn't the "market"
choosing.  You can't choose of you really havn't been informed.

		BEWARE OF THE LEOPARD

    "But Mr Dent, the plans have been available in the local planning
     office for the last nine months."

    "Oh yes, well as soon as I heard I went straight round to see
     them, yesterday afternoon. You hadn't exactly gone out of your
     way to call attention to them, had you? I mean, like actually
     telling anybody or anything."

    "But the plans were on display ..."

    "On display? I eventually had to go down to the cellar to find them."

    "That's the display department."

    "With a flashlight."

    "Ah, well the lights had probably gone."

    "So had the stairs."

    "But look, you found the notice didn't you?"

    "Yes," said Arthur, "yes I did. It was on display in the bottom
     of a locked filing cabinet stuck in a disused lavatory with a
     sign on the door saying 'Beware of the Leopard'."

     The Hitchhiker’s Guide to the Galaxy
     Douglas Adams

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From ole@cisco.com  Tue Apr 30 15:23:06 2013
Return-Path: <ole@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 5737421F9AE3 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 15:23:06 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNSxx5k6dN1x for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 15:23:01 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id CE8BF21F9903 for <ietf@ietf.org>; Tue, 30 Apr 2013 15:23:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=936; q=dns/txt; s=iport; t=1367360581; x=1368570181; h=date:from:reply-to:to:subject:message-id:mime-version; bh=jpQ/KwlXm0cv6h9B3wct9008vDxLTBnQaI5o2GVOy4U=; b=JwhJyOW2TNgUBE4Jqga8hQDkUXmtQeG0QhYxT37NfByQbOC3cI6m9RCH g/MgBzq8oI5kVjNcCyQKky4FO5m+Pl2zwJ8B8TqdEZLGM0MVtgDFUbMxk xGbdGZLRbcJAbViXKOG3Yyz1ZWKDbBXLY3Yt4gwe1aMJkBkqJ50ik7J2f M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkQFAAxDgFGrRDoJ/2dsb2JhbABSgwc2AYJvrxqNXRZ0gmCBfRwRh3ENn1+GXol7PY5jknADiReKQIR1hG2LGoMtHA
X-IronPort-AV: E=Sophos;i="4.87,584,1363132800"; d="scan'208";a="76947801"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 30 Apr 2013 22:23:01 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3UMN0SR011840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 30 Apr 2013 22:23:00 GMT
Date: Tue, 30 Apr 2013 15:22:56 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: The IETF <ietf@ietf.org>
Subject: ICANN Nomcom Extends Deadline for SOIs to 15 May 2013
Message-ID: <alpine.OSX.2.01.1304301519320.95603@rabdullah.local>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.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, 30 Apr 2013 22:23:06 -0000

http://www.icann.org/en/news/announcements/announcement-30apr13-en.htm

In order to provide additional time for candidates to apply, ICANN's 
2013 Nominating Committee (NomCom) has extended the deadline for 
Statements of Interest until 15 May 2013 at 23:59 UTC.

The 2013 NomCom is actively seeking qualified candidates for the 
following key positions within ICANN:

* Three members of the Board of Directors of ICANN

* Three members of the At Large Advisory Committee (ALAC) (one each 
  from the Africa, Asia/Australia/Pacific Islands and Latin 
  America/Caribbean Islands regions)

* Two members of the Council of the Generic Names Supporting 
  Organization (GNSO)

* One member of the Council of the Country-Code Names Supporting 
  Organization (ccNSO)

More information about the positions is available at:

http://nomcom.icann.org/positions-2013.htm


Ole J. Jacobsen (2013 ICANN nomcom member)


From ole@cisco.com  Tue Apr 30 16:42:16 2013
Return-Path: <ole@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 C728021F8682 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 16:42:16 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iF1wCxZKhMMR for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 16:42:12 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 5648321F8233 for <ietf@ietf.org>; Tue, 30 Apr 2013 16:42:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=936; q=dns/txt; s=iport; t=1367365332; x=1368574932; h=date:from:reply-to:to:subject:message-id:mime-version: resent-date:resent-from:resent-to:resent-message-id; bh=jpQ/KwlXm0cv6h9B3wct9008vDxLTBnQaI5o2GVOy4U=; b=SM/LfbqzqQlVgEDAT/Aftur1tIJf8umvc1cy+1pI3dh5OKfDnpKbtr1r BXFRRSyvyv1HaS0Sab3pxXfopMX1O1o3uro+o7vVtP7SwNizx8+5EL1HF kEK4Bf8YRRfTz5geEs9H/3KcVjzXymmcNuV0Tc9nDWRvOss5n+3f3pSAC s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkQFAIlVgFGrRDoJ/2dsb2JhbABSgwc2AYJvry+NXRZ0gmCBfRwRh3ENn1GGXol7PY5aknADiReKQIR1hG2LGoMtHA
X-IronPort-AV: E=Sophos;i="4.87,584,1363132800"; d="scan'208";a="79974393"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 30 Apr 2013 23:42:11 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3UNg96W019765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 30 Apr 2013 23:42:10 GMT
Date: Tue, 30 Apr 2013 15:22:56 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: The IETF <ietf@ietf.org>
Subject: ICANN Nomcom Extends Deadline for SOIs to 15 May 2013
Message-ID: <alpine.OSX.2.01.1304301519320.95603@rabdullah.local>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
ReSent-Date: Tue, 30 Apr 2013 16:42:06 -0700 (PDT)
ReSent-From: Ole Jacobsen <ole@cisco.com>
ReSent-To: The IETF <ietf@ietf.org>
ReSent-Subject: ICANN Nomcom Extends Deadline for SOIs to 15 May 2013
ReSent-Message-ID: <alpine.OSX.2.01.1304301642060.96684@rabdullah.local>
ReSent-User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.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, 30 Apr 2013 23:42:16 -0000

http://www.icann.org/en/news/announcements/announcement-30apr13-en.htm

In order to provide additional time for candidates to apply, ICANN's 
2013 Nominating Committee (NomCom) has extended the deadline for 
Statements of Interest until 15 May 2013 at 23:59 UTC.

The 2013 NomCom is actively seeking qualified candidates for the 
following key positions within ICANN:

* Three members of the Board of Directors of ICANN

* Three members of the At Large Advisory Committee (ALAC) (one each 
  from the Africa, Asia/Australia/Pacific Islands and Latin 
  America/Caribbean Islands regions)

* Two members of the Council of the Generic Names Supporting 
  Organization (GNSO)

* One member of the Council of the Country-Code Names Supporting 
  Organization (ccNSO)

More information about the positions is available at:

http://nomcom.icann.org/positions-2013.htm


Ole J. Jacobsen (2013 ICANN nomcom member)



From hartmans@mit.edu  Tue Apr 30 17:45:17 2013
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 008EF21F87B7 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 17:45:17 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAmIM4obcHHw for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 17:45:11 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB6521F85DC for <ietf@ietf.org>; Tue, 30 Apr 2013 17:45:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 9610B20167; Tue, 30 Apr 2013 20:42:56 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j4amHAFAUapU; Tue, 30 Apr 2013 20:42:55 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 30 Apr 2013 20:42:55 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 5EEE24499; Tue, 30 Apr 2013 20:45:04 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: David Conrad <drc@virtualized.org>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com> <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org>
Date: Tue, 30 Apr 2013 20:45:04 -0400
In-Reply-To: <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> (David Conrad's message of "Tue, 30 Apr 2013 12:52:56 -0700")
Message-ID: <tslhain34vj.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: Wed, 01 May 2013 00:45:17 -0000

I think I understand this issue well enough to comment and so I will.

1) I totally believe it is reasonable to consider operational challenges
when designing protocols. "Just upgrade your infrastructure, just use
another registrar, just upgrade the infrastructure of the people you
communicate with," are not generally reasonable advice to give people;
ingoring these concerns tend to lead to things that cannot be deployed.

2) I think it's fine to come up with a solution that   is harder to
implement because it is easier to deploy given the sorts of concerns in
1.

3) having reviewed the DNS arguments, I generally would recommend txt
records with distinct owner names over new RR types for most
protocols. I understand there are residual issues with that approach.

4) Using txt RRs the way SPF does--where the owner name is shared
potentially with other applications is kind of unfortunate.  I don't
know it's unfortunate enough to push for the SPF RR. But the issues
people have brought up with regard to updates and RR order are very
real.
But so are the operational issues with SPF.

So my personal opinion is that this is a valid discussion to be having
even if we're having it again in IETF LC.  However, to be successful we
need to get new participants and to ad more respect for arguments to the
discussion.

From marka@isc.org  Tue Apr 30 18:05:57 2013
Return-Path: <marka@isc.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 E5D7521F888C; Tue, 30 Apr 2013 18:05:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NbPOCqlgEdJC; Tue, 30 Apr 2013 18:05:57 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB6121F884F; Tue, 30 Apr 2013 18:05:57 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 675C1C942D; Wed,  1 May 2013 01:05:45 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367370357; bh=CKJVm/TxwpWQINbuo4dWkOhzTWD+9sLRJqqDa5PtJgk=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=Xxpcth9e55jX85PPjzZQ/YBkJ/7upd3knOSJJUGdhLDUn7RuUCci1ocPVjyaacitB k96BfH+MI2RqaNw39AxZ4Tj10/Q9cXr3rQlLtxK+NH2GjGKAXy+k1vWfG6W2uCt7xA ROI3i66NZtXi9a2t+sQpmmLgSy4lUfZdDMat9Y74=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Wed,  1 May 2013 01:05:45 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:9565:f4f6:719e:3954]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id D6239216C40; Wed,  1 May 2013 01:05:44 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id DE040336241D; Wed,  1 May 2013 11:04:55 +1000 (EST)
To: Alessandro Vesely <vesely@tana.it>
From: Mark Andrews <marka@isc.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
In-reply-to: Your message of "Tue, 30 Apr 2013 18:28:52 +0200." <517FF144.5040600@tana.it>
Date: Wed, 01 May 2013 11:04:52 +1000
Message-Id: <20130501010455.DE040336241D@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: "<spfbis@ietf.org>" <spfbis@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, 01 May 2013 01:05:58 -0000

In message <517FF144.5040600@tana.it>, Alessandro Vesely writes:
> On Tue 30/Apr/2013 01:07:42 +0200 Mark Andrews wrote:
> > 
> > 	The really annoying thing is that SPF is techically superior
> > 	to TXT is lots of ways.
> > 
> > 	1. It uniquely identifies the roll of the record.
> > 
> > 	2. As SPF records are singletons you don't need to identify
> > 	   and remove the old record when updating.  You can just
> > 	   remove all SPF record and add the replacement.
> > 
> > 	   For TXT you need to lookup the existing RRset, extract
> > 	   the v=spf1 record from it.  You then need to create a
> > 	   UPDATE message to delete just that record as well as add
> > 	   the new TXT record.   You then have to hope that no one
> > 	   else is performing a simultanious update as you may get
> > 	   two TXT v=spf1 records in the RRset.
> 
> That's true, except that one has TXT records anyway.

	nsupdate
	update del example.com SPF
	update add example.com 3600 SPF v=spf1 ....
	send

	txt=`dig +short example.com TXT | \
	sed -n -e '/^"v=spf1 /s/^/update del example.com TXT /p' \
	       -e '/^"v=spf1"$/^/update del example.com TXT /p'`
	nsupdate << EOF
	$txt
	update add example.com 3600 TXT v=spf1 ....
	send
	EOF

	But that doesn't work for 'example.com TXT "v" "=" "s" "p" "f" "1"'
	which is a perfectly legal SPF record.

	sed -n -e '/^"v=spf1 /s/^/update del example.com TXT /p' \
	       -e '/^"v" "=spf1 /s/^/update del example.com TXT /p' \
	       -e '/^"v" "=" "spf1 /s/^/update del example.com TXT /p' \
	       -e '/^"v" "=" "s" "pf1 /s/^/update del example.com TXT /p' \
	       -e '/^"v" "=" "s" "p" "f1 /s/^/update del example.com TXT /p' \
	       -e '/^"v" "=" "s" "p" "f" "1 /s/^/update del example.com TXT /p' \
	       -e '/^"v" "=" "s" "p" "f" "1" " /s/^/update del example.com TXT /p' \
	       -e '/^"v=spf1"$/^/update del example.com TXT /p'`
	
	And keep going because the delete needs the rdata to be a
	perfect match to identify the record to be removed.

	I'm sure I could come up with a more compact way of identifying
	a spf record but it wouldn't be needed if people published type
	SPF.

> > 	The complains about using SPF is that there are broken
>p > 	firewalls and some servers drop queries for it, some registars
> > 	don't support it.
> 
> Nits, as explained below.  The basic fact that killed the SPF type is
> the ability to use TXT as a replacement.  There must be an analogous
> of Gresham's law:  "Bad types drive out good ones."
> 
> > 	For firewalls, fix/replace the firewall if you intend to
> > 	deploy SPF and it doesn't support it.  It is total !@##@#
> > 	that firewall are incapable of handling new DNS record
> > 	types.  New records we exected to occur from the very
> > 	beginning and have been coming out regularly ever since the
> > 	DNS was invented.  Firewall vendors that are incapable of
> > 	handling new DNS types are incompetent and do not deserve
> > 	repeat business.
> > 
> > 	For servers than drop SPF queries they really are at the
> > 	noise level.  When you identify one you complain to the
> > 	owners of it.  Yes, that does work.  We needed to do that
> > 	for AAAA records.
> > 
> > 	For registrars, change registrar to one that does.
> 
> While it's too late for SPF, we can learn this lesson.
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Tue Apr 30 18:17:00 2013
Return-Path: <marka@isc.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 F023321F882A for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 18:16:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.989
X-Spam-Level: 
X-Spam-Status: No, score=-0.989 tagged_above=-999 required=5 tests=[AWL=0.370,  BAYES_00=-2.599, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oFPM6KHIHKlV for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 18:16:59 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 32A3121F8443 for <ietf@ietf.org>; Tue, 30 Apr 2013 18:16:59 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id DE11FC94AC; Wed,  1 May 2013 01:16:51 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367371018; bh=s5f7hUgYOIvTtw7PXNDDQJcUtzffjM4QuXlQJpyY3O4=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=RkGfHxsICQLyw/NfVWkJNg6/+vpXVCaXRAwfTPgtsMjvTepUx/IxC03Dw8hSTe0+y 1LNNI1URo+/nbMse6SjyO72KDH5BeMjm6nl3KKW3U8lnB+9VVmGnbrSezotjBwTrR/ TaOEsm2cpJaApk4GdPcBz1kPGyF3GBOTH5snTBmo=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Wed,  1 May 2013 01:16:51 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 3BAEA216C47; Wed,  1 May 2013 01:16:51 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 3922333626A0; Wed,  1 May 2013 11:16:48 +1000 (EST)
To: Doug Barton <dougb@dougbarton.us>
From: Mark Andrews <marka@isc.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
In-reply-to: Your message of "Tue, 30 Apr 2013 10:11:15 -0700." <517FFB33.30902@dougbarton.us>
Date: Wed, 01 May 2013 11:16:48 +1000
Message-Id: <20130501011648.3922333626A0@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
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, 01 May 2013 01:17:00 -0000

In message <517FFB33.30902@dougbarton.us>, Doug Barton writes:
> On 04/30/2013 09:28 AM, Alessandro Vesely wrote:
> > While it's too late for SPF, we can learn this lesson.
> 
> As has been repeatedly pointed out in the discussion on both dnsext and 
> spfbis, it is NOT too late for SPF. The way forward is simple:
> 
> 1. Publish the bis draft which says for senders to publish both SPF and 
> TXT versions, and receivers to query first for the SPF RRtype.
> 
> 2. Update the HOW-TO docs to reflect this change.
> 
> 3. Update the software to query SPF first (Note, Perl's NET::SPF, used 
> by SpamAssassin, already made this change).

As has libspf2.

> 4. Let time pass.
> 
> 5. When the next version of the SPF protocol (v=spf{>1}) comes out make 
> it SPF/99 only.
> 
> The discussion about this on the spfbis list all revolved around the 
> fact that TXT is widespread, SPF/99 is rarely used, so let's just stick 
> with TXT. In a pre-3597 world there _were_ problems with querying for 
> SPF first, so the fact that historically querying for SPF/99 first was 
> painful is a valid data point. However the problems encountered in the 
> early days of SPF deployment with servers not handing unknown types 
> gracefully haven't been relevant for many years now. Yet, the SPF 
> community has continued to push TXT only, in spite of the advice of 
> 4408. Almost like a self-fulfilling prophecy ...
> 
> The reasons brought forward by participants in the spfbis group to not 
> make this change all revolve around the fact that it would involve 
> additional work. Personally I don't find those arguments compelling. 
> First, some of the arguments about the extra work are just plain silly 
> (ala, "cut and paste of the same data for 2 RRtypes is too difficult"). 
> Second, there are not that many implementations that query SPF, and the 
> change is not difficult. Third, most of the "work" to be done is to wait 
> for time to pass and for people to upgrade to the new versions of 
> software. This is a bog-simple "long tail" problem that we deal with in 
> the DNS world all the time.
> 
> There was one objection that made some sense, which is that right now, 
> because the SPF world has steadfastly distributed the advice to use TXT 
> only, querying for SPF/99 first gives you what is likely to be 1 
> spurious DNS lookup per e-mail message. The obvious answer to that is to 
> do a better job of encouraging folks to publish SPF records. Meanwhile, 
> I have a fairly traditional mail server implementation that does a 
> variety of anti-spam checks. By rough count it generates about 8 DNS 
> queries for every message already. Generating 1 more is "in the noise" 
> in the short term, and as shown above goes away in the long term.
> 
> Not only is this a case where doing the right thing is good for SPF, the 
> SPF example of "let's just go with TXT because using a new RRtype is 
> hard" has spread like wildfire, especially in the mail authentication 
> world (DKIM, DMARC, etc.). The slippery slope has been well-greased at 
> this point, and it would be nice to move things back in the right 
> direction (see 5507 for example).
> 
> To be fair, there was one other objection raised, which is that DNS 
> provisioning systems haven't caught up with the need for new RRtypes. So 
> some can't go to their registrar's/web hoster's/etc. web interface and 
> enter a proper SPF record. That's a problem, sure. But it's a problem 
> that has to be solved, assuming we're actually going to take the advice 
> in 5507 seriously. Personally I'm not willing to allow all progress 
> forward in DNS to be stymied by those unwilling to make an investment in 
> their own infrastructure.
> 
> In case Dave is still wondering what all the fuss is about, and because 
> the folks in spfbis seem completely unwilling to deal with this issue in 
> the group, consider this my first draft of an IETF last call objection 
> to the fact that 4408bis wants to deprecate use of the SPF RRtype.
> 
> Doug
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From scott@kitterman.com  Tue Apr 30 19:24:48 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9E4E21F896B for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 19:24:48 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U5cZDywIX01P for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 19:24:35 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id DADD521F89C3 for <ietf@ietf.org>; Tue, 30 Apr 2013 19:24:34 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id E813C20E410C; Tue, 30 Apr 2013 22:24:33 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1367375073; bh=nM+dzFK+5MVkuftSBwd2kennF+zOUCCqrVegxbzuv1k=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nT39UB86tF6nNZdnCDHcLBtcrSm3xv7xyuEkteJpc36Hu9xeNtSNMzn1oZq8i9Hs6 vn92Hdntf/9xrFqO60hb4GWq4IJlhPRodtwJoOVr0u1VmSQhCG9DJrKzYhMiZxfP0T +6TiNkag1eJHWQooIoDdrpN37FAx7ss27dahAkB8=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id CA25220E401D;  Tue, 30 Apr 2013 22:24:33 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
Date: Tue, 30 Apr 2013 22:24:33 -0400
Message-ID: <4012904.ORnHUVMQJP@scott-latitude-e6320>
User-Agent: KMail/4.10.2 (Linux/3.8.0-19-generic; KDE/4.10.2; i686; ; )
In-Reply-To: <20130430215447.1B558335F68D@drugs.dv.isc.org>
References: <20130425013317.36729.qmail@joyce.lan> <51802793.3010003@dcrocker.net> <20130430215447.1B558335F68D@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 May 2013 02:24:49 -0000

On Wednesday, May 01, 2013 07:54:46 AM Mark Andrews wrote:
> In message <51802793.3010003@dcrocker.net>, Dave Crocker writes:
> > On 4/30/2013 12:54 PM, David Conrad wrote:
> > > On Apr 30, 2013, at 11:12 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> > >>> What is the IETF-approved timeframe in which "the market" is allowed
> > >>> to a
> > 
> > ccept/reject a particular technology?
> > 
> > >> I've no idea what the lower limit is or should be, but I'm quite sure
> > >> that
> >
> >  7 years exceeds it by a very comfortable margin.
> >
> > > By that logic we should abandon IPv6, DNSSEC, EDNS0, etc.
> >
> > 
> > 
> >
> > Gosh, David.  I guess you win.
> 
> When just about none of the documentation mentions the SPF record type
> nor has examples with both SPF and TXT records it isn't the "market"
> choosing.  You can't choose of you really havn't been informed.

I've run what I believe to be the most popular online SPF record validator 
since 2005.  You'll find it frequently linked to by other parties:

http://kitterman.com/spf/validate.html

The published SPF record validation part of the tool checks both for records 
of type TXT and of type SPF and mentions the absence of the type SPF record.  
It has done this since I first published the validator (in 2005 I believe, it 
may have been 2006).

So it has been both supported and mentioned.  The only real documentation, RFC 
4408, mentions it effectively enough that some people were fooled into 
believing that publishing type SPF only would be a good idea, fortunately only 
a few were confused by the official documentation.

Scott K

From scott@kitterman.com  Tue Apr 30 19:28:20 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E48021F8AE8 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 19:28:20 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qOAuI7fRB3Pv for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 19:28:15 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 4D43021F8B04 for <ietf@ietf.org>; Tue, 30 Apr 2013 19:28:03 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id CFA9420E410C; Tue, 30 Apr 2013 22:28:02 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1367375282; bh=xhg/41BqCyxmmX9jf8E4xex1Q4MuVXnzvwMDSqzAtcU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nsdta65gkkEOii2SIGNBQtxUzY7lduVcrJZhPyeLURbSQ+h/bDEu4TkldnhGq+wbJ FBodvpl1K0e9qjbHQ5BTF81r/TmoCeZa1Jj2qMiAr0NveFOnex1EAC5nPT67I+qWrG 23PrMmpc2zH6hc13nPtOftSiplUH0wNoNS0dwRPM=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id B212120E401D;  Tue, 30 Apr 2013 22:28:02 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
Date: Tue, 30 Apr 2013 22:28:01 -0400
Message-ID: <5182458.OvNFMaKcjM@scott-latitude-e6320>
User-Agent: KMail/4.10.2 (Linux/3.8.0-19-generic; KDE/4.10.2; i686; ; )
In-Reply-To: <20130501011648.3922333626A0@drugs.dv.isc.org>
References: <20130425013317.36729.qmail@joyce.lan> <517FFB33.30902@dougbarton.us> <20130501011648.3922333626A0@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 May 2013 02:28:20 -0000

On Wednesday, May 01, 2013 11:16:48 AM Mark Andrews wrote:
> > 3. Update the software to query SPF first (Note, Perl's NET::SPF, used 
> > by SpamAssassin, already made this change).

Actually it's Mail::SPF and as we already discussed on the spfbis list this 
design choice caused operational problems and in some cases applications that 
use Mail::SPF have disabled type SPF queries as a result.

One perl module designer being overly theoretically correct doesn't really add 
much to your overly theoretical argument.

So far, compared to the discussion we had in the working group at the time, 
there isn't any new information to evaluate.

Scott K

From superuser@gmail.com  Tue Apr 30 22:03:56 2013
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 64B1821F8AA6 for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 22:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.195
X-Spam-Level: 
X-Spam-Status: No, score=-2.195 tagged_above=-999 required=5 tests=[AWL=0.404,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s2yiRsO3xmmI for <ietf@ietfa.amsl.com>; Tue, 30 Apr 2013 22:03:33 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id E467621F8B0A for <ietf@ietf.org>; Tue, 30 Apr 2013 22:03:18 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id z2so150108wey.18 for <ietf@ietf.org>; Tue, 30 Apr 2013 22:03:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=lH8T/VvpOpeFE8e8BM7e8+EvpWCvvcnC06fb2tzmUAY=; b=AX8eIDFrQZx8fkNNTaburJM2ySoxNS+mI1nqXO4+idXnEdF4sGHmvrJyHDIZzGVOth oTeIO/o4GCID8epxCi12mEjJNES6gByFAb7Z1PjtDxWtrCWOjxsr2Non3lnP2t+M/XLz DGLYJeTlhH0X1JngELaPyI3h6j63uO+DNoaGZODTawkaHvKj//ZotbiQ5Q/KgKDk6Lyp GT3xcRsd/LSBNtLB8pUJsrBAl0+Ph3qqU2RiCrgEWkdeCYFP1JVf2bYuBnPs9DvyjV0b c8yXxdRYVBc2v7WEqyx7R+/O62lsdH3MNj5mVv0o1qETQ3Jg44VvtF3k0I9aoPww0p8I sMJA==
MIME-Version: 1.0
X-Received: by 10.194.222.100 with SMTP id ql4mr1083304wjc.59.1367384588442; Tue, 30 Apr 2013 22:03:08 -0700 (PDT)
Received: by 10.180.14.34 with HTTP; Tue, 30 Apr 2013 22:03:08 -0700 (PDT)
In-Reply-To: <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com> <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org>
Date: Tue, 30 Apr 2013 22:03:08 -0700
Message-ID: <CAL0qLwY3NAtkcznaLf-aNrKtSQLFdrPy4JV=Vmbic5kYB-wfew@mail.gmail.com>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: multipart/alternative; boundary=001a11c1b942aa637204dba10875
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, 01 May 2013 05:03:56 -0000

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

On Tue, Apr 30, 2013 at 12:52 PM, David Conrad <drc@virtualized.org> wrote:

> SPF using TXT and hence, SPFBIS forces the uniquification of the DNS
> response into the application instead of in the DNS library. Given the
> ordering of individual TXT RRs within an RRset is not guaranteed, I suspect
> the chances that every application is going to do that parsing correctly is
> relatively low (btw, the example in 3.3 in spfbis-14 is a bit misleading:
> assuming "second string" is in a separate TXT RR (which is implied), the
> concatenation might be "second stringv=spf1 ..... first").  The more
> interesting bit is if/when another protocol uses TXT at the same ownername.
>

Yes, I understand all of that, and I've written code to deal with it.  It's
not rocket science.


> The RR has been allocated and it is supported in most DNS servers and
> resolver libraries in one form or another.  Provisioning systems take much
> longer, but that isn't surprising and shouldn't be an argument to deprecate
> (if it is, we might as well close the RRtype registry for new entries).
>

We're not only talking about provisioning systems here.  We're also talking
about interference with queries and replies at the DNS protocol level.  The
survey work done for RFC6686 showed that something on the order of
thousands of domains in the sample set suffered from this.  It is a very
real issue for a deployed protocol.


> In the past, the IETF used to make decisions based on long-term
> technical/architectural correctness, even in the face of pragmatic
> complications (e.g., the choice to mandate strong crypto despite real world
> challenges some companies faced in exporting that crypto in products). In
> this particular case, there seems to be an argument to explicitly disallow
> the long-term technically/architecturally correct approach because some
> folks choose not to add an RR to their zone files or support that RR in
> their provisioning systems.  As I said in DNSEXT, this seems like the wrong
> approach to me.
>

All things being equal, I would agree with you.  And if SPF were starting
anew today, I suspect I might have a different opinion.  The question,
then, is the weight of the mitigating circumstances, which obviously the
two communities evaluate quite differently.

-MSK

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

<div dir=3D"ltr">On Tue, Apr 30, 2013 at 12:52 PM, David Conrad <span dir=
=3D"ltr">&lt;<a href=3D"mailto:drc@virtualized.org" target=3D"_blank">drc@v=
irtualized.org</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">SPF using TXT and hence, SPFBIS forces the u=
niquification of the DNS response into the application instead of in the DN=
S library. Given the ordering of individual TXT RRs within an RRset is not =
guaranteed, I suspect the chances that every application is going to do tha=
t parsing correctly is relatively low (btw, the example in 3.3 in spfbis-14=
 is a bit misleading: assuming &quot;second string&quot; is in a separate T=
XT RR (which is implied), the concatenation might be &quot;second stringv=
=3Dspf1 ..... first&quot;). =A0The more interesting bit is if/when another =
protocol uses TXT at the same ownername.<br>
</blockquote><div><br></div><div>Yes, I understand all of that, and I&#39;v=
e written code to deal with it.=A0 It&#39;s not rocket science.<br>=A0<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">

<div class=3D"im">The RR has been allocated and it is supported in most DNS=
 servers and resolver libraries in one form or another. =A0Provisioning sys=
tems take much longer, but that isn&#39;t surprising and shouldn&#39;t be a=
n argument to deprecate (if it is, we might as well close the RRtype regist=
ry for new entries).<br>
</div></blockquote><div><br></div><div>We&#39;re not only talking about pro=
visioning systems here.=A0 We&#39;re also talking about interference with q=
ueries and replies at the DNS protocol level.=A0 The survey work done for R=
FC6686 showed that something on the order of thousands of domains in the sa=
mple set suffered from this.=A0 It is a very real issue for a deployed prot=
ocol.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div class=3D"im"></div>
In the past, the IETF used to make decisions based on long-term technical/a=
rchitectural correctness, even in the face of pragmatic complications (e.g.=
, the choice to mandate strong crypto despite real world challenges some co=
mpanies faced in exporting that crypto in products). In this particular cas=
e, there seems to be an argument to explicitly disallow the long-term techn=
ically/architecturally correct approach because some folks choose not to ad=
d an RR to their zone files or support that RR in their provisioning system=
s. =A0As I said in DNSEXT, this seems like the wrong approach to me.<br>
</blockquote><div><br></div><div>All things being equal, I would agree with=
 you.=A0 And if SPF were starting anew today, I suspect I might have a diff=
erent opinion.=A0 The question, then, is the weight of the mitigating circu=
mstances, which obviously the two communities evaluate quite differently.<b=
r>
<br></div><div>-MSK<br></div></div></div></div>

--001a11c1b942aa637204dba10875--
