
From lars@netapp.com  Mon Sep  3 02:42:29 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA75B21F84EF; Mon,  3 Sep 2012 02:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.749
X-Spam-Level: 
X-Spam-Status: No, score=-9.749 tagged_above=-999 required=5 tests=[AWL=-0.549, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tGbcxIysSUVf; Mon,  3 Sep 2012 02:42:29 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0DC4521F84EB; Mon,  3 Sep 2012 02:42:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,359,1344236400";  d="p7s'?scan'208";a="685141113"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 03 Sep 2012 02:42:25 -0700
Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q839gPBt008870; Mon, 3 Sep 2012 02:42:25 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.212]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0309.002; Mon, 3 Sep 2012 02:42:24 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: IETF IETF <ietf@ietf.org>, "85attendees@ietf.org" <85attendees@ietf.org>
Subject: Fwd: [irtf-discuss] Applied Networking Research Prize 2012 presentation	s at IETF-85
Thread-Topic: [irtf-discuss] Applied Networking Research Prize 2012 presentation	s at IETF-85
Thread-Index: AQHNibhrNXj0dcB7WUyLnz1+LdBrOQ==
Date: Mon, 3 Sep 2012 09:42:11 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E906801AAB@SACEXCMBX01-PRD.hq.netapp.com>
References: <D4D47BCFFE5A004F95D707546AC0D7E9068019D6@SACEXCMBX01-PRD.hq.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_8B2E7984-73D3-4A0A-8180-0DA1AE1DEBF7"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.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: Mon, 03 Sep 2012 09:42:29 -0000

--Apple-Mail=_8B2E7984-73D3-4A0A-8180-0DA1AE1DEBF7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1



Begin forwarded message:

> From: "Eggert, Lars" <lars@netapp.com>
> Subject: [irtf-discuss] Applied Networking Research Prize 2012 =
presentation	s at IETF-85
> Date: September 3, 2012 11:38:33 GMT+02:00
> To: "irtf-announce@irtf.org" <irtf-announce@irtf.org>, =
"irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
> Reply-To: "anrp@irtf.org" <anrp@irtf.org>
>=20
>=20
> Hi,
>=20
> we are extremely pleased to report that for the 2012 award period of
> the Applied Networking Research Prize (ANRP), 20 eligible nominations
> were received. Each submission was reviewed by 5-7 members of the
> selection committee according to a diverse set of criteria, including
> scientific excellence and substance, timeliness, relevance, and
> potential impact on the Internet.
>=20
> Based on this review, three submissions were awarded an Applied
> Networking Research Prize in 2012. One of these submissions was =
already
> presenteded at IETF-84 in Vancouver, Canada. Two additional winning
> papers will be presented at IETF-85 in Atlanta, USA. The awards for
> IETF-85 go to:
>=20
>  *** Srikanth Sundaresan *** for his measurement study of
>  access link performance on home gateway devices:
>=20
>    Srikanth Sundaresan, Walter de Donato, Nick Feamster, Renata
>    Teixeira, Sam Crawford and Antonio Pescap=E8. Broadband
>    Internet Performance: A View =46rom the Gateway. Proc. ACM
>    SIGCOMM,August 2011, Toronto, Canada.
>=20
>  *** Peyman Kazemian *** for developing a general and
>  protocol-agnostic framework for statically checking network
>  specifications and configurations:
>=20
>    Peyman Kazemian, George Varghese and Nick McKeown. Header
>    Space Analysis: Static Checking For Networks. Proc. USENIX
>    Symposium on Networked Systems Design and Implementation
>    (NSDI), April 2012, San Jose, CA, USA.
>=20
> Srikanth and Peyman have been invited to present their findings in the
> IRTF Open Meeting during IETF-85, November 4-9, 2012 in Atlanta, GA,
> USA. Join them there!
>=20
> The call for ANRP nominations for the 2013 awards cycle will open in =
the
> fall of 2012. Read more about the ANRP at http://irtf.org/anrp.
>=20
> Please subscribe to the IRTF-Announce mailing list in order to receive
> future calls for ANRP nominations and join ISOC to stay informed of
> other networking research initiatives:
>=20
> http://irtf.org/mailman/listinfo/irtf-announce
> http://isoc.org/join
>=20
> Regards,
>=20
> Lars Eggert, IRTF Chair            http://irtf.org/anrp
> Mat Ford, Internet Society         http://isoc.org/research
>=20
> --
>=20
> 2012 ANRP Selection Committee
>=20
> Mark Allman, ICIR
> Marcelo Bagnulo, UC3M
> Lou Berger, LabN
> Olivier Bonaventure, UCL Louvain
> Ross Callon, Juniper
> Lars Eggert, NetApp
> Olivier Festor, INRIA
> Mat Ford, ISOC
> Lisandro Granville, UFRGS
> Andrei Gurtov, HIIT
> Dan Massey, Colorado State
> Al Morton, AT&T Laboratories
> J=F6rg Ott, Aalto University
> Colin Perkins, University of Glasgow
> Stefano Previdi, Cisco
> J=FCrgen Sch=F6nw=E4lder, Jacobs University Bremen
> Lixia Zhang, UCLA


--Apple-Mail=_8B2E7984-73D3-4A0A-8180-0DA1AE1DEBF7
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDkwMzA5NDIxOFowIwYJKoZIhvcNAQkEMRYEFCc9
S1IRvZa/TIQSiWxEZfpMTNEjMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAAwuI5yQ
fdTDDr9jiAog/Qq0JudNJspQ1FmJnfIsD2DVyvZfamg2VVNeiuNSOdH0tthVEcq7k/pzI9ZKJRp9
5DVJkELmoHM/qWazoOGFhAu4SVXKT0Mkf4b+AmwmgkHu+cgW70p14yG025vQb9gk0/9uD6fHwVVp
0v1E08f67mvgIw6sPMiOVOL8S+Ilr0n6mob7UvbdJZZwR/KqiSjK8X6WkfxB8KtY37gvG7LiceuA
pP5vEZKawB8wrUy9mCDR4EfXs+mGlZh0Dr3Q/Hz0NbMEMKokbPYUFFTdf6y92YKFmj6XskcZrhS8
7WO9YpM2x3rg9LrZghgGkegHFu0u4+kAAAAAAAA=

--Apple-Mail=_8B2E7984-73D3-4A0A-8180-0DA1AE1DEBF7--

From chair@ietf.org  Mon Sep  3 17:00:49 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 218E121F8634 for <ietf@ietfa.amsl.com>; Mon,  3 Sep 2012 17:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level: 
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zBr83I2aU58Q for <ietf@ietfa.amsl.com>; Mon,  3 Sep 2012 17:00:48 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id B3F0A21F861D for <ietf@ietf.org>; Mon,  3 Sep 2012 17:00:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id AF7BD12CE11 for <ietf@ietf.org>; Mon,  3 Sep 2012 17:00:48 -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 Tj9QLZ+Edh1U for <ietf@ietf.org>; Mon,  3 Sep 2012 17:00:48 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 6998E12CE10 for <ietf@ietf.org>; Mon,  3 Sep 2012 17:00:48 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Date: Mon, 3 Sep 2012 20:00:46 -0400
Message-Id: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Sep 2012 00:00:49 -0000

The IESG is considering this IESG Statement.  Comments from the =
community are solicited.

On behalf of the IESG,
Russ

--- DRAFT IESG STATEMENT ---

SUBJECT: Removal of an Internet-Draft from the IETF Web Site

Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,
and its Working Groups.  In addition, other groups, including the IAB
and the IRTF Research Groups, distribute working documents as I-Ds.
I-Ds are stored in two places on the IETF web site.  First, current
ones are stored in the I-D directory.  Second, current and past ones
are stored in a public I-D archive.

I-Ds are readily available to a wide audience from the IETF I-D
directory.  This availability facilitates informal review, comment,
and revision.

While entries in the I-D directory are subject to change or removal
at any time, I-Ds generally remain publicly archived to support easy
comparison with previous versions.

Entries in the I-D directory are removed as part of normal process
when it expires after six months, when it is replaced by a subsequent
I-D, or when it is replaced by the publication of an RFC.  In all
of these situations, the I-D remains in the public I-D archive.

An I-D will only be removed from the public I-D archive in compliance
with a duly authorized court order.  If possible, a removed I-D will be
replaced with a tombstone file that describes the reason that the I-D
was removed from the public I-D archive.


From chair@ietf.org  Mon Sep  3 17:02:24 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80DE721F8645 for <ietf@ietfa.amsl.com>; Mon,  3 Sep 2012 17:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B6jcnRp3EsSZ for <ietf@ietfa.amsl.com>; Mon,  3 Sep 2012 17:02:23 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED6121F8643 for <ietf@ietf.org>; Mon,  3 Sep 2012 17:02:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 69DA512CE11 for <ietf@ietf.org>; Mon,  3 Sep 2012 17:02:23 -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 TpvFsp0G7q-q for <ietf@ietf.org>; Mon,  3 Sep 2012 17:02:23 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 2638A12CE0E for <ietf@ietf.org>; Mon,  3 Sep 2012 17:02:23 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Date: Mon, 3 Sep 2012 20:02:21 -0400
Message-Id: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Sep 2012 00:02:24 -0000

The IESG is considering this IESG Statement.  Comments from the =
community are solicited.

On behalf of the IESG,
Russ

--- DRAFT IESG STATEMENT ---

Subject: Ethertype Assignments for IETF Protocols

The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
(See http://standards.ieee.org/develop/regauth/ethertype/.)  Some IETF
protocol specification make use of Ethertypes.  Since Ethertypes are a
fairly scarce resource, the IEEE RAC will not assign a new Ethertype to
a new IETF protocol specification that needs one until the IESG has
approved the protocol specification for publication as an RFC.

To let the IEEE RAC know that the IESG has approved an IETF protocol
specification for publication, all future requests for assignment of
Ethertypes for IETF protocol specifications will be made by the IESG.

Note that playpen Ethertypes have been assigned in IEEE 802 [1] for use
during development and experimentation.


[1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
   IEEE standard for Local and Metropolitan Area Networks:
   Overview and Architecture -- Amendment 1: Ethertypes for
   Prototype and Vendor-Specific Protocol Development.



From dhc@dcrocker.net  Mon Sep  3 17:44:22 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9452F21F8552; Mon,  3 Sep 2012 17:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.542
X-Spam-Level: 
X-Spam-Status: No, score=-6.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRCXwH6vqGC8; Mon,  3 Sep 2012 17:44:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0A69521F8551; Mon,  3 Sep 2012 17:44:21 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q840iKT5023527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 3 Sep 2012 17:44:20 -0700
Message-ID: <50454EE4.5070203@dcrocker.net>
Date: Mon, 03 Sep 2012 17:44:20 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: IETF Chair <chair@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
In-Reply-To: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=ISO-8859-1
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, 03 Sep 2012 17:44:20 -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: Tue, 04 Sep 2012 00:44:22 -0000

On 9/3/2012 5:00 PM, IETF Chair wrote:
> The IESG is considering this IESG Statement.  Comments from the community are solicited.

1.  Unless I've missed something, the statement seems to reflect
established practice and established policy.  Or is it changing something?

2.  I had thought that somesuch statement had already been issued, but
apparently not.  If there is a preceding document -- I can't think of
one -- then any change from it's text would be worth noting.

3.  It would be worth clarify what prompts issuing this now.

d/
-- 
 Dave Crocker
 Brandenburg InternetWorking
 bbiw.net

From hartmans@mit.edu  Mon Sep  3 18:29:23 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF78321F861E; Mon,  3 Sep 2012 18:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.604
X-Spam-Level: 
X-Spam-Status: No, score=-92.604 tagged_above=-999 required=5 tests=[FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.935, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T4T-f2FMVuC1; Mon,  3 Sep 2012 18:29:23 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id 73D6D21F861C; Mon,  3 Sep 2012 18:29:18 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 0DE902039E; Mon,  3 Sep 2012 21:29:10 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 91E564148; Mon,  3 Sep 2012 21:29:00 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: IETF Chair <chair@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
Date: Mon, 03 Sep 2012 21:29:00 -0400
In-Reply-To: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> (IETF Chair's message of "Mon, 3 Sep 2012 20:00:46 -0400")
Message-ID: <tslmx168tk3.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: Tue, 04 Sep 2012 01:29:24 -0000

I strongly urge  the IESG to be significantly more liberal in  the cases
where an I-D will be removed from the archive.

I can think of a number of cases where I'd hope that the IESg would be
cooperative:

1) the IETF recieves a DMCA take-down notice or other instrument
indicating that a third party believes an I-D infringes their copyright.
Forcing such third parties to take the IETF to court does not seem to
benefit the community.

2) An author realizes that an I-D accidentally contains proprietary
information, infringes someone else's copyright, failed to go through
external release processes for the author/editor's organization, etc.
Obviously factors like how long after the I-D is submitted might need to
be considered.


In conclusion, I believe there are a number of cases where the interests
of the community are better served by being able to ask for removal from
the archive. Being able to easily repair mistakes  is likely to
facilitate  more free discussion and more speedy updating of I-Ds.
Yes, I'm aware  that organizations other than the IETF mirror the i-ds
and some of these organizations will be less sympathetic to these
concerns.

From joelja@bogus.com  Mon Sep  3 20:36:59 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00ECE21F85F0; Mon,  3 Sep 2012 20:36: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c6hqFMkQCkc9; Mon,  3 Sep 2012 20:36:58 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3015721F8499; Mon,  3 Sep 2012 20:36:58 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (71-93-165-75.dhcp.hspr.ca.charter.com [71.93.165.75]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q843auVc011996 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 4 Sep 2012 03:36:57 GMT (envelope-from joelja@bogus.com)
Message-ID: <50457753.70402@bogus.com>
Date: Mon, 03 Sep 2012 20:36:51 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu>
In-Reply-To: <tslmx168tk3.fsf@mit.edu>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=ISO-8859-1
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, 04 Sep 2012 03:36:57 +0000 (UTC)
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Sep 2012 03:36:59 -0000

On 9/3/12 18:29 , Sam Hartman wrote:
> I strongly urge  the IESG to be significantly more liberal in  the cases
> where an I-D will be removed from the archive.
> 
> I can think of a number of cases where I'd hope that the IESg would be
> cooperative:
> 
> 1) the IETF recieves a DMCA take-down notice or other instrument
> indicating that a third party believes an I-D infringes their copyright.
> Forcing such third parties to take the IETF to court does not seem to
> benefit the community.

non-laywer here,

The IETF is not an ISP and does not accordingly have safe harbor
privileges. I doubt very much  that it would be appropriate to dutifully
remove content merely on the basis of a dmca takedown request.

> 2) An author realizes that an I-D accidentally contains proprietary
> information, infringes someone else's copyright, failed to go through
> external release processes for the author/editor's organization, etc.
> Obviously factors like how long after the I-D is submitted might need to
> be considered.
> 
> 
> In conclusion, I believe there are a number of cases where the interests
> of the community are better served by being able to ask for removal from
> the archive. Being able to easily repair mistakes  is likely to
> facilitate  more free discussion and more speedy updating of I-Ds.
> Yes, I'm aware  that organizations other than the IETF mirror the i-ds
> and some of these organizations will be less sympathetic to these
> concerns.
> 


From brian.e.carpenter@gmail.com  Tue Sep  4 02:30:46 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ACC621F865F; Tue,  4 Sep 2012 02:30:46 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y5HGBJ18XurI; Tue,  4 Sep 2012 02:30:45 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id CBA5521F8658; Tue,  4 Sep 2012 02:30:44 -0700 (PDT)
Received: by eaai11 with SMTP id i11so1864672eaa.31 for <multiple recipients>; Tue, 04 Sep 2012 02:30:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PvsEqjOscyieV77M3dAwzTF29iDjjQdtKoovI4svnJk=; b=oeMN5bTBO02jhVyWSez2ve1O0aGUlJD5LAo3DmW+djfiv/2Tg0xOzDPcPJg4beA5EB 0kor82YqtpZq21ZTq0J9PELLPEBcweTLkWRutzoDwsiRsPmnOZon0t/LP0TB/0DRSSd4 ezdSU4LjXGHxOqi5MG80/7wgZ5k3FuwtOnXPuIsxYln/BgbGnK3ng2r1xbcRxW3F317B t+vPOVzhecluiNlUwh1QzzqBwYrJIOU/22Mp84X0Hgq6fOxAr3ekeK+ewAraL/BUFJzq 7+mpvKcdaU0GIE5cgR8704SCkFUCFCbtRiRWHVdN0Fzr8fC8kSJIpnearaa2R23fPzGJ V9XA==
Received: by 10.14.203.69 with SMTP id e45mr25188649eeo.23.1346751043757; Tue, 04 Sep 2012 02:30:43 -0700 (PDT)
Received: from [128.232.110.103] (c103.al.cl.cam.ac.uk. [128.232.110.103]) by mx.google.com with ESMTPS id i8sm43723991eeo.16.2012.09.04.02.30.42 (version=SSLv3 cipher=OTHER); Tue, 04 Sep 2012 02:30:42 -0700 (PDT)
Message-ID: <5045CA44.2010206@gmail.com>
Date: Tue, 04 Sep 2012 10:30:44 +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: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu>
In-Reply-To: <tslmx168tk3.fsf@mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Sep 2012 09:30:46 -0000

Without commenting on Sam's specific examples, I think the policy
should include a "generally" or "normally" weasel word, so that
the IESG can make exceptions in unusual circumstances.

It really should be unusual though. A real case some years ago
involved a dispute between an ex-employee and ex-employer about
who had the right to update a non-WG draft. The IETF shouldn't be in the
business of deciding disputes of that kind, which could happen
any time.

Regards
   Brian Carpenter

On 04/09/2012 02:29, Sam Hartman wrote:
> I strongly urge  the IESG to be significantly more liberal in  the cases
> where an I-D will be removed from the archive.
> 
> I can think of a number of cases where I'd hope that the IESg would be
> cooperative:
> 
> 1) the IETF recieves a DMCA take-down notice or other instrument
> indicating that a third party believes an I-D infringes their copyright.
> Forcing such third parties to take the IETF to court does not seem to
> benefit the community.
> 
> 2) An author realizes that an I-D accidentally contains proprietary
> information, infringes someone else's copyright, failed to go through
> external release processes for the author/editor's organization, etc.
> Obviously factors like how long after the I-D is submitted might need to
> be considered.
> 
> 
> In conclusion, I believe there are a number of cases where the interests
> of the community are better served by being able to ask for removal from
> the archive. Being able to easily repair mistakes  is likely to
> facilitate  more free discussion and more speedy updating of I-Ds.
> Yes, I'm aware  that organizations other than the IETF mirror the i-ds
> and some of these organizations will be less sympathetic to these
> concerns.
> 

From vesely@tana.it  Tue Sep  4 04:20:41 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94D6A21F8552 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 04:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.347
X-Spam-Level: 
X-Spam-Status: No, score=-4.347 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JS4XdDedTeBE for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 04:20:41 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id BC7B521F8523 for <ietf@ietf.org>; Tue,  4 Sep 2012 04:20:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1346757639; bh=9IeQywbXRZ4d3ny7LbFUvglb8FtTZO3ffbbsunF2FjI=; l=921; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=eGn4b9pfDp5XKwjYQ+axQlxr0c0DUxujO3mZFS60msG3suCoFnhLe3sjAAHPNeItS HhGjF3r4Ivw28Rconuc+DxtHa0jjlsrjglC8LFlQAWEDJ5rc7T9QXOejDogWg94nsm XzrjgmN46TLL4CliSQ2J29gXP33EcHMCuq/NxFUs=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 04 Sep 2012 13:20:39 +0200 id 00000000005DC033.000000005045E407.000056A3
Message-ID: <5045E407.6050102@tana.it>
Date: Tue, 04 Sep 2012 13:20:39 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu>
In-Reply-To: <tslmx168tk3.fsf@mit.edu>
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: Tue, 04 Sep 2012 11:20:41 -0000

The first paragraph says:

 Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,
 and its Working Groups.  In addition, other groups, including the IAB
 and the IRTF Research Groups, distribute working documents as I-Ds.

After all the groups, I'd add "and individuals".

On Tue 04/Sep/2012 03:29:00 +0200 Sam Hartman wrote:
> 
> 2) An author realizes that an I-D accidentally contains proprietary
> information, infringes someone else's copyright, failed to go through
> external release processes for the author/editor's organization, etc.
> Obviously factors like how long after the I-D is submitted might need to
> be considered.

Except for I-Ds that reveal secret text, infringements should only
result from inappropriate boilerplate copyright claims.  It would be
enough to tag such I-Ds with a suitable disclaimer, in a way similar
to how the presence of errata is (not) handled.


From sob@sobco.com  Tue Sep  4 04:27:35 2012
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 233F921F8568; Tue,  4 Sep 2012 04:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZEpCLUMjAieC; Tue,  4 Sep 2012 04:27:34 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id A329021F8525; Tue,  4 Sep 2012 04:27:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 649C239564E4; Tue,  4 Sep 2012 07:27:33 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aX16kuS--mhe; Tue,  4 Sep 2012 07:27:30 -0400 (EDT)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by sobco.sobco.com (Postfix) with ESMTPSA id 1E6B439564CE; Tue,  4 Sep 2012 07:27:30 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <tslmx168tk3.fsf@mit.edu>
Date: Tue, 4 Sep 2012 07:27:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <59D5DC3D-AC29-48AC-BDA0-B7AD77DCBA41@sobco.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1486)
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Sep 2012 11:27:35 -0000

in addition
since there is no admissions control on IDs I would think that the IESG =
would want=20
to reserve the option to remove an ID that contained clear libel or =
inappropriate=20
material (e.g., a pornographic story published as an ID as part of a DoS =
attack
on the IETF) once the IESG had been given notice of such material

Scott

On Sep 3, 2012, at 9:29 PM, Sam Hartman <hartmans-ietf@mit.edu> wrote:

> I strongly urge  the IESG to be significantly more liberal in  the =
cases
> where an I-D will be removed from the archive.
>=20
> I can think of a number of cases where I'd hope that the IESg would be
> cooperative:
>=20
> 1) the IETF recieves a DMCA take-down notice or other instrument
> indicating that a third party believes an I-D infringes their =
copyright.
> Forcing such third parties to take the IETF to court does not seem to
> benefit the community.
>=20
> 2) An author realizes that an I-D accidentally contains proprietary
> information, infringes someone else's copyright, failed to go through
> external release processes for the author/editor's organization, etc.
> Obviously factors like how long after the I-D is submitted might need =
to
> be considered.
>=20
>=20
> In conclusion, I believe there are a number of cases where the =
interests
> of the community are better served by being able to ask for removal =
from
> the archive. Being able to easily repair mistakes  is likely to
> facilitate  more free discussion and more speedy updating of I-Ds.
> Yes, I'm aware  that organizations other than the IETF mirror the i-ds
> and some of these organizations will be less sympathetic to these
> concerns.


From paul.hoffman@vpnc.org  Tue Sep  4 07:38:20 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA25211E8097 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 07:38: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uuR7F39PwXs8 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 07:38:20 -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 2235D21F845F for <ietf@ietf.org>; Tue,  4 Sep 2012 07:38:20 -0700 (PDT)
Received: from [10.20.30.108] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q84EcFrR079034 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 4 Sep 2012 07:38:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <5045E407.6050102@tana.it>
Date: Tue, 4 Sep 2012 07:38:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A819AD9-9C8A-450D-8F06-AAB194F5387D@vpnc.org>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu> <5045E407.6050102@tana.it>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1486)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Sep 2012 14:38:20 -0000

On Sep 4, 2012, at 4:20 AM, Alessandro Vesely <vesely@tana.it> wrote:

> The first paragraph says:
>=20
> Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,
> and its Working Groups.  In addition, other groups, including the IAB
> and the IRTF Research Groups, distribute working documents as I-Ds.
>=20
> After all the groups, I'd add "and individuals".

+1. Internet Drafts are also required for publication in the Independent =
Submission stream of RFCs. They are also used by individuals who make =
proposals that they hope will later become WG items, but are not =
"working documents" of the WG when they are written.

--Paul Hoffman=

From dhc@dcrocker.net  Tue Sep  4 07:46:35 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F29BD21E8039 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 07:46:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSTGTKNfwWmV for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 07:46:34 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD0421E8034 for <ietf@ietf.org>; Tue,  4 Sep 2012 07:46:34 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q84EkW6W021066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 4 Sep 2012 07:46:33 -0700
Message-ID: <50461447.1010608@dcrocker.net>
Date: Tue, 04 Sep 2012 07:46:31 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu> <5045E407.6050102@tana.it> <6A819AD9-9C8A-450D-8F06-AAB194F5387D@vpnc.org>
In-Reply-To: <6A819AD9-9C8A-450D-8F06-AAB194F5387D@vpnc.org>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 04 Sep 2012 07:46:33 -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: Tue, 04 Sep 2012 14:46:35 -0000

> +1. Internet Drafts are also required for publication in the Independent Submission stream of RFCs. They are also used by individuals who make proposals that they hope will later become WG items, but are not "working documents" of the WG when they are written.


So are Independent submission RFCs:

   http://www.rfc-editor.org/indsubs.html

d/


-- 
 Dave Crocker
 Brandenburg InternetWorking
 bbiw.net

From johnl@iecc.com  Tue Sep  4 07:48:30 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73AF221F8510 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 07:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ljBiIVi35iQN for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 07:48:29 -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 AC20F21F84FE for <ietf@ietf.org>; Tue,  4 Sep 2012 07:48:28 -0700 (PDT)
Received: (qmail 35163 invoked from network); 4 Sep 2012 14:48:26 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 Sep 2012 14:48:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504614ba.xn--3zv.k1208; i=johnl@user.iecc.com; bh=MNjNG4mWCirqlF+QhHvkfLiF3UL/aiO2tleiBUL52+s=; b=R/3M9HSVrwzvO1vctw8WyqxknnJgsUpF3l1+/7a4k44fe9OvV8+oQeJZJpFpu/xPGS6oSSMGZAwm4A7qGE7LkQxgHgaLhWNgleikzgXYRnYHVp17VnZw7PUb/kTX7z784tbqKb1g22WWYjlvXSB7Q9JGNf6chYeZTp1s64KujZ4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504614ba.xn--3zv.k1208; olt=johnl@user.iecc.com; bh=MNjNG4mWCirqlF+QhHvkfLiF3UL/aiO2tleiBUL52+s=; b=jemLr9uk4pChbEm6O/ES56vWJlVjq3hRo+qZwSZTE5onra9mUiomRXtFlXihoyQdXJ1+EQerHJBAVnpQ69G4ey0OdMI7fssHrao1YtoLaYey7cYmnk+8rcBnaoCnLooH/UivzZvpvz6N/Umo5X3+S3k4qSpMzJ0HhI0EX3GvPFo=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 4 Sep 2012 14:48:04 -0000
Message-ID: <20120904144804.10020.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <50457753.70402@bogus.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: Tue, 04 Sep 2012 14:48:30 -0000

>non-laywer here,
>
>The IETF is not an ISP and does not accordingly have safe harbor privileges. 

Junior Lawyer here.  A quick look at the law, or even the Wikipedia
article about it
(http://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act)
reveals that the DMCA refers to "online service providers" which in
context means whoever runs the server hosting the content.  That would
be some combination of the IETF and AMS.

If someone served AMS with a DMCA complaint, the options are basically
that they remove the allegedly infringing material, or that the party
providing the material to them, who might be the IETF or the I-D
author, provide a counternotice that the material is not infringing.
In either case, AMS is off the hook, but in the latter case, the IETF
would probably have to defend if the party sending the original notice
decided to sue.

The IETF may well be able to argue that it too is a conduit just
hosting the I-D's since I-Ds are posted by individuals using an
automated process, but that is the kind of argument that makes lawyers
wealthy, no matter who finally wins.

As far as I am aware, there's never been a DMCA notice for an I-D, and
with any luck there never will be, but in practice, a reasonable
policy is that if a proper DMCA notice (one that contains all six of
the required elements) arrives about an I-D, take it down unless the
I-D author provides a counternotice and indemnifies the IETF.

R's,
John





From adrian@olddog.co.uk  Tue Sep  4 08:08:18 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A87721F855D for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 08:08: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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQSN12RbTSa0 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 08:08:16 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 1C24B21F855A for <ietf@ietf.org>; Tue,  4 Sep 2012 08:08:13 -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 q84F86F6021011;  Tue, 4 Sep 2012 16:08:07 +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 q84F85vn020993 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 4 Sep 2012 16:08:06 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'John Levine'" <johnl@taugh.com>
Subject: RE: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Date: Tue, 4 Sep 2012 16:08:05 +0100
Message-ID: <01f001cd8aaf$16d57450$44805cf0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2KrxKwnV+TxpxmQFaOp/Q4dvMj0w==
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: Tue, 04 Sep 2012 15:08:18 -0000

Hi John,

This discussion of DMCA is useful to me as a non-US resident.

Are we sure that the boilerplate included in I-Ds does not constitute a =
statement by the authors that they have not, as far as they are aware, =
infringed any copyright? In other words, isn't the boilerplate a =
pre-emptive counternotice?

Cheers,
Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of John
> Levine
> Sent: 04 September 2012 15:48
> To: ietf@ietf.org
> Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from =
the IETF
> Web Site
>=20
> >non-laywer here,
> >
> >The IETF is not an ISP and does not accordingly have safe harbor =
privileges.
>=20
> Junior Lawyer here.  A quick look at the law, or even the Wikipedia
> article about it
> =
(http://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Lim=
itatio
> n_Act)
> reveals that the DMCA refers to "online service providers" which in
> context means whoever runs the server hosting the content.  That would
> be some combination of the IETF and AMS.
>=20
> If someone served AMS with a DMCA complaint, the options are basically
> that they remove the allegedly infringing material, or that the party
> providing the material to them, who might be the IETF or the I-D
> author, provide a counternotice that the material is not infringing.
> In either case, AMS is off the hook, but in the latter case, the IETF
> would probably have to defend if the party sending the original notice
> decided to sue.
>=20
> The IETF may well be able to argue that it too is a conduit just
> hosting the I-D's since I-Ds are posted by individuals using an
> automated process, but that is the kind of argument that makes lawyers
> wealthy, no matter who finally wins.
>=20
> As far as I am aware, there's never been a DMCA notice for an I-D, and
> with any luck there never will be, but in practice, a reasonable
> policy is that if a proper DMCA notice (one that contains all six of
> the required elements) arrives about an I-D, take it down unless the
> I-D author provides a counternotice and indemnifies the IETF.
>=20
> R's,
> John
>=20
>=20



From john-ietf@jck.com  Tue Sep  4 08:16:57 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6E5421F8552; Tue,  4 Sep 2012 08:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U1ISrVbf4vg6; Tue,  4 Sep 2012 08:16:57 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 09C6021F84F1; Tue,  4 Sep 2012 08:16:57 -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 1T8us2-000Ge4-Id; Tue, 04 Sep 2012 11:16:54 -0400
Date: Tue, 04 Sep 2012 11:16:49 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott O Bradner <sob@sobco.com>, Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <398A8C589D728538A91448D3@JcK-HP8200.jck.com>
In-Reply-To: <59D5DC3D-AC29-48AC-BDA0-B7AD77DCBA41@sobco.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu> <59D5DC3D-AC29-48AC-BDA0-B7AD77DCBA41@sobco.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 Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Sep 2012 15:16:58 -0000

Hi.

I agree with Sam and Scott.  Let me add one more piece to that
picture:

We have spent many years saying not only "I-Ds expire" but "I-Ds
are not an archival series".   While I've gradually come around
to the advantages of the IETF maintaining an archive of old ones
and making it accessible, I think there are many reasons for not
promising that.  From the IETF's point of view, perhaps the most
important of those reasons is the seemingly-perennial argument
that we have about whether the existence of non-standards-track
RFCs is either misleading or provides an unnecessary avenue for
abuse by those who want to imply IETF approval when none exists.
We've seen the same games played with I-Ds, e.g., "post an I-D
and then advertise 'under consideration in the IETF" or even
"being standardized by the IETF".

I think the IESG should have the authority (and responsibility)
to remove I-Ds from the public archive, not just on the basis of
court orders and the like, but in response to any strong
evidence of abuse, without our having to try to enumerate all
categories of abuses in advance.  I think that such a decision
should be announced so that it can be appealed if necessary, but
that, to avoid both general annoyance/noise and DoS attacks, we
not get trapped into considering taking down a document to be a
consensus matter.  It is not an archival series and we should
not promise that it will be maintained as one.

If Counsel advises that we keep copies of anything that is taken
down so that, e.g., we can respond to court orders to produce or
authenticate it (at least unless a court of final jurisdiction
orders us to discard it), I'm find with that, but the draft
statement doesn't address the disposition of documents that are
removed from the web site at all.

I also believe that the IESG should reestablish policies that
permit WGs (or their leadership), ADs responsible for WG
documents, or submitters of individual or other-stream documents
to pre-expire them --i.e., have them moved from the I-D
directory and "active" status in the tracker.  When such
documents were posted in error or are clearly at risk of
becoming a distraction, the community is not well-served by
insisting that they remain "active" until the six months runs
out.

To repeat, the I-D series was explicitly designed to not be
archival.  Let's not change that by an overly restrictive
take-down policy.

   john

p.s. FWIW, my understanding of the DCMA is consistent with Dave
Crocker's and his note on the subject.  Andrian, as I understand
it, there is no such thing as a pre-emptive counternotice.  If
the IETF, faced with a proper DCMA complaint, decided to not
take something down, the boilerplate might become part of a "his
problem, not ours" defense, but, as Dave suggests, that is the
sort of thing on which lawyers become wealthy.   In practical
terms, unless we decide we have a liking for lawsuits, we'd
probably be much better off responding to a proper DCMA notice
by taking the I-D out of public view and then letting anyone who
believes that the draft should have stayed up sue the entity who
created the notice.


--On Tuesday, September 04, 2012 07:27 -0400 Scott O Bradner
<sob@sobco.com> wrote:

> in addition
> since there is no admissions control on IDs I would think that
> the IESG would want  to reserve the option to remove an ID
> that contained clear libel or inappropriate  material (e.g., a
> pornographic story published as an ID as part of a DoS attack
> on the IETF) once the IESG had been given notice of such
> material
> 
> Scott
> 
> On Sep 3, 2012, at 9:29 PM, Sam Hartman
> <hartmans-ietf@mit.edu> wrote:
> 
>> I strongly urge  the IESG to be significantly more liberal in
>> the cases where an I-D will be removed from the archive.
>> 
>> I can think of a number of cases where I'd hope that the IESg
>> would be cooperative:





From peter@akayla.com  Wed Aug 29 20:31:14 2012
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 0902E11E8106; Wed, 29 Aug 2012 20:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVrD+dtmlRTE; Wed, 29 Aug 2012 20:31:13 -0700 (PDT)
Received: from p3plsmtpa06-03.prod.phx3.secureserver.net (p3plsmtpa06-03.prod.phx3.secureserver.net [173.201.192.104]) by ietfa.amsl.com (Postfix) with ESMTP id 4667811E8103; Wed, 29 Aug 2012 20:31:13 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-03.prod.phx3.secureserver.net with  id srXC1j0011huGat01rXCj1; Wed, 29 Aug 2012 20:31:12 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-ccamp-assoc-ext.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-ccamp-assoc-ext-04
Date: Wed, 29 Aug 2012 20:31:14 -0700
Message-ID: <005e01cd865f$e9035fe0$bb0a1fa0$@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: Ac2GXGvm+GKVy5bnQKSRdf5PVgZBeA==
Content-Language: en-us
X-Mailman-Approved-At: Tue, 04 Sep 2012 08:21:08 -0700
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: Thu, 30 Aug 2012 03:31:14 -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>

Document: draft-ietf-ccamp-assoc-ext-04
Reviewer: Peter Yee
Review Date: Aug-28-2012
IETF LC End Date: Aug-29-2012
IESG Telechat date: Not known

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

This document provides extensions to the scope of use of the RSVP
ASSOCIATION
object as well as providing an extended ASSOCIATION object capable of
handling
a longer Association ID.

Nits:

In the last example (Symmetric NAT), last sentence: "mechanisms" ->
"mechanism".

Section 2, 4th paragraph (the replacement text): "the the" -> "the".

Section 3.2.1, 2nd paragraph, 1st sentence: "are" -> "is".  Alternatively,
you 
could change "format" to "formats".

Section 3.2.2, 1st sentence: "apply" -> "applies".

Section 4.2, 1st sentence: "a" -> "an" in both occurrences.

Section 4.2, last paragraph, 2nd sentence: "a" -> "an".

Questions:

These are questions you may wish to answer but the draft is acceptable
without response:

1) In Section 4.2, 4th bullet, is there any implied relationship between the
Extended Association ID and the Association ID?  Or are they independent
values that simply must be matched?

2) Section 4.2, 5th bullet, you make a first and only mention of padding
bytes.
Are you using a specific method for generating these padding bytes or are
they random?  Given the matching requirement on ASSOCIATION objects,
it might be best to specify the padding generation so that if the object is
regenerated, it will still be matched by intermediary nodes.  I've presumed
that the padding bytes are for meeting the 4-byte multiple requirement,
but I don't know if implementations would ever be free to regenerate the
object for subsequent transmissions of that object.



From chris.hall@highwayman.com  Fri Aug 31 09:45:57 2012
Return-Path: <chris.hall@highwayman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E88521F865F for <ietf@ietfa.amsl.com>; Fri, 31 Aug 2012 09:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.983
X-Spam-Level: 
X-Spam-Status: No, score=-98.983 tagged_above=-999 required=5 tests=[AWL=1.329, BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thkNezvXwOPG for <ietf@ietfa.amsl.com>; Fri, 31 Aug 2012 09:45:56 -0700 (PDT)
Received: from smtp.demon.co.uk (mdfmta009.mxout.tch.inty.net [91.221.169.50]) by ietfa.amsl.com (Postfix) with ESMTP id E65F721F865E for <ietf@ietf.org>; Fri, 31 Aug 2012 09:45:55 -0700 (PDT)
Received: from mdfmta009.tch.inty.net (unknown [127.0.0.1]) by mdfmta009.tch.inty.net (Postfix) with ESMTP id 750BB128077; Fri, 31 Aug 2012 17:45:54 +0100 (BST)
Received: from mdfmta009.tch.inty.net (unknown [127.0.0.1])	by mdfmta009.tch.inty.net (Postfix) with ESMTP id 2E31F128076; Fri, 31 Aug 2012 17:45:54 +0100 (BST)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta009.tch.inty.net (Postfix) with ESMTP; Fri, 31 Aug 2012 17:45:51 +0100 (BST)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1T7ULv-0003iY-9J; Fri, 31 Aug 2012 16:45:51 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <ietf@ietf.org>
References: <13B8E8D9-1AB1-4C22-9671-27714B8F86AD@juniper.net> <378A930E-031B-457E-8447-58AF9B98ECC6@juniper.net> <066801cd874d$f77b31d0$e6719570$@highwayman.com> <3FFE41C9-2A35-4A16-B529-8E01F5A8E270@ericsson.com> <4AB772AC-6023-4D44-AEAE-9FE71876782B@juniper.net>
In-Reply-To: <4AB772AC-6023-4D44-AEAE-9FE71876782B@juniper.net>
Subject: RE: [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
Date: Fri, 31 Aug 2012 17:45:46 +0100
Organization: Highwayman
Message-ID: <06f701cd8798$146f2720$3d4d7560$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQKOlQGOZhJFWctCjzrkYJ+6D5Co3gF+FrfJAhId3mQDcub4/wIx7k4HlahcrgA=
Content-Language: en-gb
X-MDF-HostID: 22
X-Mailman-Approved-At: Tue, 04 Sep 2012 08:21:08 -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, 31 Aug 2012 16:45:57 -0000

John G. Scudder wrote (on Fri 31-Aug-2012 at 17:24 +0100):
> By the way, since this is now in *IETF* last call, if you want your
> comments to be considered you should send them to ietf@ietf.org.
> Feel free to cc IDR and GROW if you like.

OK.  Message previously posted to idr@ietf.org follows:
----------------------------------------------------------------------
--------

OK.  Clearly I am late to the party, but here goes...

In section 2 the draft talks of three "sub-classes" of error:

  1) "...UPDATE message is considered invalid...due to an error
     within a path attribute...[which]...is syntactically valid..."

  2) "...where a valid NLRI attribute can be extracted..." 

  3) "...where an attribute is not able to be parsed..."

and of the "key requirement to maximize the number of cases in which
it is possible to extract NLRI from a BGP message".

The draft is not specific on what is "syntactically valid", or what is
a "completely parsed" a set of attributes.  However, section 2.1.2
enumerates some "Semantic BGP Errors", which imply a desire to accept
a wide range of very badly broken sets of attributes.

In that context, the proposal to place any MP_REACH_NLRI and/or
MP_UNREACH_NLRI at the start of the attributes is insufficient.

If it is possible to parse both MP_REACH_NLRI and MP_UNREACH_NLRI at
the start of the attributes, and at least the first attribute which
follows is completely valid, then it seems highly likely that all NLRI
can be extracted, no matter how badly broken the rest of the attribute
set is.

But what does it mean if that is not the case ?  It is not known
whether the sender will send attributes in the required order.  It is
not known what combination of 'Withdrawn Routes', 'Network Layer
Reachability Information', MP_REACH_NLRI and MP_UNREACH_NLRI may have
been sent.  So, does the fact that MP attributes are not visible mean
they are not there, or that they are obscured by some other broken
attribute ?

The requirements appear to say that almost any random sequence of
octets should be an acceptable set of attributes, provided that the
NLRI can be identified.  But relaxing the rules on what is an
individually valid attribute means that any (apparent) absence of MP
attribute(s) is more than a little ambiguous.  Accepting (say) an
ATOMIC_AGGREGATOR attribute with a length of (say) 421 makes me feel
more than a little queasy.  It does not contain any NLRI, but I would
not care to guess what earlier misbegotten attribute may have lead us
to this odd looking attribute, or what nonsense may follow, or what
the sender really meant to say, or whether an MP attribute is lost in
the noise.

Reliable identification of the NLRI might be achieved:

  1) as suggested in the draft, by sending MP_UNREACH_NLRI
     and MP_REACH_NLRI as the first attributes.

     But I would add the ORIGIN to that, so that the receiver
     sees:

       * no attributes at all -- hence no MP NLRI,

       * or, just an exactly correct ORIGIN -- signalling no
         MP NLRI,

       * or, MP_UNREACH_NLRI all on its own,

       * or, MP_REACH_NLRI followed by an exactly correct
         3 octets of ORIGIN attribute (as a sort of
         terminator)

       * or, all three.

     *PLUS*

       * a Capability that promises to do so, so that there
         is no ambiguity.

  2) or, more directly, by:

       * adding an UPDATEv2 message type

       * and Capability,

     to completely separate NLRI from Attributes.

Now, it is possible that no known BGP implementation out there sends
more than one form of NLRI in an UPDATE message.  So, the presence of
any one implies the absence of all others, and the presence of any
attribute other than MP_UNREACH_NLRI implies the presence of
MP_REACH_NLRI if there are no other NLRI.  If that is the assumption,
then it should be stated.

However, if the intent is to keep going despite (inter alia) problems
caused by malfunctioning software, then completely separating NLRI
from attributes seems to me the cleanest approach.

If the intent is for a "smart new" BGP implementation to be able to
avoid bringing down sessions when talking to a current BGP
implementation, then some more detailed analysis is required.  For
example, in 2.1.2 the draft defines this as a semantic error: 

    o Zero or invalid length errors in path attributes excluding those
      containing NLRI, or where the length of all path attributes
      contained within the UPDATE does not correspond to the total
path
      attributes length.  In this case, the NLRI can be correctly
      extracted, and hence acted upon.

but in the face of such broken-ness, how, exactly, can NLRI be
correctly extracted ?  (Without some guarantee of how NLRI are sent --
a guarantee which may be relied upon when the sender's attribute
handling is busted ?)

But, if it is expected that both ends of a BGP session must be "smart
new" implementations to get (full) improved error handling, why not
make a clean and complete separation of NLRI from attributes ?  One
can then stop struggling quite so hard to extract sense from nonsense
attributes.

Chris


From chris.hall@highwayman.com  Fri Aug 31 09:48:06 2012
Return-Path: <chris.hall@highwayman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3829021F8533 for <ietf@ietfa.amsl.com>; Fri, 31 Aug 2012 09:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.173
X-Spam-Level: 
X-Spam-Status: No, score=-99.173 tagged_above=-999 required=5 tests=[AWL=1.139, BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GxKaOUPt8YUV for <ietf@ietfa.amsl.com>; Fri, 31 Aug 2012 09:48:05 -0700 (PDT)
Received: from smtp.demon.co.uk (mdfmta009.mxout.tch.inty.net [91.221.169.50]) by ietfa.amsl.com (Postfix) with ESMTP id 1BBF221F852D for <ietf@ietf.org>; Fri, 31 Aug 2012 09:48:05 -0700 (PDT)
Received: from mdfmta009.tch.inty.net (unknown [127.0.0.1]) by mdfmta009.tch.inty.net (Postfix) with ESMTP id 795C0128075 for <ietf@ietf.org>; Fri, 31 Aug 2012 17:48:04 +0100 (BST)
Received: from mdfmta009.tch.inty.net (unknown [127.0.0.1])	by mdfmta009.tch.inty.net (Postfix) with ESMTP id 2C0C4128074	for <ietf@ietf.org>; Fri, 31 Aug 2012 17:48:04 +0100 (BST)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta009.tch.inty.net (Postfix) with ESMTP	for <ietf@ietf.org>; Fri, 31 Aug 2012 17:48:04 +0100 (BST)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1T7UO3-0003ib-Ij	for ietf@ietf.org; Fri, 31 Aug 2012 16:48:03 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <ietf@ietf.org>
References: <13B8E8D9-1AB1-4C22-9671-27714B8F86AD@juniper.net> <378A930E-031B-457E-8447-58AF9B98ECC6@juniper.net> <066801cd874d$f77b31d0$e6719570$@highwayman.com> <3FFE41C9-2A35-4A16-B529-8E01F5A8E270@ericsson.com> <4AB772AC-6023-4D44-AEAE-9FE71876782B@juniper.net> 
In-Reply-To: 
Subject: FW: [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
Date: Fri, 31 Aug 2012 17:47:58 +0100
Organization: Highwayman
Message-ID: <06f801cd8798$63449470$29cdbd50$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQKOlQGOZhJFWctCjzrkYJ+6D5Co3gF+FrfJAhId3mQDcub4/wIx7k4HlahcrgCAAAFCgA==
Content-Language: en-gb
X-MDF-HostID: 22
X-Mailman-Approved-At: Tue, 04 Sep 2012 08:21:08 -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, 31 Aug 2012 16:48:06 -0000

John G. Scudder wrote (on Fri 31-Aug-2012 at 17:24 +0100):
> By the way, since this is now in *IETF* last call, if you want your
> comments to be considered you should send them to ietf@ietf.org.
> Feel free to cc IDR and GROW if you like.

OK.  Message previously posted to idr@ietf.org follows:
----------------------------------------------------------------------
--------

In trying to classify Errors with BGP-4 UPDATE Messages I think it
would be useful to distinguish between the form of an error and the
severity of that error and how BGP should respond.

It seems to me that there are four severities/responses:

  1) "Critical Error" -> drop/restart session or AFI/SAFI

     So the overall response then depends on how gracefully the
     session drop and/or restart can be handled.

  2) "Serious Error" -> do something with NLRI, short of
     dropping the session.

     The "treat-as-withdraw" mechanism is mentioned.

     The requirements obviously do not wish to specify mechanisms.

     But I think that the requirements should address what outcome
     is expected if errors in an individual UPDATE message are to
     be limited to that message.  I think what that means is:

       * it must be possible to identify all NLRI that the message
         could be carrying.

       * whatever is done with those NLRI must reflect the fact
         that the recipient has an incomplete, possibly empty,
         set of attributes for those NLRI.

  3) "Ignorable Error" -> process the UPDATE message as if the
     ignored attributes had never existed.

     Some errors in some trivial attributes may be ignorable.
     The requirements could cover the criteria for being deemed
     trivial.

     Some errors in Optional Transitive may be dealt with by
     ignoring the attribute altogether.  The requirements
     mention this, but do not specify criteria for being
     ignorable.

  4) "Recoverable Error" -> process the UPDATE message which has
     had errors "patched up".

     The draft-ieft-idr-error-handling, for example, suggests
     that invalid Attribute Flags may simply be overwritten
     by the expected value.

I would then divide the forms of error into (1) "framing" and (2)
"content" (or "semantic").

A BGP UPDATE message has three levels of framing:

  * Level 1 -- the 16 octet "Marker" + Message Length
                                     + Withdrawn Routes Length
                                     + Total Path Attributes Length

    If the Message Length is broken, it is extremely likely that the
    "Marker" on the next message will be invalid.

  * Level 2(a) -- the Withdrawn Routes

    Each prefix must have a valid prefix length, and the last
    must run exactly to the end of this part of the message.

  * Level 2(b) -- the Attributes

    Each attribute must be correctly framed, and at the end of the
    attributes the last one must run to exactly the end of the
    attribute part of the message.

  * Level 2(c) -- the Network Layer Reachability Information.

    Same as 2(a).

  * Level 3 -- various Attributes

    Some attributes have internal framing.

So far, so obvious.  To judge if an individual attribute is properly
framed, we need to consider the red-tape:

  * the Flags octet has a limited set of valid values, depending
    on the Type.

  * the Type may be more or less anything, but repeats are not
    valid.
 
  * the Length is constrained for some Types

There is some redundancy here, more for known types than unknown ones,
which helps.  The Total Path Attributes Length is, effectively, a
checksum for all the Lengths of all the Attributes.  It would be
possible to specify that a set of attributes should be deemed
correctly framed solely on the basis of passing that test.  However,
my feeling is that all the available redundancy (such as it is) should
be used to minimise the possibility of accepting a broken attributes
-- *particularly* where an error is going to be treated as Ignorable.

Once attributes are correctly framed, then one can consider their
content.  Wherever the line between framing and content is drawn, I
think it helps to be clear about the distinction between them --
"framing" errors affect the attribute and the attributes around it,
"content" errors affect only the attribute.

The framing of an Optional Transitive is a special case.  If the
parser recognises an Optional Transitive, but its Length is not valid,
what should the receiver do ?  If the sender did not understand the
Attribute, then the broken Length is a "content" issue.  If the sender
did understand it, then the broken Length is a "framing" issue.  (It
is a serious disappointment to me that the Partial bit does not help
here.  But even if it did, what if the sender made a mess of
setting/clearing it !?)

In section 2.1.2 the draft specifies a number of "Semantic BGP
Errors", which includes many things which I would class as "framing"
errors.

This is all pretty low level stuff.  I can hear an argument that the
requirements document is not the place for this level of detail.
However, without a more precise understanding of how broken attributes
may be parsed, requirements for how to deal with them are hard to
specify and to interpret.

If NLRI were explicitly separate from the attributes, then if a set of
attributes fails a strict "framing" check, then "treat-as-withdraw"
(or equivalent) could be applied, reliably.  This seems to me to be as
safe as possible, short of dropping the session (which has its own
safety issues).

With NLRI mixed up in the attributes, either one plays safe and treats
all attribute errors as Critical, or a much more detailed analysis of
attribute parsing is required.  What is the cost of missing some NLRI
which were sent, but were obscured by some other broken attribute ?
What is the risk ?  What degree of broken-ness of an attribute can be
deemed not to invalidate the parsing of the attributes before and/or
after it ?  Is that different for different attributes ?

In order to contemplate classifying some attribute errors as
"Ignorable" or "Recoverable", a more detailed analysis of attribute
parsing is also required.  An ATOMIC_AGGREGATE attribute is arguably
trivial and Ignorable.  But is an ATOMIC_AGGREGATE attribute with a
length of 421 (say) likely to be a momentary lapse of concentration at
the sender end, or more likely to be a symptom of a badly broken set
of attributes ? 

Chris


From chris.hall@highwayman.com  Fri Aug 31 10:06:39 2012
Return-Path: <chris.hall@highwayman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA54421F8661; Fri, 31 Aug 2012 10:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.315
X-Spam-Level: 
X-Spam-Status: No, score=-99.315 tagged_above=-999 required=5 tests=[AWL=0.997, BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4UPj1shF9DtD; Fri, 31 Aug 2012 10:06:39 -0700 (PDT)
Received: from smtp.demon.co.uk (mdfmta005.mxout.tch.inty.net [91.221.169.46]) by ietfa.amsl.com (Postfix) with ESMTP id 0280821F865E; Fri, 31 Aug 2012 10:06:38 -0700 (PDT)
Received: from mdfmta005.tch.inty.net (unknown [127.0.0.1]) by mdfmta005.tch.inty.net (Postfix) with ESMTP id 7EAB018C29D; Fri, 31 Aug 2012 18:06:37 +0100 (BST)
Received: from mdfmta005.tch.inty.net (unknown [127.0.0.1])	by mdfmta005.tch.inty.net (Postfix) with ESMTP id F138518C13A; Fri, 31 Aug 2012 18:06:36 +0100 (BST)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta005.tch.inty.net (Postfix) with ESMTP; Fri, 31 Aug 2012 18:06:36 +0100 (BST)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1T7Ug0-0003ie-4J; Fri, 31 Aug 2012 17:06:36 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <ietf@ietf.org>
References: <13B8E8D9-1AB1-4C22-9671-27714B8F86AD@juniper.net> <378A930E-031B-457E-8447-58AF9B98ECC6@juniper.net> <066801cd874d$f77b31d0$e6719570$@highwayman.com> <3FFE41C9-2A35-4A16-B529-8E01F5A8E270@ericsson.com>
In-Reply-To: <3FFE41C9-2A35-4A16-B529-8E01F5A8E270@ericsson.com>
Subject: RE: [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
Date: Fri, 31 Aug 2012 18:06:30 +0100
Organization: Highwayman
Message-ID: <06ff01cd879a$fa65eeb0$ef31cc10$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQKOlQGOZhJFWctCjzrkYJ+6D5Co3gF+FrfJAhId3mQDcub4/5W57fQg
Content-Language: en-gb
X-MDF-HostID: 18
X-Mailman-Approved-At: Tue, 04 Sep 2012 08:21:08 -0700
Cc: 'Jakob Heitz' <jakob.heitz@ericsson.com>, idr@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Aug 2012 17:06:39 -0000

Jakob Heitz wrote (on Fri 31-Aug-2012 at 17:20 +0100):
> On Aug 31, 2012, at 12:55 AM, "Chris Hall" wrote:

> >  2) or, more directly, by:
> >
> >       * adding an UPDATEv2 message type
> >
> >       * and Capability,
> >
> >     to completely separate NLRI from Attributes.

> That does not "completely separate". You can separate with a FIN/SYN
> or put them into different packets: use UDP instead of TCP. With
> TCP, you are always at the mercy of length fields.

Perhaps I got a little over-excited, and overstated the degree of
separation.

But by moving the NLRI up a level, out of the mish-mash of Attributes
(back to the top level of the UPDATE where they were originally), then
at least extracting the NLRI from the message is not tangled up with
trying to decide how to make sense of a broken set of attributes.
Particularly as the whole point of the exercise is to minimise the
impact of broken sets of attributes.

> I mean, if you are going to require both ends of a connection to
> upgrade...

The recommendation is that MP_REACH_NLRI and MP_UNREACH_NLRI are moved
to the front of the attributes, so that they are less vulnerable to
problems in other attributes.  That is an upgrade.  But, as I said, I
don't think that is sufficient.  The receiver needs to know that the
sender is going to do that -- because otherwise the absence of
MP_REACH_NLRI and MP_UNREACH_NLRI is ambiguous.  Which requires a
capability.  That is also an upgrade.  To be fully effective,
improvements to the error handling will involve an upgrade.  In which
case, I suggest, one could go back to the future and disentangle NLRI
from Attributes.

Chris


From jakob.heitz@ericsson.com  Fri Aug 31 10:38:34 2012
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C09721F84B9; Fri, 31 Aug 2012 10:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.564
X-Spam-Level: 
X-Spam-Status: No, score=-6.564 tagged_above=-999 required=5 tests=[AWL=-0.192, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3RU8VdwUBkHE; Fri, 31 Aug 2012 10:38:33 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3F321F8495; Fri, 31 Aug 2012 10:38:33 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q7VHepEd005425; Fri, 31 Aug 2012 12:40:53 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.204]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Fri, 31 Aug 2012 13:38:24 -0400
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Chris Hall <chris.hall@highwayman.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 31 Aug 2012 13:38:23 -0400
Subject: RE: [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
Thread-Topic: [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
Thread-Index: AQKOlQGOZhJFWctCjzrkYJ+6D5Co3gF+FrfJAhId3mQDcub4/5W57fQggAAM1CA=
Message-ID: <7309FCBCAE981B43ABBE69B31C8D21394220C735C2@EUSAACMS0701.eamcs.ericsson.se>
References: <13B8E8D9-1AB1-4C22-9671-27714B8F86AD@juniper.net> <378A930E-031B-457E-8447-58AF9B98ECC6@juniper.net> <066801cd874d$f77b31d0$e6719570$@highwayman.com> <3FFE41C9-2A35-4A16-B529-8E01F5A8E270@ericsson.com> <06ff01cd879a$fa65eeb0$ef31cc10$@highwayman.com>
In-Reply-To: <06ff01cd879a$fa65eeb0$ef31cc10$@highwayman.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-Mailman-Approved-At: Tue, 04 Sep 2012 08:21:08 -0700
Cc: "idr@ietf.org" <idr@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Aug 2012 17:38:34 -0000

UPDATEv2 is also inadequate.

Either, you have a fix that does not require the other end to upgrade
or you fix it properly.

--
Jakob Heitz.

> -----Original Message-----
> From: Chris Hall [mailto:chris.hall@highwayman.com]
> Sent: Friday, August 31, 2012 10:07 AM
> To: ietf@ietf.org
> Cc: idr@ietf.org; Jakob Heitz
> Subject: RE: [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
>=20
> Jakob Heitz wrote (on Fri 31-Aug-2012 at 17:20 +0100):
> > On Aug 31, 2012, at 12:55 AM, "Chris Hall" wrote:
>=20
> > >  2) or, more directly, by:
> > >
> > >       * adding an UPDATEv2 message type
> > >
> > >       * and Capability,
> > >
> > >     to completely separate NLRI from Attributes.
>=20
> > That does not "completely separate". You can separate with a FIN/SYN
> > or put them into different packets: use UDP instead of TCP. With
> > TCP, you are always at the mercy of length fields.
>=20
> Perhaps I got a little over-excited, and overstated the degree of
> separation.
>=20
> But by moving the NLRI up a level, out of the mish-mash of Attributes
> (back to the top level of the UPDATE where they were originally), then
> at least extracting the NLRI from the message is not tangled up with
> trying to decide how to make sense of a broken set of attributes.
> Particularly as the whole point of the exercise is to minimise the
> impact of broken sets of attributes.
>=20
> > I mean, if you are going to require both ends of a connection to
> > upgrade...
>=20
> The recommendation is that MP_REACH_NLRI and MP_UNREACH_NLRI are moved
> to the front of the attributes, so that they are less vulnerable to
> problems in other attributes.  That is an upgrade.  But, as I said, I
> don't think that is sufficient.  The receiver needs to know that the
> sender is going to do that -- because otherwise the absence of
> MP_REACH_NLRI and MP_UNREACH_NLRI is ambiguous.  Which requires a
> capability.  That is also an upgrade.  To be fully effective,
> improvements to the error handling will involve an upgrade.  In which
> case, I suggest, one could go back to the future and disentangle NLRI
> from Attributes.
>=20
> Chris


From chris.hall@highwayman.com  Fri Aug 31 11:07:40 2012
Return-Path: <chris.hall@highwayman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4FC421F8501; Fri, 31 Aug 2012 11:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.426
X-Spam-Level: 
X-Spam-Status: No, score=-99.426 tagged_above=-999 required=5 tests=[AWL=0.886, BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zYT4lOXR4ap0; Fri, 31 Aug 2012 11:07:40 -0700 (PDT)
Received: from smtp.demon.co.uk (mdfmta004.mxout.tch.inty.net [91.221.169.45]) by ietfa.amsl.com (Postfix) with ESMTP id E1CBE21F84F3; Fri, 31 Aug 2012 11:07:39 -0700 (PDT)
Received: from mdfmta004.tch.inty.net (unknown [127.0.0.1]) by mdfmta004.tch.inty.net (Postfix) with ESMTP id A7ABEAC4075; Fri, 31 Aug 2012 19:07:37 +0100 (BST)
Received: from mdfmta004.tch.inty.net (unknown [127.0.0.1])	by mdfmta004.tch.inty.net (Postfix) with ESMTP id 65EF1AC406C; Fri, 31 Aug 2012 19:07:37 +0100 (BST)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta004.tch.inty.net (Postfix) with ESMTP; Fri, 31 Aug 2012 19:07:37 +0100 (BST)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1T7Vd2-0003ij-8S; Fri, 31 Aug 2012 18:07:36 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <ietf@ietf.org>
References: <13B8E8D9-1AB1-4C22-9671-27714B8F86AD@juniper.net> <378A930E-031B-457E-8447-58AF9B98ECC6@juniper.net> <066801cd874d$f77b31d0$e6719570$@highwayman.com> <3FFE41C9-2A35-4A16-B529-8E01F5A8E270@ericsson.com> <06ff01cd879a$fa65eeb0$ef31cc10$@highwayman.com> <7309FCBCAE981B43ABBE69B31C8D21394220C735C2@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <7309FCBCAE981B43ABBE69B31C8D21394220C735C2@EUSAACMS0701.eamcs.ericsson.se>
Subject: RE: [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
Date: Fri, 31 Aug 2012 19:07:30 +0100
Organization: Highwayman
Message-ID: <070601cd87a3$80008870$80019950$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQKOlQGOZhJFWctCjzrkYJ+6D5Co3gF+FrfJAhId3mQDcub4/wJu5LNKAdcLv7OVl9LBMA==
Content-Language: en-gb
X-MDF-HostID: 17
X-Mailman-Approved-At: Tue, 04 Sep 2012 08:21:08 -0700
Cc: 'Jakob Heitz' <jakob.heitz@ericsson.com>, idr@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Aug 2012 18:07:41 -0000

Jakob Heitz wrote (on Fri 31-Aug-2012 at 18:38 +0100):
> UPDATEv2 is also inadequate.

If we are agreed that the current proposals are inadequate, then we
are agreed on something.

> Either, you have a fix that does not require the other end to
> upgrade or you fix it properly.

Without an upgrade to improve the ability to extract the NLRI when
Attributes are broken, the fix is incomplete.

I look forward to a proper fix.

Chris

> --
> Jakob Heitz.
> 
> > -----Original Message-----
> > From: Chris Hall [mailto:chris.hall@highwayman.com]
> > Sent: Friday, August 31, 2012 10:07 AM
> > To: ietf@ietf.org
> > Cc: idr@ietf.org; Jakob Heitz
> > Subject: RE: [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-
> handling-05
> >
> > Jakob Heitz wrote (on Fri 31-Aug-2012 at 17:20 +0100):
> > > On Aug 31, 2012, at 12:55 AM, "Chris Hall" wrote:
> >
> > > >  2) or, more directly, by:
> > > >
> > > >       * adding an UPDATEv2 message type
> > > >
> > > >       * and Capability,
> > > >
> > > >     to completely separate NLRI from Attributes.
> >
> > > That does not "completely separate". You can separate with a
> FIN/SYN
> > > or put them into different packets: use UDP instead of TCP. With
> > > TCP, you are always at the mercy of length fields.
> >
> > Perhaps I got a little over-excited, and overstated the degree of
> > separation.
> >
> > But by moving the NLRI up a level, out of the mish-mash of
> Attributes
> > (back to the top level of the UPDATE where they were originally),
> then
> > at least extracting the NLRI from the message is not tangled up
> with
> > trying to decide how to make sense of a broken set of attributes.
> > Particularly as the whole point of the exercise is to minimise the
> > impact of broken sets of attributes.
> >
> > > I mean, if you are going to require both ends of a connection to
> > > upgrade...
> >
> > The recommendation is that MP_REACH_NLRI and MP_UNREACH_NLRI are
> moved
> > to the front of the attributes, so that they are less vulnerable
> to
> > problems in other attributes.  That is an upgrade.  But, as I
> said, I
> > don't think that is sufficient.  The receiver needs to know that
> the
> > sender is going to do that -- because otherwise the absence of
> > MP_REACH_NLRI and MP_UNREACH_NLRI is ambiguous.  Which requires a
> > capability.  That is also an upgrade.  To be fully effective,
> > improvements to the error handling will involve an upgrade.  In
> which
> > case, I suggest, one could go back to the future and disentangle
> NLRI
> > from Attributes.
> >
> > Chris


From chris.hall@highwayman.com  Sun Sep  2 03:48:29 2012
Return-Path: <chris.hall@highwayman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF7921F899A; Sun,  2 Sep 2012 03:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.215
X-Spam-Level: 
X-Spam-Status: No, score=-98.215 tagged_above=-999 required=5 tests=[AWL=-0.503, BAYES_50=0.001, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7flxRHF+xSLK; Sun,  2 Sep 2012 03:48:28 -0700 (PDT)
Received: from smtp.demon.co.uk (mdfmta010.mxout.tch.inty.net [91.221.169.51]) by ietfa.amsl.com (Postfix) with ESMTP id 023A321F8995; Sun,  2 Sep 2012 03:48:27 -0700 (PDT)
Received: from mdfmta010.tch.inty.net (unknown [127.0.0.1]) by mdfmta010.tch.inty.net (Postfix) with ESMTP id 32211400268; Sun,  2 Sep 2012 11:48:26 +0100 (BST)
Received: from mdfmta010.tch.inty.net (unknown [127.0.0.1])	by mdfmta010.tch.inty.net (Postfix) with ESMTP id CDC04400250; Sun,  2 Sep 2012 11:48:25 +0100 (BST)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta010.tch.inty.net (Postfix) with ESMTP; Sun,  2 Sep 2012 11:48:25 +0100 (BST)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1T87j6-0003kI-MO; Sun, 02 Sep 2012 10:48:24 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <ietf@ietf.org>
References: <066901cd874e$fa0605f0$ee1211d0$@highwayman.com> <CB85647B-4BC9-483C-BBA3-73B6DAA8B1F4@rob.sh>
In-Reply-To: <CB85647B-4BC9-483C-BBA3-73B6DAA8B1F4@rob.sh>
Subject: RE: [GROW] [Idr] draft-ietf-grow-ops-reqs-for-bgp-error-handling-05
Date: Sun, 2 Sep 2012 11:48:19 +0100
Organization: Highwayman
Message-ID: <07d101cd88f8$7a2c8f60$6e85ae20$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQJn9OxjujSjCTsYygfO8NLLdB3mFwInuPc+li4fbGA=
Content-Language: en-gb
X-MDF-HostID: 19
X-Mailman-Approved-At: Tue, 04 Sep 2012 08:21:08 -0700
Cc: 'idr wg' <idr@ietf.org>, grow@ietf.org, 'Rob Shakir' <rjs@rob.sh>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Sep 2012 10:48:29 -0000

Rob Shakir wrote (on Fri 31-Aug-2012 at 19:00 +0100):
...
> Thanks for this detailed analysis. It is akin to something that
> Alton Lo and I worked through whilst defining the critical and
> semantic error types (and suggested inclusions).
> 
> If you'll forgive me for responding to some particular points, I
> feel this might aid the discussion and positioning. I have added
> comments in-line marked [rjs].
> 
> On 31 Aug 2012, at 09:02, Chris Hall wrote:
> 
> > This is all pretty low level stuff.  I can hear an argument that
> > the requirements document is not the place for this level of
> > detail.  However, without a more precise understanding of how
> > broken attributes may be parsed, requirements for how to deal
> > with them are hard to specify and to interpret.

> [rjs]: What this draft intends to do is provide expectations,
> requirements and context for error handling in BGP-4, based on
> current deployments (and operator's experience). It also puts
> forwards requirements for how each type of error is reacted to in a
> broad sense. Essentially, where it came from is defining why
> amending the error handling behaviour is required, and providing a
> framework against which we can hang the different developments that
> are being discussed in IDR, such that they meet the operational
> challenges that come from amending this behaviour and form a
> complete set of solutions to meet the problem space.
> 
> [rjs]: I think the error handling solutions draft (draft-ietf-idr-
> error-handling) should take the work that we have done within IDR
> and GROW in this draft and build the next level of detail, which I
> think that you've made a great start to. I would like to try and
> keep the requirements draft such that it can be referred to by both
> existing attributes, and future ones.

I agree that the Requirements want to be at as high a level as
possible.  Requirements based on experience are good, too.

The issue I have is that the draft seems to go into too much detail in
some areas, and not enough in others.

Looking at Sections 2.1.1: at a high level, a Critical error is one
for which tearing down the session is unavoidable.  That is deemed to
be when the receiver cannot be sure that they have extracted from a
broken UPDATE all the NLRI to which it refers (yes ?).  If you don't
have the NLRI, you are stuck.  If you have the NLRI, it may be
possible to contain the error so that it affects only those NLRI (for
example, by "treat-as-withdraw").  If you have the NLRI and enough
(however defined) valid (however defined) attributes, it may be
possible to update the NLRI, perhaps partially or temporarily.

[Actually, I'm not sure that is complete.  As observed elsewhere in
the draft, a given BGP session may be carrying a number of AFI/SAFI
and possibly a number of separate VPN.  So for some purposes perhaps
it's not necessary to be able to identify all the NLRI to which the
UPDATE applies, only the AFI/SAFI or VPN to which the UPDATE applies.
If so, then perhaps there is a Requirement for Critical errors to be
handled on a per AFI/SAFI and per VPN basis -- that is, a
"semi-Critical" error which tears down a self-contained part of the
session.  I'm not sure whether the definition of a Critical BGP Error
allows for this or not, depending on how one interprets "Errors
Parsing the NLRI".] 

Staying with the high level requirements, if an error is to not be
Critical, it appears one needs:

  (a) to be able to extract the NLRI (or AFI/SAFI etc ?) with 
      some degree of certainty.

  (b) to have ways of dealing with that NLRI in ways that do not
      affect other NLRI learned in the session unnecessarily, and
      which do not cause unacceptable side effects.

  (c) to be able to extract some attributes with some degree of
      certainty, and be able to judge when proceeding to process
      an UPDATE with an incomplete or damaged set of attributes
      will yield sufficiently valid routes.

  (d) to have mechanisms to signal the problem so that the root
      cause(s) can be addressed and possibly to trigger other
      (e.g. operational) responses.

for which there could usefully be some discussion of "degree of
certainty", "affect...unnecessarily", "unacceptable side effects",
"sufficiently valid" and so on -- from a routing information and an
operational perspective.  For example, if "treat as withdraw" is
performed, but the receiver has not (for whatever reason) been able to
extract all the NLRI sent, the receiver is left with some stale
(possibly invalid) routes; that may be acceptable because the
alternative (tearing down the session) is worse, or because other
(operational/protocol) mechanisms will kick in to clean up... and so
on.

The draft appears to say that anything which is not a Critical Error
is a Semantic one -- or vice versa.  This appears to assume that in
the parsing of attributes, an error in one attribute does not affect
any other attribute -- in particular, that an error in a not-NLRI
attribute does not affect the ability to reliably (enough ?) extract
the NLRI.  To support that, I think the document would need to go down
into the nuts and bolts of the parsing mechanics.  (Section 2.1.2
starts with "Where a BGP message is correctly formed"... I assume that
means that the Message, Withdrawn Routes and Total Path Attribute
Lengths are consistent, and the Marker is 'all-ones' ?) 

This is what I mean by both too much and too little detail.  The high
level requirement is to be able to extract NLRI (etc); whatever the
issues in doing so are, they are perhaps at too great a level of
detail for this document.  On the other hand, the discussion of
Semantic Errors does not go into sufficient detail to support the
requirements which flow from (the apparently assumed) ability to parse
attributes separately.

Where an UPDATE does not contain a Critical error, the receiver has
(by definition) the NLRI (which it believes it has received correctly)
and perhaps some Attributes.  What the receiver then does may depend
on its confidence in what it has managed to extract from the broken
message.  All of that can be left as an exercise for implementers.
The requirements should focus on the implications from a
routing/operational perspective and offer some criteria for acceptable
behaviour.  The current standard requires (for safety) that any error
invalidates everything learned in the Session.  One step from there is
that some errors only invalidate all the NLRI referred to in the
erroneous UPDATE message -- which (for safety) discards all attributes
in the message.  A further step is that some errors do not invalidate
the NLRI in the erroneous UPDATE message, but processing proceeds with
some subset of the attributes.  For my money, that further step is a
giant step, and deserves to be covered at the Requirements level.
[Another step is that some errors invalidate everything learned in the
Session about a given AFI/SAFI or (possibly) VPN.]

...
> [rjs]: Please note that the requirements draft does not present
> distinctions such as recoverable and ignorable. We went around this
> loop previously. I think that in some cases, some specific errors
> may be handled by 'patching' or 'ignoring' specific errors. But
> generically, these are exceptions - the requirements try and define
> broader categories, if a particular attribute needs something else
> (e.g., AS4_PATH may have information it can recover from other
> attributes) then this can be handled in error handling solution
> considerations of these attributes or as it is defined going
> forward.

I'm sorry to have missed the previous discussion.  Suffice it to say
that, as above, I think that Ignoring or Recovering (patching up) some
errors is materially different to examining each attribute carefully
and dumping the whole lot on the floor if any one is invalid.

But this touches on the incompleteness (IMHO) of the classification.
For me, one can consider a semantic error in an attribute only after
establishing that it is (in my terms) correctly "framed".  Once one
has parsed a set of attributes, and concluded there is no reason to
believe that some invalid attribute length has thrown the parser off
track, then one can get into what to do with the contents of each
attribute.

I think the difficulty is (repeating myself, sorry) exactly
illustrated by the question of what to do with an ATOMIC_AGGREGATE
attribute which is apparently 421 octets long.

At a requirements level, you may not wish to get into the detail of
this.  But as it stands, the draft classifies pretty much every way in
which an attribute can be broken as a Semantic error.  This seems to
me to miss the important fact that an attribute is only an attribute
once the Path Attributes part of the message has been parsed
satisfactorily -- up to that point, the entire Path Attributes are a
pretty random looking collection of octets.

...
> [rjs]: The requirement the document makes is explicitly that not all
> errors are defined as critical (if they were, the requirement
> specified by section 3 would not be met, and we would stick with the
> behaviour we have right now). The reason for a distinction between
> critical and semantic is that there are certain errors that mean
> that cannot be localised to certain NLRI.

OK.  Sure.  We have Critical and Not-Critical errors.  Not-Critical
errors are those for which we can extract the NLRI.

A key reason for not being able to extract the NLRI is encountering an
error when parsing the Attributes.  Some errors may suggest that the
sender has gone barking mad, and it is not possible to say whether
there are NLRI there to extract or not.  Other errors may be less
alarming.  The given definition of Semantic errors does not
distinguish.

As above, the requirements could step back from the parsing issue, and
specify only the need to reliably extract NLRI.  And, if it is a
requirement to proceed to process (as opposed to just invalidate) NLRI
from a broken message, the requirements should specify the need to
reliably extract a good enough subset of attributes to proceed with.

At the very least, I suggest that Critical (severity of error) and
Semantic (form of error) are orthogonal notions.

> [rjs]: I hope you do not see these comments as dismissive of what
> you have put together - I think that this is where operational and
> implementation views diverge. My view is that I need to understand
> what the impact to a service, the device and the network is during
> these error conditions (and balance the risk of incorrectness
> against the correctness of the protocol). From an implementation
> perspective, clearly, one needs to understand exactly which
> circumstances one can extract the NLRI, and the particulars of how
> this is achieved. I would encourage discussion that falls into the
> latter category such that we define the solutions draft to have the
> relevant guidance where required. Comments on the former should
> absolutely live in the requirements draft

Sure.  I am trying to make the case that where the Requirements touch
on the implementation issues, it is going too deep.  And, in lumping
all kinds of errors together and deeming them to be Semantic errors,
the issues there are obscured rather than brought into focus.

If the Requirements were written without reference to the internal
organisation of the BGP UPDATE message, that would be fine.

As you say, what really matters is the operational impact of changes
to the protocol which may include, inter alia:

  1. some routes will be treated as "good" while others from the
     same source have been deemed invalid.

     This is the effect of, for example, "treat-as-withdraw".

     How much confidence can one have in the "good" routes, if the
     peer is sending a mixture of apparently valid and invalid
     stuff ?

     If a peer who sent a bunch of valid routes last week now sends a
     number of invalid ones, what do we think about the ones which
     remain "good" ?

     Should there be a mechanism to de-preference remaining "good"
     routes ?

     Is a response that has this effect required to be just the first
     step in a longer process, in which the cause of the error is
     dealt with ?  In which case, can more risks be taken when
     selecting such a response ?

  2. some routes will be treated as "good" which should be treated as
     invalid.

     This is the effect of not treating an error as Critical, but not
     identifying all affected NLRI.

     If this is not acceptable, then an implementation must take some
     care when deciding whether it has extracted all NLRI from a
     broken message.

     If there are degrees of acceptability, then an implementation
     would need to take a view... presumably based on some
     understanding of the likely operational impact ?

     Or there should be configuration knobs to twiddle ?

  3. some routes will be treated as valid which would previously have
     been treated as invalid.

     If the rules for validating attributes are changed, then some
     routes might be accepted with a variety of issues with their
     attributes.

     If processing proceeds with a partial set of attributes, routing
     may be affected.  If this is not acceptable, then an
     implementation must take great care here.

     While the question of which attributes and under what conditions
     this might happen is clearly an implementation issue, the
     acceptability of the result must be judged by its operational
     impact.

Also important from an operational perspective may be how any new
features to support better error handling are deployed.  Clearly new
code is involved.  But if new capabilities and new code at both ends
of an eBGP conversation are required, is that an issue ?  Should new
behaviour in BGP be required to be enabled by configuration, or
enabled by default but with suitable override configuration options ?

I am in violent agreement with you.  The high level requirements are
essentially operational ones.

My suggestion is that the requirements would be improved by backing
out of the discussion of the internal structure of BGP UPDATE
messages.  On the other hand, classifying errors in terms of what
information is lost/preserved, would improve things.  Such analysis
might lead to requirements which can only be met by changes at the
protocol/implementation level, and if so, more power to it, say I.

[Those changes might be: (a) a greater separation of NLRI from
Attributes, (b) more redundancy in the framing of attributes so that
the parser can have greater confidence that it has identified all
attributes sent, (c) a means to identify AFI/SAFI or VPN independent
of the NLRI, even ?, (d) etc... in addition to the various other
features mentioned in the draft for tearing down parts of a session,
recovering parts of the RIB, signalling errors, monitoring etc. etc.]

Thanks,

Chris

PS:  section 2 refers to "analysis of incidents".  Is there a
collection somewhere one could take into consideration when making
implementation decisions ?  Is there evidence, for example, that well
known attributes with invalid flags and/or lengths have been a problem
in practice ?



From rschrage@schrageconsult.net  Sun Sep  2 12:28:27 2012
Return-Path: <rschrage@schrageconsult.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 EF2BB21F8466; Sun,  2 Sep 2012 12:28:27 -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_DE=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q4ZMfnbzby8A; Sun,  2 Sep 2012 12:28:27 -0700 (PDT)
Received: from mailoutvans02.telekom-dienste.de (mailoutvans02.telekom-dienste.de [62.153.159.241]) by ietfa.amsl.com (Postfix) with ESMTP id E1B0121F8460; Sun,  2 Sep 2012 12:28:26 -0700 (PDT)
Received: from fwd04.aul.t-online.de (fwd04.aul.t-online.de ) by mailoutvans02.telekom-dienste.de with smtp  id 1T8FqJ-00046n-S3; Sun, 02 Sep 2012 21:28:23 +0200
Received: from ReinhardLaptop (TEZTw2ZZotFy6xCnr2xXDZL3unMoIOey3MSKpJ0wmM1mqR0J1mSue2mkLT84MgH5W4OwZMUJmK@[91.4.1.66]) by fwd04.webpage.t-com.de with esmtp id 1T8FqI-113QJc0; Sun, 2 Sep 2012 21:28:22 +0200
From: "Reinhard Schrage" <rschrage@schrageconsult.net>
To: <Ruediger.Geib@telekom.de>, <matt@internet2.edu>
References: <13205C286662DE4387D9AF3AC30EF456D771989330@EMBX01-WF.jnpr.net>	<50244EBF.7010709@internet2.edu> <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD77A228@HE111648.emea1.cds.t-internal.com>
In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D14DD77A228@HE111648.emea1.cds.t-internal.com>
Subject: RE: [ippm] Fwd: Liaison Statement from the Broadband Forum
Date: Sun, 2 Sep 2012 21:28:22 +0200
Message-ID: <002d01cd8941$1de09730$59a1c590$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac12ivfeUwStqsPCSreOgERWfwQNCAANZyggBJxuw9A=
Content-Language: en-gb
X-ID: TEZTw2ZZotFy6xCnr2xXDZL3unMoIOey3MSKpJ0wmM1mqR0J1mSue2mkLT84MgH5W4OwZMUJmK
X-TOI-MSGID: fcece860-4aba-4793-baf3-8c091e91b12d
X-Mailman-Approved-At: Tue, 04 Sep 2012 08:21:25 -0700
Cc: ietf@ietf.org, ippm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Sep 2012 19:28:28 -0000

I kind of like the idea of a liaison, as due to the work already done in the
IETF there is no need to re-invent already proven standards and procedures
and both sides may actually benefit.

Any actions already in place / planned?

Best regards
Reinhard Schrage
t:	+49 (0) 5137 909540
m:	+49 (0) 172  26.36.046
reinhard@schrageconsult.com


-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of
Ruediger.Geib@telekom.de
Sent: 10 August 2012 08:34
To: matt@internet2.edu
Cc: ietf@ietf.org; ippm@ietf.org
Subject: Re: [ippm] Fwd: Liaison Statement from the Broadband Forum

Matt,

I've read the liaision statement. The BBF informs us, that they plan to
"create a standard set of Broadband performance metrics to address on-going
regulatory, and consumer performance information needs."

BBF asks for guidance and support. From the document I couldn't identify the
architecture. I personally think IPPM members may volunteer to suggest IETF
metrics to BBF. But to me that requires that the architecture is clearly
defined (by BBF).

Regards,

Ruediger


-----Original Message-----
From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of
Matthew J Zekauskas
Sent: Friday, August 10, 2012 1:59 AM
To: IETF IPPM WG
Subject: [ippm] Fwd: Liaison Statement from the Broadband Forum

FYI, if folks here want to review.  Ron wants comments to ietf@ietf.org.

--Matt

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

Folks,

The Broadband Forum has sent a liaison statement to the IETF regarding a
"New Project - Broadband Access Service Attributes and Performance
Measures".

Click on the following link for details:
https://datatracker.ietf.org/liaison/1179/.

Please review and send comments to this list.

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm


From lear@cisco.com  Tue Sep  4 09:08:01 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F018621E803A; Tue,  4 Sep 2012 09:08: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9KIm2PYRRnqQ; Tue,  4 Sep 2012 09:08:00 -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 18D8221E8040; Tue,  4 Sep 2012 09:07:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=1595; q=dns/txt; s=iport; t=1346774880; x=1347984480; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=uCy8m4zeYTS/GfaFJ2rvIPYfEDGCLdSQa0dhvDt7cNM=; b=glQCoFLdnH/paL1k9F4WDXYAjAovhqPz22sspX23/4ZoPOyTenhrgDa6 pYC7jQzqMW+xfGHnI4QtL5cLM4wDdHps6G+IXeDQBqplQ6ixTAqhNTSrf tyZ8rStwLEklcJUheUrPjekcK3kSLJfFQbGS+JX0AK5mWY2AkLSp67hNV k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAIcmRlCQ/khN/2dsb2JhbABFDoV3tSaBB4IgAQEBAwESARBVARALGAICBRYLAgIJAwIBAgFFBg0BBwEBEA6HZQaaYY0ZkmKBIZAMgRIDizSKJYZLh2iBZ4IpPA
X-IronPort-AV: E=Sophos;i="4.80,367,1344211200"; d="scan'208";a="143308892"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 04 Sep 2012 16:07:53 +0000
Received: from dhcp-10-61-98-232.cisco.com (dhcp-10-61-98-232.cisco.com [10.61.98.232]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q84G7p0R020103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Sep 2012 16:07:53 GMT
Message-ID: <50462757.4090308@cisco.com>
Date: Tue, 04 Sep 2012 18:07:51 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu>
In-Reply-To: <tslmx168tk3.fsf@mit.edu>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Sep 2012 16:08:01 -0000

Sam,

On 9/4/12 3:29 AM, Sam Hartman wrote:
> I strongly urge  the IESG to be significantly more liberal in  the cases
> where an I-D will be removed from the archive.
>
> I can think of a number of cases where I'd hope that the IESg would be
> cooperative:
>
> 1) the IETF recieves a DMCA take-down notice or other instrument
> indicating that a third party believes an I-D infringes their copyright.
> Forcing such third parties to take the IETF to court does not seem to
> benefit the community.

This is knotty.

ANYONE can file a DMCA take-down notice.  Following it merely provides
safe harbor and is not always in the community interest.  The community
was disrupted because of what amounted to a bogus DMCA take-down notice
relating to the TZ database, when the NIH complied.  The IESG should
give the people who posted the draft an opportunity to respond to the
take-down notice prior to taking any action.  In the case of a WG I-D,
the IETF must take a more engaged role.

>
> 2) An author realizes that an I-D accidentally contains proprietary
> information, infringes someone else's copyright, failed to go through
> external release processes for the author/editor's organization, etc.
> Obviously factors like how long after the I-D is submitted might need to
> be considered.

It's difficult to codify policy like this in a group this large, but
except for the copyright issue in which a 3rd party may be exposed
through no fault of their own, I'd be concerned about abuse, and would
hate for us to sanction that sort of thing in text.

Eliot


From conte@isoc.org  Tue Sep  4 12:33:24 2012
Return-Path: <conte@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 7D19721E8084 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 12:33:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.265
X-Spam-Level: 
X-Spam-Status: No, score=-103.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rrCEYOAKG9dS for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 12:33:23 -0700 (PDT)
Received: from smtp197.dfw.emailsrvr.com (smtp197.dfw.emailsrvr.com [67.192.241.197]) by ietfa.amsl.com (Postfix) with ESMTP id 856AA21E8085 for <ietf@ietf.org>; Tue,  4 Sep 2012 12:33:23 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp19.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id E5B503C81CD for <ietf@ietf.org>; Tue,  4 Sep 2012 15:33:22 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp19.relay.dfw1a.emailsrvr.com (Authenticated sender: conte-AT-isoc.org) with ESMTPSA id B46DF3C815B for <ietf@ietf.org>; Tue,  4 Sep 2012 15:33:22 -0400 (EDT)
From: Steve Conte <conte@isoc.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: ISOC Fellowship to the IETF (IETF 86 and 87)
Message-Id: <32B51CE7-C101-4CA7-B78B-E7A29FF88F0E@isoc.org>
Date: Tue, 4 Sep 2012 12:33:22 -0700
To: ietf@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
X-Mailer: Apple Mail (2.1485)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Sep 2012 19:33:24 -0000

(apologies for cross-posting)
=20
Dear Colleagues,
=20
The Internet Society has announced that it is inviting applications for =
its latest Internet Society Fellowships to the IETF.  The Fellowship =
programme allows engineers from emerging and developing economies to =
attend an Internet Engineering Task Force (IETF) meeting.
=20
As you know, the IETF is the Internet's premier standards-making body, =
responsible for the development of protocols used in IP-based networks. =
IETF participants represent an international community of network =
designers, operators, vendors, and researchers involved in the technical =
operation of the Internet and the continuing evolution of Internet =
architecture.
=20
Fellowships will be awarded through a competitive application process. =
The Internet Society is currently accepting fellowship applications for =
the next two IETF meetings:
=20
* IETF 86, March 10-15, 2013, Orlando FL, USA
=20
* IETF 87, July 28 =96 August 2, 2013, Berlin, Germany
=20
Information and links to apply can be found at: =
http://www.internetsociety.org/fellows-ietf
=20
Fellowship applications for both IETF meetings are due by 01 October =
2012.
=20
=20
I encourage you apply or pass this information about this program to =
individuals involved in your network that have a keen interest in the =
Internet protocol development activities of the IETF.
=20
The Internet Society Fellowships to the IETF are sponsored by Afilias, =
SIDN, Google, Microsoft, and Verisign.
=20
If you have questions, please do not hesitate to contact Steve Conte =
<conte@isoc.org>.
=20
Kind Regards,
=20
Steve Conte
-----
Steve Conte
Internet Leadership Programmes
The Internet Society
conte@isoc.org





From chair@ietf.org  Tue Sep  4 15:11:05 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22B5321E80A1 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 15:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e+9qRtBGEudv for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 15:11:04 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 45D9F21F84B9 for <ietf@ietf.org>; Tue,  4 Sep 2012 15:11:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 4238B12BF17; Tue,  4 Sep 2012 15:11:04 -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 9RSPOiCXFAkZ; Tue,  4 Sep 2012 15:11:04 -0700 (PDT)
Received: from [10.143.192.103] (unknown [109.144.232.73]) by c8a.amsl.com (Postfix) with ESMTPSA id B0EB612BF1A; Tue,  4 Sep 2012 15:11:03 -0700 (PDT)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <50454EE4.5070203@dcrocker.net>
Date: Tue, 4 Sep 2012 13:22:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3A2461CA-73D4-42F5-A01E-F5B477A5F9D3@ietf.org>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <50454EE4.5070203@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
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, 04 Sep 2012 22:11:05 -0000

Dave:

Until recently, the I-D archive was not publicly available.  It was made =
public to support the rfcdiff tool.  Prior to this action, the I-D =
archive was accessible only to the Secretariat. This IESG statement is =
establishing the policy now that the I-D archive is public.

Russ


On Sep 3, 2012, at 8:44 PM, Dave Crocker wrote:

>=20
>=20
> On 9/3/2012 5:00 PM, IETF Chair wrote:
>> The IESG is considering this IESG Statement.  Comments from the =
community are solicited.
>=20
> 1.  Unless I've missed something, the statement seems to reflect
> established practice and established policy.  Or is it changing =
something?
>=20
> 2.  I had thought that somesuch statement had already been issued, but
> apparently not.  If there is a preceding document -- I can't think of
> one -- then any change from it's text would be worth noting.
>=20
> 3.  It would be worth clarify what prompts issuing this now.
>=20
> d/
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>=20


From housley@vigilsec.com  Tue Sep  4 15:11:12 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704C721E80A7 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 15:11:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w-b6yvaI2T8M for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 15:11:11 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 76E9121F84BF for <ietf@ietf.org>; Tue,  4 Sep 2012 15:11:11 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 13C899A400C; Tue,  4 Sep 2012 18:11:11 -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 G0SFgM6mjf5s; Tue,  4 Sep 2012 18:11:09 -0400 (EDT)
Received: from [10.143.192.103] (unknown [109.144.232.73]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 7E38F9A4008; Tue,  4 Sep 2012 18:11:09 -0400 (EDT)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5045E407.6050102@tana.it>
Date: Tue, 4 Sep 2012 13:57:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <299A1416-7E9D-4A3A-AB33-289AF70FA759@vigilsec.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu> <5045E407.6050102@tana.it>
To: Alessandro Vesely <vesely@tana.it>
X-Mailer: Apple Mail (2.1084)
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, 04 Sep 2012 22:11:12 -0000

Alessandro:

If an I-D is posted with secret text, then the secret is disclosed.  I-D =
are copied to many shadow repositories all over the world.  So, removing =
the I-D from ietf.org will not remove the secret text from the Internet.

Please explain what you mean by inappropriate boilerplate?  The I-D =
submission process checks the boilerplate.

Russ


On Sep 4, 2012, at 7:20 AM, Alessandro Vesely wrote:

> The first paragraph says:
>=20
> Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,
> and its Working Groups.  In addition, other groups, including the IAB
> and the IRTF Research Groups, distribute working documents as I-Ds.
>=20
> After all the groups, I'd add "and individuals".
>=20
> On Tue 04/Sep/2012 03:29:00 +0200 Sam Hartman wrote:
>>=20
>> 2) An author realizes that an I-D accidentally contains proprietary
>> information, infringes someone else's copyright, failed to go through
>> external release processes for the author/editor's organization, etc.
>> Obviously factors like how long after the I-D is submitted might need =
to
>> be considered.
>=20
> Except for I-Ds that reveal secret text, infringements should only
> result from inappropriate boilerplate copyright claims.  It would be
> enough to tag such I-Ds with a suitable disclaimer, in a way similar
> to how the presence of errata is (not) handled.
>=20


From johnl@iecc.com  Tue Sep  4 15:19:36 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8EEA21E8092 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 15:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6FEnAVnr-MAt for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 15:19:35 -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 7C76121E805A for <ietf@ietf.org>; Tue,  4 Sep 2012 15:19:35 -0700 (PDT)
Received: (qmail 31944 invoked from network); 4 Sep 2012 22:19:33 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 Sep 2012 22:19: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:vbr-info; s=50467e74.xn--hew.k1208; i=johnl@user.iecc.com; bh=bMMn4MUEJyJfIKC1SntBkd8g1W/kexINQvzDgzNhuME=; b=Mgv15thM4Vo51XEpFya0K273UfCmOarWVIJOjKQPi8N8DihH8+DdJhQSkFDVb9nvebTKk2Pf5iCkYGpeT5dDksHAlq6DEyAovhG0BZxDWmJxTNPpAz/8N7VjH1j/QZoyHiCLXWqEWkqPMdgkvee7OBMbmYvpJjhb78/2sPF5fG8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50467e74.xn--hew.k1208; olt=johnl@user.iecc.com; bh=bMMn4MUEJyJfIKC1SntBkd8g1W/kexINQvzDgzNhuME=; b=NkcvPXsd7XDeeskWu4XtvzJtIgrce8J8nsYqrWZHv6DRIeIBWU+Edy4y3GR5V+8MZGmFT6Tfj0vtQDFJ0z2BsgIfYIGS5M/oAuTvFxtM3iOXM1/G2evHRUYeHmI6aXE2gVhcQL0kRH/BCcY9eMBkcILksa2vLBXUPIEhq06JbhE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 4 Sep 2012 22:19:10 -0000
Message-ID: <20120904221910.6995.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <01f001cd8aaf$16d57450$44805cf0$@olddog.co.uk>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: adrian@olddog.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: Tue, 04 Sep 2012 22:19:36 -0000

> This discussion of DMCA is useful to me as a non-US resident.
> 
> Are we sure that the boilerplate included in I-Ds does not constitute a
> statement by the authors that they have not, as far as they are aware,
> infringed any copyright? In other words, isn't the boilerplate a
> pre-emptive counternotice?
  
It's not, and even if it were, would you want to find out
retroactively that you've agreed to pay the IETF's legal expenses if
someone sues about an I-D you posted?.  For more information, please
see this link in the message you just sent.

>> (http://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limita$

I agree with Elliott that we need a reasonable DMCA policy, keeping in
mind that it's pretty rare for a document, particularly a non-archival
one, to be worth the hassle of fighting a DMCA notice.  Fighting the
TZ takedown was absolutely worth it, but it was unusual in the
material attacked was of high value, and the basis for the notice was
unusually bogus.  Even so, someone had to pay for lawyers to prepare
the briefs and appear in court, and I wouldn't want the IETF to
promise to do that casually.

R's,
John


From vinayakh@gmail.com  Tue Sep  4 20:24:38 2012
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7941E11E8099 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 20:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JVm2QvBiioi0 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 20:24:37 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7518D11E808D for <ietf@ietf.org>; Tue,  4 Sep 2012 20:24:37 -0700 (PDT)
Received: by eaai11 with SMTP id i11so9442eaa.31 for <ietf@ietf.org>; Tue, 04 Sep 2012 20:24:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fklawIKVTptm+S7c2KS1yUHkPCFHPl4EGyOAXOeFwyo=; b=fOnyt3GtpwzLptPRXfzgTh6RjxkVtNgPAXQf3W6OxPvaYDc7P9M/fHGycmiajwNkbl RKF0DkGXkJYXczHl1/6SBLLwB+HZ2Ykr6GuRICGjb4X/Yk+SgtXqL3a0LOhyN6tF5jGL sPwG748SJ/iYDqMRE1457up2sOlC3g0WX0qqIbQ7hXGtEG+Q5I2sd2kKTgJAKXh5OcfA tsjD7Bu8R5p3BubBgQpDsb7dGXE+C2laBmWscads2fVTfbmRfik1JgJlcwgrGP5JvQIF WNlDiYs/R1Qshcd2M1jejUiZwucXRrZ2JCPizrUizVml9SE7Zdw25plN2jrK7hvIvwbq jjIA==
MIME-Version: 1.0
Received: by 10.14.193.136 with SMTP id k8mr28763549een.9.1346815476639; Tue, 04 Sep 2012 20:24:36 -0700 (PDT)
Received: by 10.14.100.67 with HTTP; Tue, 4 Sep 2012 20:24:36 -0700 (PDT)
In-Reply-To: <20120904221910.6995.qmail@joyce.lan>
References: <01f001cd8aaf$16d57450$44805cf0$@olddog.co.uk> <20120904221910.6995.qmail@joyce.lan>
Date: Wed, 5 Sep 2012 08:54:36 +0530
Message-ID: <CAKe6YvN8oTov0FvUtrnR=U092E7KJECyb1+-mECmvp5QKdjh4g@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Vinayak Hegde <vinayakh@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Sep 2012 03:24:38 -0000

On Wed, Sep 5, 2012 at 3:49 AM, John Levine <johnl@taugh.com> wrote:
>> This discussion of DMCA is useful to me as a non-US resident.
>>
>> Are we sure that the boilerplate included in I-Ds does not constitute a
>> statement by the authors that they have not, as far as they are aware,
>> infringed any copyright? In other words, isn't the boilerplate a
>> pre-emptive counternotice?
>
> It's not, and even if it were, would you want to find out
> retroactively that you've agreed to pay the IETF's legal expenses if
> someone sues about an I-D you posted?.  For more information, please
> see this link in the message you just sent.
>
>>> (http://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limita$
>
> I agree with Elliott that we need a reasonable DMCA policy, keeping in
> mind that it's pretty rare for a document, particularly a non-archival
> one, to be worth the hassle of fighting a DMCA notice.  Fighting the
> TZ takedown was absolutely worth it, but it was unusual in the
> material attacked was of high value, and the basis for the notice was
> unusually bogus.  Even so, someone had to pay for lawyers to prepare
> the briefs and appear in court, and I wouldn't want the IETF to
> promise to do that casually.

Also it might be useful for the submitter to sign (rather tick a
tickbox/radio button) an indemnification clause for the IETF before
submitting an I-D.

-- Vinayak

From scott@kitterman.com  Tue Sep  4 20:42:33 2012
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 DB97821F8459 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 20:42: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqw5vKTG6SNV for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 20:42:33 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4E321F842F for <ietf@ietf.org>; Tue,  4 Sep 2012 20:42:33 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 84E1020E40E3; Tue,  4 Sep 2012 23:42:32 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1346816552; bh=405ivR7YuV4Hc/tyPOQqbue8hrKQwMKplD9EL0yDJKI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=f0KKNmKFNmUK2Tf9lWenyTvPlRHMX+9EGHYr0wS6MBbZclj7loRmLq/RuFmlgu+5N SD9JhOfn+ga86XQgGy7rDyrIL4tX/OZKOqX2A5io0jpewIDWuVJAPY4iYNRPC0/9/I yc1Yi5mQjyxBRBVNPQ7P1Q7IWe8QpQBmwIKpHkac=
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 5583B20E40BD;  Tue,  4 Sep 2012 23:42:31 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Date: Tue, 04 Sep 2012 23:42:31 -0400
Message-ID: <27488276.WBa3lZnQ1F@scott-latitude-e6320>
User-Agent: KMail/4.8.4 (Linux/3.2.0-29-generic-pae; KDE/4.8.4; i686; ; )
In-Reply-To: <CAKe6YvN8oTov0FvUtrnR=U092E7KJECyb1+-mECmvp5QKdjh4g@mail.gmail.com>
References: <01f001cd8aaf$16d57450$44805cf0$@olddog.co.uk> <20120904221910.6995.qmail@joyce.lan> <CAKe6YvN8oTov0FvUtrnR=U092E7KJECyb1+-mECmvp5QKdjh4g@mail.gmail.com>
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, 05 Sep 2012 03:42:34 -0000

On Wednesday, September 05, 2012 08:54:36 AM Vinayak Hegde wrote:
> On Wed, Sep 5, 2012 at 3:49 AM, John Levine <johnl@taugh.com> wrote:
> >> This discussion of DMCA is useful to me as a non-US resident.
> >> 
> >> Are we sure that the boilerplate included in I-Ds does not constitute a
> >> statement by the authors that they have not, as far as they are aware,
> >> infringed any copyright? In other words, isn't the boilerplate a
> >> pre-emptive counternotice?
> > 
> > It's not, and even if it were, would you want to find out
> > retroactively that you've agreed to pay the IETF's legal expenses if
> > someone sues about an I-D you posted?.  For more information, please
> > see this link in the message you just sent.
> > 
> >>> (http://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Li
> >>> mita$> 
> > I agree with Elliott that we need a reasonable DMCA policy, keeping in
> > mind that it's pretty rare for a document, particularly a non-archival
> > one, to be worth the hassle of fighting a DMCA notice.  Fighting the
> > TZ takedown was absolutely worth it, but it was unusual in the
> > material attacked was of high value, and the basis for the notice was
> > unusually bogus.  Even so, someone had to pay for lawyers to prepare
> > the briefs and appear in court, and I wouldn't want the IETF to
> > promise to do that casually.
> 
> Also it might be useful for the submitter to sign (rather tick a
> tickbox/radio button) an indemnification clause for the IETF before
> submitting an I-D.

That would be an excellent way to ensure I never submitted an I.D. again.

Scott K

From marka@isc.org  Tue Sep  4 20:49:33 2012
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 12B6611E80DC for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 20:49: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8hgC1AyLZpLp for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 20:49:32 -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 5144711E80D3 for <ietf@ietf.org>; Tue,  4 Sep 2012 20:49:32 -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 48F655F984C; Wed,  5 Sep 2012 03:49:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:74ee:7a67:8ca9:e8d4]) (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 898F6216C6F; Wed,  5 Sep 2012 03:49:19 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 4CF41247B738; Wed,  5 Sep 2012 13:49:15 +1000 (EST)
To: Vinayak Hegde <vinayakh@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <01f001cd8aaf$16d57450$44805cf0$@olddog.co.uk> <20120904221910.6995.qmail@joyce.lan> <CAKe6YvN8oTov0FvUtrnR=U092E7KJECyb1+-mECmvp5QKdjh4g@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-reply-to: Your message of "Wed, 05 Sep 2012 08:54:36 +0530." <CAKe6YvN8oTov0FvUtrnR=U092E7KJECyb1+-mECmvp5QKdjh4g@mail.gmail.com>
Date: Wed, 05 Sep 2012 13:49:14 +1000
Message-Id: <20120905034915.4CF41247B738@drugs.dv.isc.org>
Cc: adrian@olddog.co.uk, 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, 05 Sep 2012 03:49:33 -0000

In message <CAKe6YvN8oTov0FvUtrnR=U092E7KJECyb1+-mECmvp5QKdjh4g@mail.gmail.com>, Vinayak Hegde writes:
> On Wed, Sep 5, 2012 at 3:49 AM, John Levine <johnl@taugh.com> wrote:
> >> This discussion of DMCA is useful to me as a non-US resident.
> >>
> >> Are we sure that the boilerplate included in I-Ds does not constitute a
> >> statement by the authors that they have not, as far as they are aware,
> >> infringed any copyright? In other words, isn't the boilerplate a
> >> pre-emptive counternotice?
> >
> > It's not, and even if it were, would you want to find out
> > retroactively that you've agreed to pay the IETF's legal expenses if
> > someone sues about an I-D you posted?.  For more information, please
> > see this link in the message you just sent.
> >
> >>> (http://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limita$
> >
> > I agree with Elliott that we need a reasonable DMCA policy, keeping in
> > mind that it's pretty rare for a document, particularly a non-archival
> > one, to be worth the hassle of fighting a DMCA notice.  Fighting the
> > TZ takedown was absolutely worth it, but it was unusual in the
> > material attacked was of high value, and the basis for the notice was
> > unusually bogus.  Even so, someone had to pay for lawyers to prepare
> > the briefs and appear in court, and I wouldn't want the IETF to
> > promise to do that casually.
> 
> Also it might be useful for the submitter to sign (rather tick a
> tickbox/radio button) an indemnification clause for the IETF before
> submitting an I-D.

We may as well close up shop if we have to start doing that.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From dwm@xpasc.com  Tue Sep  4 21:23:32 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA77211E80D3 for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 21:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQW9767c7k0j for <ietf@ietfa.amsl.com>; Tue,  4 Sep 2012 21:23: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 62F4C11E80BA for <ietf@ietf.org>; Tue,  4 Sep 2012 21:23:32 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id D768640531 for <ietf@ietf.org>; Wed,  5 Sep 2012 04:23: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 q854NV2W027965 for <ietf@ietf.org>; Tue, 4 Sep 2012 21:23:31 -0700
Date: Tue, 4 Sep 2012 21:23:31 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <CAKe6YvN8oTov0FvUtrnR=U092E7KJECyb1+-mECmvp5QKdjh4g@mail.gmail.com>
Message-ID: <alpine.LRH.2.01.1209042120560.27912@egate.xpasc.com>
References: <01f001cd8aaf$16d57450$44805cf0$@olddog.co.uk> <20120904221910.6995.qmail@joyce.lan> <CAKe6YvN8oTov0FvUtrnR=U092E7KJECyb1+-mECmvp5QKdjh4g@mail.gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 04:23:32 -0000

On Wed, 5 Sep 2012, Vinayak Hegde wrote:

> Also it might be useful for the submitter to sign (rather tick a
> tickbox/radio button) an indemnification clause for the IETF before
> submitting an I-D.

As an individual, I'd never consider agreeing to indemnify the IETF, even 
if I had created the whole document in isolation. The rightness of my
position is no guarantee there wouldn't be a false claim to the
contrary.

From johnl@iecc.com  Wed Sep  5 00:27:06 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9DF121F84F6 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 00:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBdJe6ijX-Iw for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 00:27:05 -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 94CF921F84F9 for <ietf@ietf.org>; Wed,  5 Sep 2012 00:27:05 -0700 (PDT)
Received: (qmail 28184 invoked from network); 5 Sep 2012 07:27:04 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 5 Sep 2012 07:27:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5046fec7.xn--3zv.k1208; i=johnl@user.iecc.com; bh=nm5DuEHlqoU2kdh9PVxplgmQA3M5rXAAHR3q4nx8mQ0=; b=ASDpGnV+VHSHL1i25ykty8LChXlx75wEjENkuPFzfBMDPg6DKoE8acIXZkV9Sl6id0lnK8bp9bbj3Sa8H7foNAu8YzzegM6aUZWjeI+GiCwuqwMrYl0H37jF2VggkvUzdhme2Yc6RY5Nkk4LgCcJ63zS1YprrwUVB63yDKTRiP0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5046fec7.xn--3zv.k1208; olt=johnl@user.iecc.com; bh=nm5DuEHlqoU2kdh9PVxplgmQA3M5rXAAHR3q4nx8mQ0=; b=dcywUcUwzzuQRNMVuxpJOzkiBX50JTBNSPWJNRSFyL+D4pSU7pdgZRy9Kc7pXZmu/szm/XeBJiwpS4VsCYCKYzX/P2J7qn15BABIAQVhvKm5FEiGN0SObaQg+GelMA8oFFsjYi6HN/rNwgZJHC5GO4pBUjCEhVxn0GGNgt7aieY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 5 Sep 2012 07:26:41 -0000
Message-ID: <20120905072641.5372.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <CAKe6YvN8oTov0FvUtrnR=U092E7KJECyb1+-mECmvp5QKdjh4g@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 07:27:06 -0000

>Also it might be useful for the submitter to sign (rather tick a
>tickbox/radio button) an indemnification clause for the IETF before
>submitting an I-D.

Even a totally meritless DMCA challenge could cost upwards of $100,000
in legal fees to challenge and go through court hearings.  Will that
be Mastercard, Visa, or Bitcoin?

R's,
John

PS: I think everyone else agrees with the general plan that the IESG
can use its discretion to remove I-Ds if they see a reason to do so.

From vesely@tana.it  Wed Sep  5 01:23:18 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD2D921F844D for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 01:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.471
X-Spam-Level: 
X-Spam-Status: No, score=-4.471 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOOFXEh-26sa for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 01:23:18 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id C0FC821F8648 for <ietf@ietf.org>; Wed,  5 Sep 2012 01:23:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1346833394; bh=B+8hF5bp0nxmOw44VLS3znHVVpCjeTPAND1PJJIpC7w=; l=1538; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=UIDM9kWh4q4rvJBhnpHjDvFguxAZppaxcB9Lw1WfaC/IPdX7FVmbbhBRLNnT1cXTV i0cDHkFo4gDvBnDZJUtZqxvO3242wVOLlICnAYobQQHR0AhlKi9OUhnLo8QNCId+SC I7sKP/zNF9IGCxd4Eu6P+Coguh4FaOuvKjcnmPa4=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 05 Sep 2012 10:23:14 +0200 id 00000000005DC035.0000000050470BF2.00007620
Message-ID: <50470BF1.4020409@tana.it>
Date: Wed, 05 Sep 2012 10:23:13 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <tslmx168tk3.fsf@mit.edu> <5045E407.6050102@tana.it> <299A1416-7E9D-4A3A-AB33-289AF70FA759@vigilsec.com>
In-Reply-To: <299A1416-7E9D-4A3A-AB33-289AF70FA759@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 08:23:18 -0000

On Tue 04/Sep/2012 19:57:36 +0200 Russ Housley wrote:
> 
> If an I-D is posted with secret text, then the secret is disclosed.
> I-D are copied to many shadow repositories all over the world.  So,
> removing the I-D from ietf.org will not remove the secret text from
> the Internet.

I figure the odds that an I-D contains secret text be reasonably low.

> Please explain what you mean by inappropriate boilerplate?  The I-D
> submission process checks the boilerplate.

For example, one of two authors might publish an I-D with trust200902
assuming the other author will be happy with that, and later find out
that that assumption was wrong.  As it formally licenses the work,
that boilerplate text may make the difference between fair use and
infringement of an exclusive right of the copyright owner --IANAL.

> On Sep 4, 2012, at 7:20 AM, Alessandro Vesely wrote:
>> On Tue 04/Sep/2012 03:29:00 +0200 Sam Hartman wrote:
>>> 
>>> 2) An author realizes that an I-D accidentally contains proprietary
>>> information, infringes someone else's copyright, failed to go through
>>> external release processes for the author/editor's organization, etc.
>>> Obviously factors like how long after the I-D is submitted might need to
>>> be considered.
>> 
>> Except for I-Ds that reveal secret text, infringements should only
>> result from inappropriate boilerplate copyright claims.  It would be
>> enough to tag such I-Ds with a suitable disclaimer, in a way similar
>> to how the presence of errata is (not) handled.



From sm@resistor.net  Wed Sep  5 02:39:15 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEDD121F84AE for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 02:39: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCFuCqHWdUqa for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 02:39: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 34E2A21F848B for <ietf@ietf.org>; Wed,  5 Sep 2012 02:39: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 q859d7Z5004847 for <ietf@ietf.org>; Wed, 5 Sep 2012 02:39:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1346837952; bh=zu1uDFHc1P0Mi+1wJyQmaJavjMT0VdaKJlxupTUhB5I=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=3SjgIrFdFzuTiTUuK1DhdySa1pkuWdX5D3dkuXXJ01zB2MS40uj0+witX1clblN8Q N2w2sRw9D5LlmM4k3UkTUShcEFL8np1ruz+z2GI0xHzSnixylHzXarwdwvp722hGZo fsKhDpQpUWfooOuaTLcIulPCYRLNbIKyjDDQx5jw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1346837952; i=@resistor.net; bh=zu1uDFHc1P0Mi+1wJyQmaJavjMT0VdaKJlxupTUhB5I=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=vIDSd/K3rza05VOpC4AWQIBTHOIz/UauSIBKJRqm7KbI9ARslyjx/f3437Z3Xztd1 F7wfNr2mBV+IEU7/6HonaWLdAzGl1P6aj3gEpNhoe1de3mRV/fvzV+9QTywxcQbPHz qnGkkY+4rTp+ORsJTAkIfL7XGEbz6Y6dnE7lN64c=
Message-Id: <6.2.5.6.2.20120905005713.08dde888@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 05 Sep 2012 02:20:43 -0700
To: IETF <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
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, 05 Sep 2012 09:39:16 -0000

At 17:00 03-09-2012, IETF Chair wrote:
>The IESG is considering this IESG Statement.  Comments from the 
>community are solicited.

[snip]

>An I-D will only be removed from the public I-D archive in compliance
>with a duly authorized court order.  If possible, a removed I-D will be
>replaced with a tombstone file that describes the reason that the I-D
>was removed from the public I-D archive.

I'll +1 the change (only for the IETF Stream) suggested by Alessandro Vesely.

Suggested text:

   An expired I-D will be removed from the public I-D archive when necessary.
   Such action will be taken by request of an IESG member, a chair of the
   working group associated with the I-D, or one of the document authors.
   If possible, a removed I-D will be replaced with a tombstone file that
   describes the reason that the I-D was removed from the public I-D archive.

The suggested text makes allowances for circumstances such as court 
orders.  I used "when necessary" and left it to the IESG to make the decision.

Note that there is an inconsistency between the above the existing 
guidelines.  Saying that an I-D has expired and distributing the I-D 
is a conflicting signal.

Regards,
-sm 


From vinayakh@gmail.com  Wed Sep  5 03:21:00 2012
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC46C21F8683 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 03:21:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MWC-zO-MXnXB for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 03:21:00 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id DE95E21F8688 for <ietf@ietf.org>; Wed,  5 Sep 2012 03:20:59 -0700 (PDT)
Received: by eekb45 with SMTP id b45so161221eek.31 for <ietf@ietf.org>; Wed, 05 Sep 2012 03:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=aD6e7A/Cxupy+hkLie0XWRRupiay0fZ/xZ07dLM/aPU=; b=m5e4TqoKyQ4YiDK9ejeBFjxMkmbP8Eu6I6ml5xSsjaPBImOys/s5WnrUp3gDJjN/1k OHHWYLOzV1lG7L0sCLgmk0jyJGc6L4O7c+2SRGS4GPOYJegrgoZB4rTM1vmV8dmAw0Xx 1xKyNgu5y875C6NUpB52R4gZXE0IRprqJAJV29arBtqb1EOqkcwCfjE95wapfL9HSHGp +1oKb/60ZxlnUsVy7L9dYqVivxlbUYMZL9gdgypyy8WxYrIfNLpb9xbMczrYiVX2Mpig 6qExSitaCDI5MZ/zlnFXDhxawW7BVvoNlE9jYg87RwlSpn7mSUEHNlIVk1nC0WbjLcX5 hf/g==
MIME-Version: 1.0
Received: by 10.14.202.71 with SMTP id c47mr30210925eeo.42.1346840458298; Wed, 05 Sep 2012 03:20:58 -0700 (PDT)
Received: by 10.14.100.67 with HTTP; Wed, 5 Sep 2012 03:20:58 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120905005713.08dde888@resistor.net>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net>
Date: Wed, 5 Sep 2012 15:50:58 +0530
Message-ID: <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Vinayak Hegde <vinayakh@gmail.com>
To: SM <sm@resistor.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: Wed, 05 Sep 2012 10:21:00 -0000

On Wed, Sep 5, 2012 at 2:50 PM, SM <sm@resistor.net> wrote:
>> An I-D will only be removed from the public I-D archive in compliance
>> with a duly authorized court order.  If possible, a removed I-D will be
>> replaced with a tombstone file that describes the reason that the I-D
>> was removed from the public I-D archive.
>
>
> I'll +1 the change (only for the IETF Stream) suggested by Alessandro
> Vesely.
>
> Suggested text:
>
>   An expired I-D will be removed from the public I-D archive when necessary.
>   Such action will be taken by request of an IESG member, a chair of the
>   working group associated with the I-D, or one of the document authors.
>
>   If possible, a removed I-D will be replaced with a tombstone file that
>   describes the reason that the I-D was removed from the public I-D archive.

+1
It might be prudent to add other details of the DMCA order as well. I
have seen that other websites do that.

This is a good FAQ on DMCA removal
http://www.chillingeffects.org/copyright/notice.cgi?NoticeID=627#QID130

-- Vinayak (IANAL)

From turners@ieca.com  Wed Sep  5 04:15:10 2012
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 65DD221F8530 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 04:15:10 -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.410, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SoJwXaJ-n5FX for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 04:15:10 -0700 (PDT)
Received: from gateway08.websitewelcome.com (gateway08.websitewelcome.com [69.56.224.29]) by ietfa.amsl.com (Postfix) with ESMTP id E29B321F8514 for <ietf@ietf.org>; Wed,  5 Sep 2012 04:15:09 -0700 (PDT)
Received: by gateway08.websitewelcome.com (Postfix, from userid 5007) id 4DA33A260741; Wed,  5 Sep 2012 06:15:10 -0500 (CDT)
Received: from gator1743.hostgator.com (gator1743.hostgator.com [184.173.253.227]) by gateway08.websitewelcome.com (Postfix) with ESMTP id 43129A26071E for <ietf@ietf.org>; Wed,  5 Sep 2012 06:15:10 -0500 (CDT)
Received: from [108.18.174.220] (port=50050 helo=thunderfish.local) by gator1743.hostgator.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <turners@ieca.com>) id 1T9DZd-000276-3C; Wed, 05 Sep 2012 06:15:09 -0500
Message-ID: <5047343C.6030305@ieca.com>
Date: Wed, 05 Sep 2012 07:15:08 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org, pkix@ietf.org
Subject: Re: [pkix] Last Call: <draft-ietf-pkix-rfc5280-clarifications-08.txt> (Updates	to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile) to Proposed Standard
References: <20120822150543.16802.27813.idtracker@ietfa.amsl.com>
In-Reply-To: <20120822150543.16802.27813.idtracker@ietfa.amsl.com>
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.18.174.220]:50050
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 6
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IxNzQzLmhvc3RnYXRvci5jb20=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Sep 2012 11:15:10 -0000

Based on IETF LC comments, I'm returning this draft to the WG.  Stay 
tuned for another IETF LC in a couple of weeks.

spt

On 8/22/12 11:05 AM, The IESG wrote:
>
> The IESG has received a request from the Public-Key Infrastructure
> (X.509) WG (pkix) to consider the following document:
> - 'Updates to the Internet X.509 Public Key Infrastructure Certificate
>     and Certificate Revocation List (CRL) Profile'
>    <draft-ietf-pkix-rfc5280-clarifications-08.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-09-05. 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 updates RFC 5280, the Internet X.509 Public Key
>     Infrastructure Certificate and Certificate Revocation List (CRL)
>     Profile.  This document changes the set of acceptable encoding
>     methods for the explicitText field of the user notice policy
>     qualifier and clarifies the rules for converting internationalized
>     domain name labels to ASCII.  This document also provides some
>     clarifications on the use of self-signed certificates, trust anchors,
>     and some updated security considerations.
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pkix-rfc5280-clarifications/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pkix-rfc5280-clarifications/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix
>

From ietf@thomasclausen.org  Wed Sep  5 07:32:06 2012
Return-Path: <ietf@thomasclausen.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 A999F21F85A4 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 07:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
X-Spam-Level: 
X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nc4ZBB8XLXLX for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 07:32:06 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 4644021F85AE for <ietf@ietf.org>; Wed,  5 Sep 2012 07:32:06 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 92514A4017 for <ietf@ietf.org>; Wed,  5 Sep 2012 07:32:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id CC1B01C0400; Wed,  5 Sep 2012 07:32:00 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.6.148] (ip-64-134-96-189.public.wayport.net [64.134.96.189]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 54F801C071B; Wed,  5 Sep 2012 07:32:00 -0700 (PDT)
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>
In-Reply-To: <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <5AE6DE85-2DFB-4BE2-B1E6-5E7A6BBCF4C4@thomasclausen.org>
X-Mailer: iPad Mail (9B206)
From: Thomas Heide Clausen <ietf@thomasclausen.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Date: Wed, 5 Sep 2012 10:32:01 -0400
To: Vinayak Hegde <vinayakh@gmail.com>
Cc: SM <sm@resistor.net>, 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, 05 Sep 2012 14:32:06 -0000

On 5 Sep 2012, at 06:20, Vinayak Hegde <vinayakh@gmail.com> wrote:

> On Wed, Sep 5, 2012 at 2:50 PM, SM <sm@resistor.net> wrote:
>>> An I-D will only be removed from the public I-D archive in compliance
>>> with a duly authorized court order.  If possible, a removed I-D will be
>>> replaced with a tombstone file that describes the reason that the I-D
>>> was removed from the public I-D archive.
>>=20
>>=20
>> I'll +1 the change (only for the IETF Stream) suggested by Alessandro
>> Vesely.
>>=20
>> Suggested text:
>>=20
>>  An expired I-D will be removed from the public I-D archive when necessar=
y.
>>  Such action will be taken by request of an IESG member, a chair of the
>>  working group associated with the I-D, or one of the document authors.
>>=20
>>  If possible, a removed I-D will be replaced with a tombstone file that
>>  describes the reason that the I-D was removed from the public I-D archiv=
e.
>=20
> +1
> It might be prudent to add other details of the DMCA order as well. I
> have seen that other websites do that.
>=20
> This is a good FAQ on DMCA removal
> http://www.chillingeffects.org/copyright/notice.cgi?NoticeID=3D627#QID130
>=20
> -- Vinayak (IANAL)

IANAL either, but I can imagine valid non-DMCA reasons for the IESG wanting t=
o remove an expired I-D, or add a tombstone file / note in its place.=20

For example, I have seen examples where an IETFer (who'd been around the blo=
ck a few times, and so did know better) repeatedly has held up and cited a l=
ong expired I-D claiming "Findings of the IETF show that ....", as part of h=
is/her argument in various contexts outside of the IETF.

Empowering the IESG to be able to act, in various such situations, and not j=
ust in response to court orders or DCMA requests, is IMO a good thing.

I like Alessandro's suggestion that "An expired I-D will be removed from the=
 public I-D archive when necessary".=20

I am on the fence if some sort of "consensus for removal" among the ADs shou=
ld be expected or not, though - as Alessandro's text concerns *expired* I-Ds=
. (It's trivial to render an *active* I-D *expired* by way of submitting a n=
ew version...)

Thomas=

From ted.ietf@gmail.com  Wed Sep  5 08:05:20 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29C9821F8687; Wed,  5 Sep 2012 08:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kgCU1pWaQgrL; Wed,  5 Sep 2012 08:05:19 -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 D129521F8673; Wed,  5 Sep 2012 08:05:15 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so1061404vcb.31 for <multiple recipients>; Wed, 05 Sep 2012 08:05:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=89vMCVQL1JJC4LzHrNErAT38QeA87Xs4/Gf8PX8PXUQ=; b=Om43wXrejU+z7J4SCZsaLUQUkpyIAHzYDputEFE4O0LyTG3n7WREpAj+N83FtFbExr iqf5beUwa9UPnGzN8r/HUDZHtOg2dqopLI331eDWSExtwsw95KDfXrsCOd6NRfQ7YQmP Cvj6ZmniCCe0aaAqIGlj4Ebhcjt2+TwXOd+3mvCOmrGhrs56FHj9OJZ7Gr+OK/vyU6iz LHaNGJ7kxNRdLuyfoNkMvl7EaLMQ/1Pl3myIRy6Nt0aly3YlcK7EHH9poxlUsgj7esy0 K9hfI+DNEM3uccLKkycm7xEScdiEnGu3GScJ4WfIFL6os9ThGu7GaC4eAHrfiJQCemOD p2Ig==
MIME-Version: 1.0
Received: by 10.220.107.136 with SMTP id b8mr2812286vcp.17.1346857515248; Wed, 05 Sep 2012 08:05:15 -0700 (PDT)
Received: by 10.58.201.226 with HTTP; Wed, 5 Sep 2012 08:05:15 -0700 (PDT)
In-Reply-To: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
Date: Wed, 5 Sep 2012 08:05:15 -0700
Message-ID: <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF Chair <chair@ietf.org>
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: Wed, 05 Sep 2012 15:05:20 -0000

On Mon, Sep 3, 2012 at 5:00 PM, IETF Chair <chair@ietf.org> wrote
> The IESG is considering this IESG Statement.  Comments from the community are solicited.
>
> On behalf of the IESG,
> Russ
>
> --- DRAFT IESG STATEMENT ---
>
> SUBJECT: Removal of an Internet-Draft from the IETF Web Site
>
> Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,
> and its Working Groups.  In addition, other groups, including the IAB
> and the IRTF Research Groups, distribute working documents as I-Ds.
> I-Ds are stored in two places on the IETF web site.  First, current
> ones are stored in the I-D directory.  Second, current and past ones
> are stored in a public I-D archive.
>
> I-Ds are readily available to a wide audience from the IETF I-D
> directory.  This availability facilitates informal review, comment,
> and revision.
>
> While entries in the I-D directory are subject to change or removal
> at any time, I-Ds generally remain publicly archived to support easy
> comparison with previous versions.
>
> Entries in the I-D directory are removed as part of normal process
> when it expires after six months, when it is replaced by a subsequent
> I-D, or when it is replaced by the publication of an RFC.  In all
> of these situations, the I-D remains in the public I-D archive.
>
> An I-D will only be removed from the public I-D archive in compliance
> with a duly authorized court order.  If possible, a removed I-D will be
> replaced with a tombstone file that describes the reason that the I-D
> was removed from the public I-D archive.
>

This statement doesn't actually seem to cover the case for removal
from the I-D directory, only the public archive. If you would like it
to cover the case where a court order or other action causes a
document to be removed from the public I-D directory, it probably
needs an update.  If that's covered in another document, pulling them
into a single document makes sense to me.

I support the idea that there be mechanisms for removal of IDs from
both that don't require a court order, but I don't think it should be
too simple.  I'd suggest:

a) Stream owner approval for streams outside the IETF stream
(documents identified as irtf or IAB).
b) Relevant AD for WG documents
c) IESG for individual submissions, with any AD able to put the matter
to the IESG.

There is an existing method for b as it relates to the current
directory--a working group chair replacing an editor and then having
the new editor issue a new draft. The AD should be consulted and
approve, though, if it either needs to be done more quickly than that
or it needs to relate to the archive.

c) is the most onerous because of the risk that simpler mechanisms
might be used to shut out ideas.  It might also be useful to clarify
that the appeal chain for this action follows the usual process.

Just my two cents,

Ted

From sm@resistor.net  Wed Sep  5 08:06:24 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FC321F866D for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 08:06: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ljQDQnT09Wxr for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 08:06:23 -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 05B5621F8672 for <ietf@ietf.org>; Wed,  5 Sep 2012 08:06: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 q85F64uZ027828; Wed, 5 Sep 2012 08:06:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1346857571; bh=BYOPnlQHruECSE9oY689NEpyPT4M2hUtJL8pIpw88Ks=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dWsRpb09cUl0/GmUFgFTvaNe1rB0XspyM79HWOakBvvqCFqhF8DcvWgbzKXougGar xKxSR+5dJPMvc9iHZUPmPrUEKIeW3avtNr4QVDsSw0IiHZnCt/acGO78Ou2iqADDeJ 47wLFGQJhIZ3t3ZmZIWdxxKvNqwxkLzBCuz06Qmw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1346857571; i=@resistor.net; bh=BYOPnlQHruECSE9oY689NEpyPT4M2hUtJL8pIpw88Ks=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=i3qCFw6WFYfflytzAWT1IR6q2C3MY2kyOkG5cpPN7nBJfwrJEWQMgMRS8cGLIY0rX kz1rkHKZGrreLR9miNr/QdVOduKvDh694um8eS0JIO0WOuLSI7jxcnJslLUw41UUYm tEgBmWy6rDIdwFpH3X1uAoHA3vZpbnYIzyfQQsuU=
Message-Id: <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 05 Sep 2012 07:51:40 -0700
To: IETF <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.g mail.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@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: Wed, 05 Sep 2012 15:06:25 -0000

At 03:20 05-09-2012, Vinayak Hegde wrote:
>It might be prudent to add other details of the DMCA order as well. I
>have seen that other websites do that.

The IETF can provide the reason for a removal, e.g. a DMCA order, in 
the tombstone.  The "if possible" was left in as there could be a gag 
order preventing the IETF from disclosing the facts about a removal.

Creating a perpetual I-D archive for the sake of rfcdiff is not a 
good idea as it goes against the notion of letting an I-D expire gracefully.

At 07:32 05-09-2012, Thomas Heide Clausen wrote:
>IANAL either, but I can imagine valid non-DMCA reasons for the IESG 
>wanting to remove an expired I-D, or add a tombstone file / note in its place.

Yes.  There has been a request to remove an I-D.

>For example, I have seen examples where an IETFer (who'd been around 
>the block a few times, and so did know better) repeatedly has held 
>up and cited a long expired I-D claiming "Findings of the IETF show 
>that ....", as part of his/her argument in various contexts outside 
>of the IETF.

The IETFer will now provide a long-lived URL for the expired I-D. :-)

>I am on the fence if some sort of "consensus for removal" among the 
>ADs should be expected or not, though - as Alessandro's text 
>concerns *expired* I-Ds. (It's trivial to render an *active* I-D 
>*expired* by way of submitting a new version...)

Yes.  The author has the ability to correct a mistake.  The new 
functionality makes matters more difficult for authors.  It can be 
argued that the I-D will remain available on the Internet.  There is 
nothing the IETF can do about that.  The IETF can make the matter 
easier for the author by not distributing the I-D automatically after 
six months.

Regards,
-sm 


From ietf@thomasclausen.org  Wed Sep  5 08:16:57 2012
Return-Path: <ietf@thomasclausen.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 075AA21F862B for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 08:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
X-Spam-Level: 
X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gZt4IPWzjJHG for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 08:16:56 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 7357321F85A8 for <ietf@ietf.org>; Wed,  5 Sep 2012 08:16:56 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 212CAA3263 for <ietf@ietf.org>; Wed,  5 Sep 2012 08:16:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 291E61BD2964; Wed,  5 Sep 2012 08:16:55 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.6.148] (ip-64-134-96-189.public.wayport.net [64.134.96.189]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id E81741BD2955; Wed,  5 Sep 2012 08:16:54 -0700 (PDT)
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>
In-Reply-To: <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <D5B4D55F-6C87-4F20-9086-62DC5C654B68@thomasclausen.org>
X-Mailer: iPad Mail (9B206)
From: Thomas Heide Clausen <ietf@thomasclausen.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Date: Wed, 5 Sep 2012 11:16:56 -0400
To: SM <sm@resistor.net>
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, 05 Sep 2012 15:16:57 -0000

On 5 Sep 2012, at 10:51, SM <sm@resistor.net> wrote:

> At 03:20 05-09-2012, Vinayak Hegde wrote:
>> It might be prudent to add other details of the DMCA order as well. I
>> have seen that other websites do that.
>=20
> The IETF can provide the reason for a removal, e.g. a DMCA order, in the t=
ombstone.  The "if possible" was left in as there could be a gag order preve=
nting the IETF from disclosing the facts about a removal.

I suspect that catching such things and capturing them in our procedures are=
 the reason why the IETF has legal counsel.

> Creating a perpetual I-D archive for the sake of rfcdiff is not a good ide=
a as it goes against the notion of letting an I-D expire gracefully.

On that, I agree fully.

> At 07:32 05-09-2012, Thomas Heide Clausen wrote:
>> IANAL either, but I can imagine valid non-DMCA reasons for the IESG wanti=
ng to remove an expired I-D, or add a tombstone file / note in its place.
>=20
> Yes.  There has been a request to remove an I-D.
>=20
>> For example, I have seen examples where an IETFer (who'd been around the b=
lock a few times, and so did know better) repeatedly has held up and cited a=
 long expired I-D claiming "Findings of the IETF show that ....", as part of=
 his/her argument in various contexts outside of the IETF.
>=20
> The IETFer will now provide a long-lived URL for the expired I-D. :-)

That's what has happened so far. It would be preferable if such an URL eithe=
r wasn't on an IETF-sanctioned server, though.=20

If archives of expired I-Ds are to exist on an IETF server, I-Ds should be c=
learly labeled as "These are *not* findings of the IETF, in fact, the IETF h=
as abandoned this effort, for whatever reason, whoever pointed you here isn'=
t keeping up" ;)

>=20
>> I am on the fence if some sort of "consensus for removal" among the ADs s=
hould be expected or not, though - as Alessandro's text concerns *expired* I=
-Ds. (It's trivial to render an *active* I-D *expired* by way of submitting a=
 new version...)
>=20
> Yes.  The author has the ability to correct a mistake.  The new functional=
ity makes matters more difficult for authors.  It can be argued that the I-D=
 will remain available on the Internet.  There is nothing the IETF can do ab=
out that.  The IETF can make the matter easier for the author by not distrib=
uting the I-D automatically after six months.

Yup.

Thomas

> Regards,
> -sm=20

From adrian@olddog.co.uk  Wed Sep  5 08:50:14 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1DF21F8680; Wed,  5 Sep 2012 08:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ggesdypw6vh4; Wed,  5 Sep 2012 08:50:13 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 97B8E21F867C; Wed,  5 Sep 2012 08:50:13 -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 q85FoBYE014418;  Wed, 5 Sep 2012 16:50:11 +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 q85Fo9gh014395 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Sep 2012 16:50:10 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ted Hardie'" <ted.ietf@gmail.com>, "'IETF Chair'" <chair@ietf.org>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com>
In-Reply-To: <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com>
Subject: RE: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Date: Wed, 5 Sep 2012 16:50:09 +0100
Message-ID: <03e901cd8b7e$218ab110$64a01330$@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: AQIo9JFi+jBMjw9cp0F8STNm++tPIQInASAhlrPavaA=
Content-Language: en-gb
Cc: 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 15:50:14 -0000

Hi Ted,

I think an I-D can be removed from the I-D directory by replacing it with
another I-D (possibly with null content, or possibly with tombstone text) using
existing process.

Cheers,
Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ted
> Hardie
> Sent: 05 September 2012 16:05
> To: IETF Chair
> Cc: IETF
> Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the
IETF
> Web Site
> 
> On Mon, Sep 3, 2012 at 5:00 PM, IETF Chair <chair@ietf.org> wrote
> > The IESG is considering this IESG Statement.  Comments from the community
> are solicited.
> >
> > On behalf of the IESG,
> > Russ
> >
> > --- DRAFT IESG STATEMENT ---
> >
> > SUBJECT: Removal of an Internet-Draft from the IETF Web Site
> >
> > Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,
> > and its Working Groups.  In addition, other groups, including the IAB
> > and the IRTF Research Groups, distribute working documents as I-Ds.
> > I-Ds are stored in two places on the IETF web site.  First, current
> > ones are stored in the I-D directory.  Second, current and past ones
> > are stored in a public I-D archive.
> >
> > I-Ds are readily available to a wide audience from the IETF I-D
> > directory.  This availability facilitates informal review, comment,
> > and revision.
> >
> > While entries in the I-D directory are subject to change or removal
> > at any time, I-Ds generally remain publicly archived to support easy
> > comparison with previous versions.
> >
> > Entries in the I-D directory are removed as part of normal process
> > when it expires after six months, when it is replaced by a subsequent
> > I-D, or when it is replaced by the publication of an RFC.  In all
> > of these situations, the I-D remains in the public I-D archive.
> >
> > An I-D will only be removed from the public I-D archive in compliance
> > with a duly authorized court order.  If possible, a removed I-D will be
> > replaced with a tombstone file that describes the reason that the I-D
> > was removed from the public I-D archive.
> >
> 
> This statement doesn't actually seem to cover the case for removal
> from the I-D directory, only the public archive. If you would like it
> to cover the case where a court order or other action causes a
> document to be removed from the public I-D directory, it probably
> needs an update.  If that's covered in another document, pulling them
> into a single document makes sense to me.
> 
> I support the idea that there be mechanisms for removal of IDs from
> both that don't require a court order, but I don't think it should be
> too simple.  I'd suggest:
> 
> a) Stream owner approval for streams outside the IETF stream
> (documents identified as irtf or IAB).
> b) Relevant AD for WG documents
> c) IESG for individual submissions, with any AD able to put the matter
> to the IESG.
> 
> There is an existing method for b as it relates to the current
> directory--a working group chair replacing an editor and then having
> the new editor issue a new draft. The AD should be consulted and
> approve, though, if it either needs to be done more quickly than that
> or it needs to relate to the archive.
> 
> c) is the most onerous because of the risk that simpler mechanisms
> might be used to shut out ideas.  It might also be useful to clarify
> that the appeal chain for this action follows the usual process.
> 
> Just my two cents,
> 
> Ted


From brian.e.carpenter@gmail.com  Wed Sep  5 09:04:02 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 555E021F85AA for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 09:04:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.631
X-Spam-Level: 
X-Spam-Status: No, score=-102.631 tagged_above=-999 required=5 tests=[AWL=1.060, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xtFEl7KY6dxc for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 09:04:01 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4C17C21F8498 for <ietf@ietf.org>; Wed,  5 Sep 2012 09:04:01 -0700 (PDT)
Received: by eekb45 with SMTP id b45so346209eek.31 for <ietf@ietf.org>; Wed, 05 Sep 2012 09:04:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MnME8KMKGz2zx02YfFXyCZXkKxfG9+U1yJ3D1VY9Lm0=; b=FkDHh31TWkBbgqDZMp1yn819nrINjjg/ZNv168Lu6dXk0OlKGwb+pTNAtsDL3lZPaJ e/e5cZBXOOfJTxVcT9qvqXYAxZ+tlzQX/Ntf1V09MdtM8psuHa44FA5nt8a7klzQrlrY cfXFJjn3JURJs4Yv60rhmlQvVyUxs183UG4ARUqBQiDHtNh0xYrUctcs5bPgMfdMYAmW VGSSLqcdLaAAfrZ1N0a8Pg6jvn2aE0TG9NMrPrbttLeywEvS7ffoRcT1EVY5NQmJbwEY UL5/W2whgxJDjdNwzfevXe5+UZTlTqFEz5pQba/j9g+GZYQq+MJ+iIK7OeuSB73Gs/+v yglA==
Received: by 10.14.218.5 with SMTP id j5mr31554883eep.16.1346861040549; Wed, 05 Sep 2012 09:04:00 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-127.as13285.net. [2.102.216.127]) by mx.google.com with ESMTPS id u47sm5425568eeo.9.2012.09.05.09.03.58 (version=SSLv3 cipher=OTHER); Wed, 05 Sep 2012 09:03:59 -0700 (PDT)
Message-ID: <504777F4.9000707@gmail.com>
Date: Wed, 05 Sep 2012 17:04:04 +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: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from	the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>
In-Reply-To: <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 16:04:02 -0000

On 05/09/2012 15:51, SM wrote:
...
> 
> Yes.  There has been a request to remove an I-D.
> 

That's an interesting but not very informative statement.

In the only case I am personally aware of, in 2006/7, there
was a dispute (outside the IETF), with lawyer's letters flying
around. Eventually, in a decision supported by the IETF Counsel,
not only was an I-D version taken down, but an *earlier* version
was put back with an artificially extended expiry date. No court
order was involved, and the eventual outcome was a private agreement
between the parties (outside the IETF).

I think the IESG needs to keep the flexibility to do that, although
in all normal circumstances the answer should be "we don't do that."

    Brian

From eric.gray@ericsson.com  Wed Sep  5 09:06:55 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A0F921F8672; Wed,  5 Sep 2012 09:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixgY4tBmMIUG; Wed,  5 Sep 2012 09:06:53 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 58EC121F865F; Wed,  5 Sep 2012 09:06:53 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q85G9Zod022810; Wed, 5 Sep 2012 11:09:53 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.204]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Wed, 5 Sep 2012 12:06:37 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "'Ted Hardie'" <ted.ietf@gmail.com>, "'IETF Chair'" <chair@ietf.org>
Date: Wed, 5 Sep 2012 12:06:35 -0400
Subject: RE: Draft IESG Statement on Removal of an Internet-Draft from	the IETF Web Site
Thread-Topic: Draft IESG Statement on Removal of an Internet-Draft from	the IETF Web Site
Thread-Index: AQIo9JFi+jBMjw9cp0F8STNm++tPIQInASAhlrPavaCAAAIiAA==
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB85BA2A@EUSAACMS0701.eamcs.ericsson.se>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com> <03e901cd8b7e$218ab110$64a01330$@olddog.co.uk>
In-Reply-To: <03e901cd8b7e$218ab110$64a01330$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Sep 2012 16:06:56 -0000

I am not at all convinced that there should be any reason, aside from a cou=
rt order, that
would remove an ID from the ID archive.

In addition to the potential advantages of being able to compare earlier ve=
rsions, there
is a real need to support - at some public location - what an earlier ID ac=
tually included,
for IPR and other legal reasons.

Removal of an ID from a public site - even by court order - will not remove=
 all copies of
the ID from other (private) locations (though a court order might make it i=
llegal to keep
any such "private" copies - helping to alleviate issues that might derive f=
rom them).  If
there remain nothing but private copies, it will be possible to produce mod=
ified versions
(for example) claiming they are "true copies" of the original ones.

I'm not a lawyer, but I would be more than a little bit leery of posting an=
 ID if I were not
going to be in a position to show what that ID actually said at some point =
in the future
when I might be confronted with an alleged copy that says something differe=
nt.

Bad enough we have to live with our real transgressions, without the possib=
ility of being
obliged to live with those that almost anyone could make up on our behalf..=
.

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Adr=
ian Farrel
Sent: Wednesday, September 05, 2012 11:50 AM
To: 'Ted Hardie'; 'IETF Chair'
Cc: 'IETF'
Subject: RE: Draft IESG Statement on Removal of an Internet-Draft from the =
IETF Web Site

Hi Ted,

I think an I-D can be removed from the I-D directory by replacing it with a=
nother I-D (possibly with null content, or possibly with tombstone text) us=
ing existing process.

Cheers,
Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf=20
> Of Ted Hardie
> Sent: 05 September 2012 16:05
> To: IETF Chair
> Cc: IETF
> Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from=20
> the
IETF
> Web Site
>=20
> On Mon, Sep 3, 2012 at 5:00 PM, IETF Chair <chair@ietf.org> wrote
> > The IESG is considering this IESG Statement.  Comments from the=20
> > community
> are solicited.
> >
> > On behalf of the IESG,
> > Russ
> >
> > --- DRAFT IESG STATEMENT ---
> >
> > SUBJECT: Removal of an Internet-Draft from the IETF Web Site
> >
> > Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,=20
> > and its Working Groups.  In addition, other groups, including the=20
> > IAB and the IRTF Research Groups, distribute working documents as I-Ds.
> > I-Ds are stored in two places on the IETF web site.  First, current=20
> > ones are stored in the I-D directory.  Second, current and past ones=20
> > are stored in a public I-D archive.
> >
> > I-Ds are readily available to a wide audience from the IETF I-D=20
> > directory.  This availability facilitates informal review, comment,=20
> > and revision.
> >
> > While entries in the I-D directory are subject to change or removal=20
> > at any time, I-Ds generally remain publicly archived to support easy=20
> > comparison with previous versions.
> >
> > Entries in the I-D directory are removed as part of normal process=20
> > when it expires after six months, when it is replaced by a=20
> > subsequent I-D, or when it is replaced by the publication of an RFC. =20
> > In all of these situations, the I-D remains in the public I-D archive.
> >
> > An I-D will only be removed from the public I-D archive in=20
> > compliance with a duly authorized court order.  If possible, a=20
> > removed I-D will be replaced with a tombstone file that describes=20
> > the reason that the I-D was removed from the public I-D archive.
> >
>=20
> This statement doesn't actually seem to cover the case for removal=20
> from the I-D directory, only the public archive. If you would like it=20
> to cover the case where a court order or other action causes a=20
> document to be removed from the public I-D directory, it probably=20
> needs an update.  If that's covered in another document, pulling them=20
> into a single document makes sense to me.
>=20
> I support the idea that there be mechanisms for removal of IDs from=20
> both that don't require a court order, but I don't think it should be=20
> too simple.  I'd suggest:
>=20
> a) Stream owner approval for streams outside the IETF stream=20
> (documents identified as irtf or IAB).
> b) Relevant AD for WG documents
> c) IESG for individual submissions, with any AD able to put the matter=20
> to the IESG.
>=20
> There is an existing method for b as it relates to the current=20
> directory--a working group chair replacing an editor and then having=20
> the new editor issue a new draft. The AD should be consulted and=20
> approve, though, if it either needs to be done more quickly than that=20
> or it needs to relate to the archive.
>=20
> c) is the most onerous because of the risk that simpler mechanisms=20
> might be used to shut out ideas.  It might also be useful to clarify=20
> that the appeal chain for this action follows the usual process.
>=20
> Just my two cents,
>=20
> Ted


From eric.gray@ericsson.com  Wed Sep  5 09:08:47 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 988D521F8679 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 09:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.599
X-Spam-Level: 
X-Spam-Status: No, score=-7.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qAoSSklGTwEm for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 09:08:47 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 15B6F21F8678 for <ietf@ietf.org>; Wed,  5 Sep 2012 09:08:47 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q85G8hEw028167 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Sep 2012 11:08:46 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.204]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Wed, 5 Sep 2012 12:08:24 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, SM <sm@resistor.net>
Date: Wed, 5 Sep 2012 12:08:23 -0400
Subject: RE: Draft IESG Statement on Removal of an Internet-Draft from	the IETF Web Site
Thread-Topic: Draft IESG Statement on Removal of an Internet-Draft from	the IETF Web Site
Thread-Index: Ac2LgDAv39IjOsWLRLOj5twtovBxawAAHo7Q
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB85BA33@EUSAACMS0701.eamcs.ericsson.se>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504777F4.9000707@gmail.com>
In-Reply-To: <504777F4.9000707@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Sep 2012 16:08:47 -0000

KzENCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYtYm91bmNlc0BpZXRm
Lm9yZyBbbWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEJyaWFuIEUg
Q2FycGVudGVyDQpTZW50OiBXZWRuZXNkYXksIFNlcHRlbWJlciAwNSwgMjAxMiAxMjowNCBQTQ0K
VG86IFNNDQpDYzogSUVURg0KU3ViamVjdDogUmU6IERyYWZ0IElFU0cgU3RhdGVtZW50IG9uIFJl
bW92YWwgb2YgYW4gSW50ZXJuZXQtRHJhZnQgZnJvbSB0aGUgSUVURiBXZWIgU2l0ZQ0KDQpPbiAw
NS8wOS8yMDEyIDE1OjUxLCBTTSB3cm90ZToNCi4uLg0KPiANCj4gWWVzLiAgVGhlcmUgaGFzIGJl
ZW4gYSByZXF1ZXN0IHRvIHJlbW92ZSBhbiBJLUQuDQo+IA0KDQpUaGF0J3MgYW4gaW50ZXJlc3Rp
bmcgYnV0IG5vdCB2ZXJ5IGluZm9ybWF0aXZlIHN0YXRlbWVudC4NCg0KSW4gdGhlIG9ubHkgY2Fz
ZSBJIGFtIHBlcnNvbmFsbHkgYXdhcmUgb2YsIGluIDIwMDYvNywgdGhlcmUgd2FzIGEgZGlzcHV0
ZSAob3V0c2lkZSB0aGUgSUVURiksIHdpdGggbGF3eWVyJ3MgbGV0dGVycyBmbHlpbmcgYXJvdW5k
LiBFdmVudHVhbGx5LCBpbiBhIGRlY2lzaW9uIHN1cHBvcnRlZCBieSB0aGUgSUVURiBDb3Vuc2Vs
LCBub3Qgb25seSB3YXMgYW4gSS1EIHZlcnNpb24gdGFrZW4gZG93biwgYnV0IGFuICplYXJsaWVy
KiB2ZXJzaW9uIHdhcyBwdXQgYmFjayB3aXRoIGFuIGFydGlmaWNpYWxseSBleHRlbmRlZCBleHBp
cnkgZGF0ZS4gTm8gY291cnQgb3JkZXIgd2FzIGludm9sdmVkLCBhbmQgdGhlIGV2ZW50dWFsIG91
dGNvbWUgd2FzIGEgcHJpdmF0ZSBhZ3JlZW1lbnQgYmV0d2VlbiB0aGUgcGFydGllcyAob3V0c2lk
ZSB0aGUgSUVURikuDQoNCkkgdGhpbmsgdGhlIElFU0cgbmVlZHMgdG8ga2VlcCB0aGUgZmxleGli
aWxpdHkgdG8gZG8gdGhhdCwgYWx0aG91Z2ggaW4gYWxsIG5vcm1hbCBjaXJjdW1zdGFuY2VzIHRo
ZSBhbnN3ZXIgc2hvdWxkIGJlICJ3ZSBkb24ndCBkbyB0aGF0LiINCg0KICAgIEJyaWFuDQo=

From john-ietf@jck.com  Wed Sep  5 09:46:39 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8579921F8688; Wed,  5 Sep 2012 09:46:39 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2d-o0yiU2Thw; Wed,  5 Sep 2012 09:46:39 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0759221F8686; Wed,  5 Sep 2012 09:46:39 -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 1T9IkP-000LBQ-Qc; Wed, 05 Sep 2012 12:46:37 -0400
Date: Wed, 05 Sep 2012 12:46:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Hardie <ted.ietf@gmail.com>, IETF Chair <chair@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <FDF7E4FD95E2B9EC19AC7400@JcK-HP8200.jck.com>
In-Reply-To: <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Sep 2012 16:46:39 -0000

--On Wednesday, September 05, 2012 08:05 -0700 Ted Hardie
<ted.ietf@gmail.com> wrote:

> I support the idea that there be mechanisms for removal of IDs
> from both that don't require a court order, but I don't think
> it should be too simple.  I'd suggest:
> 
> a) Stream owner approval for streams outside the IETF stream
> (documents identified as irtf or IAB).
> b) Relevant AD for WG documents
> c) IESG for individual submissions, with any AD able to put
> the matter to the IESG.

At least for category (c), it might be reasonable to be more
flexible about take-down, or at least early expiration, requests
from authors than from third parties.  That flexibility might
reasonably not apply once a WG (or RG or the IAB) has started
considering the document.

If the IESG wants to assume the burden of evaluating those
considerations on a case-by-case basis, it is fine with me, but
I continue to believe that IESG members have better things to do
with their time.  To say that a different way, we should avoid
loading more and more work onto the AD job description, even
with the assent of the incumbents, so that we can hope to get
candidates for the roles who do not have full-time support for
participation in the IETF (and who have no other substantive
responsibilities to their employers or sponsors during their
terms).

   john



From jari.arkko@piuha.net  Wed Sep  5 10:06:21 2012
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 C558D21F867B for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 10:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVI6tMwiduto for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 10:06:21 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 2B41521F86A8 for <ietf@ietf.org>; Wed,  5 Sep 2012 10:06:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3F1EF2D7DA for <ietf@ietf.org>; Wed,  5 Sep 2012 20:06: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 VR8K1MV510jZ for <ietf@ietf.org>; Wed,  5 Sep 2012 20:06:17 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 317152CC5D for <ietf@ietf.org>; Wed,  5 Sep 2012 20:06:17 +0300 (EEST)
Message-ID: <50478688.3030804@piuha.net>
Date: Wed, 05 Sep 2012 18:06:16 +0100
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com> <FDF7E4FD95E2B9EC19AC7400@JcK-HP8200.jck.com>
In-Reply-To: <FDF7E4FD95E2B9EC19AC7400@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 17:06:21 -0000

I'd be supportive of allowing the IESG to make a decision to remove I-Ds based on court orders, abuse, and other well-justified reasons.

Such events would be rare, and we should let the IESG do its job of making decisions based on available information. The statement need not and should not have an exact algorithm, because we will not be able to determine all the situations where this might be necessary. There are various abuse cases and even mistakes by the authors that in some rare cases might be something that should lead to documents being pulled. The statement should indicate, however, the reasons (such as showing prior art) why such take-downs should be rare.

Jari


From paul.hoffman@vpnc.org  Wed Sep  5 10:50:10 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0765B21F8670 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 10:50: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ztJWXD+2wzy0 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 10:50: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 79D9121F8669 for <ietf@ietf.org>; Wed,  5 Sep 2012 10:50:09 -0700 (PDT)
Received: from [10.20.30.108] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q85Ho6mE027892 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Sep 2012 10:50:07 -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.0 \(1486\))
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <50478688.3030804@piuha.net>
Date: Wed, 5 Sep 2012 10:50:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7A9CA0D-6EEC-4182-A648-548CDAD31163@vpnc.org>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com> <FDF7E4FD95E2B9EC19AC7400@JcK-HP8200.jck.com> <50478688.3030804@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1486)
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, 05 Sep 2012 17:50:10 -0000

On Sep 5, 2012, at 10:06 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> I'd be supportive of allowing the IESG to make a decision to remove =
I-Ds based on court orders, abuse, and other well-justified reasons.
>=20
> Such events would be rare, and we should let the IESG do its job of =
making decisions based on available information. The statement need not =
and should not have an exact algorithm, because we will not be able to =
determine all the situations where this might be necessary. There are =
various abuse cases and even mistakes by the authors that in some rare =
cases might be something that should lead to documents being pulled. The =
statement should indicate, however, the reasons (such as showing prior =
art) why such take-downs should be rare.

+1. I would also like to emphasize that the original statement said that =
things taken down would be replaced with descriptive tombstones. That is =
a very important feature of the proposal.

--Paul Hoffman=

From tglassey@earthlink.net  Wed Sep  5 11:01:20 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F10C21F84DE for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 11:01: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iqnoN6jfQaEJ for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 11:01:19 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id C37A121F8497 for <ietf@ietf.org>; Wed,  5 Sep 2012 11:01:19 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=WGEUBD8MZEBc1k1RpmgGk3eDmchr/7vRxTQFKi0nD9xaBLYzuu41QaTvdQbaPOuy; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1T9Juh-0008QV-8I for ietf@ietf.org; Wed, 05 Sep 2012 14:01:19 -0400
Message-ID: <5047936B.5020703@earthlink.net>
Date: Wed, 05 Sep 2012 11:01:15 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com> <FDF7E4FD95E2B9EC19AC7400@JcK-HP8200.jck.com> <50478688.3030804@piuha.net> <D7A9CA0D-6EEC-4182-A648-548CDAD31163@vpnc.org>
In-Reply-To: <D7A9CA0D-6EEC-4182-A648-548CDAD31163@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec797db09bc78b32f44ae90068f9f4c926c1350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 18:01:20 -0000

On 9/5/2012 10:50 AM, Paul Hoffman wrote:
> On Sep 5, 2012, at 10:06 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
>
>> I'd be supportive of allowing the IESG to make a decision to remove I-Ds based on court orders, abuse, and other well-justified reasons.
>>
>> Such events would be rare, and we should let the IESG do its job of making decisions based on available information. The statement need not and should not have an exact algorithm, because we will not be able to determine all the situations where this might be necessary. There are various abuse cases and even mistakes by the authors that in some rare cases might be something that should lead to documents being pulled. The statement should indicate, however, the reasons (such as showing prior art) why such take-downs should be rare.
> +1. I would also like to emphasize that the original statement said that things taken down would be replaced with descriptive tombstones. That is a very important feature of the proposal.
How would taking them down invalidate any previous licenses issued??? if 
nothing then taking the material down is meaningless since the act which 
licensed it for permanent use is irrevocable.

This was the whole point of describing the previous method as a one-way 
publishing path and it is what the problem is with any positive control 
over the IP and its licensing.

The issue is not what remains actively published but what was published 
on those previous dates and under what terms it was published. The whole 
point of taking something down is that it invalidates and revokes the 
license to use which is functionally meaningless here because of the 
original "you get to use it forever no matter what" licensing which the 
IETF has placed into control over the last 5 years or so.

As such doing anything with a public policy like this which doesn't 
address the underlying licensing is meaningless. It has no effect and is 
a waste of time since it clearly says we know something is wrong but we 
are not really going to fix it.

See my point?

Todd Glassey
>
> --Paul Hoffman
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2197 / Virus Database: 2437/5250 - Release Date: 09/05/12
>
>
>


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


From stewe@stewe.org  Wed Sep  5 11:01:26 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0E2521F86B1; Wed,  5 Sep 2012 11:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFdbWTwK23wn; Wed,  5 Sep 2012 11:01:26 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe002.messaging.microsoft.com [216.32.180.185]) by ietfa.amsl.com (Postfix) with ESMTP id 1562B21F86AF; Wed,  5 Sep 2012 11:01:25 -0700 (PDT)
Received: from mail200-co1-R.bigfish.com (10.243.78.241) by CO1EHSOBE009.bigfish.com (10.243.66.72) with Microsoft SMTP Server id 14.1.225.23; Wed, 5 Sep 2012 18:01:25 +0000
Received: from mail200-co1 (localhost [127.0.0.1])	by mail200-co1-R.bigfish.com (Postfix) with ESMTP id 3E97F1200EC; Wed,  5 Sep 2012 18:01:25 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -20
X-BigFish: PS-20(zz98dIc430I1432Izz1202h1082kzz1033IL8275dhz2fh2a8h668h839h944he5bhf0ah107ah1220h1155h)
Received-SPF: pass (mail200-co1: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail200-co1 (localhost.localdomain [127.0.0.1]) by mail200-co1 (MessageSwitch) id 134686808377900_11946; Wed,  5 Sep 2012 18:01:23 +0000 (UTC)
Received: from CO1EHSMHS024.bigfish.com (unknown [10.243.78.227])	by mail200-co1.bigfish.com (Postfix) with ESMTP id 0FCCD300050; Wed,  5 Sep 2012 18:01:23 +0000 (UTC)
Received: from BL2PRD0710HT005.namprd07.prod.outlook.com (157.56.240.133) by CO1EHSMHS024.bigfish.com (10.243.66.34) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 5 Sep 2012 18:01:22 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.242]) by BL2PRD0710HT005.namprd07.prod.outlook.com ([10.255.102.40]) with mapi id 14.16.0190.008; Wed, 5 Sep 2012 18:01:18 +0000
From: Stephan Wenger <stewe@stewe.org>
To: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Topic: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Index: AQHNi5By+Eu/tx54YkeSmteFmB35Kw==
Date: Wed, 5 Sep 2012 18:01:16 +0000
Message-ID: <CC6CCC68.8B24D%stewe@stewe.org>
In-Reply-To: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1755420024AAE9499E1D2664C3CFF21B@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 18:01:26 -0000

Hi,
I support this statement, with the additions suggested by Sam Hartman,
John Klensin, and (most importantly) Brian Carpenter.
In addition, I would suggest adding clarifying text to the extent that
I-Ds will remain to be stored in non publicly accessible form, unless
removal is required by a court order.
Stephan



On 9.3.2012 17:00 , "IETF Chair" <chair@ietf.org> wrote:

>The IESG is considering this IESG Statement.  Comments from the community
>are solicited.
>
>On behalf of the IESG,
>Russ
>
>--- DRAFT IESG STATEMENT ---
>
>SUBJECT: Removal of an Internet-Draft from the IETF Web Site
>
>Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,
>and its Working Groups.  In addition, other groups, including the IAB
>and the IRTF Research Groups, distribute working documents as I-Ds.
>I-Ds are stored in two places on the IETF web site.  First, current
>ones are stored in the I-D directory.  Second, current and past ones
>are stored in a public I-D archive.
>
>I-Ds are readily available to a wide audience from the IETF I-D
>directory.  This availability facilitates informal review, comment,
>and revision.
>
>While entries in the I-D directory are subject to change or removal
>at any time, I-Ds generally remain publicly archived to support easy
>comparison with previous versions.
>
>Entries in the I-D directory are removed as part of normal process
>when it expires after six months, when it is replaced by a subsequent
>I-D, or when it is replaced by the publication of an RFC.  In all
>of these situations, the I-D remains in the public I-D archive.
>
>An I-D will only be removed from the public I-D archive in compliance
>with a duly authorized court order.  If possible, a removed I-D will be
>replaced with a tombstone file that describes the reason that the I-D
>was removed from the public I-D archive.
>
>



From sm@resistor.net  Wed Sep  5 11:05:00 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6157121F86A8 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 11:05: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HhXQnyUnVuUs for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 11:04:59 -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 45F3221F8680 for <ietf@ietf.org>; Wed,  5 Sep 2012 11:04:53 -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 q85I4kSi022427; Wed, 5 Sep 2012 11:04:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1346868291; bh=rNqJUeNxCZFwuEwW/lhWADDGXc/I6jGBD0gLc2ga/Ws=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4sGMWIc6PtDy93hZ0VL6XJXxR7kcXwF0P+mG+l0pFkj92kwLa2Rv2ZzHHoT0XCehJ DWw0m7BVEePACRhwRpCKNquZB9bORF8TUIlopGOWfOGf3scJ6lYYzZhlL3KV1vYEZd DpCI7ev5wj8R14g3VjdpxmChwzJrvyjCUveRpVqs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1346868291; i=@resistor.net; bh=rNqJUeNxCZFwuEwW/lhWADDGXc/I6jGBD0gLc2ga/Ws=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Btw4Q0h/AekBZS/Fb4t8QBlghpwjA9oykwEMgMj6jGWTpkNHHpy9YaDydjlcdPhHD wOwjrhBrBCYxUPdmfnTrR9Tv/mbiYnGL4XBek2iRepbLlFof60W7wK3rs+Fth0v7SU MVjFdJLAUf0hQr/TvszUAGP08BX+0Y9QKYwu0IBI=
Message-Id: <6.2.5.6.2.20120905104856.0ad916a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 05 Sep 2012 11:02:37 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from	the IETF Web Site
In-Reply-To: <504777F4.9000707@gmail.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504777F4.9000707@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 05 Sep 2012 18:05:00 -0000

Hi Brian,
At 09:04 05-09-2012, Brian E Carpenter wrote:
>That's an interesting but not very informative statement.

http://www.ietf.org/mail-archive/web/ietf/current/msg71391.html

>I think the IESG needs to keep the flexibility to do that, although
>in all normal circumstances the answer should be "we don't do that."

Yes.

Regards,
-sm 


From ted.ietf@gmail.com  Wed Sep  5 11:17:34 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C82F221F863F; Wed,  5 Sep 2012 11:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bVTuKDMzGGfK; Wed,  5 Sep 2012 11:17:34 -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 F36CE21F8543; Wed,  5 Sep 2012 11:17:33 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so1363398vcb.31 for <multiple recipients>; Wed, 05 Sep 2012 11:17:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iFuEK3ET89tQNmKD/cipV9lxSwrOjAm8UsiMhT4lNGA=; b=u+ZBmbrz3HM/oc/XUwqm2VrCjsYzWvMZR5jeIm7gFnP4PoCnP/yZPQOpZ7PdIgMA6a kuC1IGV49Bi1ZIt7HbOf9A5b/yoXk9d1MqZwMXes0+OKNeuktrujXPPPaPgijh4ajviM AHf4P+sYDPtveySC+s/nKITfpfFponrpjQ1blTANvLWHetjRccg0hJ0jhThUb5hBYb1s 3U1QfNbpKgPwzYtZS5FiBwUfsuOeBt2i0SAbFjC8+yDQQdnFADSDIdndEMNT1UTK67y9 a0hnow2DKjkrhpBdRuueoJ39zBo6vx3nvd3a5E9aOUJNACVgW2qs5K9orbQ58bogmLft s9JA==
MIME-Version: 1.0
Received: by 10.52.175.193 with SMTP id cc1mr16639338vdc.61.1346869052198; Wed, 05 Sep 2012 11:17:32 -0700 (PDT)
Received: by 10.58.201.226 with HTTP; Wed, 5 Sep 2012 11:17:32 -0700 (PDT)
In-Reply-To: <03e901cd8b7e$218ab110$64a01330$@olddog.co.uk>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com> <03e901cd8b7e$218ab110$64a01330$@olddog.co.uk>
Date: Wed, 5 Sep 2012 11:17:32 -0700
Message-ID: <CA+9kkMDMtkxuELBxjYpAU8dPptO1Z0B0tcsyCz-Je8EDyTPOXQ@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Ted Hardie <ted.ietf@gmail.com>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 18:17:34 -0000

On Wed, Sep 5, 2012 at 8:50 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> Hi Ted,
>
> I think an I-D can be removed from the I-D directory by replacing it with
> another I-D (possibly with null content, or possibly with tombstone text) using
> existing process.
>
> Cheers,
> Adrian

Hi Adrian,

That's true, and if the existing author wants to do that, this policy
is not needed at all.  The question is who needs to approve a request
to remove it if it does not come from the author.  Sorry that this was
not clear.

regards,

Ted Hardie

>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ted
>> Hardie
>> Sent: 05 September 2012 16:05
>> To: IETF Chair
>> Cc: IETF
>> Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the
> IETF
>> Web Site
>>
>> On Mon, Sep 3, 2012 at 5:00 PM, IETF Chair <chair@ietf.org> wrote
>> > The IESG is considering this IESG Statement.  Comments from the community
>> are solicited.
>> >
>> > On behalf of the IESG,
>> > Russ
>> >
>> > --- DRAFT IESG STATEMENT ---
>> >
>> > SUBJECT: Removal of an Internet-Draft from the IETF Web Site
>> >
>> > Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,
>> > and its Working Groups.  In addition, other groups, including the IAB
>> > and the IRTF Research Groups, distribute working documents as I-Ds.
>> > I-Ds are stored in two places on the IETF web site.  First, current
>> > ones are stored in the I-D directory.  Second, current and past ones
>> > are stored in a public I-D archive.
>> >
>> > I-Ds are readily available to a wide audience from the IETF I-D
>> > directory.  This availability facilitates informal review, comment,
>> > and revision.
>> >
>> > While entries in the I-D directory are subject to change or removal
>> > at any time, I-Ds generally remain publicly archived to support easy
>> > comparison with previous versions.
>> >
>> > Entries in the I-D directory are removed as part of normal process
>> > when it expires after six months, when it is replaced by a subsequent
>> > I-D, or when it is replaced by the publication of an RFC.  In all
>> > of these situations, the I-D remains in the public I-D archive.
>> >
>> > An I-D will only be removed from the public I-D archive in compliance
>> > with a duly authorized court order.  If possible, a removed I-D will be
>> > replaced with a tombstone file that describes the reason that the I-D
>> > was removed from the public I-D archive.
>> >
>>
>> This statement doesn't actually seem to cover the case for removal
>> from the I-D directory, only the public archive. If you would like it
>> to cover the case where a court order or other action causes a
>> document to be removed from the public I-D directory, it probably
>> needs an update.  If that's covered in another document, pulling them
>> into a single document makes sense to me.
>>
>> I support the idea that there be mechanisms for removal of IDs from
>> both that don't require a court order, but I don't think it should be
>> too simple.  I'd suggest:
>>
>> a) Stream owner approval for streams outside the IETF stream
>> (documents identified as irtf or IAB).
>> b) Relevant AD for WG documents
>> c) IESG for individual submissions, with any AD able to put the matter
>> to the IESG.
>>
>> There is an existing method for b as it relates to the current
>> directory--a working group chair replacing an editor and then having
>> the new editor issue a new draft. The AD should be consulted and
>> approve, though, if it either needs to be done more quickly than that
>> or it needs to relate to the archive.
>>
>> c) is the most onerous because of the risk that simpler mechanisms
>> might be used to shut out ideas.  It might also be useful to clarify
>> that the appeal chain for this action follows the usual process.
>>
>> Just my two cents,
>>
>> Ted
>

From ted.ietf@gmail.com  Wed Sep  5 11:32:45 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF7721F8671; Wed,  5 Sep 2012 11:32:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GgYNbOks6VI8; Wed,  5 Sep 2012 11:32:45 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id D4C8921F8669; Wed,  5 Sep 2012 11:32:44 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so470186vbb.31 for <multiple recipients>; Wed, 05 Sep 2012 11:32:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FGyDy5s+h2eggQqairUXQt0yX0T9JdCUKRGOnng/gcY=; b=uxKVqUmJ6LZ6DxtAApq8tpE5MU3SZ+rqVVjbyXpjcUJxtcKNvCX/4SIMVd2JGh/qPp iF5Xgmgw3chAZfgsUmZxarPx8JRchm5wpAMUk3gRMRX9z9BleotHCsbw/RnvtCYWVUyM WmQJ8smwaN+86Oqhdjq5yGP4qc3R/WMsZ3+lJIVfRIRDm0pRLRAqUSiWoqa+iXKBvqwf wCjfufFlt26+GclazZj9iPy3wAJ8gjpZ4kLosL/NWuvdknRomoT/G+ZeqoZqz3hSvpei yKuvH3rNrozE/j35arKXuqid3DGeaZ+tyks3liJx/kLazIX+z8njyer9JdqyNL2HyhZp Y6jg==
MIME-Version: 1.0
Received: by 10.52.24.229 with SMTP id x5mr16428201vdf.43.1346869964237; Wed, 05 Sep 2012 11:32:44 -0700 (PDT)
Received: by 10.58.201.226 with HTTP; Wed, 5 Sep 2012 11:32:44 -0700 (PDT)
In-Reply-To: <FDF7E4FD95E2B9EC19AC7400@JcK-HP8200.jck.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com> <FDF7E4FD95E2B9EC19AC7400@JcK-HP8200.jck.com>
Date: Wed, 5 Sep 2012 11:32:44 -0700
Message-ID: <CA+9kkMBO6OWKkZa8bi__3OKrAMPgY9z3JjH-nYropF2i=ZSepw@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Ted Hardie <ted.ietf@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 18:32:45 -0000

On Wed, Sep 5, 2012 at 9:46 AM, John C Klensin <john-ietf@jck.com> wrote:
>
>> a) Stream owner approval for streams outside the IETF stream
>> (documents identified as irtf or IAB).
>> b) Relevant AD for WG documents
>> c) IESG for individual submissions, with any AD able to put
>> the matter to the IESG.
>
> At least for category (c), it might be reasonable to be more
> flexible about take-down, or at least early expiration, requests
> from authors than from third parties.

I am fine with that, though I had been assuming that replacing an I-D
in the public directory was fast enough that it would be the default.
The problem then turns into how to remove it from the archive
directory if the author also wants that.


> That flexibility might
> reasonably not apply once a WG (or RG or the IAB) has started
> considering the document.
>
> If the IESG wants to assume the burden of evaluating those
> considerations on a case-by-case basis, it is fine with me, but
> I continue to believe that IESG members have better things to do
> with their time.  To say that a different way, we should avoid
> loading more and more work onto the AD job description, even
> with the assent of the incumbents, so that we can hope to get
> candidates for the roles who do not have full-time support for
> participation in the IETF (and who have no other substantive
> responsibilities to their employers or sponsors during their
> terms).
>
For third party requests to remove others' independent submissions, I
think there should be a pretty high bar.  "Open submission" is a key
part of "open standards", in my opinion, and if it becomes overly easy
to cause submissions to be removed, we run risks to our process that I
think are worse than the added load on the IESG.  If you were replying
only in regards to first-party requests, than, as I said, I'm fine
with the moral equivalent of early expiry.

The only reason I can see for making third party removal of public,
non-expired I-Ds be at the discretion of the IESG, rather than
requiring a court order, is that someone could attempt to publish
patently offensive material in an I-D as an attack.  Forcing us to pay
the legal fees for a court order would be a potential DoS, as someone
up-thread noted.  If it weren't for that, I would support court order
only.

regards,

Ted


>    john
>
>

From john-ietf@jck.com  Wed Sep  5 13:00:05 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E036621F86B9 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 13:00:05 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QazfTz4noAs3 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 13:00:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 39A3621F86AD for <ietf@ietf.org>; Wed,  5 Sep 2012 13:00:05 -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 1T9LlZ-000LpC-PT; Wed, 05 Sep 2012 16:00:01 -0400
Date: Wed, 05 Sep 2012 15:59:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft	from	the IETF Web Site
Message-ID: <0901BE7939A76E7CA259D178@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20120905104856.0ad916a8@resistor.net>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504777F4.9000707@gmail.com> <6.2.5.6.2.20120905104856.0ad916a8@resistor.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF <ietf@ietf.org>, Subramanian Moonesamy <sm+ietf@elandsys.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, 05 Sep 2012 20:00:06 -0000

--On Wednesday, September 05, 2012 11:02 -0700 SM
<sm@resistor.net> wrote:

> At 09:04 05-09-2012, Brian E Carpenter wrote:
>> That's an interesting but not very informative statement.
> 
> http://www.ietf.org/mail-archive/web/ietf/current/msg71391.html

Of course, there is a case to be made that, if we had a more
sophisticated posting system that enforced the few rules we
already have, it would not have been accepted and posted in the
first place.  Individual drafts are supposed to be title
draft-OneOfTheAuthorNames-foo-bar-NN.  This one didn't meet that
rule.   From the standpoint of those rules/conventions about
naming at least, it is as if I posted something as
draft-moonesamy-foobar-00 or draft-carpenter-barfoo-00 in the
hope that would get extra attention.

That said, the author in this particular case could presumably
have posted draft-vesely-spam-reporting-using-imap-kleansed-00
and then persuaded the Secretariat that it replaced
draft-ordogh-spam-reporting-using-imap-kleansed-00, thereby
causing the latter to be removed from the _active_ I-D
repository and moved off to the historical I-D archive.

    john


From randy@psg.com  Wed Sep  5 15:15:39 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E9E821F86C5; Wed,  5 Sep 2012 15:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aHKSN3E+RI5o; Wed,  5 Sep 2012 15:15:39 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2D73B21F86C3; Wed,  5 Sep 2012 15:15:39 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1T9Nsm-000Fmz-DI; Wed, 05 Sep 2012 22:15:37 +0000
Date: Thu, 06 Sep 2012 05:16:36 +0700
Message-ID: <m24nnc9ku3.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Chair <chair@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF	Web Site
In-Reply-To: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: 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, 05 Sep 2012 22:15:39 -0000

> The IESG is considering this IESG Statement.  Comments from the
> community are solicited.

i presume that you have done your legal homework and know what you are
doing.  and i try not to play amateur lawyer.

so it seems like a good thing to me.

randy

From sm@resistor.net  Wed Sep  5 15:20:40 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCDFD21F86FF for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 15:20: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01egHBUp31v2 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 15:20: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 2F65D21F86F9 for <ietf@ietf.org>; Wed,  5 Sep 2012 15:20:39 -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 q85MKXnA002808; Wed, 5 Sep 2012 15:20:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1346883638; bh=zL4IU/ckc63I/TZt/pdtwusGaJW4pWScilghIcyKF48=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=g1cRuXdV+ftNSgWomLEu1kgK6njYas/YA5OyzcbKoeVCElXPJri1NGSNA50BoEVW3 T+V3jvRl0PSK9U/16YrwTY7ofHnaEy3+tcp2KBnezZCNHYUzwhn4VpsHYawdJwSQMm eoRiAU+tG2CrkCYyg5M61JAoo9gl114OTsgtSUkE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1346883638; i=@resistor.net; bh=zL4IU/ckc63I/TZt/pdtwusGaJW4pWScilghIcyKF48=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eruWo7uswTBjygaMNe8lGcu79U9VJYULAR7zDXgaK53vUbA8iunmvznBEz8bzudnu d+obcjEk8W3riZ97770FvZ5CWQLB8aNXQsiQ8f/y2F3OLzVu92GMSDJHKzRSCkznpC UAlZ8CKvMKT7c4wQcUqo2OK18VEyzvo8Hb3SrArU=
Message-Id: <6.2.5.6.2.20120905144154.0b350a18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 05 Sep 2012 15:12:57 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <0901BE7939A76E7CA259D178@JcK-HP8200.jck.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504777F4.9000707@gmail.com> <6.2.5.6.2.20120905104856.0ad916a8@resistor.net> <0901BE7939A76E7CA259D178@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 05 Sep 2012 22:20:40 -0000

Hi John,
At 12:59 05-09-2012, John C Klensin wrote:
>Of course, there is a case to be made that, if we had a more
>sophisticated posting system that enforced the few rules we
>already have, it would not have been accepted and posted in the
>first place.  Individual drafts are supposed to be title
>draft-OneOfTheAuthorNames-foo-bar-NN.  This one didn't meet that

Yes.

>That said, the author in this particular case could presumably
>have posted draft-vesely-spam-reporting-using-imap-kleansed-00
>and then persuaded the Secretariat that it replaced
>draft-ordogh-spam-reporting-using-imap-kleansed-00, thereby
>causing the latter to be removed from the _active_ I-D
>repository and moved off to the historical I-D archive.

Yes.

Mistakes can happen.  The expiration provides, to some degree, the 
ability to forget.

Regards,
-sm   


From dhc@dcrocker.net  Wed Sep  5 15:23:44 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 114E121F86F9; Wed,  5 Sep 2012 15:23: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dywg+muvmLco; Wed,  5 Sep 2012 15:23:43 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 836BC21F8681; Wed,  5 Sep 2012 15:23:43 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q85MNg7d022603 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 5 Sep 2012 15:23:43 -0700
Message-ID: <5047D0EB.90501@dcrocker.net>
Date: Wed, 05 Sep 2012 15:23:39 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF	Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <m24nnc9ku3.wl%randy@psg.com>
In-Reply-To: <m24nnc9ku3.wl%randy@psg.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, 05 Sep 2012 15:23:43 -0700 (PDT)
Cc: IETF Chair <chair@ietf.org>, 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, 05 Sep 2012 22:23:44 -0000

On 9/5/2012 3:16 PM, Randy Bush wrote:
>> The IESG is considering this IESG Statement.  Comments from the
>> community are solicited.
>
> i presume that you have done your legal homework


alas, they hadn't.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From john-ietf@jck.com  Wed Sep  5 16:41:03 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B05F21F86FE; Wed,  5 Sep 2012 16:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sv09exnIIUzQ; Wed,  5 Sep 2012 16:41:02 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 71E8C21F86EC; Wed,  5 Sep 2012 16:41:02 -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 1T9PDQ-000Mmk-4y; Wed, 05 Sep 2012 19:41:00 -0400
Date: Wed, 05 Sep 2012 19:40:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Message-ID: <D8243A23B0A3798CA947C2DF@JcK-HP8200.jck.com>
In-Reply-To: <CA+9kkMBO6OWKkZa8bi__3OKrAMPgY9z3JjH-nYropF2i=ZSepw@mail.gmail.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <CA+9kkMCs8Wcs_fs2rJDxiVwOBeUwwKwTQfAX4XWT1hQKuiFAdw@mail.gmail.com> <FDF7E4FD95E2B9EC19AC7400@JcK-HP8200.jck.com> <CA+9kkMBO6OWKkZa8bi__3OKrAMPgY9z3JjH-nYropF2i=ZSepw@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 Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 23:41:03 -0000

--On Wednesday, September 05, 2012 11:32 -0700 Ted Hardie
<ted.ietf@gmail.com> wrote:

> For third party requests to remove others' independent
> submissions, I think there should be a pretty high bar.  "Open
> submission" is a key part of "open standards", in my opinion,
> and if it becomes overly easy to cause submissions to be
> removed, we run risks to our process that I think are worse
> than the added load on the IESG.  If you were replying only in
> regards to first-party requests, than, as I said, I'm fine
> with the moral equivalent of early expiry.

I agree about the third-party requests.  If people have to
resort to legal process for them, I'd lose no sleep over it.  On
the other hand, a removal request from a WG Chair or AD for a WG
document isn't really third party, nor would be corresponding
actions by the IAB or IRTF for documents created at their
request.

> The only reason I can see for making third party removal of
> public, non-expired I-Ds be at the discretion of the IESG,
> rather than requiring a court order, is that someone could
> attempt to publish patently offensive material in an I-D as an
> attack.  Forcing us to pay the legal fees for a court order
> would be a potential DoS, as someone up-thread noted.  If it
> weren't for that, I would support court order only.

I more or less agree, but remember that a DMCA takedown request
is not a court order but has a certain amount of legal standing
in the jurisdictions in which the Secretariat, most of the
servers, the IAD, the IETF Trust, and ISOC are subject.  One
(IANAL, so not necessarily completely accurate) way to
characterize it is that it lets a recipient (potentially the
IETF) distinguish between "we just provide the service of
posting I-Ds but are not responsible for their content" and
"these are documents for which we are willing to accept
responsibility (for copyright clearance as well as conformance
with other laws)".  As long as we are willing to say "anyone can
post anything they like as I-Ds, with no prior review by 'the
IETF'", we had best decide we are a service provider and be
willing to take down on that basis -- or we better schedule the
budget increase to cover liability for copyright violations when
some third-party posts potentially infringing material and we
accept responsibility by ignoring the DMCA notice.

Again, really expert legal advice is in order here. I'm
certainly not trying to give it, but this discussion is getting
pretty far out in the weeds without that advice.   If the IESG
has already obtained it, I wish they would tell us.

   john


From nomcom-chair@ietf.org  Wed Sep  5 17:07:58 2012
Return-Path: <nomcom-chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A7B21F8703 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 17:07:58 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JdVoH02HsLlA for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 17:07:58 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4182621F86B7 for <ietf@ietf.org>; Wed,  5 Sep 2012 17:07:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: NomCom Chair <nomcom-chair@ietf.org>
To: ietf@ietf.org
Subject: NomCom 2012-2013: Call for Nomination and Feedback
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120906000758.12304.41648.idtracker@ietfa.amsl.com>
Date: Wed, 05 Sep 2012 17:07:58 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2012 00:07:58 -0000

This is a reminder that the 2012-2013 Nominating Committee (NomCom) =

is seeking nominations from now until September 24, 2012 . =


Additionally, this is an announcement that the NomCom is seeking
feedback on individuals who have accepted nominations for IETF
leadership positions. As we are following the advice of RFC 5680, the list
of individuals who have agreed to be considered for various positions can
be found on the NomCom Community Feedback Tool:

https://www.ietf.org/group/nomcom/2012/input

Within the coming weeks, we will be updating the list of individuals we
are considering for each position as more individuals accept nominations.
All feedback provided to the NomCom about these individuals is kept
strictly confidential (as per RFC 3777). Your honest
feedback is very important to the NomCom process.

The open positions being considered by this year's NomCom can be found
at the end of this email or on the NomCom 2012-2013 website: =


https://www.ietf.org/group/nomcom/2012/

Nominations may be made by selecting the Nominate link at the top of
the NomCom 2012-2013 website or by visiting the following URL: =


https://www.ietf.org/group/nomcom/2012/nominate

Note that nominations made using the web tool require an ietf.org (i.e.,
datatracker) account. You can create an ietf.org account by visiting the
following URL:

https://datatracker.ietf.org/accounts/create/

Nominations may also be made by email to nomcom12@ietf.org.
If you do so, please include the word "Nominate" in the Subject and
indicate in the email who is being nominated, their email address (to
confirm acceptance of the nomination), and the position for which you
are making the nomination. If you wish to nominate someone via email
for more than one position, please use separate emails to do so.

Self nomination is welcome.

NomCom 2012-2013 will follow the policy for "Open Disclosure of Willing
Nominees" described in RFC 5680.  As stated in RFC 5680: "The list of
nominees willing to be considered for positions under review in the
current NomCom cycle is not confidential". Willing Nominees for each
position will be publicly listed.

With the exception of publicly listing willing nominees, the
confidentiality requirements of RFC 3777 remain in effect.  All
feedback and NomCom deliberations will remain confidential and
will not be disclosed.

In order to ensure time to collect sufficient community feedback about
each of the willing nominees, nominations must be received by the =

NomCom on or before September 24, 2012.

The NomCom appoints individuals to fill the open slots on the
IAOC, the IAB, and the IESG. This year, the NomCom willing be filling the
positions currently held by the following individuals, whose terms expire
in March 2013:

IAOC:
--------
Dave Crocker

IAB:
--------
Alissa Cooper
Joel Halpern
David Kessens
Danny McPherson
Jon Peterson
Dave Thaler

IESG:
--------
Russ Housley  (IETF Chair)
Pete Resnick  (Applications Area)
Ralph Droms  (Internet Area)
Ronald Bonica  (Operations and Management Area)
Robert Sparks  (Real-Time Applications and Infrastructure Area)
Adrian Farrel  (Routing Area)
Stephen Farrell  (Security Area)
Wesley Eddy  (Transport Area)

In addition to nominations, the Nominating Committee is actively
seeking community input on the jobs that need to be filled.  We have
received the job descriptions from the IAB, IESG, and IAOC and they can =

be found at:

https://www.ietf.org/group/nomcom/2012/iaoc-requirements
https://www.ietf.org/group/nomcom/2012/iab-requirements
https://www.ietf.org/group/nomcom/2012/chair-requirements
https://www.ietf.org/group/nomcom/2012/iesg-requirements

However, we also need the community's views and input on the jobs
within each organization. If you have ideas on job responsibilities
(more, less, different), please let us know.  Please send suggestions
and feedback to nomcom12@ietf.org.

Thank you for your help in identifying qualified nominees, and in providing =

feedback about individuals we are considering for IETF leadership positions.

Matt Lepinski
nomcom-chair@ietf.org

From vesely@tana.it  Thu Sep  6 10:06:06 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD8421F870E for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 10:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.595
X-Spam-Level: 
X-Spam-Status: No, score=-4.595 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyWHT1HZIFj9 for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 10:06:05 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id D8B2621F86A8 for <ietf@ietf.org>; Thu,  6 Sep 2012 10:06:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1346951161; bh=cSDK+Lfh242QF66Amz7MET5tL1kVr9FzUvpZDjjheOY=; l=1895; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=HFnKzcsIXakDzGsttk5+0K53DZ/S+nb99kgiAEUIGEea9niQq/T2cLoGoPaikCw/n UfmsFl+6iLALgwkKGf62AHvZhIZFYnBclFHxltY3KNtJxpIfbL6VIB25F3sX6u+EfE j4VsqUrP6HGkNQd4zxIRnblBkO+QZMsLhz4SC9eY=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Thu, 06 Sep 2012 19:06:01 +0200 id 00000000005DC04A.000000005048D7F9.00004675
Message-ID: <5048D7F8.2030906@tana.it>
Date: Thu, 06 Sep 2012 19:06:00 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft	from	the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504777F4.9000707@gmail.com> <6.2.5.6.2.20120905104856.0ad916a8@resistor.net> <0901BE7939A76E7CA259D178@JcK-HP8200.jck.com>
In-Reply-To: <0901BE7939A76E7CA259D178@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2012 17:06:06 -0000

On Wed 05/Sep/2012 21:59:56 +0200 John C Klensin wrote:
> --On Wednesday, September 05, 2012 11:02 -0700 SM <sm@resistor.net> wrote:
>> At 09:04 05-09-2012, Brian E Carpenter wrote:
>>> That's an interesting but not very informative statement.
>> 
>> http://www.ietf.org/mail-archive/web/ietf/current/msg71391.html
> 
> Of course, there is a case to be made that, if we had a more
> sophisticated posting system that enforced the few rules we
> already have, it would not have been accepted and posted in the
> first place.  Individual drafts are supposed to be title
> draft-OneOfTheAuthorNames-foo-bar-NN.  This one didn't meet that
> rule.

The I-D /was/ named after one of the author names.  Although expired,
http://tools.ietf.org/html/draft-ordogh-spam-reporting-using-imap-kleansed
is still accessible.

> From the standpoint of those rules/conventions about naming at
> least, it is as if I posted something as draft-moonesamy-foobar-00
> or draft-carpenter-barfoo-00 in the hope that would get extra
> attention.

I removed much more than I added, so putting my name would have been
overly selfish.

> That said, the author in this particular case could presumably have
> posted draft-vesely-spam-reporting-using-imap-kleansed-00 and then
> persuaded the Secretariat that it replaced 
> draft-ordogh-spam-reporting-using-imap-kleansed-00, thereby causing
> the latter to be removed from the _active_ I-D repository and moved
> off to the historical I-D archive.

That maneuver sounds more contrived than what I did.  I thought about
posting a new version with null content, or possibly with tombstone
text, but that would still have left version 00 in place.

In order to invalidate an archived version, we'd need a process
mechanically similar to rfc-editor's "Errata".  If visually winsome,
Errata's content could then be rendered the new way as well.


From iad@ietf.org  Thu Sep  6 12:11:32 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFEB021F8786; Thu,  6 Sep 2012 12:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xrqp38wZq9AI; Thu,  6 Sep 2012 12:11:32 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 778E921F8769; Thu,  6 Sep 2012 12:11:32 -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: IETF 95 Date Change Proposal - Round 2
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120906191132.22712.66702.idtracker@ietfa.amsl.com>
Date: Thu, 06 Sep 2012 12:11:32 -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: Thu, 06 Sep 2012 19:11:33 -0000

All


The IAOC is seeking community feedback on a proposed date change for IETF 95
originally scheduled for 27 March to 1 April 2016.

After considering community feedback on a proposed change to 20 - 25 March
2016, the IAOC is proposing 3 - 8 April 2016 to avoid the impact on travel =
and
attendance during the 20 - 25 March period.

Comments appreciated to ietf@ietf.org by 20 September 2012.

Ray Pelletier
IETF Administrative Director

From iad@ietf.org  Thu Sep  6 12:15:52 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1B2921F877A; Thu,  6 Sep 2012 12:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3+Ai6ZAXpwrt; Thu,  6 Sep 2012 12:15:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 440C921F8775; Thu,  6 Sep 2012 12:15:52 -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: Proposed IETF Meeting Calendar 2018 - 2022
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120906191552.11119.48553.idtracker@ietfa.amsl.com>
Date: Thu, 06 Sep 2012 12:15:52 -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: Thu, 06 Sep 2012 19:15:52 -0000

All;

Below are suggested Meeting dates for 2018 - 2022, IETF's 101 - 115.

The IAOC is soliciting the community's feedback before adopting.  =


Comments appreciated to ietf@ietf.org by 20 September 2012.

Ray

2018
IETF 101		18-23 March 2018
IETF 102		22-27 July 2018
IETF 103		4 - 9 November 2018

2019
IETF 104		24 - 29 March 2019
IETF 105		21 - 26 July 2019
IETF 106		17 - 22 November 2019

2020
IETF 107		22 - 27 March 2020
IETF 108		26 - 31 July 2020
IETF 109		15 - 20 November 2020

2021
IETF 110		21 - 26 March 2021
IETF 111		25 - 30 July 2021
IETF 112		7 - 12 November 2021

2022
IETF 113		20 - 25 March 2022
IETF 114		24 - 29 July 2022
IETF 115		6 - 11 November 2022

From jmpolk@cisco.com  Thu Sep  6 12:22:09 2012
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6617721F8731; Thu,  6 Sep 2012 12:22: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQijdifidTJn; Thu,  6 Sep 2012 12:22:09 -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 ED51921F86F1; Thu,  6 Sep 2012 12:22:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1133; q=dns/txt; s=iport; t=1346959329; x=1348168929; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=+nliW5W1oqfw1nGYKVRXaXAuH19I9KpA9F4Tmm6yBzg=; b=ZMwt66ut1EEBxNVv0I1coZTulFFZm6dNHGzuMPJugjCTT1m4O4VhOide TISu2o8nhrDRQv0WpbVJN+e8Mo8sEZkDVzUKQ270VeQ3ABjlgjB/PCzoF 1xaIVLsgVmoizJQ+zcXTTpj0sHgNZA6EeAD0Zk+32a1qXIOakSyiVOJGA 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjQFADf3SFCrRDoI/2dsb2JhbABFhUC2A4EHgiABAQEEEgElAj8QBwQYHhAZPgYTFA6HbZsloDCLEYZFA4hQmz+BZ4MB
X-IronPort-AV: E=Sophos;i="4.80,380,1344211200"; d="scan'208";a="54833326"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 06 Sep 2012 19:22:08 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8715.cisco.com [10.99.80.22]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q86JM7Cq020778; Thu, 6 Sep 2012 19:22:08 GMT
Message-Id: <201209061922.q86JM7Cq020778@mtv-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 06 Sep 2012 14:22:06 -0500
To: IETF Administrative Director <iad@ietf.org>
From: James Polk <jmpolk@cisco.com>
Subject: Re: Proposed IETF Meeting Calendar 2018 - 2022
In-Reply-To: <20120906191552.11119.48553.idtracker@ietfa.amsl.com>
References: <20120906191552.11119.48553.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iesg@ietf.org, iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Sep 2012 19:22:09 -0000

IETF 106 seems a bit late in November. Are we boxed in by other SDO 
meetings, or is this by our own choice?

James

At 02:15 PM 9/6/2012, IETF Administrative Director wrote:
>All;
>
>Below are suggested Meeting dates for 2018 - 2022, IETF's 101 - 115.
>
>The IAOC is soliciting the community's feedback before adopting.
>
>Comments appreciated to ietf@ietf.org by 20 September 2012.
>
>Ray
>
>2018
>IETF 101                18-23 March 2018
>IETF 102                22-27 July 2018
>IETF 103                4 - 9 November 2018
>
>2019
>IETF 104                24 - 29 March 2019
>IETF 105                21 - 26 July 2019
>IETF 106                17 - 22 November 2019
>
>2020
>IETF 107                22 - 27 March 2020
>IETF 108                26 - 31 July 2020
>IETF 109                15 - 20 November 2020
>
>2021
>IETF 110                21 - 26 March 2021
>IETF 111                25 - 30 July 2021
>IETF 112                7 - 12 November 2021
>
>2022
>IETF 113                20 - 25 March 2022
>IETF 114                24 - 29 July 2022
>IETF 115                6 - 11 November 2022


From presnick@qualcomm.com  Thu Sep  6 13:35:30 2012
Return-Path: <presnick@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 AE71421F8780; Thu,  6 Sep 2012 13:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level: 
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wBS-X6t0IerZ; Thu,  6 Sep 2012 13:35:27 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id BED0221F8762; Thu,  6 Sep 2012 13:35:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1346963727; x=1378499727; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; bh=cfN13Vt/O8H1dlyPwoaiKs90c9/ET1O9n4qb14sw8j8=; b=A/zl7BYxJfN9licP9u4k823PhTVsmx6XRabeKemmUhbpDabHj9zgj3ww mwsZrEUQ2rjPrGuMfSlx51zkN01UE5zi+HT4UJiBSIdtctt/dZWq5uqnT CPGeX4cDXvnuhMRDSphW9bNuOUJU/Nm6YLpWe1Bi4PZnTCpxs2CEXLmuI M=;
X-IronPort-AV: E=McAfee;i="5400,1158,6827"; a="231482113"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine02.qualcomm.com with ESMTP; 06 Sep 2012 13:35:26 -0700
X-IronPort-AV: E=Sophos;i="4.80,380,1344236400"; d="scan'208";a="296075945"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Sep 2012 13:35:26 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc04.na.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.1; Thu, 6 Sep 2012 13:35:26 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.1; Thu, 6 Sep 2012 13:35:26 -0700
Message-ID: <5049090C.6000805@qualcomm.com>
Date: Thu, 6 Sep 2012 15:35:24 -0500
From: Pete Resnick <presnick@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: Stephan Wenger <stewe@stewe.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <CC6CCC68.8B24D%stewe@stewe.org>
In-Reply-To: <CC6CCC68.8B24D%stewe@stewe.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2012 20:35:30 -0000

On 9/5/12 1:01 PM, Stephan Wenger wrote:

> I support this statement, with the additions suggested by Sam Hartman,
> John Klensin, and (most importantly) Brian Carpenter.
> In addition, I would suggest adding clarifying text to the extent that
> I-Ds will remain to be stored in non publicly accessible form, unless
> removal is required by a court order.
>    

I must say, I find this a very strange thing to say. The original 
statement was "we will not remove anything from the archive unless 
ordered to by duly authorized court". Sam, John, Brian, and others have 
basically said, "No, we do not want that to be the policy. We want the 
IESG to give itself latitude to remove things from the archive for all 
sorts of other reasons." These aren't "additions"; they are a complete 
reversal of what we originally proposed. (Which, BTW, is fine. That's 
why we put these things out for review.) So either you do *not* support 
the statement and prefer the kinds of things that Sam, John, Brian, and 
others have suggested, or you *do* support the statement and do *not* 
support these other positions.

Speaking strictly for myself, I've found this conversation extremely 
helpful. The IESG's initial thought on this matter was that the bar for 
removing things from the archive ought to be set as high as we could get 
it so as to avoid all sorts of silly requests and DoS attacks (and, at 
least in my mind, so that the legal questions were near nil: unless an 
appropriate court forced us to, our policy was "leave it in there"). All 
of the exceptions that people are now suggesting are very interesting, 
but also bring up lots of legal questions. I'm not sure I like the idea 
of making my job harder, but I guess that's why you pay us the big bucks.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From narten@us.ibm.com  Thu Sep  6 21:53:40 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83B0E21F855E for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 21:53:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.299
X-Spam-Level: 
X-Spam-Status: No, score=-108.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id svQHNCCutpKa for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 21:53:40 -0700 (PDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id DBBCB21F853F for <ietf@ietf.org>; Thu,  6 Sep 2012 21:53:39 -0700 (PDT)
Received: from /spool/local by e33.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, 6 Sep 2012 22:53:38 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 6 Sep 2012 22:53:36 -0600
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id DDA5BC40003 for <ietf@ietf.org>; Thu,  6 Sep 2012 22:53:03 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q874r5aS221424 for <ietf@ietf.org>; Thu, 6 Sep 2012 22:53:05 -0600
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q874sW57003540 for <ietf@ietf.org>; Thu, 6 Sep 2012 22:54:32 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q874sWQ2003516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 6 Sep 2012 22:54:32 -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 q874r4K4028055 for <ietf@ietf.org>; Fri, 7 Sep 2012 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q874r3DY028041 for ietf@ietf.org; Fri, 7 Sep 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201209070453.q874r3DY028041@rotala.raleigh.ibm.com>
Date: Fri, 07 Sep 2012 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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12090704-2398-0000-0000-00000A62D7B0
X-IBM-ISS-SpamDetectors: 
X-IBM-ISS-DetailInfo: BY=3.00000294; HX=3.00000196; KW=3.00000007; PH=3.00000001; SC=3.00000007; SDB=6.00171971; UDB=6.00038999; UTC=2012-09-07 04:53:37
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Sep 2012 04:53:40 -0000

Total of 66 messages in the last 7 days.
 
script run at: Fri Sep  7 00:53:03 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.58% |    5 | 12.30% |    58531 | chris.hall@highwayman.com
  6.06% |    4 |  5.79% |    27548 | john-ietf@jck.com
  6.06% |    4 |  5.37% |    25561 | sm@resistor.net
  4.55% |    3 |  5.12% |    24348 | ted.ietf@gmail.com
  4.55% |    3 |  4.11% |    19554 | vesely@tana.it
  4.55% |    3 |  4.01% |    19097 | johnl@taugh.com
  4.55% |    3 |  3.80% |    18102 | chair@ietf.org
  4.55% |    3 |  3.32% |    15818 | dhc@dcrocker.net
  3.03% |    2 |  3.43% |    16315 | eric.gray@ericsson.com
  3.03% |    2 |  3.21% |    15264 | adrian@olddog.co.uk
  3.03% |    2 |  3.16% |    15019 | ietf@thomasclausen.org
  3.03% |    2 |  2.83% |    13476 | brian.e.carpenter@gmail.com
  3.03% |    2 |  2.68% |    12739 | vinayakh@gmail.com
  3.03% |    2 |  2.36% |    11217 | paul.hoffman@vpnc.org
  3.03% |    2 |  2.00% |     9524 | iad@ietf.org
  1.52% |    1 |  3.06% |    14546 | lars@netapp.com
  1.52% |    1 |  2.02% |     9617 | abdussalambaryun@gmail.com
  1.52% |    1 |  1.93% |     9188 | chris.dearlove@baesystems.com
  1.52% |    1 |  1.74% |     8258 | nomcom-chair@ietf.org
  1.52% |    1 |  1.67% |     7960 | stewe@stewe.org
  1.52% |    1 |  1.59% |     7582 | tglassey@earthlink.net
  1.52% |    1 |  1.57% |     7487 | presnick@qualcomm.com
  1.52% |    1 |  1.57% |     7457 | turners@ieca.com
  1.52% |    1 |  1.54% |     7332 | jakob.heitz@ericsson.com
  1.52% |    1 |  1.47% |     7002 | rschrage@schrageconsult.net
  1.52% |    1 |  1.47% |     7000 | lear@cisco.com
  1.52% |    1 |  1.46% |     6938 | narten@us.ibm.com
  1.52% |    1 |  1.45% |     6923 | scott@kitterman.com
  1.52% |    1 |  1.44% |     6871 | marka@isc.org
  1.52% |    1 |  1.37% |     6533 | sob@sobco.com
  1.52% |    1 |  1.35% |     6411 | housley@vigilsec.com
  1.52% |    1 |  1.33% |     6317 | jmpolk@cisco.com
  1.52% |    1 |  1.33% |     6311 | peter@akayla.com
  1.52% |    1 |  1.32% |     6285 | conte@isoc.org
  1.52% |    1 |  1.32% |     6276 | joelja@bogus.com
  1.52% |    1 |  1.26% |     5977 | hartmans-ietf@mit.edu
  1.52% |    1 |  1.20% |     5696 | jari.arkko@piuha.net
  1.52% |    1 |  1.09% |     5166 | dwm@xpasc.com
  1.52% |    1 |  0.97% |     4593 | randy@psg.com
--------+------+--------+----------+------------------------
100.00% |   66 |100.00% |   475839 | Total


From randy@psg.com  Thu Sep  6 23:34:22 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D7A921E8086 for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 23:34: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qpStiob5-BPj for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 23:34:22 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 27E3121E8050 for <ietf@ietf.org>; Thu,  6 Sep 2012 23:34:22 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1T9s8y-000LBE-Kf; Fri, 07 Sep 2012 06:34:21 +0000
Date: Fri, 07 Sep 2012 15:35:24 +0900
Message-ID: <m2ligm732r.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
In-Reply-To: <5049090C.6000805@qualcomm.com>
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Sep 2012 06:34:22 -0000

> The IESG's initial thought on this matter was that the bar for
> removing things from the archive ought to be set as high as we could
> get it so as to avoid all sorts of silly requests and DoS attacks
> (and, at least in my mind, so that the legal questions were near nil:
> unless an appropriate court forced us to, our policy was "leave it in
> there").

please stick to it.  we have enough complexity creation already.  aside
from at&t and verizon illegally giving all our packets to the nsa, the
high bar is the best and simplest.

randy

From lear@cisco.com  Thu Sep  6 23:49:57 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45E1D21E805D for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 23:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.724
X-Spam-Level: 
X-Spam-Status: No, score=-110.724 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6yVZfh-O9eE for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 23:49:56 -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 5DB0521E8034 for <ietf@ietf.org>; Thu,  6 Sep 2012 23:49:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1649; q=dns/txt; s=iport; t=1347000596; x=1348210196; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=FEK3pXkPmcHEEOJfiV6SDk9ZT7YdROWWv1pQ/a+BlM4=; b=SQAoy+WfBjsKvtqe3O1ykfoHYP2by2YTpu6OMmThRP3Awk7MFbM0NLcE AvJxkMoeAVEqiGoEyFMD0yjEq6Ux2W9oxaSviP3w7h9zFmjWve9OzWr2u vOrvxU8f4i5ja84vnRp/PooEPrwuvgkoGJ793iEszYMTMCVeekourYNgE 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAJOYSVCQ/khL/2dsb2JhbABFhge1S4EHgiABAQEDARIBEFUBBQsLGAICBRYLAgIJAwIBAgFFBg0BBwEBHodoBptYjRmTJIEhjw+BEgOLNIomhkuHaoFngmU
X-IronPort-AV: E=Sophos;i="4.80,384,1344211200";  d="scan'208";a="7862542"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 07 Sep 2012 06:49:55 +0000
Received: from dhcp-10-55-80-235.cisco.com (dhcp-10-55-80-235.cisco.com [10.55.80.235]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q876nsBx030499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Sep 2012 06:49:54 GMT
Message-ID: <50499912.9050806@cisco.com>
Date: Fri, 07 Sep 2012 08:49:54 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com>
In-Reply-To: <m2ligm732r.wl%randy@psg.com>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, John C Klensin <klensin@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: Fri, 07 Sep 2012 06:49:57 -0000

Randy,
On 9/7/12 8:35 AM, Randy Bush wrote:
>> The IESG's initial thought on this matter was that the bar for
>> removing things from the archive ought to be set as high as we could
>> get it so as to avoid all sorts of silly requests and DoS attacks
>> (and, at least in my mind, so that the legal questions were near nil:
>> unless an appropriate court forced us to, our policy was "leave it in
>> there").
> please stick to it.  we have enough complexity creation already.  aside
> from at&t and verizon illegally giving all our packets to the nsa, the
> high bar is the best and simplest.

I agree with your point about complexity and "sticking to it".  I
recommend a small change to accommodate most of what has been discussed.

OLD:
> An I-D will only be removed from the public I-D archive in compliance
> with a duly authorized court order.  If possible, a removed I-D will be
> replaced with a tombstone file that describes the reason that the I-D
> was removed from the public I-D archive.

NEW:

> An I-D MAY be removed from the public I-D archive in compliance
> with a competent legal demand.  If possible, a removed I-D will be
> replaced with a tombstone file that describes the reason that the I-D
> was removed from the public I-D archive.

This leaves sufficient flexibility for the IESG to decide when a legal
demand requires the removal and when it's bogus, but otherwise leaves
the bar high.  I would suggest that Jorge review the above text for
appropriateness.

I'll also point out that if people start to game us for illegal content,
the IESG has the ability to update the policy.

Eliot

From randy@psg.com  Thu Sep  6 23:53:11 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968A121E8085 for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 23:53: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thyiXKXtvUqT for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 23:53:11 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 3519421E8034 for <ietf@ietf.org>; Thu,  6 Sep 2012 23:53:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1T9sR9-000LDi-Dt; Fri, 07 Sep 2012 06:53:07 +0000
Date: Fri, 07 Sep 2012 15:54:11 +0900
Message-ID: <m2k3w6727g.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Eliot Lear <lear@cisco.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <50499912.9050806@cisco.com>
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: Pete Resnick <presnick@qualcomm.com>, John C Klensin <klensin@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: Fri, 07 Sep 2012 06:53:11 -0000

>> An I-D MAY be removed from the public I-D archive in compliance
>> with a competent legal demand.
> This leaves sufficient flexibility for the IESG to decide when a legal
> demand requires the removal and when it's bogus

so the iesg will now spend their spring retreat in law school?  we have
a test for competent legal demand.  it is called a court order.

randy

From lear@cisco.com  Fri Sep  7 00:00:39 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12B4621F84B9 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 00:00:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.71
X-Spam-Level: 
X-Spam-Status: No, score=-110.71 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lt+LDWUXhOTL for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 00:00:38 -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 3B76E21F84B2 for <ietf@ietf.org>; Fri,  7 Sep 2012 00:00:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=479; q=dns/txt; s=iport; t=1347001238; x=1348210838; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=NtM+2z2cyT1cwY6959wiZ81dbX99bQr8UrdUwRqKmn8=; b=VpDkhlL+C/HjH8pAEJ35tUfq5DKmHyWbJLeBUE7KS7DgJqP5TAkk/eXa 43toQhFutqTScuadHg7zY2U8qC+Us4G7TCad2q/9DKBsZoolO3WGksCVf Z/Rmi2ZMtp9s5jeDx+hASpk1TYmlWMxhs2Of5CfZ3cloZf7mrmvIZO+y+ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlQJAN+aSVCQ/khL/2dsb2JhbABFhge0PAQEgQeBB4IgAQEBAwESARBVBgsLGgIFFgsCAgkDAgECAUUGAQwIAQEeh2gGm1eNGZMogSGPD4ESA5VajjWBZ4Jl
X-IronPort-AV: E=Sophos;i="4.80,384,1344211200";  d="scan'208";a="7862778"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-3.cisco.com with ESMTP; 07 Sep 2012 07:00:37 +0000
Received: from dhcp-10-55-80-235.cisco.com (dhcp-10-55-80-235.cisco.com [10.55.80.235]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q8770af7032600 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Sep 2012 07:00:37 GMT
Message-ID: <50499B94.8080004@cisco.com>
Date: Fri, 07 Sep 2012 09:00:36 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com> <m2k3w6727g.wl%randy@psg.com>
In-Reply-To: <m2k3w6727g.wl%randy@psg.com>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 07:00:39 -0000

Randy,

> so the iesg will now spend their spring retreat in law school? we have
> a test for competent legal demand. it is called a court order.

In the case of DMCA, if you wait for a court order, you can lose your
liability shield, which has been the point that Sam and others have
raised.  There may be times when the IETF is willing to do that (had the
IETF been hosting the TZ database, perhaps it would have done so), but
it should be done consciously.

Eliot

From randy@psg.com  Fri Sep  7 00:15:35 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D80821E809C for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 00:15:35 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZakqEpLcKEgK for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 00:15:34 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id D09AE21E808A for <ietf@ietf.org>; Fri,  7 Sep 2012 00:15:34 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1T9smr-000LIn-Gy; Fri, 07 Sep 2012 07:15:33 +0000
Date: Fri, 07 Sep 2012 16:16:37 +0900
Message-ID: <m2fw6u7162.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Eliot Lear <lear@cisco.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <50499B94.8080004@cisco.com>
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com> <m2k3w6727g.wl%randy@psg.com> <50499B94.8080004@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF 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, 07 Sep 2012 07:15:35 -0000

> In the case of DMCA

i am not competent to speak to circumstances surrounding a dmca.  i am
glad you and all the other engineers here are.  sure saves the ietf
lawyer a lot of work.

randy

From ned+ietf@mauve.mrochek.com  Fri Sep  7 00:44:02 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B892421F86E3 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 00:44: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8t4JCelTfFJZ for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 00:44:01 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id B43CC21F86FC for <ietf@ietf.org>; Fri,  7 Sep 2012 00:44:01 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJYEED79I80082WT@mauve.mrochek.com> for ietf@ietf.org; Fri, 7 Sep 2012 00:38:55 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJFFFOH4280006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 7 Sep 2012 00:38:50 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OJYEEBEJDE0006TF@mauve.mrochek.com>
Date: Fri, 07 Sep 2012 00:29:28 -0700 (PDT)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
In-reply-to: "Your message dated Fri, 07 Sep 2012 16:16:37 +0900" <m2fw6u7162.wl%randy@psg.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com> <m2k3w6727g.wl%randy@psg.com> <50499B94.8080004@cisco.com> <m2fw6u7162.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
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: Fri, 07 Sep 2012 07:44:02 -0000

> > In the case of DMCA

> i am not competent to speak to circumstances surrounding a dmca.  i am
> glad you and all the other engineers here are.  sure saves the ietf
> lawyer a lot of work.

Bingo. And even if we were competent to assess this stuff - which we most
assuredly are not - any notion that a specific policy can be drafted that would
cover all the eventualities that could arise in the context of a DMCA notice is
preposterous on its face.

Anyone who has looked at even a few DMCA situations knows they range from
looneys with no grounds and no resources to entirely legitimate cases of gross
infringement to what amounts to a SLAPP suit.

If and when this happens the IETF will have to deal with the situation as it
presents, hopefully assisted by competent legal counsel.

The only question that need concern us at present is whether or not the
stated policy gives the IESG the necessary flexibility. It seems to me
that it does.

				Ned

From lear@cisco.com  Fri Sep  7 01:21:50 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9BC921F87A9 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 01:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.699
X-Spam-Level: 
X-Spam-Status: No, score=-110.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FfAhDulTIJvu for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 01:21:50 -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 8AB7121F87A7 for <ietf@ietf.org>; Fri,  7 Sep 2012 01:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=466; q=dns/txt; s=iport; t=1347006109; x=1348215709; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=qY452H6Y2w84uzqD1VV3mRTnNKEpcl5rE7Uy0gomoPw=; b=YoLWzwKTQLfeaweyHB7s6O4QwYxyTkmFL5X93Q5kwEdErIi61L/mcZqJ OqkJCZd9dsVECSvX0UIvFxgzwlDkoVvE8wIlWk9vsrBP/CEsYUE09kqJL E0LlXXFwXNMyuQCf4KpmoQCpviMZHEvM57/EKALcN45NFD9k7kLxQcNjp g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlQJACeuSVCQ/khM/2dsb2JhbABFhge0PAQEgQeBB4IgAQEBAwESARBVAQULCxoCBRYLAgIJAwIBAgFFBg0BBwEBHodoBptQjRmTMYEhjw+BEgOVWo41gWeCZQ
X-IronPort-AV: E=Sophos;i="4.80,384,1344211200";  d="scan'208";a="7872060"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 07 Sep 2012 08:21:45 +0000
Received: from dhcp-10-55-80-235.cisco.com (dhcp-10-55-80-235.cisco.com [10.55.80.235]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q878Li5W020260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Sep 2012 08:21:45 GMT
Message-ID: <5049AE98.1030405@cisco.com>
Date: Fri, 07 Sep 2012 10:21:44 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com> <m2k3w6727g.wl%randy@psg.com> <50499B94.8080004@cisco.com> <m2fw6u7162.wl%randy@psg.com> <01OJYEEBEJDE0006TF@mauve.mrochek.com>
In-Reply-To: <01OJYEEBEJDE0006TF@mauve.mrochek.com>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Fri, 07 Sep 2012 08:21:51 -0000

Ned,

We are venturing into an area of rabid agreement on the premise but
disagreement on the conclusion, which I find astonishing.

On 9/7/12 9:29 AM, Ned Freed wrote:


> The only question that need concern us at present is whether or not the
> stated policy gives the IESG the necessary flexibility. It seems to me
> that it does.		

Glad you think so, but then please enlighten the rest of us about how
the text provides this flexibility.

Eliot



From stbryant@cisco.com  Fri Sep  7 02:33:46 2012
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 6D7B921F86C6 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 02:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level: 
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RYacqyjAUWqB for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 02:33: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 93F2021F85A3 for <ietf@ietf.org>; Fri,  7 Sep 2012 02:33:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=287; q=dns/txt; s=iport; t=1347010425; x=1348220025; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=SPM5dWE9eL4oLLtQa7pXcGznOa4SAlkx5IZKoChyUmU=; b=dMRJtoEvBsOeNLzZm8udou9PZCoAq2FxW+VScEndlKHj0DUblpkSZfIx 2uNVvEX/v2m5YJFibbWuW8hAcEFF/5Ibl3U+/UYtJxc4cApHGorrZPRhT NpehFpkPriY5lF1nMX53iVDnigBaAkdsSXooQiHt+DyfMPtGzzOvWY8Zd M=;
X-IronPort-AV: E=Sophos;i="4.80,384,1344211200"; d="scan'208";a="76527730"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 07 Sep 2012 09:33:41 +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 q879Xehh015611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Sep 2012 09:33:40 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q879XahG009492; Fri, 7 Sep 2012 10:33:37 +0100 (BST)
Message-ID: <5049BF70.7050103@cisco.com>
Date: Fri, 07 Sep 2012 10:33:36 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com>
In-Reply-To: <50499912.9050806@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, John C Klensin <klensin@jck.com>, 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: Fri, 07 Sep 2012 09:33:46 -0000

On 07/09/2012 07:49, Eliot Lear wrote:
> An I-D will only be removed from the public I-D archive in compliance
> >with a duly authorized court order.
Would

"An I-D will only be removed from the public I-D archive if legally
required to do so."


fix the ambiguity?

Stewart



From lear@cisco.com  Fri Sep  7 02:42:30 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC25921F84DA for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 02:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.69
X-Spam-Level: 
X-Spam-Status: No, score=-110.69 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L1snP3c9BOLA for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 02:42:28 -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 5E75B21F846D for <ietf@ietf.org>; Fri,  7 Sep 2012 02:42:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=495; q=dns/txt; s=iport; t=1347010946; x=1348220546; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=Gnl9pVwNJFkMAGshVT9lNEdtUrtUVydRYZxEspABogk=; b=Yhx38/+cqmc83dCTXTXIBpR+25KrzK89yJO9m9fWiiHajh/Or4yFv3oe VvM/c3w2w5erWC6p7xGSbpl9DD/jfDmB0MJeCrvJJq13pTWWQTleqqIH1 EyOUB/9VQ/2Sa+xdEFwCcqmdZFHl8iKBQ5AA3lIJjJAvssOEoGkA+LHAY M=;
X-IronPort-AV: E=Sophos;i="4.80,384,1344211200";  d="scan'208";a="7866085"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 07 Sep 2012 09:42:22 +0000
Received: from dhcp-10-55-80-235.cisco.com (dhcp-10-55-80-235.cisco.com [10.55.80.235]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q879gLNm017598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Sep 2012 09:42:21 GMT
Message-ID: <5049C17D.3080103@cisco.com>
Date: Fri, 07 Sep 2012 11:42:21 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: stbryant@cisco.com, IETF Discussion <ietf@ietf.org>, Jorge Contreras <cntreras@gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com> <5049BF70.7050103@cisco.com>
In-Reply-To: <5049BF70.7050103@cisco.com>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 09:42:30 -0000

On 9/7/12 11:33 AM, Stewart Bryant wrote:
> On 07/09/2012 07:49, Eliot Lear wrote:
>> An I-D will only be removed from the public I-D archive in compliance
>> >with a duly authorized court order.
> Would
>
> "An I-D will only be removed from the public I-D archive if legally
> required to do so."

That is where I was aiming, albeit with s/will/may/.  Again, I recommend
that Jorge review.  Nothing in this policy should REQUIRE the IESG to
act, or set that expectation.

Eliot

From abdussalambaryun@gmail.com  Fri Sep  7 03:01:06 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 309F121F8694; Fri,  7 Sep 2012 03:01:06 -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.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCFFO8XBtbro; Fri,  7 Sep 2012 03:01:05 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD8421F8745; Fri,  7 Sep 2012 03:01:05 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3212326vbb.31 for <multiple recipients>; Fri, 07 Sep 2012 03:00:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IgOsZPggSeiec8ICM23nwqLQugZbPhqqLZSlK6oQAAE=; b=zbeKlQE173sNLtnORF8BykDm+GtK7Ij0f1ILHSGWGlyvWVQLPJFxkBdRumVyLL4+Kx Fn10g2o8Dwp4cdagJxfdc0Gw+q5RLZmz4FqfjtqJkyIyFP0pNxlb5oQs+9YkFKkNURTU kq1FBAv/0BeeFvZjjFA5yNZ3Le2nmbbkWj9+mJSXRihRaT+dlc1+qdABny5yJ6RJtsuV Dkj19v88qkzmw/Cr2NQqONI/rFVQ20z5Gn+aClS7FqBuX/VhleXq7WAaOr8IaKcYmayE PJwid81B0Rn+4OsAkpN3/TcUFW8m8dcMUHK7iv0xgA0Q5ju+4KraQ95oYTsmENUNi47S C1jg==
MIME-Version: 1.0
Received: by 10.52.24.201 with SMTP id w9mr5157151vdf.125.1347012059283; Fri, 07 Sep 2012 03:00:59 -0700 (PDT)
Received: by 10.220.2.83 with HTTP; Fri, 7 Sep 2012 03:00:58 -0700 (PDT)
In-Reply-To: <20120906000602.6028.69834.idtracker@ietfa.amsl.com>
References: <20120906000602.6028.69834.idtracker@ietfa.amsl.com>
Date: Fri, 7 Sep 2012 12:00:58 +0200
Message-ID: <CADnDZ88JjZbd-6AJPVBZE3gy=_fJ7r55EE=y_Jx0m_vOMO2wwA@mail.gmail.com>
Subject: Re: NomCom 2012-2013: Call for Nomination and Feedback
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: nomcom12@ietf.org
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, 07 Sep 2012 10:01:06 -0000

On 9/6/12, NomCom Chair <nomcom-chair@ietf.org> wrote:
>
> However, we also need the community's views and input on the jobs
> within each organization. If you have ideas on job responsibilities
> (more, less, different), please let us know.  Please send suggestions
> and feedback to nomcom12@ietf.org.
Suggestion to assist; 1) the DA responsibility of "The DA is to select
the WG chair"
and 2) to assist the method of NomCom collection of feedback
information from community.
-------------------------------------------------------------------------------------------------------
My suggestion is to add a report/questionnare for comments on WGs
performance, as just to collect comment/feedback on WG progress from
only the community. Usually community feedback on WGs' progresses are
very important for the IETF, which a lack of progress maybe due to
chair or DA position, which I think is the most important issue in all
nominations vote decision. The feedback can be named the
community-WG-progress-report or ietf-participants-feedback-report,
which has many advantages.

In abstract the advantages are; firstly, the
community-WG-progress-report will be attached to an optional DA-report
that will be given to the new DA. The new DA will be able to decide
how to select/advise/follow-up-with the WGs chairs for the next year.
Secondly, the community-wg-progress-report will help NomCom12 to vote
on the nominated positions, if previous chairs or DAs are going for a
position as IESG or other.

I am not sure if we already have this community feedback about WG
progress. IMO, no IETF member can vote efficiently without information
or feedback from internet-community.

Best Regards
AB

>
> Thank you for your help in identifying qualified nominees, and in providing
>
> feedback about individuals we are considering for IETF leadership
> positions.
>
> Matt Lepinski
> nomcom-chair@ietf.org
>
>

From john-ietf@jck.com  Fri Sep  7 03:19:26 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B8E321F87C6 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 03:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.437
X-Spam-Level: 
X-Spam-Status: No, score=-102.437 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kp+ta+LoZace for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 03:19:25 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id AE07421F87C5 for <ietf@ietf.org>; Fri,  7 Sep 2012 03:19:25 -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 1T9vei-0002eH-LO; Fri, 07 Sep 2012 06:19:20 -0400
Date: Fri, 07 Sep 2012 06:19:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: stbryant@cisco.com, Eliot Lear <lear@cisco.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Message-ID: <24050C52480A9121E3C45EE9@JcK-HP8200.jck.com>
In-Reply-To: <5049BF70.7050103@cisco.com>
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com> <5049BF70.7050103@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: Pete Resnick <presnick@qualcomm.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, 07 Sep 2012 10:19:26 -0000

--On Friday, September 07, 2012 10:33 +0100 Stewart Bryant
<stbryant@cisco.com> wrote:

> On 07/09/2012 07:49, Eliot Lear wrote:
>> An I-D will only be removed from the public I-D archive in
>> compliance
>> > with a duly authorized court order.
> Would
> 
> "An I-D will only be removed from the public I-D archive if
> legally required to do so."

> fix the ambiguity?

IMO, probably, But ask Jorge.  Note, however, that this opens up
another ambiguity.   If a DMCA notice, or something like it from
another jurisdiction, is received, that may not be a legal
requirement to take something down, merely a request that
presents us with alternatives between compliance and assuming
liability for not doing so.  If this restated policy requires
ignoring such requests, that is a _big_ decision.  It is also,
IMO, a dangerous and unsustainable one if we are going to
continue to permit anyone to post anything as an I-D as long as
it meets format requirements.

I still believe that this is the wrong answer -- that the IESG
(or someone) has to have discretion to take something down with
a minimum of fuss if circumstances arise that this nit-picking
about language doesn't anticipate.   Example, which would
probably be covered by "legally required" but the next one might
not:  Suppose someone posted a blatant  example of child port as
part of an I-D.  The law in some jurisdictions require that such
material be taken down (and possibly some other actions taken)
the moment we become aware of it (if not sooner).  Want to
insist that the IESG wait for a court order when that court
order might come in the form of criminal charges with severe
penalties?  Want to wait after that, until there is a conviction
(hint: that could easily result, much earlier, in a court order
to seize and take down, not the particular I-D, but our servers).

An even better answer might be to figure out why we need to
maintain a public archive of expired documents.  As someone else
said, the ability to do diffs is a pretty weak reason.  Even if
that were important, we could solve a huge fraction of the
actual requirement by adopting a model of:

	 -- I-Ds are fully public until they expire (six months,
	when replaced, or, under still-unspecified conditions,
	earlier)
	
	 -- Expired I-Ds are kept online and public for an
	additional grace period of, say, three months.  That
	allows for easy diffs.  If six months are needed instead
	of three, so be it.
	
	  -- After that, they are available on individual
	request at the discretion of the Secretariat, in
	response to court orders (which give the Secretariat no
	discretion), etc.

For most purposes, that changes the "removal" question into an
"early expiration" one -- both "early expiration" from the main
I-D directories and "early expiration of the grace period".

Just my opinion.

    john




From john-ietf@jck.com  Fri Sep  7 03:35:50 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B244121F879B for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 03:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.155
X-Spam-Level: 
X-Spam-Status: No, score=-102.155 tagged_above=-999 required=5 tests=[AWL=-0.156, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7CD9hTND0qv for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 03:35:50 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 38F6421F8799 for <ietf@ietf.org>; Fri,  7 Sep 2012 03:35: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 1T9vud-0002ij-30; Fri, 07 Sep 2012 06:35:47 -0400
Date: Fri, 07 Sep 2012 06:35:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, Eliot Lear <lear@cisco.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <FB76E7184F192F0598D9D03C@JcK-HP8200.jck.com>
In-Reply-To: <m2k3w6727g.wl%randy@psg.com>
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com>	<m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com> <m2k3w6727g.wl%randy@psg.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Pete Resnick <presnick@qualcomm.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, 07 Sep 2012 10:35:50 -0000

--On Friday, September 07, 2012 15:54 +0900 Randy Bush
<randy@psg.com> wrote:

>>> An I-D MAY be removed from the public I-D archive in
>>> compliance with a competent legal demand.
>> This leaves sufficient flexibility for the IESG to decide
>> when a legal demand requires the removal and when it's bogus
> 
> so the iesg will now spend their spring retreat in law school?
> we have a test for competent legal demand.  it is called a
> court order.

If the IESG persists in drafting statements, even proposed ones,
that could expose the community to very large levels of
liability (see earlier comments by myself and others about DCMA
notices and assumption of liability as examples), then perhaps
such a spring retreat would be a good idea.

Sorry, but this is largely a problem of our own making.  For
years, our position was that I=Ds expired after six months and,
when they expired, they disappeared from any public repository
for which the IETF had direct responsibility.  If others wanted
to capture and keep copies forever, that just wasn't our
problem.  Indeed, it might be claimed that it violated our
rules, but we weren't obligate to enforce those rules and knew
that we couldn't.  If we had stayed with that as a policy, the
only thing we'd be discussing now was early expiration.  We
might not even be discussing that because it was widely assumed
that the IESG had the authority to expire a document for any
reason it thought sensible even though that authority was almost
never used (A Good Thing, IMO).

So now we have a public archive and the IESG feels a need to
make comprehensive policies about that public archive.  To avoid
making rules about situations we can't anticipate, we say "only
with a court order", which creates even more situations we
haven't anticipated.  Perhaps a spring retreat in law school or
better and less expensively, a spring retreat in which ADs and
selected other members of the community get to write thousands
of times on a public wall "I am not a lawyer; I will not pretend
to be a lawyer or even play one on television in the sight of
the IETF; even if I were a lawyer, that doesn't make me an
expert on copyright or patent law in multiple jurisdictions",  

:-(

   john


From daedulus@btconnect.com  Fri Sep  7 04:48:16 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0603221F8731 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 04:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m+yAQuy1mIBM; Fri,  7 Sep 2012 04:48:15 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id 6921721F872A; Fri,  7 Sep 2012 04:48:15 -0700 (PDT)
Received: from mail234-tx2-R.bigfish.com (10.9.14.245) by TX2EHSOBE012.bigfish.com (10.9.40.32) with Microsoft SMTP Server id 14.1.225.23; Fri, 7 Sep 2012 11:48:14 +0000
Received: from mail234-tx2 (localhost [127.0.0.1])	by mail234-tx2-R.bigfish.com (Postfix) with ESMTP id 398653800C2; Fri,  7 Sep 2012 11:48:14 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: PS-22(zz9371I542Mzz1202hzz1033IL8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah107ah1177h1179h1288h304l1155h)
Received: from mail234-tx2 (localhost.localdomain [127.0.0.1]) by mail234-tx2 (MessageSwitch) id 1347018492431578_7540; Fri,  7 Sep 2012 11:48:12 +0000 (UTC)
Received: from TX2EHSMHS033.bigfish.com (unknown [10.9.14.250])	by mail234-tx2.bigfish.com (Postfix) with ESMTP id 64DF2900049; Fri,  7 Sep 2012 11:48:12 +0000 (UTC)
Received: from AM2PRD0710HT004.eurprd07.prod.outlook.com (157.56.249.213) by TX2EHSMHS033.bigfish.com (10.9.99.133) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 7 Sep 2012 11:48:12 +0000
Received: from DBXPRD0410HT004.eurprd04.prod.outlook.com (157.56.252.149) by pod51017.outlook.com (10.255.165.39) with Microsoft SMTP Server (TLS) id 14.16.190.9; Fri, 7 Sep 2012 11:47:54 +0000
Message-ID: <05a801cd8ced$e8252a60$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: IETF Administrative Director <iad@ietf.org>
References: <20120906191552.11119.48553.idtracker@ietfa.amsl.com>
Subject: Re: Proposed IETF Meeting Calendar 2018 - 2022
Date: Fri, 7 Sep 2012 12:42:23 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.149]
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, 07 Sep 2012 11:48:16 -0000

We seem to have adopted a policy of making the summer meeting overlap
what is for me the start of school holidays, and a time to avoid
travelling.

I used to think of IETF54, IETF57 and IETF66 as the norm and anything
else as an aberration, but now it seems the reverse is true.

Incidentally, I notice that we are now staying well away from that other
holiday season, sometimes known in the Western world as 'Easter', which
seems prudent.

Tom Petch


----- Original Message -----
From: "IETF Administrative Director" <iad@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: <iaoc@ietf.org>; <iab@iab.org>; <ietf@ietf.org>;
<wgchairs@ietf.org>; <iesg@ietf.org>
Sent: Thursday, September 06, 2012 8:15 PM
Subject: Proposed IETF Meeting Calendar 2018 - 2022


All;

Below are suggested Meeting dates for 2018 - 2022, IETF's 101 - 115.

The IAOC is soliciting the community's feedback before adopting.

Comments appreciated to ietf@ietf.org by 20 September 2012.

Ray

2018
IETF 101 18-23 March 2018
IETF 102 22-27 July 2018
IETF 103 4 - 9 November 2018

2019
IETF 104 24 - 29 March 2019
IETF 105 21 - 26 July 2019
IETF 106 17 - 22 November 2019

2020
IETF 107 22 - 27 March 2020
IETF 108 26 - 31 July 2020
IETF 109 15 - 20 November 2020

2021
IETF 110 21 - 26 March 2021
IETF 111 25 - 30 July 2021
IETF 112 7 - 12 November 2021

2022
IETF 113 20 - 25 March 2022
IETF 114 24 - 29 July 2022
IETF 115 6 - 11 November 2022



From loa@pi.nu  Fri Sep  7 05:09:15 2012
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3893621F87BE for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 05:09: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LY+p-Q6b0k4; Fri,  7 Sep 2012 05:09:14 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 8837121F872A; Fri,  7 Sep 2012 05:09:14 -0700 (PDT)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 272F1514002; Fri,  7 Sep 2012 14:09:13 +0200 (CEST)
Message-ID: <5049E3E2.7090907@pi.nu>
Date: Fri, 07 Sep 2012 14:09:06 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>,  IETF Administrative Director <iad@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Proposed IETF Meeting Calendar 2018 - 2022
References: <20120906191552.11119.48553.idtracker@ietfa.amsl.com> <05a801cd8ced$e8252a60$4001a8c0@gateway.2wire.net>
In-Reply-To: <05a801cd8ced$e8252a60$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 12:09:15 -0000

Tom,

the overlap with school holidays might be true from some perspective,
but the two countries (Sweden and Philippines) I'm most familiar with
show that if there is a goal to avoid that it is not doable.
In Sweden there is school holidays from around June 10th and into
August. In the Philippines the school starts around June 10th.

/Loa



On 2012-09-07 13:42, t.p. wrote:
> We seem to have adopted a policy of making the summer meeting overlap
> what is for me the start of school holidays, and a time to avoid
> travelling.
>
> I used to think of IETF54, IETF57 and IETF66 as the norm and anything
> else as an aberration, but now it seems the reverse is true.
>
> Incidentally, I notice that we are now staying well away from that other
> holiday season, sometimes known in the Western world as 'Easter', which
> seems prudent.
>
> Tom Petch
>
>
> ----- Original Message -----
> From: "IETF Administrative Director" <iad@ietf.org>
> To: "IETF Announcement List" <ietf-announce@ietf.org>
> Cc: <iaoc@ietf.org>; <iab@iab.org>; <ietf@ietf.org>;
> <wgchairs@ietf.org>; <iesg@ietf.org>
> Sent: Thursday, September 06, 2012 8:15 PM
> Subject: Proposed IETF Meeting Calendar 2018 - 2022
>
>
> All;
>
> Below are suggested Meeting dates for 2018 - 2022, IETF's 101 - 115.
>
> The IAOC is soliciting the community's feedback before adopting.
>
> Comments appreciated to ietf@ietf.org by 20 September 2012.
>
> Ray
>
> 2018
> IETF 101 18-23 March 2018
> IETF 102 22-27 July 2018
> IETF 103 4 - 9 November 2018
>
> 2019
> IETF 104 24 - 29 March 2019
> IETF 105 21 - 26 July 2019
> IETF 106 17 - 22 November 2019
>
> 2020
> IETF 107 22 - 27 March 2020
> IETF 108 26 - 31 July 2020
> IETF 109 15 - 20 November 2020
>
> 2021
> IETF 110 21 - 26 March 2021
> IETF 111 25 - 30 July 2021
> IETF 112 7 - 12 November 2021
>
> 2022
> IETF 113 20 - 25 March 2022
> IETF 114 24 - 29 July 2022
> IETF 115 6 - 11 November 2022
>
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From dhc@dcrocker.net  Fri Sep  7 06:30:19 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C81421F854E for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 06:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nzkR-fitUCS7 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 06:30:18 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B3AE721F854D for <ietf@ietf.org>; Fri,  7 Sep 2012 06:30:18 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q87DUD27003088 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 06:30:14 -0700
Message-ID: <5049F6DD.7040404@dcrocker.net>
Date: Fri, 07 Sep 2012 06:30:05 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com> <5049BF70.7050103@cisco.com> <5049C17D.3080103@cisco.com>
In-Reply-To: <5049C17D.3080103@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 07 Sep 2012 06:30:14 -0700 (PDT)
Cc: IETF 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: Fri, 07 Sep 2012 13:30:19 -0000

On 9/7/2012 2:42 AM, Eliot Lear wrote:
>> "An I-D will only be removed from the public I-D archive if legally
>> required to do so."
>
> That is where I was aiming, albeit with s/will/may/.  Again, I recommend
> that Jorge review.  Nothing in this policy should REQUIRE the IESG to
> act, or set that expectation.


The IESG should not be /required/ to honor a court order?

In addition, the more discretion the policy affords the IESG, the more 
it can -- unintentionally, of course -- run the risk of doing censoring.

But yes, the draft policy text needs to be vetted by counsel.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From nick@inex.ie  Fri Sep  7 07:36:40 2012
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9A8F21F86A5 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 07:36:40 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrIHL+JfMhYh for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 07:36:40 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id CD65D21F8673 for <ietf@ietf.org>; Fri,  7 Sep 2012 07:36:38 -0700 (PDT)
X-Envelope-To: ietf@ietf.org
Received: from crumpet.local (inet-gw.acquirer.com [87.198.142.10]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q87EYiTs062523 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 7 Sep 2012 15:34:44 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <504A066D.3070708@inex.ie>
Date: Fri, 07 Sep 2012 15:36:29 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com> <m2ligm732r.wl%randy@psg.com> <50499912.9050806@cisco.com> <5049BF70.7050103@cisco.com> <5049C17D.3080103@cisco.com> <5049F6DD.7040404@dcrocker.net>
In-Reply-To: <5049F6DD.7040404@dcrocker.net>
X-Enigmail-Version: 1.4.4
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Fri, 07 Sep 2012 14:36:40 -0000

On 07/09/2012 14:30, Dave Crocker wrote:
> The IESG should not be /required/ to honor a court order?

whose court order?

Nick


From ajs@anvilwalrusden.com  Fri Sep  7 07:48:34 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7576B21E80B2 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 07:48: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uGwtYkHm5cmk for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 07:48:32 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 79B7621E8051 for <ietf@ietf.org>; Fri,  7 Sep 2012 07:48:32 -0700 (PDT)
Received: from mx1.yitter.info (nat-05-mht.dyndns.com [216.146.45.244]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id C01398A031 for <ietf@ietf.org>; Fri,  7 Sep 2012 14:48:31 +0000 (UTC)
Date: Fri, 7 Sep 2012 10:48:32 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Message-ID: <20120907144831.GB16938@mx1.yitter.info>
References: <CC6CCC68.8B24D%stewe@stewe.org> <5049090C.6000805@qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5049090C.6000805@qualcomm.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 14:48:34 -0000

On Thu, Sep 06, 2012 at 03:35:24PM -0500, Pete Resnick wrote:

> I must say, I find this a very strange thing to say. The original
> statement was "we will not remove anything from the archive unless
> ordered to by duly authorized court".
[â€¦]
> questions. I'm not sure I like the idea of making my job harder, but

It seems to me you all made your jobs harder when you put up the
statement for contemplation.  Maybe I missed it in the many messages,
but I don't understant what problem the statement is trying to solve
(especially given that the goal was really just to restrict action to
exactly what you'd have to do not to go to jail)?  To me, the proposal
seems like an administrative rule without a great deal of benefit, but
with plenty of future opportunity for exception handling (and the
associated rats and holes).

Best,
A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From touch@isi.edu  Fri Sep  7 07:48:55 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73ED121E80BE for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 07:48:55 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZFU4Uq36a5k for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 07:48:55 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 1362421E80BF for <ietf@ietf.org>; Fri,  7 Sep 2012 07:48:55 -0700 (PDT)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q87Em7if018825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 07:48:16 -0700 (PDT)
Message-ID: <504A0928.2020200@isi.edu>
Date: Fri, 07 Sep 2012 07:48:08 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>
In-Reply-To: <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>
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: Fri, 07 Sep 2012 14:48:55 -0000

On 9/5/2012 7:51 AM, SM wrote:
...
> Creating a perpetual I-D archive for the sake of rfcdiff is not a good
> idea as it goes against the notion of letting an I-D expire gracefully.

+1

Let's not forget there was a reason for expiration.

I'm OK with the archive being public so long as at least the authors can 
remove an ID *without needing to provide a reason*.

Yes, removal from the IETF site will not expunge copies from the entire 
Internet, but the IETF site should set the example here, and respect the 
original intent of allowing an ID to expire.

Joe

From touch@isi.edu  Fri Sep  7 07:51:53 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B23D21E80BC; Fri,  7 Sep 2012 07:51:53 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V0F3pcS7bPFo; Fri,  7 Sep 2012 07:51:52 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id CB7F121E8051; Fri,  7 Sep 2012 07:51:52 -0700 (PDT)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q87EpMoi019553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 07:51:31 -0700 (PDT)
Message-ID: <504A09EB.1090301@isi.edu>
Date: Fri, 07 Sep 2012 07:51:23 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: IETF Chair <chair@ietf.org>
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protocols
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org>
In-Reply-To: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.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 <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Sep 2012 14:51:53 -0000

Hi, all,

This statement seems fine, but it's worth noting that it would apply 
only to  *IETF* protocol specs. The IESG has, IMO, no authority to make 
such claims for independent submissions (and what about IRTF ones?), and 
the IEEE should recognize that such protocols are described by RFCs too.

Joe

On 9/3/2012 5:02 PM, IETF Chair wrote:
> The IESG is considering this IESG Statement.  Comments from the community are solicited.
>
> On behalf of the IESG,
> Russ
>
> --- DRAFT IESG STATEMENT ---
>
> Subject: Ethertype Assignments for IETF Protocols
>
> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some IETF
> protocol specification make use of Ethertypes.  Since Ethertypes are a
> fairly scarce resource, the IEEE RAC will not assign a new Ethertype to
> a new IETF protocol specification that needs one until the IESG has
> approved the protocol specification for publication as an RFC.
>
> To let the IEEE RAC know that the IESG has approved an IETF protocol
> specification for publication, all future requests for assignment of
> Ethertypes for IETF protocol specifications will be made by the IESG.
>
> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for use
> during development and experimentation.
>
>
> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>     IEEE standard for Local and Metropolitan Area Networks:
>     Overview and Architecture -- Amendment 1: Ethertypes for
>     Prototype and Vendor-Specific Protocol Development.
>
>

From brian.e.carpenter@gmail.com  Fri Sep  7 08:32:20 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA96E21F86F9 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 08:32:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.715
X-Spam-Level: 
X-Spam-Status: No, score=-101.715 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p8jjLzLdygCs for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 08:32:20 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id E91C421F86D0 for <ietf@ietf.org>; Fri,  7 Sep 2012 08:32:19 -0700 (PDT)
Received: by eekb45 with SMTP id b45so1318056eek.31 for <ietf@ietf.org>; Fri, 07 Sep 2012 08:32:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=xeVVA8gkxaH7+1Y5JyIQMdlZu/94XRLmQyV+hmlWdFo=; b=BXSNhbMUu8uVjk4XZhrHqWYyACvZDZeR/sb84qXkhAmOzVL3J038Qp0dezKuksoAI/ rM4kYyx9Nd1s1dOM9zKpt1DZRRr2nDreWYIoHChUVXSFLFIv3eWCyw/By7de1w9i+aFj tc4NZqJvpBxcjLN62n3AkcWFD83KD+2osKWZl28nnA+nprBPrhdT6vtQ3nfGLrmPd01H hVkUD6/1LuVy5XKxaJjcFUTMsLO8HnzKBuC2gWNWO87taSxjsM0oaL+QItLZc0d/xgHy PaljVftwuvW2tSu46t/REnA2MsB8vQ69Fmi0xtShpeSc36BnnWLKKY+knivwX5QYQpfJ 56qg==
Received: by 10.14.202.71 with SMTP id c47mr8582533eeo.42.1347031939170; Fri, 07 Sep 2012 08:32:19 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-145.as13285.net. [2.102.217.145]) by mx.google.com with ESMTPS id r45sm15614886eem.6.2012.09.07.08.32.17 (version=SSLv3 cipher=OTHER); Fri, 07 Sep 2012 08:32:17 -0700 (PDT)
Message-ID: <504A138D.8050504@gmail.com>
Date: Fri, 07 Sep 2012 16:32:29 +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: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu>
In-Reply-To: <504A0928.2020200@isi.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 15:32:20 -0000

On 07/09/2012 15:48, Joe Touch wrote:
> 
> 
> On 9/5/2012 7:51 AM, SM wrote:
> ...
>> Creating a perpetual I-D archive for the sake of rfcdiff is not a good
>> idea as it goes against the notion of letting an I-D expire gracefully.

Speaking as a document reviewer for both Gen-ART and the Independent
Submission stream, and for that matter as a generic reviewer of various
WG documents, I consider the I-D archive to be an invaluable resource.
Looking back to see when a particular change was made can be quite
important.

Speaking as an author of I-Ds, I find the archive very useful when trying
to figure out if an idea is new, or tracking back from a WG mail archive
to an I-D that is discussed therein.

Basically, the archive noticeably enhances the way I work on IETF
documents.

Also, I think there is a definite benefit to having a *public* archive
of potential prior art. Anyway who suspects prior art exists in an old
I-D has the possibility of searching for confirmation. If there was no
public archive, only a subpoena would find the prior art.

> +1
> 
> Let's not forget there was a reason for expiration.

Expired != invisible

Also, expiration, as a fact of experience, does not prevent I-Ds
being widely cited. I was quite embarassed at one point to discover
that draft-carpenter-metrics (expired 11/1996) was being cited as if
it had some authority, and I can assure you that its absence from any
public *.ietf.org directory did nothing to prevent the citations.
That's one example among hundreds, no doubt.

> I'm OK with the archive being public so long as at least the authors can
> remove an ID *without needing to provide a reason*.

Why? I-Ds are public speech. Generally, you can't erase public speech.
If I decide next week that this message was stupid, I can't erase
it from the mail archive. Why are I-Ds different?

Sometimes there might be valid reasons (like "I broke the copyright rules")
but I think you need to state a reason.

> Yes, removal from the IETF site will not expunge copies from the entire
> Internet, but the IETF site should set the example here, and respect the
> original intent of allowing an ID to expire.

I think making it clear that the archive contains expired documents is
necessary, but expiry by obscurity isn't going to work.

    Brian

From touch@isi.edu  Fri Sep  7 08:43:39 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A74A21F8723 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 08:43:39 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7tYYOjvtolnF for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 08:43:38 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7F3DD21F85F0 for <ietf@ietf.org>; Fri,  7 Sep 2012 08:43:38 -0700 (PDT)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q87Fh0tE013439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 08:43:09 -0700 (PDT)
Message-ID: <504A1604.2020000@isi.edu>
Date: Fri, 07 Sep 2012 08:43:00 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com>
In-Reply-To: <504A138D.8050504@gmail.com>
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 <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Sep 2012 15:43:39 -0000

On 9/7/2012 8:32 AM, Brian E Carpenter wrote:
> On 07/09/2012 15:48, Joe Touch wrote:
...
>> Let's not forget there was a reason for expiration.
>
> Expired != invisible

Expired = no longer *published*.

IMO, the "expires" indication on an ID indicates the expiration of the 
ability of the ISOC to publish the draft.

So IMO the ISOC is then violating the terms of submission of a doc if it 
posts it publicly in perpetuity.

...
> I think making it clear that the archive contains expired documents is
> necessary, but expiry by obscurity isn't going to work.

It worked for a very long time. If you're now claiming it cannot work, 
you need to consider the potential effect on the ID process.

If IDs are published forever, ***WHY BOTHER WITH RFCS***?

Joe

From touch@isi.edu  Fri Sep  7 08:45:59 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E632421E804E for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 08:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.932
X-Spam-Level: 
X-Spam-Status: No, score=-103.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZcIuotZ2y9Dx for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 08:45:59 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB7521E8043 for <ietf@ietf.org>; Fri,  7 Sep 2012 08:45:59 -0700 (PDT)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q87FjRbN014000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 08:45:37 -0700 (PDT)
Message-ID: <504A1698.1020600@isi.edu>
Date: Fri, 07 Sep 2012 08:45:28 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com>
In-Reply-To: <504A138D.8050504@gmail.com>
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 <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Sep 2012 15:46:00 -0000

PS - to note an astonishing concept:

On 9/7/2012 8:32 AM, Brian E Carpenter wrote:
> On 07/09/2012 15:48, Joe Touch wrote:
>>
>>
>> On 9/5/2012 7:51 AM, SM wrote:
>> ...
>>> Creating a perpetual I-D archive for the sake of rfcdiff is not a good
>>> idea as it goes against the notion of letting an I-D expire gracefully.
>
> Speaking as a document reviewer for both Gen-ART and the Independent
> Submission stream, and for that matter as a generic reviewer of various
> WG documents, I consider the I-D archive to be an invaluable resource.
> Looking back to see when a particular change was made can be quite
> important.

It's not always about what is best for *you* or for other reviewers.

It's about what encourages a more open exchange of ideas.

If the community doesn't think that ID expiration serves that purpose 
anymore, fine. However, let's make this decision on *that* basis.

Joe

From dhc@dcrocker.net  Fri Sep  7 08:56:14 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB2A21F86F9 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 08:56:14 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TMSZHhOmaGKx for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 08:56:13 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BF94421F86C5 for <ietf@ietf.org>; Fri,  7 Sep 2012 08:56:13 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q87FuAjM006199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 08:56:11 -0700
Message-ID: <504A1911.8030804@dcrocker.net>
Date: Fri, 07 Sep 2012 08:56:01 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1698.1020600@isi.edu>
In-Reply-To: <504A1698.1020600@isi.edu>
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, 07 Sep 2012 08:56:11 -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, 07 Sep 2012 15:56:14 -0000

On 9/7/2012 8:45 AM, Joe Touch wrote:
> It's not always about what is best for *you* or for other reviewers.

Actually, it is.  The documents are issued by the IETF to facilitate 
public discussion.  It's the only reason to have the mechanism.


> It's about what encourages a more open exchange of ideas.

Having access to previous versions of a document often greatly 
facilitates discussion of it and later documents.

Having restricted access to the I-D archive was extremely problematic. 
Having easy access is extremely helpful to the community.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From touch@isi.edu  Fri Sep  7 09:04:35 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B12FD21F86EC for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 09:04:35 -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=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LzvnBU7oDAgR for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 09:04:34 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 6056C21F86EB for <ietf@ietf.org>; Fri,  7 Sep 2012 09:04:34 -0700 (PDT)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q87G3kck017338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 09:03:56 -0700 (PDT)
Message-ID: <504A1AE3.5010905@isi.edu>
Date: Fri, 07 Sep 2012 09:03:47 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1698.1020600@isi.edu> <504A1911.8030804@dcrocker.net>
In-Reply-To: <504A1911.8030804@dcrocker.net>
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 <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Sep 2012 16:04:35 -0000

On 9/7/2012 8:56 AM, Dave Crocker wrote:
>
>
> On 9/7/2012 8:45 AM, Joe Touch wrote:
>> It's not always about what is best for *you* or for other reviewers.
>
> Actually, it is.  The documents are issued by the IETF to facilitate
> public discussion.  It's the only reason to have the mechanism.

There are reasons not to have this too.

As I noted, if the IETF publishes IDs, why bother with RFCs?

What other publishing arena keeps its drafts public?

Joe


From rdroms.ietf@gmail.com  Fri Sep  7 09:15:40 2012
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1D321F8739; Fri,  7 Sep 2012 09:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.349
X-Spam-Level: 
X-Spam-Status: No, score=-103.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s5z+2Q2p5dQO; Fri,  7 Sep 2012 09:15:39 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6033321F8723; Fri,  7 Sep 2012 09:15:39 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so11576vbb.31 for <multiple recipients>; Fri, 07 Sep 2012 09:15:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=M8L9CiYzxilNKngj8YwRJH95697TDB4Lk9La0clOzt4=; b=yuDWPfugtPSMyAOl2Zgvo7d/JqDH6qqGa7uuLRIiUCjaskRPDIrAMxjqtD44lDD/do b+mwWAlgU8NGP4F10fXS269EKRWE4nNB9xMraJfeLJC+qSNMCqPQcyxGKiLJ1khSgf9a POn2MCFvn8md2il479VAxF/JxyaAGmrDfwFb/PyjMddp248KpyBDIgtEaB43aa6XUjIp T3wQgvgQxEFeK1LR7LUoP3tooxmhQOEf1dPEtWmbFPI8kuIF8Wcmp7UyRQ1ktec/pW+u 0j5P1pPzL+NXAYWvYdkMKP5XQ8370o63RhhZyITJqgGjHkhFFSjkTwVsDg1/V9q3+WWY bNVQ==
Received: by 10.220.149.206 with SMTP id u14mr7821134vcv.63.1347034538430; Fri, 07 Sep 2012 09:15:38 -0700 (PDT)
Received: from rtp-rdroms-8915.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id b6sm3571737vdt.17.2012.09.07.09.15.25 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 07 Sep 2012 09:15:37 -0700 (PDT)
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <504A09EB.1090301@isi.edu>
Date: Fri, 7 Sep 2012 12:15:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com>
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu>
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Apple Mail (2.1278)
Cc: IETF Chair <chair@ietf.org>, IETF list 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, 07 Sep 2012 16:15:40 -0000

On Sep 7, 2012, at 10:51 AM 9/7/12, Joe Touch wrote:

> Hi, all,
>=20
> This statement seems fine, but it's worth noting that it would apply =
only to  *IETF* protocol specs.

What did you have in mind as "noting"?  This text seems pretty clear to =
me as applying only to "IETF protocol specifications":=20

  the IEEE RAC will not assign a new Ethertype to
  a new IETF protocol specification that needs one until the IESG has
  approved the protocol specification for publication as an RFC.



> The IESG has, IMO, no authority to make such claims for independent =
submissions (and what about IRTF ones?), and the IEEE should recognize =
that such protocols are described by RFCs too.

Where do you see any such claims in this statement?  What would you =
change?

- Ralph

>=20
> Joe
>=20
> On 9/3/2012 5:02 PM, IETF Chair wrote:
>> The IESG is considering this IESG Statement.  Comments from the =
community are solicited.
>>=20
>> On behalf of the IESG,
>> Russ
>>=20
>> --- DRAFT IESG STATEMENT ---
>>=20
>> Subject: Ethertype Assignments for IETF Protocols
>>=20
>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some =
IETF
>> protocol specification make use of Ethertypes.  Since Ethertypes are =
a
>> fairly scarce resource, the IEEE RAC will not assign a new Ethertype =
to
>> a new IETF protocol specification that needs one until the IESG has
>> approved the protocol specification for publication as an RFC.
>>=20
>> To let the IEEE RAC know that the IESG has approved an IETF protocol
>> specification for publication, all future requests for assignment of
>> Ethertypes for IETF protocol specifications will be made by the IESG.
>>=20
>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for =
use
>> during development and experimentation.
>>=20
>>=20
>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>    IEEE standard for Local and Metropolitan Area Networks:
>>    Overview and Architecture -- Amendment 1: Ethertypes for
>>    Prototype and Vendor-Specific Protocol Development.
>>=20
>>=20


From dhc@dcrocker.net  Fri Sep  7 09:21:43 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A7E21E8054 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 09:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JRFZ59zHUZu for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 09:21:42 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB3721E808A for <ietf@ietf.org>; Fri,  7 Sep 2012 09:21:42 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q87GLe60010215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 09:21:40 -0700
Message-ID: <504A1F0B.9000704@dcrocker.net>
Date: Fri, 07 Sep 2012 09:21:31 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1698.1020600@isi.edu> <504A1911.8030804@dcrocker.net> <504A1AE3.5010905@isi.edu>
In-Reply-To: <504A1AE3.5010905@isi.edu>
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, 07 Sep 2012 09:21:41 -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, 07 Sep 2012 16:21:43 -0000

> As I noted, if the IETF publishes IDs, why bother with RFCs?


It's difficult to imagine that you mean that as a serious question, but 
just in case:

      You are asking whether there is an important difference between a 
circulating mechanism that has no review, approval or quality control 
processes, versus one that has all of those vetting and refinement 
attributes?

      And by the way, formally, I-D's are not "published".  That's a 
semantic point, but apparently it's important for this discussion.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From touch@isi.edu  Fri Sep  7 09:26:28 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18D6E21E804E; Fri,  7 Sep 2012 09:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.399
X-Spam-Level: 
X-Spam-Status: No, score=-103.399 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxxELhar1mRM; Fri,  7 Sep 2012 09:26:27 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8B1D621E8043; Fri,  7 Sep 2012 09:26:27 -0700 (PDT)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q87GQ8uU021283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 09:26:18 -0700 (PDT)
Message-ID: <504A2021.6040404@isi.edu>
Date: Fri, 07 Sep 2012 09:26:09 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protocols
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu> <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com>
In-Reply-To: <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.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 Chair <chair@ietf.org>, IETF list 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, 07 Sep 2012 16:26:28 -0000

Hi, Ralph,

I agree with your assessment below, but historically the IETF guidelines 
work more smoothly when cases are spelled out rather than dealt with by 
omission. I think a few sentences being more explicit about what is not 
covered would be useful, esp. for the IEEE.

Joe

On 9/7/2012 9:15 AM, Ralph Droms wrote:
>
> On Sep 7, 2012, at 10:51 AM 9/7/12, Joe Touch wrote:
>
>> Hi, all,
>>
>> This statement seems fine, but it's worth noting that it would apply only to  *IETF* protocol specs.
>
> What did you have in mind as "noting"?  This text seems pretty clear to me as applying only to "IETF protocol specifications":
>
>    the IEEE RAC will not assign a new Ethertype to
>    a new IETF protocol specification that needs one until the IESG has
>    approved the protocol specification for publication as an RFC.
>
>
>
>> The IESG has, IMO, no authority to make such claims for independent submissions (and what about IRTF ones?), and the IEEE should recognize that such protocols are described by RFCs too.
>
> Where do you see any such claims in this statement?  What would you change?
>
> - Ralph
>
>>
>> Joe
>>
>> On 9/3/2012 5:02 PM, IETF Chair wrote:
>>> The IESG is considering this IESG Statement.  Comments from the community are solicited.
>>>
>>> On behalf of the IESG,
>>> Russ
>>>
>>> --- DRAFT IESG STATEMENT ---
>>>
>>> Subject: Ethertype Assignments for IETF Protocols
>>>
>>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some IETF
>>> protocol specification make use of Ethertypes.  Since Ethertypes are a
>>> fairly scarce resource, the IEEE RAC will not assign a new Ethertype to
>>> a new IETF protocol specification that needs one until the IESG has
>>> approved the protocol specification for publication as an RFC.
>>>
>>> To let the IEEE RAC know that the IESG has approved an IETF protocol
>>> specification for publication, all future requests for assignment of
>>> Ethertypes for IETF protocol specifications will be made by the IESG.
>>>
>>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for use
>>> during development and experimentation.
>>>
>>>
>>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>>     IEEE standard for Local and Metropolitan Area Networks:
>>>     Overview and Architecture -- Amendment 1: Ethertypes for
>>>     Prototype and Vendor-Specific Protocol Development.
>>>
>>>
>

From touch@isi.edu  Fri Sep  7 09:30:37 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8F321E804E for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 09:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xhYxlnLMCRFR for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 09:30:36 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB1721E8034 for <ietf@ietf.org>; Fri,  7 Sep 2012 09:30:36 -0700 (PDT)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q87GTGj0022102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 09:29:26 -0700 (PDT)
Message-ID: <504A20DD.3050200@isi.edu>
Date: Fri, 07 Sep 2012 09:29:17 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1698.1020600@isi.edu> <504A1911.8030804@dcrocker.net> <504A1AE3.5010905@isi.edu> <504A1F0B.9000704@dcrocker.net>
In-Reply-To: <504A1F0B.9000704@dcrocker.net>
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 <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Sep 2012 16:30:37 -0000

On 9/7/2012 9:21 AM, Dave Crocker wrote:
...
>       And by the way, formally, I-D's are not "published".  That's a
> semantic point, but apparently it's important for this discussion.

At lease one of the ISOC's boilerplates states:

       "This document may not be modified, and derivative works of it
       may not be created, and it may not be published except as an
                                             ^^^^^^^^^
       Internet-Draft."

The term "published" is used throughout the process.

Web postings are often considered "published".

Joe

From roni.even@mail01.huawei.com  Thu Sep  6 12:31:37 2012
Return-Path: <roni.even@mail01.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 69A0B21F8742 for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 12:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id moI1JBJuqAYx for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 12:31:37 -0700 (PDT)
Received: from hwsga02-in.huaweimarine.com (unknown [58.251.153.224]) by ietfa.amsl.com (Postfix) with ESMTP id 58DB021F8738 for <ietf@ietf.org>; Thu,  6 Sep 2012 12:31:36 -0700 (PDT)
Received: from szxpml202-edg.exmail.huawei.com ([172.17.1.119]) by hwsga02-in.huaweimarine.com (MOS 4.1.3-GA) with ESMTP id ADC28990; Fri, 7 Sep 2012 03:31:30 +0800
X-Mirapoint-Received-SPF: 172.17.1.119 szxpml202-edg.exmail.huawei.com <roni.even@mail01.huawei.com> 5 none
From: Roni Even <roni.even@mail01.huawei.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Proposed IETF Meeting Calendar 2018 - 2022
Thread-Topic: Proposed IETF Meeting Calendar 2018 - 2022
Thread-Index: AQHNjGQ8dVSAUe+IKEWc/AguT4OKHZd9smZO
Date: Thu, 6 Sep 2012 19:31:30 +0000
Message-ID: <760B7D45D1EFF74988DBF5C2122830C205B441F9@szxpml504-mbx.exmail.huawei.com>
References: <20120906191552.11119.48553.idtracker@ietfa.amsl.com>
In-Reply-To: <20120906191552.11119.48553.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.24.1.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 07 Sep 2012 10:53:58 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2012 19:31:37 -0000

Hi,
One request about IETF 110   21 - 26 March 2021.
March 27 is Jewish Passover (Pesach) so the 26th will not work for those wh=
o observe this major Holiday
Roni Even


________________________________________
From: wgchairs-bounces@ietf.org [wgchairs-bounces@ietf.org] on behalf of IE=
TF Administrative Director [iad@ietf.org]
Sent: Thursday, September 06, 2012 10:15 PM
To: IETF Announcement List
Cc: iaoc@ietf.org; iab@iab.org; ietf@ietf.org; wgchairs@ietf.org
Subject: Proposed IETF Meeting Calendar 2018 - 2022

All;

Below are suggested Meeting dates for 2018 - 2022, IETF's 101 - 115.

The IAOC is soliciting the community's feedback before adopting.

Comments appreciated to ietf@ietf.org by 20 September 2012.

Ray

2018
IETF 101                18-23 March 2018
IETF 102                22-27 July 2018
IETF 103                4 - 9 November 2018

2019
IETF 104                24 - 29 March 2019
IETF 105                21 - 26 July 2019
IETF 106                17 - 22 November 2019

2020
IETF 107                22 - 27 March 2020
IETF 108                26 - 31 July 2020
IETF 109                15 - 20 November 2020

2021
IETF 110                21 - 26 March 2021
IETF 111                25 - 30 July 2021
IETF 112                7 - 12 November 2021

2022
IETF 113                20 - 25 March 2022
IETF 114                24 - 29 July 2022
IETF 115                6 - 11 November 2022=

From derek@ihtfp.com  Thu Sep  6 16:13:16 2012
Return-Path: <derek@ihtfp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD21E21E804B; Thu,  6 Sep 2012 16:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.988
X-Spam-Level: 
X-Spam-Status: No, score=-101.988 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tDHY8OcXXalR; Thu,  6 Sep 2012 16:13:16 -0700 (PDT)
Received: from mail2.ihtfp.org (mail2.ihtfp.org [IPv6:2001:4830:143:1::3a11]) by ietfa.amsl.com (Postfix) with ESMTP id CF66021F85A7; Thu,  6 Sep 2012 16:13:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id DA28226023A; Thu,  6 Sep 2012 19:13:12 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 18142-07; Thu,  6 Sep 2012 19:13:12 -0400 (EDT)
Received: from mocana.ihtfp.org (209-203-64-223.static.twtelecom.net [209.203.64.223]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "cliodev.ihtfp.com", Issuer "IHTFP Consulting Certification Authority" (not verified)) by mail2.ihtfp.org (Postfix) with ESMTPS id 95F57260233; Thu,  6 Sep 2012 19:13:11 -0400 (EDT)
Received: (from warlord@localhost) by mocana.ihtfp.org (8.14.5/8.14.5/Submit) id q86ND9xW013613; Thu, 6 Sep 2012 19:13:09 -0400
From: Derek Atkins <derek@ihtfp.com>
To: James Polk <jmpolk@cisco.com>
Subject: Re: Proposed IETF Meeting Calendar 2018 - 2022
References: <20120906191552.11119.48553.idtracker@ietfa.amsl.com> <201209061922.q86JM7Cq020778@mtv-core-3.cisco.com>
Date: Thu, 06 Sep 2012 19:13:09 -0400
In-Reply-To: <201209061922.q86JM7Cq020778@mtv-core-3.cisco.com> (James Polk's message of "Thu, 06 Sep 2012 14:22:06 -0500")
Message-ID: <sjmwr06n3sq.fsf@mocana.ihtfp.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: Maia Mailguard 1.0.2a
X-Mailman-Approved-At: Fri, 07 Sep 2012 10:53:58 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Sep 2012 23:13:16 -0000

James Polk <jmpolk@cisco.com> writes:

> IETF 106 seems a bit late in November. Are we boxed in by other SDO
> meetings, or is this by our own choice?

Keep in mind that Thanksgiving isn't until November 28 in 2019.  There
is certainly history of IETF being held the week before Thanksgiving.

> James
[snip]
>>2019
>>IETF 104                24 - 29 March 2019
>>IETF 105                21 - 26 July 2019
>>IETF 106                17 - 22 November 2019

-derek

-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant

From peter@akayla.com  Thu Sep  6 16:29:41 2012
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 6A9E721F854C for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 16:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N-Z6HnB3ZRmd for <ietf@ietfa.amsl.com>; Thu,  6 Sep 2012 16:29:41 -0700 (PDT)
Received: from p3plsmtpa01-03.prod.phx3.secureserver.net (p3plsmtpa01-03.prod.phx3.secureserver.net [72.167.82.83]) by ietfa.amsl.com (Postfix) with SMTP id CCFBB21F84C2 for <ietf@ietf.org>; Thu,  6 Sep 2012 16:29:40 -0700 (PDT)
Received: (qmail 27217 invoked from network); 6 Sep 2012 23:29:40 -0000
Received: from unknown (173.8.184.78) by p3plsmtpa01-03.prod.phx3.secureserver.net (72.167.82.83) with ESMTP; 06 Sep 2012 23:29:38 -0000
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-ccamp-assoc-ext.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-ccamp-assoc-ext-05
Date: Thu, 6 Sep 2012 16:29:45 -0700
Message-ID: <021301cd8c87$8015fa50$8041eef0$@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: Ac2MhruKNA/0xKrwTAOM1by6Am1dAg==
Content-Language: en-us
X-Mailman-Approved-At: Fri, 07 Sep 2012 10:53:58 -0700
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: Thu, 06 Sep 2012 23:29:41 -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>

Document: draft-ietf-ccamp-assoc-ext-05
Reviewer: Peter Yee
Review Date: Sep-06-2012
IETF LC End Date: Aug-29-2012
IESG Telechat date: Sep-13-2012

Summary: This draft is basically ready for publication, but has a nit that
could be
fixed before publication. [Ready with nits.]

Generally, the diffs between -04 and -05 look fine to me and incorporate my
previously offered suggestions.

Nit:

Section 4, 1st paragraph, 3rd sentence: "identifies" -> "identify".




From mcr@sandelman.ca  Wed Sep  5 06:12:46 2012
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3563421F84D7 for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 06:12: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E53ZLHw7H-Ey for <ietf@ietfa.amsl.com>; Wed,  5 Sep 2012 06:12:45 -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 4459621F843C for <ietf@ietf.org>; Wed,  5 Sep 2012 06:12:43 -0700 (PDT)
Received: from [192.168.0.151] (CPE000d88c2eac8-CM0011ae90856a.cpe.net.cable.rogers.com [99.246.27.91]) by tuna.sandelman.ca (Postfix) with ESMTPSA id 751BF2018B for <ietf@ietf.org>; Wed,  5 Sep 2012 09:27:05 -0400 (EDT)
User-Agent: K-9 Mail for Android
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: IETF...the unconference of SDOs
From: Michael Richardson {quigon} <mcr@sandelman.ca>
Date: Wed, 05 Sep 2012 09:12:47 -0400
To: ietf@ietf.org
Message-ID: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
X-Mailman-Approved-At: Fri, 07 Sep 2012 10:57:29 -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: Wed, 05 Sep 2012 13:12:46 -0000

When I started attending IETF meetings in 1996, it was after about 6 years of reading mailing lists, at a time when "netetiquette"
or "Internet 101" was actively taught.  We (because I taught others after learning it) taught people enough about how email worked so that
they would understand basic things like quoting intelligently.  Further, in 1996, the IETF had not entered the "endless September"
(even though the Internet might have as a whole), and had time to actually guide people, and I am thankful to have learned what I did. 
The newcomer's orientation were simpler (because there was less to learn), but they occurred, and having attended Scott's orientation 
again this year (in Paris), I think they continue to do a very good job for the person who is attending.

They don't work at all for the person who has yet to attend a meeting.  We have a slow influx of very smart people who can and
do read all of rules, but like all organizations, not all of our rules are equally applied. It's also possible that some grey beards 
who have only remote attended for years (Yes, I thinking about you Melinda, Keith...) might have missed some subtle change in process.

The IETF's endless september mostly ended after the bust, leaving us, I think, in a summer session with few new people; I'd put us in January now.  
Few freshmen joining.

What I am writing about is that I think that we a problem with transfer students... those who did their september elsewhere, and 
have now switched schools for the winter semester.  It doesn't occur to them that they don't know how the IETF works... it must work
like other SDOs, they think.  Worse of all, I think, many of these people have doing what they thought was email for around a decade,
(yes, using Outlook), they have no idea how email works, nor do they even know there is another interface.  They simply do not know what happens 
to their mis-formatted emails, and why often this results in people being unable to listens to them in the mailing list.  

I don't have an answer to this; I'm not even sure there is a problem; I have a problem of writing too long emails.

I got thinking about this while reading this blog entry about structureless-ness:
   http://eaves.ca/2009/07/06/structurelessness-feminism-and-open/

In particular he notes the way that Elites form/exist.  I would quote it here, but it's hard to take it out context, so please read it.

Let me suggest that at the IETF, where the mailing list is king, you can't join the Elite if you can't quote email properly.  
Maybe we should *state* this.   
Maybe I'm also concerned because many in the former "elite" have moved to Apple Mail, and it seems that it is bug 
compatible with Outlook in it's assumption that format=flowed is the default, an act which destroys email quoting, and therefore discussion.

-- 
Sent from my android transformer, running CM9

From melinda.shore@gmail.com  Fri Sep  7 11:12:07 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0292921E80C6 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58LzmD0m5+QD for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:12:06 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 43C1E21E80C4 for <ietf@ietf.org>; Fri,  7 Sep 2012 11:12:06 -0700 (PDT)
Received: by iabz21 with SMTP id z21so3820764iab.31 for <ietf@ietf.org>; Fri, 07 Sep 2012 11:12:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=AjKa8cAYuAhShN001HTT928HlVQElLkv4SguhmZf/rs=; b=KFP68cBLKOlB+/nE0187OJllsbG/tlcV+cKbr9/RT8Stin9ORMJjvc4nzOlZLQ/54M h+EnY5MXsCxBYy4N8pshnBlz2BidoXsOBE0/JQkOtGHurR3qXpOT6zvhuxbtihw76oUG ofEQky6pIWuWUvHebsropwPZFu8dJQHBCD5o6uvxRZJ92KLbCzAuvFd8LMxw7XH0Gbnw chztQPul7gprSQ6chhHs1Iz6bwqNIlZ7BQHNJ9t2s3e89Hh595RHG38aH2pFE1PHcz+N hSQat+O2m4/oDOZVzziZuTZfPyQS70VU0vOR8uDmIMJI6LWYrBBeruKXgz8bSzND3GC3 +W2g==
Received: by 10.42.163.135 with SMTP id c7mr8090067icy.45.1347041525790; Fri, 07 Sep 2012 11:12:05 -0700 (PDT)
Received: from spandex.local (66-230-80-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.245]) by mx.google.com with ESMTPS id i2sm8991703igl.8.2012.09.07.11.12.04 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 07 Sep 2012 11:12:05 -0700 (PDT)
Message-ID: <504A38F3.6040805@gmail.com>
Date: Fri, 07 Sep 2012 10:12:03 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF...the unconference of SDOs
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
In-Reply-To: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.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, 07 Sep 2012 18:12:07 -0000

On 9/5/12 5:12 AM, Michael Richardson {quigon} wrote:
> It's also possible that some grey beards who
> have only remote attended for years (Yes, I thinking about you
> Melinda, Keith...) might have missed some subtle change in process.

This is a great note, Michael, and now that I'm attending again
I have to say that the changes are not at all subtle.  Processes
are more formal in part to protect the organization from legal
threats, in part because the boom in internetiness has increased
the number of bodies and therefore the need to negotiate both
relationships and space, and in part because of the reasons
you've identified.  There have also been some geopolitical changes
that ripple down into the IETF, and while there have been problems
and pressures as a result I think that there's been a very large
net benefit.  More has needed to be codified, though.

> Let me suggest that at the IETF, where the mailing list is king, you
> can't join the Elite if you can't quote email properly.

Well, okay, but I have to say that that's probably the least
of the failures of culture transfer.  I have a bigger problem
with the very large number of junk drafts being generated for
political reasons.

Still, I understand what you're saying and agree with it.  Maybe
we can start with getting something into the wg chairs wiki and
starting a discussion on the mailing list.

Melinda


From ynir@checkpoint.com  Fri Sep  7 11:17:39 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFEE21F8518 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:17:39 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BL2t+zzwlnUi for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:17:38 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 0E1B921F84F1 for <ietf@ietf.org>; Fri,  7 Sep 2012 11:17:37 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q87IHR1t005577; Fri, 7 Sep 2012 21:17:27 +0300
X-CheckPoint: {504A35C1-1-1B221DC2-4FFFF}
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 7 Sep 2012 21:17:27 +0300
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Fri, 7 Sep 2012 21:17:26 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Joe Touch <touch@isi.edu>
Date: Fri, 7 Sep 2012 21:17:32 +0300
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Topic: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Index: Ac2NJQiOuGmY/UIdQtOpDLNj20kjKQ==
Message-ID: <CCA56974-4201-49A4-81C8-6CC3E4281019@checkpoint.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>	<504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com>	<504A1698.1020600@isi.edu> <504A1911.8030804@dcrocker.net> <504A1AE3.5010905@isi.edu>
In-Reply-To: <504A1AE3.5010905@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, 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, 07 Sep 2012 18:17:39 -0000

On Sep 7, 2012, at 7:03 PM, Joe Touch wrote:

> As I noted, if the IETF publishes IDs, why bother with RFCs?

In addition to what Dave said, the target audience of drafts are IETF parti=
cipants. The target audience of RFCs varies, but in the usual case it's imp=
lementers. So drafts might have statements like "we should decide whether t=
his MUST is necessary", but that would be inappropriate in an RFC.

Because our processes are not fast, people end up implementing from drafts.=
 This is risky business, because implementations of draft-=85-01 may not in=
teroperate with implementations of draft-=85-02. If you implement -01 you'r=
e always at risk that your implementation will become obsolete and then you=
'll have to worry about all those deployed products.=20

RFCs put an end to the series of drafts, requiring a new series of drafts t=
o change.


From simon.perreault@viagenie.ca  Fri Sep  7 11:31:21 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2869521E80B7 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:31:21 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejfmxok9DwyH for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:31:20 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 60A9221E808F for <ietf@ietf.org>; Fri,  7 Sep 2012 11:31:20 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:183e:b0be:9214:97a9]) by jazz.viagenie.ca (Postfix) with ESMTPSA id E89F145BD2 for <ietf@ietf.org>; Fri,  7 Sep 2012 14:31:18 -0400 (EDT)
Message-ID: <504A3D76.4050208@viagenie.ca>
Date: Fri, 07 Sep 2012 14:31:18 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF...the unconference of SDOs
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
In-Reply-To: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 18:31:21 -0000

Le 2012-09-05 09:12, Michael Richardson {quigon} a Ã©crit :
> Let me suggest that at the IETF, where the mailing list is king, you can't join the Elite if you can't quote email properly.
> Maybe we should *state* this.
> Maybe I'm also concerned because many in the former "elite" have moved to Apple Mail, and it seems that it is bug
> compatible with Outlook in it's assumption that format=flowed is the default, an act which destroys email quoting, and therefore discussion.

Two things:

1) I agree it's a pain. But in Thunderbird there is Edit --> Reflow 
which helps a lot. It's not perfect, but it makes the pain bearable.

2) You too are guilty. Your email was not flowed and with very long 
lines (not infinite like Apple, but still way more than 80 characters).

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

From swb@internet2.edu  Fri Sep  7 11:36:32 2012
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D11DB21E80CF for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:36: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BN08A+a7RmXW for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:36:31 -0700 (PDT)
Received: from int-proxy01.merit.edu (int-proxy01.merit.edu [207.75.116.230]) by ietfa.amsl.com (Postfix) with ESMTP id 956BE21E80C9 for <ietf@ietf.org>; Fri,  7 Sep 2012 11:36:30 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by int-proxy01.merit.edu (Postfix) with ESMTP id D2B2710002B; Fri,  7 Sep 2012 14:36:29 -0400 (EDT)
X-Virus-Scanned: amavisd-new at int-proxy01.merit.edu
Received: from int-proxy01.merit.edu ([127.0.0.1]) by localhost (int-proxy01.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3CW934BSsX4Y; Fri,  7 Sep 2012 14:36:29 -0400 (EDT)
Received: from swbi2mbp.local (cpe-74-79-27-61.twcny.res.rr.com [74.79.27.61]) by int-proxy01.merit.edu (Postfix) with ESMTPSA id 225EC100027; Fri,  7 Sep 2012 14:36:29 -0400 (EDT)
Message-ID: <504A3EAC.1090309@internet2.edu>
Date: Fri, 07 Sep 2012 14:36:28 -0400
From: Scott Brim <swb@internet2.edu>
Organization: Internet2
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Michael Richardson {quigon} <mcr@sandelman.ca>
Subject: Re: IETF...the unconference of SDOs
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
In-Reply-To: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 18:36:32 -0000

On 09/05/12 09:12, Michael Richardson {quigon} allegedly wrote:
> What I am writing about is that I think that we a problem with
> transfer students... those who did their september elsewhere, and
> have now switched schools for the winter semester.  It doesn't occur
> to them that they don't know how the IETF works... it must work like
> other SDOs, they think.

Yes, and within WGs there are attempts to teach culture.  However, the
IETF is an amalgamation of its participants, and the IETF culture
should be able to adapt.  Like any technical architecture, the basic
framework of the IETF should be robust and flexible enough that it can
adapt to unforeseen inputs.

> Worse of all, I think, many of these people have doing what they
> thought was email for around a decade, (yes, using Outlook), they
> have no idea how email works, nor do they even know there is another
> interface.  They simply do not know what happens to their
> mis-formatted emails, and why often this results in people being
> unable to listens to them in the mailing list.

We know how to deal with this in our friends and relatives every day,
and we can learn to do it in the IETF.  On occasion I've reorganized
received outlook mail into the form I wanted to respond to.  I did
once get asked "why don't you just put your response at the top like
everybody else" :-)  But anyway we can be lenient in what we receive.
The smart ones will adapt, themselves, so we won't have to do so for
long with them.

> I don't have an answer to this; I'm not even sure there is a
> problem; I have a problem of writing too long emails.

You can get help for that.

> Let me suggest that at the IETF, where the mailing list is king, you
> can't join the Elite if you can't quote email properly.

> Maybe I'm also concerned because many in the former "elite" have
> moved to Apple Mail, and it seems that it is bug compatible with
> Outlook in it's assumption that format=flowed is the default, an act
> which destroys email quoting, and therefore discussion.

and if you figure out the right settings in Thunderbird please let me
know.


On 09/07/12 14:12, Melinda Shore allegedly wrote:> On 9/5/12 5:12 AM,
Michael Richardson {quigon} wrote:
> This is a great note, Michael, and now that I'm attending again I
> have to say that the changes are not at all subtle.  Processes are
> more formal in part to protect the organization from legal threats,
> in part because the boom in internetiness has increased the number
> of bodies and therefore the need to negotiate both relationships and
> space, and in part because of the reasons you've identified.

It's also a reflex of a technologist mind.  If there's uncertainty,
put in a procedure.

Scott (writing this in emacs)

From sm@resistor.net  Fri Sep  7 11:37:37 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4924F21F84B9 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:37:37 -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, J_CHICKENPOX_12=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FNW+AIfAsnxr for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:37:32 -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 CE12821F84B6 for <ietf@ietf.org>; Fri,  7 Sep 2012 11:37:32 -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 q87IbPqo002917; Fri, 7 Sep 2012 11:37:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1347043050; bh=v6F8cPcn93WwMYIuAg7mR963RXgVdh1cSsMzIvm0DL8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=t+aRm/7LY7aIvh4lCzLzGAnOB4KzYUnqAQyQ+9ugtkIJ99hWbDLAsFjydy4t/xpRi 21ZeMdOqHpw+I9ErW+L+DPLHADHJYZiMM9GMZwPKxuusYfhblRBFjDvcuppzKkzS+4 E6+OymYKfLRef8C9sHE1ZqtnuqE4ttytuCK74Wgw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1347043050; i=@resistor.net; bh=v6F8cPcn93WwMYIuAg7mR963RXgVdh1cSsMzIvm0DL8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=C4kEFk61yALGF8gO6YWtmiVtp3NALqBK3Xv1c7nsounnSLoLsL0k8hbOsXUZP6bEW QSxRXxh9eDpYOMQch5xTSHn511HHOy8zxJiPH4l2qgZ1CEfvyhRYFXhsvTL1V6gZA4 UmBXEPLCYlP63zK6W5oiyfRsQsMgYGp2Ajx2pL50=
Message-Id: <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 07 Sep 2012 11:37:17 -0700
To: IETF <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <504A1604.2020000@isi.edu>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john-ietf@jck.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, 07 Sep 2012 18:37:37 -0000

At 08:43 07-09-2012, Joe Touch wrote:
>IMO, the "expires" indication on an ID indicates the expiration of 
>the ability of the ISOC to publish the draft.

This raises the question of what "expires" means.

>So IMO the ISOC is then violating the terms of submission of a doc 
>if it posts it publicly in perpetuity.

An I-D made available through ietf.org has:

   "Copyright (c) 2012 IETF Trust and the persons identified as the
    document authors.  All rights reserved."

>If IDs are published forever, ***WHY BOTHER WITH RFCS***?

The I-D mentions that:

   "Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time."

The above question comes to mind.  The IETF could spare itself the 
expense of a RFC Editor to process IETF Stream documents.  That's 
approximately US $933,000 a year.

At 03:35 07-09-2012, John C Klensin wrote:
>Sorry, but this is largely a problem of our own making.  For
>years, our position was that I=Ds expired after six months and,
>when they expired, they disappeared from any public repository
>for which the IETF had direct responsibility.  If others wanted
>to capture and keep copies forever, that just wasn't our
>problem.  Indeed, it might be claimed that it violated our

Yes.

If I am not mistaken, the I-D archive referred to in the draft 
statement belongs to the IETF Trust.  Does the IETF Trust have a 
policy about the "DMCA" which has been mentioned in this thread?  On 
an unrelated note, It is strange that the IETF Trust hasn't had a 
meeting since March.

Regards,
-sm 


From simon.perreault@viagenie.ca  Fri Sep  7 11:53:37 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF3D21F852C for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:53:37 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lXXZLw6v3663 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 11:53:36 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 93B7221E808F for <ietf@ietf.org>; Fri,  7 Sep 2012 11:53:36 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:183e:b0be:9214:97a9]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C321B415A3 for <ietf@ietf.org>; Fri,  7 Sep 2012 14:53:35 -0400 (EDT)
Message-ID: <504A42AF.4090800@viagenie.ca>
Date: Fri, 07 Sep 2012 14:53:35 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF...the unconference of SDOs
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <504A3EAC.1090309@internet2.edu>
In-Reply-To: <504A3EAC.1090309@internet2.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 18:53:37 -0000

Le 2012-09-07 14:36, Scott Brim a Ã©crit :
>> Maybe I'm also concerned because many in the former "elite" have
>> moved to Apple Mail, and it seems that it is bug compatible with
>> Outlook in it's assumption that format=flowed is the default, an act
>> which destroys email quoting, and therefore discussion.
>
> and if you figure out the right settings in Thunderbird please let me
> know.

Thunderbird is correct by default AFAIK.

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

From melinda.shore@gmail.com  Fri Sep  7 12:15:19 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCA3D21E80C0 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 12:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.166
X-Spam-Level: 
X-Spam-Status: No, score=-3.166 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EvEgCLocNtox for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 12:15:19 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 43DAB21E808F for <ietf@ietf.org>; Fri,  7 Sep 2012 12:15:19 -0700 (PDT)
Received: by dadf8 with SMTP id f8so1914022dad.31 for <ietf@ietf.org>; Fri, 07 Sep 2012 12:15:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=52Rl6am4BqCtcZZrivjQK1TKfg/p6+jFr4gKD7n5EX0=; b=zJfswvxNtlj9jwnjmhQ+x9PmBhYMKcOUy74t9JMLe7+LLCk8/m+FhCpnlzpt79Tcmw cCdZvsX/RkItlEZGyMsIRL7D+T6QAlJGQCda9NYVW3MLcKoVGDjAXZqvfz3Q3ybtrIDp WebGWl109egPijLnlYx3kLrslRne8WEjC4jtBk38Q9QNnlDZ4ezSNTR0FCvN++hy6UlT Z9y8nQHUHFTKHHPD0xGircsg3aGd6kK79Q5dA8jnWDKQToizWY6gBymGVBtUHTwoFNFY kfeyGnKemp4aZwRumhmnwUysIl5TIxsodA5dDXV4h4XkVtvZwRLGKpcKvuz6NBjbRpUF EI1Q==
Received: by 10.66.87.132 with SMTP id ay4mr9243230pab.82.1347045319086; Fri, 07 Sep 2012 12:15:19 -0700 (PDT)
Received: from spandex.local (66-230-80-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.245]) by mx.google.com with ESMTPS id pj8sm3600309pbb.60.2012.09.07.12.15.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 07 Sep 2012 12:15:18 -0700 (PDT)
Message-ID: <504A47C4.6070103@gmail.com>
Date: Fri, 07 Sep 2012 11:15:16 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF...the unconference of SDOs
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <504A3EAC.1090309@internet2.edu> <504A42AF.4090800@viagenie.ca>
In-Reply-To: <504A42AF.4090800@viagenie.ca>
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, 07 Sep 2012 19:15:19 -0000

On 9/7/12 10:53 AM, Simon Perreault wrote:
> Thunderbird is correct by default AFAIK.

Unfortunately not on Mac OS.  It's become automatic for me to
hit command-R when replying, but that doesn't solve the basic
problem.

Melinda


From simon.perreault@viagenie.ca  Fri Sep  7 12:30:11 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5940F21F8574 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 12:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWlEYMI3X7np for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 12:30:10 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 86AE621F851E for <ietf@ietf.org>; Fri,  7 Sep 2012 12:30:10 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:183e:b0be:9214:97a9]) by jazz.viagenie.ca (Postfix) with ESMTPSA id BF48C415A3 for <ietf@ietf.org>; Fri,  7 Sep 2012 15:30:09 -0400 (EDT)
Message-ID: <504A4B41.1060905@viagenie.ca>
Date: Fri, 07 Sep 2012 15:30:09 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF...the unconference of SDOs
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <504A3EAC.1090309@internet2.edu> <504A42AF.4090800@viagenie.ca> <504A47C4.6070103@gmail.com>
In-Reply-To: <504A47C4.6070103@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 19:30:11 -0000

Le 2012-09-07 15:15, Melinda Shore a Ã©crit :
> On 9/7/12 10:53 AM, Simon Perreault wrote:
>> Thunderbird is correct by default AFAIK.
>
> Unfortunately not on Mac OS.  It's become automatic for me to
> hit command-R when replying, but that doesn't solve the basic
> problem.

That's what we've been saying. Apple sends broken mail. Thunderbird has 
a function to fix broken mail (command-R). Thunderbird is correct. Apple 
is broken.

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

From melinda.shore@gmail.com  Fri Sep  7 12:35:59 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39FBC21F861F for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 12:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.274
X-Spam-Level: 
X-Spam-Status: No, score=-3.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lysNzkjrybx9 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 12:35:58 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B531D21F861E for <ietf@ietf.org>; Fri,  7 Sep 2012 12:35:58 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so68088pbb.31 for <ietf@ietf.org>; Fri, 07 Sep 2012 12:35:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=k14/Az0GDwmGsRq3xbtCqqvilHZZFcRix4NunQSSlXw=; b=a7Q15wSgslV8IEmAHK7E38eW8ci2qpAoyOLlCOQtOdJgno4nRoll8oPaRjUvv12mTW GONsQ/StJJe9eVdan8l5XckzTw2Co7X6+uQbj68ixPI6vvoxXrbMwPZUlZ+mZsLTj9+5 1uouwy7X7ZyxwybEGz8Le1G9KcGra5bVr7JWGFa8ekXvMGbL/H0cfeoo8KXpLaXUqZSb 5FiwmFsy7ebgeRP0F9Kwus7CzV0l2mMq+Xmkk8Y5DPdRFJMA+OirMGD6s/OmWXhtqZPl G/rwwQDZlCMXXGucb8z8wcznz/9DBz8KrYhto3ZGHXFS+9+uTjKE8GlTImmFLofTYToS RA8Q==
Received: by 10.66.75.201 with SMTP id e9mr9420490paw.54.1347046558525; Fri, 07 Sep 2012 12:35:58 -0700 (PDT)
Received: from spandex.local (66-230-80-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.245]) by mx.google.com with ESMTPS id hc10sm3640610pbc.21.2012.09.07.12.35.56 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 07 Sep 2012 12:35:57 -0700 (PDT)
Message-ID: <504A4C9B.4010900@gmail.com>
Date: Fri, 07 Sep 2012 11:35:55 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF...the unconference of SDOs
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <504A3EAC.1090309@internet2.edu> <504A42AF.4090800@viagenie.ca> <504A47C4.6070103@gmail.com> <504A4B41.1060905@viagenie.ca>
In-Reply-To: <504A4B41.1060905@viagenie.ca>
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, 07 Sep 2012 19:35:59 -0000

On 9/7/12 11:30 AM, Simon Perreault wrote:
> That's what we've been saying. Apple sends broken mail. Thunderbird has
> a function to fix broken mail (command-R). Thunderbird is correct. Apple
> is broken.

Sure, but the default wrapping is wrong for many of us and wrong
for IETF email.  Thunderbird needs to provide an option to wrap at
a given column by default.

Unfortunately there's some stuff going around that line
wrapping with hard line terminations is retrograde and goes
back to punch cards.  I guess that's probably true but
aside from the fact that I'm retrograde and go back to
punch cards, myself, application line wrapping and flowed
text don't deal well (yet) with multiple character sets,
fonts, etc. and I'll take readability over application
purity every single time.

Melinda


From sm@resistor.net  Fri Sep  7 13:31:28 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 475DD21F845F for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 13:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jBM3daiang+L for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 13:31:27 -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 A581821F8446 for <ietf@ietf.org>; Fri,  7 Sep 2012 13:31:27 -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 q87KVLWr000676; Fri, 7 Sep 2012 13:31:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1347049886; bh=9eQCGrRPWXen5p4VOzX4UqQd3CGJRubTxIFxTgUg8OE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4hPI2K+nfExTlaLYueEteU+jV+xLXBUGK0pUZ1XDNDGC+dc5A9XAjr95O+9Tovk1J BXZKo8mXndesd2vQIwo88SLc14RtlEo8j8sltdHGQM3DtsmEdJkxQZYbA7vjF51XHG OvvPf42Hwhlt2AV0ggETh/p9m99IgmBj+ed2/gfc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1347049886; i=@resistor.net; bh=9eQCGrRPWXen5p4VOzX4UqQd3CGJRubTxIFxTgUg8OE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=q/Xb4xIRTGOcuGqs9bLyO1xe8wn8c7htbev37UvtbTJmg7zdbg2UschlKvZzWZcn0 SsQSx9H3RF8PlSps32gaKajtXgpCHRVAxd2+hNlp2yyWKo2qI+D8r4dqwCkn6EzJfQ fbhJS4UmV2q5gwdWoTgZZ482Iur7l406yFLeLnFc=
Message-Id: <6.2.5.6.2.20120907122215.09203460@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 07 Sep 2012 13:25:51 -0700
To: Michael Richardson {quigon} <mcr@sandelman.ca>
From: SM <sm@resistor.net>
Subject: Re: IETF...the unconference of SDOs
In-Reply-To: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2012 20:31:28 -0000

Hi Michael,
At 06:12 05-09-2012, Michael Richardson {quigon} wrote:
>like other SDOs, they think.  Worse of all, I think, many of these 
>people have doing what they thought was email for around a decade,
>(yes, using Outlook), they have no idea how email works, nor do they 
>even know there is another interface.  They simply do not know what happens
>to their mis-formatted emails, and why often this results in people 
>being unable to listens to them in the mailing list.

People use email in various ways.  Each person has his/her own idea 
of how email works.  I wonder if people think about whether a message 
will be formatted differently making it more difficult for the reader 
to understand.

>Let me suggest that at the IETF, where the mailing list is king, you 
>can't join the Elite if you can't quote email properly.

Some quoting styles make it tedious to follow the conversation.  Some 
people consider it as inefficient to trim the content in their 
reply.  That has been triggering more digests  from an IETF mailing 
list.  Some message bodies are a continuation of the subject line.

Whether any of the above is a good idea is subjective.

Regards,
-sm 


From chair@ietf.org  Fri Sep  7 14:09:40 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD9421E80E0; Fri,  7 Sep 2012 14:09: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TGrsKgakWmzn; Fri,  7 Sep 2012 14:09:39 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 7AACA21E80D3; Fri,  7 Sep 2012 14:09:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id BB14712D3F0; Fri,  7 Sep 2012 14:09:33 -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 eZmfZN1pz4KP; Fri,  7 Sep 2012 14:09:33 -0700 (PDT)
Received: from [192.168.2.105] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 6379C12D3EA; Fri,  7 Sep 2012 14:09:33 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Passing of Dr. John Larmouth
Date: Fri, 7 Sep 2012 17:09:31 -0400
Message-Id: <B7E27D87-1FA7-483C-8827-B4B4D49CDDFE@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
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, 07 Sep 2012 21:09:40 -0000

Dr. John Larmouth was one of the creators of ASN.1.  He was an active =
participant in ITU SG 17.  The IETF makes use of ASN.1 for several =
protocols.  I have placed an online condolence at =
http://www.itu.int/ITU-T/studygroups/com17/condolences.html.  If you =
knew Dr. Larmouth, you may wish to do the same.  On behalf of the IETF, =
I said:

   Dear Mme Larmouth, family, and friends,

   On behalf of the Internet Engineering Task Force, I wish to express =
our
   condolences on the loss of Dr. Larmouth.

   The IETF makes great use of ASN.1 in its SNMP, LDAP, CMS and other
   protocols.  The IETF also makes use of X.509, which in turn uses =
ASN.1.
   Dr. Larmouth's work lives on, and it provides a very strong =
foundation
   for many other works.

   Sincerely,
   Russ Housley
   IETF Chair




From rbarnes@bbn.com  Fri Sep  7 14:45:21 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2B821F85B1; Fri,  7 Sep 2012 14:45:21 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MImj5NAAj1Tp; Fri,  7 Sep 2012 14:45:20 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id ACFC321F85AE; Fri,  7 Sep 2012 14:45:20 -0700 (PDT)
Received: from ros-dhcp192-1-51-103.bbn.com ([192.1.51.103]:53267) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1TA6MZ-00091x-7L; Fri, 07 Sep 2012 17:45:19 -0400
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART review of draft-ietf-eai-mailinglistbis-05
Date: Fri, 7 Sep 2012 17:45:18 -0400
Message-Id: <47B04128-2745-479D-99BA-5FFB6CF66B55@bbn.com>
To: gen-art@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Cc: draft-ietf-eai-mailinglistbis@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: Fri, 07 Sep 2012 21:45:21 -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-eai-mailinglistbis-05
Reviewer: Richard Barnes
Review Date: 7 September 2012
IETF LC End Date: 29 August 2012
IESG Telechat date: (unknown)

Summary: Ready=

From touch@isi.edu  Fri Sep  7 18:52:53 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F71121E8041 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 18:52: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbC0+fpZGDgP for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 18:52:53 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 2EFC521E8040 for <ietf@ietf.org>; Fri,  7 Sep 2012 18:52:53 -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 q881qcv5027430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Sep 2012 18:52:38 -0700 (PDT)
Message-ID: <504AA4E7.8060000@isi.edu>
Date: Fri, 07 Sep 2012 18:52:39 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net>
In-Reply-To: <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net>
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: 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, 08 Sep 2012 01:52:53 -0000

On 9/7/2012 11:37 AM, SM wrote:
> At 08:43 07-09-2012, Joe Touch wrote:
>> IMO, the "expires" indication on an ID indicates the expiration of the
>> ability of the ISOC to publish the draft.
>
> This raises the question of what "expires" means.

At the least, if IDs are published publicly forever, then "expires" is 
no longer meaningful and the entirety of that notion needs to be 
expunged from the ID process.

Joe

From barryleiba.mailing.lists@gmail.com  Fri Sep  7 19:36:11 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC3F121F8620 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 19:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.939
X-Spam-Level: 
X-Spam-Status: No, score=-102.939 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jcj7KzighRBg for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 19:36:11 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id CD64A21F861F for <ietf@ietf.org>; Fri,  7 Sep 2012 19:36:10 -0700 (PDT)
Received: by lbky2 with SMTP id y2so206739lbk.31 for <ietf@ietf.org>; Fri, 07 Sep 2012 19:36:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=7Zr9P/e/jgOodpjjoH7kwx7tnHxaNOIGeGhXAk8GHy4=; b=IU7rGqqhYXb/yIOtnIJhFbxgKC/EWvVCliYiw7IPLHvC+9fRY+6eT61Y9hb2EWckZc lcb+PAMiWgKfLgBW5pO9UYMsxE2UDTO+qBc0omeV6JciVGR2AteM3aoPB30t/YIe61nI B0IhjiJ24Ir05C5QUSHaDbOYbWa9vUKrqshABLzSVrLAxRqYRdofFNUhJjADevETlqLi emwtfZpy2RZPgmNHRSfj+JwybApnGgNZPg6pVYlr3LAoFyhQ9I+r4olCWvrqk0pHRJU3 DvqosSwIV26XRsyo06pVOYwGX2idpaXSsmOflNInNVW2/TUyzEBmcZRbwFcrI7fhvMAk HrtQ==
MIME-Version: 1.0
Received: by 10.112.31.233 with SMTP id d9mr2769051lbi.116.1347071769405; Fri, 07 Sep 2012 19:36:09 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.91.33 with HTTP; Fri, 7 Sep 2012 19:36:09 -0700 (PDT)
In-Reply-To: <504AA4E7.8060000@isi.edu>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net> <504AA4E7.8060000@isi.edu>
Date: Fri, 7 Sep 2012 22:36:09 -0400
X-Google-Sender-Auth: a3nJX9BmysY0uwt7aZeAWPhPNfs
Message-ID: <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Barry Leiba <barryleiba@computer.org>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=bcaec55554344d692804c92796ea
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, 08 Sep 2012 02:36:11 -0000

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

>> This raises the question of what "expires" means.
>
> At the least, if IDs are published publicly forever, then "expires" is no
> longer meaningful and the entirety of that notion needs to be expunged
> from the ID process.

But you haven't addressed SM's comment. The point is that you and I have
different views of what it means for a draft to expire.

You seem to think it means something like "expunged from the record, and no
longer available for viewing."

I think it means "no longer current for the purposes of work and
discussion."

And I think those are very different things.  The fact that expired drafts
used to not be available for public viewing on the IETF site does not, by
itself, mean that that was or is the intent of expiration.

Barry

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

<span class=3D"Apple-style-span" style>&gt;&gt; This raises the question of=
 what &quot;expires&quot; means.</span><div><span class=3D"Apple-style-span=
" style>&gt;<br></span><div><span class=3D"Apple-style-span" style>&gt; At =
the least, if IDs are published publicly forever, then &quot;expires&quot; =
is no</span></div>
<div><span class=3D"Apple-style-span" style>&gt; longer meaningful and the =
entirety of that notion needs to be expunged</span></div><div><span class=
=3D"Apple-style-span" style>&gt; from the ID process.</span></div><div><spa=
n class=3D"Apple-style-span" style><br>
</span></div><div><span class=3D"Apple-style-span" style>But you haven&#39;=
t addressed SM&#39;s comment. The point is that you and I have different vi=
ews of what it means for a draft to expire.</span></div><div><span class=3D=
"Apple-style-span" style><br>
</span></div><div><span class=3D"Apple-style-span" style>You seem to think =
it means something like &quot;expunged from the record, and no longer avail=
able for viewing.&quot;</span></div><div><span class=3D"Apple-style-span" s=
tyle><br>
</span></div><div><span class=3D"Apple-style-span" style>I think it means &=
quot;no longer current for the purposes of work and discussion.&quot;</span=
></div><div><span class=3D"Apple-style-span" style><br></span></div><div><s=
pan class=3D"Apple-style-span" style>And I think those are very different t=
hings. =A0The fact that expired drafts used to not be available for public =
viewing on the IETF site does not, by itself, mean that that was or is the =
intent of expiration.<span></span></span></div>
<div><span class=3D"Apple-style-span" style><br></span></div><div><span cla=
ss=3D"Apple-style-span" style>Barry</span></div><div></div></div>

--bcaec55554344d692804c92796ea--

From randy@psg.com  Fri Sep  7 20:50:21 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5308921E805A for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 20:50: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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LLWh8T0c1lHz for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 20:50:21 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id E9D5721E8053 for <ietf@ietf.org>; Fri,  7 Sep 2012 20:50:20 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TAC3n-0000EA-MO; Sat, 08 Sep 2012 03:50:20 +0000
Date: Sat, 08 Sep 2012 12:51:23 +0900
Message-ID: <m21uid2mv8.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF...the unconference of SDOs
In-Reply-To: <504A47C4.6070103@gmail.com>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <504A3EAC.1090309@internet2.edu> <504A42AF.4090800@viagenie.ca> <504A47C4.6070103@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Sep 2012 03:50:21 -0000

really good message michael.  shame about the line wrap :)

>> Thunderbird is correct by default AFAIK.
> Unfortunately not on Mac OS.  It's become automatic for me to hit
> command-R when replying, but that doesn't solve the basic problem.

in the new ietf, everyone will use emacs.  the old dogs' macos users
list is rife with pleas for apple and tbird mua config magic, with rare
screams of shock, pain, and disgust from someone who has to use
outschnook for $dayjob mail.

i have given up reading the horribly mis-quoted email.  i concluded
there was a high correlation between not knowing how to use email and
other, even more drastic, clue gaps.  i just hit delete.  there already
is too much clueful mail to read.

if y'all come up with a constructive plan and i can help, holler.  i say
scott should teach emacs :)

randy

From touch@isi.edu  Fri Sep  7 20:58:28 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1057421F8599 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 20:58:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.472
X-Spam-Level: 
X-Spam-Status: No, score=-102.472 tagged_above=-999 required=5 tests=[AWL=-1.269, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R33U-Bm3ydgW for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 20:58:27 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 9C83D21F8594 for <ietf@ietf.org>; Fri,  7 Sep 2012 20:58:27 -0700 (PDT)
Received: from [192.168.1.97] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q883w9fn024174 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 7 Sep 2012 20:58:12 -0700 (PDT)
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net> <504AA4E7.8060000@isi.edu> <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com>
In-Reply-To: <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset=us-ascii
Message-Id: <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (9B206)
From: Joe Touch <touch@isi.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Date: Fri, 7 Sep 2012 20:58:08 -0700
To: Barry Leiba <barryleiba@computer.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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, 08 Sep 2012 03:58:28 -0000

On Sep 7, 2012, at 7:36 PM, Barry Leiba <barryleiba@computer.org> wrote:

> >> This raises the question of what "expires" means.
> >
> > At the least, if IDs are published publicly forever, then "expires" is n=
o
> > longer meaningful and the entirety of that notion needs to be expunged
> > from the ID process.
>=20
> But you haven't addressed SM's comment. The point is that you and I have d=
ifferent views of what it means for a draft to expire.
>=20
> You seem to think it means something like "expunged from the record, and n=
o longer available for viewing."

I seem to think it means what it wk ways has.  The desire to change that is t=
he basis of this thread.=20

> I think it means "no longer current for the purposes of work and discussio=
n."

What can that mean if it remains available to the public?  What purpose does=
 such an automatic timeout have if it is left up? IMO, none.=20

> And I think those are very different things.  The fact that expired drafts=
 used to not be available for public viewing on the IETF site does not, by i=
tself, mean that that was or is the intent of expiration.

That is exact what it meant. Or are you claiming that it was a coincidence t=
hat this entire time that derafts were removed in sync with that expiry?

Joe=

From jnc@mercury.lcs.mit.edu  Fri Sep  7 21:49:46 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2C6321F8666 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 21:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.854
X-Spam-Level: 
X-Spam-Status: No, score=-5.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tAvIJhwuZmnj for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 21:49:46 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 562A821F8668 for <ietf@ietf.org>; Fri,  7 Sep 2012 21:49:46 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C686518C0E7; Sat,  8 Sep 2012 00:49:44 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IETF...the unconference of SDOs
Message-Id: <20120908044944.C686518C0E7@mercury.lcs.mit.edu>
Date: Sat,  8 Sep 2012 00:49:44 -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: Sat, 08 Sep 2012 04:49:46 -0000

    > From: Randy Bush <randy@psg.com>

    > i say scott should teach emacs :)

Epsilon, dude! Who the heck wants to write their editor extensions in freaking
LISP? :-)

	Noel

From brian.e.carpenter@gmail.com  Sat Sep  8 01:14:00 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F5F21F8645 for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 01:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.711
X-Spam-Level: 
X-Spam-Status: No, score=-101.711 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPQs0UCYO7tX for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 01:13:59 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 3ABDD21F85DA for <ietf@ietf.org>; Sat,  8 Sep 2012 01:13:58 -0700 (PDT)
Received: by wibhr14 with SMTP id hr14so215489wib.13 for <ietf@ietf.org>; Sat, 08 Sep 2012 01:13:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Mg5VttTDPZnqduYxnx5vNLsdeBWY2b5tBouf4K8b7Vs=; b=PKLWCX7K1CgjIPN1LOCk66tpWs0A+SYBVCU/Qe2Gny9gld7hE5wpgkStijzlzpz/Hr IBVDOTSMdqHOQzhETTOQkO7hR6W8aWdNWsRZ5i268eXKBR+vIHm4ufth2bVeLy0KmpvC WFIKtXdDOcWRWuItsDVZ+Fpv6ZoMVoSOmPcVqShe7PVsq6KmxxyuvHZ+mL442Srxu7Ia r8+/2H/aA0KHy5xRJjyOV2Y0KindDrpF+CmBtMEjtF2WtfI5+ODw5F9NHY7W3XJXmiwU AkNtF2FWvHZyDEjE4SNEAO4twqf2206g6ofoXE6sXjmgnnIzvYnSJIsik9yDxA/NFCp/ GvEw==
Received: by 10.180.109.166 with SMTP id ht6mr3639754wib.11.1347092037680; Sat, 08 Sep 2012 01:13:57 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-188.as13285.net. [2.102.218.188]) by mx.google.com with ESMTPS id r9sm5264275wia.2.2012.09.08.01.13.55 (version=SSLv3 cipher=OTHER); Sat, 08 Sep 2012 01:13:56 -0700 (PDT)
Message-ID: <504AFE51.1080705@gmail.com>
Date: Sat, 08 Sep 2012 09:14: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: Joe Touch <touch@isi.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net>	<504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com>	<504A1604.2020000@isi.edu>	<6.2.5.6.2.20120907085007.0aaa2d38@resistor.net>	<504AA4E7.8060000@isi.edu>	<CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu>
In-Reply-To: <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.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: Sat, 08 Sep 2012 08:14:00 -0000

Joe,

On 08/09/2012 04:58, Joe Touch wrote:
> 
> On Sep 7, 2012, at 7:36 PM, Barry Leiba <barryleiba@computer.org> wrote:

...
>> And I think those are very different things.  The fact that expired drafts used to not be available for public viewing on the IETF site does not, by itself, mean that that was or is the intent of expiration.
> 
> That is exact what it meant. Or are you claiming that it was a coincidence that this entire time that derafts were removed in sync with that expiry?

It may be what some people thought it meant, or wished it meant.

And yes, it was intentional that you wouldn't find them in the *active*
drafts directory after expiry.

The factual reality is that I-D's have always been more or less perpetual,
given that anonymous FTP has existed longer than any I-D. Admittedly the
record is spotty for drafts earlier that about 1995, when HTTP became a
major factor (but I suspect you could find them with gopher etc before HTTP).
The difference today is that we are sort-of admitting officially that
obsolete drafts can be found, and that this is useful.

The word "expired" is perhaps not ideal; "obsolete" or "out of date" would
perhaps be more precise, but it's probably too late to change it now.

   Brian

From eburger-l@standardstrack.com  Sat Sep  8 04:02:12 2012
Return-Path: <eburger-l@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9AE721F8634 for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 04:02:11 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gY3zHdZ9TFT for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 04:02:11 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id CC5CE21F863F for <ietf@ietf.org>; Sat,  8 Sep 2012 04:02:10 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:62313 helo=[192.168.15.111]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from <eburger-l@standardstrack.com>) id 1TAIne-0004fQ-DH for ietf@ietf.org; Sat, 08 Sep 2012 04:02:06 -0700
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net> <504AA4E7.8060000@isi.edu> <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504AFE51.1080705@gmail.com>
From: Eric Burger <eburger-l@standardstrack.com>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (9B206)
In-Reply-To: <504AFE51.1080705@gmail.com>
Message-Id: <5350AE08-B2B8-4AB2-9E10-2119731E0B62@standardstrack.com>
Date: Sat, 8 Sep 2012 07:02:08 -0400
To: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Sep 2012 11:02:12 -0000

Keeping I-D's around forever is incredibly important form a historical, tech=
nical, and legal perspective. They people understand how we work, think, and=
 develop protocols (history). They help people what was tried and did or did=
 not succeed (technology). And they provide a record of the state of the art=
 at a particular point in time (legal).

--
Sent from a mobile device. Sorry for typos or weird auto-correct. Thank IETF=
 LEMONADE for mobile email! See <http://www.standardstrack.com/ietf/lemonade=
/>

On Sep 8, 2012, at 4:14 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> w=
rote:

> Joe,
>=20
> On 08/09/2012 04:58, Joe Touch wrote:
>>=20
>> On Sep 7, 2012, at 7:36 PM, Barry Leiba <barryleiba@computer.org> wrote:
>=20
> ...
>>> And I think those are very different things.  The fact that expired draf=
ts used to not be available for public viewing on the IETF site does not, by=
 itself, mean that that was or is the intent of expiration.
>>=20
>> That is exact what it meant. Or are you claiming that it was a coincidenc=
e that this entire time that derafts were removed in sync with that expiry?
>=20
> It may be what some people thought it meant, or wished it meant.
>=20
> And yes, it was intentional that you wouldn't find them in the *active*
> drafts directory after expiry.
>=20
> The factual reality is that I-D's have always been more or less perpetual,=

> given that anonymous FTP has existed longer than any I-D. Admittedly the
> record is spotty for drafts earlier that about 1995, when HTTP became a
> major factor (but I suspect you could find them with gopher etc before HTT=
P).
> The difference today is that we are sort-of admitting officially that
> obsolete drafts can be found, and that this is useful.
>=20
> The word "expired" is perhaps not ideal; "obsolete" or "out of date" would=

> perhaps be more precise, but it's probably too late to change it now.
>=20
>   Brian

From cabo@tzi.org  Sat Sep  8 04:48:18 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 493AF21F85EA for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 04:48:18 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VekojgG56vNZ for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 04:48:17 -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 E72CF21F8587 for <ietf@ietf.org>; Sat,  8 Sep 2012 04:48:13 -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.3/8.14.3) with ESMTP id q88Bm631007516; Sat, 8 Sep 2012 13:48:06 +0200 (CEST)
Received: from [192.168.217.105] (p54893BAA.dip.t-dialin.net [84.137.59.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id BB43C569; Sat,  8 Sep 2012 13:48:05 +0200 (CEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Content-Type: text/plain; charset=utf-8
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5350AE08-B2B8-4AB2-9E10-2119731E0B62@standardstrack.com>
Date: Sat, 8 Sep 2012 13:47:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E45EE27-89EC-41C3-8BD8-7C79064BA12D@tzi.org>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net> <504AA4E7.8060000@isi.edu> <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504AFE51.1080705@gmail.com> <5350AE08-B2B8-4AB2-9E10-2119731E0B62@standardstrack.com>
To: Eric Burger <eburger-l@standardstrack.com>
X-Mailer: Apple Mail (2.1486)
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, 08 Sep 2012 11:48:18 -0000

On Sep 8, 2012, at 13:02, Eric Burger <eburger-l@standardstrack.com> =
wrote:

> Keeping I-D's around forever is incredibly important form a =
historical, technical, and legal perspective. They people understand how =
we work, think, and develop protocols (history). They help people what =
was tried and did or did not succeed (technology). And they provide a =
record of the state of the art at a particular point in time (legal).

+1.  I have used rfcdiff with drafts from the 90s, and that was very =
useful.

I wonder why some people think "expired" means "purged from the face of =
the earth".  Let's see:
 expire |=C9=AAk=CB=88spa=C9=AA(=C9=99)r|
 verb
 1 [ no obj. ] (of a document, authorization, or agreement) cease to be =
valid, typically after a fixed period of time: the old contract had =
expired.

See, I have this expired passport in front of me, and it is every bit as =
accessible to me as it was when it still was valid. =20
I can pull it out of the drawer as much as I want, show it to my =
friends, etc.
It is just expired.
And there is no confusion whatsoever about that fact: It actually says =
so on page 3.

Now about removing I-Ds from public view: This has no bearing whatsoever =
on how we express expiration. =20
Drafts may need to be removed from view when they aren't expired yet.  =
So there is no need to discuss expiration under this headline.

Back to the actual subject:
I believe the policy should be, exactly in these words:

"Internet-Drafts will be removed from the archives only when this is =
really, really, necessary.
The determination whether this is really, really, necessary lies with =
the IESG.
The usual appeals process applies."

Gr=C3=BC=C3=9Fe, Carsten


From melinda.shore@gmail.com  Sat Sep  8 08:19:33 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD5921F8535 for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 08:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.382
X-Spam-Level: 
X-Spam-Status: No, score=-3.382 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X690J1+IF8Nd for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 08:19:33 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 058DA21F852B for <ietf@ietf.org>; Sat,  8 Sep 2012 08:19:32 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so926644pbb.31 for <ietf@ietf.org>; Sat, 08 Sep 2012 08:19:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Bjj63b9I3Ubd5gjerPRV8NthwKWW2emylwfc19zKAus=; b=DaSQRwrihWO29QcPkTJbx4BZ4+5ajmooDopV1BjVF79yukIdifudoPCqftTq/Ylbk6 eZL6AJzH4c3G6fFnCRy1njxWiSg15PdGjJpNCcofPdOGuVxIMplaEgSxbELQpzyG5x9P mB9VYTzJpqYr+QZ+z9JDJS//0fgDSWHVJcxTyC0ZQxWxHD6aUXaQD2RTR4U2bs4fRIwD D+r/W8jQF5ZmaVIfs9KU7dh6otmxyFB6+lWgDp+6YSvCfrFqHttH4AxAOpLeMctxOEqk 2pEhg/owh13T1eR00NRSbj6PBSCLILPrm62WHY9eafZ6GsTDSdGeEaXiJ4s+lR96DFCS GGbQ==
Received: by 10.68.197.167 with SMTP id iv7mr11873234pbc.113.1347117572630; Sat, 08 Sep 2012 08:19:32 -0700 (PDT)
Received: from spandex.local (66-230-80-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.245]) by mx.google.com with ESMTPS id rm9sm5418208pbc.72.2012.09.08.08.19.30 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 08 Sep 2012 08:19:31 -0700 (PDT)
Message-ID: <504B6201.9060904@gmail.com>
Date: Sat, 08 Sep 2012 07:19:29 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net> <504AA4E7.8060000@isi.edu> <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu>
In-Reply-To: <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu>
Content-Type: text/plain; charset=us-ascii; 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, 08 Sep 2012 15:19:33 -0000

On 9/7/12 7:58 PM, Joe Touch wrote:
> What can that mean if it remains available to the public?  What
> purpose does such an automatic timeout have if it is left up? IMO,
> none.

It seems to me that the "timeout" takes the draft out of consideration.
If someone wants to have a discussion about it, it needs to be revised.

I've looked at old drafts for background material for current work.
They're useful.

Melinda

From touch@isi.edu  Sat Sep  8 11:52:21 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD9321F8528 for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 11:52:21 -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, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cb7PGxUZG52G for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 11:52:20 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id DE30521F8518 for <ietf@ietf.org>; Sat,  8 Sep 2012 11:52:20 -0700 (PDT)
Received: from [128.9.176.217] (c2-vpn05.isi.edu [128.9.176.217]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q88IpBiS001693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 8 Sep 2012 11:51:12 -0700 (PDT)
Message-ID: <504B939F.8020002@isi.edu>
Date: Sat, 08 Sep 2012 11:51:11 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net>	<504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com>	<504A1604.2020000@isi.edu>	<6.2.5.6.2.20120907085007.0aaa2d38@resistor.net>	<504AA4E7.8060000@isi.edu>	<CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504AFE51.1080705@gmail.com>
In-Reply-To: <504AFE51.1080705@gmail.com>
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: Barry Leiba <barryleiba@computer.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: Sat, 08 Sep 2012 18:52:21 -0000

On 9/8/2012 1:14 AM, Brian E Carpenter wrote:
...
> The factual reality is that I-D's have always been more or less perpetual,
> given that anonymous FTP has existed longer than any I-D.

It has always been the case that some sites have violated the copyright 
and explicit instructions of IDs.

> The difference today is that we are sort-of admitting officially that
> obsolete drafts can be found, and that this is useful.

Admitting that there is piracy is not the same as the IETF posting them 
publicly on their site.

> The word "expired" is perhaps not ideal; "obsolete" or "out of date" would
> perhaps be more precise, but it's probably too late to change it now.

Nothing about an ID is inherently obsolete or out of date after 6 months 
except its being publicly available on authorized sites (up until now).

If we remove that rule, then the notion of expiration is outdated.

If it's not too late to change the "they are removed from the IESG site" 
rule, it's absolutely not too late to remove the "Expires:" indication 
on all IDs published as we go forward.

Note - I don't agree that past IDs should be posted after expiration 
without the author's consent. They were submitted with that 
understanding, and post-facto changing it by the IETF is not appropriate.

Joe

From touch@isi.edu  Sat Sep  8 11:55:47 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E956321F853C for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 11:55:47 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f+CaYn1ZeJQ5 for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 11:55:47 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 53B4D21F84A2 for <ietf@ietf.org>; Sat,  8 Sep 2012 11:55:47 -0700 (PDT)
Received: from [128.9.176.217] (c2-vpn05.isi.edu [128.9.176.217]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q88It5tL002322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 8 Sep 2012 11:55:06 -0700 (PDT)
Message-ID: <504B9489.4090500@isi.edu>
Date: Sat, 08 Sep 2012 11:55:05 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net> <504AA4E7.8060000@isi.edu> <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504B6201.9060904@gmail.com>
In-Reply-To: <504B6201.9060904@gmail.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Sep 2012 18:55:48 -0000

On 9/8/2012 8:19 AM, Melinda Shore wrote:
> On 9/7/12 7:58 PM, Joe Touch wrote:
>> What can that mean if it remains available to the public?  What
>> purpose does such an automatic timeout have if it is left up? IMO,
>> none.
>
> It seems to me that the "timeout" takes the draft out of consideration.

A new draft supercedes that timeout.

And if they're "useful", then you're admitting that continued discussion 
can occur after 6 months.

At which point there is no meaning to expiration. Any note regarding how 
long the discussion of a draft should occur would be on the mailing list 
anyway, and thus no longer would belong on the document.

---

I'm baffled by the notion that posting IDs forever is OK, but that 
simply removing the "Expires" statement is so controversial.

Joe

From melinda.shore@gmail.com  Sat Sep  8 11:59:56 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3E821F84E7 for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 11:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.413
X-Spam-Level: 
X-Spam-Status: No, score=-3.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAEc8psbIZ5c for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 11:59:56 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id E526821F84E6 for <ietf@ietf.org>; Sat,  8 Sep 2012 11:59:55 -0700 (PDT)
Received: by dadf8 with SMTP id f8so471937dad.31 for <ietf@ietf.org>; Sat, 08 Sep 2012 11:59:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=EjvGf9GrznYFN/8FHGgRFgMMKeHnQrvwoFp1IyCeXpc=; b=jlwhrBAMH7dmuh45rDX9yg54Tt7QxzbU+58iz3+rcFb2iLXKXiRieGf05rXU5wI4RF RNdzosQ4OdY9l9XSk1k/IqeGEqW/FKHmKuf8FWy8gijyOP/akJIsAKV4Z1XbqCSuUX2V 3JYvGFVhB772ML/BMhln+TXPxsUQGSidhG76gEH1nSm0OoNioXuR5yryQtO/J3bBSfpV /c1H/if4z/ehl5Bdsj8ZkVOtlG82OALfVupSp5ZL0G6gVbvWJ3aShAjYmDs5XvaILbO0 lQS2TXug4KcpKdUtPHZBZrfMZbg1JHBGBzlH0+IsjmFuXDF+A5/I/xVunkFdabKLALBR Ygcg==
Received: by 10.68.222.102 with SMTP id ql6mr16854528pbc.72.1347130795737; Sat, 08 Sep 2012 11:59:55 -0700 (PDT)
Received: from spandex.local (66-230-80-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.245]) by mx.google.com with ESMTPS id or1sm5761629pbb.10.2012.09.08.11.59.54 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 08 Sep 2012 11:59:54 -0700 (PDT)
Message-ID: <504B95A8.2070301@gmail.com>
Date: Sat, 08 Sep 2012 10:59:52 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net>	<504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com>	<504A1604.2020000@isi.edu>	<6.2.5.6.2.20120907085007.0aaa2d38@resistor.net>	<504AA4E7.8060000@isi.edu>	<CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504AFE51.1080705@gmail.com> <504B939F.8020002@isi.edu>
In-Reply-To: <504B939F.8020002@isi.edu>
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: Sat, 08 Sep 2012 18:59:56 -0000

On 9/8/12 10:51 AM, Joe Touch wrote:
> Nothing about an ID is inherently obsolete or out of date after 6 months
> except its being publicly available on authorized sites (up until now).

I think this is absolutely incorrect.  Internet Drafts are IETF
documents, and expiration changes the relationship between the draft
and the IETF.  I have to say that I think it's terribly unprofessional
not to hang onto archival material and frankly it's in the interest
of the IETF as an *open* standards organization to keep archival
material accessible.

When you're working on a problem that's been around forever and
still hasn't been solved (like, oh, I dunno - firewall/NAT traversal?),
easy access to expired drafts is an enormous help.

Would you be more comfortable if there were some sort of visual
flag that a draft had expired?

Melinda


From sm@resistor.net  Sat Sep  8 13:56:11 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47C5521F84EC for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 13:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rk-4Wx+oV0Pe for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 13:56:10 -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 A697C21F84EA for <ietf@ietf.org>; Sat,  8 Sep 2012 13:56:10 -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 q88KtvbI006394; Sat, 8 Sep 2012 13:56:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1347137769; bh=PT2Qn4TJJ0ymWu0yRl0Jq+XegH9NBxt/Nt3tnEJx/lY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ri8ujXl48JauBECYX3QbitMTYSCFibyx+cCVuf8Eo3Tq9Mh2RGyxtVf2lz4+dwhN+ 3xD4P63tNjU4z5t/Q+3U1qNxqrh/h3FifMd++5tph0c31opK7mQ/HpNTxAF9oH7Ujq PIadeEuMaXRokxLe1APdDS7OjsCiIko+k6yZng00=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1347137769; i=@resistor.net; bh=PT2Qn4TJJ0ymWu0yRl0Jq+XegH9NBxt/Nt3tnEJx/lY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vYtDN7l2mTjv56lfJGtjxWuGFcXwRt3Vc3HHosLAVaGx/ms4P7CGA/3tfUiVylj9N ++T6zxFiT6d749mcyTvXWmVdspxz4jpUFZMU4TMhupShvaw7czt0f4Nf40myTrM8Nj /M5R+hMxZ5fQH9cxg1z4QMar+frjqgz8gnZ4nBr4=
Message-Id: <6.2.5.6.2.20120908121713.093892f0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 08 Sep 2012 13:53:34 -0700
To: Joe Touch <touch@isi.edu>
From: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <504B939F.8020002@isi.edu>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net> <504AA4E7.8060000@isi.edu> <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504AFE51.1080705@gmail.com> <504B939F.8020002@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 08 Sep 2012 20:56:11 -0000

Hi Joe,
At 11:51 08-09-2012, Joe Touch wrote:
>Note - I don't agree that past IDs should be posted after expiration 
>without the author's consent. They were submitted with that 
>understanding, and post-facto changing it by the IETF is not appropriate.

I would rephrase the above as whether it is appropriate to take 
someone's work and post it as your own or use the work.  For the 
former, I don't think it is appropriate.  For the latter, the author 
has given the IETF change control over the work.  I'll ignore the 
exceptions.  That does not mean that the author should not be 
credited for the work.  If I am not mistaken it is IETF practice to do so.

"An expired I-D may be unexpired when necessary to further the work 
of the IETF, including IETF liaison with other standards 
bodies".  The IETF Trust has a retention policy of forever for 
I-Ds.  It is possible to use the override in extreme cases.  That 
does not mean that things should be done without the author's consent.

Regards,
-sm 


From touch@isi.edu  Sat Sep  8 18:36:34 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CDBC21F84E6 for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 18:36:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.012
X-Spam-Level: 
X-Spam-Status: No, score=-103.012 tagged_above=-999 required=5 tests=[AWL=-0.413, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id phoIa4wp+xCm for <ietf@ietfa.amsl.com>; Sat,  8 Sep 2012 18:36:33 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id C6AEF21F84D3 for <ietf@ietf.org>; Sat,  8 Sep 2012 18:36:33 -0700 (PDT)
Received: from [192.168.1.92] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q891a6Dv019928 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 8 Sep 2012 18:36:09 -0700 (PDT)
Message-ID: <504BF285.7050404@isi.edu>
Date: Sat, 08 Sep 2012 18:36:05 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>	<6.2.5.6.2.20120905005713.08dde888@resistor.net>	<CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com>	<6.2.5.6.2.20120905063923.0b328fe0@resistor.net>	<504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com>	<504A1604.2020000@isi.edu>	<6.2.5.6.2.20120907085007.0aaa2d38@resistor.net>	<504AA4E7.8060000@isi.edu>	<CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504AFE51.1080705@gmail.com> <504B939F.8020002@isi.edu> <504B95A8.2070301@gmail.com>
In-Reply-To: <504B95A8.2070301@gmail.com>
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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Sep 2012 01:36:34 -0000

On 9/8/2012 11:59 AM, Melinda Shore wrote:
> On 9/8/12 10:51 AM, Joe Touch wrote:
>> Nothing about an ID is inherently obsolete or out of date after 6 months
>> except its being publicly available on authorized sites (up until now).
>
> I think this is absolutely incorrect.  Internet Drafts are IETF
> documents, and expiration changes the relationship between the draft
> and the IETF.  I have to say that I think it's terribly unprofessional
> not to hang onto archival material

Draft != archival

Or do you keep copies of all versions of papers you publish, including 
the ones submitted for review? In case lawyers might need it, or for the 
benefit of the public?

> and frankly it's in the interest
> of the IETF as an *open* standards organization to keep archival
> material accessible.

Agreed.

> When you're working on a problem that's been around forever and
> still hasn't been solved (like, oh, I dunno - firewall/NAT traversal?),
> easy access to expired drafts is an enormous help.

The needs of the community - including the lawyers - do not outweigh the 
rights of the author or the agreement they make with the IETF to date.

The original point of having drafts expire seems to have been forgotten 
here. That's a pity. It did have a reason, and it was useful.

> Would you be more comfortable if there were some sort of visual
> flag that a draft had expired?

If you post it, it's not expired. There's no point in claiming otherwise.

Joe

From robert@raszuk.net  Sun Sep  9 04:00:05 2012
Return-Path: <robert@raszuk.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 138E621F84D7 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 04:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_ABOUTYOU=0.5]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDC-GHvX9TPX for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 04:00:04 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 0082E21F8437 for <ietf@ietf.org>; Sun,  9 Sep 2012 04:00:03 -0700 (PDT)
Received: (qmail 7622 invoked by uid 399); 9 Sep 2012 11:01:05 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.13.163.62) by mail1310.opentransfer.com with ESMTPM; 9 Sep 2012 11:01:05 -0000
X-Originating-IP: 83.13.163.62
Message-ID: <504C76B2.9080304@raszuk.net>
Date: Sun, 09 Sep 2012 13:00:02 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com> <504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net> <504AA4E7.8060000@isi.edu> <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504AFE51.1080705@gmail.com> <504B939F.8020002@isi.edu> <6.2.5.6.2.20120908121713.093892f0@resistor.net>
In-Reply-To: <6.2.5.6.2.20120908121713.093892f0@resistor.net>
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: robert@raszuk.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Sep 2012 11:00:05 -0000

>> Note - I don't agree that past IDs should be posted after expiration
>> without the author's consent. They were submitted with that
>> understanding, and post-facto changing it by the IETF is not appropriate.
>
> I would rephrase the above as whether it is appropriate to take
> someone's work and post it as your own or use the work.  For the former,
> I don't think it is appropriate.  For the latter, the author has given
> the IETF change control over the work.  I'll ignore the exceptions.
> That does not mean that the author should not be credited for the work.
> If I am not mistaken it is IETF practice to do so.

Actually regarding reusing the former drafts we have been discussing 
this in 2008 at depth when one draft reused most of the text of another 
draft.

The end result was that technically and legally it is appropriate. 
Reference section 3.3 of BCP78 / RFC5378.

However while the above documents do not mandate it I very much agree 
that it is in good taste to first ping the original authors about your 
intentions to extend and build on top of their idea.

R.



From barryleiba.mailing.lists@gmail.com  Sun Sep  9 08:33:26 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE3E421F84D7; Sun,  9 Sep 2012 08:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.935
X-Spam-Level: 
X-Spam-Status: No, score=-102.935 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWWz-zkp7v3s; Sun,  9 Sep 2012 08:33:26 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id B5D3221F84B2; Sun,  9 Sep 2012 08:33:25 -0700 (PDT)
Received: by lahm15 with SMTP id m15so670548lah.31 for <multiple recipients>; Sun, 09 Sep 2012 08:33:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=dAw/tVm17BEH1lyk1a5VvINjDvtUlsWxfeYyL3cWLzA=; b=UuhDvXwEMRD+3MvFgidFn7/maEXTCuvQ3RIQnQvVO/AuvqfeX4u3hhr2/QDtmTWnBH vmBIvuySBUDHMd53ypZbbh+oL3+10r1XrZBK4zJeBLiIwjHnQsrXpBQSHbpITmU8Q7d5 Q6QYTBea2D1vscYfg6dsQtbVxkIXZnPKAwNyT18Z2aU16CH6ZLA7sGuJhBXLB1lwhiZO w25Uzu+EOocZdAcA3XifsVmaOKdMqMPOhqXYxNQco1ZkU8HPqOg7yCogBcmHqtxfXWJG cv9yyqSKpkCvV31wlIT3fyvnwSiNHExrpN+i2685+TOTTE7POqT2ldf1JJGMBKIF7yc3 43+g==
MIME-Version: 1.0
Received: by 10.152.104.44 with SMTP id gb12mr6957241lab.29.1347204804446; Sun, 09 Sep 2012 08:33:24 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.91.33 with HTTP; Sun, 9 Sep 2012 08:33:24 -0700 (PDT)
In-Reply-To: <20120906150526.5342.57611.idtracker@ietfa.amsl.com>
References: <20120906150526.5342.57611.idtracker@ietfa.amsl.com>
Date: Sun, 9 Sep 2012 11:33:24 -0400
X-Google-Sender-Auth: ElI_317zTH8MoKfBPUTaExAp7W0
Message-ID: <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com>
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email Messages) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: ietf@ietf.org, ima@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: Sun, 09 Sep 2012 15:33:26 -0000

> The IESG has received a request from the Email Address
> Internationalization WG (eai) to consider the following document:
> - 'Post-delivery Message Downgrading for Internationalized Email
> Messages'
>   <draft-ietf-eai-popimap-downgrade-07.txt> as Proposed Standard

Rats; I missed this in earlier review:

-- Section 3.2.1 --

   This procedure may generate empty <group> elements in "From:",
   "Sender:" and "Reply-To:" header fields.
   [I-D.leiba-5322upd-from-group] updates [RFC5322] to allow (empty)
   <group> elements in "From:", "Sender:" and "Reply-To:" header fields.

It does not.  It adds group syntax to "From" only.  Group syntax is
already allowed in "Reply-To", and the draft does not change the rules
for "Sender".

If this spec also needs "Sender" to change, I can update the
5322upd-from-group for that, but it's not there now.

Barry

From klensin@jck.com  Sun Sep  9 08:48:15 2012
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 F15F821F851B; Sun,  9 Sep 2012 08:48: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]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tod-2s4YUVl5; Sun,  9 Sep 2012 08:48:15 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 79F2521F84D6; Sun,  9 Sep 2012 08:48:15 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <klensin@jck.com>) id 1TAjk5-000Btl-HH; Sun, 09 Sep 2012 11:48:13 -0400
X-Vipre-Scanned: 04864E7D002C3104864FCA-TDI
Date: Sun, 09 Sep 2012 11:48:12 -0400
From: John C Klensin <klensin@jck.com>
To: Barry Leiba <barryleiba@computer.org>, ietf@ietf.org, ima@ietf.org
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email Messages) to Proposed Standard
Message-ID: <C69ED8A0C98787E4C29AA162@[192.168.1.128]>
In-Reply-To: <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com>
References: <20120906150526.5342.57611.idtracker@ietfa.amsl.com> <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Sep 2012 15:48:16 -0000

--On Sunday, September 09, 2012 11:33 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>...
> Rats; I missed this in earlier review:
> 
> -- Section 3.2.1 --
> 
>    This procedure may generate empty <group> elements in
> "From:",    "Sender:" and "Reply-To:" header fields.
>    [I-D.leiba-5322upd-from-group] updates [RFC5322] to allow
> (empty)    <group> elements in "From:", "Sender:" and
> "Reply-To:" header fields.
> 
> It does not.  It adds group syntax to "From" only.  Group
> syntax is already allowed in "Reply-To", and the draft does
> not change the rules for "Sender".
> 
> If this spec also needs "Sender" to change, I can update the
> 5322upd-from-group for that, but it's not there now.

Barry, I think it does.  The presumption (since before 822) has
been that "Sender:" can contain any address that can appear in
"From:".   The ancient history is that "From:" need not even
contain a deliverable address if "Sender:" is specified to match
a business correspondence model in which:

    From: "Big boss who doesn't use computers"
    Sender: Assistanct-to-boss@example.com

has to be legitimate.  5322 and its predecessors took some of
that capability away, but the only difference now is that
"From:" can take a list of mailboxes and "Sender:" can take only
one.

I think 5322upd-from-group needs to apply to both
backward-pointing address types to be effective for what
popimap-downgrade needs.

Sorry for not finding this in my reviews -- I should have.

    john




From barryleiba@gmail.com  Sun Sep  9 08:53:00 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F5921F8513; Sun,  9 Sep 2012 08:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.936
X-Spam-Level: 
X-Spam-Status: No, score=-102.936 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y2V9SAO1dbUA; Sun,  9 Sep 2012 08:53:00 -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 EC2D821F84F8; Sun,  9 Sep 2012 08:52:59 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so302716vcb.31 for <multiple recipients>; Sun, 09 Sep 2012 08:52:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wHWc2Auyk91xXKC4DSP61nLKsdSFUwhQ+Uh2DTYDFSo=; b=YtlZ6/u4ZBR771KMS48WKwB0MNujhs38kV01sjYgF1LeA0bo/pIJwiBYO20N/Xl3Yi 9bIDfjBixouonbbdb2sU3c8WOyoPQokFogIC1dzuj5gtpiT3LSDr4XDJh7xDYLRgufsa wkiUsYpYvW2zLwclpOoeNsxfGhOtacfd9bVKlHt2VGmgoEY/Ki56uLzgI2+m+6V+v2Oj GL2SHH7qPqUHkPRY2YfQ8rZ6V3vaWabyVbkdsYFou3hwF5ZMw8ThFf6Z8ar5bSOXg/Fi zNNhUw5YJp45rTU4xFbJHtX1jjd41CIvn6J86rLO+qYKdiSueB/LDVcz243qfO+oBNPx leRA==
MIME-Version: 1.0
Received: by 10.58.102.80 with SMTP id fm16mr2246940veb.2.1347205979486; Sun, 09 Sep 2012 08:52:59 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Sun, 9 Sep 2012 08:52:59 -0700 (PDT)
In-Reply-To: <C69ED8A0C98787E4C29AA162@192.168.1.128>
References: <20120906150526.5342.57611.idtracker@ietfa.amsl.com> <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com> <C69ED8A0C98787E4C29AA162@192.168.1.128>
Date: Sun, 9 Sep 2012 11:52:59 -0400
X-Google-Sender-Auth: -YswM3VsZxRz7NBbWv5fZjD2kKQ
Message-ID: <CALaySJJyqppmdNUSGFYXG0qWLwTTu1Y_U4sZDiaLgDM-ytpDCw@mail.gmail.com>
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email Messages) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <klensin@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, ima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Sep 2012 15:53:00 -0000

> I think 5322upd-from-group needs to apply to both
> backward-pointing address types to be effective for what
> popimap-downgrade needs.

I will make the change.  I'll also remind the EAI group that there
have been a couple of objections to the 5322upd-from-group spec, which
I have to address.  I might do that by scoping it down a bit with some
"SHOULD NOT use" sort of language to address those concerns.  Have to
review them and see.

> Sorry for not finding this in my reviews -- I should have.

As should I have.  Flrg.

Barry

From barryleiba@gmail.com  Sun Sep  9 08:55:49 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 505D521F8522; Sun,  9 Sep 2012 08:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.937
X-Spam-Level: 
X-Spam-Status: No, score=-102.937 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PFrjBoVMTysz; Sun,  9 Sep 2012 08:55:48 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id AE9E521F851B; Sun,  9 Sep 2012 08:55:48 -0700 (PDT)
Received: by vbal1 with SMTP id l1so1854084vba.31 for <multiple recipients>; Sun, 09 Sep 2012 08:55:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=bGnmI7TS/iVNaJr0FDOIr2Xvb084KKJR6IWAsxF1KDk=; b=kfMBxHb8SIx6QG7BYjWJZmwI7NoKayqXmeeiFsBAdrCQn013eEEBca64Nk3gJPFqe+ ronmMCieD/c+gqk0tzUPsyGGOjzb/HltwVni6SGih9EC602SibAzGvFiUkJK1u74UPQX 0OXN4OHiVkcUKAHrhvbIUjUOfojy8sbKclRn7mnq5xefOk79qgUahuCbbptw6gXj5K0c EhoCaQAFpOnREVQV4LgdZ5BYwx9UL75PHniijUbyECSY+BXsM24wWJw71llqp9j3BUW3 4sii26OkrwyNFTzKh0cbUpZbq8WrkA28hX/Zwsj8fMGT7ixTDI76xVQEuap6Wwe/5VK1 JAbw==
MIME-Version: 1.0
Received: by 10.220.149.6 with SMTP id r6mr15270571vcv.53.1347206143675; Sun, 09 Sep 2012 08:55:43 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Sun, 9 Sep 2012 08:55:43 -0700 (PDT)
In-Reply-To: <CALaySJJyqppmdNUSGFYXG0qWLwTTu1Y_U4sZDiaLgDM-ytpDCw@mail.gmail.com>
References: <20120906150526.5342.57611.idtracker@ietfa.amsl.com> <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com> <C69ED8A0C98787E4C29AA162@192.168.1.128> <CALaySJJyqppmdNUSGFYXG0qWLwTTu1Y_U4sZDiaLgDM-ytpDCw@mail.gmail.com>
Date: Sun, 9 Sep 2012 11:55:43 -0400
X-Google-Sender-Auth: gUA6Eqyn-EIbBpR7VNVX577851I
Message-ID: <CALaySJKR8r_Zk8kFgvxHWiAGZOBkanPXOXe662k=xMkRMAqgMg@mail.gmail.com>
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email Messages) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <klensin@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, ima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Sep 2012 15:55:49 -0000

>> I think 5322upd-from-group needs to apply to both
>> backward-pointing address types to be effective for what
>> popimap-downgrade needs.
>
> I will make the change.

But in any case, the downgrade doc needs to remove "reply-to" from the
list of header fields that 5322upd-from-group changes.  Maybe this:

OLD
   This procedure may generate empty <group> elements in
   "From:", "Sender:" and "Reply-To:" header fields.
   [I-D.leiba-5322upd-from-group] updates [RFC5322] to allow
   (empty) <group> elements in "From:", "Sender:" and
   "Reply-To:" header fields.

NEW
   This procedure may generate empty <group> elements in
   "From:",    "Sender:" and "Reply-To:" header fields.
   [I-D.leiba-5322upd-from-group] updates [RFC5322] to allow
   (empty) <group> elements in "From:" and "Sender:".

Barry

From john-ietf@jck.com  Sun Sep  9 09:15:23 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8442021F8523; Sun,  9 Sep 2012 09:15: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xn-0KmyFzfxA; Sun,  9 Sep 2012 09:15:23 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EF1F721F8522; Sun,  9 Sep 2012 09:15:22 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TAkAM-000C0e-3j; Sun, 09 Sep 2012 12:15:22 -0400
X-Vipre-Scanned: 049F282F002C31049F297C-TDI
Date: Sun, 09 Sep 2012 12:15:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email Messages) to Proposed Standard
Message-ID: <F2031A4E98AC2BDE461710FF@[192.168.1.128]>
In-Reply-To: <CALaySJJyqppmdNUSGFYXG0qWLwTTu1Y_U4sZDiaLgDM-ytpDCw@mail.gmail.com>
References: <20120906150526.5342.57611.idtracker@ietfa.amsl.com> <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com> <C69ED8A0C98787E4C29AA162@192.168.1.128> <CALaySJJyqppmdNUSGFYXG0qWLwTTu1Y_U4sZDiaLgDM-ytpDCw@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, ima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Sep 2012 16:15:23 -0000

--On Sunday, September 09, 2012 11:52 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>> I think 5322upd-from-group needs to apply to both
>> backward-pointing address types to be effective for what
>> popimap-downgrade needs.
> 
> I will make the change.  I'll also remind the EAI group that
> there have been a couple of objections to the
> 5322upd-from-group spec, which I have to address.  I might do
> that by scoping it down a bit with some "SHOULD NOT use" sort
> of language to address those concerns.  Have to review them
> and see.

My suggestion is to say something like the following:

	A great deal of Internet email procedures and software
	assume that the addresses in "From:" and "Sender:"
	fields can be replied to and are suitable for use in
	mail organizing and filtering.  The use of groups
	instead of mailboxes may disrupt those uses.
	Consequently, with this specification legitimizes the
	use of group syntax, that syntax should be used in those
	fields only under special circumstances and with
	caution.  In particular, users and MUAs should generally
	not permit the use of group syntax in those fields in
	outgoing messages since the syntax will usually provide
	even less information than a null address ("<>") which
	is already prohibited by RFC 5321.

That could be either in Security Considerations or a separate
section.  You could even do something radical and incorporate it
as a section called "Applicability" and use the words "LIMITED
USE" (and, since no one seems to remember, a citation of RFC
2026 Section 3.3).   You can probably figure out how to use
fewer words, but something like that would address the comments
I've seen so far and, IMO, generally strengthen the spec.

best,
   john




From johnl@iecc.com  Sun Sep  9 11:44:13 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06AC921F8551 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 11:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZcXflX-6Zuk7 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 11:44:12 -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 D4A1221F8437 for <ietf@ietf.org>; Sun,  9 Sep 2012 11:44:11 -0700 (PDT)
Received: (qmail 93189 invoked from network); 9 Sep 2012 18:44:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 9 Sep 2012 18:44:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504ce379.xn--btvx9d.k1208; i=johnl@user.iecc.com; bh=SdN2+lqV+gg8HzWvVwBHwbDkLvVsfLGSI4mI70qNhW4=; b=viIgH2H/xESebuLEm0YPUuyV/rB3IIEGOEESQVLlWBlCxFJaUpm0/SsKUZhFzE6Hp+TJC0MYL/Rathx+1dzkvOi5M1D0T+KX2RvMsZGSmkxXMJkUkNI0L/pbEyMz8kgyjxAgUWO3zm4vg8IenKC+KCRokGaRA8+hW9u6bagcgJA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504ce379.xn--btvx9d.k1208; olt=johnl@user.iecc.com; bh=SdN2+lqV+gg8HzWvVwBHwbDkLvVsfLGSI4mI70qNhW4=; b=KQEweSl+eKH/o2JGbCgSA/jRAxNpByJijbL4NJxLBudj0meit4OFxBdz8J8tqcRL7uWbXeJZhObLwmw5l4X8Z1Zy/sbwTZoO9tAUWuxov1Za6dcaFjLI2SSnsdZeZG1QlANW9TfWKbr+cInMrTkKYB6EVkBBBzkodGcB5NmpdTM=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 9 Sep 2012 18:43:47 -0000
Message-ID: <20120909184347.32346.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <50499912.9050806@cisco.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, 09 Sep 2012 18:44:13 -0000

>NEW:
>
>> An I-D MAY be removed from the public I-D archive in compliance
>> with a competent legal demand.  If possible, a removed I-D will be
>> replaced with a tombstone file that describes the reason that the I-D
>> was removed from the public I-D archive.
>
>This leaves sufficient flexibility for the IESG to decide when a legal
>demand requires the removal and when it's bogus, but otherwise leaves
>the bar high.  I would suggest that Jorge review the above text for
>appropriateness.

Let's say I write to the IESG and say this:

  Due to a late night editing error, draft-foo-bar-42 which I
  submitted yesterday contains several paragraphs of company
  confidential information which you can easily see are irrelevant to
  the draft.  My boss wants it taken down pronto, even though he
  realizes that third parties may have made copies of it in the
  meantime.  I will probably lose my job if it stays up for more than a
  few days.  Thanks for your consideration.

Is this the response?

  You didn't make any legal threats, and now that we know the
  situation, we wouldn't believe any legal threats you might make in the
  future, so you better check out those burger flipping opportunities.

What was wrong with the original version which gave the IESG the
latitude to remove an I-D if they feel, for whatever reason, that it
would be a good idea to do so?  If the IESG were so screwed up that
they started deleting I-Ds for bad reasons, no amount of process
verbiage would help.

R's,
John

From ned+ietf@mauve.mrochek.com  Sun Sep  9 12:07:09 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498A021F857A for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 12:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YHhjDVJ0kvEE for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 12:07:08 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id B02BD21F856C for <ietf@ietf.org>; Sun,  9 Sep 2012 12:07:08 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OK1UU5T7W0008WV7@mauve.mrochek.com> for ietf@ietf.org; Sun, 9 Sep 2012 12:02:07 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJFFFOH4280006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sun, 9 Sep 2012 12:02:06 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OK1UU567QY0006TF@mauve.mrochek.com>
Date: Sun, 09 Sep 2012 12:01:44 -0700 (PDT)
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email	Messages) to Proposed Standard
In-reply-to: "Your message dated Sun, 09 Sep 2012 11:33:24 -0400" <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120906150526.5342.57611.idtracker@ietfa.amsl.com> <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: ietf@ietf.org, ima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Sep 2012 19:07:09 -0000

> > The IESG has received a request from the Email Address
> > Internationalization WG (eai) to consider the following document:
> > - 'Post-delivery Message Downgrading for Internationalized Email
> > Messages'
> >   <draft-ietf-eai-popimap-downgrade-07.txt> as Proposed Standard

> Rats; I missed this in earlier review:

> -- Section 3.2.1 --

>    This procedure may generate empty <group> elements in "From:",
>    "Sender:" and "Reply-To:" header fields.
>    [I-D.leiba-5322upd-from-group] updates [RFC5322] to allow (empty)
>    <group> elements in "From:", "Sender:" and "Reply-To:" header fields.

> It does not.  It adds group syntax to "From" only.  Group syntax is
> already allowed in "Reply-To", and the draft does not change the rules
> for "Sender".

> If this spec also needs "Sender" to change, I can update the
> 5322upd-from-group for that, but it's not there now.

I think the answer to that is yes, this needs to be allowed for "Sender".

				Ned

From johnl@iecc.com  Sun Sep  9 12:26:21 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99B6D21F84E6 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 12:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g1jxNGBLDOI1 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 12:26:21 -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 BB7A321F847F for <ietf@ietf.org>; Sun,  9 Sep 2012 12:26:20 -0700 (PDT)
Received: (qmail 6616 invoked from network); 9 Sep 2012 19:26:19 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 9 Sep 2012 19:26:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504ced5b.xn--hew.k1208; i=johnl@user.iecc.com; bh=uthJgGn55sf6ncaj+fdEOXkpyTEIFWJ3kRwqK/Ton/s=; b=EbMIVNP2akItNmdAH612HXAK7c5qIvKs/eO5WV5eGyWGSHrtcqQoNW/P+RrA9laadAbV8akRYbLkfNN0h5A9avWn0And4OeM2xQqhGOIqMqa47qOJhuec0XWtFKekwHZjiwGNNEhL7lUf0ePtzuRavmqeGF3F+4NRLjXGxt/RLk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504ced5b.xn--hew.k1208; olt=johnl@user.iecc.com; bh=uthJgGn55sf6ncaj+fdEOXkpyTEIFWJ3kRwqK/Ton/s=; b=VJtjT8xTyeUjWn6xBrvvOTlknqRbqhshKOJF0DAY1WnrdkkNgEZN/6S6CJdPN4SwXJ3OvfKEXIieEPm4O/ktWqh1V9DT+1xwWnGV6aPMwgDgwGWfZDJqsqiFowsQHaaJ/Y0qdqIz0CH4accm5w7PDlRH68CN9fBvJHZTSYubqVk=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 9 Sep 2012 19:25:57 -0000
Message-ID: <20120909192557.33735.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
In-Reply-To: <504A4C9B.4010900@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Sep 2012 19:26:21 -0000

I have to say that I'm baffled at the perverse pride that people seem
to take in being so technically backward that they're unable to handle
the mail that 99% of the world uses today.  While not being a fan of
overdecorated HTML and endless font changes, and strongly preferring a
mail program that lets me keep my fingers on the keyboard, I can deal
with it.  (I use Alpine, keep meaning to take another look at mutt.)
I remember how to punch drum cards, but I have no interest in using
one to send mail in 2012.

For the large majority of mail that is written in paragraphs rather
than tables, line wrapping is a useful feature, regardless of the
character set, particularly for those of us who sometimes read our
mail on a tablet or phone while changing planes.  For mail that is a
table and stuff has to line up in columns, use HTML tables. That's
what they're for.

R's,
John

PS: Yes, this is top posted.  You can deal with that, too.

>Unfortunately there's some stuff going around that line
>wrapping with hard line terminations is retrograde and goes
>back to punch cards.  I guess that's probably true but
>aside from the fact that I'm retrograde and go back to
>punch cards, myself, application line wrapping and flowed
>text don't deal well (yet) with multiple character sets,
>fonts, etc. and I'll take readability over application
>purity every single time.


From ned+ietf@mauve.mrochek.com  Sun Sep  9 12:34:06 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 054F221F8574 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 12:34: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LtdnzXRQvLXx for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 12:34:05 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8CEFE21F8567 for <ietf@ietf.org>; Sun,  9 Sep 2012 12:34:05 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OK1VRL5M00008L2D@mauve.mrochek.com> for ietf@ietf.org; Sun, 9 Sep 2012 12:29:04 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJFFFOH4280006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sun, 9 Sep 2012 12:29:02 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OK1VRJUJMC0006TF@mauve.mrochek.com>
Date: Sun, 09 Sep 2012 12:28:46 -0700 (PDT)
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email	Messages) to Proposed Standard
In-reply-to: "Your message dated Sun, 09 Sep 2012 11:55:43 -0400" <CALaySJKR8r_Zk8kFgvxHWiAGZOBkanPXOXe662k=xMkRMAqgMg@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120906150526.5342.57611.idtracker@ietfa.amsl.com> <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com> <C69ED8A0C98787E4C29AA162@192.168.1.128> <CALaySJJyqppmdNUSGFYXG0qWLwTTu1Y_U4sZDiaLgDM-ytpDCw@mail.gmail.com> <CALaySJKR8r_Zk8kFgvxHWiAGZOBkanPXOXe662k=xMkRMAqgMg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: John C Klensin <klensin@jck.com>, ietf@ietf.org, ima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Sep 2012 19:34:07 -0000

> >> I think 5322upd-from-group needs to apply to both
> >> backward-pointing address types to be effective for what
> >> popimap-downgrade needs.
> >
> > I will make the change.

> But in any case, the downgrade doc needs to remove "reply-to" from the
> list of header fields that 5322upd-from-group changes.  Maybe this:

> OLD
>    This procedure may generate empty <group> elements in
>    "From:", "Sender:" and "Reply-To:" header fields.
>    [I-D.leiba-5322upd-from-group] updates [RFC5322] to allow
>    (empty) <group> elements in "From:", "Sender:" and
>    "Reply-To:" header fields.

> NEW
>    This procedure may generate empty <group> elements in
>    "From:",    "Sender:" and "Reply-To:" header fields.
>    [I-D.leiba-5322upd-from-group] updates [RFC5322] to allow
>    (empty) <group> elements in "From:" and "Sender:".

Looks like the correct change to me.

				Ned

From melinda.shore@gmail.com  Sun Sep  9 12:36:35 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB6C521F8575 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 12:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.437
X-Spam-Level: 
X-Spam-Status: No, score=-3.437 tagged_above=-999 required=5 tests=[AWL=0.162,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vJ2MZjbx9Q55 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 12:36:35 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 22D5421F855F for <ietf@ietf.org>; Sun,  9 Sep 2012 12:36:35 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so1409353pbb.31 for <ietf@ietf.org>; Sun, 09 Sep 2012 12:36:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ch7h0iDlkmuiCApXxpGV5gNWJnavOK3YOFke72yViLk=; b=mxZt+mOILCOgUC5XofIsd7ToPlrGmzJvTPV87fZqyavTKclAGFKDgMmrvFsPNcHQMP Y0ttc2AKXm+qnKc5o9h/fy81q/An0uaz0sWaUWZ5Cb+Hq2JpFwLwd/5oW8fjZz9A9Ddv nzQSApTynzNvPuT/h46husgb3c8PCQk5ZBPWUVbcq1H2wqWyqtDRUCvU1Ch1bu1+VdwL q6nkIKBxYIVzgvL20sS1AftEpDxnPdr9UVPtNrJWKA4TO7G2GXrfQEkXumoaCwprBUv8 2HQzu9PgYegQ7xaOmNjM1l/uJ0OH4d5//wDOUx1UfSl3Yn4D+t5KQO9fzIxryGrGGW50 C9uA==
Received: by 10.68.240.236 with SMTP id wd12mr1714675pbc.83.1347219392669; Sun, 09 Sep 2012 12:36:32 -0700 (PDT)
Received: from spandex.local (66-230-80-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.245]) by mx.google.com with ESMTPS id qf4sm6724102pbc.1.2012.09.09.12.36.30 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 09 Sep 2012 12:36:31 -0700 (PDT)
Message-ID: <504CEFBC.6000701@gmail.com>
Date: Sun, 09 Sep 2012 11:36:28 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
References: <20120909192557.33735.qmail@joyce.lan>
In-Reply-To: <20120909192557.33735.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, 09 Sep 2012 19:36:35 -0000

On 9/9/12 11:25 AM, John Levine wrote:
> I have to say that I'm baffled at the perverse pride that people seem
> to take in being so technically backward that they're unable to handle
> the mail that 99% of the world uses today.

99% (I made up a number!) of the world is sending fairly
straightforward email within one language group and one set of
recipients.  IETF participants use a heterogeneous set of
technologies and that seems to me to be a very good thing.
It seems reasonable to me to keep the formatting
that needs to be applied by the mail reader to a minimum.
There's some stuff that's being sent that is extremely
difficult to pull apart.

Melinda


From barryleiba@gmail.com  Sun Sep  9 14:01:24 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E01DA21F8469; Sun,  9 Sep 2012 14:01:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.938
X-Spam-Level: 
X-Spam-Status: No, score=-102.938 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SpVdIbTQGmxt; Sun,  9 Sep 2012 14:01:24 -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 D045121F8564; Sun,  9 Sep 2012 14:01:23 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so490834vcb.31 for <multiple recipients>; Sun, 09 Sep 2012 14:01:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Wf5mMcqTls0FNXTVz1JDnaUU6U1RquzQAiQ+9ZYTzxM=; b=VsDjZqeUBUpebTVEENZEpkETW+wUy0RZMcW17LGRK4en/G7my3ZwcKbRlISQ+jZgxj iFyo60ZDw81ev0QQRKplLnGO4UyGyimuLpqVS/VpT9chZ7dzmkIHXTqQtNNub5x/vAgj Dfrj6En5+v61L/iPYuFxZvbKThVwcKMnsfDitNmwt3MiRpKP+wmC7SNOWMVxW93gkmpu inyCnuHvDUIBuM2N3k/6qTSb+accJzq8EtZJAMb45d9OXFi+ZVf6yRufstU9PegnSXZ5 J+kjqjCbhGeztgUUngo9X/UQKe2uondTEHqV7RxmqnaAh+V77owallLcnMk3c+dgqLCc 6exg==
MIME-Version: 1.0
Received: by 10.220.149.6 with SMTP id r6mr16244321vcv.53.1347224483301; Sun, 09 Sep 2012 14:01:23 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Sun, 9 Sep 2012 14:01:23 -0700 (PDT)
In-Reply-To: <F2031A4E98AC2BDE461710FF@192.168.1.128>
References: <20120906150526.5342.57611.idtracker@ietfa.amsl.com> <CAC4RtVAf9dzEp1c=PaieZpDC085NSaKH9RUT2ugeK3F5ZbuOfQ@mail.gmail.com> <C69ED8A0C98787E4C29AA162@192.168.1.128> <CALaySJJyqppmdNUSGFYXG0qWLwTTu1Y_U4sZDiaLgDM-ytpDCw@mail.gmail.com> <F2031A4E98AC2BDE461710FF@192.168.1.128>
Date: Sun, 9 Sep 2012 17:01:23 -0400
X-Google-Sender-Auth: 2FWNwv5_NBoMGRfgyTNfwXFD6bY
Message-ID: <CALaySJJhRwO0qAq9GFB+X82DGnh53+jG8+Kj3-9i=zYJxJ7pBA@mail.gmail.com>
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email Messages) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, ima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Sep 2012 21:01:25 -0000

>> I will make the change.  I'll also remind the EAI group that
>> there have been a couple of objections to the
>> 5322upd-from-group spec, which I have to address.  I might do
>> that by scoping it down a bit with some "SHOULD NOT use" sort
>> of language to address those concerns.  Have to review them
>> and see.
>
> My suggestion is to say something like the following:
...
> That could be either in Security Considerations or a separate
> section.  You could even do something radical and incorporate it
> as a section called "Applicability" and use the words "LIMITED
> USE" (and, since no one seems to remember, a citation of RFC
> 2026 Section 3.3).

I have just posted drft-leiba-5322upd-from-group-04:
   http://datatracker.ietf.org/doc/draft-leiba-5322upd-from-group/

That changes the definition of Sender as well as From, and also adds a
new "Applicability Statement" section that has an edited version of
John's suggested text.  I like the result, and I hope others do as
well.  I will post something to the 5322upd-from-group thread, asking
that those who had objected look at the new text and see if they're
happy (or at least somewhat happier) with it.

Barry

From john-ietf@jck.com  Sun Sep  9 15:47:29 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8EF721F8445; Sun,  9 Sep 2012 15:47: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HHxNjNZktnvE; Sun,  9 Sep 2012 15:47:15 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 10E5021F85EA; Sun,  9 Sep 2012 15:47:07 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TAqHP-000D2X-Vp; Sun, 09 Sep 2012 18:47:04 -0400
X-Vipre-Scanned: 0605C4B0002C310605C5FD-TDI
Date: Sun, 09 Sep 2012 18:47:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Franck Martin <fmartin@linkedin.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email Messages) to Proposed Standard
Message-ID: <0893C01D4C3F0F63F04944D2@[192.168.1.128]>
In-Reply-To: <CC725DC8.57DBF%fmartin@linkedin.com>
References: <CC725DC8.57DBF%fmartin@linkedin.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, ima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Sep 2012 22:47:29 -0000

--On Sunday, September 09, 2012 21:58 +0000 Franck Martin
<fmartin@linkedin.com> wrote:

> I'm happier,
> 
> Made comments in another thread on why I believe it opens a
> security hole wider rather than trying to close it.
> 
> I guess I could leave with it, when this downgrade is only
> done from a SMTPUTF8 compatible MTA to an ASCII MTA.

But, as several people have tried to remind you, the EAI specs
are consistent with the prohibitions in RFC 5321, prohibitions
that expressedly forbid MTAs from changing addresses enrounte
(for downgrading or any other reason).  The specs in Last Call
now don't apply to MTAs or MTA actions _at all_.  They apply
_only_ to communication between an SMTPUTF8-compatible IMAP or
POP server and a legacy IMAP or POP client.

The experimental versions of the EAI specs did provide for
in-transit downgrading.   The main conclusion from those
experiments (described in RFC 6530, which I'd still encourage
you to read) was that such MTA->MTA downgrading was a bad idea.


So the WG agrees with you, so do the specs, and you are
attacking a (rather worn and threadbare) strawman.

Please focus on where this actually occurs and what the specs
actually say.  And, again, you might start by responding to
Ned's questions.

> I mean a SMTPUTF8 MTA MUST reject such downgrade.

With regard to whether it will tolerate group syntax in
backward-pointing header fields, the decision has absolutely
nothing to do with EAI and whether MTA is SMTPUTF8-capable or
not.  However, to get anything close to a "MUST reject", you'd
need to propose a very radical change to the way email is
specified.   In theory and largely in practice, MTAs deal with
envelopes, not header fields.  RFC 5321 and its successors are
carefully designed to never require that an MTA do anything with
header fields other than prepending information to them.   I
think we all recognize that mail filtering and classification
has created a lot of exceptions in which header fields (and
content) are inspected prior to the final delivery server.  Even
that typically occurs close to either the submission or final
delivery points.  I think you would get a _lot_ of resistance to
a change that would _require_ SMTP MTAs to inspect message
bodies (including header fields) to see if they contained some
offending construction.

> Let's not try to legitimize an attack vector (Friendly from
> having nothing to do with the author of the email).

I've seen no evidence at all that this does any such thing.

   john




From johnl@iecc.com  Sun Sep  9 17:49:49 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40A9521F858F for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 17:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6O8-8OGVk53w for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 17:49:48 -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 6FAB121F856D for <ietf@ietf.org>; Sun,  9 Sep 2012 17:49:48 -0700 (PDT)
Received: (qmail 60349 invoked from network); 10 Sep 2012 00:49:47 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 10 Sep 2012 00:49:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504d392b.xn--hew.k1208; i=johnl@user.iecc.com; bh=oRQsop+gHlAUmagkbARLjXx01vbNg3MLmXz14z3YMMg=; b=HC5JckiUQwx/S0KwmwDx9Cg1AQ1Vf+2szYt/2NAyUYgatpD/F9fT6MjFY2kUyhboahf8IEOGE6HDcP1VagwDK6BAVx9ekFsoKmbiWyN8P06F8rny1CFodTTOy+OI2K0H2RphaqST0cUbHeFvpawfBJ7E0YS4fY6nJtHgQwQKWWA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504d392b.xn--hew.k1208; olt=johnl@user.iecc.com; bh=oRQsop+gHlAUmagkbARLjXx01vbNg3MLmXz14z3YMMg=; b=mAL0vjMFf9DX3PpTlA6QogH6/xVfhMw5Q7P4dbTnr7QKuLoeXDWy0PX8MabsTgmQ3a/898Cy9ZzZnlaZvr5ibSUKLDWYuw3pfth2y/9uh2px3USW4Eu/wxQlQX6DTJvCLIJraXKIz/7BiraWjI54451nZc9GP3pS+GBBF41RfcE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 10 Sep 2012 00:49:25 -0000
Message-ID: <20120910004925.44193.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
In-Reply-To: <504CEFBC.6000701@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 00:49:49 -0000

>There's some stuff that's being sent that is extremely
>difficult to pull apart.

Really?  Like what?  (This is an honest question -- it's been
ages since I recall seeing a message that my fairly dorky
mail software couldn't handle.)

R's,
John

From randy@psg.com  Sun Sep  9 19:51:24 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED0121F8600 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 19:51: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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n56CzT9DQ4jl for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 19:51:23 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id A175421F847F for <ietf@ietf.org>; Sun,  9 Sep 2012 19:51:23 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TAu5q-0006Ox-01; Mon, 10 Sep 2012 02:51:22 +0000
Date: Mon, 10 Sep 2012 11:52:25 +0900
Message-ID: <m2a9wyy4gm.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "John Levine" <johnl@taugh.com>
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
In-Reply-To: <20120910004925.44193.qmail@joyce.lan>
References: <504CEFBC.6000701@gmail.com> <20120910004925.44193.qmail@joyce.lan>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 02:51:24 -0000

>> There's some stuff that's being sent that is extremely
>> difficult to pull apart.
> Really?  Like what?

try reading the nov3 list in a text mua.  and do not tell folk what mua
they should use.

randy

From johnl@taugh.com  Sun Sep  9 20:51:04 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CBE421F8534 for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 20:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.414
X-Spam-Level: 
X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id orQ+bJB54rVM for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 20:51: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 D7B2D21F852B for <ietf@ietf.org>; Sun,  9 Sep 2012 20:51:01 -0700 (PDT)
Received: (qmail 88557 invoked from network); 10 Sep 2012 03:51:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=159ec.504d63a4.k1209; bh=6nqC4X9Tivk4H3b3VNxcXuBGwaXy92b5OVmkAsR+xRU=; b=fqaxCJ3aR3pWKIw+1ID/OKiKJTGSg5Z4vLRtK8S+Hkh6AzskpVor+aGgeIumn9swbx4l6KxlkyDeiVZ9u3HCl6PvYXcBQuIpOu3Mb5EoBA72xmZrhY0xDkqpopX13ZnOKZDndebZx4E2vdkl+ILFAI055g+UA26c2lKMV+u6blE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=159ec.504d63a4.k1209; bh=6nqC4X9Tivk4H3b3VNxcXuBGwaXy92b5OVmkAsR+xRU=; b=dM3ks54hLgMdTb+3/ZkDWJjTh77eGYVrfmi2m7qgaVB6b8oKZMz143otkJLrCK1oT6dtYgJ0ZYDi/A0VhxViDUd6ifDbxrh31qbgDkRVA16E4VZ5q/c1fsJigB5+HDLSwMd+t/myDQW9w1aHfuuH9f8jdEF4kMID+il9vM1WYAA=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 10 Sep 2012 03:50:37 -0000
Date: 9 Sep 2012 23:50:59 -0400
Message-ID: <alpine.BSF.2.00.1209092350220.78149@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Randy Bush" <randy@psg.com>
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
In-Reply-To: <m2a9wyy4gm.wl%randy@psg.com>
References: <504CEFBC.6000701@gmail.com> <20120910004925.44193.qmail@joyce.lan> <m2a9wyy4gm.wl%randy@psg.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-357062251-1347249059=:78149"
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, 10 Sep 2012 03:51:04 -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-357062251-1347249059=:78149
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

> try reading the nov3 list in a text mua.  and do not tell folk what mua
> they should use.

Gee, this whole argument is about telling people what MUA to use.
Apparently nothing written since about 1996 need apply.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.
--3825401791-357062251-1347249059=:78149
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIIBgYJKoZIhvcNAQcCoIIH9zCCB/MCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBSMwggUfMIIEB6ADAgECAhBqmDwY4viwyBNv7hg7djRHMA0G
CSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRl
ciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01P
RE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDgyNzAwMDAwMFoX
DTEyMDgyNjIzNTk1OVowIDEeMBwGCSqGSIb3DQEJARYPam9obmxAdGF1Z2gu
Y29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArjjY2CfvJ3My
a2g1aOrImd0uJVLaah8aKJ8PSJJZth2vTQsMq3ozNxcZWKKRROOUfMeJWQDa
xl0J7d0XCdVjK40s+ZWKvlqwxLHCyIn4Enzk8lkoMq2qQUqnGaGbNQBxQK11
4JINMKOLMkP1WZgOwfDcROBhlKnK7FgNFgXouNS0nFUzosqlKOfYW6Ryl5rV
cLInOqGv78O/ekb9YtzHMVlrF9sKC5D8ijis0RY5uvdb47YCoKvI/Pm5g2wK
EYeD+sJXhSUp3zPct5VLDG1jrN2zjQEVrSFDQ/Ny58EnaNkOSMdE1tRQ7/Nf
ckoMGXqJRedbx7d/H62kGaDb7QrAawIDAQABo4IB3zCCAdswHwYDVR0jBBgw
FoAUehNOAHRbxnhjZCfBL+KgW7x5xXswHQYDVR0OBBYEFFNpWjhcj0fXS96W
ENsvzag4QY9yMA4GA1UdDwEB/wQEAwIFoDAMBgNVHRMBAf8EAjAAMCAGA1Ud
JQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgBhvhCAQEEBAMC
BSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYd
aHR0cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwVwYDVR0fBFAwTjBMoEqg
SIZGaHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVu
dGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNybDCBiAYIKwYBBQUHAQEEfDB6
MFIGCCsGAQUFBzAChkZodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9D
bGllbnRBdXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsG
AQUFBzABhhhodHRwOi8vb2NzcC5jb21vZG9jYS5jb20wGgYDVR0RBBMwEYEP
am9obmxAdGF1Z2guY29tMA0GCSqGSIb3DQEBBQUAA4IBAQB1BxfCpqDbjmN/
bGxym680l1in8LQqE0Vr/zbbz9lcDIPDdaQRDxtRkEf5KdlSrfLk23R0Ri9x
UQanAmVsFpboEhR/rmSdECdkImgAHd+ruZwNpbwX5+U8T0yaU0/Y/Xm+Rdfa
KuEJTVFsO9S6KsKkgTyDoeMoCRIER6ChQyRE51QCyREk9xt6aw03Vj42mZBq
v4mYNVpqzFLs9JLCotV7C9oViKip1UzYj3khybTrC0wn8Q+c99qr03YCpdD5
G+fotgtPEBomtRW4UnUBmZ3foBBah5mTSwPkaBC6p1yN+2qEy075c5tzT/EH
xs7UzXgqn87a8S6cROUqPtykd+NGMYICqzCCAqcCAQEwgagwgZMxCzAJBgNV
BAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcT
B1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQD
EzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1h
aWwgQ0ECEGqYPBji+LDIE2/uGDt2NEcwCQYFKw4DAhoFAKCB2DAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjA5MTAwMzUw
NTlaMCMGCSqGSIb3DQEJBDEWBBSsQmjIFJPrsKJa4WcuItW2L60rlzB5Bgkq
hkiG9w0BCQ8xbDBqMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0D
AgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASC
AQBF4SLbZO0JoeHuTb6OmSK6sn7Zs0FfAaFc06sDChLWXjBQwwGMJSfjrxLf
J+zVPWrgJCM2xpQD9pLDzAJKskkArnZTCAAr+UeOyoFHZpnXsFbrStVUDhSs
F2tY6UN2gWH0xIkd/rDzt7XKg/Gn7KUjb1NzMByxicKSLqS9npLNijrL5Y2l
3Bzfd9psbqdGYYdchVi5FDQiKftlEcGTr8AtTSBEw7o8ksaNPncumrmJa8ti
HGnymD3JNDTszXhSoa7TQZNXFAtRaUeS9c8DhxI5urJh/mepxksW1IHQMLu/
NHjEb4bB2+TO65WLScMO9kwkYIDbzh55t1J9FDgSUcK5

--3825401791-357062251-1347249059=:78149--

From lear@cisco.com  Mon Sep 10 00:33:49 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA2121F84FD for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 00:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.67
X-Spam-Level: 
X-Spam-Status: No, score=-110.67 tagged_above=-999 required=5 tests=[AWL=-0.071, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0wEsCY1rDesk for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 00:33:48 -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 8E7FB21F84F3 for <ietf@ietf.org>; Mon, 10 Sep 2012 00:33:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1714; q=dns/txt; s=iport; t=1347262428; x=1348472028; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WwKL2LRNoKeYAx+pefBB2keXzYht7nT5zV/DwEyXlaw=; b=RdNmFk5BqFJ6hWbIjhHmh4JMW5ahJOSkQaCzqkVph2tEVpTDS2/nFldH UfzVBeqfuoA7Tr82Fwq6z2+/PT/py9HLXose6lY8uO5RbY0cCv/GoC1FM bGhpg8D6D8EgHuv833Mhw1Ub/FdBQ7y6tkgsTNAmDDjhX6840CzsX8Xc0 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFACiXTVCQ/khL/2dsb2JhbABFhge1SYEHgiABAQEDARIBEFUBBQsLGAICBRYLAgIJAwIBAgFFBg0BBwEBHodoBpp+jRmSLoEhjxaBEgOLN4omhkuHa4Fngmg
X-IronPort-AV: E=Sophos;i="4.80,396,1344211200";  d="scan'208";a="7927187"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 10 Sep 2012 07:33:47 +0000
Received: from dhcp-10-55-94-127.cisco.com (dhcp-10-55-94-127.cisco.com [10.55.94.127]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q8A7XkLR031371 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Sep 2012 07:33:47 GMT
Message-ID: <504D97DB.3090205@cisco.com>
Date: Mon, 10 Sep 2012 09:33:47 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120909184347.32346.qmail@joyce.lan>
In-Reply-To: <20120909184347.32346.qmail@joyce.lan>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 07:33:49 -0000

Hi John,

On 9/9/12 8:43 PM, John Levine wrote:
> Let's say I write to the IESG and say this:
>
>   Due to a late night editing error, draft-foo-bar-42 which I
>   submitted yesterday contains several paragraphs of company
>   confidential information which you can easily see are irrelevant to
>   the draft.  My boss wants it taken down pronto, even though he
>   realizes that third parties may have made copies of it in the
>   meantime.  I will probably lose my job if it stays up for more than a
>   few days.  Thanks for your consideration.
>
> Is this the response?
>
>   You didn't make any legal threats, and now that we know the
>   situation, we wouldn't believe any legal threats you might make in the
>   future, so you better check out those burger flipping opportunities.

No, the response is that we refer you to our policy.  As an open
organization we do not remove information once posted, except under
extraordinary circumstances.

>
> What was wrong with the original version which gave the IESG the
> latitude to remove an I-D if they feel, for whatever reason, that it
> would be a good idea to do so?  

What original?  The draft policy states:

> An I-D will only be removed from the public I-D archive in compliance
> with a duly authorized court order.


> If the IESG were so screwed up that
> they started deleting I-Ds for bad reasons, no amount of process
> verbiage would help.

Certainly, but let's not start from the wrong place to begin with. 
Let's also set expectations that the IESG may be used to clean up after
other peoples' messes.  They have enough to do.

And again, this is best developed with counsel.

Regards,

Eliot

From fanf2@hermes.cam.ac.uk  Mon Sep 10 01:47:42 2012
Return-Path: <fanf2@hermes.cam.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 2839C21F84A2 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 01:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.392
X-Spam-Level: 
X-Spam-Status: No, score=-5.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hx+jLg0kTpOy for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 01:47:41 -0700 (PDT)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id EFD4821F8495 for <ietf@ietf.org>; Mon, 10 Sep 2012 01:47:40 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:40263) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:fanf2) id 1TAzed-0005P6-Wj (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 10 Sep 2012 09:47:39 +0100
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1TAzed-0008Le-3V (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 10 Sep 2012 09:47:39 +0100
Date: Mon, 10 Sep 2012 09:47:39 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Michael Richardson {quigon} <mcr@sandelman.ca>
Subject: Re: IETF...the unconference of SDOs
In-Reply-To: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
Message-ID: <alpine.LSU.2.00.1209100939010.9973@hermes-1.csi.cam.ac.uk>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
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, 10 Sep 2012 08:47:42 -0000

Michael Richardson {quigon} <mcr@sandelman.ca> wrote:

> Let me suggest that at the IETF, where the mailing list is king, you
> can't join the Elite if you can't quote email properly.  Maybe we should
> *state* this.

:-)

> Maybe I'm also concerned because many in the former "elite" have moved
> to Apple Mail, and it seems that it is bug compatible with Outlook in
> it's assumption that format=flowed is the default, an act which destroys
> email quoting, and therefore discussion.

I feel a bit sorry for Apple Mail. It used to use format=flowed very
nicely, but stopped presubably for bug compatibility with Outlook which
treats a flowed paragraph as a sequence of one-line paragraphs.

There are some other interop problems caused by Outlook's gratuitous
disregard for standards:

multipart/mixed; Content-Disposition: inline doesn't work very well.
(I predict Apple Mail will stop generating this too.)

message/rfc822 attachments don't work. If it did it would be a much better
way to do forwarding and top-posting repliesthan at present. (For
instance, Outlook can hide those horrible confusing email addresses rather
than stripping them out.)

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From Chris.Dearlove@baesystems.com  Mon Sep 10 03:47:03 2012
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C72321F8644 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 03:47:03 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nUjhUd32Z8H4 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 03:47:02 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 1201221F863F for <ietf@ietf.org>; Mon, 10 Sep 2012 03:47:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,396,1344207600"; d="scan'208";a="269565741"
Received: from unknown (HELO baemasmds009.greenlnk.net) ([141.245.68.246]) by baemasmds003ir.sharelnk.net with ESMTP; 10 Sep 2012 11:47:00 +0100
Received: from GLKXH0003V.GREENLNK.net ([10.109.2.34]) by baemasmds009.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id q8AAkxPr014889 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 10 Sep 2012 11:47:00 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.208]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.02.0309.002; Mon, 10 Sep 2012 11:46:59 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: the usual mail stuff, was IETF...the unconference of SDOs
Thread-Topic: the usual mail stuff, was IETF...the unconference of SDOs
Thread-Index: AQHNjSJFImKYt6uEXEWOfuwslkSlpZd/JFoAgAAEyICAAAYPAIAABCmAgAABnICAAyHhgIABETzg
Date: Mon, 10 Sep 2012 10:46:59 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24F5312E@GLKXM0002V.GREENLNK.net>
References: <504A4C9B.4010900@gmail.com> <20120909192557.33735.qmail@joyce.lan>
In-Reply-To: <20120909192557.33735.qmail@joyce.lan>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=utf-8
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, 10 Sep 2012 10:47:03 -0000

If someone wants to provide guidance on how to do a least bad job
with Outlook, that will be gratefully received. But advice that says
"don't use Outlook" will be filed with the advice that says "pick
another employer to work for".

--=20
Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=C2=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Joh=
n Levine
Sent: 09 September 2012 20:26
To: ietf@ietf.org
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs

----------------------! WARNING ! ----------------------
This message originates from outside our organisation,
either from an external partner or from the internet.
Keep this in mind if you answer this message.
Follow the 'Report Suspicious Emails' link on IT matters
for instructions on reporting suspicious email messages.
--------------------------------------------------------

I have to say that I'm baffled at the perverse pride that people seem
to take in being so technically backward that they're unable to handle
the mail that 99% of the world uses today.  While not being a fan of
overdecorated HTML and endless font changes, and strongly preferring a
mail program that lets me keep my fingers on the keyboard, I can deal
with it.  (I use Alpine, keep meaning to take another look at mutt.)
I remember how to punch drum cards, but I have no interest in using
one to send mail in 2012.

For the large majority of mail that is written in paragraphs rather
than tables, line wrapping is a useful feature, regardless of the
character set, particularly for those of us who sometimes read our
mail on a tablet or phone while changing planes.  For mail that is a
table and stuff has to line up in columns, use HTML tables. That's
what they're for.

R's,
John

PS: Yes, this is top posted.  You can deal with that, too.

>Unfortunately there's some stuff going around that line
>wrapping with hard line terminations is retrograde and goes
>back to punch cards.  I guess that's probably true but
>aside from the fact that I'm retrograde and go back to
>punch cards, myself, application line wrapping and flowed
>text don't deal well (yet) with multiple character sets,
>fonts, etc. and I'll take readability over application
>purity every single time.


********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From cabo@tzi.org  Mon Sep 10 04:04:13 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF3821F84B2 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 04:04:13 -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=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tnjZdCEyuSeV for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 04:04:12 -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 7C07521F84A0 for <ietf@ietf.org>; Mon, 10 Sep 2012 04:04:12 -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.3/8.14.3) with ESMTP id q8AB41hd004988; Mon, 10 Sep 2012 13:04:01 +0200 (CEST)
Received: from [192.168.217.117] (p5489396D.dip.t-dialin.net [84.137.57.109]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 0C116912; Mon, 10 Sep 2012 13:04:00 +0200 (CEST)
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24F5312E@GLKXM0002V.GREENLNK.net>
Date: Mon, 10 Sep 2012 13:04:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <302823B7-5AE8-416B-8593-0FAD0CD1DF1C@tzi.org>
References: <504A4C9B.4010900@gmail.com> <20120909192557.33735.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24F5312E@GLKXM0002V.GREENLNK.net>
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1486)
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 11:04:13 -0000

On Sep 10, 2012, at 12:46, "Dearlove, Christopher (UK)" =
<Chris.Dearlove@baesystems.com> wrote:

> If someone wants to provide guidance on how to do a least bad job
> with Outlook, that will be gratefully received.

I'm not an expert for this, but, as far as I am aware of, it has not =
been=20
possible to productively participate in e-mail conversations using =
Outlook.

> But advice that says
> "don't use Outlook" will be filed with the advice that says "pick
> another employer to work for".

For a while, the stock advice has been slightly different:
"Get a $WEBMAIL account", where one popular value for WEBMAIL is =
"gmail".

Of course, if policies prevent using the Web from workplace, I feel your =
pain.

Gr=FC=DFe, Carsten


From petithug@acm.org  Mon Sep 10 08:47:06 2012
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDFD321F8738 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 08:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.195
X-Spam-Level: 
X-Spam-Status: No, score=-102.195 tagged_above=-999 required=5 tests=[AWL=0.405, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LivZZQxu+t1z for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 08:47:06 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 411CD21F8737 for <ietf@ietf.org>; Mon, 10 Sep 2012 08:47:06 -0700 (PDT)
Received: from [IPv6:2601:9:4b80:32:213:d4ff:fe04:3e08] (unknown [IPv6:2601:9:4b80:32:213:d4ff:fe04:3e08]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 45446204E2; Mon, 10 Sep 2012 15:47:01 +0000 (UTC)
Message-ID: <504E0B72.2090700@acm.org>
Date: Mon, 10 Sep 2012 08:46:58 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6esrpre) Gecko/20120817 Icedove/10.0.6
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
References: <504A4C9B.4010900@gmail.com> <20120909192557.33735.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24F5312E@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24F5312E@GLKXM0002V.GREENLNK.net>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 15:47:07 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09/10/2012 03:46 AM, Dearlove, Christopher (UK) wrote:
> If someone wants to provide guidance on how to do a least bad job with
> Outlook, that will be gratefully received. But advice that says "don't use
> Outlook" will be filed with the advice that says "pick another employer to
> work for".
> 

OK, here's how your post looks in my mailer:

http://ietf.implementers.org/irony.png

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQTgtwAAoJECnERZXWan7EOXwQANMQLtZ8JajzX3VK2M1PrpT/
ORkEVIva9GseZWo15zQre8NGdVlY/omRyGjAaoIFXKuWIRObXu4rftZ2HHQ2OKe1
FQZoqKFSx8i2G6yBie9VL1NNmBS0InPYcflK0aZOGr7jNjGBP3EGHCnX5ouJtcB/
pXDTXQbXOM71jPujyV6JJZ2sFGKtdNSOltd8FwkqqogkMK6S5PxJmYnV/4I+iBVl
c82wD04nx+vS5UiF3gJiSWGdmIZ48m5ShODxYTTYPvXZhLRS/lTYpTcx+Rv9RCam
Xwo+MYW0qiW89x4SGXMzCXAEtP2VxBfII/jWxiKGdcoH9877++c6yW2fFDQU/Qv4
x4uw9+rigncwSmLAQnr1UZ+APWRmq0DLH2X6J4pMFsMH9NuTCaLlRVHgizrgG6LW
nrTI34Xsp3A0WmP2H6IZCFtur1BAVio2JMp26MZsWKDAa0aD3ClJvlk/Ju37VsKV
JVujmJVnS0JHYJjK1BY1TWLhumusgEIrtl+4jM9yVMOS+DCJj5fB66Lnw1DJq/e3
hwhwRZcTk+obmdCf9eQIsAeH1HXxzkupJDQKDnMQe8gF3su6QeWap7YFFCAc7PXT
Xycq9qw2YskkWGNHwsZW/LId33M/SuKlKsqZgrEFoKBe/AwkBeQntdIoLQp/Rw4Y
uRoC3rlQDqpgdENYw0vV
=KpjV
-----END PGP SIGNATURE-----

From david.black@emc.com  Fri Sep  7 16:29:17 2012
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 0430C21E8047 for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 16:29: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mk7QZsW1jfNr for <ietf@ietfa.amsl.com>; Fri,  7 Sep 2012 16:29: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 6573121E8044 for <ietf@ietf.org>; Fri,  7 Sep 2012 16:29:16 -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 q87NTFgA016119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 7 Sep 2012 19:29:15 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor) for <ietf@ietf.org>; Fri, 7 Sep 2012 19:29:01 -0400
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q87NSxEf030813 for <ietf@ietf.org>; Fri, 7 Sep 2012 19:28:59 -0400
Received: from mx15a.corp.emc.com ([169.254.1.66]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Fri, 7 Sep 2012 19:28:59 -0400
From: "Black, David" <david.black@emc.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 7 Sep 2012 19:28:58 -0400
Subject: RE: Proposed IETF Meeting Calendar 2018 - 2022
Thread-Topic: Proposed IETF Meeting Calendar 2018 - 2022
Thread-Index: Ac2MZFS59/megtHbTnGDc2u72ubSSAA6/n9Q
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120A4E1347@MX15A.corp.emc.com>
References: <20120906191552.11119.48553.idtracker@ietfa.amsl.com>
In-Reply-To: <20120906191552.11119.48553.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 10 Sep 2012 08:54:38 -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, 07 Sep 2012 23:29:17 -0000

VGhlIGZpcnN0IHdlZWsgb2YgTm92ZW1iZXIgZGF0ZXMgZm9yIDIwMTgsIDIwMjEgYW5kIDIwMjIg
YXJlIGxpa2VseSB0bw0KY29uZmxpY3Qgd2l0aCBUMTAgKFNDU0kgc3RvcmFnZSBzdGFuZGFyZHMg
Ym9keSkuDQoNClRoYW5rcywNCi0tRGF2aWQgKHN0b3JtIFdHIGNvLWNoYWlyKQ0KDQo+IC0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IHdnY2hhaXJzLWJvdW5jZXNAaWV0Zi5vcmcg
W21haWx0bzp3Z2NoYWlycy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYNCj4gT2YgSUVURiBB
ZG1pbmlzdHJhdGl2ZSBEaXJlY3Rvcg0KPiBTZW50OiBUaHVyc2RheSwgU2VwdGVtYmVyIDA2LCAy
MDEyIDM6MTYgUE0NCj4gVG86IElFVEYgQW5ub3VuY2VtZW50IExpc3QNCj4gQ2M6IGlhb2NAaWV0
Zi5vcmc7IGlhYkBpYWIub3JnOyBpZXRmQGlldGYub3JnOyB3Z2NoYWlyc0BpZXRmLm9yZw0KPiBT
dWJqZWN0OiBQcm9wb3NlZCBJRVRGIE1lZXRpbmcgQ2FsZW5kYXIgMjAxOCAtIDIwMjINCj4gDQo+
IEFsbDsNCj4gDQo+IEJlbG93IGFyZSBzdWdnZXN0ZWQgTWVldGluZyBkYXRlcyBmb3IgMjAxOCAt
IDIwMjIsIElFVEYncyAxMDEgLSAxMTUuDQo+IA0KPiBUaGUgSUFPQyBpcyBzb2xpY2l0aW5nIHRo
ZSBjb21tdW5pdHkncyBmZWVkYmFjayBiZWZvcmUgYWRvcHRpbmcuDQo+IA0KPiBDb21tZW50cyBh
cHByZWNpYXRlZCB0byBpZXRmQGlldGYub3JnIGJ5IDIwIFNlcHRlbWJlciAyMDEyLg0KPiANCj4g
UmF5DQo+IA0KPiAyMDE4DQo+IElFVEYgMTAxCQkxOC0yMyBNYXJjaCAyMDE4DQo+IElFVEYgMTAy
CQkyMi0yNyBKdWx5IDIwMTgNCj4gSUVURiAxMDMJCTQgLSA5IE5vdmVtYmVyIDIwMTgNCj4gDQo+
IDIwMTkNCj4gSUVURiAxMDQJCTI0IC0gMjkgTWFyY2ggMjAxOQ0KPiBJRVRGIDEwNQkJMjEgLSAy
NiBKdWx5IDIwMTkNCj4gSUVURiAxMDYJCTE3IC0gMjIgTm92ZW1iZXIgMjAxOQ0KPiANCj4gMjAy
MA0KPiBJRVRGIDEwNwkJMjIgLSAyNyBNYXJjaCAyMDIwDQo+IElFVEYgMTA4CQkyNiAtIDMxIEp1
bHkgMjAyMA0KPiBJRVRGIDEwOQkJMTUgLSAyMCBOb3ZlbWJlciAyMDIwDQo+IA0KPiAyMDIxDQo+
IElFVEYgMTEwCQkyMSAtIDI2IE1hcmNoIDIwMjENCj4gSUVURiAxMTEJCTI1IC0gMzAgSnVseSAy
MDIxDQo+IElFVEYgMTEyCQk3IC0gMTIgTm92ZW1iZXIgMjAyMQ0KPiANCj4gMjAyMg0KPiBJRVRG
IDExMwkJMjAgLSAyNSBNYXJjaCAyMDIyDQo+IElFVEYgMTE0CQkyNCAtIDI5IEp1bHkgMjAyMg0K
PiBJRVRGIDExNQkJNiAtIDExIE5vdmVtYmVyIDIwMjINCg0K

From lizhong.jin@zte.com.cn  Sun Sep  9 22:58:57 2012
Return-Path: <lizhong.jin@zte.com.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1549C21F848B for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 22:58:57 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzd3ocmcMKpO for <ietf@ietfa.amsl.com>; Sun,  9 Sep 2012 22:58:56 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 276B921F847F for <ietf@ietf.org>; Sun,  9 Sep 2012 22:58:55 -0700 (PDT)
Received: from [192.168.168.119] by mx5.zte.com.cn with surfront esmtp id 1072311182326; Mon, 10 Sep 2012 13:40:27 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id A4AEA70DB17 for <ietf@ietf.org>; Mon, 10 Sep 2012 13:54:56 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id q8A5wboS085623 for <ietf@ietf.org>; Mon, 10 Sep 2012 13:58:37 +0800 (GMT-8) (envelope-from lizhong.jin@zte.com.cn)
In-Reply-To: <OF81D339BE.7DD73704-ON48257A75.00092902-48257A75.00094CD5@LocalDomain>
To: ietf@ietf.org
Subject: Re: IETF 95 Date Change Proposal - Round 2
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF06DE53BF.494CA042-ON48257A75.0020611C-48257A75.0020D493@zte.com.cn>
From: lizhong.jin@zte.com.cn
Date: Mon, 10 Sep 2012 13:58:03 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-09-10 13:58:37, Serialize complete at 2012-09-10 13:58:37
Content-Type: multipart/alternative; boundary="=_alternative 0020D48D48257A75_="
X-MAIL: mse02.zte.com.cn q8A5wboS085623
X-Mailman-Approved-At: Mon, 10 Sep 2012 08:54:38 -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, 10 Sep 2012 05:58:57 -0000

This is a multipart message in MIME format.
--=_alternative 0020D48D48257A75_=
Content-Type: text/plain; charset="US-ASCII"

Hi Ray,
1-3 April 2016 will be holiday in China. If the time is 3-8 April, then 
many Chinese attendees have to give up the holiday. Would you propose 
another time? Thank you.

Lizhong

> 
> ----- Forwarded on 2012-09-10 09:40 -----
> 
> IETF Administrative Director <iad@ietf.org> 
> Sender:  ietf-bounces@ietf.org
> 
> 2012-09-07 03:11
> 
> To
> 
> IETF Announcement List <ietf-announce@ietf.org>
> 
> CC
> 
> iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, 
iesg@ietf.org
> 
> Subject
> 
> IETF 95 Date Change Proposal - Round 2
> 
> All
> 
> 
> The IAOC is seeking community feedback on a proposed date change for 
IETF 95
> originally scheduled for 27 March to 1 April 2016.
> 
> After considering community feedback on a proposed change to 20 - 25 
March
> 2016, the IAOC is proposing 3 - 8 April 2016 to avoid the impact on 
travel and
> attendance during the 20 - 25 March period.
> 
> Comments appreciated to ietf@ietf.org by 20 September 2012.
> 
> Ray Pelletier
> IETF Administrative Director
> 

--=_alternative 0020D48D48257A75_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Ray,</font>
<br><font size=2 face="sans-serif">1-3 April 2016 will be holiday in China.
If the time is 3-8 April, then many Chinese attendees have to give up the
holiday. Would you propose another time? Thank you.</font>
<br>
<br><font size=2 face="sans-serif">Lizhong</font>
<br>
<br><font size=2 face="sans-serif">&gt; <br>
&gt; ----- Forwarded on 2012-09-10 09:40 -----</font>
<br><font size=2 face="sans-serif">&gt; <br>
&gt; IETF Administrative Director &lt;iad@ietf.org&gt; </font>
<br><font size=2 face="sans-serif">&gt; Sender: &nbsp;ietf-bounces@ietf.org<br>
&gt; </font>
<br><font size=2 face="sans-serif">&gt; 2012-09-07 03:11</font>
<br><font size=2 face="sans-serif">&gt; <br>
&gt; To</font>
<br><font size=2 face="sans-serif">&gt; <br>
&gt; IETF Announcement List &lt;ietf-announce@ietf.org&gt;</font>
<br><font size=2 face="sans-serif">&gt; <br>
&gt; CC</font>
<br><font size=2 face="sans-serif">&gt; <br>
&gt; iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org</font>
<br><font size=2 face="sans-serif">&gt; <br>
&gt; Subject</font>
<br><font size=2 face="sans-serif">&gt; <br>
&gt; IETF 95 Date Change Proposal - Round 2</font>
<br><font size=2 face="sans-serif">&gt; <br>
&gt; All<br>
&gt; <br>
&gt; <br>
&gt; The IAOC is seeking community feedback on a proposed date change for
IETF 95<br>
&gt; originally scheduled for 27 March to 1 April 2016.<br>
&gt; <br>
&gt; After considering community feedback on a proposed change to 20 -
25 March<br>
&gt; 2016, the IAOC is proposing 3 - 8 April 2016 to avoid the impact on
travel and<br>
&gt; attendance during the 20 - 25 March period.<br>
&gt; <br>
&gt; Comments appreciated to ietf@ietf.org by 20 September 2012.<br>
&gt; <br>
&gt; Ray Pelletier<br>
&gt; IETF Administrative Director<br>
&gt; <br>
</font>
--=_alternative 0020D48D48257A75_=--


From prvs=56001bc076=david.borman@quantum.com  Mon Sep 10 08:24:31 2012
Return-Path: <prvs=56001bc076=david.borman@quantum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DDF521E8034 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 08:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.265
X-Spam-Level: 
X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ny9b1GyFP8jF for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 08:24:30 -0700 (PDT)
Received: from mx0a-000ceb01.pphosted.com (mx0a-000ceb01.pphosted.com [67.231.144.126]) by ietfa.amsl.com (Postfix) with ESMTP id 986B711E808D for <ietf@ietf.org>; Mon, 10 Sep 2012 08:24:30 -0700 (PDT)
Received: from pps.filterd (m0030277 [127.0.0.1]) by m0030277.ppops.net (8.14.4/8.14.4) with SMTP id q8AFOS7O012057; Mon, 10 Sep 2012 08:24:28 -0700
Received: from ppoxedge1.quantum.com ([146.174.252.27]) by mx0a-000ceb01.pphosted.com with ESMTP id 179hj4g4dm-2 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 10 Sep 2012 08:24:28 -0700
Received: from PPOMSG2.QUANTUM.com (10.50.35.27) by PPOXEDGE1.quantum.com (146.174.252.27) with Microsoft SMTP Server (TLS) id 14.2.309.2; Mon, 10 Sep 2012 09:24:19 -0600
Received: from PPOMSG1.QUANTUM.com ([10.50.35.26]) by PPOMSG2.QUANTUM.com ([fe80::e4fd:df34:99ee:ac5e%20]) with mapi id 14.02.0309.002; Mon, 10 Sep 2012 09:24:24 -0600
From: David Borman <David.Borman@quantum.com>
To: Joe Touch <touch@ISI.EDU>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Topic: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Index: AQHNj2hbMijDpXsH9kqKxwzUIyAIjg==
Date: Mon, 10 Sep 2012 15:24:23 +0000
Message-ID: <AD01EFBA971A0A4EBB41E1AF7D81F000067C3719@PPOMSG1.QUANTUM.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>	<504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com>	<504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net>	<504AA4E7.8060000@isi.edu> <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504AFE51.1080705@gmail.com> <504B939F.8020002@isi.edu> <504B95A8.2070301@gmail.com> <504BF285.7050404@isi.edu>
In-Reply-To: <504BF285.7050404@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.176.229]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9D24BF1E042D374B80E7BD2C4107B39C@QUANTUM.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.431, 0.0.0000 definitions=2012-09-10_03:2012-09-06, 2012-09-10, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1209100127
X-Mailman-Approved-At: Mon, 10 Sep 2012 08:54:38 -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, 10 Sep 2012 15:24:31 -0000

On Sep 8, 2012, at 8:36 PM, Joe Touch <touch@ISI.EDU> wrote:

>=20
>=20
> On 9/8/2012 11:59 AM, Melinda Shore wrote:
>> On 9/8/12 10:51 AM, Joe Touch wrote:
>>> Nothing about an ID is inherently obsolete or out of date after 6 months
>>> except its being publicly available on authorized sites (up until now).
>>=20
>> I think this is absolutely incorrect.  Internet Drafts are IETF
>> documents, and expiration changes the relationship between the draft
>> and the IETF.  I have to say that I think it's terribly unprofessional
>> not to hang onto archival material
>=20
> Draft !=3D archival
>=20
> Or do you keep copies of all versions of papers you publish, including th=
e ones submitted for review? In case lawyers might need it, or for the bene=
fit of the public?
>=20
>> and frankly it's in the interest
>> of the IETF as an *open* standards organization to keep archival
>> material accessible.
>=20
> Agreed.
>=20
>> When you're working on a problem that's been around forever and
>> still hasn't been solved (like, oh, I dunno - firewall/NAT traversal?),
>> easy access to expired drafts is an enormous help.
>=20
> The needs of the community - including the lawyers - do not outweigh the =
rights of the author or the agreement they make with the IETF to date.
>=20
> The original point of having drafts expire seems to have been forgotten h=
ere. That's a pity. It did have a reason, and it was useful.

The original reason for expiring drafts, along with giving them long,
complicated names that includes the word "draft", was to keep them
from being referenced as if they were standards, based on experience
gathered from the short lived IDEA document series.  I don't think
that having an archive of expired drafts weakens that original goal.

			-David Borman

>=20
>> Would you be more comfortable if there were some sort of visual
>> flag that a draft had expired?
>=20
> If you post it, it's not expired. There's no point in claiming otherwise.
>=20
> Joe

----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any dis=
closure, copying, or further distribution of confidential information is no=
t permitted unless such privilege is explicitly granted in writing by Quant=
um. Quantum reserves the right to have electronic communications, including=
 email and attachments, sent across its networks filtered through anti viru=
s and spam software programs and retain such messages in order to comply wi=
th applicable data security and retention requirements. Quantum is not resp=
onsible for the proper and complete transmission of the substance of this c=
ommunication or for any delay in its receipt.

From prvs=592801385=fmartin@linkedin.com  Sun Sep  9 14:59:13 2012
Return-Path: <prvs=592801385=fmartin@linkedin.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDE321F84D2; Sun,  9 Sep 2012 14:59: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=[AWL=-0.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vO4Dxc-LQTzM; Sun,  9 Sep 2012 14:59:12 -0700 (PDT)
Received: from esv4-mav05.corp.linkedin.com (esv4-mav05.corp.linkedin.com [69.28.149.81]) by ietfa.amsl.com (Postfix) with ESMTP id D355D21F845C; Sun,  9 Sep 2012 14:59:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; i=@linkedin.com; q=dns/txt; s=proddkim1024; t=1347227952; x=1378763952; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=9EWQ7A06WuM3yWjHlKBWUBM4bkkw7egNbbZvH2D7ob0=; b=BTqv1m60rEczamYkNw5ax7E3yc3VKbzGQ182ZAiTBVHA+7/wDGhIDGC/ mjSRHiK4wdsV/8KODVqmke+YjJ+fXe1Wx+oXkz7i9tjxZcEhNpGUI86o7 SF6D65IWV9StX/vEWQSrC7W8AA8V6/miBPdkPBOleWN+DZVuYPcmb8bZv w=;
X-IronPort-AV: E=Sophos;i="4.80,126,1344236400"; d="scan'208";a="25019393"
Received: from ESV4-HT02.linkedin.biz (172.18.46.236) by esv4-cas01.linkedin.biz (172.18.46.140) with Microsoft SMTP Server (TLS) id 14.1.355.2; Sun, 9 Sep 2012 14:58:48 -0700
Received: from ESV4-EXC02.linkedin.biz ([fe80::4d74:48bd:e0bd:13ee]) by ESV4-HT02.linkedin.biz ([::1]) with mapi id 14.01.0218.012; Sun, 9 Sep 2012 14:58:48 -0700
From: Franck Martin <fmartin@linkedin.com>
To: Barry Leiba <barryleiba@computer.org>, John C Klensin <john-ietf@jck.com>
Subject: Re: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email Messages) to Proposed Standard
Thread-Topic: [EAI] Last Call: <draft-ietf-eai-popimap-downgrade-07.txt> (Post-delivery Message Downgrading for Internationalized Email Messages) to Proposed Standard
Thread-Index: AQHNjs5ELWePH7UMy0mnra8dO5E1tZeCjw8A
Date: Sun, 9 Sep 2012 21:58:47 +0000
Message-ID: <CC725DC8.57DBF%fmartin@linkedin.com>
In-Reply-To: <CALaySJJhRwO0qAq9GFB+X82DGnh53+jG8+Kj3-9i=zYJxJ7pBA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.18.46.247]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7EFF82ACB4DAAC49BB2CF1E906024AE6@linkedin.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 10 Sep 2012 08:54:53 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "ima@ietf.org" <ima@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Sep 2012 21:59:13 -0000

I'm happier,

Made comments in another thread on why I believe it opens a security hole
wider rather than trying to close it.

I guess I could leave with it, when this downgrade is only done from a
SMTPUTF8 compatible MTA to an ASCII MTA.

I mean a SMTPUTF8 MTA MUST reject such downgrade.

Let's not try to legitimize an attack vector (Friendly from having nothing
to do with the author of the email).

On 9/9/12 2:01 PM, "Barry Leiba" <barryleiba@computer.org> wrote:

>>> I will make the change.  I'll also remind the EAI group that
>>> there have been a couple of objections to the
>>> 5322upd-from-group spec, which I have to address.  I might do
>>> that by scoping it down a bit with some "SHOULD NOT use" sort
>>> of language to address those concerns.  Have to review them
>>> and see.
>>
>> My suggestion is to say something like the following:
>...
>> That could be either in Security Considerations or a separate
>> section.  You could even do something radical and incorporate it
>> as a section called "Applicability" and use the words "LIMITED
>> USE" (and, since no one seems to remember, a citation of RFC
>> 2026 Section 3.3).
>
>I have just posted drft-leiba-5322upd-from-group-04:
>   http://datatracker.ietf.org/doc/draft-leiba-5322upd-from-group/
>
>That changes the definition of Sender as well as From, and also adds a
>new "Applicability Statement" section that has an edited version of
>John's suggested text.  I like the result, and I hope others do as
>well.  I will post something to the 5322upd-from-group thread, asking
>that those who had objected look at the new text and see if they're
>happy (or at least somewhat happier) with it.
>
>Barry
>_______________________________________________
>IMA mailing list
>IMA@ietf.org
>https://www.ietf.org/mailman/listinfo/ima


From dhc@dcrocker.net  Mon Sep 10 08:58:40 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F3D521F874C for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 08:58: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cDN4jdbxNvNT for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 08:58:38 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D7CC621F8746 for <ietf@ietf.org>; Mon, 10 Sep 2012 08:58:38 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8AFwVix018831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 10 Sep 2012 08:58:32 -0700
Message-ID: <504E0E27.70906@dcrocker.net>
Date: Mon, 10 Sep 2012 08:58:31 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
Subject: Re: IETF...the unconference of SDOs
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <alpine.LSU.2.00.1209100939010.9973@hermes-1.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1209100939010.9973@hermes-1.csi.cam.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 10 Sep 2012 08:58:32 -0700 (PDT)
Cc: Michael Richardson {quigon} <mcr@sandelman.ca>, 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, 10 Sep 2012 15:58:40 -0000

On 9/10/2012 1:47 AM, Tony Finch wrote:
> Michael Richardson {quigon} <mcr@sandelman.ca> wrote:
>
>> Let me suggest that at the IETF, where the mailing list is king, you
>> can't join the Elite if you can't quote email properly.  Maybe we should
>> *state* this.
...
> message/rfc822 attachments don't work. If it did it would be a much better
> way to do forwarding and top-posting repliesthan at present. (For
> instance, Outlook can hide those horrible confusing email addresses rather
> than stripping them out.)


Plaintive humor notwithstanding, this all starts to look as if some sort 
of BCP or even protocol "profile" is warranted, to describe preferred 
practices in the creation and interpretation of RFC5322 objects within 
"conversational exchanges".

I'd be happy to participate in a specification effort, assuming 
community interest.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From d3e3e3@gmail.com  Mon Sep 10 09:01:33 2012
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35CD21F876E for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 09:01:32 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xslqu7MmU8jn for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 09:01:32 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id ECDD321F876C for <ietf@ietf.org>; Mon, 10 Sep 2012 09:01:31 -0700 (PDT)
Received: by ieak13 with SMTP id k13so3770662iea.31 for <ietf@ietf.org>; Mon, 10 Sep 2012 09:01:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Ix1C+auBejPLeorn/WgpuAJU6z6Cz2Dqu6h/rduVfPs=; b=a6KDkeX7SV7eylZY7/mYZ1uFT3+2OzE/jv/9rkAA9Q4rtoY4OQNr6V9icdTeikmpJ8 tYvoxKQwbwy1V5T5zvOW7vh+SPw+jUptJNjT5/3rUBaw8Crh/eFhQnFztx+zQHQVKlZA erbNb0LT2deeDkOdsp6Kajh3k4DRFMbvOyjv+sFQ0v8cCyggoqHwdtmXWV2HLCX0vTYn ajgp/pNrkkD2hZgTMboSd3j1kgM3Vtz7U8wgHyU40wwnc5kISYnF1i7V2y+mUOi3jOP5 gf1BMlZsB1dAylBGAboEpnLKusbXbXD42xeXeZX1PbS39mDzasYBXeoBAz7SgT7LGcgG 5RMQ==
Received: by 10.50.57.168 with SMTP id j8mr11942224igq.16.1347292891425; Mon, 10 Sep 2012 09:01:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.143.103 with HTTP; Mon, 10 Sep 2012 09:01:08 -0700 (PDT)
In-Reply-To: <20120908044944.C686518C0E7@mercury.lcs.mit.edu>
References: <20120908044944.C686518C0E7@mercury.lcs.mit.edu>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 10 Sep 2012 12:01:08 -0400
Message-ID: <CAF4+nEHeML9s3eToQShthFJXxd7Bbe4C8wjBycKZBEbCVfqFSw@mail.gmail.com>
Subject: Re: IETF...the unconference of SDOs
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 16:01:33 -0000

On Sat, Sep 8, 2012 at 12:49 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>     > From: Randy Bush <randy@psg.com>
>
>     > i say scott should teach emacs :)
>
> Epsilon, dude! Who the heck wants to write their editor extensions in freaking
> LISP? :-)

http://xkcd.com/297/

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

>         Noel

From simon.perreault@viagenie.ca  Mon Sep 10 09:08:37 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2A721E8034 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 09:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FME7Zc2fhH-i for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 09:08:36 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id F1F0F21F85F7 for <ietf@ietf.org>; Mon, 10 Sep 2012 09:08:35 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:1888:2198:f259:5e43]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 5D5D2412FB for <ietf@ietf.org>; Mon, 10 Sep 2012 12:08:35 -0400 (EDT)
Message-ID: <504E1082.5020106@viagenie.ca>
Date: Mon, 10 Sep 2012 12:08:34 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
References: <504A4C9B.4010900@gmail.com> <20120909192557.33735.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24F5312E@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24F5312E@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 16:08:37 -0000

Le 2012-09-10 06:46, Dearlove, Christopher (UK) a Ã©crit :
> If someone wants to provide guidance on how to do a least bad job
> with Outlook, that will be gratefully received.

Found this using the Google:
http://home.in.tum.de/~jain/software/outlook-quotefix/

No idea if it's any good as I don't have access to Outlook...

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

From cos@mip.polyamory.org  Mon Sep 10 10:51:44 2012
Return-Path: <cos@mip.polyamory.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 C84E421E8045 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 10:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.51
X-Spam-Level: 
X-Spam-Status: No, score=-0.51 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, J_CHICKENPOX_26=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f5wmqH6oSpFy for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 10:51:44 -0700 (PDT)
Received: from mip.polyamory.org (mip.aaaaa.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id 12BE221E8041 for <ietf@ietf.org>; Mon, 10 Sep 2012 10:51:43 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id 9EF0B10760; Mon, 10 Sep 2012 13:51:37 -0400 (EDT)
Date: Mon, 10 Sep 2012 13:51:37 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: lizhong.jin@zte.com.cn
Subject: Re: IETF 95 Date Change Proposal - Round 2
Message-ID: <20120910175137.GP3710@mip.aaaaa.org>
References: <OF81D339BE.7DD73704-ON48257A75.00092902-48257A75.00094CD5@LocalDomain> <OF06DE53BF.494CA042-ON48257A75.0020611C-48257A75.0020D493@zte.com.cn>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF06DE53BF.494CA042-ON48257A75.0020611C-48257A75.0020D493@zte.com.cn>
User-Agent: Mutt/1.4.2.3i
Organization: American Association Against Acronym Abuse
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, 10 Sep 2012 17:51:44 -0000

lizhong.jin@zte.com.cn wrote:
> 1-3 April 2016 will be holiday in China. If the time is 3-8 April, then 
> many Chinese attendees have to give up the holiday. Would you propose 
> another time? Thank you.

I think there's probably always either a major holiday somewhere or
another conference that the IETF wants to avoid conflicting with, so
avoiding significant holidays in all parts of the world is not a
practical pursuit.  The goal of this date change proposal seems to
be to avoid holding an IETF when there is a major travel disruption,
or days when travel and other public services are shut down, in the
place where the IETF meeting is to be held.  IETF 95 lists "target
location: Europe", and holding a meeting in Europe overlapping with
Easter would probably cause challenges.

However, I do wonder how major a holiday this is?

While there are parts of the world where it would not be challenging
to hold an IETF meeting over Christmas, international organizations
with major US+Europe participation seem to avoid doing so nonetheless.
Is this one a special case of similar magnitude?

Searching the web suggests that it may be:
  https://en.wikipedia.org/wiki/Qingming_Festival


Since I'm not planning to attend in person, I'll keep my comments general.
  -- Cos

From ned+ietf@mauve.mrochek.com  Mon Sep 10 11:41:13 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BA7621E8056 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 11:41:13 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDhPUCfTL05r for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 11:41:13 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0EEE021E8049 for <ietf@ietf.org>; Mon, 10 Sep 2012 11:41:12 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OK388C1J40008QTR@mauve.mrochek.com> for ietf@ietf.org; Mon, 10 Sep 2012 11:36:11 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJFFFOH4280006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 10 Sep 2012 11:36:09 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OK388BAQEC0006TF@mauve.mrochek.com>
Date: Mon, 10 Sep 2012 11:26:29 -0700 (PDT)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
In-reply-to: "Your message dated Mon, 10 Sep 2012 09:33:47 +0200" <504D97DB.3090205@cisco.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120909184347.32346.qmail@joyce.lan> <504D97DB.3090205@cisco.com>
To: Eliot Lear <lear@cisco.com>
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: Mon, 10 Sep 2012 18:41:13 -0000

> On 9/9/12 8:43 PM, John Levine wrote:
> > Let's say I write to the IESG and say this:
> >
> >   Due to a late night editing error, draft-foo-bar-42 which I
> >   submitted yesterday contains several paragraphs of company
> >   confidential information which you can easily see are irrelevant to
> >   the draft.  My boss wants it taken down pronto, even though he
> >   realizes that third parties may have made copies of it in the
> >   meantime.  I will probably lose my job if it stays up for more than a
> >   few days.  Thanks for your consideration.
> >
> > Is this the response?
> >
> >   You didn't make any legal threats, and now that we know the
> >   situation, we wouldn't believe any legal threats you might make in the
> >   future, so you better check out those burger flipping opportunities.

> No, the response is that we refer you to our policy.  As an open
> organization we do not remove information once posted, except under
> extraordinary circumstances.

Exactly. This sort of thing is wh a policy is needed, although I note in
passing that the folks at this hypothetical might want to read up on the
Streisand Effect.

> >
> > What was wrong with the original version which gave the IESG the
> > latitude to remove an I-D if they feel, for whatever reason, that it
> > would be a good idea to do so?

> What original?  The draft policy states:

> > An I-D will only be removed from the public I-D archive in compliance
> > with a duly authorized court order.


> > If the IESG were so screwed up that
> > they started deleting I-Ds for bad reasons, no amount of process
> > verbiage would help.

> Certainly, but let's not start from the wrong place to begin with.
> Let's also set expectations that the IESG may be used to clean up after
> other peoples' messes.  They have enough to do.

That is if anything an understatement. 

> And again, this is best developed with counsel.

A very emphatic +1 to this.

				Ned

From johnl@taugh.com  Mon Sep 10 11:52:33 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7EA21E8086 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 11:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 83PBhIUfFMlz for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 11:52:31 -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 8D81521E8064 for <ietf@ietf.org>; Mon, 10 Sep 2012 11:52:31 -0700 (PDT)
Received: (qmail 10760 invoked from network); 10 Sep 2012 18:52:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=2a07.504e36ec.k1209; bh=elHDOjSreCJq0QeFoDR5dbPCWmzmMig//oQJaGCMfag=; b=Mlz/K1osFl+7oMqWuG4FzwzCdesX47Q5MUYgSeZHrLLc5uZgp8gNfyJxNBM2WdwXrRx6KksnoZ4jx27tZhbf2h4nvJ4HemDGwPH3GnsaNIHeJEamWhRbvw+G8OLvn5ji7GM51nYkxO3ezf/jkeTz0Rw+SX5buyvVKqSpLHVMPGo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=2a07.504e36ec.k1209; bh=elHDOjSreCJq0QeFoDR5dbPCWmzmMig//oQJaGCMfag=; b=qUyDbzYOMFGXB49z05HnSBTt2+q/GhNK4RCD9cHNmHvschfktYM7PF34rg96yP8IWHn15TSmzcZcVmbSzpID1gpdSaaTSkgIvYgO9E/d6LZ2dPgtHtOWQu60YSR2F4Ho9kDbloVjM99m02q6PAASuNj7bG9K8dzWp86615QEiBY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 10 Sep 2012 18:52:06 -0000
Date: 10 Sep 2012 14:52:27 -0400
Message-ID: <alpine.BSF.2.00.1209101450280.78731@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Ned Freed" <ned.freed@mrochek.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <01OK388BAQEC0006TF@mauve.mrochek.com>
References: <20120909184347.32346.qmail@joyce.lan> <504D97DB.3090205@cisco.com> <01OK388BAQEC0006TF@mauve.mrochek.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 18:52:33 -0000

>>> Let's say I write to the IESG and say this:
>>>
>>>   Due to a late night editing error, draft-foo-bar-42 which I
>>>   submitted yesterday contains several paragraphs of company
>>>   confidential information which you can easily see are irrelevant to
>>>   the draft.  My boss wants it taken down pronto, even though he
>>>   realizes that third parties may have made copies of it in the
>>>   meantime.  I will probably lose my job if it stays up for more than a
>>>   few days.  Thanks for your consideration.

> Exactly. This sort of thing is wh a policy is needed, although I note in
> passing that the folks at this hypothetical might want to read up on the
> Streisand Effect.

Note that I phrased it as a polite request, not a threat.

>> And again, this is best developed with counsel.
> A very emphatic +1 to this.

Sure, but keep in mind that it's one thing to minimize legal risk, 
is not the same as minimizing cost or complexity, or doing what's best for 
the IETF and the community.

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 ajs@anvilwalrusden.com  Mon Sep 10 12:07:20 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2E1611E8099 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 12:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.522
X-Spam-Level: 
X-Spam-Status: No, score=-0.522 tagged_above=-999 required=5 tests=[AWL=0.319,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4IQWSmM6dyyf for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 12:07:19 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6C34C11E8097 for <ietf@ietf.org>; Mon, 10 Sep 2012 12:07:19 -0700 (PDT)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 89EB98A031 for <ietf@ietf.org>; Mon, 10 Sep 2012 19:07:13 +0000 (UTC)
Date: Mon, 10 Sep 2012 15:07:11 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Message-ID: <20120910190711.GO84264@mx1.yitter.info>
References: <20120909184347.32346.qmail@joyce.lan> <504D97DB.3090205@cisco.com> <01OK388BAQEC0006TF@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01OK388BAQEC0006TF@mauve.mrochek.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Sep 2012 19:07:21 -0000

On Mon, Sep 10, 2012 at 11:26:29AM -0700, ned+ietf@mauve.mrochek.com wrote:

> > No, the response is that we refer you to our policy.  As an open
> > organization we do not remove information once posted, except under
> > extraordinary circumstances.
> 
> Exactly. This sort of thing is wh a policy is needed

I attempted to hint at it already in this thread, but frankly, this
sort of thing is why a policy _is not_ needed.  The IESG has that
discretion already, and I would prefer to trust their judgement than
to write a policy governing all future action, thereby running the
risk that we'll have overlooked something and having a resulting
problem with policies down the road.

I do not understand this nearly constitutional obsession with writing
down policies for everything we do and don't do.  It turns us into a
bureaucratic process slaves for no benefit I can see.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From ned+ietf@mauve.mrochek.com  Mon Sep 10 13:30:46 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B1C211E80BF for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 13:30: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TUjgxA4KJQJY for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 13:30:45 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7869511E80B8 for <ietf@ietf.org>; Mon, 10 Sep 2012 13:30:45 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OK3C25GY40008GAX@mauve.mrochek.com> for ietf@ietf.org; Mon, 10 Sep 2012 13:25:44 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJFFFOH4280006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 10 Sep 2012 13:25:42 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OK3C2488IE0006TF@mauve.mrochek.com>
Date: Mon, 10 Sep 2012 13:14:54 -0700 (PDT)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-reply-to: "Your message dated Mon, 10 Sep 2012 14:52:27 -0400" <alpine.BSF.2.00.1209101450280.78731@joyce.lan>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <20120909184347.32346.qmail@joyce.lan> <504D97DB.3090205@cisco.com> <01OK388BAQEC0006TF@mauve.mrochek.com> <alpine.BSF.2.00.1209101450280.78731@joyce.lan>
To: John R Levine <johnl@taugh.com>
Cc: Ned Freed <ned.freed@mrochek.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, 10 Sep 2012 20:30:46 -0000

> >>> Let's say I write to the IESG and say this:
> >>>
> >>>   Due to a late night editing error, draft-foo-bar-42 which I
> >>>   submitted yesterday contains several paragraphs of company
> >>>   confidential information which you can easily see are irrelevant to
> >>>   the draft.  My boss wants it taken down pronto, even though he
> >>>   realizes that third parties may have made copies of it in the
> >>>   meantime.  I will probably lose my job if it stays up for more than a
> >>>   few days.  Thanks for your consideration.

> > Exactly. This sort of thing is wh a policy is needed, although I note in
> > passing that the folks at this hypothetical might want to read up on the
> > Streisand Effect.

> Note that I phrased it as a polite request, not a threat.

I don't see that as especially relevant: There have been plenty of cases where
a polite request called attention to something that would otherwise have been
ignored, although of course the ones that get reported at
http://www.thestreisandeffect.com/ tend to be the ones where bad behavior
was involved.

> >> And again, this is best developed with counsel.
> > A very emphatic +1 to this.

> Sure, but keep in mind that it's one thing to minimize legal risk,
> is not the same as minimizing cost or complexity, or doing what's best for
> the IETF and the community.

The narrow goal of minimizing the immediate legal risk is hardly the only, or
even an especially good, reason to seek advice of counsel. Counsel is there to
assist you in understanding the legal implications of your possible choices and
then in implementing the choice you make. They are not there to make your
decisions for you.

				Ned

From touch@isi.edu  Mon Sep 10 22:21:36 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C64FE21F8658 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 22:21: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vfv-UMxQnHO for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 22:21:36 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 4A1CE21F8653 for <ietf@ietf.org>; Mon, 10 Sep 2012 22:21:36 -0700 (PDT)
Received: from [192.168.0.15] ([210.114.91.71]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8B5LGYX029277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 10 Sep 2012 22:21:27 -0700 (PDT)
Message-ID: <504ECA4C.40305@isi.edu>
Date: Mon, 10 Sep 2012 22:21:16 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: David Borman <David.Borman@quantum.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net>	<504A0928.2020200@isi.edu> <504A138D.8050504@gmail.com>	<504A1604.2020000@isi.edu> <6.2.5.6.2.20120907085007.0aaa2d38@resistor.net>	<504AA4E7.8060000@isi.edu> <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com> <58581B89-7D2D-4CF8-9E85-014016A86E5D@isi.edu> <504AFE51.1080705@gmail.com> <504B939F.8020002@isi.edu> <504B95A8.2070301@gmail.com> <504BF285.7050404@isi.edu> <AD01EFBA971A0A4EBB41E1AF7D81F000067C3719@PPOMSG1.QUANTUM.com>
In-Reply-To: <AD01EFBA971A0A4EBB41E1AF7D81F000067C3719@PPOMSG1.QUANTUM.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: Tue, 11 Sep 2012 05:21:36 -0000

On 9/10/2012 8:24 AM, David Borman wrote:
...
> The original reason for expiring drafts, along with giving them long,
> complicated names that includes the word "draft", was to keep them
> from being referenced as if they were standards, based on experience
> gathered from the short lived IDEA document series.

It was also to encourage authors to post half-baked* ideas without 
having them persist - either as standards, or in general as something 
the author needed to continue to defend.

 > I don't think
> that having an archive of expired drafts weakens that original goal.

It weakens both goals. A key complaint has been that the doc disappears 
from an IETF site. Neither the length nor the name has been an impediment

Joe



From glenzorn@gmail.com  Mon Sep 10 23:14:25 2012
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 36A8A21F8678 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 23:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZEGGCQ9H8Kd1 for <ietf@ietfa.amsl.com>; Mon, 10 Sep 2012 23:14:24 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id AE52021F8658 for <ietf@ietf.org>; Mon, 10 Sep 2012 23:14:24 -0700 (PDT)
Received: by ieak13 with SMTP id k13so320155iea.31 for <ietf@ietf.org>; Mon, 10 Sep 2012 23:14:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Mqr1fuKc6ik6Cgsy1NBRzgJtJzVcvYo3WKqQwpGlRIs=; b=vvaJGlZiqym0O//XuaMDtjwvfjJKDm3mONLtX3r+cVSotbBlWtZEaJwrFkLGcrCIAk j12mT1/zaqXPqmJ1ay9XrJJVyyaG5tjD8Z3/KogBns3pO/VHr0chowlrnOJuQZ9A/4Rb fZqs/9xmsyn5kVocLYJ9L6zJcwsBmqXWWnZrl2PaLSy5QZAQQpJ/3J+V813kpiilEhgX fe6tdzmPKsR4wUhIjHdsNbw8Ll9gmmFPD2sySRaFXWH2q2hQlHR0j/ym+nGFNplp+Iop yd9N7L4hZYGyGoWrQytMHJWKF51E58UsSKka7CpEgDotVfndzkTAU2aTx39mLM8UAluC /shw==
Received: by 10.50.95.198 with SMTP id dm6mr14248679igb.60.1347344064284; Mon, 10 Sep 2012 23:14:24 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-120-184-78.revip2.asianet.co.th. [124.120.184.78]) by mx.google.com with ESMTPS id ce6sm971095igb.1.2012.09.10.23.14.21 (version=SSLv3 cipher=OTHER); Mon, 10 Sep 2012 23:14:23 -0700 (PDT)
Message-ID: <504ED6BA.5040207@gmail.com>
Date: Tue, 11 Sep 2012 13:14:18 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120721 Thunderbird/14.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
References: <504A4C9B.4010900@gmail.com> <20120909192557.33735.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D24F5312E@GLKXM0002V.GREENLNK.net> <302823B7-5AE8-416B-8593-0FAD0CD1DF1C@tzi.org>
In-Reply-To: <302823B7-5AE8-416B-8593-0FAD0CD1DF1C@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Sep 2012 06:14:25 -0000

On 09/10/2012 06:04 PM, Carsten Bormann wrote:
> On Sep 10, 2012, at 12:46, "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com> wrote:
>
>> If someone wants to provide guidance on how to do a least bad job
>> with Outlook, that will be gratefully received.
> I'm not an expert for this, but, as far as I am aware of, it has not been
> possible to productively participate in e-mail conversations using Outlook.

Actually, I managed to do so for more than 10 years (at least I received 
very few complaints once I learned how to reply in ASCII ;-)

>
>> But advice that says
>> "don't use Outlook" will be filed with the advice that says "pick
>> another employer to work for".

Or, since we're all "volunteers", we could just do IETF work on our own 
time & using our own computers.

> For a while, the stock advice has been slightly different:
> "Get a $WEBMAIL account", where one popular value for WEBMAIL is "gmail".
>
> Of course, if policies prevent using the Web from workplace, I feel your pain.
Grüße, Carsten


From eric.gray@ericsson.com  Tue Sep 11 03:31:18 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 097CB21F876D; Tue, 11 Sep 2012 03:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level: 
X-Spam-Status: No, score=-7.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBwQ5Fj-tCDt; Tue, 11 Sep 2012 03:31:16 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 8971921F8770; Tue, 11 Sep 2012 03:31:16 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q8BAUGOc027523 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Sep 2012 05:31:15 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.204]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 11 Sep 2012 06:30:32 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Ralph Droms <rdroms.ietf@gmail.com>, Joe Touch <touch@ISI.EDU>
Date: Tue, 11 Sep 2012 06:30:30 -0400
Subject: RE: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Topic: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Index: Ac2NFB7vOAdR+XRRS3avmuvQJYb+AAC81Hqw
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se>
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu> <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com>
In-Reply-To: <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Chair <chair@ietf.org>, IETF list 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, 11 Sep 2012 10:31:18 -0000

Ralph,

	It cannot hurt to try to make this as unambiguous as possible.

	The IETF cannot instruct the IEEE RAC not to assign an Ethertype to anyone=
 who
applies for it, assuming they otherwise comply with RAC requirements and ar=
e willing to
pay for the assignment, if necessary. =20

	However, the IETF can caution the RAC that any such assignment can only be=
 (or=20
become) associated with an IETF protocol specification upon its approval an=
d publication=20
as an IETF RFC.

--
Eric

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ral=
ph Droms
Sent: Friday, September 07, 2012 12:15 PM
To: Joe Touch
Cc: IETF Chair; IETF list discussion
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protoco=
ls


On Sep 7, 2012, at 10:51 AM 9/7/12, Joe Touch wrote:

> Hi, all,
>=20
> This statement seems fine, but it's worth noting that it would apply only=
 to  *IETF* protocol specs.

What did you have in mind as "noting"?  This text seems pretty clear to me =
as applying only to "IETF protocol specifications":=20

  the IEEE RAC will not assign a new Ethertype to
  a new IETF protocol specification that needs one until the IESG has
  approved the protocol specification for publication as an RFC.



> The IESG has, IMO, no authority to make such claims for independent submi=
ssions (and what about IRTF ones?), and the IEEE should recognize that such=
 protocols are described by RFCs too.

Where do you see any such claims in this statement?  What would you change?

- Ralph

>=20
> Joe
>=20
> On 9/3/2012 5:02 PM, IETF Chair wrote:
>> The IESG is considering this IESG Statement.  Comments from the communit=
y are solicited.
>>=20
>> On behalf of the IESG,
>> Russ
>>=20
>> --- DRAFT IESG STATEMENT ---
>>=20
>> Subject: Ethertype Assignments for IETF Protocols
>>=20
>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some=20
>> IETF protocol specification make use of Ethertypes.  Since Ethertypes=20
>> are a fairly scarce resource, the IEEE RAC will not assign a new=20
>> Ethertype to a new IETF protocol specification that needs one until=20
>> the IESG has approved the protocol specification for publication as an R=
FC.
>>=20
>> To let the IEEE RAC know that the IESG has approved an IETF protocol=20
>> specification for publication, all future requests for assignment of=20
>> Ethertypes for IETF protocol specifications will be made by the IESG.
>>=20
>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for=20
>> use during development and experimentation.
>>=20
>>=20
>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>    IEEE standard for Local and Metropolitan Area Networks:
>>    Overview and Architecture -- Amendment 1: Ethertypes for
>>    Prototype and Vendor-Specific Protocol Development.
>>=20
>>=20


From eric.gray@ericsson.com  Tue Sep 11 03:36:14 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D55D21F87AD; Tue, 11 Sep 2012 03:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.932
X-Spam-Level: 
X-Spam-Status: No, score=-6.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u7M3eZdcc1o5; Tue, 11 Sep 2012 03:36:13 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 464FE21F87AE; Tue, 11 Sep 2012 03:36:13 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q8BAe9uO019432; Tue, 11 Sep 2012 05:40:10 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.204]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 11 Sep 2012 06:36:04 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Eric Gray <eric.gray@ericsson.com>, Ralph Droms <rdroms.ietf@gmail.com>, Joe Touch <touch@ISI.EDU>
Date: Tue, 11 Sep 2012 06:36:02 -0400
Subject: RE: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Topic: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Index: Ac2NFB7vOAdR+XRRS3avmuvQJYb+AAC81HqwAABqCfA=
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADD@EUSAACMS0701.eamcs.ericsson.se>
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu>	<792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Chair <chair@ietf.org>, IETF list 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, 11 Sep 2012 10:36:14 -0000

Has anyone considered the possibility that the application for an Ethertype=
 to be associated=20
with an IETF protocol specification should become a responsibility for IANA=
?

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Eri=
c Gray
Sent: Tuesday, September 11, 2012 6:31 AM
To: Ralph Droms; Joe Touch
Cc: IETF Chair; IETF list discussion
Subject: RE: Draft IESG Statement on Ethertype Assignments for IETF Protoco=
ls

Ralph,

	It cannot hurt to try to make this as unambiguous as possible.

	The IETF cannot instruct the IEEE RAC not to assign an Ethertype to anyone=
 who applies for it, assuming they otherwise comply with RAC requirements a=
nd are willing to pay for the assignment, if necessary. =20

	However, the IETF can caution the RAC that any such assignment can only be=
 (or
become) associated with an IETF protocol specification upon its approval an=
d publication as an IETF RFC.

--
Eric

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ral=
ph Droms
Sent: Friday, September 07, 2012 12:15 PM
To: Joe Touch
Cc: IETF Chair; IETF list discussion
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protoco=
ls


On Sep 7, 2012, at 10:51 AM 9/7/12, Joe Touch wrote:

> Hi, all,
>=20
> This statement seems fine, but it's worth noting that it would apply only=
 to  *IETF* protocol specs.

What did you have in mind as "noting"?  This text seems pretty clear to me =
as applying only to "IETF protocol specifications":=20

  the IEEE RAC will not assign a new Ethertype to
  a new IETF protocol specification that needs one until the IESG has
  approved the protocol specification for publication as an RFC.



> The IESG has, IMO, no authority to make such claims for independent submi=
ssions (and what about IRTF ones?), and the IEEE should recognize that such=
 protocols are described by RFCs too.

Where do you see any such claims in this statement?  What would you change?

- Ralph

>=20
> Joe
>=20
> On 9/3/2012 5:02 PM, IETF Chair wrote:
>> The IESG is considering this IESG Statement.  Comments from the communit=
y are solicited.
>>=20
>> On behalf of the IESG,
>> Russ
>>=20
>> --- DRAFT IESG STATEMENT ---
>>=20
>> Subject: Ethertype Assignments for IETF Protocols
>>=20
>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some=20
>> IETF protocol specification make use of Ethertypes.  Since Ethertypes=20
>> are a fairly scarce resource, the IEEE RAC will not assign a new=20
>> Ethertype to a new IETF protocol specification that needs one until=20
>> the IESG has approved the protocol specification for publication as an R=
FC.
>>=20
>> To let the IEEE RAC know that the IESG has approved an IETF protocol=20
>> specification for publication, all future requests for assignment of=20
>> Ethertypes for IETF protocol specifications will be made by the IESG.
>>=20
>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for=20
>> use during development and experimentation.
>>=20
>>=20
>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>    IEEE standard for Local and Metropolitan Area Networks:
>>    Overview and Architecture -- Amendment 1: Ethertypes for
>>    Prototype and Vendor-Specific Protocol Development.
>>=20
>>=20


From rdroms.ietf@gmail.com  Tue Sep 11 03:43:26 2012
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEA7B21F8790; Tue, 11 Sep 2012 03:43:26 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mH7bLQMJ8xAZ; Tue, 11 Sep 2012 03:43:25 -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 7E1B721F877B; Tue, 11 Sep 2012 03:43:25 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so493300vcb.31 for <multiple recipients>; Tue, 11 Sep 2012 03:43:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=hsv4a2DDKkF2UD1A1uCWgqs1wBd9CPcDKPQblV+Rjwk=; b=pPlvDw5+DaqaF/r6M3xaq1lfZq//bNrCkeKn6M5svW8mw6spnsrjc2N0jF0KxiqHXv yUh4h0fJDhywaI/EFgeSMZUQ+T4d9kYOFt0FVQ5/dhADMl1ujQDqhEgAAoX4WX2AZ3R/ JJla+M0sBnnQJoisZNwRZfvyjDIudf4KiIv4HYM8L2JMeLjJELHOG2zqiYEendTeTw14 9Bt3daTZGuoE1huCeFCdiOJKZv2MBPof6Y4w4SJ9UdP6NRRBlFV9z7RI9Uz7Y7UjW5EA qKEzXavqRob4+6ro/07gSMrq9VpCf3CPUBm7ofBH4GBE++2sUAu/RygSKmCdLUdu+GPi JoiA==
Received: by 10.58.64.103 with SMTP id n7mr252842ves.35.1347360204844; Tue, 11 Sep 2012 03:43:24 -0700 (PDT)
Received: from [10.86.255.227] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPS id w10sm10629592vef.5.2012.09.11.03.43.20 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Sep 2012 03:43:23 -0700 (PDT)
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se>
Date: Tue, 11 Sep 2012 06:43:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <54E5F2A0-1539-4158-BD59-8D5414CCE992@gmail.com>
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu> <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se>
To: Eric Gray <eric.gray@ericsson.com>
X-Mailer: Apple Mail (2.1278)
Cc: IETF Chair <chair@ietf.org>, IETF list 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, 11 Sep 2012 10:43:26 -0000

On Sep 11, 2012, at 6:30 AM 9/11/12, Eric Gray wrote:

> Ralph,
>=20
> 	It cannot hurt to try to make this as unambiguous as possible.
>=20
> 	The IETF cannot instruct the IEEE RAC not to assign an Ethertype =
to anyone who
> applies for it, assuming they otherwise comply with RAC requirements =
and are willing to
> pay for the assignment, if necessary. =20

Eric - As I understand the IESG statement, the intent is not to give any =
instructions to the IEEE RAC.  I read the text I quoted in my e-mail:

  the IEEE RAC will not assign a new Ethertype to
  a new IETF protocol specification that needs one until the IESG has
  approved the protocol specification for publication as an RFC.

as a restatement of the IEEE RAC policy, which was included in the IESG =
statement as explanation for this text:

  To let the IEEE RAC know that the IESG has approved an IETF protocol=20=

  specification for publication, all future requests for assignment of=20=

  Ethertypes for IETF protocol specifications will be made by the IESG.

which describes how the IESG will inform the IEEE RAC about which =
protocol specifications meet the IEEE RAC policy.

- Ralph


>=20
> 	However, the IETF can caution the RAC that any such assignment =
can only be (or=20
> become) associated with an IETF protocol specification upon its =
approval and publication=20
> as an IETF RFC.


>=20
> --
> Eric
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Ralph Droms
> Sent: Friday, September 07, 2012 12:15 PM
> To: Joe Touch
> Cc: IETF Chair; IETF list discussion
> Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF =
Protocols
>=20
>=20
> On Sep 7, 2012, at 10:51 AM 9/7/12, Joe Touch wrote:
>=20
>> Hi, all,
>>=20
>> This statement seems fine, but it's worth noting that it would apply =
only to  *IETF* protocol specs.
>=20
> What did you have in mind as "noting"?  This text seems pretty clear =
to me as applying only to "IETF protocol specifications":=20
>=20
>  the IEEE RAC will not assign a new Ethertype to
>  a new IETF protocol specification that needs one until the IESG has
>  approved the protocol specification for publication as an RFC.
>=20
>=20
>=20
>> The IESG has, IMO, no authority to make such claims for independent =
submissions (and what about IRTF ones?), and the IEEE should recognize =
that such protocols are described by RFCs too.
>=20
> Where do you see any such claims in this statement?  What would you =
change?
>=20
> - Ralph
>=20
>>=20
>> Joe
>>=20
>> On 9/3/2012 5:02 PM, IETF Chair wrote:
>>> The IESG is considering this IESG Statement.  Comments from the =
community are solicited.
>>>=20
>>> On behalf of the IESG,
>>> Russ
>>>=20
>>> --- DRAFT IESG STATEMENT ---
>>>=20
>>> Subject: Ethertype Assignments for IETF Protocols
>>>=20
>>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some=20
>>> IETF protocol specification make use of Ethertypes.  Since =
Ethertypes=20
>>> are a fairly scarce resource, the IEEE RAC will not assign a new=20
>>> Ethertype to a new IETF protocol specification that needs one until=20=

>>> the IESG has approved the protocol specification for publication as =
an RFC.
>>>=20
>>> To let the IEEE RAC know that the IESG has approved an IETF protocol=20=

>>> specification for publication, all future requests for assignment of=20=

>>> Ethertypes for IETF protocol specifications will be made by the =
IESG.
>>>=20
>>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for=20=

>>> use during development and experimentation.
>>>=20
>>>=20
>>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>>   IEEE standard for Local and Metropolitan Area Networks:
>>>   Overview and Architecture -- Amendment 1: Ethertypes for
>>>   Prototype and Vendor-Specific Protocol Development.
>>>=20
>>>=20
>=20


From eric.gray@ericsson.com  Tue Sep 11 03:53:15 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E3621F8716; Tue, 11 Sep 2012 03:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.849
X-Spam-Level: 
X-Spam-Status: No, score=-6.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V97PGVIyV0bW; Tue, 11 Sep 2012 03:53:15 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 17D9921F8735; Tue, 11 Sep 2012 03:53:14 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q8BAv9An020170; Tue, 11 Sep 2012 05:57:11 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.204]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 11 Sep 2012 06:53:09 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Date: Tue, 11 Sep 2012 06:53:07 -0400
Subject: RE: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Topic: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Index: Ac2QCktOHxK3ceraS3WGI4656rI54wAAEzRg
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADF@EUSAACMS0701.eamcs.ericsson.se>
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu> <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se> <54E5F2A0-1539-4158-BD59-8D5414CCE992@gmail.com>
In-Reply-To: <54E5F2A0-1539-4158-BD59-8D5414CCE992@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Chair <chair@ietf.org>, IETF list 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, 11 Sep 2012 10:53:16 -0000

Ralph,

	The statement "the IEEE RAC will not assign" sounds very explicitly like a=
n instruction
to the IEEE RAC, does it not?

	Also, it is difficult to enforce, since an implementer can certainly get t=
heir company=20
to request an Ethertype to be used on their own proprietary version of an I=
ETF protocol,
and it is not within the purview of the IETF (or IESG) to prevent an assign=
ment in this case.

	If it then turns out that the implementation that uses this Ethertype subs=
equently
becomes a de-facto standard that happens to align perfectly with the publis=
hed RFC, then
the intention of the proposed wording is subverted.

--
Eric

-----Original Message-----
From: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
Sent: Tuesday, September 11, 2012 6:43 AM
To: Eric Gray
Cc: Joe Touch; IETF Chair; IETF list discussion
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protoco=
ls
Importance: High


On Sep 11, 2012, at 6:30 AM 9/11/12, Eric Gray wrote:

> Ralph,
>=20
> 	It cannot hurt to try to make this as unambiguous as possible.
>=20
> 	The IETF cannot instruct the IEEE RAC not to assign an Ethertype to=20
> anyone who applies for it, assuming they otherwise comply with RAC=20
> requirements and are willing to pay for the assignment, if necessary.

Eric - As I understand the IESG statement, the intent is not to give any in=
structions to the IEEE RAC.  I read the text I quoted in my e-mail:

  the IEEE RAC will not assign a new Ethertype to
  a new IETF protocol specification that needs one until the IESG has
  approved the protocol specification for publication as an RFC.

as a restatement of the IEEE RAC policy, which was included in the IESG sta=
tement as explanation for this text:

  To let the IEEE RAC know that the IESG has approved an IETF protocol
  specification for publication, all future requests for assignment of
  Ethertypes for IETF protocol specifications will be made by the IESG.

which describes how the IESG will inform the IEEE RAC about which protocol =
specifications meet the IEEE RAC policy.

- Ralph


>=20
> 	However, the IETF can caution the RAC that any such assignment can=20
> only be (or
> become) associated with an IETF protocol specification upon its=20
> approval and publication as an IETF RFC.


>=20
> --
> Eric
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf=20
> Of Ralph Droms
> Sent: Friday, September 07, 2012 12:15 PM
> To: Joe Touch
> Cc: IETF Chair; IETF list discussion
> Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF=20
> Protocols
>=20
>=20
> On Sep 7, 2012, at 10:51 AM 9/7/12, Joe Touch wrote:
>=20
>> Hi, all,
>>=20
>> This statement seems fine, but it's worth noting that it would apply onl=
y to  *IETF* protocol specs.
>=20
> What did you have in mind as "noting"?  This text seems pretty clear to m=
e as applying only to "IETF protocol specifications":=20
>=20
>  the IEEE RAC will not assign a new Ethertype to  a new IETF protocol=20
> specification that needs one until the IESG has  approved the protocol=20
> specification for publication as an RFC.
>=20
>=20
>=20
>> The IESG has, IMO, no authority to make such claims for independent subm=
issions (and what about IRTF ones?), and the IEEE should recognize that suc=
h protocols are described by RFCs too.
>=20
> Where do you see any such claims in this statement?  What would you chang=
e?
>=20
> - Ralph
>=20
>>=20
>> Joe
>>=20
>> On 9/3/2012 5:02 PM, IETF Chair wrote:
>>> The IESG is considering this IESG Statement.  Comments from the communi=
ty are solicited.
>>>=20
>>> On behalf of the IESG,
>>> Russ
>>>=20
>>> --- DRAFT IESG STATEMENT ---
>>>=20
>>> Subject: Ethertype Assignments for IETF Protocols
>>>=20
>>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some=20
>>> IETF protocol specification make use of Ethertypes.  Since=20
>>> Ethertypes are a fairly scarce resource, the IEEE RAC will not=20
>>> assign a new Ethertype to a new IETF protocol specification that=20
>>> needs one until the IESG has approved the protocol specification for pu=
blication as an RFC.
>>>=20
>>> To let the IEEE RAC know that the IESG has approved an IETF protocol=20
>>> specification for publication, all future requests for assignment of=20
>>> Ethertypes for IETF protocol specifications will be made by the IESG.
>>>=20
>>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for=20
>>> use during development and experimentation.
>>>=20
>>>=20
>>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>>   IEEE standard for Local and Metropolitan Area Networks:
>>>   Overview and Architecture -- Amendment 1: Ethertypes for
>>>   Prototype and Vendor-Specific Protocol Development.
>>>=20
>>>=20
>=20


From eric.gray@ericsson.com  Tue Sep 11 03:54:25 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAB9221F87A8; Tue, 11 Sep 2012 03:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.799
X-Spam-Level: 
X-Spam-Status: No, score=-6.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itmSZBOjtrsf; Tue, 11 Sep 2012 03:54:25 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC5E21F8798; Tue, 11 Sep 2012 03:54:25 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q8BAsNN2028188 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Sep 2012 05:54:24 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.204]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 11 Sep 2012 06:54:22 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Date: Tue, 11 Sep 2012 06:54:21 -0400
Subject: RE: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Topic: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Index: Ac2QCktOHxK3ceraS3WGI4656rI54wAAWfNw
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CAE0@EUSAACMS0701.eamcs.ericsson.se>
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu> <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se> <54E5F2A0-1539-4158-BD59-8D5414CCE992@gmail.com>
In-Reply-To: <54E5F2A0-1539-4158-BD59-8D5414CCE992@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Chair <chair@ietf.org>, IETF list 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, 11 Sep 2012 10:54:25 -0000

I guess what you're saying is that "will" in this case is a statement of IE=
EE RAC policy.

In that case, I understand your point...

-----Original Message-----
From: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
Sent: Tuesday, September 11, 2012 6:43 AM
To: Eric Gray
Cc: Joe Touch; IETF Chair; IETF list discussion
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protoco=
ls
Importance: High


On Sep 11, 2012, at 6:30 AM 9/11/12, Eric Gray wrote:

> Ralph,
>=20
> 	It cannot hurt to try to make this as unambiguous as possible.
>=20
> 	The IETF cannot instruct the IEEE RAC not to assign an Ethertype to=20
> anyone who applies for it, assuming they otherwise comply with RAC=20
> requirements and are willing to pay for the assignment, if necessary.

Eric - As I understand the IESG statement, the intent is not to give any in=
structions to the IEEE RAC.  I read the text I quoted in my e-mail:

  the IEEE RAC will not assign a new Ethertype to
  a new IETF protocol specification that needs one until the IESG has
  approved the protocol specification for publication as an RFC.

as a restatement of the IEEE RAC policy, which was included in the IESG sta=
tement as explanation for this text:

  To let the IEEE RAC know that the IESG has approved an IETF protocol
  specification for publication, all future requests for assignment of
  Ethertypes for IETF protocol specifications will be made by the IESG.

which describes how the IESG will inform the IEEE RAC about which protocol =
specifications meet the IEEE RAC policy.

- Ralph


>=20
> 	However, the IETF can caution the RAC that any such assignment can=20
> only be (or
> become) associated with an IETF protocol specification upon its=20
> approval and publication as an IETF RFC.


>=20
> --
> Eric
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf=20
> Of Ralph Droms
> Sent: Friday, September 07, 2012 12:15 PM
> To: Joe Touch
> Cc: IETF Chair; IETF list discussion
> Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF=20
> Protocols
>=20
>=20
> On Sep 7, 2012, at 10:51 AM 9/7/12, Joe Touch wrote:
>=20
>> Hi, all,
>>=20
>> This statement seems fine, but it's worth noting that it would apply onl=
y to  *IETF* protocol specs.
>=20
> What did you have in mind as "noting"?  This text seems pretty clear to m=
e as applying only to "IETF protocol specifications":=20
>=20
>  the IEEE RAC will not assign a new Ethertype to  a new IETF protocol=20
> specification that needs one until the IESG has  approved the protocol=20
> specification for publication as an RFC.
>=20
>=20
>=20
>> The IESG has, IMO, no authority to make such claims for independent subm=
issions (and what about IRTF ones?), and the IEEE should recognize that suc=
h protocols are described by RFCs too.
>=20
> Where do you see any such claims in this statement?  What would you chang=
e?
>=20
> - Ralph
>=20
>>=20
>> Joe
>>=20
>> On 9/3/2012 5:02 PM, IETF Chair wrote:
>>> The IESG is considering this IESG Statement.  Comments from the communi=
ty are solicited.
>>>=20
>>> On behalf of the IESG,
>>> Russ
>>>=20
>>> --- DRAFT IESG STATEMENT ---
>>>=20
>>> Subject: Ethertype Assignments for IETF Protocols
>>>=20
>>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some=20
>>> IETF protocol specification make use of Ethertypes.  Since=20
>>> Ethertypes are a fairly scarce resource, the IEEE RAC will not=20
>>> assign a new Ethertype to a new IETF protocol specification that=20
>>> needs one until the IESG has approved the protocol specification for pu=
blication as an RFC.
>>>=20
>>> To let the IEEE RAC know that the IESG has approved an IETF protocol=20
>>> specification for publication, all future requests for assignment of=20
>>> Ethertypes for IETF protocol specifications will be made by the IESG.
>>>=20
>>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for=20
>>> use during development and experimentation.
>>>=20
>>>=20
>>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>>   IEEE standard for Local and Metropolitan Area Networks:
>>>   Overview and Architecture -- Amendment 1: Ethertypes for
>>>   Prototype and Vendor-Specific Protocol Development.
>>>=20
>>>=20
>=20


From rdroms.ietf@gmail.com  Tue Sep 11 05:29:14 2012
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6025321F8773; Tue, 11 Sep 2012 05:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Level: 
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=-0.198, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I42Us4Qr4RFv; Tue, 11 Sep 2012 05:29: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 C069421F8770; Tue, 11 Sep 2012 05:29:12 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so629588vcb.31 for <multiple recipients>; Tue, 11 Sep 2012 05:29:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=/bSkJ5nPoe6yOgKtgL6NK9m5VsuRTtB6HI/sGM61NcM=; b=CkoEAwce5bKPPJ0j7WJZAoXNiHPidTp4ZW3eWIIoHdL5apBNi0d1tFjRc+FbWqZGRG DgibEvirYhGrCyfy3RhL3dPQibUfpKj6Q/hzzacxW4kNSVGUxt0zS0bkHDcvEvapb0BP TQ9h1v3z9ONmnIu2l0UYAJ/Ot3wW+kiVW7G7NHrFo7Mqsn77zgMXmNSi0Xt0Mx9jbhtR hC+8RU2SxvRfjKWfvvEsuHDEoQ5c4WTPQjjuvHKVJbMf7YfuUTMTdJjFjnLcinPjWGAI u8f4JrJQXhts/FRyL6NoQf9hDOcsqKHS431LZ0cBSr5pphz7NUY0656XXE4S7zcs89fz 6iEQ==
Received: by 10.58.32.233 with SMTP id m9mr27343547vei.23.1347366552110; Tue, 11 Sep 2012 05:29:12 -0700 (PDT)
Received: from [10.79.104.251] (mobile-198-228-206-094.mycingular.net. [198.228.206.94]) by mx.google.com with ESMTPS id bh5sm11730539vdc.16.2012.09.11.05.29.10 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 11 Sep 2012 05:29:11 -0700 (PDT)
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu> <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se> <54E5F2A0-1539-4158-BD59-8D5414CCE992@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CAE0@EUSAACMS0701.eamcs.ericsson.se>
In-Reply-To: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CAE0@EUSAACMS0701.eamcs.ericsson.se>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <AE88C39C-4C4B-4904-AA97-A852CAA15CD8@gmail.com>
X-Mailer: iPhone Mail (9B206)
From: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Date: Tue, 11 Sep 2012 08:29:04 -0400
To: Eric Gray <eric.gray@ericsson.com>
Cc: IETF Chair <chair@ietf.org>, IETF listdiscussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Sep 2012 12:29:14 -0000

On Sep 11, 2012, at 6:54 AM, Eric Gray <eric.gray@ericsson.com> wrote:

> I guess what you're saying is that "will" in this case is a statement of I=
EEE RAC policy.

Yup ... Would s/will not/has adopted a policy not to/ clarify that part of t=
he statement?

- Ralph

>=20
> In that case, I understand your point...
>=20
> -----Original Message-----
> From: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
> Sent: Tuesday, September 11, 2012 6:43 AM
> To: Eric Gray
> Cc: Joe Touch; IETF Chair; IETF list discussion
> Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protoc=
ols
> Importance: High
>=20
>=20
> On Sep 11, 2012, at 6:30 AM 9/11/12, Eric Gray wrote:
>=20
>> Ralph,
>>=20
>>    It cannot hurt to try to make this as unambiguous as possible.
>>=20
>>    The IETF cannot instruct the IEEE RAC not to assign an Ethertype to=20=

>> anyone who applies for it, assuming they otherwise comply with RAC=20
>> requirements and are willing to pay for the assignment, if necessary.
>=20
> Eric - As I understand the IESG statement, the intent is not to give any i=
nstructions to the IEEE RAC.  I read the text I quoted in my e-mail:
>=20
>  the IEEE RAC will not assign a new Ethertype to
>  a new IETF protocol specification that needs one until the IESG has
>  approved the protocol specification for publication as an RFC.
>=20
> as a restatement of the IEEE RAC policy, which was included in the IESG st=
atement as explanation for this text:
>=20
>  To let the IEEE RAC know that the IESG has approved an IETF protocol
>  specification for publication, all future requests for assignment of
>  Ethertypes for IETF protocol specifications will be made by the IESG.
>=20
> which describes how the IESG will inform the IEEE RAC about which protocol=
 specifications meet the IEEE RAC policy.
>=20
> - Ralph
>=20
>=20
>>=20
>>    However, the IETF can caution the RAC that any such assignment can=20
>> only be (or
>> become) associated with an IETF protocol specification upon its=20
>> approval and publication as an IETF RFC.
>=20
>=20
>>=20
>> --
>> Eric
>>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf=20
>> Of Ralph Droms
>> Sent: Friday, September 07, 2012 12:15 PM
>> To: Joe Touch
>> Cc: IETF Chair; IETF list discussion
>> Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF=20
>> Protocols
>>=20
>>=20
>> On Sep 7, 2012, at 10:51 AM 9/7/12, Joe Touch wrote:
>>=20
>>> Hi, all,
>>>=20
>>> This statement seems fine, but it's worth noting that it would apply onl=
y to  *IETF* protocol specs.
>>=20
>> What did you have in mind as "noting"?  This text seems pretty clear to m=
e as applying only to "IETF protocol specifications":=20
>>=20
>> the IEEE RAC will not assign a new Ethertype to  a new IETF protocol=20
>> specification that needs one until the IESG has  approved the protocol=20=

>> specification for publication as an RFC.
>>=20
>>=20
>>=20
>>> The IESG has, IMO, no authority to make such claims for independent subm=
issions (and what about IRTF ones?), and the IEEE should recognize that such=
 protocols are described by RFCs too.
>>=20
>> Where do you see any such claims in this statement?  What would you chang=
e?
>>=20
>> - Ralph
>>=20
>>>=20
>>> Joe
>>>=20
>>> On 9/3/2012 5:02 PM, IETF Chair wrote:
>>>> The IESG is considering this IESG Statement.  Comments from the communi=
ty are solicited.
>>>>=20
>>>> On behalf of the IESG,
>>>> Russ
>>>>=20
>>>> --- DRAFT IESG STATEMENT ---
>>>>=20
>>>> Subject: Ethertype Assignments for IETF Protocols
>>>>=20
>>>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>>>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some=20
>>>> IETF protocol specification make use of Ethertypes.  Since=20
>>>> Ethertypes are a fairly scarce resource, the IEEE RAC will not=20
>>>> assign a new Ethertype to a new IETF protocol specification that=20
>>>> needs one until the IESG has approved the protocol specification for pu=
blication as an RFC.
>>>>=20
>>>> To let the IEEE RAC know that the IESG has approved an IETF protocol=20=

>>>> specification for publication, all future requests for assignment of=20=

>>>> Ethertypes for IETF protocol specifications will be made by the IESG.
>>>>=20
>>>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for=20
>>>> use during development and experimentation.
>>>>=20
>>>>=20
>>>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>>>  IEEE standard for Local and Metropolitan Area Networks:
>>>>  Overview and Architecture -- Amendment 1: Ethertypes for
>>>>  Prototype and Vendor-Specific Protocol Development.
>>>>=20
>>>>=20
>>=20
>=20

From john-ietf@jck.com  Tue Sep 11 06:10:47 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E4CF21F87CB for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 06:10:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.439
X-Spam-Level: 
X-Spam-Status: No, score=-102.439 tagged_above=-999 required=5 tests=[AWL=0.160, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7QDWgtmBR+QU for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 06:10:41 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4F43121F86B1 for <ietf@ietf.org>; Tue, 11 Sep 2012 06:10:41 -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 1TBQEg-000Iwd-EX; Tue, 11 Sep 2012 09:10:38 -0400
Date: Tue, 11 Sep 2012 09:10:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <7903414FB89B681698BE825F@JcK-HP8200.jck.com>
In-Reply-To: <20120910190711.GO84264@mx1.yitter.info>
References: <20120909184347.32346.qmail@joyce.lan> <504D97DB.3090205@cisco.com> <01OK388BAQEC0006TF@mauve.mrochek.com> <20120910190711.GO84264@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: Tue, 11 Sep 2012 13:10:47 -0000

--On Monday, September 10, 2012 15:07 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> On Mon, Sep 10, 2012 at 11:26:29AM -0700,
> ned+ietf@mauve.mrochek.com wrote:
> 
>> > No, the response is that we refer you to our policy.  As an
>> > open organization we do not remove information once posted,
>> > except under extraordinary circumstances.
>> 
>> Exactly. This sort of thing is wh a policy is needed
> 
> I attempted to hint at it already in this thread, but frankly,
> this sort of thing is why a policy _is not_ needed.  The IESG
> has that discretion already, and I would prefer to trust their
> judgement than to write a policy governing all future action,
> thereby running the risk that we'll have overlooked something
> and having a resulting problem with policies down the road.

Or, to be more specific, that we will encounter a situation that
no one quite anticipated, know perfectly well what the rational
and appropriate action is, and find that we can't take it
because we established policies that tied our hands.  

> I do not understand this nearly constitutional obsession with
> writing down policies for everything we do and don't do.  It
> turns us into a bureaucratic process slaves for no benefit I
> can see.

I've said this before, but one of the things that used to
distinguish the IETF from other standards bodies is that we
operated with good sense and leadership discretion as our
guides, spending as little time as possible on the specification
and adoption of rigid procedures.  We believed and behaved as if
IESG and IAB positions could be filled on a part-time basis,
needing people to dedicate a day or two a week from their
regular jobs, not require that they devote full-time to those
positions and do the rest of their jobs (if any) in their spare
time.   When someone showed up and said "I don't really know
anything about the Internet and almost nothing about
engineering; I'm just a procedures guy and I wasn't to help", we
would help him understand that he was in the wrong place.

We might have responded to claims that more procedures make
things easier in cases like this by noting that handling the
actual number of take-down requests a year on a case-by-case
basis would take years to reach the break-even point with the
number of IESG hours that have presumably been spent following
this long (and predictable) thread, much less the costs to the
community of participating in it.   We might also have suggested
the possibility of the IESG delegating the work to some other
group or committee -- if there are ever so many requests that
the IESG would find the time it takes to evaluate them
burdensome, we might be happy with a small committee (volunteer,
IESG-designated, chosen at random, or a combination and ideally
including Counsel) and subject to appeal on the basis that what
can be taken down can be put up again).

Clearly the IETF has changed.  My colleagues at ANSI, INCITS,
and JTC1 would have claimed that it was inevitable with growth
(and maybe with age).  And maybe I'm just old and nostalgic.
But I suggest that, if we need rigid procedures like this, the
debates it takes to get to them, and to the full-time
"standardizer" leadership to which history should teach us that
they ultimately lead, we probably have the wrong organizational
and decision-making structures and need to look forward to
structural reforms that will make the post-Kobe ones of the
early 1990s look like a minor adjustment.  Or we can voluntarily
turn the trend around, one step at a time, starting with
rejecting this proposed statement in favor of discretion,
flexibility, and intelligence (and definitely not a statement/
policy of even more complexity) and maybe even including "do we
really have resources for this" among the criteria used to
evaluate the creation or continuation of WGs.
 
best,
    john







From johnl@iecc.com  Tue Sep 11 06:59:56 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B942321F87CA for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 06:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-JsUu5Wil1j for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 06:59:56 -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 E5A3E21F87C8 for <ietf@ietf.org>; Tue, 11 Sep 2012 06:59:55 -0700 (PDT)
Received: (qmail 36066 invoked from network); 11 Sep 2012 13:59:53 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Sep 2012 13:59:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504f43d9.xn--9vv.k1208; i=johnl@user.iecc.com; bh=MYBD/W9sQmgD7fka6ve0XQLmm3/kNJAKQgxMzUAKfhk=; b=JUM6oFHNdjrLLPPaAPeEegEge08YkQfHlaYCcQTxI8QntKJWtEnlOY2GuNQkpahatGdpXp4BXkZnIU1qDuFlYJfXU3crQQTHwuzAFXE79KGkB1uNxaJ93WnGs2ScjqrNUP4CDDNICuWoqpqdqHTuKZ7vu7NuiEJz5lYM+xOv+Ho=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=504f43d9.xn--9vv.k1208; olt=johnl@user.iecc.com; bh=MYBD/W9sQmgD7fka6ve0XQLmm3/kNJAKQgxMzUAKfhk=; b=cvob6ZM1fLwzXEA6kS5FbfHECQeFi6mtY9sLyE7Es4YfD1rLLnRj+x1M6TNSHZ6GX7SKjDdfYM6CRX9e7DQAs0bfOext7d6os1+Cd7X5+MUFHu9vKHaPzQgbiWMrMrjtHlm6DOj0KF2lJYb12AeG2UTFDw5dUF+f4JnJoL1/O9I=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 11 Sep 2012 13:59:31 -0000
Message-ID: <20120911135931.47271.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
In-Reply-To: <7903414FB89B681698BE825F@JcK-HP8200.jck.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: john-ietf@jck.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, 11 Sep 2012 13:59:56 -0000

>  Or we can voluntarily
>turn the trend around, one step at a time, starting with
>rejecting this proposed statement in favor of discretion,
>flexibility, and intelligence (and definitely not a statement/
>policy of even more complexity) and maybe even including "do we
>really have resources for this" among the criteria used to
>evaluate the creation or continuation of WGs.

+1

If the IESG doesn't have the native intelligence to figure out how to
deal with a removal request based on the facts of the specific
request, we have a problem no set of rules can solve.  (Personally, I
don't think we have that problem.)

It might be useful to ask Jorge to prepare a note about dealing with
DMCA notices which are not court orders, but do require a response.
Or since the DMCA has been in effect for 14 years and we have yet to
get the first notice, we could save time and money drop the topic
unless and until the issue arises.  

There are a whole lot of hypothetical threats that the IETF might have
to deal with someday, or not.  Life is not long enough to make plans
for all of them.

R's,
John

From hallam@gmail.com  Tue Sep 11 08:37:16 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D62CF21F8688 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 08:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.565
X-Spam-Level: 
X-Spam-Status: No, score=-3.565 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bri-gVfqnUGx for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 08:37:16 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 43C8621F8678 for <ietf@ietf.org>; Tue, 11 Sep 2012 08:37:16 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so1132226obb.31 for <ietf@ietf.org>; Tue, 11 Sep 2012 08:37:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=cSYSU7Z2l9uIbe7CUxJsQxWeHdBcAWjrLCgP7imUn8o=; b=kiNNjnTNsReVanYpqcSrygypxQO1KS+uX/cL0OkzS/RgLRfQK52Mp+BRAM1bbRqWoj QIxdduAM6vi7mU8Xxgj6gvVc3XOQ/SZW2usDbdBbO8AHNsecGdxsT4ymK7RHkQCh5krY zrpQRhx8QhEdvRt+CNFC8gsDvgfQTEt7suDVBWT/G1va1Myy7SuCyoRFMD2yot1p0r3W xnXrVnWKM00rb3zCvRzWAHGFo1a3ho2eZieQQK9euTOSvjlrRmGpRj/HZh7VBohKxjka onIhJKqrX7GJ4Qyps3OG4HZMtw1fADUeGyL2pdQFxNuU/yaq3b9Ti1gBLqQMjIKNcDNU HIPQ==
MIME-Version: 1.0
Received: by 10.182.152.36 with SMTP id uv4mr18471594obb.81.1347377835918; Tue, 11 Sep 2012 08:37:15 -0700 (PDT)
Received: by 10.76.80.10 with HTTP; Tue, 11 Sep 2012 08:37:15 -0700 (PDT)
Date: Tue, 11 Sep 2012 11:37:15 -0400
Message-ID: <CAMm+Lwi_tAYqbk-z-aHjNymz_Dh-KkbhvQ5n1Mthn+W-xFCbFQ@mail.gmail.com>
Subject: Steven Bellovin appointed FTC CTO
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d044472f349c52b04c96ed980
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Sep 2012 15:37:16 -0000

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

Some happy news about an IETF-er for a change:

http://idealab.talkingpointsmemo.com/2012/09/ftcs-new-chief-technologist-deterrence-isnt-perfect.php?ref=fpb


Congrats Steve.

-- 
Website: http://hallambaker.com/

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

Some happy news about an IETF-er for a change:<div><br></div><div><a href=
=3D"http://idealab.talkingpointsmemo.com/2012/09/ftcs-new-chief-technologis=
t-deterrence-isnt-perfect.php?ref=3Dfpb">http://idealab.talkingpointsmemo.c=
om/2012/09/ftcs-new-chief-technologist-deterrence-isnt-perfect.php?ref=3Dfp=
b</a>=A0</div>
<div><br></div><div>Congrats Steve.<br clear=3D"all"><div><br></div>-- <br>=
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
><br>
</div>

--f46d044472f349c52b04c96ed980--

From rgolodner@infratection.com  Tue Sep 11 08:43:15 2012
Return-Path: <rgolodner@infratection.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA0E321F8620 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 08:43: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]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IAX7bj0JVYw2 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 08:43:15 -0700 (PDT)
Received: from omr6.networksolutionsemail.com (omr6.networksolutionsemail.com [205.178.146.56]) by ietfa.amsl.com (Postfix) with ESMTP id F303421F8616 for <ietf@ietf.org>; Tue, 11 Sep 2012 08:43:14 -0700 (PDT)
Received: from cm-omr14 (mail.networksolutionsemail.com [205.178.146.50]) by omr6.networksolutionsemail.com (8.14.4/8.14.4) with ESMTP id q8BFhDSV026051 for <ietf@ietf.org>; Tue, 11 Sep 2012 11:43:13 -0400
Authentication-Results: cm-omr14 smtp.user=rgolodner@infratection.com; auth=pass (PLAIN)
X-Authenticated-UID: rgolodner@infratection.com
Received: from [205.178.90.66] ([205.178.90.66:40714] helo=[10.10.10.33]) by cm-omr14 (envelope-from <rgolodner@infratection.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 6E/DF-32426-11C5F405; Tue, 11 Sep 2012 11:43:13 -0400
Subject: Re: Steven Bellovin appointed FTC CTO
From: Richard Golodner <rgolodner@infratection.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
In-Reply-To: <CAMm+Lwi_tAYqbk-z-aHjNymz_Dh-KkbhvQ5n1Mthn+W-xFCbFQ@mail.gmail.com>
References: <CAMm+Lwi_tAYqbk-z-aHjNymz_Dh-KkbhvQ5n1Mthn+W-xFCbFQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 11 Sep 2012 10:43:12 -0500
Message-ID: <1347378192.2529.1.camel@Andromeda>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Content-Transfer-Encoding: 7bit
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: Tue, 11 Sep 2012 15:43:15 -0000

On Tue, 2012-09-11 at 11:37 -0400, Phillip Hallam-Baker wrote:
> Some happy news about an IETF-er for a change:
> 
> 
> http://idealab.talkingpointsmemo.com/2012/09/ftcs-new-chief-technologist-deterrence-isnt-perfect.php?ref=fpb 
> 
> 
> Congrats Steve.
> 
> 
> -- 
> Website: http://hallambaker.com/
> 
> 

	Congratulations Dr.Bellovin. A good fit I believe.
	Sincerely, Richard


From chair@ietf.org  Tue Sep 11 08:57:29 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94A5021F845E for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 08:57: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvuuk8iOtkJ0 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 08:57:29 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB1221F845C for <ietf@ietf.org>; Tue, 11 Sep 2012 08:57:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A876712DA66 for <ietf@ietf.org>; Tue, 11 Sep 2012 08:57:29 -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 aCmC-SXYk9pb for <ietf@ietf.org>; Tue, 11 Sep 2012 08:57:29 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 658BD12DA59 for <ietf@ietf.org>; Tue, 11 Sep 2012 08:57:29 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protocols
From: IETF Chair <chair@ietf.org>
In-Reply-To: <54E5F2A0-1539-4158-BD59-8D5414CCE992@gmail.com>
Date: Tue, 11 Sep 2012 11:57:26 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <E1DD2514-7AB2-426C-A7CF-BA7921AC7C7E@ietf.org>
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu> <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se> <54E5F2A0-1539-4158-BD59-8D5414CCE992@gmail.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Sep 2012 15:57:29 -0000

I propose the following rewording to address the issue that has been raised.

Russ

= = = = = = = = =

The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
(See http://standards.ieee.org/develop/regauth/ethertype/.)  Some IETF
protocol specification make use of Ethertypes.  Since Ethertypes are a
fairly scarce resource, the IEEE RAC has let us know that they will not
assign a new Ethertype to a new IETF protocol specification that needs
one until the IESG has approved the protocol specification for
publication as an RFC.

To let the IEEE RAC know that the IESG has approved an IETF protocol
specification for publication, all future requests for assignment of
Ethertypes for IETF protocol specifications will be made by the IESG.

Note that playpen Ethertypes have been assigned in IEEE 802 [1] for use
during protocol development and experimentation.


[1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
    IEEE standard for Local and Metropolitan Area Networks:
    Overview and Architecture -- Amendment 1: Ethertypes for
    Prototype and Vendor-Specific Protocol Development.


From eric.gray@ericsson.com  Tue Sep 11 09:37:27 2012
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6FDA21F845F; Tue, 11 Sep 2012 09:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.766
X-Spam-Level: 
X-Spam-Status: No, score=-6.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bl1EkLmAbwWY; Tue, 11 Sep 2012 09:37:26 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id B938121F845A; Tue, 11 Sep 2012 09:37:26 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q8BGfHsA022700; Tue, 11 Sep 2012 11:41:26 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([169.254.1.204]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 11 Sep 2012 12:37:03 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Date: Tue, 11 Sep 2012 12:36:59 -0400
Subject: RE: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Topic: Draft IESG Statement on Ethertype Assignments for IETF Protocols
Thread-Index: Ac2QGTun5c6sFGPOR7C23tYK0jTRlAAImLCA
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CDA7@EUSAACMS0701.eamcs.ericsson.se>
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org> <504A09EB.1090301@isi.edu> <792B97C6-3490-43C3-AFDF-69C6C412FE3E@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CADC@EUSAACMS0701.eamcs.ericsson.se> <54E5F2A0-1539-4158-BD59-8D5414CCE992@gmail.com> <C0AC8FAB6849AB4FADACCC70A949E2F12FAB95CAE0@EUSAACMS0701.eamcs.ericsson.se> <AE88C39C-4C4B-4904-AA97-A852CAA15CD8@gmail.com>
In-Reply-To: <AE88C39C-4C4B-4904-AA97-A852CAA15CD8@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Chair <chair@ietf.org>, IETF listdiscussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Sep 2012 16:37:27 -0000

Yes, something along those lines would make it clearer.  Thanks!

-----Original Message-----
From: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
Sent: Tuesday, September 11, 2012 8:29 AM
To: Eric Gray
Cc: Joe Touch; IETF Chair; IETF listdiscussion
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protoco=
ls
Importance: High





On Sep 11, 2012, at 6:54 AM, Eric Gray <eric.gray@ericsson.com> wrote:

> I guess what you're saying is that "will" in this case is a statement of =
IEEE RAC policy.

Yup ... Would s/will not/has adopted a policy not to/ clarify that part of =
the statement?

- Ralph

>=20
> In that case, I understand your point...
>=20
> -----Original Message-----
> From: Ralph Droms [mailto:rdroms.ietf@gmail.com]
> Sent: Tuesday, September 11, 2012 6:43 AM
> To: Eric Gray
> Cc: Joe Touch; IETF Chair; IETF list discussion
> Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF=20
> Protocols
> Importance: High
>=20
>=20
> On Sep 11, 2012, at 6:30 AM 9/11/12, Eric Gray wrote:
>=20
>> Ralph,
>>=20
>>    It cannot hurt to try to make this as unambiguous as possible.
>>=20
>>    The IETF cannot instruct the IEEE RAC not to assign an Ethertype=20
>> to anyone who applies for it, assuming they otherwise comply with RAC=20
>> requirements and are willing to pay for the assignment, if necessary.
>=20
> Eric - As I understand the IESG statement, the intent is not to give any =
instructions to the IEEE RAC.  I read the text I quoted in my e-mail:
>=20
>  the IEEE RAC will not assign a new Ethertype to  a new IETF protocol=20
> specification that needs one until the IESG has  approved the protocol=20
> specification for publication as an RFC.
>=20
> as a restatement of the IEEE RAC policy, which was included in the IESG s=
tatement as explanation for this text:
>=20
>  To let the IEEE RAC know that the IESG has approved an IETF protocol =20
> specification for publication, all future requests for assignment of =20
> Ethertypes for IETF protocol specifications will be made by the IESG.
>=20
> which describes how the IESG will inform the IEEE RAC about which protoco=
l specifications meet the IEEE RAC policy.
>=20
> - Ralph
>=20
>=20
>>=20
>>    However, the IETF can caution the RAC that any such assignment can=20
>> only be (or
>> become) associated with an IETF protocol specification upon its=20
>> approval and publication as an IETF RFC.
>=20
>=20
>>=20
>> --
>> Eric
>>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf=20
>> Of Ralph Droms
>> Sent: Friday, September 07, 2012 12:15 PM
>> To: Joe Touch
>> Cc: IETF Chair; IETF list discussion
>> Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF=20
>> Protocols
>>=20
>>=20
>> On Sep 7, 2012, at 10:51 AM 9/7/12, Joe Touch wrote:
>>=20
>>> Hi, all,
>>>=20
>>> This statement seems fine, but it's worth noting that it would apply on=
ly to  *IETF* protocol specs.
>>=20
>> What did you have in mind as "noting"?  This text seems pretty clear to =
me as applying only to "IETF protocol specifications":=20
>>=20
>> the IEEE RAC will not assign a new Ethertype to  a new IETF protocol=20
>> specification that needs one until the IESG has  approved the=20
>> protocol specification for publication as an RFC.
>>=20
>>=20
>>=20
>>> The IESG has, IMO, no authority to make such claims for independent sub=
missions (and what about IRTF ones?), and the IEEE should recognize that su=
ch protocols are described by RFCs too.
>>=20
>> Where do you see any such claims in this statement?  What would you chan=
ge?
>>=20
>> - Ralph
>>=20
>>>=20
>>> Joe
>>>=20
>>> On 9/3/2012 5:02 PM, IETF Chair wrote:
>>>> The IESG is considering this IESG Statement.  Comments from the commun=
ity are solicited.
>>>>=20
>>>> On behalf of the IESG,
>>>> Russ
>>>>=20
>>>> --- DRAFT IESG STATEMENT ---
>>>>=20
>>>> Subject: Ethertype Assignments for IETF Protocols
>>>>=20
>>>> The IEEE Registration Authority Committee (RAC) assigns Ethertypes.
>>>> (See http://standards.ieee.org/develop/regauth/ethertype/.)  Some=20
>>>> IETF protocol specification make use of Ethertypes.  Since=20
>>>> Ethertypes are a fairly scarce resource, the IEEE RAC will not=20
>>>> assign a new Ethertype to a new IETF protocol specification that=20
>>>> needs one until the IESG has approved the protocol specification for p=
ublication as an RFC.
>>>>=20
>>>> To let the IEEE RAC know that the IESG has approved an IETF=20
>>>> protocol specification for publication, all future requests for=20
>>>> assignment of Ethertypes for IETF protocol specifications will be made=
 by the IESG.
>>>>=20
>>>> Note that playpen Ethertypes have been assigned in IEEE 802 [1] for=20
>>>> use during development and experimentation.
>>>>=20
>>>>=20
>>>> [1] IEEE Std 802a-2003 (Amendment to IEEE Std 802-2001).
>>>>  IEEE standard for Local and Metropolitan Area Networks:
>>>>  Overview and Architecture -- Amendment 1: Ethertypes for =20
>>>> Prototype and Vendor-Specific Protocol Development.
>>>>=20
>>>>=20
>>=20
>=20

From smb@cs.columbia.edu  Tue Sep 11 11:33:22 2012
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72B4A21F854E for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 11:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DlihY+oxZa0u for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 11:33:21 -0700 (PDT)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id BEB3621F84D7 for <ietf@ietf.org>; Tue, 11 Sep 2012 11:33:21 -0700 (PDT)
Received: from [10.9.0.134] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q8BIXGdR015455 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 11 Sep 2012 14:33:20 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Subject: Re: Steven Bellovin appointed FTC CTO
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <CAMm+Lwi_tAYqbk-z-aHjNymz_Dh-KkbhvQ5n1Mthn+W-xFCbFQ@mail.gmail.com>
Date: Tue, 11 Sep 2012 14:33:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <36F2596B-CF62-4837-AC2B-342CB328E94B@cs.columbia.edu>
References: <CAMm+Lwi_tAYqbk-z-aHjNymz_Dh-KkbhvQ5n1Mthn+W-xFCbFQ@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1486)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
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: Tue, 11 Sep 2012 18:33:22 -0000

On Sep 11, 2012, at 11:37 AM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:

> Some happy news about an IETF-er for a change:
>=20
> =
http://idealab.talkingpointsmemo.com/2012/09/ftcs-new-chief-technologist-d=
eterrence-isnt-perfect.php?ref=3Dfpb=20
>=20
> Congrats Steve.

Thanks!=20

Yes, for the next year I'll be at the Federal Trade Commission,
advising on security, privacy, and other technical issues.  Because
I'm still doing technology and not just policy, I will not have to
put the technical part of my brain into storage while I'm here.

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






From bob.hinden@gmail.com  Tue Sep 11 12:18:45 2012
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC57B21F868A for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 12:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.686
X-Spam-Level: 
X-Spam-Status: No, score=-102.686 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_RECV_BEZEQINT_B=0.763, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D7hH6EWFQUQS for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 12:18:44 -0700 (PDT)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 07B9C21F8685 for <ietf@ietf.org>; Tue, 11 Sep 2012 12:18:43 -0700 (PDT)
Received: by eekb45 with SMTP id b45so762112eek.31 for <ietf@ietf.org>; Tue, 11 Sep 2012 12:18:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=WndzDQDRKEOucdtT1ok9gpXEkDuGkBdvecub+7c09Rc=; b=lzt/aeImEImKh18OR8vJJasyCkti6XC7EKT4WpBEg5CMTk3Q/4z2vwdKgnTWjY87mL yzZvR99k78XsBuTaX344dAnV/o/zMbqCYLKledy1Ky3LNHMPE8BYMGOyFCqYbhTz/FBT Vw7yGrKFQ6PZ68cGcb7rthj+8hLfOGELTQY0Buyztm3gq2Skuz+Rh6L9pYSGwW55GcsV oHo4URHLhdcLYzOm+fDmn7Evc/fKYqUvFdFc3VNvw4jbC3fIp99RclYLJI1en65BpojR 0G22EwTtCHHTx1WUWBwYfiz6TpczBhw3xjTsYRmEFlB26rqNCH+p8Ff6Wr/4u3oT379R 1mww==
Received: by 10.14.215.197 with SMTP id e45mr27196315eep.36.1347391123225; Tue, 11 Sep 2012 12:18:43 -0700 (PDT)
Received: from [192.168.5.42] (bzq-218-39-90.cablep.bezeqint.net. [81.218.39.90]) by mx.google.com with ESMTPS id u47sm49666738eeo.9.2012.09.11.12.18.38 (version=SSLv3 cipher=OTHER); Tue, 11 Sep 2012 12:18:42 -0700 (PDT)
Subject: Re: Steven Bellovin appointed FTC CTO
Mime-Version: 1.0 (Apple Message framework v1280)
Content-Type: text/plain; charset=iso-8859-1
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <36F2596B-CF62-4837-AC2B-342CB328E94B@cs.columbia.edu>
Date: Tue, 11 Sep 2012 22:18:36 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <BDC0ED60-E612-4333-98B0-AC56F35475F5@gmail.com>
References: <CAMm+Lwi_tAYqbk-z-aHjNymz_Dh-KkbhvQ5n1Mthn+W-xFCbFQ@mail.gmail.com> <36F2596B-CF62-4837-AC2B-342CB328E94B@cs.columbia.edu>
To: Steven Bellovin <smb@cs.columbia.edu>
X-Mailer: Apple Mail (2.1280)
Cc: Phillip Hallam-Baker <hallam@gmail.com>, Bob Hinden <bob.hinden@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: Tue, 11 Sep 2012 19:18:45 -0000

Steve,

Congratulations!!!   =20

Bob

On Sep 11, 2012, at 9:33 PM, Steven Bellovin wrote:

>=20
> On Sep 11, 2012, at 11:37 AM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:
>=20
>> Some happy news about an IETF-er for a change:
>>=20
>> =
http://idealab.talkingpointsmemo.com/2012/09/ftcs-new-chief-technologist-d=
eterrence-isnt-perfect.php?ref=3Dfpb=20
>>=20
>> Congrats Steve.
>=20
> Thanks!=20
>=20
> Yes, for the next year I'll be at the Federal Trade Commission,
> advising on security, privacy, and other technical issues.  Because
> I'm still doing technology and not just policy, I will not have to
> put the technical part of my brain into storage while I'm here.
>=20
> 		--Steve Bellovin, https://www.cs.columbia.edu/~smb
>=20
>=20
>=20
>=20
>=20


From cabo@tzi.org  Tue Sep 11 12:42:11 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 616BC21F8673 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 12:42:11 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2G7zOUpNafW for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 12:42:10 -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 8B4E721F8669 for <ietf@ietf.org>; Tue, 11 Sep 2012 12:42:10 -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.3/8.14.3) with ESMTP id q8BJfsCB013559; Tue, 11 Sep 2012 21:41:55 +0200 (CEST)
Received: from [192.168.217.105] (p54894B4C.dip.t-dialin.net [84.137.75.76]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 60F721A1; Tue, 11 Sep 2012 21:41:54 +0200 (CEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7903414FB89B681698BE825F@JcK-HP8200.jck.com>
Date: Tue, 11 Sep 2012 21:41:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E21742E-2DEE-4A7B-9C8C-1E587D82F0E2@tzi.org>
References: <20120909184347.32346.qmail@joyce.lan> <504D97DB.3090205@cisco.com> <01OK388BAQEC0006TF@mauve.mrochek.com> <20120910190711.GO84264@mx1.yitter.info> <7903414FB89B681698BE825F@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1486)
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, 11 Sep 2012 19:42:11 -0000

On Sep 11, 2012, at 15:10, John C Klensin <john-ietf@jck.com> wrote:

> rejecting this proposed statement in favor of discretion,

I'm not privy to the circumstances that caused the original proposal to =
come up.
Maybe the reason was that the IESG *wants* its hands bound so there is =
no further need to waste time on such decisions (e.g., because the =
policy discourages or can be used to discourage requests of this kind in =
the first place).

But this is all speculation without further background.
And I'm not that interested in the subject anyway.
(I *am* interested we don't use it as an excuse to break the I-D =
archive.)

Gr=FC=DFe, Carsten


From dan@fsround.org  Tue Sep 11 12:59:05 2012
Return-Path: <dan@fsround.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 0ED1821F86F0 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 12:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k3Ls1MlCbnBn for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 12:59:04 -0700 (PDT)
Received: from mail.fsround.org (unknown [66.63.57.4]) by ietfa.amsl.com (Postfix) with ESMTP id 212D521F85A1 for <ietf@ietf.org>; Tue, 11 Sep 2012 12:59:04 -0700 (PDT)
Received: from MAIL2.fsround.org ([fe80::71ac:4745:9f75:c49f]) by MAIL2.fsround.org ([fe80::71ac:4745:9f75:c49f%11]) with mapi id 14.02.0318.001; Tue, 11 Sep 2012 15:58:18 -0400
From: Dan Schutzer <dan@fsround.org>
To: 'Richard Golodner' <rgolodner@infratection.com>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: RE: Steven Bellovin appointed FTC CTO
Thread-Topic: Steven Bellovin appointed FTC CTO
Thread-Index: AQHNkDM61Sz3+hd0U0mr7KLQFw/Jt5eFivQAgAAETuA=
Date: Tue, 11 Sep 2012 19:58:17 +0000
Message-ID: <D05F3EAA82A2724AB500AC9F59E4D42410E877BB@MAIL2.fsround.org>
References: <CAMm+Lwi_tAYqbk-z-aHjNymz_Dh-KkbhvQ5n1Mthn+W-xFCbFQ@mail.gmail.com> <1347378192.2529.1.camel@Andromeda>
In-Reply-To: <1347378192.2529.1.camel@Andromeda>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.10.10.15]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
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: Tue, 11 Sep 2012 19:59:05 -0000

TXkgY29uZ3JhdHVsYXRpb25zIHRvIHlvdSBhcyB3ZWxsIFN0ZXZlDQoNCkRhbiBTY2h1dHplcg0K
DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaWV0Zi1ib3VuY2VzQGlldGYub3Jn
IFttYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgUmljaGFyZCBHb2xv
ZG5lcg0KU2VudDogVHVlc2RheSwgU2VwdGVtYmVyIDExLCAyMDEyIDExOjQzIEFNDQpUbzogUGhp
bGxpcCBIYWxsYW0tQmFrZXINCkNjOiBJRVRGIERpc2N1c3Npb24gTWFpbGluZyBMaXN0DQpTdWJq
ZWN0OiBSZTogU3RldmVuIEJlbGxvdmluIGFwcG9pbnRlZCBGVEMgQ1RPDQoNCk9uIFR1ZSwgMjAx
Mi0wOS0xMSBhdCAxMTozNyAtMDQwMCwgUGhpbGxpcCBIYWxsYW0tQmFrZXIgd3JvdGU6DQo+IFNv
bWUgaGFwcHkgbmV3cyBhYm91dCBhbiBJRVRGLWVyIGZvciBhIGNoYW5nZToNCj4gDQo+IA0KPiBo
dHRwOi8vaWRlYWxhYi50YWxraW5ncG9pbnRzbWVtby5jb20vMjAxMi8wOS9mdGNzLW5ldy1jaGll
Zi10ZWNobm9sb2dpc3QtZGV0ZXJyZW5jZS1pc250LXBlcmZlY3QucGhwP3JlZj1mcGIgDQo+IA0K
PiANCj4gQ29uZ3JhdHMgU3RldmUuDQo+IA0KPiANCj4gLS0gDQo+IFdlYnNpdGU6IGh0dHA6Ly9o
YWxsYW1iYWtlci5jb20vDQo+IA0KPiANCg0KCUNvbmdyYXR1bGF0aW9ucyBEci5CZWxsb3Zpbi4g
QSBnb29kIGZpdCBJIGJlbGlldmUuDQoJU2luY2VyZWx5LCBSaWNoYXJkDQoNCg==

From paf@frobbit.se  Tue Sep 11 14:15:35 2012
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D6CA21E8037 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 14:15:35 -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=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q0HJGQNIe4tW for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 14:15:34 -0700 (PDT)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id 20A9921F8682 for <ietf@ietf.org>; Tue, 11 Sep 2012 14:15:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id BFB04168803F7; Tue, 11 Sep 2012 23:15:30 +0200 (CEST)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nOgnaeHxLYZe; Tue, 11 Sep 2012 23:15:26 +0200 (CEST)
Received: from [192.168.200.32] (LPuteaux-151-43-9-223.w217-128.abo.wanadoo.fr [217.128.248.223]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 435B416880379; Tue, 11 Sep 2012 23:15:24 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Subject: Re: Steven Bellovin appointed FTC CTO
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <36F2596B-CF62-4837-AC2B-342CB328E94B@cs.columbia.edu>
Date: Tue, 11 Sep 2012 23:14:35 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <95FAD635-23B7-416F-84A9-3B83EE9A7D8A@frobbit.se>
References: <CAMm+Lwi_tAYqbk-z-aHjNymz_Dh-KkbhvQ5n1Mthn+W-xFCbFQ@mail.gmail.com> <36F2596B-CF62-4837-AC2B-342CB328E94B@cs.columbia.edu>
To: Steven Bellovin <smb@cs.columbia.edu>
X-Mailer: Apple Mail (2.1486)
Cc: Phillip Hallam-Baker <hallam@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: Tue, 11 Sep 2012 21:15:35 -0000

On 11 sep 2012, at 20:33, Steven Bellovin <smb@cs.columbia.edu> wrote:

> Yes, for the next year I'll be at the Federal Trade Commission,
> advising on security, privacy, and other technical issues.  Because
> I'm still doing technology and not just policy, I will not have to
> put the technical part of my brain into storage while I'm here.

Steve, congratulations!

   Patrik


From adrian@olddog.co.uk  Tue Sep 11 14:25:22 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9354821F86B2 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 14:25: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sr0Rce+Epsv8 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 14:25:22 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id D697721F86B3 for <ietf@ietf.org>; Tue, 11 Sep 2012 14:25:21 -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 q8BLPKeX023698;  Tue, 11 Sep 2012 22:25:20 +0100
Received: from 950129200 ([200.35.189.178]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q8BLPFpO023644 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 11 Sep 2012 22:25:19 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Carsten Bormann'" <cabo@tzi.org>
Subject: RE: the usual mail stuff, was IETF...the unconference of SDOs
Date: Tue, 11 Sep 2012 22:25:13 +0100
Message-ID: <03ab01cd9063$f13c37f0$d3b4a7d0$@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: Ac2QY+SUIN0M2imcRgCexs7gFSSAqg==
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: Tue, 11 Sep 2012 21:25:22 -0000

Carsten sed:

> I'm not an expert for this, but, as far as I am aware of, it has not been
> possible to productively participate in e-mail conversations using Outlook.

You're right, Carsten. Nothing I have done in the last 10 years has been in any
way productive.

Adrian


From wjhns1@hardakers.net  Wed Sep 12 09:44:47 2012
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7935B21F856C for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 09:44:47 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o4JzQD+DBT9k for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 09:44:47 -0700 (PDT)
Received: from mail.hardakers.net (unknown [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id 156B721F8532 for <ietf@ietf.org>; Wed, 12 Sep 2012 09:44:47 -0700 (PDT)
Received: from localhost (wjhw.hardakers.net [IPv6:2001:470:1f00:187:62d8:19ff:fed4:c8b6]) by mail.hardakers.net (Postfix) with ESMTPSA id C061D28E; Wed, 12 Sep 2012 09:44:45 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Steven Bellovin <smb@cs.columbia.edu>
Subject: Re: Steven Bellovin appointed FTC CTO
References: <CAMm+Lwi_tAYqbk-z-aHjNymz_Dh-KkbhvQ5n1Mthn+W-xFCbFQ@mail.gmail.com> <36F2596B-CF62-4837-AC2B-342CB328E94B@cs.columbia.edu>
Date: Wed, 12 Sep 2012 09:44:45 -0700
In-Reply-To: <36F2596B-CF62-4837-AC2B-342CB328E94B@cs.columbia.edu> (Steven Bellovin's message of "Tue, 11 Sep 2012 14:33:16 -0400")
Message-ID: <0lk3vzgphe.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: Phillip Hallam-Baker <hallam@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: Wed, 12 Sep 2012 16:44:47 -0000

Steven Bellovin <smb@cs.columbia.edu> writes:

> Yes, for the next year I'll be at the Federal Trade Commission,
> advising on security, privacy, and other technical issues.  Because
> I'm still doing technology and not just policy, I will not have to
> put the technical part of my brain into storage while I'm here.

It's rare, these days, to see people with a clue appointed to important
positions where a difference can be made.  I'm very happy that it
happens occasionally; your appointment proves it can.
-- 
Wes Hardaker
SPARTA, Inc.

From Kuor-Hsin.Chang@us.elster.com  Tue Sep 11 18:05:29 2012
Return-Path: <Kuor-Hsin.Chang@us.elster.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 380DB21F8530 for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 18:05:29 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZC675kw-AK0H for <ietf@ietfa.amsl.com>; Tue, 11 Sep 2012 18:05:28 -0700 (PDT)
Received: from mail196.messagelabs.com (mail196.messagelabs.com [216.82.254.67]) by ietfa.amsl.com (Postfix) with SMTP id 84D8321F854C for <ietf@ietf.org>; Tue, 11 Sep 2012 18:05:28 -0700 (PDT)
X-Env-Sender: Kuor-Hsin.Chang@us.elster.com
X-Msg-Ref: server-14.tower-196.messagelabs.com!1347411914!4937992!2
X-Originating-IP: [129.179.1.27]
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23404 invoked from network); 12 Sep 2012 01:05:14 -0000
Received: from ip27.net129179-1.block1.us.syntegra.com (HELO us-smtp01.smtp.elster.com) (129.179.1.27) by server-14.tower-196.messagelabs.com with SMTP; 12 Sep 2012 01:05:14 -0000
To: ietf@ietf.org
MIME-Version: 1.0
Subject: Fw: IETF 95 Date Change Proposal - Round 2
X-KeepSent: 38B61C7B:9177207F-88257A77:0005998C; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.3 September 15, 2011
From: Kuor-Hsin.Chang@us.elster.com
Message-ID: <OF38B61C7B.9177207F-ON88257A77.0005998C-88257A77.0005AFA9@gb.elster.com>
Date: Tue, 11 Sep 2012 18:02:53 -0700
X-MIMETrack: Serialize by Router on US-SMTP01.domino.elster-group.com/RIM-TEMP(Release 8.5.2FP3|July 10, 2011) at 09/11/2012 08:57:38 PM, Serialize complete at 09/11/2012 08:57:38 PM
Content-Type: multipart/alternative; boundary="=_alternative 0005A38C88257A77_="
X-Mailman-Approved-At: Wed, 12 Sep 2012 09:55:36 -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: Wed, 12 Sep 2012 01:05:29 -0000

This is a multipart message in MIME format.
--=_alternative 0005A38C88257A77_=
Content-Type: text/plain; charset="US-ASCII"

3 - 8 April 2016 is good.

----- Forwarded by Kuor-Hsin Chang/USE/Elster on 09/11/2012 06:01 PM -----

From:
IETF Administrative Director <iad@ietf.org>
To:
IETF Announcement List <ietf-announce@ietf.org>, 
Cc:
iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, 
iesg@ietf.org
Date:
09/06/2012 12:13 PM
Subject:
IETF 95 Date Change Proposal - Round 2
Sent by:
ietf-announce-bounces@ietf.org



All


The IAOC is seeking community feedback on a proposed date change for IETF 
95
originally scheduled for 27 March to 1 April 2016.

After considering community feedback on a proposed change to 20 - 25 March
2016, the IAOC is proposing 3 - 8 April 2016 to avoid the impact on travel 
and
attendance during the 20 - 25 March period.

Comments appreciated to ietf@ietf.org by 20 September 2012.

Ray Pelletier
IETF Administrative Director

______________________________________________________________________
This email has been spam and virus checked by Elster IT Services.

--=_alternative 0005A38C88257A77_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2>3 - 8 April 2016</font></tt><font size=2 face="sans-serif">
is good.</font>
<br>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Kuor-Hsin
Chang/USE/Elster on 09/11/2012 06:01 PM -----</font>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">IETF Administrative Director &lt;iad@ietf.org&gt;</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">IETF Announcement List &lt;ietf-announce@ietf.org&gt;,
</font>
<tr>
<td valign=top><font size=1 color=#5f5f5f face="sans-serif">Cc:</font>
<td><font size=1 face="sans-serif">iaoc@ietf.org, iab@iab.org, ietf@ietf.org,
wgchairs@ietf.org, iesg@ietf.org</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">09/06/2012 12:13 PM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">IETF 95 Date Change Proposal - Round
2</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">ietf-announce-bounces@ietf.org</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>All<br>
<br>
<br>
The IAOC is seeking community feedback on a proposed date change for IETF
95<br>
originally scheduled for 27 March to 1 April 2016.<br>
<br>
After considering community feedback on a proposed change to 20 - 25 March<br>
2016, the IAOC is proposing 3 - 8 April 2016 to avoid the impact on travel
and<br>
attendance during the 20 - 25 March period.<br>
<br>
Comments appreciated to ietf@ietf.org by 20 September 2012.<br>
<br>
Ray Pelletier<br>
IETF Administrative Director<br>
<br>
______________________________________________________________________<br>
This email has been spam and virus checked by Elster IT Services.<br>
</font></tt>
--=_alternative 0005A38C88257A77_=--

From lars@netapp.com  Wed Sep 12 09:59:10 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D52921F865F for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 09:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.643
X-Spam-Level: 
X-Spam-Status: No, score=-11.643 tagged_above=-999 required=5 tests=[AWL=0.845, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_HI=-8, SARE_NETPROD=0.111]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S-BerMAQx50v for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 09:59:09 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 605EF21F857D for <ietf@ietf.org>; Wed, 12 Sep 2012 09:59:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,410,1344236400";  d="p7s'?scan'208";a="688824370"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 12 Sep 2012 09:59:09 -0700
Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q8CGx9fP027910 for <ietf@ietf.org>; Wed, 12 Sep 2012 09:59:09 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.212]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.02.0309.002; Wed, 12 Sep 2012 09:59:08 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: IETF IETF <ietf@ietf.org>
Subject: Call for Nominations: Applied Networking Research Prize 2013
Thread-Topic: Call for Nominations: Applied Networking Research Prize 2013
Thread-Index: AQHNkQfrUtkftmdCbkyY9CoHX1sjUA==
Date: Wed, 12 Sep 2012 16:59:07 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E9068235E2@SACEXCMBX01-PRD.hq.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_71B570C8-592F-4779-96D7-3A51648CAEEE"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "anrp@irtf.org" <anrp@irtf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Sep 2012 16:59:10 -0000

--Apple-Mail=_71B570C8-592F-4779-96D7-3A51648CAEEE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


                      CALL FOR NOMINATIONS:

           APPLIED NETWORKING RESEARCH PRIZE (ANRP) 2013

                      http://irtf.org/anrp

********************************************************************
***     Submit nominations for the 2013 award period of the      ***
***  Applied Networking Research Prize until November 30, 2012!  ***
***                                                              ***
***    (Please share this announcement with your colleagues.)    ***
********************************************************************

The Applied Networking Research Prize (ANRP) is awarded for recent
results in applied networking research that are relevant for
transitioning into shipping Internet products and related
standardization efforts. Researchers with relevant, recent results
are encouraged to apply for this prize, which will offer them the
opportunity to present and discuss their work with the engineers,
network operators, policy makers and scientists that participate in
the Internet Engineering Task Force (IETF) and its research arm, the
Internet Research Task Force (IRTF). Third-party nominations for this
prize are also encouraged. The goal of the Applied Networking
Research Prize is to recognize the best new ideas in networking, and
bring them to the IETF and IRTF especially in cases where they would
not otherwise see much exposure or discussion.

The Applied Networking Research Prize (ANRP) consists of:

 =95 cash prize of $500 (USD)
 =95 invited talk at the IRTF Open Meeting
 =95 travel grant to attend a week-long IETF meeting (airfare, hotel,
   registration, stipend)
 =95 recognition at the IETF plenary
 =95 invitation to related social activities
 =95 potential for additional travel grants to future IETF meetings,
   based on community feedback

The Applied Networking Research Prize will be awarded once per
calendar year. Each year, several winners will be chosen and invited
to present their work at one of the three IETF meetings during the
year.


HOW TO NOMINATE

Only a single person can be nominated for the award. The basis of the
nomination is a peer-reviewed, original journal, conference or
workshop paper they authored, which was recently published or
accepted for publication. The nominee must be one of the main authors
of the nominated paper. Both self nominations (nominating one=92s own
paper) and third-party nominations (nominating someone else=92s paper)
are encouraged.

The nominated paper should provide a scientific foundation for
possible future IETF engineering work or IRTF research and
experimentation, analyze the behavior of Internet protocols in
operational deployments or realistic testbeds, make an important
contribution to the understanding of Internet scalability,
performance, reliability, security or capability, or otherwise be of
relevance to ongoing or future IETF or IRTF activities.

Applicants must briefly describe how the nominated paper relates to
these goals, and are encouraged to describe how a presentation of
these research results would foster their transition into new IETF
engineering or IRTF experimentation, or otherwise seed new activities
that will have an impact on the real-world Internet.

The goal of the Applied Networking Research Prize (ANRP) is to foster
the transitioning of research results into real-world benefits for
the Internet. Therefore, applicants must indicate that they (or the
nominee, in case of third-party nominations) are available to attend
at least one of the year=92s IETF meetings in person and in its
entirety.

Nominations must include:

 =95 the name and email address of the nominee
 =95 a bibliographic reference to the published (or accepted)
   nominated paper
 =95 a PDF copy of the nominated paper
 =95 a statement that describes how the nominated paper fulfills the
   goals of the award
 =95 a statement about which of the year=92s IETF meetings the nominee
   would be available to attend in person and in its entirety
 =95 a brief biography or CV of the nominee
 =95 optionally, any other supporting information (link to nominee=92s
   web site, etc.)

Nominations are submitted via the submission site at
http://irtf.org/anrp/2013/. In exceptional cases, nominations may
also be submitted by email to anrp@irtf.org.


SELECTION PROCESS

A small selection committee comprised of individuals knowledgeable
about the IRTF, IETF and the broader networking research community
will evaluate the submissions against these selection criteria.


IMPORTANT DATES

Applications close: November 30, 2012 (hard)
Notifications:      December 20, 2012


SPONSORS

The Applied Networking Research Prize (ANRP) is supported by the
Internet Society (ISOC), as part of its Internet Research Award
Programme, in coordination with the Internet Research Task Force
(IRTF).


HELP PUBLICIZE THE ANRP

If you would like to help publicize the ANRP within your
organization, you are welcome to print and use the flyer at
http://irtf.org/anrp-2013-flyer.pdf


--Apple-Mail=_71B570C8-592F-4779-96D7-3A51648CAEEE
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDkxMjE2NTg0M1owIwYJKoZIhvcNAQkEMRYEFBjT
aX077WTgDs97msFn1R17+s6zMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAJ7bf9UI
4PGq4Jubz7XQazZ3+6AovTs7o+DzaMsSR0HvUMxvaja1bdemvPOXzGvMap6dm3pMiob8SMB7pxcT
sjuoyLRTI0eS4wnE9A36M6BR5yUXae4MkPWf3rCmwrztVOR2NjwYZbKDctmIeaMLmLafLL13Vv+7
8v77UcxvdAseOjme5Cn/wlblWBrbtK1ZQLZxUGMZGuZEWB8qGej7BZHinNmLmqqi/gFGNSjNG/DG
C8QQWRryoVYYVraxLigqf0EPy7czYS3bBuCvKQ0Xau3sMwl76hzI6/XzPhMgvPlhqHWMDifvkxPy
shTtuPsr07LT+l1fY1Z01ICN+HLhq9EAAAAAAAA=

--Apple-Mail=_71B570C8-592F-4779-96D7-3A51648CAEEE--

From mrex@sap.com  Wed Sep 12 17:59:16 2012
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 5920921F8681 for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 17:59:16 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NwZ87WIy6Mqx for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 17:59:15 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9E30A21F8672 for <ietf@ietf.org>; Wed, 12 Sep 2012 17:59:15 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q8D0x66s028206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Sep 2012 02:59:11 +0200 (MEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <CAC4RtVAsUPo21t2BPj6cjbFiE6m1+eyS_AtDXBAwpyEJ1dao1g@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Date: Thu, 13 Sep 2012 02:59:05 +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: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF <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: Thu, 13 Sep 2012 00:59:16 -0000

Barry Leiba wrote:
> >> This raises the question of what "expires" means.
> >
> > At the least, if IDs are published publicly forever, then "expires" is no
> > longer meaningful and the entirety of that notion needs to be expunged
> > from the ID process.
> 
> You seem to think it means something like "expunged from the record, and no
> longer available for viewing."
> 
> I think it means "no longer current for the purposes of work and
> discussion."

I fully agree to the latter.

Expunging I-Ds that are older than 6 months looks like a silly idea
to me.  Nothing in "Note Well" indicates that an IETF contribution
that is not published as RFC or regurgitated as a successor I-D
will be automatically un-contributed from the IETF.

Actually, to me the Note Well says just the opposite.
There are numerous I-Ds that are idle for > 6 month (even WG documents)
and there are also numerous abandoned I-Ds (WG documents and individual
submissions).  I consider it perfectly reasonable to keep them as easily
accessible as IETF mailing list archives to the community so that
any existing contribution can be easily found and reused whenever
anyone feels like it.

I consider it a matter of self-evident courtesy to contact the original
author(s) before submitting a new I-D that incorporates elses I-D (or RFC),
independent of whether that document is active(I-D)/published(RFC) or
expired(I-D).

An expired or abandoned individual I-D might be an indicator that the
author(s) did not have the time/energy/endurance to carry it through
to RFC, not necessarily that the document (or technology described by it)
is not mature or does not exist.  I expect that a number of expired I-Ds
describes an installed base that is alive and kicking.


-Martin

From touch@isi.edu  Wed Sep 12 18:09:16 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB4721F8674 for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 18:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qeQBUZRGtjJQ for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 18:09:16 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0901721F8661 for <ietf@ietf.org>; Wed, 12 Sep 2012 18:09:16 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8D18J1e005288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Sep 2012 18:08:30 -0700 (PDT)
Message-ID: <50513202.7070107@isi.edu>
Date: Wed, 12 Sep 2012 18:08:18 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp>
In-Reply-To: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp>
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: Barry Leiba <barryleiba@computer.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: Thu, 13 Sep 2012 01:09:16 -0000

On 9/12/2012 5:59 PM, Martin Rex wrote:
> Barry Leiba wrote:
>>>> This raises the question of what "expires" means.
>>>
>>> At the least, if IDs are published publicly forever, then "expires" is no
>>> longer meaningful and the entirety of that notion needs to be expunged
>>> from the ID process.
>>
>> You seem to think it means something like "expunged from the record, and no
>> longer available for viewing."
>>
>> I think it means "no longer current for the purposes of work and
>> discussion."
>
> I fully agree to the latter.
>
> Expunging I-Ds that are older than 6 months looks like a silly idea
> to me.  Nothing in "Note Well" indicates that an IETF contribution
> that is not published as RFC or regurgitated as a successor I-D
> will be automatically un-contributed from the IETF.

Nothing in the Note Well, but there is specific text in the ID 
Guidelines (written by the IESG):

http://www.ietf.org/ietf-ftp/1id-guidelines.txt

8.  Expiring

    An Internet-Draft will expire exactly 185 days from the date that it
    is posted on the IETF Web site (<http://www.ietf.org/id-info/>)
    unless it is replaced by an updated version (in which case the clock
    will start all over again for the new version, and the old version
    will be removed from the I-D repository), or unless it is under
    official review by the IESG (i.e., a request to publish it as an RFC
    has been submitted)...

I.e., this is not a matter of "interpretation".

If you want to change the rules, then it cannot apply to past IDs unless 
authors give explicit permission, because the IETF would be changing the 
terms of this statement.

Joe

From barryleiba@gmail.com  Wed Sep 12 20:13:14 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7BCA21E803A for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 20:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.955
X-Spam-Level: 
X-Spam-Status: No, score=-102.955 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NipGbdiYNb7y for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 20:13:14 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 16AAF21E8034 for <ietf@ietf.org>; Wed, 12 Sep 2012 20:13:14 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so3261371vbb.31 for <ietf@ietf.org>; Wed, 12 Sep 2012 20:13:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wo4KebozoK+EUDYppnosJZ7ry5EdOQSyR/FSx5R796Q=; b=WOcx+z8xIbqSy2yQJzLvouqqse4fY9+O6Adv0zip8v1NXSiPdmT6lM5VgBOJfR+L+a LfMni8tNAkpXcxuprckwnPswT8hj6cAjOyQy4Nfq80qJ2B/LB+IWH/OhZRXA7J9ikxWk 9uHt8LZD9rJT9Gv/mfxOWC9c0Ku9ELAJ9qM4nZyZLESRYXHyY9VJ/g7mvl1d9M8XS6PQ P5v5Hp3HCpcDKBJgycFFJYaK+y5rojwi51rDzgGv9DYtJNChfi84VCDdDdVuqTcbv3rc eVGnpmdywElUoMJpInHuVJaURc6nEmcBXpYpsY8zL/mcwkf26I9n1XRxpvwEIEKSMhVx fxDw==
MIME-Version: 1.0
Received: by 10.58.58.161 with SMTP id s1mr403992veq.14.1347505989189; Wed, 12 Sep 2012 20:13:09 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.58.41 with HTTP; Wed, 12 Sep 2012 20:13:09 -0700 (PDT)
In-Reply-To: <50513202.7070107@isi.edu>
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp> <50513202.7070107@isi.edu>
Date: Wed, 12 Sep 2012 23:13:09 -0400
X-Google-Sender-Auth: J9ksvsxcu3WPwch2PYwNWbWyBJ4
Message-ID: <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Barry Leiba <barryleiba@computer.org>
To: Joe 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: Thu, 13 Sep 2012 03:13:14 -0000

>>> I think it means "no longer current for the purposes of work and
>>> discussion."
>
> Nothing in the Note Well, but there is specific text in the ID Guidelines
> (written by the IESG):
>
> http://www.ietf.org/ietf-ftp/1id-guidelines.txt
>
> 8.  Expiring
>
>    An Internet-Draft will expire exactly 185 days from the date that it
>    is posted on the IETF Web site (<http://www.ietf.org/id-info/>)
>    unless it is replaced by an updated version (in which case the clock
>    will start all over again for the new version, and the old version
>    will be removed from the I-D repository), or unless it is under
>    official review by the IESG (i.e., a request to publish it as an RFC
>    has been submitted)...
>
> I.e., this is not a matter of "interpretation".

'tis, apparently, because you are still interpreting it differently to how I am.

There's nothing in the quote above that says that the expired document
will not be available *in the archive*.  It says that it will be
removed *from the repository*, which it is... and the text you cite
later goes on to talk about the tombstone file that replaced it in the
repository, which we can easily see when we go to the datatracker
entry for an expired I-D.

And then the statement you cite further goes on to say this:

   An expired I-D may be unexpired when necessary to further the work of
   the IETF, including IETF liaison with other standards bodies.  Such
   action will be taken by request of an IESG member, a chair of the
   working group associated with the I-D, or one of the document
   authors.

That *clearly* implies that it's not *gone*, else how could it be
unexpired when necessary, by anyone's request?

I'll also note, Joe, that you are the *only* one arguing this point.
Does anyone agree with Joe?  If not, it seems fair to say that it
looks like you're well in the rough here.

Barry

From touch@isi.edu  Wed Sep 12 21:33:33 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4ECF21E8040 for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 21:33:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.556
X-Spam-Level: 
X-Spam-Status: No, score=-104.556 tagged_above=-999 required=5 tests=[AWL=2.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9CiKIkrTzP+6 for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 21:33:32 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE8921E803C for <ietf@ietf.org>; Wed, 12 Sep 2012 21:33:25 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q8D4WhvH003152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Sep 2012 21:32:54 -0700 (PDT)
Message-ID: <505161E9.5050800@isi.edu>
Date: Wed, 12 Sep 2012 21:32:41 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp> <50513202.7070107@isi.edu> <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com>
In-Reply-To: <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Sep 2012 04:33:33 -0000

Hi, Barry,

On 9/12/2012 8:13 PM, Barry Leiba wrote:
>>>> I think it means "no longer current for the purposes of work and
>>>> discussion."
>>
>> Nothing in the Note Well, but there is specific text in the ID Guidelines
>> (written by the IESG):
>>
>> http://www.ietf.org/ietf-ftp/1id-guidelines.txt
>>
>> 8.  Expiring
>>
>>     An Internet-Draft will expire exactly 185 days from the date that it
>>     is posted on the IETF Web site (<http://www.ietf.org/id-info/>)
>>     unless it is replaced by an updated version (in which case the clock
>>     will start all over again for the new version, and the old version
>>     will be removed from the I-D repository), or unless it is under
>>     official review by the IESG (i.e., a request to publish it as an RFC
>>     has been submitted)...
>>
>> I.e., this is not a matter of "interpretation".
>
> 'tis, apparently, because you are still interpreting it differently to how I am.
>
> There's nothing in the quote above that says that the expired document
> will not be available *in the archive*.

There's nothing that says it won't be available by Santa Claus delivery 
either. However, the document states how things will be made available, 
and how that will change upon expiration.

> And then the statement you cite further goes on to say this:
>
>     An expired I-D may be unexpired when necessary to further the work of
>     the IETF, including IETF liaison with other standards bodies.  Such
>     action will be taken by request of an IESG member, a chair of the
>     working group associated with the I-D, or one of the document
>     authors.
>
> That *clearly* implies that it's not *gone*, else how could it be
> unexpired when necessary, by anyone's request?

Nobody is debating whether the IETF can/should have an archive. The 
question is whether that archive should be public - which effectively 
negates the concept of taking the doc out of the I-D repository.

And I see you selectively omitted the rest of that paragraph:

    Such a request may be overridden; e.g., a chair of the
    working group associated with the I-D will be notified if an author
    requests unexpiration and may request that the action not occur.
    This request should be sent to internet-drafts@ietf.org (using the
    suggested subject line "Resurrect I-D <filename>") and should come
    from an author, a working group chair, or an IESG member.

I recognize the IETF might change this policy, but I want to be clear 
that I don't consider this is ambiguous to date.

If the IETF wants to put all old IDs on a public site, I consider that 
equivalent to unexpiration, and the authors must be given the right to 
opt-out.

Joe

From mrex@sap.com  Wed Sep 12 23:02:18 2012
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 CEC4521E803C for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 23:02:18 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lPica1c817uV for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 23:02:17 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB9721E8041 for <ietf@ietf.org>; Wed, 12 Sep 2012 23:02:16 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q8D61v64002293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Sep 2012 08:02:11 +0200 (MEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <505161E9.5050800@isi.edu>
To: Joe Touch <touch@isi.edu>
Date: Thu, 13 Sep 2012 08:01:56 +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: <20120913060156.D387D1A216@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Barry Leiba <barryleiba@computer.org>, IETF <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: Thu, 13 Sep 2012 06:02:19 -0000

Joe Touch wrote:
> >
> > There's nothing in the quote above that says that the expired document
> > will not be available *in the archive*.
> 
> There's nothing that says it won't be available by Santa Claus delivery 
> either. However, the document states how things will be made available, 
> and how that will change upon expiration.

While the 6-month timer (or any earlier I-D update!!) will, in fact,
change how the *IETF* distributes and promotes a particular I-D (version),
there is actually *NO* limitation in what folks downloading I-Ds
with the URLs from the i-d-announce  I-D Action: EMails do with
any of the I-Ds that they download.

When I startet mirroring I-Ds in 1995, I did so by processing the
I-D announce Emails, rather than mirroring the IETF ftp server,
because (a) I did want to retain old I-Ds of WG document that
I was actively participating in, and I had no desire to obtain
the tombstone files.


> 
> Nobody is debating whether the IETF can/should have an archive. The 
> question is whether that archive should be public - which effectively 
> negates the concept of taking the doc out of the I-D repository.
> 
> And I see you selectively omitted the rest of that paragraph:
> 
>     Such a request may be overridden; e.g., a chair of the
>     working group associated with the I-D will be notified if an author
>     requests unexpiration and may request that the action not occur.
>     This request should be sent to internet-drafts@ietf.org (using the
>     suggested subject line "Resurrect I-D <filename>") and should come
>     from an author, a working group chair, or an IESG member.

This describes how _one_ very specific IETF document repository
(of active I-Ds) is managed.


> 
> I recognize the IETF might change this policy, but I want to be clear 
> that I don't consider this is ambiguous to date.


I *never* understood this to be any kind of polic, but rather a
description of the current procedure, deliberatly chosen by the
secretariat and server admin how to process and make available
I-Ds for download.

Since 1995, the location&(favorite)protocol moved around a few times:

    ftp://ds.internic.net/
    ftp://ftp.ietf.org/
    http://www.ietf.org/internet-drafts/
    http://www.ietf.org/id/


I never understood the submission of a successor I-D or creation
of a tombstone I-D by the secretariat to imply un-publication or
un-contribution of an earlier or expired I-D.

Personally, I consider the possibility to diff arbitrary RFCs and I-D
version from the past through the tools.ietf.org interface extremely useful.
Similar to being able to browse IETF mailing list archives.
Not being able to browse old IETF WG mailing list archives that have been
hosted by other organizations is sometimes a problem.  (there are many
interesting discussions and information in the archives, many of
which are still quite relevant today).


> 
> If the IETF wants to put all old IDs on a public site, I consider that 
> equivalent to unexpiration, and the authors must be given the right to 
> opt-out.


You're asking for an opt-out from "Note Well" here.  I strongly object
to such a change of IETF policy.


Several I-Ds, and in particular abandoned/expired I-Ds were originally
cometing proposals, and only one or a few of them was/were selected to
become adopted/published as RFCs.  That doesn't mean that the other
proposals were useless, flawed or not being actively discussed
on IETF mailing lists.  Just the opposite.  I-Ds are often regular
parts of WG mailing list discussions, they're just managed/distributed
in a fashion that differes from Mailing list archives.


-Martin

From touch@isi.edu  Wed Sep 12 23:27:02 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC92321F8472 for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 23:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.812
X-Spam-Level: 
X-Spam-Status: No, score=-104.812 tagged_above=-999 required=5 tests=[AWL=1.788, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H+wcZSIkfy1C for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 23:27:02 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5D58021F846E for <ietf@ietf.org>; Wed, 12 Sep 2012 23:27:02 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q8D6QABK027608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Sep 2012 23:26:25 -0700 (PDT)
Message-ID: <50517C80.9040807@isi.edu>
Date: Wed, 12 Sep 2012 23:26:08 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120913060156.D387D1A216@ld9781.wdf.sap.corp>
In-Reply-To: <20120913060156.D387D1A216@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Barry Leiba <barryleiba@computer.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: Thu, 13 Sep 2012 06:27:02 -0000

On 9/12/2012 11:01 PM, Martin Rex wrote:
> While the 6-month timer (or any earlier I-D update!!) will, in fact,
> change how the*IETF*  distributes and promotes a particular I-D (version),
> there is actually*NO*  limitation in what folks downloading I-Ds
> with the URLs from the i-d-announce  I-D Action: EMails do with
> any of the I-Ds that they download.

At least one limitation is here:

             c.         Pre-5378 Material.  In some cases, IETF 
Contributions or IETF Documents may contain material from IETF 
Contributions or IETF Documents published or made publicly available 
before November 10, 2008 as to which the persons controlling the 
copyright in such material have not granted rights to the IETF Trust 
under the terms of RFC 5378 (“Pre-5378 Material”).  If a Contributor 
includes the legend contained in Section 6.c.iii of these Legal 
Provisions on such IETF Contributions or IETF Documents containing 
Pre-5378 Materials, the IETF Trust agrees that it shall not grant any 
third party the right to use such Pre-5378 Material outside the IETF 
Standards Process unless and until it has obtained sufficient rights to 
do so from the persons controlling the copyright in such Pre-5378 
Material.  Where practical, Contributors are encouraged to identify 
which portions of such IETF Contributions and IETF Documents contain 
Pre-5378 Material, including the source (by RFC number or otherwise) of 
the Pre-5378 Material.

Note that the "standards process" is defined in a way that includes 
archiving, but does not explicitly include publication:

             b.         IETF Standards Process.  The term IETF Standards 
Process has the meaning assigned to it in RFC 5378.  In addition, the 
IETF Trust interprets the IETF Standards Process to include the 
archiving of IETF Documents in perpetuity for reference in support of 
IETF activities and the implementation of IETF standards and specifications.

So it's not a slam dunk that you have the rights you think for every 
I-D; you definitely don't have those rights for IDs published before Nov 
10, 2008 since the copyright was not transferred to the ISOC/IETF or 
their Trustees.

Joe

From john-ietf@jck.com  Wed Sep 12 23:31:04 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC5D021F8491 for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 23:31:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level: 
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LnXfrh+oiyMm for <ietf@ietfa.amsl.com>; Wed, 12 Sep 2012 23:31:04 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6222D21F848B for <ietf@ietf.org>; Wed, 12 Sep 2012 23:31:04 -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 1TC2x1-000PPJ-UN; Thu, 13 Sep 2012 02:30:59 -0400
Date: Thu, 13 Sep 2012 02:30:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Joe Touch <touch@isi.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <4C1F0118D8069BF8DFDC9F9B@JcK-HP8200.jck.com>
In-Reply-To: <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com>
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp> <50513202.7070107@isi.edu> <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Sep 2012 06:31:05 -0000

--On Wednesday, September 12, 2012 23:13 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>...
> There's nothing in the quote above that says that the expired
> document will not be available *in the archive*.  It says that
> it will be removed *from the repository*, which it is... and
> the text you cite later goes on to talk about the tombstone
> file that replaced it in the repository, which we can easily
> see when we go to the datatracker entry for an expired I-D.
> 
> And then the statement you cite further goes on to say this:
> 
>    An expired I-D may be unexpired when necessary to further
> the work of    the IETF, including IETF liaison with other
> standards bodies.  Such    action will be taken by request of
> an IESG member, a chair of the    working group associated
> with the I-D, or one of the document    authors.
> 
> That *clearly* implies that it's not *gone*, else how could it
> be unexpired when necessary, by anyone's request?

Barry,

Without trying to figure out whether or not I agree with Joe,
the key question has never been, IMO, whether or not the IETF
has the right to _keep_ expired documents.  Keeping them is
clearly necessary to un-expire them, as you note, and has a
number of other significant advantages and useful properties.
As far as I know, a file of expired I-Ds have been maintained
since I-Ds were introduced as a tool.

But nothing in the above, nor in the text you cite, requires
that _keep_ imply "guarantee to have available for retrieval
over the network by any interested party, with no requirement
for a special request".  It seems to me that it is only the
latter that is of interest here and only the latter that is the
subject of the proposed policy.   "Remove from public archive"
does not imply "it is gone, forget it ever existed" either, only
making it inaccessible for retrieval except perhaps in response
to other court orders or for other good causes that might be
permitted.

I don't have an opinion or intend to make any claim as to which
this part of the discussion turned fishy, but the smell of red
herring does not help advance discussions.

   john




From dhc@dcrocker.net  Thu Sep 13 00:03:02 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1706A21E8039 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 00:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zWiw11Ub1xYu for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 00:03:01 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4A96F21E8037 for <ietf@ietf.org>; Thu, 13 Sep 2012 00:03:01 -0700 (PDT)
Received: from [192.168.1.8] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8D72v85018551 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 00:02:57 -0700
Message-ID: <5051851E.6050208@dcrocker.net>
Date: Thu, 13 Sep 2012 00:02:54 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp> <50513202.7070107@isi.edu> <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com> <4C1F0118D8069BF8DFDC9F9B@JcK-HP8200.jck.com>
In-Reply-To: <4C1F0118D8069BF8DFDC9F9B@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.17]); Thu, 13 Sep 2012 00:02:58 -0700 (PDT)
Cc: Barry Leiba <barryleiba@computer.org>, 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, 13 Sep 2012 07:03:02 -0000

On 9/12/2012 11:30 PM, John C Klensin wrote:
> But nothing in the above, nor in the text you cite, requires
> that _keep_ imply "guarantee to have available for retrieval
> over the network by any interested party, with no requirement
> for a special request".


It's interesting how this line of analysis entirely ignores pragmatics.

It has been noted by a number of folk that public access has repeatedly 
been demonstrated to be... useful.

That's why they were made accessible.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From glenzorn@gmail.com  Thu Sep 13 00:09:21 2012
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 DE7E321F846D for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 00:09:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ziOnAyXOjZNX for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 00:09:21 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6632C21F846C for <ietf@ietf.org>; Thu, 13 Sep 2012 00:09:21 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so4422821obb.31 for <ietf@ietf.org>; Thu, 13 Sep 2012 00:09:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5ijpjXrGqw78MJHXqQkF8jVkv6cUURJO37PVPrqlwNk=; b=OyiQ+6CgP26NuRN9J9VywSyQ+YtZoxN9IZqQNAIiKhr21cDsDzkZ29IWw9zBi6eox8 byTFX/K6W6etDTW5QzhLYKkOi8WfKj5g4RUA0gHnYaKHlp4Oic1zvCFZXhUsCeskVqew UliImQTdTH2ee/ICvvULATsgb7VQr17p7o7G+GXdqQNenZdnX47zydvEQK1xC/v0OnYS ikzZhiG7L4X2mMT7oPkvmSOZsLYSmtuwGabbm9hxIpbTg0fH2qXHk/1gtjXrsye/8XQq gDCCOd12doXWLLNHBqJCklTcDPCprWyfb91dPQXkEOcGACzkY3xgJR8Iy5Fd5XZHqhNT eEgw==
Received: by 10.182.164.103 with SMTP id yp7mr857397obb.26.1347520160987; Thu, 13 Sep 2012 00:09:20 -0700 (PDT)
Received: from [192.168.0.102] (ppp-58-11-152-121.revip2.asianet.co.th. [58.11.152.121]) by mx.google.com with ESMTPS id hz6sm23073253obb.1.2012.09.13.00.09.18 (version=SSLv3 cipher=OTHER); Thu, 13 Sep 2012 00:09:20 -0700 (PDT)
Message-ID: <5051869C.3050407@gmail.com>
Date: Thu, 13 Sep 2012 14:09:16 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120721 Thunderbird/14.0
MIME-Version: 1.0
To: Kuor-Hsin.Chang@us.elster.com
Subject: Re: Fw: IETF 95 Date Change Proposal - Round 2
References: <OF38B61C7B.9177207F-ON88257A77.0005998C-88257A77.0005AFA9@gb.elster.com>
In-Reply-To: <OF38B61C7B.9177207F-ON88257A77.0005998C-88257A77.0005AFA9@gb.elster.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
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Sep 2012 07:09:22 -0000

By my count that would put about 5 months between IETF 94 and 95, and 
just a bit more than 3 months separating 95 from 96.  Leave it the way 
it was.

On 09/12/2012 08:02 AM, Kuor-Hsin.Chang@us.elster.com wrote:
> 3 - 8 April 2016is good.
>
> ----- Forwarded by Kuor-Hsin Chang/USE/Elster on 09/11/2012 06:01 PM 
> -----
> From: 	IETF Administrative Director <iad@ietf.org>
> To: 	IETF Announcement List <ietf-announce@ietf.org>,
> Cc: 	iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, 
> iesg@ietf.org
> Date: 	09/06/2012 12:13 PM
> Subject: 	IETF 95 Date Change Proposal - Round 2
> Sent by: 	ietf-announce-bounces@ietf.org
>
>
> ------------------------------------------------------------------------
>
>
>
> All
>
>
> The IAOC is seeking community feedback on a proposed date change for 
> IETF 95
> originally scheduled for 27 March to 1 April 2016.
>
> After considering community feedback on a proposed change to 20 - 25 March
> 2016, the IAOC is proposing 3 - 8 April 2016 to avoid the impact on 
> travel and
> attendance during the 20 - 25 March period.
>
> Comments appreciated to ietf@ietf.org by 20 September 2012.
>
> Ray Pelletier
> IETF Administrative Director
>
> ______________________________________________________________________
> This email has been spam and virus checked by Elster IT Services.


From touch@isi.edu  Thu Sep 13 00:20:42 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B970F21E8047 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 00:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.01
X-Spam-Level: 
X-Spam-Status: No, score=-103.01 tagged_above=-999 required=5 tests=[AWL=-0.411, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6faimwzjjtkD for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 00:20:41 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 5118E21E8043 for <ietf@ietf.org>; Thu, 13 Sep 2012 00:20:41 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q8D7Jtlx012307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 00:19:59 -0700 (PDT)
Message-ID: <50518919.6070403@isi.edu>
Date: Thu, 13 Sep 2012 00:19:53 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp> <50513202.7070107@isi.edu> <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com> <4C1F0118D8069BF8DFDC9F9B@JcK-HP8200.jck.com> <5051851E.6050208@dcrocker.net>
In-Reply-To: <5051851E.6050208@dcrocker.net>
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: John C Klensin <john-ietf@jck.com>, IETF <ietf@ietf.org>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 07:20:42 -0000

On 9/13/2012 12:02 AM, Dave Crocker wrote:
>
> On 9/12/2012 11:30 PM, John C Klensin wrote:
>> But nothing in the above, nor in the text you cite, requires
>> that _keep_ imply "guarantee to have available for retrieval
>> over the network by any interested party, with no requirement
>> for a special request".
>
>
> It's interesting how this line of analysis entirely ignores pragmatics.
>
> It has been noted by a number of folk that public access has repeatedly
> been demonstrated to be... useful.
>
> That's why they were made accessible.
>
> d/

PirateBay believes this too, and helps make movies available for public 
access, honoring pragmatics.

Good luck with that line of reasoning.

Joe

From daedulus@btconnect.com  Thu Sep 13 01:17:53 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5299C21F8534 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 01:17:53 -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_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V0WPfUug5Rz4 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 01:17:52 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe005.messaging.microsoft.com [213.199.154.143]) by ietfa.amsl.com (Postfix) with ESMTP id 76A3A21F8467 for <ietf@ietf.org>; Thu, 13 Sep 2012 01:17:48 -0700 (PDT)
Received: from mail67-db3-R.bigfish.com (10.3.81.241) by DB3EHSOBE002.bigfish.com (10.3.84.22) with Microsoft SMTP Server id 14.1.225.23; Thu, 13 Sep 2012 08:17:47 +0000
Received: from mail67-db3 (localhost [127.0.0.1])	by mail67-db3-R.bigfish.com (Postfix) with ESMTP id EA0F41200FD; Thu, 13 Sep 2012 08:17:46 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: PS-23(zz9371I542M1432I1418Id6f1izz1202h1d1ah1d2ahzz1033IL17326ah8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah1177h1179h1288h12a5h12a9h12bdh304l1155h)
Received: from mail67-db3 (localhost.localdomain [127.0.0.1]) by mail67-db3 (MessageSwitch) id 1347524265418399_2907; Thu, 13 Sep 2012 08:17:45 +0000 (UTC)
Received: from DB3EHSMHS014.bigfish.com (unknown [10.3.81.248])	by mail67-db3.bigfish.com (Postfix) with ESMTP id 5A3803C0057; Thu, 13 Sep 2012 08:17:45 +0000 (UTC)
Received: from AMSPRD0710HT001.eurprd07.prod.outlook.com (157.56.249.85) by DB3EHSMHS014.bigfish.com (10.3.87.114) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 13 Sep 2012 08:17:40 +0000
Received: from CH1PRD0710HT002.namprd07.prod.outlook.com (157.56.245.5) by pod51017.outlook.com (10.255.160.164) with Microsoft SMTP Server (TLS) id 14.16.190.9; Thu, 13 Sep 2012 08:17:36 +0000
Message-ID: <00da01cd9188$51d05540$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Barry Leiba <barryleiba@computer.org>
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp><50513202.7070107@isi.edu> <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from theIETF Web Site
Date: Thu, 13 Sep 2012 09:18:05 +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.245.5]
X-OriginatorOrg: btconnect.com
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 08:17:53 -0000

When I read the original IESG statement, I thought it sloppily worded,
since it did not use the same terminology as in
 http://www.ietf.org/ietf-ftp/1id-guidelines.txt
which has been cited below.

I then wondered if the sloppy, as I saw it, wording might reflect less
than precise thinking in the semantics, and I think that the subsequent
posts have born that out.  There are a lot of not-so-corner cases that
need considering.  For me, the 'public I-D archive', as the statement
calls it, is of great value; some I-Ds keep doing U-turns and I need to
go back and see what has been there before.  Also, I may want to
incorporate some material from a years old I-D that never got adopted.
And so on.

So I believe that everything should stay in that archive unless there is
a very good reason for it not to; court order but not that alone  I
would add either or both of IESG vote (as for the approval of an I-D,
DISCUSS, ABSTAIN etc) and IETF Consensus.

Tom Petch

----- Original Message -----
From: "Barry Leiba" <barryleiba@computer.org>
To: "Joe Touch" <touch@isi.edu>
Cc: "IETF" <ietf@ietf.org>
Sent: Thursday, September 13, 2012 4:13 AM
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from
theIETF Web Site


> >>> I think it means "no longer current for the purposes of work and
> >>> discussion."
> >
> > Nothing in the Note Well, but there is specific text in the ID
Guidelines
> > (written by the IESG):
> >
> > http://www.ietf.org/ietf-ftp/1id-guidelines.txt
> >
> > 8.  Expiring
> >
> >    An Internet-Draft will expire exactly 185 days from the date that
it
> >    is posted on the IETF Web site (<http://www.ietf.org/id-info/>)
> >    unless it is replaced by an updated version (in which case the
clock
> >    will start all over again for the new version, and the old
version
> >    will be removed from the I-D repository), or unless it is under
> >    official review by the IESG (i.e., a request to publish it as an
RFC
> >    has been submitted)...
> >
> > I.e., this is not a matter of "interpretation".
>
> 'tis, apparently, because you are still interpreting it differently to
how I am.
>
> There's nothing in the quote above that says that the expired document
> will not be available *in the archive*.  It says that it will be
> removed *from the repository*, which it is... and the text you cite
> later goes on to talk about the tombstone file that replaced it in the
> repository, which we can easily see when we go to the datatracker
> entry for an expired I-D.
>
> And then the statement you cite further goes on to say this:
>
>    An expired I-D may be unexpired when necessary to further the work
of
>    the IETF, including IETF liaison with other standards bodies.  Such
>    action will be taken by request of an IESG member, a chair of the
>    working group associated with the I-D, or one of the document
>    authors.
>
> That *clearly* implies that it's not *gone*, else how could it be
> unexpired when necessary, by anyone's request?
>
> I'll also note, Joe, that you are the *only* one arguing this point.
> Does anyone agree with Joe?  If not, it seems fair to say that it
> looks like you're well in the rough here.
>
> Barry
>



From john-ietf@jck.com  Thu Sep 13 05:17:12 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0467421F8570 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 05:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qMj7edXYuoP for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 05:17:11 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD0F21F8568 for <ietf@ietf.org>; Thu, 13 Sep 2012 05:17:11 -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 1TC8Lq-0000ni-A9; Thu, 13 Sep 2012 08:16:58 -0400
Date: Thu, 13 Sep 2012 08:16:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joe Touch <touch@isi.edu>, dcrocker@bbiw.net
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Message-ID: <1702A63A6B85C232A1C13C1C@JcK-HP8200.jck.com>
In-Reply-To: <50518919.6070403@isi.edu>
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp> <50513202.7070107@isi.edu> <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com> <4C1F0118D8069BF8DFDC9F9B@JcK-HP8200.jck.com> <5051851E.6050208@dcrocker.net> <50518919.6070403@isi.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF <ietf@ietf.org>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 12:17:12 -0000

--On Thursday, September 13, 2012 00:19 -0700 Joe Touch
<touch@isi.edu> wrote:
 
> On 9/13/2012 12:02 AM, Dave Crocker wrote:
>> 
>> On 9/12/2012 11:30 PM, John C Klensin wrote:
>>> But nothing in the above, nor in the text you cite, requires
>>> that _keep_ imply "guarantee to have available for retrieval
>>> over the network by any interested party, with no requirement
>>> for a special request".
>> 
>> 
>> It's interesting how this line of analysis entirely ignores
>> pragmatics.
>> 
>> It has been noted by a number of folk that public access has
>> repeatedly been demonstrated to be... useful.
>> 
>> That's why they were made accessible.
>> 
>> d/
> 
> PirateBay believes this too, and helps make movies available
> for public access, honoring pragmatics.
> 
> Good luck with that line of reasoning.

Let me try that a different way.  Suppose someone were to
propose that ISOC increase the subsidy to IETF sufficiently to
drop all registration fees.  That would certainly be "useful".
It would be useful to those who have to pay those fees out of
their own pockets, increasing the costs of attendance and making
it harder to attend.  It would be useful to those who have to
justify travel budgets and expenses.   One might even suggest
that it would be useful to everyone who wasn't interested in
using the rising costs of IETF meetings to keep people out.

It would perhaps be even more useful to offer a distance-based
cash subsidy to anyone who has to travel more than, say, 3000
miles to an IETF meeting.  That would not only be useful to
individuals, but would be useful in balancing out the
differential cost effects of meeting location choices and hence
in improving geographical balance in meetings.

Are there pragmatic reasons to not do either of these useful
things?  Sure there are.  But they would definitely be
pragmatically useful.

The questions about the public archive aren't "do people find
this useful?" but "does the utility of having the archive public
outweigh the costs and risks?"   And, if the answer to the
second question is even only "maybe", "can we analyze the real
needs and determine other ways to meet them, such as by keeping
expired drafts available for a relatively short time after
expiration rather than forever, with authors having an opt-out
option?".

best,
    john




From simon@josefsson.org  Thu Sep 13 07:18:25 2012
Return-Path: <simon@josefsson.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 8DBFD21F85AA for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 07:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.609
X-Spam-Level: 
X-Spam-Status: No, score=-98.609 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M9Y31ODCJbTn for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 07:18:21 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3C921F85A8 for <ietf@ietf.org>; Thu, 13 Sep 2012 07:18:20 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q8DEI9VZ003080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 13 Sep 2012 16:18:10 +0200
X-Hashcash: 1:22:120913:ietf@ietf.org::3pUpMv91THGg0iwS:0Jri
From: Simon Josefsson <simon@josefsson.org>
To: ietf@ietf.org
Subject: copyright notices in RFC 6716
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
Date: Thu, 13 Sep 2012 16:18:09 +0200
Message-ID: <87a9wuropq.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Sep 2012 14:18:25 -0000

All,

I noticed that the recent RFC 6716 contains some reference code that
contain the copyright and licenses notice reproduced below.  The IETF
TLP [1] mandates a certain form of copyright notices and the TLP does
not, as far as I can see, permit varying the boiler plate in any way.
Note that both companies and organisations are mentioned in the
copyright notice in RFC 6716, besides individuals.

Does this indicate a policy change, a mistake with that document, or
something else?

Btw, kudos to the RFC 6716 authors for shipping reference code!  I hope
this will establish a best practice for standards in the future.

/Simon

[1] http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-20091228.htm

Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
                    Jean-Marc Valin, Timothy B. Terriberry,
                    CSIRO, Gregory Maxwell, Mark Borgerding,
                    Erik de Castro Lopo. All rights reserved.

This file is extracted from RFC6716. Please see that RFC for additional
information.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

- Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.

- Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

- Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

From hartmans@mit.edu  Thu Sep 13 10:32:11 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF3821F85AE for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 10:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.657
X-Spam-Level: 
X-Spam-Status: No, score=-97.657 tagged_above=-999 required=5 tests=[AWL=-1.945, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CkEdlomMa7dw for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 10:32:11 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id E7FEC21F8592 for <ietf@ietf.org>; Thu, 13 Sep 2012 10:32:10 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 973C72010F; Thu, 13 Sep 2012 13:32:01 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id F19C34149; Thu, 13 Sep 2012 13:31:52 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Joe Touch <touch@isi.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <6.2.5.6.2.20120905005713.08dde888@resistor.net> <CAKe6YvOxcuHh7R3MfmYnCRWymAqW-Tum6H9Hc_aAhERohevyEA@mail.gmail.com> <6.2.5.6.2.20120905063923.0b328fe0@resistor.net> <504A0928.2020200@isi.edu>
Date: Thu, 13 Sep 2012 13:31:52 -0400
In-Reply-To: <504A0928.2020200@isi.edu> (Joe Touch's message of "Fri, 07 Sep 2012 07:48:08 -0700")
Message-ID: <tsly5kd7rsn.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 17:32:11 -0000

>>>>> "Joe" == Joe Touch <touch@isi.edu> writes:

    Joe> On 9/5/2012 7:51 AM, SM wrote:
    Joe> ...
    >> Creating a perpetual I-D archive for the sake of rfcdiff is not a
    >> good idea as it goes against the notion of letting an I-D expire
    >> gracefully.

    Joe> +1

    Joe> Let's not forget there was a reason for expiration.

    Joe> I'm OK with the archive being public so long as at least the
    Joe> authors can remove an ID *without needing to provide a reason*.

    Joe> Yes, removal from the IETF site will not expunge copies from
    Joe> the entire Internet, but the IETF site should set the example
    Joe> here, and respect the original intent of allowing an ID to
    Joe> expire.

I find myself in agreement with Joe here.
I'm kind of horrified that this discussion is still going on.

If I write that super-offensive porn in the form of an i-d that Scott
warned about can we all find something else to mail about?:-)

From hsantos@isdg.net  Thu Sep 13 10:47:59 2012
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 868B621F8607 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 10:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.139
X-Spam-Level: 
X-Spam-Status: No, score=-102.139 tagged_above=-999 required=5 tests=[AWL=0.460, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zUT-I0z3svHT for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 10:47:58 -0700 (PDT)
Received: from mail.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7564321F8602 for <ietf@ietf.org>; Thu, 13 Sep 2012 10:47:58 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3777; t=1347558469; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=sMXE+6hvPnTQAAAEi+yT8oSBYP4=; b=UW+qhyXQlGNyWrzf9g5B LRc66CJGqBdNBWKGy6S2ZJTaI72c9eUzGipu5Z4kVGRJ/JZe++izEOU+1od9XWs6 Bq5CBi8XcdOywGW5sKlhzL+p2eqV9bw0kUsqpvYd+AiTy3XHJdKD/BTQFgKnImVV Tid5v2ohxCfRuqBkBkR6wR4=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 13 Sep 2012 13:47:49 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3580245653.7193.2804; Thu, 13 Sep 2012 13:47:49 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3777; t=1347558242; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=B2ZGiW+ SXq5f77TWCZpBosvTRQIqNoNGBbVMag/oxck=; b=yharZRKIQenc2Ct1khGD50a ridyWq5XQLvYNEb1B/sN0+S61ypmYjYJ1c+wnD+XY36fuxfUJu2zYiCfhGuadEty XbIWFH/Ubeps0oh9QIQ6A9JNlzl2XlVWoq9enGXtO3fSrCUUC8OXehJwdwexHu6x Ba6rs+yTukekrTwyO788=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 13 Sep 2012 13:44:02 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4179040083.9.432; Thu, 13 Sep 2012 13:44:01 -0400
Message-ID: <50521C67.2020009@isdg.net>
Date: Thu, 13 Sep 2012 13:48:23 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft	from the IETF Web Site
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp>	<50513202.7070107@isi.edu>	<CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com>	<4C1F0118D8069BF8DFDC9F9B@JcK-HP8200.jck.com>	<5051851E.6050208@dcrocker.net> <50518919.6070403@isi.edu> <1702A63A6B85C232A1C13C1C@JcK-HP8200.jck.com>
In-Reply-To: <1702A63A6B85C232A1C13C1C@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.org>, IETF <ietf@ietf.org>, 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: Thu, 13 Sep 2012 17:47:59 -0000

I find the archives very useful, especially when you have your own I-D 
history and contribution to WG works perhaps.  It helps to show 
different views, the synergism, the competitive engineering views, the 
history, etc behind the final development of WG work.

Whenever I do find a need to reference them in the eDiscussion, I will 
make sure I parenthetically note  they are expired information.

My input is limited due to legal reasons and try to keep with public 
domain technology exchanges and communications.

I can understand if an expired I-D touches base with some level of IP 
that may be conflictive in the future, i.e. someone does a patent 
search/research and finds prior art in an expired I-D and it may be 
advantageous to them to have it removed from the archives.  However, 
this is what the lawyers and courts are for.  I'm sure the IETF/IESG 
archive keepers can also make judgment calls but I don't think it will 
be harmful to keep them around until it became a legal issue and like 
everything else, dealt on a case by case basis.

I will say that I like to believe (maybe I am naive) the IETF/IESG 
does represents the community at large and I like to believe it 
represent even the "Small Guys" that really is not interested in the 
politics and battles.


John C Klensin wrote:
> 
> --On Thursday, September 13, 2012 00:19 -0700 Joe Touch
> <touch@isi.edu> wrote:
>  
>> On 9/13/2012 12:02 AM, Dave Crocker wrote:
>>> On 9/12/2012 11:30 PM, John C Klensin wrote:
>>>> But nothing in the above, nor in the text you cite, requires
>>>> that _keep_ imply "guarantee to have available for retrieval
>>>> over the network by any interested party, with no requirement
>>>> for a special request".
>>>
>>> It's interesting how this line of analysis entirely ignores
>>> pragmatics.
>>>
>>> It has been noted by a number of folk that public access has
>>> repeatedly been demonstrated to be... useful.
>>>
>>> That's why they were made accessible.
>>>
>>> d/
>> PirateBay believes this too, and helps make movies available
>> for public access, honoring pragmatics.
>>
>> Good luck with that line of reasoning.
> 
> Let me try that a different way.  Suppose someone were to
> propose that ISOC increase the subsidy to IETF sufficiently to
> drop all registration fees.  That would certainly be "useful".
> It would be useful to those who have to pay those fees out of
> their own pockets, increasing the costs of attendance and making
> it harder to attend.  It would be useful to those who have to
> justify travel budgets and expenses.   One might even suggest
> that it would be useful to everyone who wasn't interested in
> using the rising costs of IETF meetings to keep people out.
> 
> It would perhaps be even more useful to offer a distance-based
> cash subsidy to anyone who has to travel more than, say, 3000
> miles to an IETF meeting.  That would not only be useful to
> individuals, but would be useful in balancing out the
> differential cost effects of meeting location choices and hence
> in improving geographical balance in meetings.
> 
> Are there pragmatic reasons to not do either of these useful
> things?  Sure there are.  But they would definitely be
> pragmatically useful.
> 
> The questions about the public archive aren't "do people find
> this useful?" but "does the utility of having the archive public
> outweigh the costs and risks?"   And, if the answer to the
> second question is even only "maybe", "can we analyze the real
> needs and determine other ways to meet them, such as by keeping
> expired drafts available for a relatively short time after
> expiration rather than forever, with authors having an opt-out
> option?".
> 
> best,
>     john
> 
> 
> 
> 
> 

-- 
HLS



From melinda.shore@gmail.com  Thu Sep 13 11:04:34 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A125D21F8504 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 11:04:34 -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=0.130,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H2GfStj6S5pT for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 11:04:33 -0700 (PDT)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4417E21F84F6 for <ietf@ietf.org>; Thu, 13 Sep 2012 11:04:33 -0700 (PDT)
Received: by oagk14 with SMTP id k14so2362774oag.31 for <ietf@ietf.org>; Thu, 13 Sep 2012 11:04:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ZJCbSDeXyyG8EWxQ/C81peIpSqKdFWNio25QTAZ3nZg=; b=E9F/1plBp5qBrOg1sSabFN+Ps1ApQ+4yRE8D/8Gxfjiib7pA/Snd74MiMa3wHcObuz rV1WMPaMXGy7QAJTlFAtScjJmtUThV1oeV7WD7dIz60O/Me2HZVOAxSz9WT4bxmHpS+8 13EoKlmoVv1Jt1exDv0rLmk8hfzJBElq+EGhl5432iN9rm6oH4PdHeokheRJgPaWB8uw boS/l0KYdAsCl4Spst84m4342VynChIHveWmCc0Zq2km4E9sF3Msop7jZIvGzWWme5QO /iES0Swm+KFMDm+S0Ix8KyffoU4hpP2OfUGAucgtdFVcCYNoQ3iF4ARZ16prIv06vvMx DM8g==
Received: by 10.182.179.100 with SMTP id df4mr54805obc.59.1347559472945; Thu, 13 Sep 2012 11:04:32 -0700 (PDT)
Received: from spandex.local (66-230-80-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.245]) by mx.google.com with ESMTPS id j10sm20033900oej.10.2012.09.13.11.04.31 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Sep 2012 11:04:32 -0700 (PDT)
Message-ID: <5052202D.1010509@gmail.com>
Date: Thu, 13 Sep 2012 10:04:29 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp> <50513202.7070107@isi.edu> <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com> <4C1F0118D8069BF8DFDC9F9B@JcK-HP8200.jck.com> <5051851E.6050208@dcrocker.net> <50518919.6070403@isi.edu>
In-Reply-To: <50518919.6070403@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: Thu, 13 Sep 2012 18:04:34 -0000

On 9/12/12 11:19 PM, Joe Touch wrote:
> PirateBay believes this too, and helps make movies available for public
> access, honoring pragmatics.

I'm not sure I understand this analogy.  Are you saying that there are
IPR issues related to making expired drafts available?

Melinda


From dhc@dcrocker.net  Thu Sep 13 11:27:27 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EBBF21F843C for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 11:27:27 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y6pf5b2jjU1B for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 11:27:26 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9722221F8444 for <ietf@ietf.org>; Thu, 13 Sep 2012 11:27:26 -0700 (PDT)
Received: from [192.168.1.8] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8DIRP32032145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 13 Sep 2012 11:27:26 -0700
Message-ID: <5052258A.6040001@dcrocker.net>
Date: Thu, 13 Sep 2012 11:27:22 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp> <50513202.7070107@isi.edu> <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com> <4C1F0118D8069BF8DFDC9F9B@JcK-HP8200.jck.com> <5051851E.6050208@dcrocker.net> <50518919.6070403@isi.edu> <5052202D.1010509@gmail.com>
In-Reply-To: <5052202D.1010509@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 13 Sep 2012 11:27:26 -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: Thu, 13 Sep 2012 18:27:27 -0000

>> PirateBay believes this too, and helps make movies available for public
>> access, honoring pragmatics.
>
> I'm not sure I understand this analogy.  Are you saying that there are
> IPR issues related to making expired drafts available?


And since we've had a public archive of expired drafts for quite awhile, 
where have the purported problems been, that would justify this lengthy 
thread?

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From mrex@sap.com  Thu Sep 13 12:28:29 2012
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 1B19221F84F3 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 12:28:29 -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_47=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E+qSXZ98Oji0 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 12:28:28 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 647DA21F84F1 for <ietf@ietf.org>; Thu, 13 Sep 2012 12:28:28 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q8DJSJfV021512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Sep 2012 21:28:24 +0200 (MEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <50517C80.9040807@isi.edu>
To: Joe Touch <touch@isi.edu>
Date: Thu, 13 Sep 2012 21:28: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: <20120913192819.3EC361A223@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: IETF <ietf@ietf.org>, Barry Leiba <barryleiba@computer.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, 13 Sep 2012 19:28:29 -0000

Joe,

> 
> So it's not a slam dunk that you have the rights you think for every
> I-D; you definitely don't have those rights for IDs

We're NOT talking about rights that were transfered from the document
author to arbitrary third parties here, but about rights that were
given to the IETF ("IETF contribution"), and which have never been
time-limited.

So archival and making accessible I-D contributions past the "expiration"
of an I-D is perfectly legal for the IETF, unless the I-D contains an
explicit copyright notice to the contrary (most I-Ds from 199x do not
seem to carry any copyright notice at all).


Where you are _correct_ is, copy&pasting parts of such an old I-D
or the whole document into new documents will in fact require contacting
the original author(s)/copyright holder(s) and obtain permission,
the Note Well provisions likely will not be sufficient, at least for those
old I-Ds. (it is not just a matter of courtesy, but a requirement).

I assume the latter is what rfc5378 is supposed to fix.

-Martin

From fluffy@cisco.com  Thu Sep 13 12:42:50 2012
Return-Path: <fluffy@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 9508221F84F1 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 12:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iO9MAOrLTjUa for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 12:42:46 -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 B69AB21F8503 for <ietf@ietf.org>; Thu, 13 Sep 2012 12:42:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4158; q=dns/txt; s=iport; t=1347565366; x=1348774966; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=CJMJkJTKYgjfGLsN0EDE6oarhQk95nD58FV7A/HOQHo=; b=O5aIObB1dBQ7ywODh5nMoHHDAW2P+Kv+vNe6ih+PKQsVn7irD5PLdzAx Vk4oTCmNf3PcdjEO3kQBJVzuRuUgc/t++uq4m5fstCLRh2Z+n+kvJEYEP fUnVhDGPg3sdtT057N2rPs4Oq22jeKpnIJyJ5hlTYnRTTh8fle60gVD0N 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAMI1UlCtJV2a/2dsb2JhbABFu3iBB4IgAQEBAwESASc/BQsCAQg2EDIlAgQOBSKHZQYLmz6gLYsQFIVDYAOVYIEUjSSBaYJmgVo9
X-IronPort-AV: E=Sophos;i="4.80,418,1344211200"; d="scan'208";a="121409178"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP; 13 Sep 2012 19:42:46 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q8DJgkPU001969 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 13 Sep 2012 19:42:46 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.26]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.02.0318.001; Thu, 13 Sep 2012 14:42:46 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Simon Josefsson <simon@josefsson.org>
Subject: Re: copyright notices in RFC 6716
Thread-Topic: copyright notices in RFC 6716
Thread-Index: AQHNkefyvKaHV2QDxUmsIxn7BWKakw==
Date: Thu, 13 Sep 2012 19:42:45 +0000
Message-ID: <AEDE2561-B533-418E-8141-0DFB59F578F8@cisco.com>
References: <87a9wuropq.fsf@latte.josefsson.org>
In-Reply-To: <87a9wuropq.fsf@latte.josefsson.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.167]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19182.001
x-tm-as-result: No--44.551500-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <92AEC63C55B7F949A075D4D8DFAA4966@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 19:42:50 -0000

I was only peripherally involved in this and don't know all the in's and ou=
ts of this but let me try and provide a bit of information and hopefully so=
meone from the IETF Trust or RFC Editor can correct me where I am wrong.=20

The internet draft was done with the normal boiler plate that granted a bun=
ch of rights to the IETF Trust. There was also text in the draft where the =
authors granted additional rights.  The trust normally publishes the RFC wi=
th about the same license that is used in the draft however the Trust retai=
ns the rights to do whatever they want within the range of the license gran=
ted to them in the draft. In this case, the RFC was published with slightly=
 different boiler plate than what was in draft.=20

So no, I don't think the policy has changed, and no I don't think this was =
a mistake. I think the RFC Editor working with the IETF Trust and IETF lega=
l advice made this change. My understanding of the reasons for the change w=
as something like this makes it easier for some linux distribution to inclu=
de the RFC with their distribution or something. Keep in mind this is a wei=
rd RFC in that it includes a huge amount of normative code in the RFC.=20

Hope this helps - and amazed anyone noticed.=20

Cullen

PS - I may have this all wrong - I'm not the person that knows but I hope t=
hat provides some help.=20
On Sep 13, 2012, at 8:18 AM, Simon Josefsson <simon@josefsson.org> wrote:

> All,
>=20
> I noticed that the recent RFC 6716 contains some reference code that
> contain the copyright and licenses notice reproduced below.  The IETF
> TLP [1] mandates a certain form of copyright notices and the TLP does
> not, as far as I can see, permit varying the boiler plate in any way.
> Note that both companies and organisations are mentioned in the
> copyright notice in RFC 6716, besides individuals.
>=20
> Does this indicate a policy change, a mistake with that document, or
> something else?
>=20
> Btw, kudos to the RFC 6716 authors for shipping reference code!  I hope
> this will establish a best practice for standards in the future.
>=20
> /Simon
>=20
> [1] http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-200912=
28.htm
>=20
> Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
>                    Jean-Marc Valin, Timothy B. Terriberry,
>                    CSIRO, Gregory Maxwell, Mark Borgerding,
>                    Erik de Castro Lopo. All rights reserved.
>=20
> This file is extracted from RFC6716. Please see that RFC for additional
> information.
>=20
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions
> are met:
>=20
> - Redistributions of source code must retain the above copyright
> notice, this list of conditions and the following disclaimer.
>=20
> - Redistributions in binary form must reproduce the above copyright
> notice, this list of conditions and the following disclaimer in the
> documentation and/or other materials provided with the distribution.
>=20
> - Neither the name of Internet Society, IETF or IETF Trust, nor the
> names of specific contributors, may be used to endorse or promote
> products derived from this software without specific prior written
> permission.
>=20
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNE=
R
> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


From simon@josefsson.org  Thu Sep 13 13:01:15 2012
Return-Path: <simon@josefsson.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 91A4A21F85C3 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 13:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.723
X-Spam-Level: 
X-Spam-Status: No, score=-99.723 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aXppg7JELhfe for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 13:01:11 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id 5812921F85B1 for <ietf@ietf.org>; Thu, 13 Sep 2012 13:01:11 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q8DK0q0J021725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 13 Sep 2012 22:00:53 +0200
From: Simon Josefsson <simon@josefsson.org>
To: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>
Subject: Re: copyright notices in RFC 6716
References: <87a9wuropq.fsf@latte.josefsson.org> <AEDE2561-B533-418E-8141-0DFB59F578F8@cisco.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120913:fluffy@cisco.com::bYr+CeaR9qagam6y:3zyv
X-Hashcash: 1:22:120913:ietf@ietf.org::61d3xMJ3R2q3Hw86:6pb1
Date: Thu, 13 Sep 2012 22:00:52 +0200
In-Reply-To: <AEDE2561-B533-418E-8141-0DFB59F578F8@cisco.com> (Cullen Jennings's message of "Thu, 13 Sep 2012 19:42:45 +0000")
Message-ID: <874nn1r8uj.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
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, 13 Sep 2012 20:01:15 -0000

"Cullen Jennings (fluffy)" <fluffy@cisco.com> writes:

> I was only peripherally involved in this and don't know all the in's
> and outs of this but let me try and provide a bit of information and
> hopefully someone from the IETF Trust or RFC Editor can correct me
> where I am wrong.

Thanks.  Input from members of the Trust, if they were involved, would
be appreciated.

> The internet draft was done with the normal boiler plate that granted
> a bunch of rights to the IETF Trust. There was also text in the draft
> where the authors granted additional rights.  The trust normally
> publishes the RFC with about the same license that is used in the
> draft however the Trust retains the rights to do whatever they want
> within the range of the license granted to them in the draft. In this
> case, the RFC was published with slightly different boiler plate than
> what was in draft.

That is not the case, draft -16 had the same license.

> So no, I don't think the policy has changed, and no I don't think this
> was a mistake. I think the RFC Editor working with the IETF Trust and
> IETF legal advice made this change. My understanding of the reasons
> for the change was something like this makes it easier for some linux
> distribution to include the RFC with their distribution or
> something.

I don't believe that is the case here.  The license used is the same as
normal license, only the copyright header is different.  Distributions
rarely cares who the copyright holder is.  IETF rules says additional
copyright notices aren't permitted.

/Simon

> Keep in mind this is a weird RFC in that it includes a huge amount of
> normative code in the RFC.
>
> Hope this helps - and amazed anyone noticed. 
>
> Cullen
>
> PS - I may have this all wrong - I'm not the person that knows but I
> hope that provides some help.
> On Sep 13, 2012, at 8:18 AM, Simon Josefsson <simon@josefsson.org> wrote:
>
>> All,
>> 
>> I noticed that the recent RFC 6716 contains some reference code that
>> contain the copyright and licenses notice reproduced below.  The IETF
>> TLP [1] mandates a certain form of copyright notices and the TLP does
>> not, as far as I can see, permit varying the boiler plate in any way.
>> Note that both companies and organisations are mentioned in the
>> copyright notice in RFC 6716, besides individuals.
>> 
>> Does this indicate a policy change, a mistake with that document, or
>> something else?
>> 
>> Btw, kudos to the RFC 6716 authors for shipping reference code!  I hope
>> this will establish a best practice for standards in the future.
>> 
>> /Simon
>> 
>> [1]
>> http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-20091228.htm
>> 
>> Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
>>                    Jean-Marc Valin, Timothy B. Terriberry,
>>                    CSIRO, Gregory Maxwell, Mark Borgerding,
>>                    Erik de Castro Lopo. All rights reserved.
>> 
>> This file is extracted from RFC6716. Please see that RFC for additional
>> information.
>> 
>> Redistribution and use in source and binary forms, with or without
>> modification, are permitted provided that the following conditions
>> are met:
>> 
>> - Redistributions of source code must retain the above copyright
>> notice, this list of conditions and the following disclaimer.
>> 
>> - Redistributions in binary form must reproduce the above copyright
>> notice, this list of conditions and the following disclaimer in the
>> documentation and/or other materials provided with the distribution.
>> 
>> - Neither the name of Internet Society, IETF or IETF Trust, nor the
>> names of specific contributors, may be used to endorse or promote
>> products derived from this software without specific prior written
>> permission.
>> 
>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
>> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
>> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
>> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
>> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
>> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
>> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

From fluffy@cisco.com  Thu Sep 13 14:35:49 2012
Return-Path: <fluffy@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 07C7021F8619; Thu, 13 Sep 2012 14:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVq9QV7B3CVR; Thu, 13 Sep 2012 14:35:48 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 3651621F8606; Thu, 13 Sep 2012 14:35:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2485; q=dns/txt; s=iport; t=1347572148; x=1348781748; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ccrpwIM+ScBNiaVkOu4NCobv7cAQxAysVRTXP4TWM6E=; b=mb/Ui+X5xmsrtOOa+8pkv6GDT85CAb3b/JV4XkuG9LFNKmLsTz5wpu0m ETQNKG6ERJ98IxBIl0fEdpGU3uslF0wj/6L36nnYcChGQYy48TDrSYfoR YSfwdAL2w4aj4O/tNlasK1pgObw1DXy7qiWtE3qoz7S4potKxbvNK9Dkl g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAKdQUlCtJXG8/2dsb2JhbABFu3mBB4IgAQEBAwESASc/BQsCAQg2EDIlAgQOBRQOh2UGm02gIYsQhVdgA4s6iiaGTIdsgWmCZoIX
X-IronPort-AV: E=Sophos;i="4.80,419,1344211200"; d="scan'208";a="121383582"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 13 Sep 2012 21:35:47 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id q8DLZl5X028085 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 13 Sep 2012 21:35:47 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.26]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0298.004; Thu, 13 Sep 2012 16:35:47 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: IETF Chair <chair@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Topic: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Index: AQHNkfe84kt1iOU1okqTaNzpsDjdaQ==
Date: Thu, 13 Sep 2012 21:35:46 +0000
Message-ID: <51E05E18-F61D-4915-8282-CB0D580443D1@cisco.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
In-Reply-To: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.167]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19182.001
x-tm-as-result: No--29.179600-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A25002E808FB504CAC1D87537E272341@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 21:35:49 -0000

I like the whole and +1 to it. I can see the pros and cons of make "drafts"=
 actually go away but given it is impossible to get rid of a draft from the=
 internet, all we end up with in the current situation are the cons and non=
e of the pros.

I do have one suggested change=20

OLD
> An I-D will only be removed from the public I-D archive in compliance
> with a duly authorized court order. =20

NEW
> The IETF Chair may decide to removed an I-D from the public I-D archive.=
=20


We have better things to do than argue which courts we might accept court o=
rders from or what a court order is so I suggest we just let the chair do t=
he right thing. The chair will understand the goals of the IETF and have le=
gal advice available to them.  If the wrong thing happens, we can fix it af=
ter the fact by putting the ID back.=20


On Sep 3, 2012, at 6:00 PM, IETF Chair <chair@ietf.org> wrote:

> The IESG is considering this IESG Statement.  Comments from the community=
 are solicited.
>=20
> On behalf of the IESG,
> Russ
>=20
> --- DRAFT IESG STATEMENT ---
>=20
> SUBJECT: Removal of an Internet-Draft from the IETF Web Site
>=20
> Internet-Drafts (I-Ds) are working documents of the IETF, its Areas,
> and its Working Groups.  In addition, other groups, including the IAB
> and the IRTF Research Groups, distribute working documents as I-Ds.
> I-Ds are stored in two places on the IETF web site.  First, current
> ones are stored in the I-D directory.  Second, current and past ones
> are stored in a public I-D archive.
>=20
> I-Ds are readily available to a wide audience from the IETF I-D
> directory.  This availability facilitates informal review, comment,
> and revision.
>=20
> While entries in the I-D directory are subject to change or removal
> at any time, I-Ds generally remain publicly archived to support easy
> comparison with previous versions.
>=20
> Entries in the I-D directory are removed as part of normal process
> when it expires after six months, when it is replaced by a subsequent
> I-D, or when it is replaced by the publication of an RFC.  In all
> of these situations, the I-D remains in the public I-D archive.
>=20
> An I-D will only be removed from the public I-D archive in compliance
> with a duly authorized court order.  If possible, a removed I-D will be
> replaced with a tombstone file that describes the reason that the I-D
> was removed from the public I-D archive.
>=20


From dhc@dcrocker.net  Thu Sep 13 14:59:22 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEB1121F867B; Thu, 13 Sep 2012 14:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kq6TqImpEsy8; Thu, 13 Sep 2012 14:59:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0B721F867A; Thu, 13 Sep 2012 14:59:22 -0700 (PDT)
Received: from [192.168.1.8] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8DLxK8e003831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 14:59:21 -0700
Message-ID: <50525736.9020005@dcrocker.net>
Date: Thu, 13 Sep 2012 14:59:18 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <51E05E18-F61D-4915-8282-CB0D580443D1@cisco.com>
In-Reply-To: <51E05E18-F61D-4915-8282-CB0D580443D1@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.17]); Thu, 13 Sep 2012 14:59:21 -0700 (PDT)
Cc: IETF Chair <chair@ietf.org>, 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, 13 Sep 2012 21:59:23 -0000

On 9/13/2012 2:35 PM, Cullen Jennings (fluffy) wrote:
> OLD
>> An I-D will only be removed from the public I-D archive in compliance
>> with a duly authorized court order.
>
> NEW
>> The IETF Chair may decide to removed an I-D from the public I-D archive.


This defines the IETF Chair as Chief Censor, with no written policy 
guidance.  That is, deletion is at the whimsy of the Chair.

Is that really what we (and the Chair) want?

Given possible legal implications of claimed unfair treatment of a 
document, that's pretty onerous exposure for the Chair.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From barryleiba.mailing.lists@gmail.com  Thu Sep 13 15:08:29 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A43FC21F85FC; Thu, 13 Sep 2012 15:08:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.954
X-Spam-Level: 
X-Spam-Status: No, score=-102.954 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egzxr8gVdB8x; Thu, 13 Sep 2012 15:08:28 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC6721F85F9; Thu, 13 Sep 2012 15:08:27 -0700 (PDT)
Received: by lahm15 with SMTP id m15so2431235lah.31 for <multiple recipients>; Thu, 13 Sep 2012 15:08:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=49+7GFAz9sqI5letVt3sbLH5DJxFFIz4GvfXdwgnsms=; b=NCcJrbxoznoBiyijSOVcuzYitWIVBP+aGiezdNkvhuypplCY3Ml1J0tM22OMGm4ecu xvP3B9OaCTnwUXYlZD8y0aAbaw0PSCGLgbwLNBwmp6RspCz1KcRMQffaXk4B6qhv2xzL 4gk3Yid19i/1zCXqi3H+RS/0mCAC11YtP2EgwER5RoIISbR0CeFmQmAKaloFGoql05a3 Y2DriLF/Y1S2qNffr3RxdG3SDNWaPOcZDyba0Iy7UliheicMItAxbhjQH3ts3QkEDljA mVkKlxkaaCXHad5hRrfPSEB8jyi9q/GIfJtZJJVY8caErnfXBqsGdxZ7WKpx0u/VPMho nMTQ==
MIME-Version: 1.0
Received: by 10.152.112.136 with SMTP id iq8mr568623lab.18.1347574102624; Thu, 13 Sep 2012 15:08:22 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.91.33 with HTTP; Thu, 13 Sep 2012 15:08:22 -0700 (PDT)
In-Reply-To: <50525736.9020005@dcrocker.net>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <51E05E18-F61D-4915-8282-CB0D580443D1@cisco.com> <50525736.9020005@dcrocker.net>
Date: Thu, 13 Sep 2012 18:08:22 -0400
X-Google-Sender-Auth: EmWUa4LNeqULaWl7tUjTGVh4LDA
Message-ID: <CAC4RtVAYy1cpWk1jESkNKZbS-hieJBHh2CYnxabgXwoLfW_SSg@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Barry Leiba <barryleiba@computer.org>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 22:08:29 -0000

>>> The IETF Chair may decide to removed an I-D from the public I-D archive.
>
> This defines the IETF Chair as Chief Censor, with no written policy
> guidance.  That is, deletion is at the whimsy of the Chair.
>
> Is that really what we (and the Chair) want?

I very much agree.  I'm happy with the decision being the consensus of
a board, but not giving it to an individual.

Barry

From dcrocker@bbiw.net  Thu Sep 13 15:11:23 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F68721F869A; Thu, 13 Sep 2012 15:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Md4rCknO-R73; Thu, 13 Sep 2012 15:11:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 98AE121F8600; Thu, 13 Sep 2012 15:11:22 -0700 (PDT)
Received: from [192.168.1.8] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8DMAs0b004156 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 15:10:55 -0700
Message-ID: <505259EB.9020604@bbiw.net>
Date: Thu, 13 Sep 2012 15:10:51 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <51E05E18-F61D-4915-8282-CB0D580443D1@cisco.com> <50525736.9020005@dcrocker.net> <CAC4RtVAYy1cpWk1jESkNKZbS-hieJBHh2CYnxabgXwoLfW_SSg@mail.gmail.com>
In-Reply-To: <CAC4RtVAYy1cpWk1jESkNKZbS-hieJBHh2CYnxabgXwoLfW_SSg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 13 Sep 2012 15:10:55 -0700 (PDT)
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 22:11:23 -0000

On 9/13/2012 3:08 PM, Barry Leiba wrote:
>>>> The IETF Chair may decide to removed an I-D from the public I-D archive.
>>
>> This defines the IETF Chair as Chief Censor, with no written policy
>> guidance.  That is, deletion is at the whimsy of the Chair.
>>
>> Is that really what we (and the Chair) want?
>
> I very much agree.  I'm happy with the decision being the consensus of
> a board, but not giving it to an individual.


Not that you've said something to exclude this, but I want to make sure 
we don't lose the second part:

      I believe we /do/ need a written policy that has been reviewed by 
legal counsel.  Even with a group -- versus individual -- we should not 
create possible charges of censorship up to the personal whims of the 
moment.

d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From david.kessens@nsn.com  Thu Sep 13 15:26:38 2012
Return-Path: <david.kessens@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 5FB3821F86A7; Thu, 13 Sep 2012 15:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.349
X-Spam-Level: 
X-Spam-Status: No, score=-6.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3CPdtyTkhyN; Thu, 13 Sep 2012 15:26:38 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 86E5121F869E; Thu, 13 Sep 2012 15:26:36 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q8DMQ6v0018386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 Sep 2012 00:26:07 +0200
Received: from localhost.localdomain ([10.138.54.205]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q8DMQ2ZY003279; Fri, 14 Sep 2012 00:26:03 +0200
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.14.5/8.14.5) with ESMTP id q8DMQ168017913;  Thu, 13 Sep 2012 15:26:01 -0700
Received: (from david@localhost) by localhost.localdomain (8.14.5/8.14.5/Submit) id q8DMPupV017912; Thu, 13 Sep 2012 15:25:56 -0700
Date: Thu, 13 Sep 2012 15:25:56 -0700
From: David Kessens <david.kessens@nsn.com>
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Message-ID: <20120913222556.GX3051@nsn.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <51E05E18-F61D-4915-8282-CB0D580443D1@cisco.com> <50525736.9020005@dcrocker.net> <CAC4RtVAYy1cpWk1jESkNKZbS-hieJBHh2CYnxabgXwoLfW_SSg@mail.gmail.com> <505259EB.9020604@bbiw.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <505259EB.9020604@bbiw.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: 505
X-purgate-ID: 151667::1347575167-00003184-BC7BCAC1/0-0/0-0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF Chair <chair@ietf.org>, Barry Leiba <barryleiba@computer.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: Thu, 13 Sep 2012 22:26:38 -0000

Dave,

On Thu, Sep 13, 2012 at 03:10:51PM -0700, Dave Crocker wrote:
> 
>      I believe we /do/ need a written policy that has been reviewed
> by legal counsel.

I think the lengthy discussion that we have seen on this topic proofs that
we should NOT have a written policy.

Deal with this on a case-by-case basis seems the most efficient way until we
hear that the IESG spends more time arguing on a particular case than the
IETF community does on a written policy.

David Kessens
---

From dcrocker@bbiw.net  Thu Sep 13 15:43:10 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFD6221F869A; Thu, 13 Sep 2012 15:43:09 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PkdpSw+ZxTZJ; Thu, 13 Sep 2012 15:43:09 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1281621F8698; Thu, 13 Sep 2012 15:43:09 -0700 (PDT)
Received: from [192.168.1.8] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8DMh4oK004751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 15:43:05 -0700
Message-ID: <50526175.30005@bbiw.net>
Date: Thu, 13 Sep 2012 15:43:01 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: David Kessens <david.kessens@nsn.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <51E05E18-F61D-4915-8282-CB0D580443D1@cisco.com> <50525736.9020005@dcrocker.net> <CAC4RtVAYy1cpWk1jESkNKZbS-hieJBHh2CYnxabgXwoLfW_SSg@mail.gmail.com> <505259EB.9020604@bbiw.net> <20120913222556.GX3051@nsn.com>
In-Reply-To: <20120913222556.GX3051@nsn.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, 13 Sep 2012 15:43:05 -0700 (PDT)
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF Chair <chair@ietf.org>, Barry Leiba <barryleiba@computer.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: Thu, 13 Sep 2012 22:43:10 -0000

David,


On 9/13/2012 3:25 PM, David Kessens wrote:
> On Thu, Sep 13, 2012 at 03:10:51PM -0700, Dave Crocker wrote:
>>
>>       I believe we /do/ need a written policy that has been reviewed
>> by legal counsel.
>
> I think the lengthy discussion that we have seen on this topic proofs that
> we should NOT have a written policy.

It shows a tendency of the active IETF discussants to resist doing the 
work of settling on policy for the IETF.  That's quite different from 
demonstrating a lack of /need/.

Essentially none of the enlightened discussion on this thread considered 
legal ramifications of potentially arbitrary censorship by a public 
group such as ourselves.

In other words, I saw the /actual/ implication of the thread as making 
it crystal clear that we do /not/ want a collection of amateurs 
formulating ad hoc censorship policies on the fly.

(Forgive me for underscoring this, but I think the original policy draft 
that was floated to the community was a good demonstration of this 
danger.  Although I happened to like the details of what was floated, 
the fact that it had not been reviewed by counsel prior to being made 
public is quite troubling.)


> Deal with this on a case-by-case basis seems the most efficient way until we
> hear that the IESG spends more time arguing on a particular case than the
> IETF community does on a written policy.

For an organization in the business of writing global standards, we are 
remarkably resistant to doing the thoughtful and deliberate policy work 
of writing standards for ourselves.

Instead we tend to prefer the whimsy of personal adhoc-racy, with its 
typical dangers of inconsistency and incompleteness.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From david.kessens@nsn.com  Thu Sep 13 15:55:14 2012
Return-Path: <david.kessens@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 09AFB21F868A; Thu, 13 Sep 2012 15:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.37
X-Spam-Level: 
X-Spam-Status: No, score=-6.37 tagged_above=-999 required=5 tests=[AWL=0.229,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMY-ld7MKzkf; Thu, 13 Sep 2012 15:55:13 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8446D21F86B7; Thu, 13 Sep 2012 15:55:08 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q8DMsu2V012269 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 Sep 2012 00:54:57 +0200
Received: from localhost.localdomain ([10.138.54.205]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q8DMsrBg018844; Fri, 14 Sep 2012 00:54:54 +0200
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.14.5/8.14.5) with ESMTP id q8DMsq0M018004;  Thu, 13 Sep 2012 15:54:52 -0700
Received: (from david@localhost) by localhost.localdomain (8.14.5/8.14.5/Submit) id q8DMsqOf018003; Thu, 13 Sep 2012 15:54:52 -0700
Date: Thu, 13 Sep 2012 15:54:52 -0700
From: David Kessens <david.kessens@nsn.com>
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Message-ID: <20120913225452.GZ3051@nsn.com>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <51E05E18-F61D-4915-8282-CB0D580443D1@cisco.com> <50525736.9020005@dcrocker.net> <CAC4RtVAYy1cpWk1jESkNKZbS-hieJBHh2CYnxabgXwoLfW_SSg@mail.gmail.com> <505259EB.9020604@bbiw.net> <20120913222556.GX3051@nsn.com> <50526175.30005@bbiw.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50526175.30005@bbiw.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: 334
X-purgate-ID: 151667::1347576897-00003184-CD472CE5/0-0/0-0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF Chair <chair@ietf.org>, Barry Leiba <barryleiba@computer.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: Thu, 13 Sep 2012 22:55:14 -0000

Dave,

On Thu, Sep 13, 2012 at 03:43:01PM -0700, Dave Crocker wrote:
> 
> Essentially none of the enlightened discussion on this thread
> considered legal ramifications of potentially arbitrary censorship
> by a public group such as ourselves.

Aren't you going a little overboard in hyperbole here ?

David Kessens
---

From dcrocker@bbiw.net  Thu Sep 13 16:05:01 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BFF921F8557; Thu, 13 Sep 2012 16:05: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7gsXsxvp2wt6; Thu, 13 Sep 2012 16:05:01 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C3FD421F8546; Thu, 13 Sep 2012 16:04:54 -0700 (PDT)
Received: from [192.168.1.8] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8DN4lfX005287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 16:04:48 -0700
Message-ID: <5052668D.3040304@bbiw.net>
Date: Thu, 13 Sep 2012 16:04:45 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: David Kessens <david.kessens@nsn.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <51E05E18-F61D-4915-8282-CB0D580443D1@cisco.com> <50525736.9020005@dcrocker.net> <CAC4RtVAYy1cpWk1jESkNKZbS-hieJBHh2CYnxabgXwoLfW_SSg@mail.gmail.com> <505259EB.9020604@bbiw.net> <20120913222556.GX3051@nsn.com> <50526175.30005@bbiw.net> <20120913225452.GZ3051@nsn.com>
In-Reply-To: <20120913225452.GZ3051@nsn.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, 13 Sep 2012 16:04:48 -0700 (PDT)
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF Chair <chair@ietf.org>, Barry Leiba <barryleiba@computer.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: Thu, 13 Sep 2012 23:05:01 -0000

On 9/13/2012 3:54 PM, David Kessens wrote:
> On Thu, Sep 13, 2012 at 03:43:01PM -0700, Dave Crocker wrote:
>>
>> Essentially none of the enlightened discussion on this thread
>> considered legal ramifications of potentially arbitrary censorship
>> by a public group such as ourselves.
>
> Aren't you going a little overboard in hyperbole here ?


you mean by claiming the discussion was enlightened?

the rest was offered as an observation and reporting of what I believe 
to fact, in factual language.  if you see hyperbole in any of it, please 
explain.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From john-ietf@jck.com  Thu Sep 13 16:20:44 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44B6221F855F; Thu, 13 Sep 2012 16:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JoJQFqpZTeSc; Thu, 13 Sep 2012 16:20:43 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DFDA321F84FD; Thu, 13 Sep 2012 16:20:41 -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 1TCIi2-0002kL-CC; Thu, 13 Sep 2012 19:20:34 -0400
Date: Thu, 13 Sep 2012 19:20:29 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@bbiw.net>, Barry Leiba <barryleiba@computer.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <F9099C1545DE9339E93ACE9D@JcK-HP8200.jck.com>
In-Reply-To: <505259EB.9020604@bbiw.net>
References: <612BDD24-8E51-43D9-BFB6-25C90635CA5C@ietf.org> <51E05E18-F61D-4915-8282-CB0D580443D1@cisco.com> <50525736.9020005@dcrocker.net> <CAC4RtVAYy1cpWk1jESkNKZbS-hieJBHh2CYnxabgXwoLfW_SSg@mail.gmail.com> <505259EB.9020604@bbiw.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: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 23:20:44 -0000

--On Thursday, September 13, 2012 15:10 -0700 Dave Crocker
<dcrocker@bbiw.net> wrote:

> On 9/13/2012 3:08 PM, Barry Leiba wrote:
>>>>> The IETF Chair may decide to removed an I-D from the
>>>>> public I-D archive.
>>> 
>>> This defines the IETF Chair as Chief Censor, with no written
>>> policy guidance.  That is, deletion is at the whimsy of the
>>> Chair.
>>> 
>>> Is that really what we (and the Chair) want?
>> 
>> I very much agree.  I'm happy with the decision being the
>> consensus of a board, but not giving it to an individual.
> 
> 
> Not that you've said something to exclude this, but I want to
> make sure we don't lose the second part:
> 
>       I believe we /do/ need a written policy that has been
> reviewed by legal counsel.  Even with a group -- versus
> individual -- we should not create possible charges of
> censorship up to the personal whims of the moment.

I'm not sure, Dave.  I see the theoretical risk, but the number
of times that problem has occurred in the past is, I believe,
zero.  I'd be more concerned about it if we were talking about
removing active documents rather than taking something out of
the publicly-available archive of expired documents.   And a
decision by the IESG to remove a document would presumably be,
like all other IESG decisions, subject to appeal.   

If the IESG started taking down documents just because they
didn't like them, I'd also think we'd quickly try out the recall
procedure for the first time.  But, again, the IESG has had many
years of experience with I-Ds they don't like (and many such
documents), during most of which time no one questioned their
ability to remove a document from public view (active or
archived) and, AFAIK, we have seen absolutely no abuse of that
type.

I'd be ok with a "written policy that has been reviewed by legal
counsel" if I thought there were even reasonable odds of its
adequately covering all the cases.  But I fear that such a
policy would exclude some important case and thereby get the
IESG in trouble as we tried to work with (or work around, or
revise on an emergency basis) a policy that turned out to
prevent us (or even the IESG or IETF Trust) from exercising good
sense and doing what is either obviously right or as advised by
Counsel when Counsel is presented by a particular situation.

Proposal: I think it would be fine to have a policy in which:

(1) A document would be taken down as quickly as
	possible in response to a legitimate court order with
	approval of Counsel.
(2) A document to which, in the opinion of Counsel, the
	IETF might not have clear copyright title, and for which
	a DCMA take-down notice or equivalent was received
	unless the IESG, with advice and consent of Counsel,
	advised against such a takedown.
(3) The IESG could take anything else down for cause
   at its discretion after:
	(3.1) Seeking and receiving advice of Counsel
	(3.2) Announcing intention to do so, and the cause,
     on the IETF-announce list and allowing a brief 
     period for objections.
	(3.3) Considering any advice and objections before
   	making a final decision.
   (3.4) Subject to the above, the IESG is encouraged 
     to look with favor on requests to remove already- 
     expired documents from the public archive from the 
     party responsible for the document (authors of 
     individual drafts; WGs for WG drafts).  We 
     recognize that such removal doesn't cause the 
     documents to disappear from the Internet, but 
     responsible parties making such requests about
     their own documents presumably have reasons that 
     we should treat respectfully.
(4) Any of those actions would be subject to appeal if
	members of the community felt there were important
	issues that had not been considered.  An appeal could
	request that the advice from Counsel be made available
	to the community.  The IESG would be required to either
	comply with that request or explain why not.

I don't like it --my personal position is much closer to Joe's
or Sam's-- but, if there is consensus that we have to have a
written policy, one like the above at least doesn't tie our
hands when a situation arises that we haven't anticipated.
While there is some possibility of DoS attacks embedded in it,
it remains important that we haven't seen huge numbers of these
requests (or even small numbers).  Indeed, one of my fears about
the amount of discussion we've had (and any formal policy at
this point) is that it may encourage such requests.  Too late to
worry about that now.

best,
   john


From johnl@iecc.com  Thu Sep 13 16:56:31 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBD5821F866D for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 16:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4QU-bLj6sXKo for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 16:56:30 -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 EC0A121F866C for <ietf@ietf.org>; Thu, 13 Sep 2012 16:56:29 -0700 (PDT)
Received: (qmail 19803 invoked from network); 13 Sep 2012 23:56:26 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 13 Sep 2012 23:56:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=505272aa.xn--30v786c.k1208; i=johnl@user.iecc.com; bh=b09axdiCdCSymTFJKog2KbKMc/MZo5fzAa8F//Sqjdg=; b=P/DzFOTwTWpN8ijWQ9nqUDM0018PYEl8l0xKvavt057ahDRoouFf170WfBP+5vwuwIiVJFuklXIPzplSGCik35CqE8MGO381NNUD+VCd4hQ6L1/VpLcrlQoiuPHDzslOI/7bsZc9dxwLOvKDztw5WzuREB/7GcISbt/pmhrL8Xo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=505272aa.xn--30v786c.k1208; olt=johnl@user.iecc.com; bh=b09axdiCdCSymTFJKog2KbKMc/MZo5fzAa8F//Sqjdg=; b=IN4X6VwfpO7pa9YHemR6gun2ZkD67kEdcWFkXrmqyXMwgQe1jYM7pCpAZ7Q2Ck72FaUUaQp9IlyXJMTUxaN7YQeiN4g1QJI+19gJmoNn4MSo38tBSGjd/jx9JzDA21Xd9XDvj0nYdqi1obFsUC1mvOclb4dGWAZgwC8E6Vgfkvo=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 13 Sep 2012 23:56:03 -0000
Message-ID: <20120913235603.81747.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <CAC4RtVAYy1cpWk1jESkNKZbS-hieJBHh2CYnxabgXwoLfW_SSg@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: barryleiba@computer.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 23:56:31 -0000

>I very much agree.  I'm happy with the decision being the consensus of
>a board, but not giving it to an individual.

So give it to the IESG and we can stop arguing about it.

I have to say, the urge to post a few I-D's consisting of snuff porn
is nearly irresistible.

R's,
John

From johnl@iecc.com  Thu Sep 13 16:59:40 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FDAB21F8672 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 16:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oi9VBRzC6r2W for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 16:59:40 -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 BDE1021F867A for <ietf@ietf.org>; Thu, 13 Sep 2012 16:59:39 -0700 (PDT)
Received: (qmail 20425 invoked from network); 13 Sep 2012 23:59:39 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 13 Sep 2012 23:59: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:mime-version:content-type:content-transfer-encoding:vbr-info; s=5052736b.xn--btvx9d.k1208; i=johnl@user.iecc.com; bh=/4HfLxh3cgfPK7i2laZw10Y/2774oZR0KCR9BKlQ9YU=; b=AiXNoyhawIpoaPlKoALuaW6nDzYLNSIoPQV7yJ13/LOsR+znay+p9Qw+yxZC1gBDBEcAt0T/nHH9gro5mGhMypbt1RfbdEgkNBjXKnGD0+pt3ee6lh4yAr3YIzU3raqELFtUPsOnRGwAQ9IpnNz040JXRupH7q3R/ZejMSGURdo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5052736b.xn--btvx9d.k1208; olt=johnl@user.iecc.com; bh=/4HfLxh3cgfPK7i2laZw10Y/2774oZR0KCR9BKlQ9YU=; b=Qnn2D8Vb2ArtqVHtRh1S3/oUi48xNgyXif0s8iEdy2kD18AFjQVXVa9mhOtRJtg7G8Zf38K3IXNrhh+Ee0LfS8DeUAkGEiQngkigZS/UVAebTQ1n8q/v+Row6+3Ss/RvbStEVKeaC3+Nshft9V5W1k4mvSviniGxOUpn/AtznBY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 13 Sep 2012 23:59:16 -0000
Message-ID: <20120913235916.87233.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <505259EB.9020604@bbiw.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: 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: Thu, 13 Sep 2012 23:59:40 -0000

>      I believe we /do/ need a written policy that has been reviewed by 
>legal counsel.  Even with a group -- versus individual -- we should not 
>create possible charges of censorship up to the personal whims of the 
>moment.

Censorship?  Sheesh.

The IETF is not the government.  We have no obligation to anyone to
publish anything, nor can we keep anyone from publishing anything on
the 99.99999% of the Internet that the IETF does not control.  

As I think I've said several times before, if we think the IESG would
start gratuitously deleting stuff, we have much worse problems than
any policy statement could solve.

R's,
John

From johnl@iecc.com  Thu Sep 13 17:25:38 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 452FF21F8672 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 17:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kRGoJ5Z1fxvk for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 17:25:37 -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 5A20A21F866C for <ietf@ietf.org>; Thu, 13 Sep 2012 17:25:37 -0700 (PDT)
Received: (qmail 26197 invoked from network); 14 Sep 2012 00:25:35 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 14 Sep 2012 00:25:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5052797f.xn--i8sz2z.k1208; i=johnl@user.iecc.com; bh=dcorAWV6zHCBYNR6tRUVd2suOl/GivC7B1SClgueYu0=; b=iXhz2u70Qmm3gcJtfGXwThE+f2qJ0bUqmL1tWT6hgg7yQTXOEWjkAeHk2vMKrQ8jWk9xRCmOEHbmdhQ9fDqu6wGzF/Gbl1IOO1vbewbdRSLQGKVPjm48hC/UpTmYgzZstceBFJoE2J54FW0BHfejJ+ia/Yow6BR4Ti8vVUzG8yI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5052797f.xn--i8sz2z.k1208; olt=johnl@user.iecc.com; bh=dcorAWV6zHCBYNR6tRUVd2suOl/GivC7B1SClgueYu0=; b=U9zDpQKFwCuy2GkOsf6Lsr/Xx+pVYcHBnVtC9Ww9BcI2bdECzerjRqNhzC1rnugRrTwtYCLMkgu7Y/g301lV7IpCMevVpEhxb4M7vGsUeieeWU1otfiE3l3TJWpNptJRgKPe8OztuLqvj2N5TQbNM0RxEg2ZgsaHaYr3Psti/ss=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 14 Sep 2012 00:25:13 -0000
Message-ID: <20120914002513.21159.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <50526175.30005@bbiw.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: 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: Fri, 14 Sep 2012 00:25:38 -0000

>It shows a tendency of the active IETF discussants to resist doing the 
>work of settling on policy for the IETF.  That's quite different from 
>demonstrating a lack of /need/.

The IETF has been around for 26 years, and has had, I gather, zero
removal requests to date.

If that doesn't demonstrate lack of need, what would?

R's,
John

From touch@isi.edu  Thu Sep 13 18:25:00 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CCDD21F865C for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 18:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.669
X-Spam-Level: 
X-Spam-Status: No, score=-104.669 tagged_above=-999 required=5 tests=[AWL=1.330, BAYES_00=-2.599, J_CHICKENPOX_47=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNrvolDqEaBt for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 18:24:59 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id E7D3421F8624 for <ietf@ietf.org>; Thu, 13 Sep 2012 18:24:59 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q8E1NiWd010070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 18:23:55 -0700 (PDT)
Message-ID: <50528720.6050507@isi.edu>
Date: Thu, 13 Sep 2012 18:23:44 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120913192819.3EC361A223@ld9781.wdf.sap.corp>
In-Reply-To: <20120913192819.3EC361A223@ld9781.wdf.sap.corp>
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: Barry Leiba <barryleiba@computer.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: Fri, 14 Sep 2012 01:25:00 -0000

On 9/13/2012 12:28 PM, Martin Rex wrote:
> Joe,
>
>>
>> So it's not a slam dunk that you have the rights you think for every
>> I-D; you definitely don't have those rights for IDs
>
> We're NOT talking about rights that were transfered from the document
> author to arbitrary third parties here, but about rights that were
> given to the IETF ("IETF contribution"), and which have never been
> time-limited.

The "expires" term and corresponding entire text of the ID submissions 
guidelines suggest otherwise.

> So archival and making accessible I-D contributions past the "expiration"
> of an I-D is perfectly legal for the IETF, unless the I-D contains an
> explicit copyright notice to the contrary (most I-Ds from 199x do not
> seem to carry any copyright notice at all).

I've already pointed out text that, e.g., someone might use to make the 
case to the contrary.

Finally, in the US, lawyer isn't who would decide this; a jury would.

> Where you are _correct_ is, copy&pasting parts of such an old I-D
> or the whole document into new documents will in fact require contacting
> the original author(s)/copyright holder(s) and obtain permission,
> the Note Well provisions likely will not be sufficient, at least for those
> old I-Ds. (it is not just a matter of courtesy, but a requirement).
>
> I assume the latter is what rfc5378 is supposed to fix.

There are several variants of issues that apply, at least three I recall:

	pre 1994
	1994-2008
	2008-now

This isn't the first time this issue has been discussed on this list.

RFC 5378 is intended to address reuse of material, as you suggest - not 
whether that material can be publicly posted.

Joe




From touch@isi.edu  Thu Sep 13 20:15:26 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1812321F864D for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 20:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.09
X-Spam-Level: 
X-Spam-Status: No, score=-103.09 tagged_above=-999 required=5 tests=[AWL=-0.491, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UzrUGGhc8njs for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 20:15:25 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id A367521F861C for <ietf@ietf.org>; Thu, 13 Sep 2012 20:15:25 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8E3EGtU017003 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 20:14:26 -0700 (PDT)
Message-ID: <5052A107.9080803@isi.edu>
Date: Thu, 13 Sep 2012 20:14:15 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120913005905.B5B1F1A216@ld9781.wdf.sap.corp> <50513202.7070107@isi.edu> <CALaySJLgpKY7iGvawK-H8WOnq+qn82kS+Lb5w+gqxa_H0iR4CQ@mail.gmail.com> <4C1F0118D8069BF8DFDC9F9B@JcK-HP8200.jck.com> <5051851E.6050208@dcrocker.net> <50518919.6070403@isi.edu> <5052202D.1010509@gmail.com>
In-Reply-To: <5052202D.1010509@gmail.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Sep 2012 03:15:26 -0000

On 9/13/2012 11:04 AM, Melinda Shore wrote:
> On 9/12/12 11:19 PM, Joe Touch wrote:
>> PirateBay believes this too, and helps make movies available for public
>> access, honoring pragmatics.
>
> I'm not sure I understand this analogy.  Are you saying that there are
> IPR issues related to making expired drafts available?

Yes. Depends on the IDs, when they were authored, and which version of 
the boilerplate they contain.

Joe

From johnl@iecc.com  Thu Sep 13 20:41:02 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB8221F8685 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 20:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eG1+ATOagIBQ for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 20:41:01 -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 1946321F85AC for <ietf@ietf.org>; Thu, 13 Sep 2012 20:41:00 -0700 (PDT)
Received: (qmail 70617 invoked from network); 14 Sep 2012 03:40:59 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 14 Sep 2012 03:40:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5052a74a.xn--btvx9d.k1208; i=johnl@user.iecc.com; bh=YP8q/KzDD/N2oakdPMI9xrVZ0OT+FTamgrWNWfKK1Ow=; b=adavNl73yz2WKmF1+G0n7v3UOXViCgwXkto1Q3s1u+L1gH1JXuVY35f26037nyNeyiWoI7WK52U9Utz3LRV4OyNX3qQsIIr/OUZqm9HBJx6DauHPlCLUBxI6kA2VGUBh/NviCTU15zcSpugVBHxW19XvspF2WqW9T78Fuyz27dQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5052a74a.xn--btvx9d.k1208; olt=johnl@user.iecc.com; bh=YP8q/KzDD/N2oakdPMI9xrVZ0OT+FTamgrWNWfKK1Ow=; b=Bs3IVtDYVFywWOWJSdltGRHNeSA8STQRFNsRn6607YSfKGgrRxzr37Yhw4MSOWyfbEbCnvaZn78jMhYHJmSFC1Z1kuu1QUPZfJDLiW4LhOixlCpnlzQyDzETmbR4kZg275bLDrlhTh/i9HA5YaU9H6UlgIaL2zYZLwTtgsW7A+Y=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 14 Sep 2012 03:40:36 -0000
Message-ID: <20120914034036.2211.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <5052A107.9080803@isi.edu>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2012 03:41:02 -0000

>> I'm not sure I understand this analogy.  Are you saying that there are
>> IPR issues related to making expired drafts available?
>
>Yes. Depends on the IDs, when they were authored, and which version of 
>the boilerplate they contain.

Can you give a concrete example of an I-D with this problem?  I don't ever
recall a time when the grant of rights to the IETF had a time limit.

R's,
John

From touch@isi.edu  Thu Sep 13 21:24:13 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCB7021F8645 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 21:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.049
X-Spam-Level: 
X-Spam-Status: No, score=-105.049 tagged_above=-999 required=5 tests=[AWL=1.550, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UxWdOq8SFBwe for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 21:24:13 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 9B7ED21F863C for <ietf@ietf.org>; Thu, 13 Sep 2012 21:24:11 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q8E4Nbut003778 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 21:23:47 -0700 (PDT)
Message-ID: <5052B148.9030803@isi.edu>
Date: Thu, 13 Sep 2012 21:23:36 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120914034036.2211.qmail@joyce.lan>
In-Reply-To: <20120914034036.2211.qmail@joyce.lan>
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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Sep 2012 04:24:13 -0000

There were times when there were no rights granted explicitly, at least. 
I indicated the three ranges in a previous mail.

Joe

On 9/13/2012 8:40 PM, John Levine wrote:
>>> I'm not sure I understand this analogy.  Are you saying that there are
>>> IPR issues related to making expired drafts available?
>>
>> Yes. Depends on the IDs, when they were authored, and which version of
>> the boilerplate they contain.
>
> Can you give a concrete example of an I-D with this problem?  I don't ever
> recall a time when the grant of rights to the IETF had a time limit.
>
> R's,
> John
>

From narten@us.ibm.com  Thu Sep 13 21:53:11 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5497421F85AD for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 21:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.449
X-Spam-Level: 
X-Spam-Status: No, score=-109.449 tagged_above=-999 required=5 tests=[AWL=1.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DwrOEmRfiqVo for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 21:53:10 -0700 (PDT)
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2708421F859F for <ietf@ietf.org>; Thu, 13 Sep 2012 21:53:09 -0700 (PDT)
Received: from /spool/local by e1.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, 14 Sep 2012 00:53:06 -0400
Received: from d01relay07.pok.ibm.com (9.56.227.147) by e1.ny.us.ibm.com (192.168.1.101) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 14 Sep 2012 00:53:05 -0400
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 q8E4r5Oe15597712 for <ietf@ietf.org>; Fri, 14 Sep 2012 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 q8E4r4Ft017137 for <ietf@ietf.org>; Fri, 14 Sep 2012 01:53:04 -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 q8E4r3Zx017093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 14 Sep 2012 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 q8E4r3qj021401 for <ietf@ietf.org>; Fri, 14 Sep 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q8E4r30H021362 for ietf@ietf.org; Fri, 14 Sep 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201209140453.q8E4r30H021362@rotala.raleigh.ibm.com>
Date: Fri, 14 Sep 2012 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
x-cbid: 12091404-6078-0000-0000-00000F7C0E63
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Sep 2012 04:53:11 -0000

Total of 150 messages in the last 7 days.
 
script run at: Fri Sep 14 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 12.67% |   19 | 11.73% |   116162 | touch@isi.edu
  6.67% |   10 |  6.47% |    64122 | johnl@taugh.com
  5.33% |    8 |  6.01% |    59500 | john-ietf@jck.com
  4.67% |    7 |  4.65% |    46042 | barryleiba@computer.org
  4.67% |    7 |  4.40% |    43565 | melinda.shore@gmail.com
  4.67% |    7 |  3.98% |    39383 | dhc@dcrocker.net
  3.33% |    5 |  4.62% |    45769 | eric.gray@ericsson.com
  3.33% |    5 |  3.28% |    32519 | lear@cisco.com
  3.33% |    5 |  3.06% |    30300 | ned+ietf@mauve.mrochek.com
  3.33% |    5 |  2.49% |    24665 | randy@psg.com
  2.67% |    4 |  2.10% |    20831 | simon.perreault@viagenie.ca
  2.00% |    3 |  2.77% |    27395 | rdroms.ietf@gmail.com
  2.00% |    3 |  2.04% |    20188 | sm@resistor.net
  2.00% |    3 |  2.01% |    19880 | mrex@sap.com
  2.00% |    3 |  1.91% |    18944 | cabo@tzi.org
  2.00% |    3 |  1.86% |    18424 | dcrocker@bbiw.net
  1.33% |    2 |  1.83% |    18142 | fluffy@cisco.com
  1.33% |    2 |  1.68% |    16630 | simon@josefsson.org
  1.33% |    2 |  1.64% |    16223 | daedulus@btconnect.com
  1.33% |    2 |  1.52% |    15096 | brian.e.carpenter@gmail.com
  1.33% |    2 |  1.35% |    13386 | glenzorn@gmail.com
  1.33% |    2 |  1.20% |    11892 | david.kessens@nsn.com
  1.33% |    2 |  1.18% |    11664 | chair@ietf.org
  1.33% |    2 |  1.11% |    11000 | ajs@anvilwalrusden.com
  0.67% |    1 |  1.65% |    16355 | lars@netapp.com
  0.67% |    1 |  1.01% |     9976 | hsantos@isdg.net
  0.67% |    1 |  0.92% |     9118 | david.borman@quantum.com
  0.67% |    1 |  0.86% |     8518 | chris.dearlove@baesystems.com
  0.67% |    1 |  0.84% |     8350 | narten@us.ibm.com
  0.67% |    1 |  0.82% |     8072 | kuor-hsin.chang@us.elster.com
  0.67% |    1 |  0.81% |     8034 | lizhong.jin@zte.com.cn
  0.67% |    1 |  0.77% |     7660 | swb@internet2.edu
  0.67% |    1 |  0.77% |     7620 | fmartin@linkedin.com
  0.67% |    1 |  0.74% |     7323 | eburger-l@standardstrack.com
  0.67% |    1 |  0.73% |     7185 | mcr@sandelman.ca
  0.67% |    1 |  0.70% |     6907 | abdussalambaryun@gmail.com
  0.67% |    1 |  0.69% |     6794 | loa@pi.nu
  0.67% |    1 |  0.67% |     6643 | david.black@emc.com
  0.67% |    1 |  0.65% |     6452 | ynir@checkpoint.com
  0.67% |    1 |  0.65% |     6424 | bob.hinden@gmail.com
  0.67% |    1 |  0.64% |     6363 | roni.even@mail01.huawei.com
  0.67% |    1 |  0.64% |     6313 | petithug@acm.org
  0.67% |    1 |  0.63% |     6247 | robert@raszuk.net
  0.67% |    1 |  0.63% |     6223 | dot@dotat.at
  0.67% |    1 |  0.62% |     6100 | klensin@jck.com
  0.67% |    1 |  0.61% |     6017 | hartmans-ietf@mit.edu
  0.67% |    1 |  0.60% |     5894 | stbryant@cisco.com
  0.67% |    1 |  0.59% |     5859 | hallam@gmail.com
  0.67% |    1 |  0.59% |     5811 | derek@ihtfp.com
  0.67% |    1 |  0.58% |     5720 | cos@aaaaa.org
  0.67% |    1 |  0.57% |     5606 | dan@fsround.org
  0.67% |    1 |  0.56% |     5520 | d3e3e3@gmail.com
  0.67% |    1 |  0.55% |     5463 | paf@frobbit.se
  0.67% |    1 |  0.54% |     5386 | smb@cs.columbia.edu
  0.67% |    1 |  0.53% |     5283 | rgolodner@infratection.com
  0.67% |    1 |  0.53% |     5249 | nick@inex.ie
  0.67% |    1 |  0.52% |     5146 | peter@akayla.com
  0.67% |    1 |  0.52% |     5139 | wjhns1@hardakers.net
  0.67% |    1 |  0.50% |     4904 | adrian@olddog.co.uk
  0.67% |    1 |  0.49% |     4847 | rbarnes@bbn.com
  0.67% |    1 |  0.42% |     4168 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |  150 |100.00% |   990411 | Total


From mrex@sap.com  Thu Sep 13 22:10:08 2012
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 CB00A21F86B9 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 22:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.189
X-Spam-Level: 
X-Spam-Status: No, score=-10.189 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OBv0cKFYa+sA for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 22:10:07 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 8739621F84EC for <ietf@ietf.org>; Thu, 13 Sep 2012 22:10:07 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q8E5A5Tf013222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 Sep 2012 07:10:05 +0200 (MEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <5052B148.9030803@isi.edu>
To: Joe Touch <touch@isi.edu>
Date: Fri, 14 Sep 2012 07:10:04 +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: <20120914051004.9A16F1A224@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: John Levine <johnl@taugh.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: Fri, 14 Sep 2012 05:10:08 -0000

Joe Touch wrote:
>
> There were times when there were no rights granted explicitly, at least. 
> I indicated the three ranges in a previous mail.

In which case the Note Well concludently applies to the I-D contents,
which seems to have first appeared on www.ietf.org around 2001,

  http://web.archive.org/web/20010413091132/http://ietf.org/overview.html

and slightly extended in 2002:

  http://web.archive.org/web/20020605140239/http://ietf.org/overview.html

primarily refering to the IETF process described in rfc2026 section 10:

http://tools.ietf.org/html/rfc2026#section-10

  10.2, 10.3, 10.3.1 (2), 10.3.1 (5), 10.3.1 (7)


  10.3.1.  All Contributions 

   7. The contributor represents that there are no limits to the
      contributor's ability to make the grants acknowledgments and
      agreements above that are reasonably and personally known to the
      contributor.

      By ratifying this description of the IETF process the Internet
      Society warrants that it will not inhibit the traditional open and
*>    free access to IETF documents for which license and right have
*>    been assigned according to the procedures set forth in this
*>    section, including Internet-Drafts and RFCs. This warrant is
*>    perpetual and will not be revoked by the Internet Society or its
*>    successors or assigns.


So which specific part of "including Internet-Drafts and RFCs"
and "This warrent is perpetual" caused your impression that
there was a time-limit on an I-D contribution?

-Martin


btw. rfc2026 10.3.1 (2) looks like an explicit non-policy for dissemmination
or termination of dissemination to me:

   2. The contributor acknowledges that the ISOC and IETF have no duty
      to publish or otherwise use or disseminate any contribution.


I would be OK with a single person from (IESG member or IETF Chair)
quickly decides about suspending dissemination of a document based on
personal judgement and that the IESG wiggles out by themselves an
informal procedure (rather than a formal policy) for safeguarding
the process (from bias and abuse).  This cuts into their time budget
and seems to not be a concerningly frequent occurence to spend
much polish on it at this point.


From touch@isi.edu  Thu Sep 13 22:36:22 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8FA21F8715 for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 22:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.168
X-Spam-Level: 
X-Spam-Status: No, score=-103.168 tagged_above=-999 required=5 tests=[AWL=-0.569, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48crITS4g6HP for <ietf@ietfa.amsl.com>; Thu, 13 Sep 2012 22:36:21 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id C333521F8705 for <ietf@ietf.org>; Thu, 13 Sep 2012 22:36:21 -0700 (PDT)
Received: from [192.168.0.17] ([210.114.91.73]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q8E5ZQcY004860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 13 Sep 2012 22:35:37 -0700 (PDT)
Message-ID: <5052C21E.4030408@isi.edu>
Date: Thu, 13 Sep 2012 22:35:26 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120914051004.9A16F1A224@ld9781.wdf.sap.corp>
In-Reply-To: <20120914051004.9A16F1A224@ld9781.wdf.sap.corp>
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: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2012 05:36:22 -0000

Note well, as you noted well, does not go back to the beginning of all IDs.

I.e., this is a tangled mess of different copyrights, different note 
wells, etc., and it's not as simple as "it's the IETF's right" to do 
anything except - maybe - going forward with a new copyright statement 
for IDs.



Joe

On 9/13/2012 10:10 PM, Martin Rex wrote:
> Joe Touch wrote:
>>
>> There were times when there were no rights granted explicitly, at least.
>> I indicated the three ranges in a previous mail.
>
> In which case the Note Well concludently applies to the I-D contents,
> which seems to have first appeared on www.ietf.org around 2001,
>
>    http://web.archive.org/web/20010413091132/http://ietf.org/overview.html
>
> and slightly extended in 2002:
>
>    http://web.archive.org/web/20020605140239/http://ietf.org/overview.html
>
> primarily refering to the IETF process described in rfc2026 section 10:
>
> http://tools.ietf.org/html/rfc2026#section-10
>
>    10.2, 10.3, 10.3.1 (2), 10.3.1 (5), 10.3.1 (7)
>
>
>    10.3.1.  All Contributions
>
>     7. The contributor represents that there are no limits to the
>        contributor's ability to make the grants acknowledgments and
>        agreements above that are reasonably and personally known to the
>        contributor.
>
>        By ratifying this description of the IETF process the Internet
>        Society warrants that it will not inhibit the traditional open and
> *>    free access to IETF documents for which license and right have
> *>    been assigned according to the procedures set forth in this
> *>    section, including Internet-Drafts and RFCs. This warrant is
> *>    perpetual and will not be revoked by the Internet Society or its
> *>    successors or assigns.
>
>
> So which specific part of "including Internet-Drafts and RFCs"
> and "This warrent is perpetual" caused your impression that
> there was a time-limit on an I-D contribution?
>
> -Martin
>
>
> btw. rfc2026 10.3.1 (2) looks like an explicit non-policy for dissemmination
> or termination of dissemination to me:
>
>     2. The contributor acknowledges that the ISOC and IETF have no duty
>        to publish or otherwise use or disseminate any contribution.
>
>
> I would be OK with a single person from (IESG member or IETF Chair)
> quickly decides about suspending dissemination of a document based on
> personal judgement and that the IESG wiggles out by themselves an
> informal procedure (rather than a formal policy) for safeguarding
> the process (from bias and abuse).  This cuts into their time budget
> and seems to not be a concerningly frequent occurence to spend
> much polish on it at this point.
>

From john-ietf@jck.com  Fri Sep 14 03:39:51 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B30B321F84A5 for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 03:39:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Carh2UATLF6n for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 03:39:50 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id F384321F849B for <ietf@ietf.org>; Fri, 14 Sep 2012 03:39:49 -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 1TCTJL-0004Tt-VP; Fri, 14 Sep 2012 06:39:47 -0400
Date: Fri, 14 Sep 2012 06:39:42 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <F9730848908AE0E280FE0693@JcK-HP8200.jck.com>
In-Reply-To: <20120913235916.87233.qmail@joyce.lan>
References: <20120913235916.87233.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2012 10:39:51 -0000

--On Thursday, September 13, 2012 23:59 +0000 John Levine
<johnl@taugh.com> wrote:

> Censorship?  Sheesh.
>...
> As I think I've said several times before, if we think the
> IESG would start gratuitously deleting stuff, we have much
> worse problems than any policy statement could solve.

+1 
Exactly.

The jump from "what do we do with the range of
seemingly-legitimate request from an outside party to remove a
document from public view" to "if give flexibility, the IETF
might use it to start removing (or censoring) documents they
don't like" seems incredible to me.  

     john


From tglassey@earthlink.net  Fri Sep 14 06:27:14 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8BA21F84F6 for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 06:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level: 
X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5bb8Zzs0lMF for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 06:27:14 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 05DDA21F84F5 for <ietf@ietf.org>; Fri, 14 Sep 2012 06:27:13 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=i0WGgKdcmGjyFgeqR0ery0OtYRjMrkkBZ9IfHpdZG6WEIVlTl37zNFMmr/JYuyJx; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TCVvN-0002yX-EO for ietf@ietf.org; Fri, 14 Sep 2012 09:27:13 -0400
Message-ID: <505330A8.5010605@earthlink.net>
Date: Fri, 14 Sep 2012 06:27:04 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120914034036.2211.qmail@joyce.lan>
In-Reply-To: <20120914034036.2211.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7951872a33ecee3c0a114e16c3ac2b2b7c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2012 13:27:14 -0000

On 9/13/2012 8:40 PM, John Levine wrote:
>>> I'm not sure I understand this analogy.  Are you saying that there are
>>> IPR issues related to making expired drafts available?
>> Yes. Depends on the IDs, when they were authored, and which version of
>> the boilerplate they contain.
> Can you give a concrete example of an I-D with this problem?  I don't ever
> recall a time when the grant of rights to the IETF had a time limit.
They dont - and this is the problem. It means that there is no revision 
control in the license and NO ONE HAS TO USE OR IMPLEMENT ANY SPECIFIC 
SET OF SERVICES.  It also means that there is no way to pull anything - 
even stolen or unauthorized materials once licensed.

Todd
>
> R's,
> John
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2437/5267 - Release Date: 09/13/12
>
>


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


From tglassey@earthlink.net  Fri Sep 14 07:24:22 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 803AC21F84A2 for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 07:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.475
X-Spam-Level: 
X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HQl6l-Z7wi6Y for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 07:24:21 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id B877C21F846F for <ietf@ietf.org>; Fri, 14 Sep 2012 07:24:21 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=kh0wBbE2G3KShDqTpfzxyIHR4r8S8PuMYWp0qQtX8KYKRCiSipK3SWv6Dhfs+Xtz; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TCWof-0007Vv-4U for ietf@ietf.org; Fri, 14 Sep 2012 10:24:21 -0400
Message-ID: <50533E0C.3030009@earthlink.net>
Date: Fri, 14 Sep 2012 07:24:12 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120914034036.2211.qmail@joyce.lan> <5052B148.9030803@isi.edu>
In-Reply-To: <5052B148.9030803@isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79c2a049ca9177bcaad0a8d765ba42d324350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2012 14:24:22 -0000

On 9/13/2012 9:23 PM, Joe Touch wrote:
> There were times when there were no rights granted explicitly, at 
> least. I indicated the three ranges in a previous mail.
>
> Joe
>
> On 9/13/2012 8:40 PM, John Levine wrote:
>>>> I'm not sure I understand this analogy.  Are you saying that there are
>>>> IPR issues related to making expired drafts available?
>>>
>>> Yes. Depends on the IDs, when they were authored, and which version of
>>> the boilerplate they contain.
>>
>> Can you give a concrete example of an I-D with this problem?  I don't 
>> ever
>> recall a time when the grant of rights to the IETF had a time limit.

For instance - how do you deal with an ID which was originally published 
under one set of IP rights and another later one - or a derivative work 
which is published under a separate set of rights - which functionally 
contravenes or sets aside those original rights authorizations?

This is a serious issue.

Todd
>>
>> R's,
>> John
>>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2437/5267 - Release Date: 09/13/12
>
>


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


From tglassey@earthlink.net  Fri Sep 14 07:36:49 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E99AB21F851E for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 07:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qg32CS92+LXq for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 07:36:49 -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 D126221F851C for <ietf@ietf.org>; Fri, 14 Sep 2012 07:36:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=KaMeTyO5tzoHzjtdosMJqYKBV+lqk3oC3/WCSMtabGFuEytyKcKQpJJMtLUijOR2; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TCX0i-0006XW-6f for ietf@ietf.org; Fri, 14 Sep 2012 10:36:48 -0400
Message-ID: <505340F7.6010708@earthlink.net>
Date: Fri, 14 Sep 2012 07:36:39 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120914051004.9A16F1A224@ld9781.wdf.sap.corp> <5052C21E.4030408@isi.edu>
In-Reply-To: <5052C21E.4030408@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79638a7ef86377b0a13738586d1487c207350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2012 14:36:50 -0000

On 9/13/2012 10:35 PM, Joe Touch wrote:
> Note well, as you noted well, does not go back to the beginning of all 
> IDs.
>
> I.e., this is a tangled mess of different copyrights, different note 
> wells, etc., and it's not as simple as "it's the IETF's right" to do 
> anything except - maybe - going forward with a new copyright statement 
> for IDs.
>
>
>
> Joe
>
> On 9/13/2012 10:10 PM, Martin Rex wrote:
>>
I think Joe is right here. What the real issue is is simply that you 
have no actual way of proving #7 and this process is so bad it fails to 
meet the basic IP Licensing Process Rules that *** ALL *** commercial 
and academic providers are tied to in the real world so this is more of 
the IETF's actions  about its ability to create RIGHTS in a legal sense 
for anyone to anything it cannot formally prove it has legal power of 
attorney over.

If you dont own it - granting a third part rights to something over an 
electronic transport is actually a criminal act AFAIK.

Todd
>>
>>    10.3.1.  All Contributions
>>
>>     7. The contributor represents that there are no limits to the
>>        contributor's ability to make the grants acknowledgments and
>>        agreements above that are reasonably and personally known to the
>>        contributor.
>>
>>        By ratifying this description of the IETF process the Internet
>>        Society warrants that it will not inhibit the traditional open 
>> and
>> *>    free access to IETF documents for which license and right have
>> *>    been assigned according to the procedures set forth in this
>> *>    section, including Internet-Drafts and RFCs. This warrant is
>> *>    perpetual and will not be revoked by the Internet Society or its
>> *>    successors or assigns.

>>
>>
>> So which specific part of "including Internet-Drafts and RFCs"
>> and "This warrent is perpetual" caused your impression that
>> there was a time-limit on an I-D contribution?
>>
>> -Martin
>>
>>
>> btw. rfc2026 10.3.1 (2) looks like an explicit non-policy for 
>> dissemmination
>> or termination of dissemination to me:
>>
>>     2. The contributor acknowledges that the ISOC and IETF have no duty
>>        to publish or otherwise use or disseminate any contribution.
>>
>>
>> I would be OK with a single person from (IESG member or IETF Chair)
>> quickly decides about suspending dissemination of a document based on
>> personal judgement and that the IESG wiggles out by themselves an
>> informal procedure (rather than a formal policy) for safeguarding
>> the process (from bias and abuse).  This cuts into their time budget
>> and seems to not be a concerningly frequent occurence to spend
>> much polish on it at this point.
>>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2437/5267 - Release Date: 09/13/12
>
>


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


From ajs@anvilwalrusden.com  Fri Sep 14 07:38:41 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AA6221F850D for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 07:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.595
X-Spam-Level: 
X-Spam-Status: No, score=-0.595 tagged_above=-999 required=5 tests=[AWL=0.245,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2MMu+8ynwOh for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 07:38:40 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id BDDFC21F84FA for <ietf@ietf.org>; Fri, 14 Sep 2012 07:38:40 -0700 (PDT)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 9948E8A031 for <ietf@ietf.org>; Fri, 14 Sep 2012 14:38:39 +0000 (UTC)
Date: Fri, 14 Sep 2012 10:38:37 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Message-ID: <20120914143837.GC91272@mx1.yitter.info>
References: <20120914034036.2211.qmail@joyce.lan> <5052B148.9030803@isi.edu> <50533E0C.3030009@earthlink.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50533E0C.3030009@earthlink.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, 14 Sep 2012 14:38:41 -0000

On Fri, Sep 14, 2012 at 07:24:12AM -0700, tglassey wrote:
> 
> For instance - how do you deal with an ID which was originally
> published under one set of IP rights and another later one - or a
> derivative work which is published under a separate set of rights -
> which functionally contravenes or sets aside those original rights
> authorizations?
> 
> This is a serious issue.

Indeed, it is, and if anybody would provide examples where we've had
this problem, I would be standing in line to argue that indeed we need
to make a policy and write stuff down.

Instead, the best anyone comes up with is (1) artificial examples of
stuff that might happen someday maybe if someone does something wrong
and (2) one-off cases that are incredibly tricky anyway.

In response to (1), I say this is a problem we don't have.  We have a
poor track record with protocols for which there is no obvious
immediate need (indeed, even when there's an obvious immediate need,
we often screw it up).  Why would policy be different?

In response to (2), I say that hard cases make bad law.  They're all
going to be exceptions anyway.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sob@harvard.edu  Fri Sep 14 08:22:04 2012
Return-Path: <sob@harvard.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 0EBA721F84F3 for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 08:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.399
X-Spam-Level: 
X-Spam-Status: No, score=-104.399 tagged_above=-999 required=5 tests=[AWL=1.200, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xjqozFyNCaQ for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 08:21:54 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 40C8721F8514 for <ietf@ietf.org>; Fri, 14 Sep 2012 08:21:53 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000004.university.harvard.edu [10.35.202.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id CB8011F7064 for <ietf@ietf.org>; Fri, 14 Sep 2012 11:21:51 -0400 (EDT)
Received: from ENTWHUBT0000002.university.harvard.edu (192.168.36.23) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 14 Sep 2012 11:21:45 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.142]) by entwhubt0000002.university.harvard.edu ([192.168.36.46]) with mapi id 14.01.0355.002; Fri, 14 Sep 2012 11:21:51 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Topic: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Index: AQHNkoyqOWR+HYLpYEu2VliANb8+dw==
Date: Fri, 14 Sep 2012 15:21:51 +0000
Message-ID: <4A0FA4FB-FB1F-4B77-921C-2A3E557FBA3B@harvard.edu>
References: <20120914051004.9A16F1A224@ld9781.wdf.sap.corp> <5052C21E.4030408@isi.edu>
In-Reply-To: <5052C21E.4030408@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.248.127.162]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8D9387B08BF406459A570B15AFFDA637@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2012 15:22:04 -0000

I don't think that the Note Well note has much to do with what Joe started =
talking about

we have had this discussion before

quite a few years ago (pre tools) I suggested moving "expired" IDs to an "e=
xpired IDs" directory
rather than removing them from the IETF public repository as well as postin=
g all the old
expired IDs in the same directory (changing only the filename to prepend "e=
xpired-")

seemed like a good idea to me & to many other people, for the reasons peopl=
e find the tools ID archive
useful & the IESG at the time said to move ahead

Steve Coya started the (long) process f pulling the old IDs from backup tap=
es=20

as he was finishing that process a new IESG was seated and the new IESG was=
 not as in=20
favor of the idea and wanted a fuller mailing list discussion (there had be=
en a short
discussion when I proposed the idea)

there were a few people (Joe was one) that felt that IDs were published und=
er the rights implied
in rfc 2026, which said that IDs expired, and, thus, the IETF did to have t=
he right to not remove them
(there fact that other repositories existed did not change the IETF's right=
s in their opinion - in at least
one case someone (I think Bill Manning) sent letters to some of those archi=
ves asking that their=20
ID be removed)

with support from the then IETF lawyer, I suggested that there be a way for=
 a ID author to
request that their ID be removed from the expired IDs directory but that id=
ea did not carry the
day and the expired IDs directory idea died

then, at some later point, the tools function showed up - I do not think I =
was still on the=20
IESG at that point so I do not know if the IESG discussed the question

I think this is a very useful service (for history of how the technology ev=
olved=20
and for prior art searches in patent cases) and think that pretending that =
anything=20
published on the Internet ever quite goes away is not realistic.

Scott



On Sep 14, 2012, at 1:35 AM, Joe Touch <touch@isi.edu> wrote:

> Note well, as you noted well, does not go back to the beginning of all ID=
s.


From sm@resistor.net  Fri Sep 14 16:22:32 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0349321F84A5 for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 16:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l5S58qtGKJfk for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 16:22:31 -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 4C8E521F84A0 for <ietf@ietf.org>; Fri, 14 Sep 2012 16:22:31 -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 q8ENMOrl000765 for <ietf@ietf.org>; Fri, 14 Sep 2012 16:22:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1347664949; bh=3FZT2ZZSF19JWV3MDk3kVVUl8fWEIcwrPRjdiRt/Q98=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=lzpc6uOj0Bd6qu02an/drP7kyhUC4Kmh8YYVCE4KG2zhOETP05eqbdALz5fRbLAU7 g+9+gnViJwx63ApsCmiRajyE3jOdiZH3XoIPcUXCbGQki+RwCdheZUYujOGlDgZXue Jp2RQxfhq0peCMgpm95icM7t1Z9xbrC+2nlKIhpk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1347664949; i=@resistor.net; bh=3FZT2ZZSF19JWV3MDk3kVVUl8fWEIcwrPRjdiRt/Q98=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=dzY+OUT3x66psiy3FApayWAYZauI8IiEGGHMYpEY7f3seUmRlQ9+vHXEcSIlgI9gp buzo3kCIeRlQBdv0yypJLD3E2cVDjQpdIUoap1IuffWPPzJaAEFWPHRav6iake/Ba2 zXidK07dnqAjHefizWD4+C0qWnnpasPx2N7qjXuQ=
Message-Id: <6.2.5.6.2.20120914153648.09f87700@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 14 Sep 2012 16:20:56 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-snell-http-prefer-14.txt> (Prefer Header for HTTP) to Proposed Standard
In-Reply-To: <20120914184457.16683.33382.idtracker@ietfa.amsl.com>
References: <20120914184457.16683.33382.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Sep 2012 23:22:32 -0000

At 11:44 14-09-2012, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Prefer Header for HTTP'
>   <draft-snell-http-prefer-14.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2012-10-12. Exceptionally, comments may be

I took a quick look at the draft.

In the Abstract:

   "This specification defines an HTTP header field that can be used by a
    client to request that certain behaviors be implemented by a server
    while processing a request."

The "request that certain behaviors be implemented by a server" 
sounds odd.  The "employ" from the Introduction section is a better fit.

In Section 2:

   "A server that does not recognize or is unable to comply with
    particular preference tokens in the Prefer header field of a request
    MUST ignore those tokens and MUST NOT stop processing or signal an
    error."

Suggested text:

    A server that does not recognize or is unable to comply with
    particular preference tokens in the Prefer header field of a request
    MUST ignore those tokens and continue processing instead of signalling
    an error.

In Section 4.1:

   "Registration requests consist of the completed registration template
    below, typically published in an RFC or Open Standard (in the sense
    described by Section 7 of [RFC2026])."

Is it necessary to get into the details of the Specification Required 
policy?  "Permanent and readily available public specification" would 
be better than the reference to RFC 2026.

BTW, the RFC 5023 informative reference is missing.

Regards,
-sm





From barryleiba.mailing.lists@gmail.com  Fri Sep 14 19:14:01 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98DFB21F852D for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 19:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.957
X-Spam-Level: 
X-Spam-Status: No, score=-102.957 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WRPCyZtEZjTk for <ietf@ietfa.amsl.com>; Fri, 14 Sep 2012 19:13:58 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 44C3C21F8528 for <ietf@ietf.org>; Fri, 14 Sep 2012 19:13:58 -0700 (PDT)
Received: by lahm15 with SMTP id m15so3309556lah.31 for <ietf@ietf.org>; Fri, 14 Sep 2012 19:13:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=8GFuDdWeql/KCcPyXTExbGpsP4WVVGkipZWivhCR7Hk=; b=Dt/n9qO3Oja3CR2BDbiedLj7SNs3Cnrw3HSmmwYId2wR35CkfRuk5tLY1oJZ6n079q KPp0OV6qAauHUMPHDxDBSpsrp0BRhb0yAQLvECp/7G+vVvOdeW9MKztODYmjNVNtQKGT RSUBOGbVCGVjKc29IuTkCgEObdm+vkopRsR8dp3CZux/y0nkvNWOkqa4AdrIWuf2rVwz pFwihBzU0sBg2XfBA+zn3ISxLqC0b1e/Cy//MJAUQeRL/o3oSzLd2Xq98weL+F2PJuW6 /ChQbxFzlUN+OIPR95ucUb8cmrSrlX9YCaucuAKeEEy+dQjfoaA/ax97jubTHIbksYta kvdg==
MIME-Version: 1.0
Received: by 10.152.122.9 with SMTP id lo9mr4092019lab.41.1347675237002; Fri, 14 Sep 2012 19:13:57 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.91.33 with HTTP; Fri, 14 Sep 2012 19:13:56 -0700 (PDT)
Date: Fri, 14 Sep 2012 22:13:56 -0400
X-Google-Sender-Auth: XF_hpWctcrQAO6J7MaOewyrCTU8
Message-ID: <CAC4RtVBWp6WM7pUkjP_mBQGUucczC7MdG2k8-jbnDZSmWXPvDQ@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-03.txt
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Sep 2012 02:14:01 -0000

Russ has asked that SM and I pare down the proposal for a 3777 update,
back down to my original one that just adds the IAOC and the
ex-officio roles to the exclusion list.  After talking with SM, I have
re-posted a slightly edited version of that original proposal (below),
and we have decided that either SM or SM and I will re-propose the
other changes at a later time.

For now, the -03 version is just the original proposal: add the IAOC
and the two IAB ex-officio positions (IAB Executive Director and IRTF
Chair) to the current list of who RFC 3777 excludes from eligibility
to volunteer for NomCom.

Further comments on this limited proposal are welcome and encouraged.

Barry (and SM)

On Fri, Sep 14, 2012 at 12:57 PM,  <internet-drafts@ietf.org> wrote:
>
> A new version of I-D, draft-leiba-3777upd-eligibility-03.txt
> has been successfully submitted by Barry Leiba and posted to the
> IETF repository.
>
> Filename:        draft-leiba-3777upd-eligibility
> Revision:        03
> Title:           Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership
> Creation date:   2012-09-14
> WG ID:           Individual Submission
> Number of pages: 4
> URL:             http://www.ietf.org/internet-drafts/draft-leiba-3777upd-eligibility-03.txt
> Status:          http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility
> Htmlized:        http://tools.ietf.org/html/draft-leiba-3777upd-eligibility-03
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-leiba-3777upd-eligibility-03
>
> Abstract:
>    RFC 3777 specifies that "sitting members" of the IAB and IESG "may
>    not volunteer to serve on the nominating commitee".  Since that
>    document was written the IAOC was formed, and that body is not
>    covered by RFC 3777.  There is also uncertainty about whether ex-
>    officio members and liaisons are included as "sitting members".  This
>    document clarifies those situations.

From lconroy@insensate.co.uk  Sun Sep 16 06:56:31 2012
Return-Path: <lconroy@insensate.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 DF7FD21F8514 for <ietf@ietfa.amsl.com>; Sun, 16 Sep 2012 06:56:31 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5kskx8enrkf for <ietf@ietfa.amsl.com>; Sun, 16 Sep 2012 06:56:31 -0700 (PDT)
Received: from insensate.co.uk (ghost.insensate.co.uk [213.152.49.121]) by ietfa.amsl.com (Postfix) with ESMTP id B5C4921F84B5 for <ietf@ietf.org>; Sun, 16 Sep 2012 06:56:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTP id E2FE31E7214; Sun, 16 Sep 2012 14:56:27 +0100 (BST)
Received: from insensate.co.uk ([127.0.0.1]) by localhost (psyche.insensate.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vfkXzg2vAc5w; Sun, 16 Sep 2012 14:56:25 +0100 (BST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by insensate.co.uk (Postfix) with ESMTPSA id 4F5C31E7209; Sun, 16 Sep 2012 14:56:25 +0100 (BST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Lawrence Conroy <lconroy@insensate.co.uk>
X-Mailer: Apple Mail (2.1084)
In-Reply-To: <4A0FA4FB-FB1F-4B77-921C-2A3E557FBA3B@harvard.edu>
Date: Sun, 16 Sep 2012 14:56:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFA7205B-EB69-4088-BDC9-8A7762A12133@insensate.co.uk>
References: <20120914051004.9A16F1A224@ld9781.wdf.sap.corp> <5052C21E.4030408@isi.edu> <4A0FA4FB-FB1F-4B77-921C-2A3E557FBA3B@harvard.edu>
To: "Bradner, Scott" <sob@harvard.edu>
Cc: The 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, 16 Sep 2012 13:56:32 -0000

Hi Scott, folks,
 with due deference to Joe Touch & Bill Manning, whenever I have =
created/requested publication of an I-D, it never occurred to me that I =
was actually withdrawing the rights I had signed up to after six months =
(i.e., insisting on removal). That seems a novel reading of the =
boilerplate/2026.

There were times people have had to refresh a draft before it =
disappeared (with precious few changes), just to keep them published.
That always struck me as bonkers, and am roundly happy that/if expired =
drafts don't evaporate with the season.
I can't be alone in this -- these docs may not be current, but having a =
trail of drafts NOT take up gigabytes on [some] people's hard drives is =
good.

As for Scott's comments/efforts to have an expired-draft directory -- =
amen to that, for both reasons.
(I hadn't realised that Steve had just about done this; good chap, who's =
sorely missed).

It is VERY useful to be able to search through drafts to see how we got =
here, AND to see things that were explored and abandoned.
It's also useful to be able to check when things were published relative =
to applications; having that information potentially go away was/is a =
nuisance.

IMHO:
If authors insist, OK -- the expired draft is toast (although it being =
replaced by a published note that it has been deleted would be good).
Otherwise, why would/should the IESG decide to remove a document?

... which is a long way of saying: +1

all the best,
  Lawrence



On 14 Sep 2012, at 16:21, Bradner, Scott wrote:
> I don't think that the Note Well note has much to do with what Joe =
started talking about
>=20
> we have had this discussion before
>=20
> quite a few years ago (pre tools) I suggested moving "expired" IDs to =
an "expired IDs" directory
> rather than removing them from the IETF public repository as well as =
posting all the old
> expired IDs in the same directory (changing only the filename to =
prepend "expired-")
>=20
> seemed like a good idea to me & to many other people, for the reasons =
people find the tools ID archive
> useful & the IESG at the time said to move ahead
>=20
> Steve Coya started the (long) process f pulling the old IDs from =
backup tapes=20
>=20
> as he was finishing that process a new IESG was seated and the new =
IESG was not as in=20
> favor of the idea and wanted a fuller mailing list discussion (there =
had been a short
> discussion when I proposed the idea)
>=20
> there were a few people (Joe was one) that felt that IDs were =
published under the rights implied
> in rfc 2026, which said that IDs expired, and, thus, the IETF did to =
have the right to not remove them
> (there fact that other repositories existed did not change the IETF's =
rights in their opinion - in at least
> one case someone (I think Bill Manning) sent letters to some of those =
archives asking that their=20
> ID be removed)
>=20
> with support from the then IETF lawyer, I suggested that there be a =
way for a ID author to
> request that their ID be removed from the expired IDs directory but =
that idea did not carry the
> day and the expired IDs directory idea died
>=20
> then, at some later point, the tools function showed up - I do not =
think I was still on the=20
> IESG at that point so I do not know if the IESG discussed the question
>=20
> I think this is a very useful service (for history of how the =
technology evolved=20
> and for prior art searches in patent cases) and think that pretending =
that anything=20
> published on the Internet ever quite goes away is not realistic.
>=20
> Scott
>=20
>=20
>=20
> On Sep 14, 2012, at 1:35 AM, Joe Touch <touch@isi.edu> wrote:
>=20
>> Note well, as you noted well, does not go back to the beginning of =
all IDs.
>=20


From tglassey@earthlink.net  Sun Sep 16 07:08:40 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF4D21F8510 for <ietf@ietfa.amsl.com>; Sun, 16 Sep 2012 07:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.506
X-Spam-Level: 
X-Spam-Status: No, score=-3.506 tagged_above=-999 required=5 tests=[AWL=1.093,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Odg1auQj-IPL for <ietf@ietfa.amsl.com>; Sun, 16 Sep 2012 07:08:40 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id DEF6521F850C for <ietf@ietf.org>; Sun, 16 Sep 2012 07:08:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=N+WB0Uqs9/A8+5tYcUfhFhti6W080gPvduF/FnqX9a7NGBWaZUWp9SuDhfpZJmWQ; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TDFWU-0005B9-Qj for ietf@ietf.org; Sun, 16 Sep 2012 10:08:35 -0400
Message-ID: <5055DD60.5060209@earthlink.net>
Date: Sun, 16 Sep 2012 07:08:32 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120914051004.9A16F1A224@ld9781.wdf.sap.corp> <5052C21E.4030408@isi.edu> <4A0FA4FB-FB1F-4B77-921C-2A3E557FBA3B@harvard.edu> <AFA7205B-EB69-4088-BDC9-8A7762A12133@insensate.co.uk>
In-Reply-To: <AFA7205B-EB69-4088-BDC9-8A7762A12133@insensate.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7992e6c21c1a874aaeab41022a99a4057a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Sep 2012 14:08:41 -0000

On 9/16/2012 6:56 AM, Lawrence Conroy wrote:
> Hi Scott, folks,
>   with due deference to Joe Touch & Bill Manning, whenever I have created/requested publication of an I-D, it never occurred to me that I was actually withdrawing the rights I had signed up to after six months (i.e., insisting on removal). That seems a novel reading of the boilerplate/2026.
>
> There were times people have had to refresh a draft before it disappeared (with precious few changes), just to keep them published.
> That always struck me as bonkers, and am roundly happy that/if expired drafts don't evaporate with the season.
> I can't be alone in this -- these docs may not be current, but having a trail of drafts NOT take up gigabytes on [some] people's hard drives is good.
>
> As for Scott's comments/efforts to have an expired-draft directory -- amen to that, for both reasons.
> (I hadn't realised that Steve had just about done this; good chap, who's sorely missed).
>
> It is VERY useful to be able to search through drafts to see how we got here, AND to see things that were explored and abandoned.
> It's also useful to be able to check when things were published relative to applications; having that information potentially go away was/is a nuisance.
>
> IMHO:
> If authors insist, OK -- the expired draft is toast (although it being replaced by a published note that it has been deleted would be good).
> Otherwise, why would/should the IESG decide to remove a document?
>
> ... which is a long way of saying: +1
>
> all the best,
>    Lawrence
>
>
>
> On 14 Sep 2012, at 16:21, Bradner, Scott wrote:
>> I don't think that the Note Well note has much to do with what Joe started talking about
>>
>> we have had this discussion before
>>
>> quite a few years ago (pre tools) I suggested moving "expired" IDs to an "expired IDs" directory
>> rather than removing them from the IETF public repository as well as posting all the old
>> expired IDs in the same directory (changing only the filename to prepend "expired-")
>>
>> seemed like a good idea to me & to many other people, for the reasons people find the tools ID archive
>> useful & the IESG at the time said to move ahead
>>
>> Steve Coya started the (long) process f pulling the old IDs from backup tapes
>>
>> as he was finishing that process a new IESG was seated and the new IESG was not as in
>> favor of the idea and wanted a fuller mailing list discussion (there had been a short
>> discussion when I proposed the idea)
>>
>> there were a few people (Joe was one) that felt that IDs were published under the rights implied
>> in rfc 2026, which said that IDs expired, and, thus, the IETF did to have the right to not remove them
>> (there fact that other repositories existed did not change the IETF's rights in their opinion - in at least
>> one case someone (I think Bill Manning) sent letters to some of those archives asking that their
>> ID be removed)
>>
>> with support from the then IETF lawyer, I suggested that there be a way for a ID author to
>> request that their ID be removed from the expired IDs directory but that idea did not carry the
>> day and the expired IDs directory idea died
>>
>> then, at some later point, the tools function showed up - I do not think I was still on the
>> IESG at that point so I do not know if the IESG discussed the question
>>
>> I think this is a very useful service (for history of how the technology evolved
>> and for prior art searches in patent cases) and think that pretending that anything
>> published on the Internet ever quite goes away is not realistic.
>>
>> Scott
The issue isnt whether the publications are available in an archive 
taking up space but whether the IP licensing rights to the content of 
that draft are persistent through a revision process or not. i.e. 
whether that right evaporates with the new publications then anyone 
implementing the protocol must also upgrade as well to stay in proper IP 
licensing state  or it persists.

Further if an IETF Draft is expired and there are support issues (from a 
contractual basis between parties who sold code implemented on those 
standards to a relying party) what happens to that contract?

One of the things this group has done is to ignore the practices of the 
real-world and its time this was addressed.  Code implemented from these 
publication standards is tied to the flow and protocol practices defined 
therein and its a real issue.

Todd


>>
>>
>> On Sep 14, 2012, at 1:35 AM, Joe Touch <touch@isi.edu> wrote:
>>
>>> Note well, as you noted well, does not go back to the beginning of all IDs.
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2437/5270 - Release Date: 09/15/12
>
>
>


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


From tglassey@earthlink.net  Sun Sep 16 07:11:14 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C9A721F8510 for <ietf@ietfa.amsl.com>; Sun, 16 Sep 2012 07:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.627
X-Spam-Level: 
X-Spam-Status: No, score=-2.627 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9sjdmoWReR6 for <ietf@ietfa.amsl.com>; Sun, 16 Sep 2012 07:11:13 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id A7A0321F850C for <ietf@ietf.org>; Sun, 16 Sep 2012 07:11:13 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=kngNcLJsNUWfVMUSxKwlPlkJoyLh1ltr0Xt6ZQI3YCLT23cHhJS9E6k7tDr5DMIg; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TDFZ3-0004O2-0n for ietf@ietf.org; Sun, 16 Sep 2012 10:11:13 -0400
Message-ID: <5055DDFF.9000108@earthlink.net>
Date: Sun, 16 Sep 2012 07:11:11 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120914034036.2211.qmail@joyce.lan> <5052B148.9030803@isi.edu> <50533E0C.3030009@earthlink.net> <20120914143837.GC91272@mx1.yitter.info>
In-Reply-To: <20120914143837.GC91272@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79ea9c18cb69192e708173c2a89c46b4c2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Sep 2012 14:11:14 -0000

On 9/14/2012 7:38 AM, Andrew Sullivan wrote:
> On Fri, Sep 14, 2012 at 07:24:12AM -0700, tglassey wrote:
>> For instance - how do you deal with an ID which was originally
>> published under one set of IP rights and another later one - or a
>> derivative work which is published under a separate set of rights -
>> which functionally contravenes or sets aside those original rights
>> authorizations?
>>
>> This is a serious issue.
> Indeed, it is, and if anybody would provide examples where we've had
> this problem, I would be standing in line to argue that indeed we need
> to make a policy and write stuff down.
I want to clarify what you are asking for in this statement - what 
specifically would satisfy this request here?

Todd
>
> Instead, the best anyone comes up with is (1) artificial examples of
> stuff that might happen someday maybe if someone does something wrong
> and (2) one-off cases that are incredibly tricky anyway.
>
> In response to (1), I say this is a problem we don't have.  We have a
> poor track record with protocols for which there is no obvious
> immediate need (indeed, even when there's an obvious immediate need,
> we often screw it up).  Why would policy be different?
>
> In response to (2), I say that hard cases make bad law.  They're all
> going to be exceptions anyway.
>
> A
>


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


From housley@vigilsec.com  Tue Sep 18 07:50:11 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9CA321F84A1 for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 07:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.469
X-Spam-Level: 
X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6IPTBe+ZT5Ss for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 07:50:07 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 034F621F848B for <ietf@ietf.org>; Tue, 18 Sep 2012 07:50:07 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 3F2409A4005; Tue, 18 Sep 2012 10:50:24 -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 LHZtAhU26L9b; Tue, 18 Sep 2012 10:49:49 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 9DC889A4004; Tue, 18 Sep 2012 10:50:21 -0400 (EDT)
Subject: Re: copyright notices in RFC 6716
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <87a9wuropq.fsf@latte.josefsson.org>
Date: Tue, 18 Sep 2012 10:50:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A34B4161-4C39-4A3A-BDDA-207448BD985B@vigilsec.com>
References: <87a9wuropq.fsf@latte.josefsson.org>
To: Simon Josefsson <simon@josefsson.org>
X-Mailer: Apple Mail (2.1084)
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, 18 Sep 2012 14:50:11 -0000

Simon:

The authors wanted to grant additional rights beyond those that are =
granted by the TLP.  They indicated those rights in Section 10 of the =
internet-Draft.  This was challenged during WG Last Call, and it was =
challenged during IETF Last Call.  In each case, the authors make their =
desire clear and the community supported them.  For this reason the IETF =
Trust granted the usual TLP rights and the additional rights as well.

Russ


On Sep 13, 2012, at 10:18 AM, Simon Josefsson wrote:

> All,
>=20
> I noticed that the recent RFC 6716 contains some reference code that
> contain the copyright and licenses notice reproduced below.  The IETF
> TLP [1] mandates a certain form of copyright notices and the TLP does
> not, as far as I can see, permit varying the boiler plate in any way.
> Note that both companies and organisations are mentioned in the
> copyright notice in RFC 6716, besides individuals.
>=20
> Does this indicate a policy change, a mistake with that document, or
> something else?
>=20
> Btw, kudos to the RFC 6716 authors for shipping reference code!  I =
hope
> this will establish a best practice for standards in the future.
>=20
> /Simon
>=20
> [1] =
http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-20091228.ht=
m
>=20
> Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
>                    Jean-Marc Valin, Timothy B. Terriberry,
>                    CSIRO, Gregory Maxwell, Mark Borgerding,
>                    Erik de Castro Lopo. All rights reserved.
>=20
> This file is extracted from RFC6716. Please see that RFC for =
additional
> information.
>=20
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions
> are met:
>=20
> - Redistributions of source code must retain the above copyright
> notice, this list of conditions and the following disclaimer.
>=20
> - Redistributions in binary form must reproduce the above copyright
> notice, this list of conditions and the following disclaimer in the
> documentation and/or other materials provided with the distribution.
>=20
> - Neither the name of Internet Society, IETF or IETF Trust, nor the
> names of specific contributors, may be used to endorse or promote
> products derived from this software without specific prior written
> permission.
>=20
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT =
OWNER
> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, =
SPECIAL,
> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


From david.black@emc.com  Mon Sep 17 16:53:49 2012
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 ECD2921E809E; Mon, 17 Sep 2012 16:53:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sQvhnJr6R2B5; Mon, 17 Sep 2012 16:53:49 -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 D0AE821E804A; Mon, 17 Sep 2012 16:53:48 -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 q8HNrgpa021273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Sep 2012 19:53:44 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 17 Sep 2012 19:53:28 -0400
Received: from mxhub09.corp.emc.com (mxhub09.corp.emc.com [10.254.92.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8HNrR6P018901; Mon, 17 Sep 2012 19:53:27 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub09.corp.emc.com ([10.254.92.104]) with mapi; Mon, 17 Sep 2012 19:53:28 -0400
From: "Black, David" <david.black@emc.com>
To: "glenzorn@gmail.com" <glenzorn@gmail.com>, "lionel.morand@orange.com" <lionel.morand@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 17 Sep 2012 19:53:10 -0400
Subject: Gen-ART review of draft-ietf-dime-rfc4005bis-11
Thread-Topic: Gen-ART review of draft-ietf-dime-rfc4005bis-11
Thread-Index: Ac2VL5e17q8ZkxfMT6qPIiZvpDm54w==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-puzzleid: {CC92EE8F-E26A-46B9-9CA3-81DF9893E330}
x-cr-hashedpuzzle: CT9C Ev4n J0Jv PZY7 PoOn P6Gt Udj6 WGZf e2Mc mlNc 461k 5bD3 AB+piw== ACGfjQ== ACJGGg== AEavpg==; 8; YgBjAGwAYQBpAHMAZQBAAGMAaQBzAGMAbwAuAGMAbwBtADsAZABpAG0AZQAtAGMAaABhAGkAcgBzAEAAdABvAG8AbABzAC4AaQBlAHQAZgAuAG8AcgBnADsAZABpAG0AZQBAAGkAZQB0AGYALgBvAHIAZwA7AGQAcgBhAGYAdAAtAGkAZQB0AGYALQBkAGkAbQBlAC0AcgBmAGMANAAwADAANQBiAGkAcwBAAHQAbwBvAGwAcwAuAGkAZQB0AGYALgBvAHIAZwA7AGcAZQBuAC0AYQByAHQAQABpAGUAdABmAC4AbwByAGcAOwBnAGwAZQBuAHoAbwByAG4AQABnAG0AYQBpAGwALgBjAG8AbQA7AGkAZQB0AGYAQABpAGUAdABmAC4AbwByAGcAOwBsAGkAbwBuAGUAbAAuAG0AbwByAGEAbgBkAEAAbwByAGEAbgBnAGUALgBjAG8AbQA=; Sosha1_v1; 7; {CC92EE8F-E26A-46B9-9CA3-81DF9893E330}; ZABhAHYAaQBkAC4AYgBsAGEAYwBrAEAAZQBtAGMALgBjAG8AbQA=; Mon, 17 Sep 2012 23:53:10 GMT; RwBlAG4ALQBBAFIAVAAgAHIAZQB2AGkAZQB3ACAAbwBmACAAZAByAGEAZgB0AC0AaQBlAHQAZgAtAGQAaQBtAGUALQByAGYAYwA0ADAAMAA1AGIAaQBzAC0AMQAxAA==
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: Tue, 18 Sep 2012 11:32:06 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dime-rfc4005bis@tools.ietf.org" <draft-ietf-dime-rfc4005bis@tools.ietf.org>, "Black, David" <david.black@emc.com>, "dime@ietf.org" <dime@ietf.org>, "dime-chairs@tools.ietf.org" <dime-chairs@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, 17 Sep 2012 23:53: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-dime-rfc4005bis-11
Reviewer: David L. Black
Review Date: September 17, 2012
IETF LC End Date: September 18, 2012
IESG Telechat date: (if known)

Summary:

This draft is on the right track but has open issues, described in the revi=
ew.

This draft is part of a set of drafts that updates the DIAMETER protocol;
this draft specifies the application of DIAMETER to AAA for network access.
The draft is heavily based on RFC 4005, which it obsoletes, and requires
significant DIAMETER familiarity (including familiarity with its companion
drafts, starting with the rfc3588bis draft) for complete understanding.

The draft is in good shape and reads well.  I found one major open issue,
a few minor issues, and several nits.

Major issues:

This draft makes significant use of UTF-8 in its formats (some subsections
of sections 4.2, 4.4 and 4.5) for strings that are intended to be compared
for equality or processed by protocol participants, but does not contain
considerations for Unicode processing that are sufficient to support this
usage.  Examples of UTF-8 usage in this draft include:

- 4.2.5 and 4.2.6: The NAS server may perform authorization based on the
	Called-Station-Id and Calling-Station-Id AVPs under some
	circumstances.
- 4.4.3: The Callback-Id AVP is intended to be interpreted by the NAS.

All use of UTF-8 in this draft relies upon the specification of the
UTF8String format in the rfc3588bis draft.  That specification is
insufficient to support the usage in the above examples, and there are
no Unicode considerations in this draft. Even binary comparison of
Unicode strings for equality generally requires specification of
string preparation (e.g., normalization) in order for string comparison
to work as expected.

The variety of Unicode strings in this draft makes it important to lay
out the Unicode requirements and considerations for each AVP.  I see
at least 5 classes of possible Unicode requirements/considerations:

1) String preparation so that tests for equality work as expected.
	This may suffice for the Called-Station-ID AVP (4.2.5) and
	Calling-Station-ID AVP (4.2.6) if the internal structure of
	those strings is not used in authorization.
2) Detailed string format for a string that is processed by a protocol=09
	participant, e.g., the Callback-ID AVP (4.4.3).
3) Restriction of the string to ASCII-only, e.g., as already stated
	for the Framed-Route AVP (4.4.10.5.3).
4) Specification that the string is for display to human users only,
	e.g., as already stated for the Reply-Message AVP (4.2.9).
5) Statement that the string contains an FQDN, as stated for one
	case of the Tunnel-Client-Endpoint AVP in 4.5.4.  That specific
	statement is incomplete, as it needs to be accompanied by a
	normative reference to a document that specifies the format
	of internationalized domain names, and probably needs to also
	state which types of labels (e.g., A-label, U-label) are allowed.

Every use of UTF8String in this draft needs to be checked, and most of
them are likely to need some attention. The ongoing work in the precis
WG may help with some of this, and I would suggest talking to the APP
ADs, especially Pete Resnick (hi Pete) before embarking on significant
work in this area in order to avoid wasted or duplicated efforts.

Minor Issues:

[1] End of Section 2 on p.8:

   As a result,
   service cannot be started as a result of a response to an
   authorization-only request without introducing a significant security
   vulnerability.

Please explain what to do about this - a simple rewrite with a
"SHOULD NOT" would suffice, e.g.:

   As a result,
   service SHOULD NOT be started as a result of a response to an
   authorization-only request because that may introduce a significant
   security vulnerability.

This should also be noted in the Security Considerations section.

[2] In the message formats in Section 3, QoS-Filter-Rule is inconsistently
capitalized.  Also the use of QoSFilterRule as the format for the
QoS-Filter-Rule AVP in Section 4.1.1 is potentially confusing.  Please
add a sentence in 4.1.1 to say that QoSFilterRule is the format for the
QoS-Filter-Rule AVP.

[3] Section 4.2.1.  In this and the other AVP Flag Rules tables, please
explain what the values in the MUST and MUST NOT columns mean.

[4] Based on this text in 4.4.9:

   The use of this AVP is NOT RECOMMENDED; the AVPs defined by Korhonen,
   et al. [RFC5777] SHOULD be used instead.

I would have expected RFC5777 to be a Normative Reference, not an
Informative Reference.

Nits/editorial comments:

After the command table in Section 3 and other similar tables, please add a
sentence to say that the -Request and -Answer commands in each similarly-na=
med
command pair are distinguished by the value of the 'R' bit in the Command
Flags field of the command.  This is already stated in the command definiti=
ons,
but the sentence should be added after the table for clarity because each c=
ommand
pair shares a Command Code.

idnits 2.12.13 found a few potential nits:

  =3D=3D There are 7 instances of lines with non-RFC5735-compliant IPv4 add=
resses
     in the document.  If these are example addresses, they should be chang=
ed.

That can probably be ignored, as these instances are likely generated by
text such as cross-references to Section 4.4.10.1

  =3D=3D Missing Reference: 'BASE' is mentioned on line 219, but not define=
d

That's definitely a problem.  Was [I-D.ietf-dime-rfc3588bis] intended?

  -- Possible downref: Non-RFC (?) normative reference: ref. 'ANITypes'

That reference would be:

	[ANITypes]            NANPA Number Resource Info, "ANI
                            Assignments", <http://www.nanpa.com/
                            number_resource_info/
                            ani_ii_assignments.html>.

Is that reference sufficiently stable (e.g., IANA-class or better managemen=
t)?
My guess is that it is sufficiently stable, but I'm not the expert.

  -- Obsolete informational reference (is this intentional?): RFC 1334
     (Obsoleted by RFC 1994)

That reference may be intentional, as it's cited exactly once:

263	   PAP (Password Authentication Protocol)
264	      A deprecated PPP authentication process, but often used for
265	      backward compatibility [RFC1334].


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 simon@josefsson.org  Tue Sep 18 14:33:52 2012
Return-Path: <simon@josefsson.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 51B8811E80A6 for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 14:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.822
X-Spam-Level: 
X-Spam-Status: No, score=-99.822 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xanG3oXZzX7V for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 14:33:45 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id 22AFB11E80A5 for <ietf@ietf.org>; Tue, 18 Sep 2012 14:33:44 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q8ILXZC8011107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 18 Sep 2012 23:33:36 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: copyright notices in RFC 6716
References: <87a9wuropq.fsf@latte.josefsson.org> <A34B4161-4C39-4A3A-BDDA-207448BD985B@vigilsec.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120918:ietf@ietf.org::0pX92gMxCp0BfLq3:uRto
X-Hashcash: 1:22:120918:housley@vigilsec.com::0zdl14aWBDnyGCrj:+V90
Date: Tue, 18 Sep 2012 23:33:35 +0200
In-Reply-To: <A34B4161-4C39-4A3A-BDDA-207448BD985B@vigilsec.com> (Russ Housley's message of "Tue, 18 Sep 2012 10:50:00 -0400")
Message-ID: <87k3vrj9sg.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
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, 18 Sep 2012 21:33:52 -0000

Russ,

I can't seem to align what you say with the document content.  The
rights granted by the license text in the document (quoted below)
appears to me be identical to the TLP except that the copyright header
also includes non-authors.  Is this what you refer to with granting
additional rights?

My concern is not about rights granted (they appear to follow the TLD),
but with the form of the copyright header that deviates from the TLD
boilerplate.

What puzzles me is that the explanation that I have received earlier is
that variations beyond what the TLP demand is not permitted even if
there is community support for the content of a particular document.
I'm happy if this is now the policy, as it would allow including more
source code into RFCs.

/Simon

Russ Housley <housley@vigilsec.com> writes:

> Simon:
>
> The authors wanted to grant additional rights beyond those that are
> granted by the TLP.  They indicated those rights in Section 10 of the
> internet-Draft.  This was challenged during WG Last Call, and it was
> challenged during IETF Last Call.  In each case, the authors make
> their desire clear and the community supported them.  For this reason
> the IETF Trust granted the usual TLP rights and the additional rights
> as well.
>
> Russ
>
>
> On Sep 13, 2012, at 10:18 AM, Simon Josefsson wrote:
>
>> All,
>> 
>> I noticed that the recent RFC 6716 contains some reference code that
>> contain the copyright and licenses notice reproduced below.  The IETF
>> TLP [1] mandates a certain form of copyright notices and the TLP does
>> not, as far as I can see, permit varying the boiler plate in any way.
>> Note that both companies and organisations are mentioned in the
>> copyright notice in RFC 6716, besides individuals.
>> 
>> Does this indicate a policy change, a mistake with that document, or
>> something else?
>> 
>> Btw, kudos to the RFC 6716 authors for shipping reference code!  I hope
>> this will establish a best practice for standards in the future.
>> 
>> /Simon
>> 
>> [1]
>> http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-20091228.htm
>> 
>> Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
>>                    Jean-Marc Valin, Timothy B. Terriberry,
>>                    CSIRO, Gregory Maxwell, Mark Borgerding,
>>                    Erik de Castro Lopo. All rights reserved.
>> 
>> This file is extracted from RFC6716. Please see that RFC for additional
>> information.
>> 
>> Redistribution and use in source and binary forms, with or without
>> modification, are permitted provided that the following conditions
>> are met:
>> 
>> - Redistributions of source code must retain the above copyright
>> notice, this list of conditions and the following disclaimer.
>> 
>> - Redistributions in binary form must reproduce the above copyright
>> notice, this list of conditions and the following disclaimer in the
>> documentation and/or other materials provided with the distribution.
>> 
>> - Neither the name of Internet Society, IETF or IETF Trust, nor the
>> names of specific contributors, may be used to endorse or promote
>> products derived from this software without specific prior written
>> permission.
>> 
>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
>> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
>> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
>> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
>> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
>> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
>> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

From tglassey@earthlink.net  Tue Sep 18 14:47:26 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE7B311E80A6 for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 14:47:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level: 
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2JJGtI2mqni for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 14:47:23 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 2026311E808D for <ietf@ietf.org>; Tue, 18 Sep 2012 14:47:23 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=ocUTkvbsnhD68LA5BHpHzfEyTORtLucdS9nD/7AiCMa/wW2srZCrpRzlkk3XLL8b; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TE5da-0000a8-0h for ietf@ietf.org; Tue, 18 Sep 2012 17:47:22 -0400
Message-ID: <5058EBE8.7000708@earthlink.net>
Date: Tue, 18 Sep 2012 14:47:20 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: copyright notices in RFC 6716
References: <87a9wuropq.fsf@latte.josefsson.org> <A34B4161-4C39-4A3A-BDDA-207448BD985B@vigilsec.com> <87k3vrj9sg.fsf@latte.josefsson.org>
In-Reply-To: <87k3vrj9sg.fsf@latte.josefsson.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79ce0ba19f4a58e530d3aacfa27aef533f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Sep 2012 21:47:27 -0000

On 9/18/2012 2:33 PM, Simon Josefsson wrote:
> Russ,
>
> I can't seem to align what you say with the document content.  The
> rights granted by the license text in the document (quoted below)
> appears to me be identical to the TLP except that the copyright header
> also includes non-authors.  Is this what you refer to with granting
> additional rights?
>
> My concern is not about rights granted (they appear to follow the TLD),
> but with the form of the copyright header that deviates from the TLD
> boilerplate.
Is there from this point forward a requirement for future works in this 
vein to also use the same rights statement? I am curious because of the 
complexity of merging this with other right specific issues.

For instance if ID "A" is published with normal use rights and it is 
expanded in a revision which then increases its rights to some secondary 
set of rights-states and in so doing permanently seems to alter the 
baseline.

What also if ID "A" is published with rights-set #1 and a formal work 
(like those described in the AIA (the America Invents Act) for instance, 
and then this is altered. The issue is how these rights do or do not 
promulgate from ID or RFC revision-to-revision.

Todd//
> What puzzles me is that the explanation that I have received earlier is
> that variations beyond what the TLP demand is not permitted even if
> there is community support for the content of a particular document.
> I'm happy if this is now the policy, as it would allow including more
> source code into RFCs.
>
> /Simon
>
> Russ Housley <housley@vigilsec.com> writes:
>
>> Simon:
>>
>> The authors wanted to grant additional rights beyond those that are
>> granted by the TLP.  They indicated those rights in Section 10 of the
>> internet-Draft.  This was challenged during WG Last Call, and it was
>> challenged during IETF Last Call.  In each case, the authors make
>> their desire clear and the community supported them.  For this reason
>> the IETF Trust granted the usual TLP rights and the additional rights
>> as well.
>>
>> Russ
>>
>>
>> On Sep 13, 2012, at 10:18 AM, Simon Josefsson wrote:
>>
>>> All,
>>>
>>> I noticed that the recent RFC 6716 contains some reference code that
>>> contain the copyright and licenses notice reproduced below.  The IETF
>>> TLP [1] mandates a certain form of copyright notices and the TLP does
>>> not, as far as I can see, permit varying the boiler plate in any way.
>>> Note that both companies and organisations are mentioned in the
>>> copyright notice in RFC 6716, besides individuals.
>>>
>>> Does this indicate a policy change, a mistake with that document, or
>>> something else?
>>>
>>> Btw, kudos to the RFC 6716 authors for shipping reference code!  I hope
>>> this will establish a best practice for standards in the future.
>>>
>>> /Simon
>>>
>>> [1]
>>> http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-20091228.htm
>>>
>>> Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
>>>                     Jean-Marc Valin, Timothy B. Terriberry,
>>>                     CSIRO, Gregory Maxwell, Mark Borgerding,
>>>                     Erik de Castro Lopo. All rights reserved.
>>>
>>> This file is extracted from RFC6716. Please see that RFC for additional
>>> information.
>>>
>>> Redistribution and use in source and binary forms, with or without
>>> modification, are permitted provided that the following conditions
>>> are met:
>>>
>>> - Redistributions of source code must retain the above copyright
>>> notice, this list of conditions and the following disclaimer.
>>>
>>> - Redistributions in binary form must reproduce the above copyright
>>> notice, this list of conditions and the following disclaimer in the
>>> documentation and/or other materials provided with the distribution.
>>>
>>> - Neither the name of Internet Society, IETF or IETF Trust, nor the
>>> names of specific contributors, may be used to endorse or promote
>>> products derived from this software without specific prior written
>>> permission.
>>>
>>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>>> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>>> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>>> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
>>> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
>>> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
>>> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
>>> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
>>> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
>>> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>>> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2437/5275 - Release Date: 09/18/12
>
>


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


From ben@nostrum.com  Tue Sep 18 18:18:35 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38F9011E80CC; Tue, 18 Sep 2012 18:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.594
X-Spam-Level: 
X-Spam-Status: No, score=-102.594 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sSPj1xNJ-OB; Tue, 18 Sep 2012 18:18:34 -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 2C32611E80A5; Tue, 18 Sep 2012 18:18:34 -0700 (PDT)
Received: from [10.0.1.3] (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 q8J1IUN9015741 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Sep 2012 20:18:30 -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-eai-rfc5721bis-07,
Date: Tue, 18 Sep 2012 20:18:30 -0500
Message-Id: <E9ECAFE2-F301-449A-B6D7-C550956B8ED7@nostrum.com>
To: draft-ietf-eai-rfc5721bis-07.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
X-Mailer: Apple Mail (2.1486)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 01:18:35 -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-eai-rfc5721bis-07
Reviewer: Ben Campbell
Review Date: 2012-09-18
IETF LC End Date: 2012-09-20



Summary:   The draft is mostly ready for publication as a draft =
standard. I have a few editorial comments that should be considered =
prior to publication.

Major issues: None

Minor issues:=20

Nits/editorial comments:

-- IDNits has some complaints; please check.

-- The abstract should mention that this obsoletes 5721

-- section 2.1, 2nd paragraph: "The character encoding format of =
maildrops may not be UTF-8 or ASCII."

I'm confused by this sentence, as it seems to say that the format can't =
be UTF-8 or ASCII, which otherwise seem to be the only ones contemplated =
by the draft.  Do you mean to say that it may be some format other than =
those?

-- same paragraph : "The UTF8 command MAY fail."

Under what circumstances? (this seems sort of tacked onto the =
paragraph--does it belong there?)

-- 2.1, 4th paragraph: "...need not be accurate, but it is preferable if =
they were."

Not preferable enough for a SHOULD? (Note that the previous sentence =
used SHOULD for reporting actual message size counts)

-- section 7, 3rd paragraph: "It is possible for a man-in-the-middle =
attacker to insert a LANG command in the command stream, thus making =
protocol-level diagnostic responses unintelligible to the user."

This seems a bit unnecessary to call out, given that a MiTM could just =
change the diagnostic responses into Klingon even in the absence of the =
LANG command. It's at least worth mentioning that the LANG command =
really doesn't make this issue worse than it already was.



From ben@nostrum.com  Tue Sep 18 18:20:53 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4527221E8037; Tue, 18 Sep 2012 18:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PL5KMGH397oi; Tue, 18 Sep 2012 18:20:52 -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 C3F5721F85EF; Tue, 18 Sep 2012 18:20:52 -0700 (PDT)
Received: from [10.0.1.3] (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 q8J1KpOt015968 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Sep 2012 20:20:52 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Subject: Re: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07,
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <E9ECAFE2-F301-449A-B6D7-C550956B8ED7@nostrum.com>
Date: Tue, 18 Sep 2012 20:20:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3DE746A-8A6F-497E-AFAD-84B69FB846FA@nostrum.com>
References: <E9ECAFE2-F301-449A-B6D7-C550956B8ED7@nostrum.com>
To: draft-ietf-eai-rfc5721bis-07.all@tools.ietf.org
X-Mailer: Apple Mail (2.1486)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 01:20:53 -0000

On Sep 18, 2012, at 8:18 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> .
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:  draft-ietf-eai-rfc5721bis-07
> Reviewer: Ben Campbell
> Review Date: 2012-09-18
> IETF LC End Date: 2012-09-20
>=20
>=20
>=20
> Summary:   The draft is mostly ready for publication as a draft =
standard. I have a few editorial comments that should be considered =
prior to publication.

Oops, I meant proposed standard. Sorry for the confusion.


From ben@nostrum.com  Tue Sep 18 18:44:19 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6B7621E8055; Tue, 18 Sep 2012 18:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b3xdLgr5uqRy; Tue, 18 Sep 2012 18:44:19 -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 D39A221E8037; Tue, 18 Sep 2012 18:44:18 -0700 (PDT)
Received: from [10.0.1.3] (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 q8J1iFjZ017955 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Sep 2012 20:44:16 -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-eai-5738bis-09
Date: Tue, 18 Sep 2012 20:44:15 -0500
Message-Id: <2549BC7F-FD4D-4D65-817F-98833573D899@nostrum.com>
To: draft-ietf-eai-5738bis.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
X-Mailer: Apple Mail (2.1486)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 01:44:20 -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-eai-5738bis-09
Reviewer: Ben Campbell
Review Date: 2012-09-18
IETF LC End Date: 2012-09-20

Summary: The draft is almost ready for publication as a proposed =
standard. I have a few editorial comments as well as some questions =
about how this relates to the EAI downgrade drafts.

Major issues: None

Minor issues:=20

-- section 7 talks about how to handle MUAs that do not understand the =
UTF8 extensions. It talks about doing complex vs rudimentary downgrades, =
and lists draft-ietf-eai-popimap-downgrade and =
draft-ietf-eai-simpledowngrade as examples. These are both informational =
references. I note, however, that both of those drafts are standards =
track, which makes me wonder if the authors expected a normative =
reference?

Along the same lines, section 7 seems to go to lengths to illustrate why =
downgrading is somewhere between hard and  problematic. Do we really =
believe that downgrading will ever be the "least bad"?

Nits/editorial comments:

-- IDNits reports issues; please check.

-- Abstract: "This specification replaces RFC 5738."

s/replaces/obsoletes
 (repeats in the last paragraph of section 1).

-- section 3, 1st paragraph: "Note that the "UTF8=3DONLY" capability =
described in Section 6 implies the "UTF8=3DACCEPT" capability."

I assumed from  context (the paragraph talks about client's use of =
ENABLE) that  this refers to client use of the ENABLE command. But =
section 6 talks about server usemof the capability.

-- 3, 2nd to last paragraph: "Mailbox names MUST comply with the =
Net-Unicode Definition (Section 2 of [RFC5198]) with the specific =
exception that they MUST NOT contain control characters (0000-001F, =
0080-009F), delete (007F), line separator (2028), or paragraph separator =
(2029)."

You might consider recasting that in terms of actor behavior (i.e. what =
must a client and/or server do), given that the mailbox name doesn't get =
much say in the matter. This would be more consistent with the adjoining =
normative text (e.g. the next paragraph talks about how a client MUST do =
something and a server SHOULD enforce it.)

-- 4, 2nd to last paragraph:

Can this sentence be broken up or otherwise simplified? I found it easy =
to get lost in the conditions.

-- 6, 1st paragraph: "As this is an incompatible change to IMAP, a clear =
warning is necessary.  IMAP clients that find implementation of the =
"UTF8=3DONLY" capability problematic are encouraged to at least detect =
the "UTF8=3DONLY" capability and provide an informative error message to =
the end-user."

Seems like this should warrant a SHOULD

-- 6, 2nd paragraph: 'The "UTF8=3DONLY" capability includes all of the =
functions of "UTF8=3DACCEPT"'

Previous text said UTF8-ONLY implied UTF8-ACCEPT. That's subtly =
different than the language in this section. There may not be a =
practical difference, but it would be better to be consistent.

-- 7, 3rd paragraph: "... not really "downgraded ones" (although that =
terminology is often used for convenience) ..."

is there a formal definition of downgrade somewhere? Otherwise it's not =
clear what the objection to its use is.

-- section 9, 1st paragraph:

Is OBSOLETE in all-caps on purpose? It's not a 2119 term.
=20






From ben@nostrum.com  Tue Sep 18 18:45:22 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14C5411E80A5; Tue, 18 Sep 2012 18:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pq1t2hu0AusI; Tue, 18 Sep 2012 18:45:21 -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 4BEB411E808D; Tue, 18 Sep 2012 18:45:21 -0700 (PDT)
Received: from [10.0.1.3] (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 q8J1jJdJ018117 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Sep 2012 20:45:20 -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-eai-rfc5721bis-07,
Date: Tue, 18 Sep 2012 20:45:19 -0500
Message-Id: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com>
To: draft-ietf-eai-rfc5721bis.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
X-Mailer: Apple Mail (2.1486)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 01:45:22 -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-eai-rfc5721bis-07
Reviewer: Ben Campbell
Review Date: 2012-09-18
IETF LC End Date: 2012-09-20



Summary:   The draft is mostly ready for publication as a draft =
standard. I have a few editorial comments that should be considered =
prior to publication.

Major issues: None

Minor issues:=20

Nits/editorial comments:

-- IDNits has some complaints; please check.

-- The abstract should mention that this obsoletes 5721

-- section 2.1, 2nd paragraph: "The character encoding format of =
maildrops may not be UTF-8 or ASCII."

I'm confused by this sentence, as it seems to say that the format can't =
be UTF-8 or ASCII, which otherwise seem to be the only ones contemplated =
by the draft.  Do you mean to say that it may be some format other than =
those?

-- same paragraph : "The UTF8 command MAY fail."

Under what circumstances? (this seems sort of tacked onto the =
paragraph--does it belong there?)

-- 2.1, 4th paragraph: "...need not be accurate, but it is preferable if =
they were."

Not preferable enough for a SHOULD? (Note that the previous sentence =
used SHOULD for reporting actual message size counts)

-- section 7, 3rd paragraph: "It is possible for a man-in-the-middle =
attacker to insert a LANG command in the command stream, thus making =
protocol-level diagnostic responses unintelligible to the user."

This seems a bit unnecessary to call out, given that a MiTM could just =
change the diagnostic responses into Klingon even in the absence of the =
LANG command. It's at least worth mentioning that the LANG command =
really doesn't make this issue worse than it already was.



From ben@nostrum.com  Tue Sep 18 18:45:44 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5860911E80DE; Tue, 18 Sep 2012 18:45:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e6+3t+yQ2Pgg; Tue, 18 Sep 2012 18:45:43 -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 9FA5B11E80D9; Tue, 18 Sep 2012 18:45:43 -0700 (PDT)
Received: from [10.0.1.3] (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 q8J1jJdK018117 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Sep 2012 20:45:43 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Subject: Re: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07,
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <E9ECAFE2-F301-449A-B6D7-C550956B8ED7@nostrum.com>
Date: Tue, 18 Sep 2012 20:45:43 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E99E3186-1A6A-442D-818D-B53EE27A9801@nostrum.com>
References: <E9ECAFE2-F301-449A-B6D7-C550956B8ED7@nostrum.com>
To: "draft-ietf-eai-rfc5721bis.all@tools.ietf.org" <draft-ietf-eai-rfc5721bis.all@tools.ietf.org>
X-Mailer: Apple Mail (2.1486)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 01:45:44 -0000

On Sep 18, 2012, at 8:18 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> .
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:  draft-ietf-eai-rfc5721bis-07
> Reviewer: Ben Campbell
> Review Date: 2012-09-18
> IETF LC End Date: 2012-09-20
>=20
>=20
>=20
> Summary:   The draft is mostly ready for publication as a draft =
standard. I have a few editorial comments that should be considered =
prior to publication.

Oops, I meant proposed standard. Sorry for the confusion.


From housley@vigilsec.com  Tue Sep 18 18:51:38 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9F611E80D1 for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 18:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.476
X-Spam-Level: 
X-Spam-Status: No, score=-102.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gdchWePgJcK1 for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 18:51:34 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8F25111E80BA for <ietf@ietf.org>; Tue, 18 Sep 2012 18:51:34 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id E85FE9A4003; Tue, 18 Sep 2012 21:51:41 -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 xJSWBU-5y8rs; Tue, 18 Sep 2012 21:51:29 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 41B559A4001; Tue, 18 Sep 2012 21:51:39 -0400 (EDT)
Subject: Re: copyright notices in RFC 6716
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <87k3vrj9sg.fsf@latte.josefsson.org>
Date: Tue, 18 Sep 2012 21:51:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C3D5F13-C037-4BA4-900E-BA15F580A8DB@vigilsec.com>
References: <87a9wuropq.fsf@latte.josefsson.org> <A34B4161-4C39-4A3A-BDDA-207448BD985B@vigilsec.com> <87k3vrj9sg.fsf@latte.josefsson.org>
To: Simon Josefsson <simon@josefsson.org>
X-Mailer: Apple Mail (2.1084)
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, 19 Sep 2012 01:51:38 -0000

Simon:

The RFC contains the usual boilerplate and one additional paragraph.  =
The rights granted in the additional paragraph align with the rights =
that the authors wanted to provide.  Here is the additional paragraph:

   The licenses granted by the IETF Trust to this RFC under Section 3.c
   of the Trust Legal Provisions shall also include the right to extract
   text from Sections 1 through 8 and Appendix A and Appendix B of this
   RFC and create derivative works from these extracts, and to copy,
   publish, display and distribute such derivative works in any medium
   and for any purpose, provided that no such derivative work shall be
   presented, displayed or published in a manner that states or implies
   that it is part of this RFC or any other IETF Document.

Russ


On Sep 18, 2012, at 5:33 PM, Simon Josefsson wrote:

> Russ,
>=20
> I can't seem to align what you say with the document content.  The
> rights granted by the license text in the document (quoted below)
> appears to me be identical to the TLP except that the copyright header
> also includes non-authors.  Is this what you refer to with granting
> additional rights?
>=20
> My concern is not about rights granted (they appear to follow the =
TLD),
> but with the form of the copyright header that deviates from the TLD
> boilerplate.
>=20
> What puzzles me is that the explanation that I have received earlier =
is
> that variations beyond what the TLP demand is not permitted even if
> there is community support for the content of a particular document.
> I'm happy if this is now the policy, as it would allow including more
> source code into RFCs.
>=20
> /Simon
>=20
> Russ Housley <housley@vigilsec.com> writes:
>=20
>> Simon:
>>=20
>> The authors wanted to grant additional rights beyond those that are
>> granted by the TLP.  They indicated those rights in Section 10 of the
>> internet-Draft.  This was challenged during WG Last Call, and it was
>> challenged during IETF Last Call.  In each case, the authors make
>> their desire clear and the community supported them.  For this reason
>> the IETF Trust granted the usual TLP rights and the additional rights
>> as well.
>>=20
>> Russ
>>=20
>>=20
>> On Sep 13, 2012, at 10:18 AM, Simon Josefsson wrote:
>>=20
>>> All,
>>>=20
>>> I noticed that the recent RFC 6716 contains some reference code that
>>> contain the copyright and licenses notice reproduced below.  The =
IETF
>>> TLP [1] mandates a certain form of copyright notices and the TLP =
does
>>> not, as far as I can see, permit varying the boiler plate in any =
way.
>>> Note that both companies and organisations are mentioned in the
>>> copyright notice in RFC 6716, besides individuals.
>>>=20
>>> Does this indicate a policy change, a mistake with that document, or
>>> something else?
>>>=20
>>> Btw, kudos to the RFC 6716 authors for shipping reference code!  I =
hope
>>> this will establish a best practice for standards in the future.
>>>=20
>>> /Simon
>>>=20
>>> [1]
>>> =
http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-20091228.ht=
m
>>>=20
>>> Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
>>>                   Jean-Marc Valin, Timothy B. Terriberry,
>>>                   CSIRO, Gregory Maxwell, Mark Borgerding,
>>>                   Erik de Castro Lopo. All rights reserved.
>>>=20
>>> This file is extracted from RFC6716. Please see that RFC for =
additional
>>> information.
>>>=20
>>> Redistribution and use in source and binary forms, with or without
>>> modification, are permitted provided that the following conditions
>>> are met:
>>>=20
>>> - Redistributions of source code must retain the above copyright
>>> notice, this list of conditions and the following disclaimer.
>>>=20
>>> - Redistributions in binary form must reproduce the above copyright
>>> notice, this list of conditions and the following disclaimer in the
>>> documentation and/or other materials provided with the distribution.
>>>=20
>>> - Neither the name of Internet Society, IETF or IETF Trust, nor the
>>> names of specific contributors, may be used to endorse or promote
>>> products derived from this software without specific prior written
>>> permission.
>>>=20
>>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>>> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>>> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS =
FOR
>>> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT =
OWNER
>>> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, =
SPECIAL,
>>> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
>>> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
>>> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY =
OF
>>> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
>>> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>>> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


From housley@vigilsec.com  Tue Sep 18 18:53:04 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A76B11E80BA for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 18:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7BWU3+jKnvCs for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 18:53:00 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7A63A11E808D for <ietf@ietf.org>; Tue, 18 Sep 2012 18:53:00 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id C26C69A4004; Tue, 18 Sep 2012 21:53:08 -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 JC-QypKWzSDf; Tue, 18 Sep 2012 21:52:57 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3F65C9A4001; Tue, 18 Sep 2012 21:53:07 -0400 (EDT)
Subject: Re: copyright notices in RFC 6716
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5058EBE8.7000708@earthlink.net>
Date: Tue, 18 Sep 2012 21:52:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <989D1211-013C-42D3-89CF-61074EF972CF@vigilsec.com>
References: <87a9wuropq.fsf@latte.josefsson.org> <A34B4161-4C39-4A3A-BDDA-207448BD985B@vigilsec.com> <87k3vrj9sg.fsf@latte.josefsson.org> <5058EBE8.7000708@earthlink.net>
To: tglassey <tglassey@earthlink.net>
X-Mailer: Apple Mail (2.1084)
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, 19 Sep 2012 01:53:04 -0000

Todd:

No.  The additional rights are granted for RFC 6716, and there is no =
implication about any other RFC.

Russ


On Sep 18, 2012, at 5:47 PM, tglassey wrote:

> On 9/18/2012 2:33 PM, Simon Josefsson wrote:
>> Russ,
>>=20
>> I can't seem to align what you say with the document content.  The
>> rights granted by the license text in the document (quoted below)
>> appears to me be identical to the TLP except that the copyright =
header
>> also includes non-authors.  Is this what you refer to with granting
>> additional rights?
>>=20
>> My concern is not about rights granted (they appear to follow the =
TLD),
>> but with the form of the copyright header that deviates from the TLD
>> boilerplate.
> Is there from this point forward a requirement for future works in =
this vein to also use the same rights statement? I am curious because of =
the complexity of merging this with other right specific issues.
>=20
> For instance if ID "A" is published with normal use rights and it is =
expanded in a revision which then increases its rights to some secondary =
set of rights-states and in so doing permanently seems to alter the =
baseline.
>=20
> What also if ID "A" is published with rights-set #1 and a formal work =
(like those described in the AIA (the America Invents Act) for instance, =
and then this is altered. The issue is how these rights do or do not =
promulgate from ID or RFC revision-to-revision.
>=20
> Todd//
>> What puzzles me is that the explanation that I have received earlier =
is
>> that variations beyond what the TLP demand is not permitted even if
>> there is community support for the content of a particular document.
>> I'm happy if this is now the policy, as it would allow including more
>> source code into RFCs.
>>=20
>> /Simon
>>=20
>> Russ Housley <housley@vigilsec.com> writes:
>>=20
>>> Simon:
>>>=20
>>> The authors wanted to grant additional rights beyond those that are
>>> granted by the TLP.  They indicated those rights in Section 10 of =
the
>>> internet-Draft.  This was challenged during WG Last Call, and it was
>>> challenged during IETF Last Call.  In each case, the authors make
>>> their desire clear and the community supported them.  For this =
reason
>>> the IETF Trust granted the usual TLP rights and the additional =
rights
>>> as well.
>>>=20
>>> Russ
>>>=20
>>>=20
>>> On Sep 13, 2012, at 10:18 AM, Simon Josefsson wrote:
>>>=20
>>>> All,
>>>>=20
>>>> I noticed that the recent RFC 6716 contains some reference code =
that
>>>> contain the copyright and licenses notice reproduced below.  The =
IETF
>>>> TLP [1] mandates a certain form of copyright notices and the TLP =
does
>>>> not, as far as I can see, permit varying the boiler plate in any =
way.
>>>> Note that both companies and organisations are mentioned in the
>>>> copyright notice in RFC 6716, besides individuals.
>>>>=20
>>>> Does this indicate a policy change, a mistake with that document, =
or
>>>> something else?
>>>>=20
>>>> Btw, kudos to the RFC 6716 authors for shipping reference code!  I =
hope
>>>> this will establish a best practice for standards in the future.
>>>>=20
>>>> /Simon
>>>>=20
>>>> [1]
>>>> =
http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-20091228.ht=
m
>>>>=20
>>>> Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
>>>>                    Jean-Marc Valin, Timothy B. Terriberry,
>>>>                    CSIRO, Gregory Maxwell, Mark Borgerding,
>>>>                    Erik de Castro Lopo. All rights reserved.
>>>>=20
>>>> This file is extracted from RFC6716. Please see that RFC for =
additional
>>>> information.
>>>>=20
>>>> Redistribution and use in source and binary forms, with or without
>>>> modification, are permitted provided that the following conditions
>>>> are met:
>>>>=20
>>>> - Redistributions of source code must retain the above copyright
>>>> notice, this list of conditions and the following disclaimer.
>>>>=20
>>>> - Redistributions in binary form must reproduce the above copyright
>>>> notice, this list of conditions and the following disclaimer in the
>>>> documentation and/or other materials provided with the =
distribution.
>>>>=20
>>>> - Neither the name of Internet Society, IETF or IETF Trust, nor the
>>>> names of specific contributors, may be used to endorse or promote
>>>> products derived from this software without specific prior written
>>>> permission.
>>>>=20
>>>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>>>> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>>>> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS =
FOR
>>>> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE =
COPYRIGHT OWNER
>>>> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, =
SPECIAL,
>>>> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
>>>> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
>>>> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY =
OF
>>>> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT =
(INCLUDING
>>>> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>>>> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>>=20
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2012.0.2221 / Virus Database: 2437/5275 - Release Date: =
09/18/12
>>=20
>>=20
>=20
>=20
> --=20
> //Confidential Mailing - Please destroy this if you are not the =
intended recipient.
>=20


From ben@nostrum.com  Tue Sep 18 19:15:16 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32F4421E8090; Tue, 18 Sep 2012 19:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxLz+k+4mxjp; Tue, 18 Sep 2012 19:15:15 -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 5060821E8055; Tue, 18 Sep 2012 19:15:15 -0700 (PDT)
Received: from [10.0.1.3] (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 q8J2FBRq020619 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Sep 2012 21:15:12 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-ietf-eai-popimap-downgrade-07
Date: Tue, 18 Sep 2012 21:15:11 -0500
Message-Id: <0E190012-B2A0-4F52-9BC0-ED32E803440B@nostrum.com>
To: draft-ietf-eai-popimap-downgrade.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
X-Mailer: Apple Mail (2.1486)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 02:15:16 -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-eai-popimap-downgrade-07
Reviewer: Ben Campbell=09
Review Date: 2012-09-18
IETF LC End Date: 2012-09-20

Summary: This draft is mostly on the right track, but has open issues

Major issues:

-- I'm concerned about the security considerations related to having a =
mail drop modify a potentially signed message. The draft mentions that =
this is an issue. I think more discussion is warranted. In particular. =
What client behavior is expected when a signature is invalidated due to =
downgrading? I suspect the answer is "warn the user, who will most =
likely just click through without understanding the issue." I'm =
concerned about adding yet another reason to train end users to ignore =
security warnings. OTOH, should the mail drop strip out signatures? That =
has it's own issues. I'm not saying that I know the answer--merely that =
it's not clear to me that it has been sufficiently explored.

[Note: The same issue is there for draft-ietf-eai-simpledowngrade]

Minor issues:

-- It's not clear to me why this is standards track rather than =
informational. As far as I can tell, it's mainly used by the IMAP UTF8 =
capability draft. But that draft seems to list this as an example of =
something you can do, and lists it as an informational reference.

--  draft-ietf-eai-simpledowngrade proposes to register a "DOWNGRADED" =
response code. It seems like that should be used by both or neither =
downgrade draft. (This is mentioned as an open issue in =
draft-ietf-eai-simpledowngrade).

Nits/editorial comments:

-- General:=20

As far as I can tell, this draft and draft-ietf-eai-simpledowngrade =
offer two alternatives to solve the same problem. Unfortunately they are =
very different in structure and terminology. It would make life easier =
for the reader if they were more consistent with one-another.

I found the structure hard to read in places. In particular, the mixing =
of imperative sentences  in paragraph form with complicated conditions =
made it easy to get lost. Either a more descriptive vs imperative style, =
or breaking things down more into (numbered or bulleted) steps might =
make it easier to read.=20

-- 1.1:

It would be helpful to be more explicit about what is meant by "legacy =
clients". Am I correct to assume it means clients that do not support =
the UTF8 capabilities in the relevant drafts from this workgroup?

-- 1.3, 2nd paragraph

s/ "unknown/broken" / "unknown or broken"

-- 3.1.8, 1st paragraph: " If the <local-part> of the <mailbox> element =
does not contain non-ASCII characters, the <domain> element contains =
non-ASCII characters."

This appears to say that if the local part has no non-ASCII characters, =
then the domain part does. Is that the intent? I.e. there is no =
possibility that neither has non-ASCII chars?

-- 3.1.8, 2nd paragraph: "... the model above."

Please reference the section number.

-- 3.2.1:

Jumping right into the header field list without any preamble is rather =
abrubt.

--3.2.1: First paragraph after the header field list: " Optionally add =
those words where appropriate to the next paragraph, but I think once =
will make it clear."

I assume this was an internal comment meant to be deleted?

-- 3.2.9: 2nd paragraph: "Perform <UNSTRUCTURED> downgrading."

Is there a condition missing here? (The structure of 3.2.9 is confusing =
in general--the paragraphs feel out of order.)

-- 5:=20

Nothing for content-type?

-- 6, 1st paragraph: "But they still contain MIME-encapsulated header =
fields that contain non-ASCII strings."

Is that always true?

-- 6, 4th paragraph: "Receivers may know they need to update their MUAs, =
or they don=92t care."

I don't get the point of this sentence.

-- 8, 1st paragraph: "Please change "should now be" and "should be" to =
"have been""

It's probably not worth changing at this point, but I suggest in general =
writing the words you want to see in the RFC. With all due respect to =
the apparent super powers of the RFC editor staff, asking them to change =
things unnecessarily creates opportunities for error.

-- 8, 2nd paragraph: "However [RFC6530] obsoleted [RFC5504] and this =
document does not use all "Downgraded-" header fields registered by =
[RFC5504]."

... And therefore what? I sounds like you expect the reader to draw a =
conclusion--better to spell it out.=

From ben@nostrum.com  Tue Sep 18 19:24:52 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0443711E80D1; Tue, 18 Sep 2012 19:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8k7LzZwpfji4; Tue, 18 Sep 2012 19:24:51 -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 C281611E808D; Tue, 18 Sep 2012 19:24:49 -0700 (PDT)
Received: from [10.0.1.3] (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 q8J2OmXm021355 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Sep 2012 21:24:48 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-ietf-eai-simpledowngrade-07
Date: Tue, 18 Sep 2012 21:24:48 -0500
Message-Id: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.com>
To: draft-ietf-eai-simpledowngrade.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
X-Mailer: Apple Mail (2.1486)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 02:24:52 -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-eai-simpledowngrade-07
Reviewer: Ben Campbell
Review Date: 2012-09-18
IETF LC End Date: 2012-09-20

Summary: This draft is mostly on the right track, but has open issues

Major issues:

-- I'm concerned about the security considerations related to having a =
mail drop modify a potentially signed message. The draft mentions that =
this is an issue. I think more discussion is warranted. In particular. =
What client behavior is expected when a signature is invalidated due to =
downgrading? I suspect the answer is "warn the user, who will most =
likely just click through without understanding the issue." I'm =
concerned about adding yet another reason to train end users to ignore =
security warnings. OTOH, should the mail drop strip out signatures? That =
has it's own issues. I'm not saying that I know the answer--merely that =
it's not clear to me that it has been sufficiently explored.

Minor Issues:

-- It's not clear to me why this is standards track rather than =
informational. As far as I can tell, it's mainly used by the IMAP UTF8 =
capability draft. But that draft seems to list this as an example of =
something you can do, and lists it as an informational reference.

-- section 3, 2nd paragraph:

Are there any limits on how much the size can differ from the actual =
delivered message? Can it be larger? Smaller? It's worth commenting on =
whether this could cause errors in the client. (e.g. Improper memory =
allocation)

-- "Open Issues" section: "Should Kazunori Fujiwara=92s downgrade =
document also mention DOWNGRADED?"

Good question. It seems like they should be consistent on things like =
this. (This is really more a comment on that draft than this one.)


Nits and Editorial Comments:

-- This draft appears to dispense with 2119 language. It be nice if all =
the drafts in the group handled this consistently.

-- Abstract should mention that this updates 3501

-- section 1:

Can you more explicitly define "conventional"? I assume this means =
clients not supporting the relevant UTF8 capabilities? This terminology =
is inconsistent between this and draft-ietf-eai-popimap-downgrade.



From tglassey@earthlink.net  Tue Sep 18 20:28:28 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C129521E804B for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 20:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.622
X-Spam-Level: 
X-Spam-Status: No, score=-2.622 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZG22PN45GPMk for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 20:28:25 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id EFD5511E80DE for <ietf@ietf.org>; Tue, 18 Sep 2012 20:28:24 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=PLyxIfjbFXjM7p68G8SRqOn3duwDuaBq31Gk6gyixG7irA3dfaEZFt4TJBz92YaZ; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TEAxS-0005MC-28; Tue, 18 Sep 2012 23:28:14 -0400
Message-ID: <50593BCB.9040001@earthlink.net>
Date: Tue, 18 Sep 2012 20:28:11 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: copyright notices in RFC 6716
References: <87a9wuropq.fsf@latte.josefsson.org> <A34B4161-4C39-4A3A-BDDA-207448BD985B@vigilsec.com> <87k3vrj9sg.fsf@latte.josefsson.org> <5058EBE8.7000708@earthlink.net> <989D1211-013C-42D3-89CF-61074EF972CF@vigilsec.com>
In-Reply-To: <989D1211-013C-42D3-89CF-61074EF972CF@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec795efd433493bab636340a70b04ea38f6b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
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, 19 Sep 2012 03:28:28 -0000

On 9/18/2012 6:52 PM, Russ Housley wrote:
> Todd:
>
> No.  The additional rights are granted for RFC 6716, and there is no implication about any other RFC.
I do understand that Russ, its the precedent I am worried about,. The 
process issues. My point also is that ID owners are not the only ones 
who can write an ID on a subject, any number of them under the current 
rules are possible. Of course the process of that would be slammed in 
the specific WG so it hasnt happened yet but with the current process 
rules there is nothing to stop it.

Or for that mater pirating another's work in any form.

Todd
>
> Russ
>
>
> On Sep 18, 2012, at 5:47 PM, tglassey wrote:
>
>> On 9/18/2012 2:33 PM, Simon Josefsson wrote:
>>> Russ,
>>>
>>> I can't seem to align what you say with the document content.  The
>>> rights granted by the license text in the document (quoted below)
>>> appears to me be identical to the TLP except that the copyright header
>>> also includes non-authors.  Is this what you refer to with granting
>>> additional rights?
>>>
>>> My concern is not about rights granted (they appear to follow the TLD),
>>> but with the form of the copyright header that deviates from the TLD
>>> boilerplate.
>> Is there from this point forward a requirement for future works in this vein to also use the same rights statement? I am curious because of the complexity of merging this with other right specific issues.
>>
>> For instance if ID "A" is published with normal use rights and it is expanded in a revision which then increases its rights to some secondary set of rights-states and in so doing permanently seems to alter the baseline.
>>
>> What also if ID "A" is published with rights-set #1 and a formal work (like those described in the AIA (the America Invents Act) for instance, and then this is altered. The issue is how these rights do or do not promulgate from ID or RFC revision-to-revision.
>>
>> Todd//
>>> What puzzles me is that the explanation that I have received earlier is
>>> that variations beyond what the TLP demand is not permitted even if
>>> there is community support for the content of a particular document.
>>> I'm happy if this is now the policy, as it would allow including more
>>> source code into RFCs.
>>>
>>> /Simon
>>>
>>> Russ Housley <housley@vigilsec.com> writes:
>>>
>>>> Simon:
>>>>
>>>> The authors wanted to grant additional rights beyond those that are
>>>> granted by the TLP.  They indicated those rights in Section 10 of the
>>>> internet-Draft.  This was challenged during WG Last Call, and it was
>>>> challenged during IETF Last Call.  In each case, the authors make
>>>> their desire clear and the community supported them.  For this reason
>>>> the IETF Trust granted the usual TLP rights and the additional rights
>>>> as well.
>>>>
>>>> Russ
>>>>
>>>>
>>>> On Sep 13, 2012, at 10:18 AM, Simon Josefsson wrote:
>>>>
>>>>> All,
>>>>>
>>>>> I noticed that the recent RFC 6716 contains some reference code that
>>>>> contain the copyright and licenses notice reproduced below.  The IETF
>>>>> TLP [1] mandates a certain form of copyright notices and the TLP does
>>>>> not, as far as I can see, permit varying the boiler plate in any way.
>>>>> Note that both companies and organisations are mentioned in the
>>>>> copyright notice in RFC 6716, besides individuals.
>>>>>
>>>>> Does this indicate a policy change, a mistake with that document, or
>>>>> something else?
>>>>>
>>>>> Btw, kudos to the RFC 6716 authors for shipping reference code!  I hope
>>>>> this will establish a best practice for standards in the future.
>>>>>
>>>>> /Simon
>>>>>
>>>>> [1]
>>>>> http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-20091228.htm
>>>>>
>>>>> Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
>>>>>                     Jean-Marc Valin, Timothy B. Terriberry,
>>>>>                     CSIRO, Gregory Maxwell, Mark Borgerding,
>>>>>                     Erik de Castro Lopo. All rights reserved.
>>>>>
>>>>> This file is extracted from RFC6716. Please see that RFC for additional
>>>>> information.
>>>>>
>>>>> Redistribution and use in source and binary forms, with or without
>>>>> modification, are permitted provided that the following conditions
>>>>> are met:
>>>>>
>>>>> - Redistributions of source code must retain the above copyright
>>>>> notice, this list of conditions and the following disclaimer.
>>>>>
>>>>> - Redistributions in binary form must reproduce the above copyright
>>>>> notice, this list of conditions and the following disclaimer in the
>>>>> documentation and/or other materials provided with the distribution.
>>>>>
>>>>> - Neither the name of Internet Society, IETF or IETF Trust, nor the
>>>>> names of specific contributors, may be used to endorse or promote
>>>>> products derived from this software without specific prior written
>>>>> permission.
>>>>>
>>>>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>>>>> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>>>>> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>>>>> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
>>>>> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
>>>>> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
>>>>> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
>>>>> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
>>>>> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
>>>>> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>>>>> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>>> -----
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 2012.0.2221 / Virus Database: 2437/5275 - Release Date: 09/18/12
>>>
>>>
>>
>> -- 
>> //Confidential Mailing - Please destroy this if you are not the intended recipient.
>>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2441/5276 - Release Date: 09/18/12
>
>
>


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


From touch@isi.edu  Tue Sep 18 23:47:45 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 452A121F8456 for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 23:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.98
X-Spam-Level: 
X-Spam-Status: No, score=-101.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ro2GUoZuAHWp for <ietf@ietfa.amsl.com>; Tue, 18 Sep 2012 23:47:44 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 7F5F421F8455 for <ietf@ietf.org>; Tue, 18 Sep 2012 23:47:44 -0700 (PDT)
Received: from [10.59.76.247] ([210.229.158.64]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q8J6kFSZ006058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 18 Sep 2012 23:46:33 -0700 (PDT)
Message-ID: <50596A36.4080007@isi.edu>
Date: Tue, 18 Sep 2012 23:46:14 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Lawrence Conroy <lconroy@insensate.co.uk>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120914051004.9A16F1A224@ld9781.wdf.sap.corp> <5052C21E.4030408@isi.edu> <4A0FA4FB-FB1F-4B77-921C-2A3E557FBA3B@harvard.edu> <AFA7205B-EB69-4088-BDC9-8A7762A12133@insensate.co.uk>
In-Reply-To: <AFA7205B-EB69-4088-BDC9-8A7762A12133@insensate.co.uk>
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: "Bradner, Scott" <sob@harvard.edu>, The 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, 19 Sep 2012 06:47:45 -0000

On 9/16/2012 6:56 AM, Lawrence Conroy wrote:
...
> It is VERY useful to be able to search through drafts to see how we
> got here, AND to see things that were explored and abandoned.

Thieves find it very useful to have what they steal. That doesn't 
legitimize their theft.

Utility can determine whether it's worth the effort/expense to run a 
public archive, but your utility never undermines my rights as an author.

Joe


From joelja@bogus.com  Wed Sep 19 00:33:39 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2CB921F86A2 for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 00:33: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfsdVvLRAwaF for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 00:33:39 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3EED921F855E for <ietf@ietf.org>; Wed, 19 Sep 2012 00:33:39 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q8J7XXST050915 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 19 Sep 2012 07:33:33 GMT (envelope-from joelja@bogus.com)
Message-ID: <5059754D.5020404@bogus.com>
Date: Wed, 19 Sep 2012 00:33:33 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120821 Thunderbird/15.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120914051004.9A16F1A224@ld9781.wdf.sap.corp> <5052C21E.4030408@isi.edu> <4A0FA4FB-FB1F-4B77-921C-2A3E557FBA3B@harvard.edu> <AFA7205B-EB69-4088-BDC9-8A7762A12133@insensate.co.uk> <50596A36.4080007@isi.edu>
In-Reply-To: <50596A36.4080007@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 19 Sep 2012 07:33:34 +0000 (UTC)
Cc: "Bradner, Scott" <sob@harvard.edu>, The 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, 19 Sep 2012 07:33:39 -0000

On 9/18/12 11:46 PM, Joe Touch wrote:
>
>
> On 9/16/2012 6:56 AM, Lawrence Conroy wrote:
> ...
>> It is VERY useful to be able to search through drafts to see how we
>> got here, AND to see things that were explored and abandoned.
>
> Thieves find it very useful to have what they steal. That doesn't 
> legitimize their theft.
>
> Utility can determine whether it's worth the effort/expense to run a 
> public archive, but your utility never undermines my rights as an author.
Non-lawyer here...

An authors rights are not entirely exclusive. e.g. 17 U.S.C 107 applies.
> Joe
>


From simon@josefsson.org  Wed Sep 19 01:21:15 2012
Return-Path: <simon@josefsson.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 0166721F8647 for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 01:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.85
X-Spam-Level: 
X-Spam-Status: No, score=-99.85 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553,  HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JioaPNfN+zfU for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 01:21:11 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id C80E821F8688 for <ietf@ietf.org>; Wed, 19 Sep 2012 01:21:10 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q8J8KtL2010576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 19 Sep 2012 10:20:56 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: copyright notices in RFC 6716
References: <87a9wuropq.fsf@latte.josefsson.org> <A34B4161-4C39-4A3A-BDDA-207448BD985B@vigilsec.com> <87k3vrj9sg.fsf@latte.josefsson.org> <5C3D5F13-C037-4BA4-900E-BA15F580A8DB@vigilsec.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120919:ietf@ietf.org::OxWdwS7Q0FALkPR0:MYfC
X-Hashcash: 1:22:120919:housley@vigilsec.com::+UwmOLt1D4j5n5Bl:ccmZ
Date: Wed, 19 Sep 2012 10:20:54 +0200
In-Reply-To: <5C3D5F13-C037-4BA4-900E-BA15F580A8DB@vigilsec.com> (Russ Housley's message of "Tue, 18 Sep 2012 21:51:29 -0400")
Message-ID: <87k3vqh195.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
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, 19 Sep 2012 08:21:15 -0000

Russ,

I had missed that section (which seems like a wonderful section btw).
However the license isn't what my initial question was about, so this is
a red herring.  This also explains why I wasn't able to follow Cullen's
initial reply.  My question was about the copyright header.  Let's see
if I can be clearer...  The TLP says the copyright header must be:

Copyright (c) <insert year> IETF Trust and the persons identified as
authors of the code.  All rights reserved.

but the code in the document uses:

Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
                   Jean-Marc Valin, Timothy B. Terriberry,
                   CSIRO, Gregory Maxwell, Mark Borgerding,
                   Erik de Castro Lopo. All rights reserved.

The difference between these two forms is what I'm wondering about.
Essentially what I'm asking is which one applies of:

 1) Was the copyright header variation permitted intentionally for this
 document as an exception to the TLP?

 2) Nobody noticed that the copyright header was different from what the
 TLP demands.

 3) Something else.

/Simon

Russ Housley <housley@vigilsec.com> writes:

> Simon:
>
> The RFC contains the usual boilerplate and one additional paragraph.
> The rights granted in the additional paragraph align with the rights
> that the authors wanted to provide.  Here is the additional paragraph:
>
>    The licenses granted by the IETF Trust to this RFC under Section 3.c
>    of the Trust Legal Provisions shall also include the right to extract
>    text from Sections 1 through 8 and Appendix A and Appendix B of this
>    RFC and create derivative works from these extracts, and to copy,
>    publish, display and distribute such derivative works in any medium
>    and for any purpose, provided that no such derivative work shall be
>    presented, displayed or published in a manner that states or implies
>    that it is part of this RFC or any other IETF Document.
>
> Russ
>
>
> On Sep 18, 2012, at 5:33 PM, Simon Josefsson wrote:
>
>> Russ,
>> 
>> I can't seem to align what you say with the document content.  The
>> rights granted by the license text in the document (quoted below)
>> appears to me be identical to the TLP except that the copyright header
>> also includes non-authors.  Is this what you refer to with granting
>> additional rights?
>> 
>> My concern is not about rights granted (they appear to follow the TLD),
>> but with the form of the copyright header that deviates from the TLD
>> boilerplate.
>> 
>> What puzzles me is that the explanation that I have received earlier is
>> that variations beyond what the TLP demand is not permitted even if
>> there is community support for the content of a particular document.
>> I'm happy if this is now the policy, as it would allow including more
>> source code into RFCs.
>> 
>> /Simon
>> 
>> Russ Housley <housley@vigilsec.com> writes:
>> 
>>> Simon:
>>> 
>>> The authors wanted to grant additional rights beyond those that are
>>> granted by the TLP.  They indicated those rights in Section 10 of the
>>> internet-Draft.  This was challenged during WG Last Call, and it was
>>> challenged during IETF Last Call.  In each case, the authors make
>>> their desire clear and the community supported them.  For this reason
>>> the IETF Trust granted the usual TLP rights and the additional rights
>>> as well.
>>> 
>>> Russ
>>> 
>>> 
>>> On Sep 13, 2012, at 10:18 AM, Simon Josefsson wrote:
>>> 
>>>> All,
>>>> 
>>>> I noticed that the recent RFC 6716 contains some reference code that
>>>> contain the copyright and licenses notice reproduced below.  The IETF
>>>> TLP [1] mandates a certain form of copyright notices and the TLP does
>>>> not, as far as I can see, permit varying the boiler plate in any way.
>>>> Note that both companies and organisations are mentioned in the
>>>> copyright notice in RFC 6716, besides individuals.
>>>> 
>>>> Does this indicate a policy change, a mistake with that document, or
>>>> something else?
>>>> 
>>>> Btw, kudos to the RFC 6716 authors for shipping reference code!  I hope
>>>> this will establish a best practice for standards in the future.
>>>> 
>>>> /Simon
>>>> 
>>>> [1]
>>>> http://trustee.ietf.org/license-info/IETF-Trust-License-Policy-20091228.htm
>>>> 
>>>> Copyright 1994-2011 IETF Trust, Xiph.Org, Skype Limited, Octasic,
>>>>                   Jean-Marc Valin, Timothy B. Terriberry,
>>>>                   CSIRO, Gregory Maxwell, Mark Borgerding,
>>>>                   Erik de Castro Lopo. All rights reserved.
>>>> 
>>>> This file is extracted from RFC6716. Please see that RFC for additional
>>>> information.
>>>> 
>>>> Redistribution and use in source and binary forms, with or without
>>>> modification, are permitted provided that the following conditions
>>>> are met:
>>>> 
>>>> - Redistributions of source code must retain the above copyright
>>>> notice, this list of conditions and the following disclaimer.
>>>> 
>>>> - Redistributions in binary form must reproduce the above copyright
>>>> notice, this list of conditions and the following disclaimer in the
>>>> documentation and/or other materials provided with the distribution.
>>>> 
>>>> - Neither the name of Internet Society, IETF or IETF Trust, nor the
>>>> names of specific contributors, may be used to endorse or promote
>>>> products derived from this software without specific prior written
>>>> permission.
>>>> 
>>>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>>>> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>>>> LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>>>> A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
>>>> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
>>>> EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
>>>> PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
>>>> PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
>>>> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
>>>> NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>>>> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

From john-ietf@jck.com  Wed Sep 19 01:45:39 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27E4521F86EA; Wed, 19 Sep 2012 01:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7ZZKnw3FF51; Wed, 19 Sep 2012 01:45:38 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2D81021F869F; Wed, 19 Sep 2012 01:45:38 -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 1TEFuX-000PAu-T3; Wed, 19 Sep 2012 04:45:33 -0400
Date: Wed, 19 Sep 2012 04:45:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ben Campbell <ben@nostrum.com>, draft-ietf-eai-simpledowngrade.all@tools.ietf.org
Subject: Re: Gen-ART LC Review of draft-ietf-eai-simpledowngrade-07
Message-ID: <E8CE99257EB153D5FEF25432@JcK-HP8200.jck.com>
In-Reply-To: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.com>
References: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.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: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 08:45:39 -0000

--On Tuesday, September 18, 2012 21:24 -0500 Ben Campbell
<ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For
> background on Gen-ART, please see the FAQ at
> 
> <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-eai-simpledowngrade-07
> Reviewer: Ben Campbell
> Review Date: 2012-09-18
> IETF LC End Date: 2012-09-20
> 
> Summary: This draft is mostly on the right track, but has open
> issues
> 
> Major issues:
> 
> -- I'm concerned about the security considerations related to
> having a mail drop modify a potentially signed message. The
> draft mentions that this is an issue. I think more discussion
> is warranted. In particular. What client behavior is expected
> when a signature is invalidated due to downgrading? I suspect
> the answer is "warn the user, who will most likely just click
> through without understanding the issue." I'm concerned about
> adding yet another reason to train end users to ignore
> security warnings. OTOH, should the mail drop strip out
> signatures? That has it's own issues. I'm not saying that I
> know the answer--merely that it's not clear to me that it has
> been sufficiently explored.

Ben,

I want to respond as WG Co-chair to this one issue.  Comments on
your minor issues will follow, but please be assured that the
non-editorial ones (and even some of those) have been discussed
extensively in the WG.

There is a fundamental issue that runs across the four
documents, that the WG discussed extensively, and that the WG
believes is adequately described.  The WG made an explicit
decision to not repeat that explanation at every possible point
and in each document.  It explicitly chose overall brevity over
repetition partially in the belief that repeating the material
might cause important comments or requirements to get lost in
the noise.  At the same time, it is easy to lose sight of the
issue and its implications when reviewing the documents.  It
actually becomes very clear when one starts considering
implementation details.

That issue is that a upgraded IMAP or POP server may find itself
in possession of an message that requires SMTPUTF8 ("EAI")
capability, that it may be one message of that type among many
messages with ACSCII-only headers that do not require that
capability, and that it may find itself connected to by a legacy
client.  There are two important things about that case:

	* There is absolutely no way to deliver the problem
	message to the client.  The IMAP and POP specifications,
	and the basic email transport and header specifications
	from which their provisions are derived, are absolutely
	clear that addresses and header fields are in ASCII
	(IMAP allows for the use of some alternate character
	sets and encodings, but that turns out to be a bad
	choice in this case and, fwiw, conversion to use any of
	them would also invalidate signatures.
	
	* There are no provisions in POP or IMAP for the server
	to say to the client "this particular message fails
	within the range you have specified, but cannot be
	delivered to you" (much less why that is the case).  In
	principle, EAI could have added such capabilities but
	they would not haved helped legacy clients (that, by
	definition, didn't implement them), would have added
	clutter to the protocols, and would not have benefited
	upgraded clients either (because it is easier to just
	support UTF-8 headers and other requirements.

Given that situation, the POP or IMAP server can choose to do
any of a range of things, all of them bad news.  Two of the
choices are to _replace_ the original message with a substitute
(or "synthetic" or "surrogate") message that provides the user
of the client some more or less good hints  about what is going
on and what the original message was about.  What is being
delivered is not the original message.  If the original
contained non-ASCII addresses, the surrogate will not be able to
represent them directly and will, in general, not be reply-able.
Expecting an integrity check on the original message to be valid
with the surrogate one is unreasonable; indeed, one would be
very concerned if such a check (signature-based or otherwise)
did validate.  

When there is an integrity check present, perhaps the Right
Thing would be to disable it and include a note in the surrogate
message that indicates that the original contained such a check.
The wording was intended to allow for that option when it is
deemed appropriate and feasible by the server's designers and
operators.  But remember that there are undetectable cases (not
covered specifically by IETF standards) such as when the
signature or equivalent information is transmitted out of band.

The net result of this is that saying much more in the Security
Considerations section would be likely to be misleading,
covering some cases and not others.  And, to answer your
specific question above, the WG did consider the issue and the
various cases and alternatives, and did so at great length.

The complexity of the situation also explains the choice of
standards track for the two downgrade specs.  On the one hand,
as you note, the POP and IMAP specs are written primarily from
the standpoint of an upgraded server talking to an upgraded
client.  We expect that to be the long-term situation and it is
the right way to write the specs given that situation.  Because
of the many options as to what to do in this transitional case,
a normative reference to one or more specific ones would have
been inappropriate.   On the other hand, while the two
strategies represented by popimap-downgrade and simpledowngrade
are believed by the WG to be self-consistent and adequate given
the assumptions identified for them, there are _many_ ways to
get things wrong (some of which the WG discovered only after
considerable discussion).  The only way we have to clearly say
"if you are going to make these decisions and assumptions, then
implement downgrading this way" is by putting those documents on
standards track.  

As I hope it clear from the above, the WG has strong consensus
that the only correct and completely adequate solution to the
problem of an upgraded server interacting with a legacy client
over a message that requires those upgraded capabilities is to
avoid having the problem occur by getting an upgraded client.
We could write more explicit applicability language to say that,
but, IMO and that of the WG, it wouldn't contribute anything.

best,
   john


From john-ietf@jck.com  Wed Sep 19 04:54:06 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C77821F86E1; Wed, 19 Sep 2012 04:54:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.515
X-Spam-Level: 
X-Spam-Status: No, score=-102.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bguZcZSViNC1; Wed, 19 Sep 2012 04:54:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CE1DA21F8690; Wed, 19 Sep 2012 04:54:05 -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 1TEIqt-000PNm-HA; Wed, 19 Sep 2012 07:53:59 -0400
Date: Wed, 19 Sep 2012 07:53:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ben Campbell <ben@nostrum.com>, draft-ietf-eai-5738bis.all@tools.ietf.org
Subject: Re: Gen-ART LC Review of draft-ietf-eai-5738bis-09
Message-ID: <C5852787C87923CBA226D36A@JcK-HP8200.jck.com>
In-Reply-To: <2549BC7F-FD4D-4D65-817F-98833573D899@nostrum.com>
References: <2549BC7F-FD4D-4D65-817F-98833573D899@nostrum.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: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 11:54:06 -0000

Following up on my earlier note about a comment from you that
really applies to the strategy on which all four documents are
really based...

--On Tuesday, September 18, 2012 20:44 -0500 Ben Campbell
<ben@nostrum.com> wrote:

>...
> Along the same lines, section 7 seems to go to lengths to
> illustrate why downgrading is somewhere between hard and
> problematic. Do we really believe that downgrading will ever
> be the "least bad"?

As compared to what, Ben?  

One alternative is to not support delivery of SMTPUTF8 messages
at all except in environments in which it can be guaranteed that
all IMAP and POP clients that might contact the servers are
already upgraded.  It is operationally possible to make that
guarantee in a few scenarios, but they are rare.   In those
scenarios, many people in the WG would say "do that" (easily
managed by not having the delivery servers accept SMTPUTF8
messages until the POP/IMAP client upgrades are complete).
But, for all of the more usual cases in which the IMAP/POP
server operator cannot control exactly what clients might be
used, the only alternate is to not allow such messages, ever.
We don't think that is a desirable choice (or we wouldn't have
done the work in the WG) but nothing in these protocols require
that anyone deploy i18n mail.

For the other alternatives, yes, downgrading --by one of these
scenarios or some other one-- is, indeed, likely to be "less
bad" than others in some operational scenarios.   In particular,
one alternate is for the server to silently delete all messages
requiring SMTPUTF8 (EAI) capability if a client connects that
doesn't support the needed capability.  If only because the user
might later come back with a more capable client (or a message
access mechanism that doesn't use a POP or IMAP client at all),
that messaging-deleting alternative is almost certainly the
worst option of all, making almost anything else "less bad".

And, again, yes the WG discussed these issues at length, perhaps
even ad nauseam.

    john



From mrex@sap.com  Wed Sep 19 09:55:55 2012
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 253D321F875B for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 09:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.161
X-Spam-Level: 
X-Spam-Status: No, score=-10.161 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D067B4yvVEXl for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 09:55:54 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 05F0921F8551 for <ietf@ietf.org>; Wed, 19 Sep 2012 09:55:53 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q8JGtniK028248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Sep 2012 18:55:49 +0200 (MEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <50596A36.4080007@isi.edu>
To: Joe Touch <touch@isi.edu>
Date: Wed, 19 Sep 2012 18:55:49 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
Message-Id: <20120919165549.5535C1A23C@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: "Bradner, Scott" <sob@harvard.edu>, The IETF <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: Wed, 19 Sep 2012 16:55:55 -0000

Joe Touch wrote:
>=20
> Lawrence Conroy wrote:
>>=20
>> It is VERY useful to be able to search through drafts to see how we
>> got here, AND to see things that were explored and abandoned.
>=20
> Thieves find it very useful to have what they steal. That doesn't=20
> legitimize their theft.
>=20
> Utility can determine whether it's worth the effort/expense to run a=20
> public archive, but your utility never undermines my rights as an author.

You're still seriously confusing things.

An I-D contribution transfers perpetual (i.e. irrevocable) redistribution
rights to the IETF -- at a minimum since rfc2026 (Oct 1996) and
1id-guidelines.txt pointing to rfc2026 section 10.  For copyrighted
contents, the perpetual, irrevocable transfer of specific rights is
actually the norm, and an extraordinary, time-limited lease of rights
would have to be negotiated and mutually agreed to in order to apply.
(in German legalese the term is "Ersch=F6pfungsgrundsatz").


The management of the online I-D repository and the expiration of
documents in there has NOTHING whatsoever to do with that transfer
of rights.

Surely an author can decide to re-publish the I-D contents under
different licenses somewhere else or later.  But that does not
impair the rights previously granted to the IETF in any way.


What is necessary, however, for the transfer of rights according to
rfc2026 section 10 to have happened, is that the I-D submitter was
in posession of (or entitled to) grant/transfer these rights. =20
Only when the I-D submitter did not have that rights when he submitted
the document, would require the IETF to stop re-distribution the I-D
when it became aware of this (and found itself unable to retroactively
obtain the necessary rights from the rightful owner).


-Martin

From johnl@iecc.com  Wed Sep 19 11:25:08 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5647B21F8493 for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 11:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FCNrUZAgw4Ud for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 11:25:07 -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 24BA521F8489 for <ietf@ietf.org>; Wed, 19 Sep 2012 11:25:06 -0700 (PDT)
Received: (qmail 77406 invoked from network); 19 Sep 2012 18:25:05 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Sep 2012 18:25:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=505a0e01.xn--btvx9d.k1208; i=johnl@user.iecc.com; bh=9nRCvPwb3StN0EDv5cBp1v9KfRbkm2Ekc0Fd0pJ9TuM=; b=cBVG/tK5M4gtdDwXoAi6vDb9hLF5hofouv2cz78u97aLpYvYjE55ZFBRbuomddBZY/fDqB3208ihhEHoP0qHkRZYUCdWBPtC82NUnUbumk94g79bKB5Or+wTdedeWThfBwJLS7dCmKRtR6dVHWw65+8C8ALPzql4z5YwjiwVpPA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=505a0e01.xn--btvx9d.k1208; olt=johnl@user.iecc.com; bh=9nRCvPwb3StN0EDv5cBp1v9KfRbkm2Ekc0Fd0pJ9TuM=; b=UfyyL80dZQ3whO5Gnhg+jhr1Rkx/vs5kyOsxjvHRbrfIkHevjjSfR4JoOSqO0RJFsp3kbNyO+dS6178vdq8uTt+EOPCEqm9inaDfSgSBkhhMm7NFuC2LyVPQs61Kki3yYUTv6NoDXdGRvGtvlvkO6ewzIOfNphiKm0uakeHSaio=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 19 Sep 2012 18:24:43 -0000
Message-ID: <20120919182443.74080.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <50596A36.4080007@isi.edu>
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: Wed, 19 Sep 2012 18:25:08 -0000

>Utility can determine whether it's worth the effort/expense to run a 
>public archive, but your utility never undermines my rights as an author.

We're very deep into Junior Lawyer territory here.

You might want to review RFC 3978, section 3.3a, in which contributors
make a:

      perpetual, irrevocable, non-exclusive, royalty-free, world-wide
      right and license to the ISOC and the IETF under all intellectual
      property rights in the Contribution:

This is unrelated to how long I-D's stay in the public archive.  If
you're not willing to accept those terms including the perpetual and
irrevocable part, you really shouldn't be submitting I-Ds or sending
mail to IETF mailing lists.

R's,
John

From touch@isi.edu  Wed Sep 19 13:29:22 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2F4221F851E for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 13:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.966
X-Spam-Level: 
X-Spam-Status: No, score=-102.966 tagged_above=-999 required=5 tests=[AWL=-0.367, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HMq-cQ0ko8+3 for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 13:29:22 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 2830621F851B for <ietf@ietf.org>; Wed, 19 Sep 2012 13:29:22 -0700 (PDT)
Received: from [192.168.1.94] (pool-71-105-94-82.lsanca.dsl-w.verizon.net [71.105.94.82]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q8JKSv1l006424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 19 Sep 2012 13:29:01 -0700 (PDT)
Message-ID: <505A2B08.70805@isi.edu>
Date: Wed, 19 Sep 2012 13:28:56 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120919182443.74080.qmail@joyce.lan>
In-Reply-To: <20120919182443.74080.qmail@joyce.lan>
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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Sep 2012 20:29:23 -0000

On 9/19/2012 11:24 AM, John Levine wrote:
>> Utility can determine whether it's worth the effort/expense to run a
>> public archive, but your utility never undermines my rights as an author.
>
> We're very deep into Junior Lawyer territory here.

I'm not. I'm simply refuting *any* argument that starts with "because 
it's useful to the community".

There are other arguments - that lawyers will make - that depend on the 
particular boilerplate used, when the ID was published, whether 
click-based copyright transfer holds up, and so forth.

But utility doesn't drive the law. There are rights -rights of the 
author, and rights of the copyright holder - which are protected here, 
and they trump any perceived benefit to the community.

Joe

From cabo@tzi.org  Wed Sep 19 14:38:15 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C59921F84F2 for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 14:38:15 -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=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZDWQGvQW8yHL for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 14:38:14 -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 7C19F21F84F1 for <ietf@ietf.org>; Wed, 19 Sep 2012 14:38:14 -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.3/8.14.3) with ESMTP id q8JLc7RA001511; Wed, 19 Sep 2012 23:38:07 +0200 (CEST)
Received: from [192.168.217.117] (p54893C28.dip.t-dialin.net [84.137.60.40]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id AD53B4C7; Wed, 19 Sep 2012 23:38:06 +0200 (CEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <505A2B08.70805@isi.edu>
Date: Wed, 19 Sep 2012 23:38:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org>
References: <20120919182443.74080.qmail@joyce.lan> <505A2B08.70805@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1486)
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, 19 Sep 2012 21:38:15 -0000

On Sep 19, 2012, at 22:28, Joe Touch <touch@isi.edu> wrote:

> I'm simply refuting *any* argument that starts with "because it's =
useful to the community".

Interestingly, these kinds of arguments are the only ones I'm interested =
in.

Until there is a court decision impacting this usefulness (or one can be =
reasonably expected), the legal angle is simply irrelevant.

(Just keeping the thread alive so it doesn't seem that everybody agrees =
with the strangely luddite position taken here.)

Gr=FC=DFe, Carsten


From johnl@iecc.com  Wed Sep 19 15:31:31 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0659321E8048 for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 15:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level: 
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7TU4T1EgucyX for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 15:31:30 -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 2561D21E8034 for <ietf@ietf.org>; Wed, 19 Sep 2012 15:31:29 -0700 (PDT)
Received: (qmail 34385 invoked from network); 19 Sep 2012 22:31:28 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Sep 2012 22:31:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=505a47c0.xn--btvx9d.k1208; i=johnl@user.iecc.com; bh=Rzji8Re4AtMWUIvufDAty7oNl2L/xIUcupyA2tzIrtw=; b=g/d1BeFSEtpPoeGiSnsJlJGSziwWWp97QwuPj6QwPpScNrV1Z19ihhoZVB+XvdZtnVvqn9rv2yRafu9mOvyugu68C80LgcMPEwCTiidWRz+9uylkJ2JjuZYyzn5FGcT03gkeve0tLhtmTfs5iYvgTgxOAMWUYc8rtNPRGxH50nw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=505a47c0.xn--btvx9d.k1208; olt=johnl@user.iecc.com; bh=Rzji8Re4AtMWUIvufDAty7oNl2L/xIUcupyA2tzIrtw=; b=IPQC0SjWC/A7+mZcDwiwxYaIq/waLG/oOGd79y0bA8TRclH8atBDl0ZoG9uTCjlMIpcQkousd0fcZ0UyJGUb9AZZmxmWz14FHmmx4pKDIT7Jz1WKXw0nC68R5/pzqp6nXQszpCjVUJu7S9c6H26DAdGpwiF5nkixspKgy6twczU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 19 Sep 2012 22:31:06 -0000
Message-ID: <20120919223106.79603.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <505A2B08.70805@isi.edu>
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: Wed, 19 Sep 2012 22:31:31 -0000

In article <505A2B08.70805@isi.edu> you write:
>
>
>On 9/19/2012 11:24 AM, John Levine wrote:
>>> Utility can determine whether it's worth the effort/expense to run a
>>> public archive, but your utility never undermines my rights as an author.
>>
>> We're very deep into Junior Lawyer territory here.
>
>I'm not. I'm simply refuting *any* argument that starts with "because 
>it's useful to the community".

Could you answer the question, please?  Are you saying that you are
unaware, or do not believe that you have already given the IETF a
permanent license for all of your I-Ds and all your other IETF
contributions, which means it can publish them any way it wants
whether you like it or not?

This horse left the barn so long ago that the barn has long since
been torn down and replaced by a parking lot.

R's,
John

From touch@isi.edu  Thu Sep 20 07:44:43 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A29621F867A for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 07:44:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.929
X-Spam-Level: 
X-Spam-Status: No, score=-104.929 tagged_above=-999 required=5 tests=[AWL=1.670, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MqM6ikmMr+u6 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 07:44:42 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id B19A721F8674 for <ietf@ietf.org>; Thu, 20 Sep 2012 07:44:28 -0700 (PDT)
Received: from [192.168.1.94] (pool-71-105-94-82.lsanca.dsl-w.verizon.net [71.105.94.82]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q8KEh1Ro029367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 20 Sep 2012 07:43:10 -0700 (PDT)
Message-ID: <505B2B75.9060803@isi.edu>
Date: Thu, 20 Sep 2012 07:43:01 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120919223106.79603.qmail@joyce.lan>
In-Reply-To: <20120919223106.79603.qmail@joyce.lan>
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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Sep 2012 14:44:43 -0000

On 9/19/2012 3:31 PM, John Levine wrote:
> In article <505A2B08.70805@isi.edu> you write:
>>
>>
>> On 9/19/2012 11:24 AM, John Levine wrote:
>>>> Utility can determine whether it's worth the effort/expense to run a
>>>> public archive, but your utility never undermines my rights as an author.
>>>
>>> We're very deep into Junior Lawyer territory here.
>>
>> I'm not. I'm simply refuting *any* argument that starts with "because
>> it's useful to the community".
>
> Could you answer the question, please?  Are you saying that you are
> unaware, or do not believe that you have already given the IETF a
> permanent license for all of your I-Ds and all your other IETF
> contributions, which means it can publish them any way it wants
> whether you like it or not?

I definitely have IDs that predate the new policies, and did not 
transfer rights to the IETF for those.

> This horse left the barn so long ago that the barn has long since
> been torn down and replaced by a parking lot.

So could you answer this question - do you pirate DVDs too? That horse 
also left the barn, and presumably wild horses determine what you think 
is both legal and appropriate.

Joe




From arnt@gulbrandsen.priv.no  Wed Sep 19 08:18:10 2012
Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1803021F86F5; Wed, 19 Sep 2012 08:18:10 -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=[AWL=0.153,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1RXx5FO4YUtP; Wed, 19 Sep 2012 08:18:09 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) by ietfa.amsl.com (Postfix) with ESMTP id F29CF21F8622; Wed, 19 Sep 2012 08:18:05 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (unknown [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 59081FA09EB; Wed, 19 Sep 2012 15:18:04 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1348067883-31560-31559/10/2; Wed, 19 Sep 2012 15:18:03 +0000
Message-Id: <5059E240.8040702@gulbrandsen.priv.no>
Date: Wed, 19 Sep 2012 17:18:24 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0
Mime-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-eai-simpledowngrade-07
References: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.com>
In-Reply-To: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 20 Sep 2012 09:03:39 -0700
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-eai-simpledowngrade.all@tools.ietf.org, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 15:18:10 -0000

On 09/19/2012 04:24 AM, Ben Campbell 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-eai-simpledowngrade-07
> Reviewer: Ben Campbell
> Review Date: 2012-09-18
> IETF LC End Date: 2012-09-20
>
> Summary: This draft is mostly on the right track, but has open issues
>
> Major issues:
>
> -- I'm concerned about the security considerations related to having a =
mail drop modify a potentially signed message.
...

Hm, sounds like a misunderstanding. Did you understand that the=20
modification happens in RAM, and that the message stored unmodified and=20
has the valid signature? If not I suppose extra verbiage is needed.

The signature issue has been discussed. The answer is more or less: The=20
WG expects EAI users to use EAI-capable software, and to accept partial=20
failure when using software that cannot be updated.

This entire draft is draft is about damage limitation when an EAI user=20
uses EAI-ignorant software (e.g. your phone, if you do your main mail=20
handling on a computer but occasionally look using the phone). That=20
there will be damage is expected and accepted. IMO it's unavoidable. The=20
WG tries to ensure that the damage is not permanent (in the same=20
example: so you can still read the mail, properly signed and addressed,=20
on your computer).

FWIW, I mangled a message by hand to see what happened to a signature,=20
and got an angry-looking complaint above the body text. Or maybe it was=20
above the headers. Whatever.

> Minor Issues:
>
> -- It's not clear to me why this is standards track rather than =
informational.

I don't remember. Perhaps because it needs to update 3501.

> -- section 3, 2nd paragraph:
>
> Are there any limits on how much the size can differ from the actual =
delivered message? Can it be larger? Smaller? It's worth commenting on =
whether this could cause errors in the client. (e.g. Improper memory =
allocation)

An input message can be constructed to make the difference arbitrarily=20
large. For instance, just add an attachment with a suggested filename of=20
a million unicode snowmen, and the surrogate message will be several=20
megabyte smaller than the original. Or if you know that the target=20
server uses a long surrogate address format, add a million short Cc=20
addresses and the surrogate will be blown up by a million long CC =
addresses.

I doubt that this is exploitable. You can confuse or irritate the user=20
by making the client say "downloading 1.2MB" when the size before=20
download was reported as 42kb, that's all. I wish all my problems were=20
as small.

I'll add a comment and a reminder that the actual size is supplied along=20
with the literal during download.

> -- "Open Issues" section: "Should Kazunori Fujiwara=92s downgrade =
document also mention DOWNGRADED?"
>
> Good question. It seems like they should be consistent on things like =
this. (This is really more a comment on that draft than this one.)

I think I've made up my mind that in this case it doesn't matter.=20
Kazunori's task is complex reversible downgrade and has the Downgraded-*=20
header fields, why then bother with the DOWNGRADED response code? But=20
it's not my decision.

> -- Abstract should mention that this updates 3501

Really? A detail of this document updates a minor detail of that=20
document, that's hardly what I would expect to see in a single-paragraph=20
summary.

I know someone who likes to repeat the Subject in the first line of the=20
email body text. Just in case I didn't see it the first time, I suppose.

> -- section 1:
>
> Can you more explicitly define "conventional"? I assume this means =
clients not supporting the relevant UTF8 capabilities? This terminology =
is inconsistent between this and draft-ietf-eai-popimap-downgrade.

OK.

Arnt


From nico@cryptonector.com  Wed Sep 19 15:02:18 2012
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 6399721E8050 for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 15:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.073
X-Spam-Level: 
X-Spam-Status: No, score=-2.073 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tGEZHpF9HuRt for <ietf@ietfa.amsl.com>; Wed, 19 Sep 2012 15:02:17 -0700 (PDT)
Received: from homiemail-a72.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by ietfa.amsl.com (Postfix) with ESMTP id E108321E8034 for <ietf@ietf.org>; Wed, 19 Sep 2012 15:02:17 -0700 (PDT)
Received: from homiemail-a72.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTP id 264E26B007F for <ietf@ietf.org>; Wed, 19 Sep 2012 15:02:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:date:message-id:subject:from:to:content-type; s= cryptonector.com; bh=os2+MtuaZE5HLRqmXR79aUNokDI=; b=lDK2DfMOmYD 7LNwCQrlhBq88wLjfnH9DhHTjv8L9LzmLQq8avxWKOlIFYb2rrOsZ1yuobIp0uXB 0F5NxfJegXD/9yBfQc4fSNhR+IFp+yV5E+MXpFNeq/kgKNPCihcXY3QKBRnuf1hM uqC+MOpQakzVB9k/RP6x7E5qG03lNKBQ=
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a72.g.dreamhost.com (Postfix) with ESMTPSA id D139F6B007C for <ietf@ietf.org>; Wed, 19 Sep 2012 15:02:16 -0700 (PDT)
Received: by pbbjt11 with SMTP id jt11so1149432pbb.31 for <ietf@ietf.org>; Wed, 19 Sep 2012 15:02:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.85.133 with SMTP id h5mr623125paz.10.1348092136390; Wed, 19 Sep 2012 15:02:16 -0700 (PDT)
Received: by 10.68.20.194 with HTTP; Wed, 19 Sep 2012 15:02:16 -0700 (PDT)
Date: Wed, 19 Sep 2012 17:02:16 -0500
Message-ID: <CAK3OfOhhm8-88w+4wYq9bYQV_gErU_q5jExREzMPvTF0c51org@mail.gmail.com>
Subject: Are there XMPP conference servers for IETF in use outside of IETF meeting weeks?
From: Nico Williams <nico@cryptonector.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Thu, 20 Sep 2012 09:04:04 -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: Wed, 19 Sep 2012 22:02:18 -0000

There are times when I hunger for IETF chat rooms in between IETF
meetings.  Some mailing list discussions suffer from latency + piling
on.  I understand that IM chat rooms would often suffer from lack of
attendance, but a sort of interim meeting could get called on IM much
more often than physical interim meetings, and might help resolve
disagreements / reach consensus more quickly and with less effort than
e-mail (consensus would still have to be confirmed on-list, of
course).

Nico
--

From stephen.farrell@cs.tcd.ie  Thu Sep 20 09:09:43 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0139421F86FF for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 09:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wY+1eWwBDNnS for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 09:09:42 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 6633321F84B6 for <ietf@ietf.org>; Thu, 20 Sep 2012 09:09:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 08A4C17147D; Thu, 20 Sep 2012 17:09:41 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1348157380; bh=GdOt0+aQTMvhPQ ibV4oV/n6B7eacpP1M4kyNuisFU3o=; b=LbdXFt57tgsF8CHpeIgyFeeuYukdSd /pKLQ9ahb6SaP3olsuWNwtPEBQgA20dax58LCuWsZbRCYQQMdMKIH4UNT2BhSmnD mkRK0llbSCNi0gBqwxsL5+mIeQuKrvvhXxOvn4TZTIE8OtTcnJfe+VvYI9+eaGNL lyxdHl4rnvM2LKM7bySmgvCF25VjQe34s3x0lQX05/xFvDMdPecNtiJRPxFdoRUt /GTtW2AkkZm1TORhSJbfSI0jpYFwLfwWxA2Fcjjp5FBvhJHFB9i1sFMGgoM4th0J S9fU1jE0mbllcwf6c48QhNXrcd/Qm/ckWWP/8YUlgtQCWrSnB2Kqrn2w==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id Ox6QTZj6iaiU; Thu, 20 Sep 2012 17:09:40 +0100 (IST)
Received: from [192.6.10.171] (bri-event-72.hpl.hp.com [192.6.10.171]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 6CD19171477; Thu, 20 Sep 2012 17:09:40 +0100 (IST)
Message-ID: <505B3FC2.8080608@cs.tcd.ie>
Date: Thu, 20 Sep 2012 17:09:38 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
Subject: Re: Are there XMPP conference servers for IETF in use outside of IETF meeting weeks?
References: <CAK3OfOhhm8-88w+4wYq9bYQV_gErU_q5jExREzMPvTF0c51org@mail.gmail.com>
In-Reply-To: <CAK3OfOhhm8-88w+4wYq9bYQV_gErU_q5jExREzMPvTF0c51org@mail.gmail.com>
X-Enigmail-Version: 1.4.4
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: Thu, 20 Sep 2012 16:09:43 -0000

Hi Nico,

On 09/19/2012 11:02 PM, Nico Williams wrote:
> There are times when I hunger for IETF chat rooms in between IETF
> meetings.  Some mailing list discussions suffer from latency + piling
> on.  I understand that IM chat rooms would often suffer from lack of
> attendance, but a sort of interim meeting could get called on IM much
> more often than physical interim meetings, and might help resolve
> disagreements / reach consensus more quickly and with less effort than
> e-mail (consensus would still have to be confirmed on-list, of
> course).

Yes, the wg meeting rooms are always available.

If you want to use them for a more formal wg session then that's
a virtual interim. [1] We used that (just jabber, no voice) for
DKIM a few years ago and it worked ok. Other WGs also make use
of voice calls in parallel.

Cheers,
S.

[1] https://www.ietf.org/iesg/statement/interim-meetings.html

> 
> Nico
> --
> 
> 

From john-ietf@jck.com  Thu Sep 20 09:49:47 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8474F21F86E1 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 09:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.519
X-Spam-Level: 
X-Spam-Status: No, score=-102.519 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QjGcWFQ-+BgJ for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 09:49:46 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D75F721F86E4 for <ietf@ietf.org>; Thu, 20 Sep 2012 09:49:45 -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 1TEjwM-0002f5-8J; Thu, 20 Sep 2012 12:49:26 -0400
Date: Thu, 20 Sep 2012 12:49:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: Carsten Bormann <cabo@tzi.org>, Joe Touch <touch@isi.edu>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <07A7151E396F3AAA85F4A53F@JcK-HP8200.jck.com>
In-Reply-To: <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org>
References: <20120919182443.74080.qmail@joyce.lan> <505A2B08.70805@isi.edu> <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org>
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: 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: Thu, 20 Sep 2012 16:49:47 -0000

--On Wednesday, September 19, 2012 23:38 +0200 Carsten Bormann
<cabo@tzi.org> wrote:

>...
> Until there is a court decision impacting this usefulness (or
> one can be reasonably expected), the legal angle is simply
> irrelevant.
> 
> (Just keeping the thread alive so it doesn't seem that
> everybody agrees with the strangely luddite position taken
> here.)

Carsten,

Without completely agreeing with Joe (I don't), let me suggest
that the above may be the wrong way to look at this.

First of all, the "court decision impacting this..." argument
should be approached like any other risk-benefit analysis.   If
things were to get into a court and we were to lose, the
consequences could be nasty indeed.  While it is possible that a
judge might say "well, you were bad and shouldn't be doing this,
but I won't punish you if you promise to clean up your act in
the future", it isn't terribly likely.  If things were to get to
that point, prompted by a legal action by someone who could
actually claim to have been damaged by the current policy, it is
far more likely that the IETF would end up feeling significant
pain, possibly accompanied by penalties severe enough to prevent
us from keeping and getting the insurance on which we depend in
the future.

I personally don't consider it very likely that someone would
actually sue or convince some appropriate prosecutor to come
after us.  But, however one assesses the likelihood of that
happening and of that party winning, I think an attitude of
"don't worry about it until that happens and we lose" would
represent severely bad judgment.

Perhaps more important from my point of view, the IETF depends
on a social contract with its participants.  For many years,
participants had reason to believe that "expire after six
months" meant that the IETF would not publicly facilitate, or
directly provide public access to, expired I-Ds.  They also had
reason to believe that any rights they gave the IETF by posting
a document as an I-D did not extend beyond the IETF especially
after that six months -- that anyone else who wanted to make use
of the material would have to come and discuss it with them.
Whether that view was generally held or not is an almost
meaningless question: I'm pretty sure that the vast majority of
IETF participants, and even that of I-D authors, didn't give the
issue a moment's thought.

That same set of assumptions mostly applied even after that
changes that led to the current BCP 78/79 language: the IETF
Trust was granted (non-retroactively wrt earlier documents) the
rights to do a number of things that the community might need,
but there was no explicit assumption that all of those things
_would_ be done unless the community necessity (not just
convenience or wishes) were clear.  Again, opinions differed
about what was reasonable and appropriate in the normal case (an
issue the IPR WG definitely did not reach a consensus conclusion
about) and the evidence is (and was) that that vast majority of
IETF participants still didn't care enough to pay attention.

But that is precisely where the social contract becomes
important.  BCP 78 clearly gives the IETF the right to take a
document you have written without asking you, remove your name
from it, and publish it, possibly with modifications of which
you might not approve, under someone else's name.  That just
doesn't happen, not because the written rules prohibit it (or
because the IETF Trust is certain those provisions would hold up
in court), but because there is general understanding that it
would be in bad taste.  Equally important, many of us would
respond to such an action, at least one taken without a very
good and clear reason, by deciding that the IETF is not a place
where we care to do work any more.  The "contributions", at
least from those thus offended, would stop.  And, to the extent
that those contributions, and the credibility of the
contributors as a group, were important, the IETF would be in
serious, perhaps fatal trouble.

So, like you, I'm really not concerned whether Joe's arguments
are on firm legal ground or not even though I completely reject
the idea of "let's keep doing it until court to which we have to
pay attention tells us that we are wrong".   But I am concerned
that he and other authors of I-Ds, especially I-Ds that long
predate RFC 5378, made good-faith assumption, based on practices
at the time, about how their documents would be handled
post-expiration.  I think that, as a community, we ought to
respect those assumptions more than saying, effectively, "we are
going to maintain a public archive no matter what commitments
you thought were made to you because we can and because we don't
think you will actually sue us".  The latter is just bad for the
community, whether it "works" or not.

best,
   john









From dhc@dcrocker.net  Thu Sep 20 10:23:42 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F15D121F87EA for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 10:23: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.037,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cI7zj-+2HOYa for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 10:23:41 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1F22421F87E9 for <ietf@ietf.org>; Thu, 20 Sep 2012 10:23:41 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8KHNdJN001137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 20 Sep 2012 10:23:40 -0700
Message-ID: <505B5114.2050400@dcrocker.net>
Date: Thu, 20 Sep 2012 10:23:32 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120919182443.74080.qmail@joyce.lan> <505A2B08.70805@isi.edu> <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org>
In-Reply-To: <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 20 Sep 2012 10:23:40 -0700 (PDT)
Cc: John Levine <johnl@taugh.com>, 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, 20 Sep 2012 17:23:42 -0000

On 9/19/2012 2:38 PM, Carsten Bormann wrote:
> On Sep 19, 2012, at 22:28, Joe Touch <touch@isi.edu> wrote:
>
>> I'm simply refuting *any* argument that starts with "because it's
>> useful to the community".
>
> Interestingly, these kinds of arguments are the only ones I'm
> interested in.
>
> Until there is a court decision impacting this usefulness (or one can
> be reasonably expected), the legal angle is simply irrelevant.
>
> (Just keeping the thread alive so it doesn't seem that everybody
> agrees with the strangely luddite position taken here.)


Thanks for pressing the point.

I'm trying to imagine anything useful coming from decision-making 
process that ignores utility.  Accidents do occur, of course, but do we 
want the utility of an effort to be an accidental outcome?

At the same time, the real-world imposes legal concerns whether we want 
them or not.  The challenge, here, is to balance realistic concerns 
against realistic costs.  It is as dangerous to pay too much attention 
to legal issues as it is too much.

However...

We are a public-interest organization, with open participation, 
automated issuing of I-Ds, and a policy of their permanent retention and 
availability.

I'd expect an exceptional action to remove content from the permanent 
archive to create substantial legal exposure in many jurisdictions. 
Unfair bias and censoring of speech are two catch-phrases that occur to 
my non-lawyer brain.  I can too-easily serious liabilities for a removal 
action deemed legally inappropriate.

Worrying about that exposure only after the fact does not strike me as 
prudent.


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From cabo@tzi.org  Thu Sep 20 10:28:23 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88ED921F87FC for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 10:28:23 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DeWf7vSvXQpO for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 10:28:23 -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 C036F21F87E9 for <ietf@ietf.org>; Thu, 20 Sep 2012 10:28:22 -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.3/8.14.3) with ESMTP id q8KHSFF2021311; Thu, 20 Sep 2012 19:28:15 +0200 (CEST)
Received: from [192.168.217.117] (p5489283B.dip.t-dialin.net [84.137.40.59]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C508E9C6; Thu, 20 Sep 2012 19:28:14 +0200 (CEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <07A7151E396F3AAA85F4A53F@JcK-HP8200.jck.com>
Date: Thu, 20 Sep 2012 19:28:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <243065D9-3A39-4DD3-8BCA-371935FCA228@tzi.org>
References: <20120919182443.74080.qmail@joyce.lan> <505A2B08.70805@isi.edu> <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org> <07A7151E396F3AAA85F4A53F@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1498)
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, 20 Sep 2012 17:28:23 -0000

On Sep 20, 2012, at 18:49, John C Klensin <john-ietf@jck.com> wrote:

> I personally don't consider it very likely that someone would
> actually sue or convince some appropriate prosecutor to come
> after us.  But, however one assesses the likelihood of that
> happening and of that party winning, I think an attitude of
> "don't worry about it until that happens and we lose" would
> represent severely bad judgment.

It may be news for many people, but we all do things all day that might =
be considered illegal by someone.
(The image of a "law-abiding citizen" is mostly romantics.)
The question is whether there is an actual risk involved.
When there isn't, and people still press the point, we call that a red =
herring.

There is always a non-zero risk that some of our actions could by some =
jurisdiction maybe considered illegal.
Whether that likelihood (and the potential damage) is bearable or not, =
is indeed a matter of judgement.
Lawyers engage in assessing such a risk, and it is then usually a =
business (or personal life) decision whether you take the risk.

In this specific case, however, let me just opine that anybody who sees =
a serious risk here doesn't seem to get out much otherwise.

> Perhaps more important from my point of view, [...]

Now those are the interesting questions, indeed.
Let's focus on what is useful, and what is right (not what can be =
considered legal or illegal using some contrived amateur lawyer =
thinking).

The reality is that there is no harm coming to a submitter from the fact =
that the IETF is the 1001st place where expired drafts can be had.
There simply is no downside to the IETF also archiving them and making =
the archive available for our purposes.
The upside of doing this is that we maintain control, and that we can =
have tools operate on that archive that are useful to our work.
That is the right thing to do.

Now the one single thing that irks me, but I don't know how to solve:=20
We just had a consensus call in one WG on adopting a draft that at this =
time had been expired for a year.
The chairs didn't notice, because the URI was stable (as it should be).

Gr=FC=DFe, Carsten


From barryleiba.mailing.lists@gmail.com  Thu Sep 20 11:30:50 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914AB21F8733; Thu, 20 Sep 2012 11:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.956
X-Spam-Level: 
X-Spam-Status: No, score=-102.956 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqz7OqaYc62d; Thu, 20 Sep 2012 11:30:50 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id B827A21F8731; Thu, 20 Sep 2012 11:30:48 -0700 (PDT)
Received: by lboj14 with SMTP id j14so2540473lbo.31 for <multiple recipients>; Thu, 20 Sep 2012 11:30:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=CoTQaCIPSvH3MZ5oITbHk654TiQQr5hSzf1AomJGV2I=; b=aAru/g6jdGzCd2LP/17vvDA643K9+PyZfkVnrgwjWNeaAYsu7xGJ2KfZrw/8toEsPO kLO5unteyrWEvk3EhiBLzhxREgJhucGtFzId8MKQbq4Udn9LOIoKnCF+cYuGeMRijV8I 7nChUA4pJ2eRDDRxo7/FuPUecC0f9mFSPFJLpF1OYd3bbVCHwGEM5ORkFMa+YQufRPSH viTVisrz7JRHcrRgHHLBpcLQdLIo3rPSqrPDyTxXtlJVQWx6InYBgw5pbTCQcMRe2oXQ /JRw1WjJx4jyou2tO7CsTQrq4dVTBLXtCXbtGRYrTRA/dKsCDMvuRY1q6DUphDszw55Q 29aA==
MIME-Version: 1.0
Received: by 10.152.123.103 with SMTP id lz7mr2244122lab.21.1348165847663; Thu, 20 Sep 2012 11:30:47 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.91.33 with HTTP; Thu, 20 Sep 2012 11:30:47 -0700 (PDT)
In-Reply-To: <5059E240.8040702@gulbrandsen.priv.no>
References: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.com> <5059E240.8040702@gulbrandsen.priv.no>
Date: Thu, 20 Sep 2012 14:30:47 -0400
X-Google-Sender-Auth: ume0gzkK2nKDUxmbVSu9wryrjYc
Message-ID: <CAC4RtVCqB5GDXmyi1TDE-B+dBbJaN7veM15GfGD+eNk+VNyAUQ@mail.gmail.com>
Subject: Re: Gen-ART LC Review of draft-ietf-eai-simpledowngrade-07
From: Barry Leiba <barryleiba@computer.org>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-eai-simpledowngrade.all@tools.ietf.org, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2012 18:30:50 -0000

>> -- Abstract should mention that this updates 3501
>
> Really? A detail of this document updates a minor detail of that document,
> that's hardly what I would expect to see in a single-paragraph summary.
>
> I know someone who likes to repeat the Subject in the first line of the
> email body text. Just in case I didn't see it the first time, I suppose.

There's no need to be flippant; this is called out by the idnits
program, and Ben is highlighting it.  It's not a big deal, but there
are reasons for it:

1. The "updates" (and "obsoletes") information is not in the text of
the published RFC, but is part of the RFC's metadata.  Not everyone
who will look at the RFC will see the metadata.  Some will see only
Title and Abstract.  And so on.  It's not just frivolity to put
something in the Abstract.

2. We also like to have an *explanation* in the Introduction, saying
why a document updates another.  For that part, it's not just "This
document updates RFC 3501," but "This document updates RFC 3501
because it adds [this] and changes [that]."

Barry

From ned+ietf@mauve.mrochek.com  Thu Sep 20 11:52:34 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F97921E808B for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 11:52:34 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DtE5JJ84WZeA for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 11:52:28 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id C596A21E804B for <ietf@ietf.org>; Thu, 20 Sep 2012 11:52:28 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OKH7IR4BFK00AG95@mauve.mrochek.com> for ietf@ietf.org; Thu, 20 Sep 2012 11:47:26 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=windows-1252; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJFFFOH4280006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 20 Sep 2012 11:47:23 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OKH7IPJ5E00006TF@mauve.mrochek.com>
Date: Thu, 20 Sep 2012 11:30:38 -0700 (PDT)
Subject: Re: Gen-ART LC Review of draft-ietf-eai-simpledowngrade-07
In-reply-to: "Your message dated Wed, 19 Sep 2012 17:18:24 +0200" <5059E240.8040702@gulbrandsen.priv.no>
References: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.com> <5059E240.8040702@gulbrandsen.priv.no>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-eai-simpledowngrade.all@tools.ietf.org, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2012 18:52:34 -0000

> On 09/19/2012 04:24 AM, Ben Campbell 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-eai-simpledowngrade-07
> > Reviewer: Ben Campbell
> > Review Date: 2012-09-18
> > IETF LC End Date: 2012-09-20
> >
> > Summary: This draft is mostly on the right track, but has open issues
> >
> > Major issues:
> >
> > -- I'm concerned about the security considerations related to having a
> > mail drop modify a potentially signed message.
> ...

> Hm, sounds like a misunderstanding. Did you understand that the
> modification happens in RAM, and that the message stored unmodified and
> has the valid signature? If not I suppose extra verbiage is needed.

I think this is already pretty clear: The texts says things like "present"
and "serve". It takes a pretty deliberate misreading to miss those words.

Moreover, stating that this "happens only in RAM" may not be correct. A server
could choose to store a downgraded version so it doesn't have to be rerendered,
for example. The point is that version isn't going to be presented to a client
that supports EAI, not that it only happens in RAM.

> The signature issue has been discussed. The answer is more or less: The
> WG expects EAI users to use EAI-capable software, and to accept partial
> failure when using software that cannot be updated.

> This entire draft is draft is about damage limitation when an EAI user
> uses EAI-ignorant software (e.g. your phone, if you do your main mail
> handling on a computer but occasionally look using the phone). That
> there will be damage is expected and accepted. IMO it's unavoidable.

I think that's more a matter of fact, not opinion. If your software is
incapable of presenting something, it's incapable of presenting something.
The only question is whether you get a downgraded version the software is
capable of handling or nothing. EAI allows that choice to be made by
the implementation or operationally.

> > Minor Issues:
> >
> > -- It's not clear to me why this is standards track rather than informational.

> I don't remember. Perhaps because it needs to update 3501.

> > -- section 3, 2nd paragraph:
> >
> > Are there any limits on how much the size can differ from the actual delivered message? Can it be larger? Smaller? It's worth commenting on whether this could cause errors in the client. (e.g. Improper memory allocation)

> An input message can be constructed to make the difference arbitrarily
> large. For instance, just add an attachment with a suggested filename of
> a million unicode snowmen, and the surrogate message will be several
> megabyte smaller than the original. Or if you know that the target
> server uses a long surrogate address format, add a million short Cc
> addresses and the surrogate will be blown up by a million long CC addresses.

> I doubt that this is exploitable. You can confuse or irritate the user
> by making the client say "downloading 1.2MB" when the size before
> download was reported as 42kb, that's all. I wish all my problems were
> as small.

If it's exploitable it almost certainly is what I refer to as the "tiny twig on
the attack tree". That is, if there's a size-related issue there are going to
be much easier ways to exploit it than this.

I suppose some folks may believe that describing these sorts of twigs is 
valuable. I disgree and believe it to be unncesssary clutter that is likely to
end up detracting from overall security.

> I'll add a comment and a reminder that the actual size is supplied along
> with the literal during download.

> > -- "Open Issues" section: "Should Kazunori Fujiwara’s downgrade document also mention DOWNGRADED?"
> >
> > Good question. It seems like they should be consistent on things like this. (This is really more a comment on that draft than this one.)

> I think I've made up my mind that in this case it doesn't matter.
> Kazunori's task is complex reversible downgrade and has the Downgraded-*
> header fields, why then bother with the DOWNGRADED response code? But
> it's not my decision.

I agree it doesn't matter.

> > -- Abstract should mention that this updates 3501

> Really? A detail of this document updates a minor detail of that
> document, that's hardly what I would expect to see in a single-paragraph
> summary.

Exactly right. This is a silly thing to do.

> I know someone who likes to repeat the Subject in the first line of the
> email body text. Just in case I didn't see it the first time, I suppose.

The policy for EAI documents, which was agreed to by the working group and
which is now reflected in a number of RFCs, is not to put this sort of nonsense
in the abstract.

				Ned

From chair@ietf.org  Thu Sep 20 12:00:02 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24BF721F8712; Thu, 20 Sep 2012 12:00: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DwAtefrOVlQ; Thu, 20 Sep 2012 12:00:01 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 789AC21F8670; Thu, 20 Sep 2012 12:00:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 6CFCB12CC87; Thu, 20 Sep 2012 12:00:01 -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 gb8IDNwJ+9Uv; Thu, 20 Sep 2012 12:00:01 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id D403612CC85; Thu, 20 Sep 2012 12:00:00 -0700 (PDT)
Subject: Bits-N-Bites Sponsors Needed for Atlanta
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <AACFEBDA-32AE-4EBE-BA33-098C57D0CA06@vigilsec.com>
Date: Thu, 20 Sep 2012 14:59:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2E2F587-35E4-4222-AC26-FDC0F65A203B@ietf.org>
References: <DE4124BA-DD93-402C-9ACE-6FA00D9A9CC9@isoc.org> <11724634-145D-4DB9-A8FB-F4737E246DF6@gmail.com> <19B867F4-E3E6-4DBC-AFDF-411DF63E20DE@isoc.org> <BB1F3D21-1A95-4333-B1E6-C1E7EAF462C4@gmail.com> <349E9555-336D-4C18-8A01-A5CBBFE5598B@isoc.org> <6F50A7D4-A3F3-45B5-A6CB-A52AE67CE853@gmail.com> <E4AB856A-1509-41A3-AAF1-54CC2C2933AA@isoc.org> <AACFEBDA-32AE-4EBE-BA33-098C57D0CA06@vigilsec.com>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>, Drew Dvorshak <dvorshak@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2012 19:00:02 -0000

We are seeking sponsors for the Bits-N-Bites event at IETF 85 in =
Atlanta.

This is a fairly new community networking experimental event; the first =
Bits-N-Bites took place in at IETF 84 in Vancouver.  The Inaugural =
Sponsors in Vancouver were Juniper, Huawei, ICANN, IPSO Alliance, and =
the Internet Society. People had a good time, and the sponsor tables =
were busy throughout the event.

Bits-N-Bites will bring together IETF participants, with exhibitors, =
product vendors, and service providers to share information, and =
showcase products and services in a social setting with food and drink.  =
Participants have an opportunity to network, speak with the sponsors, =
and enjoy the complimentary beer, wine, and hors d'oeuvres. =20

Bits-N-Bites will be held Thursday evening, November 8th, from 7:00 - =
9:00 PM at the meeting hotel.

Sponsorship tables are still available!  For more information see =
<http://www.ietf.org/meeting/85/bits-n-bites.html> and contact Drew =
Dvorshak at dvorshak@isoc.org.

  Russ Housley
  IETF Chair

  Bob Hinden
  IAOC Chair


From ben@estacado.net  Thu Sep 20 12:33:13 2012
Return-Path: <ben@estacado.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 5C5CA21F84B5; Thu, 20 Sep 2012 12:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ODTsuxmkI+BB; Thu, 20 Sep 2012 12:33:12 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 0170321F84B2; Thu, 20 Sep 2012 12:33:11 -0700 (PDT)
Received: from [10.0.1.3] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q8KJX5Kk029778 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Sep 2012 14:33:09 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: Gen-ART LC Review of draft-ietf-eai-simpledowngrade-07
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <E8CE99257EB153D5FEF25432@JcK-HP8200.jck.com>
Date: Thu, 20 Sep 2012 14:33:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F8B4B02-4617-48CF-A03D-B24F167B1925@estacado.net>
References: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.com> <E8CE99257EB153D5FEF25432@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1498)
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-eai-simpledowngrade.all@tools.ietf.org, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2012 19:33:13 -0000

Hi John, thanks for the response. Comments inline:

On Sep 19, 2012, at 3:45 AM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Tuesday, September 18, 2012 21:24 -0500 Ben Campbell
> <ben@nostrum.com> wrote:
>=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-eai-simpledowngrade-07
>> Reviewer: Ben Campbell
>> Review Date: 2012-09-18
>> IETF LC End Date: 2012-09-20
>>=20
>> Summary: This draft is mostly on the right track, but has open
>> issues
>>=20
>> Major issues:
>>=20
>> -- I'm concerned about the security considerations related to
>> having a mail drop modify a potentially signed message. The
>> draft mentions that this is an issue. I think more discussion
>> is warranted. In particular. What client behavior is expected
>> when a signature is invalidated due to downgrading? I suspect
>> the answer is "warn the user, who will most likely just click
>> through without understanding the issue." I'm concerned about
>> adding yet another reason to train end users to ignore
>> security warnings. OTOH, should the mail drop strip out
>> signatures? That has it's own issues. I'm not saying that I
>> know the answer--merely that it's not clear to me that it has
>> been sufficiently explored.
>=20
> Ben,
>=20
> I want to respond as WG Co-chair to this one issue.  Comments on
> your minor issues will follow, but please be assured that the
> non-editorial ones (and even some of those) have been discussed
> extensively in the WG.
>=20
> There is a fundamental issue that runs across the four
> documents, that the WG discussed extensively, and that the WG
> believes is adequately described.  The WG made an explicit
> decision to not repeat that explanation at every possible point
> and in each document.  It explicitly chose overall brevity over
> repetition partially in the belief that repeating the material
> might cause important comments or requirements to get lost in
> the noise.  At the same time, it is easy to lose sight of the
> issue and its implications when reviewing the documents.  It
> actually becomes very clear when one starts considering
> implementation details.
>=20
> That issue is that a upgraded IMAP or POP server may find itself
> in possession of an message that requires SMTPUTF8 ("EAI")
> capability, that it may be one message of that type among many
> messages with ACSCII-only headers that do not require that
> capability, and that it may find itself connected to by a legacy
> client.  There are two important things about that case:
>=20
> 	* There is absolutely no way to deliver the problem
> 	message to the client.  The IMAP and POP specifications,
> 	and the basic email transport and header specifications
> 	from which their provisions are derived, are absolutely
> 	clear that addresses and header fields are in ASCII
> 	(IMAP allows for the use of some alternate character
> 	sets and encodings, but that turns out to be a bad
> 	choice in this case and, fwiw, conversion to use any of
> 	them would also invalidate signatures.
> =09
> 	* There are no provisions in POP or IMAP for the server
> 	to say to the client "this particular message fails
> 	within the range you have specified, but cannot be
> 	delivered to you" (much less why that is the case).  In
> 	principle, EAI could have added such capabilities but
> 	they would not haved helped legacy clients (that, by
> 	definition, didn't implement them), would have added
> 	clutter to the protocols, and would not have benefited
> 	upgraded clients either (because it is easier to just
> 	support UTF-8 headers and other requirements.
>=20
> Given that situation, the POP or IMAP server can choose to do
> any of a range of things, all of them bad news.  Two of the
> choices are to _replace_ the original message with a substitute
> (or "synthetic" or "surrogate") message that provides the user
> of the client some more or less good hints  about what is going
> on and what the original message was about.  What is being
> delivered is not the original message.  If the original
> contained non-ASCII addresses, the surrogate will not be able to
> represent them directly and will, in general, not be reply-able.
> Expecting an integrity check on the original message to be valid
> with the surrogate one is unreasonable; indeed, one would be
> very concerned if such a check (signature-based or otherwise)
> did validate. =20

I understand this part, and I think the general "no satisfactory =
solution other than a forklift upgrade" problem is reasonably we doll =
expressed. My personal feelings are that downgrading is likely to cause =
more harm than good--but I'm willing to accept that the working group is =
in a "can't please everyone (if anyone)" situation, and  considered it a =
reasonable enough option to document it. But... (see next)


>=20
> When there is an integrity check present, perhaps the Right
> Thing would be to disable it and include a note in the surrogate
> message that indicates that the original contained such a check.
> The wording was intended to allow for that option when it is
> deemed appropriate and feasible by the server's designers and
> operators.  But remember that there are undetectable cases (not
> covered specifically by IETF standards) such as when the
> signature or equivalent information is transmitted out of band.
>=20
> The net result of this is that saying much more in the Security
> Considerations section would be likely to be misleading,
> covering some cases and not others.  And, to answer your
> specific question above, the WG did consider the issue and the
> various cases and alternatives, and did so at great length.

I have trouble seeing how discussing the known issues (including the =
out-of-band one you just mentioned) would be misleading. I realize the =
wg can't come up with one-size-fits-all guidance. But one of the =
purposes of the security considerations is to document issues that =
implementors and deployers need to think about, even if it doesn't tell =
them the answers.=20

I'm mostly agnostic about where this sort of information goes. 5738bis =
does mention the potential problem, but offers little guidance beyond =
"extreme care". I do see some value in putting it in the drafts that =
actually talk about the details of modifying content.

>=20
> The complexity of the situation also explains the choice of
> standards track for the two downgrade specs.  On the one hand,
> as you note, the POP and IMAP specs are written primarily from
> the standpoint of an upgraded server talking to an upgraded
> client.  We expect that to be the long-term situation and it is
> the right way to write the specs given that situation.  Because
> of the many options as to what to do in this transitional case,
> a normative reference to one or more specific ones would have
> been inappropriate.   On the other hand, while the two
> strategies represented by popimap-downgrade and simpledowngrade
> are believed by the WG to be self-consistent and adequate given
> the assumptions identified for them, there are _many_ ways to
> get things wrong (some of which the WG discovered only after
> considerable discussion).  The only way we have to clearly say
> "if you are going to make these decisions and assumptions, then
> implement downgrading this way" is by putting those documents on
> standards track. =20

My concern here is that 5738bis doesn't really say that. It take more =
the approach of saying "you really should forklift upgrade. Really. We =
mean it. But if you must do downgrading, where's some =
examples[informational references]" If the downgrade docs are really to =
be considered standards, then wouldn't it make more sense to treat these =
as a normative reference, and strengthen the language to say "if you =
must do downgrades, here are the two best alternative approaches =
[Normative Reference]"? I further note that 5721bis has a normative =
reference to section 7 of 5738bis for this very purpose, but that's =
diluted by lack of normative reference do the downgrade drafts in =
5738bis.

>=20
> As I hope it clear from the above, the WG has strong consensus
> that the only correct and completely adequate solution to the
> problem of an upgraded server interacting with a legacy client
> over a message that requires those upgraded capabilities is to
> avoid having the problem occur by getting an upgraded client.
> We could write more explicit applicability language to say that,
> but, IMO and that of the WG, it wouldn't contribute anything.

Now, that argues the exact opposite than the previous paragraph, doesn't =
it? That points more to like "you really shouldn't downgrade. But if you =
must, here's some example approaches", and making the downgrade docs =
informational. (For that matter, since the only consumers of downgraded =
content will be clients that don't implement these drafts, is there any =
reason to standardize downgrading at all? We're not talking about =
interoperability here, are we?)

>=20
> best,
>   john
>=20


From sm@resistor.net  Thu Sep 20 12:35:17 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A9DC21F84B6 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 12:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2fArcCuz+PC8 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 12:35:16 -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 41DD321F84D7 for <ietf@ietf.org>; Thu, 20 Sep 2012 12:35:16 -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 q8KJZAck020423; Thu, 20 Sep 2012 12:35:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1348169715; bh=lMmdnFtIRtzii41veB/nD4ljxnyJuhVo5IXRH7DXIKE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=s3IfrxrvxCogv21zjWa3baK71ExnVLCV6jaPVqbdPrTyLY9k+W9Z7rRJihGNyekTm xyRCF8Y3AQqwmeULCR1OOzSxmL7HfPFRVDXc9ICunQFERWADVZYIfaRh9q5GmA1NiQ 8eRQlJ0HX7LgbozA6i8kQn1YtqnSI2FuSuh6FWPs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1348169715; i=@resistor.net; bh=lMmdnFtIRtzii41veB/nD4ljxnyJuhVo5IXRH7DXIKE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HrVbv6CqJOxe7KzqrNdbSlELotMpLiBYJ5VZtGvjThPpFVZCqIhda2vmxWNo+5yK9 S+Pc46YFpvOh4CBfazyYNTvthukd2rZpRVfRFkOCaqw+VctjjG/fc5wKJai5cLLRIH q8o4SuiALmmZS4ElI3lqF4w0nWmVdGUWWkKYD//U=
Message-Id: <6.2.5.6.2.20120920121208.0a164868@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 20 Sep 2012 12:22:12 -0700
To: Carsten Bormann <cabo@tzi.org>
From: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <243065D9-3A39-4DD3-8BCA-371935FCA228@tzi.org>
References: <20120919182443.74080.qmail@joyce.lan> <505A2B08.70805@isi.edu> <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org> <07A7151E396F3AAA85F4A53F@JcK-HP8200.jck.com> <243065D9-3A39-4DD3-8BCA-371935FCA228@tzi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 20 Sep 2012 19:35:17 -0000

Hi Carsten,
At 10:28 20-09-2012, Carsten Bormann wrote:
>We just had a consensus call in one WG on adopting a draft that at 
>this time had been expired for a year.
>The chairs didn't notice, because the URI was stable (as it should be).

Send a message with a subject line of Resurrect I-D file to internet-drafts@.

Regards,
-sm 


From ben@estacado.net  Thu Sep 20 12:44:07 2012
Return-Path: <ben@estacado.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 0EBF721F86A3; Thu, 20 Sep 2012 12:44: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAhozxOZ3-Pt; Thu, 20 Sep 2012 12:44:06 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC0B21F86A2; Thu, 20 Sep 2012 12:44:05 -0700 (PDT)
Received: from [10.0.1.3] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q8KJi0xM031178 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Sep 2012 14:44:05 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: Gen-ART LC Review of draft-ietf-eai-5738bis-09
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <C5852787C87923CBA226D36A@JcK-HP8200.jck.com>
Date: Thu, 20 Sep 2012 14:44:00 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A44DB6C-3A5C-4BB1-BCAC-A939EB4E0148@estacado.net>
References: <2549BC7F-FD4D-4D65-817F-98833573D899@nostrum.com> <C5852787C87923CBA226D36A@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1498)
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, draft-ietf-eai-5738bis.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: Thu, 20 Sep 2012 19:44:07 -0000

On Sep 19, 2012, at 6:53 AM, John C Klensin <john-ietf@jck.com> wrote:

> Following up on my earlier note about a comment from you that
> really applies to the strategy on which all four documents are
> really based...
>=20
> --On Tuesday, September 18, 2012 20:44 -0500 Ben Campbell
> <ben@nostrum.com> wrote:
>=20
>> ...
>> Along the same lines, section 7 seems to go to lengths to
>> illustrate why downgrading is somewhere between hard and
>> problematic. Do we really believe that downgrading will ever
>> be the "least bad"?
>=20
> As compared to what, Ben? =20

(I assume that to be rhetorical :-) )

> One alternative is to not support delivery of SMTPUTF8 messages
> at all except in environments in which it can be guaranteed that
> all IMAP and POP clients that might contact the servers are
> already upgraded.  It is operationally possible to make that
> guarantee in a few scenarios, but they are rare.   In those
> scenarios, many people in the WG would say "do that" (easily
> managed by not having the delivery servers accept SMTPUTF8
> messages until the POP/IMAP client upgrades are complete).
> But, for all of the more usual cases in which the IMAP/POP
> server operator cannot control exactly what clients might be
> used, the only alternate is to not allow such messages, ever.
> We don't think that is a desirable choice (or we wouldn't have
> done the work in the WG) but nothing in these protocols require
> that anyone deploy i18n mail.
>=20
> For the other alternatives, yes, downgrading --by one of these
> scenarios or some other one-- is, indeed, likely to be "less
> bad" than others in some operational scenarios.   In particular,
> one alternate is for the server to silently delete all messages
> requiring SMTPUTF8 (EAI) capability if a client connects that
> doesn't support the needed capability.  If only because the user
> might later come back with a more capable client (or a message
> access mechanism that doesn't use a POP or IMAP client at all),
> that messaging-deleting alternative is almost certainly the
> worst option of all, making almost anything else "less bad".
>=20
> And, again, yes the WG discussed these issues at length, perhaps
> even ad nauseam.

I'm willing to accept that the work group decided this was the best that =
could be done. My concern is that the current situation (5721bis =
normatively [with a MUST] references 5738 bis, which informatively =
references the downgrade drafts (as examples), which are themselves =
standards track) seems internally inconsistent.=20

>=20
>    john
>=20
>=20


From ben@estacado.net  Thu Sep 20 12:58:39 2012
Return-Path: <ben@estacado.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 E7D3421F86AA; Thu, 20 Sep 2012 12:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KsIVdQWRQ4-P; Thu, 20 Sep 2012 12:58:39 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id E8DD621F869F; Thu, 20 Sep 2012 12:58:38 -0700 (PDT)
Received: from [10.0.1.3] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q8KJwWpi033574 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Sep 2012 14:58:36 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: Gen-ART LC Review of draft-ietf-eai-simpledowngrade-07
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <5059E240.8040702@gulbrandsen.priv.no>
Date: Thu, 20 Sep 2012 14:58:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D78F06B7-6359-4500-89B4-579060B2C852@estacado.net>
References: <74115521-D2B3-419B-9571-660D16F06BB1@nostrum.com> <5059E240.8040702@gulbrandsen.priv.no>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
X-Mailer: Apple Mail (2.1498)
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-eai-simpledowngrade.all@tools.ietf.org, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2012 19:58:40 -0000

Thanks for the response--comments inline:

On Sep 19, 2012, at 10:18 AM, Arnt Gulbrandsen =
<arnt@gulbrandsen.priv.no> wrote:

> On 09/19/2012 04:24 AM, Ben Campbell wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>=20
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>  .
>>=20
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>=20
>> Document:  draft-ietf-eai-simpledowngrade-07
>> Reviewer: Ben Campbell
>> Review Date: 2012-09-18
>> IETF LC End Date: 2012-09-20
>>=20
>> Summary: This draft is mostly on the right track, but has open issues
>>=20
>> Major issues:
>>=20
>> -- I'm concerned about the security considerations related to having =
a mail drop modify a potentially signed message.
> ...
>=20
> Hm, sounds like a misunderstanding. Did you understand that the =
modification happens in RAM, and that the message stored unmodified and =
has the valid signature? If not I suppose extra verbiage is needed.

I make no assumptions about whether the modification is persistent in =
the mail drop. The message as delivered to the client, which is where =
the end user actually reads it, is modified.

>=20
> The signature issue has been discussed. The answer is more or less: =
The WG expects EAI users to use EAI-capable software, and to accept =
partial failure when using software that cannot be updated.

My point is that I believe the potential issues caused by the =
modification of signed content should be covered in more depth. You =
mention the problem, which is good.  I'm not proposing normative =
guidance, but there's a lot an implementor and deployer should think =
before breaking signed content.=20

For example, could they strip signatures? Put in warnings that explain =
the reason a signature cannot be verified? Verify locally and resign the =
modified version (along with a statement about what happened)? Ignore =
the problem because their users never do S/MIME anyway? Even if the =
draft offers no answers, I think it needs to offer more guidance about =
issues that the reader needs to think about and draw conclusions from.

>=20
> This entire draft is draft is about damage limitation when an EAI user =
uses EAI-ignorant software (e.g. your phone, if you do your main mail =
handling on a computer but occasionally look using the phone). That =
there will be damage is expected and accepted. IMO it's unavoidable. The =
WG tries to ensure that the damage is not permanent (in the same =
example: so you can still read the mail, properly signed and addressed, =
on your computer).
>=20
> FWIW, I mangled a message by hand to see what happened to a signature, =
and got an angry-looking complaint above the body text. Or maybe it was =
above the headers. Whatever.
>=20
>> Minor Issues:
>>=20
>> -- It's not clear to me why this is standards track rather than =
informational.
>=20
> I don't remember. Perhaps because it needs to update 3501.

Ah, that's a better explanation than I've seen so far :-)

>=20
>> -- section 3, 2nd paragraph:
>>=20
>> Are there any limits on how much the size can differ from the actual =
delivered message? Can it be larger? Smaller? It's worth commenting on =
whether this could cause errors in the client. (e.g. Improper memory =
allocation)
>=20
> An input message can be constructed to make the difference arbitrarily =
large. For instance, just add an attachment with a suggested filename of =
a million unicode snowmen, and the surrogate message will be several =
megabyte smaller than the original. Or if you know that the target =
server uses a long surrogate address format, add a million short Cc =
addresses and the surrogate will be blown up by a million long CC =
addresses.
>=20
> I doubt that this is exploitable. You can confuse or irritate the user =
by making the client say "downloading 1.2MB" when the size before =
download was reported as 42kb, that's all. I wish all my problems were =
as small.
>=20
> I'll add a comment and a reminder that the actual size is supplied =
along with the literal during download.
>=20

Thanks--It's been a while since I worried about IMAP protocol details. =
The fact that the actual downloaded content size is expressed elsewhere =
makes this less of a concern. (And adding the proposed reminder would =
help other's avoid the same mistake :-)  )

>> -- "Open Issues" section: "Should Kazunori Fujiwara=92s downgrade =
document also mention DOWNGRADED?"
>>=20
>> Good question. It seems like they should be consistent on things like =
this. (This is really more a comment on that draft than this one.)
>=20
> I think I've made up my mind that in this case it doesn't matter. =
Kazunori's task is complex reversible downgrade and has the Downgraded-* =
header fields, why then bother with the DOWNGRADED response code? But =
it's not my decision.

Do you consider the open issue called out in the draft to be resolved, =
then?

OTOH, this highlights a concern I didn't think about when reviewing the =
other draft, which is a user agent unaware of the UTF8 updates is =
unlikely to present new, unknown headers to the end user. I don't know =
if the error code is more likely to be presented. (I will comment on =
that in the thread specific to that draft.)


>=20
>> -- Abstract should mention that this updates 3501
>=20
> Really? A detail of this document updates a minor detail of that =
document, that's hardly what I would expect to see in a single-paragraph =
summary.
>=20
> I know someone who likes to repeat the Subject in the first line of =
the email body text. Just in case I didn't see it the first time, I =
suppose.

It's standard RFC editor procedure. The abstract is often presented =
separate from the rest of the draft, and the draft headers.

[...]


From ben@nostrum.com  Thu Sep 20 13:03:43 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4FCD21F86B8; Thu, 20 Sep 2012 13:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1w1g4eK-lebF; Thu, 20 Sep 2012 13:03:43 -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 D5D4421F86B7; Thu, 20 Sep 2012 13:03:42 -0700 (PDT)
Received: from [10.0.1.3] (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 q8KK3dSw052182 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Sep 2012 15:03:39 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: Gen-ART LC Review of draft-ietf-eai-popimap-downgrade-07
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <0E190012-B2A0-4F52-9BC0-ED32E803440B@nostrum.com>
Date: Thu, 20 Sep 2012 15:03:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C26E2EBF-7D73-434B-A05A-0B2EB5F9F6DD@nostrum.com>
References: <0E190012-B2A0-4F52-9BC0-ED32E803440B@nostrum.com>
To: draft-ietf-eai-popimap-downgrade.all@tools.ietf.org
X-Mailer: Apple Mail (2.1498)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2012 20:03:44 -0000

Hi,

Email discussion about the simple downgrade draft made me think of a =
concern that I think I failed to mention in my review. In particular, =
the "tunneling" mechanism allows the creation of several new =
"Downgraded-*" header fields containing encoded content from the =
original message. Given that downgraded messages are primarily to be =
consumed by legacy clients, which we can assume do not know anything =
about this draft, why would we expect the clients to present those =
headers to the user, or otherwise notify the user of their existence?

Thanks!

Ben.


On Sep 18, 2012, at 9:15 PM, Ben Campbell <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq> .
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-eai-popimap-downgrade-07
> Reviewer: Ben Campbell=09
> Review Date: 2012-09-18
> IETF LC End Date: 2012-09-20
>=20
> Summary: This draft is mostly on the right track, but has open issues
>=20
> Major issues:
>=20
> -- I'm concerned about the security considerations related to having a =
mail drop modify a potentially signed message. The draft mentions that =
this is an issue. I think more discussion is warranted. In particular. =
What client behavior is expected when a signature is invalidated due to =
downgrading? I suspect the answer is "warn the user, who will most =
likely just click through without understanding the issue." I'm =
concerned about adding yet another reason to train end users to ignore =
security warnings. OTOH, should the mail drop strip out signatures? That =
has it's own issues. I'm not saying that I know the answer--merely that =
it's not clear to me that it has been sufficiently explored.
>=20
> [Note: The same issue is there for draft-ietf-eai-simpledowngrade]
>=20
> Minor issues:
>=20
> -- It's not clear to me why this is standards track rather than =
informational. As far as I can tell, it's mainly used by the IMAP UTF8 =
capability draft. But that draft seems to list this as an example of =
something you can do, and lists it as an informational reference.
>=20
> --  draft-ietf-eai-simpledowngrade proposes to register a "DOWNGRADED" =
response code. It seems like that should be used by both or neither =
downgrade draft. (This is mentioned as an open issue in =
draft-ietf-eai-simpledowngrade).
>=20
> Nits/editorial comments:
>=20
> -- General:=20
>=20
> As far as I can tell, this draft and draft-ietf-eai-simpledowngrade =
offer two alternatives to solve the same problem. Unfortunately they are =
very different in structure and terminology. It would make life easier =
for the reader if they were more consistent with one-another.
>=20
> I found the structure hard to read in places. In particular, the =
mixing of imperative sentences  in paragraph form with complicated =
conditions made it easy to get lost. Either a more descriptive vs =
imperative style, or breaking things down more into (numbered or =
bulleted) steps might make it easier to read.=20
>=20
> -- 1.1:
>=20
> It would be helpful to be more explicit about what is meant by "legacy =
clients". Am I correct to assume it means clients that do not support =
the UTF8 capabilities in the relevant drafts from this workgroup?
>=20
> -- 1.3, 2nd paragraph
>=20
> s/ "unknown/broken" / "unknown or broken"
>=20
> -- 3.1.8, 1st paragraph: " If the <local-part> of the <mailbox> =
element does not contain non-ASCII characters, the <domain> element =
contains non-ASCII characters."
>=20
> This appears to say that if the local part has no non-ASCII =
characters, then the domain part does. Is that the intent? I.e. there is =
no possibility that neither has non-ASCII chars?
>=20
> -- 3.1.8, 2nd paragraph: "... the model above."
>=20
> Please reference the section number.
>=20
> -- 3.2.1:
>=20
> Jumping right into the header field list without any preamble is =
rather abrubt.
>=20
> --3.2.1: First paragraph after the header field list: " Optionally add =
those words where appropriate to the next paragraph, but I think once =
will make it clear."
>=20
> I assume this was an internal comment meant to be deleted?
>=20
> -- 3.2.9: 2nd paragraph: "Perform <UNSTRUCTURED> downgrading."
>=20
> Is there a condition missing here? (The structure of 3.2.9 is =
confusing in general--the paragraphs feel out of order.)
>=20
> -- 5:=20
>=20
> Nothing for content-type?
>=20
> -- 6, 1st paragraph: "But they still contain MIME-encapsulated header =
fields that contain non-ASCII strings."
>=20
> Is that always true?
>=20
> -- 6, 4th paragraph: "Receivers may know they need to update their =
MUAs, or they don=92t care."
>=20
> I don't get the point of this sentence.
>=20
> -- 8, 1st paragraph: "Please change "should now be" and "should be" to =
"have been""
>=20
> It's probably not worth changing at this point, but I suggest in =
general writing the words you want to see in the RFC. With all due =
respect to the apparent super powers of the RFC editor staff, asking =
them to change things unnecessarily creates opportunities for error.
>=20
> -- 8, 2nd paragraph: "However [RFC6530] obsoleted [RFC5504] and this =
document does not use all "Downgraded-" header fields registered by =
[RFC5504]."
>=20
> ... And therefore what? I sounds like you expect the reader to draw a =
conclusion--better to spell it out.


From simon@josefsson.org  Thu Sep 20 15:15:27 2012
Return-Path: <simon@josefsson.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 E4C2921E80A5; Thu, 20 Sep 2012 15:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.871
X-Spam-Level: 
X-Spam-Status: No, score=-99.871 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wwlk+HzrPYSe; Thu, 20 Sep 2012 15:15:27 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id C046521E803C; Thu, 20 Sep 2012 15:15:25 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q8KMFGUq029866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 21 Sep 2012 00:15:18 +0200
From: Simon Josefsson <simon@josefsson.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes	for the GSS-API EAP mechanism) to Proposed Standard
References: <20120920141717.4821.29598.idtracker@ietfa.amsl.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120920:ietf@ietf.org::ZJ9qPi94zPtEvUGQ:1PaJ
X-Hashcash: 1:22:120920:abfab@ietf.org::duoE3tSFmeVx7mLe:8yI+
X-Hashcash: 1:22:120920:ietf-announce@ietf.org::9XbAlBcDeESGZQnu:JkTn
Date: Fri, 21 Sep 2012 00:15:16 +0200
In-Reply-To: <20120920141717.4821.29598.idtracker@ietfa.amsl.com> (The IESG's message of "Thu, 20 Sep 2012 07:17:17 -0700")
Message-ID: <87fw6c9w97.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: abfab@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Sep 2012 22:15:28 -0000

I found no major issues with this document.  I support publishing it if
the minor issues below are resolved.  The document is written in a
rather information dense style, but I can't come up with any easy way to
make it more accessible.  More examples and illustrations would help,
but I don't see this as sufficient reason to not move forward.

/Simon

Minor issues:

   The naming extensions [I-D.ietf-kitten-gssapi-naming-exts]to the
                                                             ^
insert SPC

   mechanism allows an Authentication/Authorization/Accounting peer to
                                                              ^
...
   [I-D.ietf-abfab-gss-eap] allows an Authentication/Authorization/
   Accounting peer to provide authorization attributes along side an
             ^
add '(AAA)'.  Otherwise the AAA acronym is not expanded.

   The first is a URI describing the format of the name.  The second
                  ^^^
Expand acronym on first use.

   The first is a URN indicating that the name is a SAML attribute and
                  ^^^
Expand acronym on first use.

   context Section 4 are issued by the same party performing the
          ^         ^
I believe parenthesis should be inserted here.

   information is combined from AAA and SAML sources.  The SAML IDP and
                                                                ^^^
Expand acronym on first use.

   GSS_S_COMPLETE.  Attributes MAy be absent or values MAY change in
                                 ^
Typo.

   value of this attribute would first wait until GSS-
                                                  ^^^^
   _Accept_sec_Context returned GSS_S_COMPLETE.  Then the application
   ^^^^^^^^^^^^^^^^^^^
Typo, should be 'GSS_Accept_sec_context'.  Check this throughout the
document, there are more incorrect uses.

   GSS_Get_Name_attribute passing this name and an attribute of
           ^
Typo, should be 'GSS_Get_name_attribute'.  Check this throughout the
document, there are more incorrect uses.

   This attribute is returned with the authenticatedoutput of
                                                    ^
Typo.

   assertion, then An attribute with the name
                   ^
Typo.

   "urn:ietf:params:gss:federated-saml-attribute
   urn:oasis:names:tc:SAML:2.0:attrname-format:uri
   urn:oid:1.3.6.1.4.1.5923.1.1.1.7 " could be returned from
                                   ^
Should there really be a SPC at the end?  It is also not clear that
there is a SPC between the parts since they terminate the line.

   GSS_Inquire_Name.  If an application calls GSS_Get_Name_attribute
               ^
Typo, 'GSS_Inquire_name' (and 'GSS_Get_name_attribute'...).

   If the value is not simple or is empty, then the raw value(s) of the
   GSS name attribute MUST be the well-formed serialization of the
   <saml:AttributeValue> element(s) encoded as UTF-8.  The "display"
   values are implementation-defined.

Question: what serialization is intended here?  An example here would
make this more clear.

   mechanisms are permitted to perform local policy checks on SAML
   ^
Typo, capitalize to 'M'.

   choices for non-IETf work.  Expert review is permitted mainly to
                      ^
Typo.

From narten@us.ibm.com  Thu Sep 20 21:53:25 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFD8521F85F9 for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 21:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.024
X-Spam-Level: 
X-Spam-Status: No, score=-110.024 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3gtOXUbiCP3i for <ietf@ietfa.amsl.com>; Thu, 20 Sep 2012 21:53:25 -0700 (PDT)
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.145]) by ietfa.amsl.com (Postfix) with ESMTP id BA62E21F85FC for <ietf@ietf.org>; Thu, 20 Sep 2012 21:53:24 -0700 (PDT)
Received: from /spool/local by e5.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, 21 Sep 2012 00:53:16 -0400
Received: from d01relay06.pok.ibm.com (9.56.227.116) by e5.ny.us.ibm.com (192.168.1.105) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 21 Sep 2012 00:53:05 -0400
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q8L4r4lj33358042 for <ietf@ietf.org>; Fri, 21 Sep 2012 00:53:04 -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 q8L4r4cC028731 for <ietf@ietf.org>; Fri, 21 Sep 2012 01:53:04 -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 q8L4r35R028697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 21 Sep 2012 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 q8L4r3P1014586 for <ietf@ietf.org>; Fri, 21 Sep 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q8L4r3eC014562 for ietf@ietf.org; Fri, 21 Sep 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201209210453.q8L4r3eC014562@rotala.raleigh.ibm.com>
Date: Fri, 21 Sep 2012 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
x-cbid: 12092104-5930-0000-0000-00000C50DEDE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Sep 2012 04:53:26 -0000

Total of 56 messages in the last 7 days.
 
script run at: Fri Sep 21 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 14.29% |    8 | 15.33% |    66407 | tglassey@earthlink.net
 14.29% |    8 | 13.55% |    58688 | ben@nostrum.com
  8.93% |    5 |  6.72% |    29105 | touch@isi.edu
  7.14% |    4 |  7.43% |    32180 | john-ietf@jck.com
  5.36% |    3 |  7.32% |    31698 | ben@estacado.net
  5.36% |    3 |  6.61% |    28631 | housley@vigilsec.com
  5.36% |    3 |  6.57% |    28437 | simon@josefsson.org
  3.57% |    2 |  3.09% |    13395 | barryleiba@computer.org
  3.57% |    2 |  3.01% |    13020 | mrex@sap.com
  3.57% |    2 |  2.97% |    12859 | cabo@tzi.org
  3.57% |    2 |  2.94% |    12718 | sm@resistor.net
  3.57% |    2 |  2.81% |    12178 | johnl@taugh.com
  1.79% |    1 |  3.07% |    13284 | david.black@emc.com
  1.79% |    1 |  2.25% |     9740 | ned+ietf@mauve.mrochek.com
  1.79% |    1 |  2.14% |     9266 | narten@us.ibm.com
  1.79% |    1 |  2.03% |     8788 | arnt@gulbrandsen.priv.no
  1.79% |    1 |  1.99% |     8635 | lconroy@insensate.co.uk
  1.79% |    1 |  1.73% |     7497 | sob@harvard.edu
  1.79% |    1 |  1.52% |     6603 | dhc@dcrocker.net
  1.79% |    1 |  1.51% |     6525 | stephen.farrell@cs.tcd.ie
  1.79% |    1 |  1.44% |     6251 | chair@ietf.org
  1.79% |    1 |  1.34% |     5816 | nico@cryptonector.com
  1.79% |    1 |  1.33% |     5748 | ajs@anvilwalrusden.com
  1.79% |    1 |  1.30% |     5611 | joelja@bogus.com
--------+------+--------+----------+------------------------
100.00% |   56 |100.00% |   433080 | Total


From sm@resistor.net  Fri Sep 21 03:43:06 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3727821F865E for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 03:43:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQ3-kVa4Cg7p for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 03:43:05 -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 088D021F864A for <ietf@ietf.org>; Fri, 21 Sep 2012 03:43:04 -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 q8LAgxST026223; Fri, 21 Sep 2012 03:43:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1348224183; bh=DfeB/x3fXwUDxruCO+qk9+9FWer+5h2NG1lRg+vpikg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jbobQ1g13m45MObfrmkYv2+XlsXi2Z96b9lezNVkxO1rbLcoZkXpZDF68UwMw+H+8 LOuaER/6/oYejrgOQsNyaexURTDOcbyy2jKRC4ITwkxZed1BlFLeIh1A3iDPq78LYx 2NFWSSA1g7IrZfoVI4cW5TRRwPOUpdldvQuIxDCw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1348224183; i=@resistor.net; bh=DfeB/x3fXwUDxruCO+qk9+9FWer+5h2NG1lRg+vpikg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vwoGWh1j/7xEnf11uuwoeB/jGx9xo+xJjpANUxqKhNqkbWyFmqmc0viU4nStXtTj9 tpwVvBCOHpQqzSgaPF+g8ewsV1YSzy6Kjafa+66YfyGScbj6kCzoQlbLyY8qrQFS5s C+uHxayMxuQe6BL7+vKC7jhRIZYImFtIQQSoPvQg=
Message-Id: <6.2.5.6.2.20120921022839.08dd0280@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 21 Sep 2012 03:42:43 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
In-Reply-To: <07A7151E396F3AAA85F4A53F@JcK-HP8200.jck.com>
References: <20120919182443.74080.qmail@joyce.lan> <505A2B08.70805@isi.edu> <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org> <07A7151E396F3AAA85F4A53F@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Sep 2012 10:43:06 -0000

Hi John,
At 09:49 20-09-2012, John C Klensin wrote:
>post-expiration.  I think that, as a community, we ought to
>respect those assumptions more than saying, effectively, "we are
>going to maintain a public archive no matter what commitments
>you thought were made to you because we can and because we don't
>think you will actually sue us".  The latter is just bad for the
>community, whether it "works" or not.

In a past century there was a discussion about maintaining a public 
archive of expired I-Ds.  There is a striking difference in the 
arguments; there wasn't much discussion about the legal 
side.  Nowadays an individual has to hire a practicing lawyer from 
the state of Virginia before making any contribution.

It was also argued that the IETF would need a policy to decide on 
whether to turn I-Ds into an archival series.  IENs and RFCs where 
mentioned.  In those ancient times the question was also about 
distribution instead of publication.  It was also pointed out that it 
was better not to perpetuate bad ideas.  There wasn't any mention of 
the social contract.  At a guess it was probably because everything 
was not a matter of "rights" or legal issues.  Or it might be that 
social contracts were part of the obvious.

A sift of long disagreements might show that the sensible "opposing" 
argument is often missed because of the sugarcoating.  A dismissive 
attitude might also have something to do with that.

Consensus is when no man or woman is left standing on the battlefield.

Regards,
-sm 


From cabo@tzi.org  Fri Sep 21 06:11:24 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B50421F8593 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 06:11:24 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mK+xZ2KmuI-t for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 06:11:24 -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 C9DD221F875C for <ietf@ietf.org>; Fri, 21 Sep 2012 06:11:23 -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.3/8.14.3) with ESMTP id q8LDBEgr029006; Fri, 21 Sep 2012 15:11:14 +0200 (CEST)
Received: from [192.168.217.105] (p54893726.dip.t-dialin.net [84.137.55.38]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 5A521D8F; Fri, 21 Sep 2012 15:11:14 +0200 (CEST)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <6.2.5.6.2.20120920121208.0a164868@resistor.net>
Date: Fri, 21 Sep 2012 15:11:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE14F744-AF30-4F4B-959C-9BD585169FA9@tzi.org>
References: <20120919182443.74080.qmail@joyce.lan> <505A2B08.70805@isi.edu> <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org> <07A7151E396F3AAA85F4A53F@JcK-HP8200.jck.com> <243065D9-3A39-4DD3-8BCA-371935FCA228@tzi.org> <6.2.5.6.2.20120920121208.0a164868@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1498)
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: Fri, 21 Sep 2012 13:11:24 -0000

On Sep 20, 2012, at 21:22, SM <sm@resistor.net> wrote:

>> We just had a consensus call in one WG on adopting a draft that at =
this time had been expired for a year.
>> The chairs didn't notice, because the URI was stable (as it should =
be).
>=20
> Send a message with a subject line of Resurrect I-D file to =
internet-drafts@.

Interesting.
Actually, in this case I'd rather have the author resubmit, just to make =
sure not only the rest of the WG, but also the author continues to like =
the draft...
(But I'm not chair for this WG.)

(My problem was not that draft expiry makes the process more =
complicated, but that the chairs didn't notice the expiry and I can't =
blame them.)

Gr=FC=DFe, Carsten


From adrian@olddog.co.uk  Fri Sep 21 07:01:56 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8029521F8844 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 07:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.214
X-Spam-Level: 
X-Spam-Status: No, score=-2.214 tagged_above=-999 required=5 tests=[AWL=0.385,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFlnKYn4Kx8m for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 07:01:56 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id B2C0921F8824 for <ietf@ietf.org>; Fri, 21 Sep 2012 07:01: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 q8LE1qf2010361;  Fri, 21 Sep 2012 15:01:52 +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 q8LE1o34010306 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Sep 2012 15:01:51 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Carsten Bormann'" <cabo@tzi.org>, "'SM'" <sm@resistor.net>
Subject: RE: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Date: Fri, 21 Sep 2012 15:01:49 +0100
Message-ID: <0b4e01cd9801$a5b3ddb0$f11b9910$@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: Ac2YAaH4K0xDNv88SZGWID251OyZNQ==
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: Fri, 21 Sep 2012 14:01:56 -0000

> (My problem was not that draft expiry makes the process more complicated, but
> that the chairs didn't notice the expiry and I can't blame them.)

Weeeeell, the system does send out automatic reminders (entitled "Expiration
Impending: draft-foo") to all authors and copied to the WG chairs.

So not noticing is almost as bad as continuing to post emails on this thread
without changing the subject line :-Z

Cheers,
Adrian


From presnick@qualcomm.com  Fri Sep 21 08:23:26 2012
Return-Path: <presnick@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 A49C621F8792; Fri, 21 Sep 2012 08:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.534
X-Spam-Level: 
X-Spam-Status: No, score=-106.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6Lj0LbZrDap; Fri, 21 Sep 2012 08:23:26 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id EA26821F86E5; Fri, 21 Sep 2012 08:23:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1348241005; x=1379777005; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; bh=Tc93HiZL5Qoh6qM1nWS1K/meSPr9UcaWSGm3WLAqogs=; b=ICIGXACEC0dAQZQ28Rod65HaCLChmlL9M9lkMwgGfLQDFTnweFu/EBoj zJ2RRrTdhoUgksQylYDcP6IPC1kkZniNJx6YX6mtHW9PGGJeYzsQ+Yu/2 cQXMRbND5/8V7EZXXH9VDW5wGylWlSja5OpdqH+KBvdCWhxChN+H1f4if k=;
X-IronPort-AV: E=McAfee;i="5400,1158,6841"; a="239622559"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 21 Sep 2012 08:23:25 -0700
X-IronPort-AV: E=Sophos;i="4.80,463,1344236400"; d="scan'208";a="330683761"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Sep 2012 08:23:25 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.1; Fri, 21 Sep 2012 08:23:24 -0700
Message-ID: <505C866B.9050506@qualcomm.com>
Date: Fri, 21 Sep 2012 10:23:23 -0500
From: Pete Resnick <presnick@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: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07,
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com>
In-Reply-To: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, draft-ietf-eai-rfc5721bis.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: Fri, 21 Sep 2012 15:23:26 -0000

On 9/18/12 8:45 PM, Ben Campbell wrote:

> Nits/editorial comments:
>
> -- IDNits has some complaints; please check.
>    

They were checked.

> -- The abstract should mention that this obsoletes 5721
>    

It does.

> -- section 2.1, 2nd paragraph: "The character encoding format of maildrops may not be UTF-8 or ASCII."
>
> I'm confused by this sentence, as it seems to say that the format can't be UTF-8 or ASCII, which otherwise seem to be the only ones contemplated by the draft.  Do you mean to say that it may be some format other than those?
>    

Yes, I believe that is an editing error. I will confirm and put in an 
RFC Editor note.

> -- same paragraph : "The UTF8 command MAY fail."
>
> Under what circumstances? (this seems sort of tacked onto the paragraph--does it belong there?)
>    

AFAICT, it is simply a warning to client writers that the server may 
(for whatever reasons under whatever circumstances) send back an -ERR 
response to the command, even if it advertises the capability. Seems 
appropriate.

> -- 2.1, 4th paragraph: "...need not be accurate, but it is preferable if they were."
>
> Not preferable enough for a SHOULD? (Note that the previous sentence used SHOULD for reporting actual message size counts)
>    

There is no interoperability impact regarding sizes in STAT and 
free-form text (unlike LIST), so SHOULD is inappropriate.

> -- section 7, 3rd paragraph: "It is possible for a man-in-the-middle attacker to insert a LANG command in the command stream, thus making protocol-level diagnostic responses unintelligible to the user."
>
> This seems a bit unnecessary to call out, given that a MiTM could just change the diagnostic responses into Klingon even in the absence of the LANG command. It's at least worth mentioning that the LANG command really doesn't make this issue worse than it already was.
>    

Taken under advisement.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From presnick@qualcomm.com  Fri Sep 21 08:44:22 2012
Return-Path: <presnick@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 0DCBF21F86BE; Fri, 21 Sep 2012 08:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.535
X-Spam-Level: 
X-Spam-Status: No, score=-106.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-w6AhUK61ex; Fri, 21 Sep 2012 08:44:21 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 72BF421F86BD; Fri, 21 Sep 2012 08:44:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1348242261; x=1379778261; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; bh=6U1Jw3HxCb8mK3vEGL27aRYZ1DzGvc2NqkNo+GFU9Mg=; b=o8Hglti8GHZGtY9oK+N8tO06WmA08GbBNdVR5QOc6TTJqduny2JfSr7q WFMrZGrsaPhWu2E8VVI5OA83XaoVkEwOlWuA4pMJLMf7X3JwRvTrIuhMS FKlhF0vDL6IF6zxURyz4wdWCfUagmL06tk2TBqWOkN/sRZmsIq3g7CCOM 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,6841"; a="237348400"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 21 Sep 2012 08:44:21 -0700
X-IronPort-AV: E=Sophos;i="4.80,463,1344236400"; d="scan'208";a="335550769"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Sep 2012 08:44:20 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.1; Fri, 21 Sep 2012 08:44:20 -0700
Message-ID: <505C8B52.6070603@qualcomm.com>
Date: Fri, 21 Sep 2012 10:44:18 -0500
From: Pete Resnick <presnick@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: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07,
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com> <505C866B.9050506@qualcomm.com>
In-Reply-To: <505C866B.9050506@qualcomm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, draft-ietf-eai-rfc5721bis.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: Fri, 21 Sep 2012 15:44:22 -0000

On 9/21/12 10:23 AM, Pete Resnick wrote:
>> -- The abstract should mention that this obsoletes 5721
>
> It does.

Sorry. You said abstract, not intro. Got it.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From glenzorn@gmail.com  Fri Sep 21 08:52:39 2012
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 630F221E80B4; Fri, 21 Sep 2012 08:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.218
X-Spam-Level: 
X-Spam-Status: No, score=-3.218 tagged_above=-999 required=5 tests=[AWL=0.381,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LRhn5KQJMKfM; Fri, 21 Sep 2012 08:52:38 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id DA49821E80B0; Fri, 21 Sep 2012 08:52:38 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id jt11so5526409pbb.31 for <multiple recipients>; Fri, 21 Sep 2012 08:52:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=rSCi2d/Lv/Rgzm3bVzwgjnDHuquJNFUVViK0PWKZ6kk=; b=zSHSbLByik4P5GTHJ7jYWbxfDP7J2282FSxpHfbvdLnMvgxK6lCI2G1z8Vu+XZI8jV AO4xjJQMlfTauVmMA68tCX1IGTXaSjJLQNH6f8mh/xCI95FQ8Li1p9EfZzQZeZbLG6ur lpE1pGIJg6KEtOzbL4ibJ6O4AGLyKhK6SSM/QQXKLCny7wgTodYE010uqXgbgZ94p3Xq Cnh7g8caW9qI5GECjPi3rlEK5PFKsIskVePSwl7dIYi1Bt8af9oJaoAGQwIh447NpWVR RDJmPq/A7cyP00ttrVAvPCF/AyyI/skZJlH4GbalZfjWIeVDwILAkDlI2s5Tk26FRM+G cBwQ==
Received: by 10.68.196.169 with SMTP id in9mr14856383pbc.70.1348242758674; Fri, 21 Sep 2012 08:52:38 -0700 (PDT)
Received: from [192.168.0.102] (ppp-110-169-206-48.revip5.asianet.co.th. [110.169.206.48]) by mx.google.com with ESMTPS id qw6sm5308149pbc.26.2012.09.21.08.52.34 (version=SSLv3 cipher=OTHER); Fri, 21 Sep 2012 08:52:37 -0700 (PDT)
Message-ID: <505C8D41.5080202@gmail.com>
Date: Fri, 21 Sep 2012 22:52:33 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120830 Thunderbird/15.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07,
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com> <505C866B.9050506@qualcomm.com> <505C8B52.6070603@qualcomm.com>
In-Reply-To: <505C8B52.6070603@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, draft-ietf-eai-rfc5721bis.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: Fri, 21 Sep 2012 15:52:39 -0000

On 09/21/2012 10:44 PM, Pete Resnick wrote:
> On 9/21/12 10:23 AM, Pete Resnick wrote:
>>> -- The abstract should mention that this obsoletes 5721

Why?  There is a statement in the header, 10 lines above the abstract, 
that says "Obsoletes: 5721 (if approved)".

>>
>> It does.
>
> Sorry. You said abstract, not intro. Got it.
>
> pr
>


From presnick@qualcomm.com  Fri Sep 21 09:14:23 2012
Return-Path: <presnick@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 6842721F8713 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 09:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.539
X-Spam-Level: 
X-Spam-Status: No, score=-106.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-Vz0panhP6d for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 09:14:22 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 1350F21F8711 for <ietf@ietf.org>; Fri, 21 Sep 2012 09:14:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1348244062; x=1379780062; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; bh=HsB/aZayWq/mSvmHpxTVgILaSTnAzj7wgHM6feTjAvQ=; b=hyGtwNYTCIONmR5nDKYeZ3Tpl9KEu2K9OkiM1CCV5bAwbfdWKL7E0XDm V0izrmflY0QfsybAM2B9cZPgMlDm5JHtPtNnbEWzwc6NpJ+CvtFuZFRpe 1W1griEDcMYAqWg/ln5yobGt4zdVoP22zjqlTq6uWtIq4da/V0vw++1lU o=;
X-IronPort-AV: E=McAfee;i="5400,1158,6842"; a="239645506"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 21 Sep 2012 09:14:21 -0700
X-IronPort-AV: E=Sophos;i="4.80,463,1344236400"; d="scan'208";a="391677738"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Sep 2012 09:14:21 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.1; Fri, 21 Sep 2012 09:14:20 -0700
Message-ID: <505C925B.2060907@qualcomm.com>
Date: Fri, 21 Sep 2012 11:14:19 -0500
From: Pete Resnick <presnick@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: Glen Zorn <glenzorn@gmail.com>
Subject: Obsoletes/Updates in the abstract (Was: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07)
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com>	<505C866B.9050506@qualcomm.com> <505C8B52.6070603@qualcomm.com> <505C8D41.5080202@gmail.com>
In-Reply-To: <505C8D41.5080202@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: "ietf@ietf.org 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, 21 Sep 2012 16:14:23 -0000

[Changing the subject and removing GenArt and the document authors/chairs]

On 9/21/12 10:52 AM, Glen Zorn wrote:

>>> -- The abstract should mention that this obsoletes 5721
>
> Why?  There is a statement in the header, 10 lines above the abstract, 
> that says "Obsoletes: 5721 (if approved)".

The IESG put this into the nits check before my time. The Last Call and 
publication announcements normally contain only the abstract, not the 
metadata above, and I believe the thinking was that if you are a person 
who scans through those announcements, you probably would (and would 
want to) take notice of documents that purport to obsolete or update 
document that you recognize. We could probably change the tool to add 
the metadata to the announcements, but apparently quite a few people 
read "abstracting" services that grab the abstracts of newly published 
documents. Not much we can do for them.

It's certainly useful to some folks. Necessary? (*Shrug*) Not enough 
wasted bits for me to care one way or the other.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From ben@estacado.net  Fri Sep 21 09:15:20 2012
Return-Path: <ben@estacado.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 98F3921F8714; Fri, 21 Sep 2012 09:15: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uj9eyjtDjpjG; Fri, 21 Sep 2012 09:15:20 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 03A0421F8713; Fri, 21 Sep 2012 09:15:19 -0700 (PDT)
Received: from [10.12.11.64] ([10.12.11.64]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q8LGFHZY004661 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Sep 2012 11:15:17 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07,
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <505C8D41.5080202@gmail.com>
Date: Fri, 21 Sep 2012 11:15:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D60CD10-21CA-4DF6-899C-99359EC6C8F2@estacado.net>
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com> <505C866B.9050506@qualcomm.com> <505C8B52.6070603@qualcomm.com> <505C8D41.5080202@gmail.com>
To: Glen Zorn <glenzorn@gmail.com>
X-Mailer: Apple Mail (2.1498)
Cc: Pete Resnick <presnick@qualcomm.com>, Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, draft-ietf-eai-rfc5721bis.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: Fri, 21 Sep 2012 16:15:20 -0000

On Sep 21, 2012, at 10:52 AM, Glen Zorn <glenzorn@gmail.com> wrote:

>=20
> On 09/21/2012 10:44 PM, Pete Resnick wrote:
>> On 9/21/12 10:23 AM, Pete Resnick wrote:
>>>> -- The abstract should mention that this obsoletes 5721
>=20
> Why?  There is a statement in the header, 10 lines above the abstract, =
that says "Obsoletes: 5721 (if approved)".

The abstract is sometimes displayed without the rest of the document, =
for example, in new RFC announcements.

>=20
>>>=20
>>> It does.
>>=20
>> Sorry. You said abstract, not intro. Got it.
>>=20
>> pr
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From dhc@dcrocker.net  Fri Sep 21 09:22:08 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB6421F877E; Fri, 21 Sep 2012 09:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.565
X-Spam-Level: 
X-Spam-Status: No, score=-6.565 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tt1Togg1hNu0; Fri, 21 Sep 2012 09:22:07 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 201EA21F8777; Fri, 21 Sep 2012 09:22:07 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8LGM5nT021541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 21 Sep 2012 09:22:06 -0700
Message-ID: <505C9425.8040306@dcrocker.net>
Date: Fri, 21 Sep 2012 09:21:57 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07,
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com> <505C866B.9050506@qualcomm.com>
In-Reply-To: <505C866B.9050506@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 21 Sep 2012 09:22:06 -0700 (PDT)
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, draft-ietf-eai-rfc5721bis.all@tools.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, 21 Sep 2012 16:22:08 -0000

On 9/21/2012 8:23 AM, Pete Resnick wrote:
> On 9/18/12 8:45 PM, Ben Campbell wrote:abstract should mention that this obsoletes 5721
>
> It does.


Stylistic point:  RFCs last a long time.  Including ephemeral 
information can be distracting, especially in the Abstract.  5 and 10 
years from now, the fact that this RFC replaces another will be 
essentially irrelevant, but the Abstract will still be spending valuable 
space citing the fact.

It is better to have the document written as standing on its own, rather 
than focus on its relationship to its predecessors, except perhaps in 
isolated 'background' or 'history' discussions (and, of course, the 
Updates field...)


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sm@resistor.net  Fri Sep 21 09:58:57 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D65B21F8705 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 09:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id phZoI8o803po for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 09:58:56 -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 70F1521F8704 for <ietf@ietf.org>; Fri, 21 Sep 2012 09:58:56 -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 q8LGwnKh020822; Fri, 21 Sep 2012 09:58:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1348246735; bh=hEegnJhsZ0/1cKDpB++4YXpOkwmf1QY6hsMQKDe3svY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ySCMqimcn9HeN6EIAri4YqWh+m8QihDAXVJFzv75Plee+p2JrUKyr1wabq7zjwOph /aTcVOjwv9kZzuYin80PLslCl4fEl3PY82qqyYMpL+k+z+ii4QPeADM+p1Mrvfwz1d Yo8hSHgtKm5rpsxeQUBRteSjV78Z26azQLjf6fvA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1348246735; i=@resistor.net; bh=hEegnJhsZ0/1cKDpB++4YXpOkwmf1QY6hsMQKDe3svY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JtQTv8ljo+8mbDiowl/4xraQBONGwUwOOL0cE9ZsFciOquae5ps9SbKYjkUys+W5O 7oIFRbSvf93HqNa/2z4ykRFbhqi0TfMorStPEBzEBr/DkMom78BIKLfDYM0jWnhTus Xu/slpuhOeyao2Ip2ocGdT+VMTH0wJOPiRZN3Az8=
Message-Id: <6.2.5.6.2.20120921083547.0a616088@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 21 Sep 2012 09:55:15 -0700
To: Carsten Bormann <cabo@tzi.org>
From: SM <sm@resistor.net>
Subject: The case of the expired I-D (was: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site)
In-Reply-To: <BE14F744-AF30-4F4B-959C-9BD585169FA9@tzi.org>
References: <20120919182443.74080.qmail@joyce.lan> <505A2B08.70805@isi.edu> <3B972B3E-D86A-4715-A2B2-CFB34D859C7B@tzi.org> <07A7151E396F3AAA85F4A53F@JcK-HP8200.jck.com> <243065D9-3A39-4DD3-8BCA-371935FCA228@tzi.org> <6.2.5.6.2.20120920121208.0a164868@resistor.net> <BE14F744-AF30-4F4B-959C-9BD585169FA9@tzi.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Sep 2012 16:58:57 -0000

Hi Carsten,
At 06:11 21-09-2012, Carsten Bormann wrote:
>Actually, in this case I'd rather have the author resubmit, just to 
>make sure not only the rest of the WG, but also the author continues 
>to like the draft...
>(But I'm not chair for this WG.)

It's better if the author resubmits the draft.

>(My problem was not that draft expiry makes the process more 
>complicated, but that the chairs didn't notice the expiry and I 
>can't blame them.)

Ah, that's a different problem.  There was a draft which went through 
WGLC without any further action for nearly a year.  The lifetime is a 
"tool" which can be used to gauge whether the author continues to 
like the draft or is still interested in working on it.  It is also a 
way for the author to gauge whether the IETF is still interested in 
working on the draft.

Regards,
-sm

P.S. If you say that the draft expiry makes the process more 
complicated, that's the view that primes and not what I want to believe. 


From ben@estacado.net  Fri Sep 21 11:03:38 2012
Return-Path: <ben@estacado.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 3C00F21F84B5; Fri, 21 Sep 2012 11:03: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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GucwXLsQBeFu; Fri, 21 Sep 2012 11:03:37 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 4514721F84A7; Fri, 21 Sep 2012 11:03:37 -0700 (PDT)
Received: from [10.12.11.64] ([10.12.11.64]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q8LI3Zsd019320 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Sep 2012 13:03:36 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07,
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <505C866B.9050506@qualcomm.com>
Date: Fri, 21 Sep 2012 13:03:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D538851-A786-4720-AE8E-392AADDE191A@estacado.net>
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com> <505C866B.9050506@qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.1498)
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, draft-ietf-eai-rfc5721bis.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: Fri, 21 Sep 2012 18:03:38 -0000

Thanks for the response!

On Sep 21, 2012, at 10:23 AM, Pete Resnick <presnick@qualcomm.com> =
wrote:
>=20

[...]

>> -- same paragraph : "The UTF8 command MAY fail."
>>=20
>> Under what circumstances? (this seems sort of tacked onto the =
paragraph--does it belong there?)
>>  =20
>=20
> AFAICT, it is simply a warning to client writers that the server may =
(for whatever reasons under whatever circumstances) send back an -ERR =
response to the command, even if it advertises the capability. Seems =
appropriate.
>=20
>> -- 2.1, 4th paragraph: "...need not be accurate, but it is preferable =
if they were."
>>=20
>> Not preferable enough for a SHOULD? (Note that the previous sentence =
used SHOULD for reporting actual message size counts)
>>  =20
>=20
> There is no interoperability impact regarding sizes in STAT and =
free-form text (unlike LIST), so SHOULD is inappropriate.
>=20

Okay.


>> -- section 7, 3rd paragraph: "It is possible for a man-in-the-middle =
attacker to insert a LANG command in the command stream, thus making =
protocol-level diagnostic responses unintelligible to the user."
>>=20
>> This seems a bit unnecessary to call out, given that a MiTM could =
just change the diagnostic responses into Klingon even in the absence of =
the LANG command. It's at least worth mentioning that the LANG command =
really doesn't make this issue worse than it already was.
>>  =20
>=20
> Taken under advisement.
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: =
(858)651-1102
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From ben@estacado.net  Fri Sep 21 13:25:39 2012
Return-Path: <ben@estacado.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 29FC921E8045 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 13:25:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eUFJgRONskB2 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 13:25:38 -0700 (PDT)
Received: from estacado.net (vicuna.estacado.net [4.30.77.35]) by ietfa.amsl.com (Postfix) with ESMTP id 67CC721E8039 for <ietf@ietf.org>; Fri, 21 Sep 2012 13:25:38 -0700 (PDT)
Received: from [10.12.11.64] ([10.12.11.64]) (authenticated bits=0) by estacado.net (8.14.3/8.14.3) with ESMTP id q8LKPSfc038470 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Sep 2012 15:25:28 -0500 (CDT) (envelope-from ben@estacado.net)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: Obsoletes/Updates in the abstract (Was: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07)
From: Ben Campbell <ben@estacado.net>
In-Reply-To: <505C925B.2060907@qualcomm.com>
Date: Fri, 21 Sep 2012 15:25:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0021B4DD-870E-41A5-938D-75A1ED233BAC@estacado.net>
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com>	<505C866B.9050506@qualcomm.com> <505C8B52.6070603@qualcomm.com> <505C8D41.5080202@gmail.com> <505C925B.2060907@qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.1498)
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: Fri, 21 Sep 2012 20:25:39 -0000

On Sep 21, 2012, at 11:14 AM, Pete Resnick <presnick@qualcomm.com> =
wrote:

> [Changing the subject and removing GenArt and the document =
authors/chairs]
>=20
> On 9/21/12 10:52 AM, Glen Zorn wrote:
>=20
>>>> -- The abstract should mention that this obsoletes 5721
>>=20
>> Why?  There is a statement in the header, 10 lines above the =
abstract, that says "Obsoletes: 5721 (if approved)".
>=20
> The IESG put this into the nits check before my time. The Last Call =
and publication announcements normally contain only the abstract, not =
the metadata above, and I believe the thinking was that if you are a =
person who scans through those announcements, you probably would (and =
would want to) take notice of documents that purport to obsolete or =
update document that you recognize. We could probably change the tool to =
add the metadata to the announcements, but apparently quite a few people =
read "abstracting" services that grab the abstracts of newly published =
documents. Not much we can do for them.
>=20
> It's certainly useful to some folks. Necessary? (*Shrug*) Not enough =
wasted bits for me to care one way or the other.
>=20

As a Gen-ART reviewer, I called it out for exactly the reasons Pete =
mentions, and care about the same amount :-) But putting it there seems =
to hurt nothing, and maybe help just a little bit in some cases.



From housley@vigilsec.com  Fri Sep 21 13:28:44 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A60E521F85F4 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 13:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10WsnPcFJSmW for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 13:28:44 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id E648421F85F0 for <ietf@ietf.org>; Fri, 21 Sep 2012 13:28:43 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 37FD29A400C; Fri, 21 Sep 2012 16:28:48 -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 F2xD4AoR6ypi; Fri, 21 Sep 2012 16:28:40 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C44729A400B; Fri, 21 Sep 2012 16:28:46 -0400 (EDT)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <505B2B75.9060803@isi.edu>
Date: Fri, 21 Sep 2012 16:28:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D455BDA3-A3B7-4A2C-9C61-3267323A7CB8@vigilsec.com>
References: <20120919223106.79603.qmail@joyce.lan> <505B2B75.9060803@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1084)
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, 21 Sep 2012 20:28:44 -0000

I believe that the IETF has all of the necessary rights to reproduce, =
distribute, and display publicly all Internet-Drafts.  Here is my =
analysis:

In RFC 1310, March 1992, the IAB describes Internet-Drafts, but
it does not define the rights that contributors grant.  As best I can
determine, the very first I-D was posted shortly after this RFC
was published.

In RFC 1602, March 1994, the grant of rights becomes very
explicit:

   Contributor agrees to grant, and does grant to ISOC, a
   perpetual, non-exclusive, royalty-free, world-wide right
   and license under any copyrights in the contribution to
   reproduce, distribute, perform or display publicly and
   prepare derivative works that are based on or incorporate
   all or part of the contribution, and to reproduce,
   distribute and perform or display publicly any such
   derivative works, in any form and in all languages, and to
   authorize others to do so.

In RFC 2026, BCP 9, October 1996, the explicit grant of rights
is published in a consensus BCP:

   Some works (e.g. works of the U.S. Government) are not subject to
   copyright.  However, to the extent that the submission is or may
   be subject to copyright, the contributor, the organization he
   represents (if any) and the owners of any proprietary rights in
   the contribution, grant an unlimited perpetual, non-exclusive,
   royalty-free, world-wide right and license to the ISOC and the
   IETF under any copyrights in the contribution.  This license
   includes the right to copy, publish and distribute the
   contribution in any way, and to prepare derivative works that are
   based on or incorporate all or part of the contribution, the
   license to such derivative works to be of the same scope as the
   license of the original contribution.

Internet-Drafts provide important historical records for the open and =
transparent operation of the IETF.  For this reason, removal of an I-D =
from the Public I-D Archive is a significant action.

If someone posted an I-D under RFC 1310, when the grant was not =
explicit, and they want to have their Internet-Draft removed from the =
Public I-D Archive, then they ought to request that action from the =
IESG.  However, RFC 1602 and RFC 2026 are quite clear about the grant.  =
The request for removal of an Internet-Draft posted after March 1994 =
needs to be associated with some legal action or some form of abuse.

Russ


From chair@ietf.org  Fri Sep 21 13:45:37 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42FD221E8039 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 13:45: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mTULgJFLyrgo for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 13:45:36 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id B494B21E8043 for <ietf@ietf.org>; Fri, 21 Sep 2012 13:45:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id AB2BB12BAB8 for <ietf@ietf.org>; Fri, 21 Sep 2012 13:45:36 -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 Z8VmzILzSC+f for <ietf@ietf.org>; Fri, 21 Sep 2012 13:45:36 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 4856412BAB7 for <ietf@ietf.org>; Fri, 21 Sep 2012 13:45:36 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Date: Fri, 21 Sep 2012 16:45:34 -0400
Message-Id: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Sep 2012 20:45:37 -0000

The IESG has updated the draft IESG Statement based on the many comments =
that have been received.  It is clear that the community wants the IESG =
to be able to remove an Internet-Draft from the Public I-D Archive =
without a court order to do so.  That said, the IESG firmly believes =
that the collection of I-Ds provide important historical records for the =
open and transparent operation of the IETF.  Therefore, removal of a I-D =
from the  Public I-D Archive should teated as a significant event.

Comments from the community are solicited on the revised draft IESG =
statement.

On behalf of the IESG,
Russ

--- DRAFT IESG STATEMENT ---

SUBJECT: Removal of an Internet-Draft from the IETF Web Site

Internet-Drafts (I-Ds) are working documents of the IETF.  I-Ds provide
important historical records for the open and transparent operation of
the IETF.  Other individuals and groups, including the IAB and IRTF
Research Groups, have chosen to distribute working documents as I-Ds.

I-Ds are stored in two places on the IETF web site.  First, current I-Ds
are stored in the I-D Repository.  Second, current and past I-Ds are
stored in a Public I-D Archive.

While entries in the I-D Repository are subject to change or removal
at any time, I-Ds generally remain in the Public I-D Archive to support
easy comparison with previous versions.  This availability facilitates
review, comment, and revision.

An entry in the I-D Repository is removed as part of normal process
when it expires after six months, when it is replaced by a subsequent
I-D, or when it is replaced by the publication of an RFC.  In all
of these situations, the I-D remains in the Public I-D Archive.

An I-D will only be removed from the Public I-D Archive with consensus
of the IESG.  There are two situations when the IESG will take this
action.  First, to comply with a duly authorized court order.  Second,
to resolve some form of abuse.  If possible, a removed I-D will be
replaced with a tombstone file that describes the reason that the I-D
was removed from the Public I-D Archive.

When an I-D is removed from the Public I-D Archive, a copy will be kept
in a location accessible only by the IETF Leadership and the IETF
Secretariat.  This private location may be searched by the IETF
Leadership or the IETF Secretariat when responding to appeals,
responding to subpoenas, or otherwise handling to legal matters.

If you are aware of abuse that warrants removal of an I-D from the
Public I-D Archive, please write to the iesg@ietf.org and explain the
situation.  At its discretion, the IESG may consult counsel or the IETF
community before taking any action on such requests.


From touch@isi.edu  Fri Sep 21 13:55:28 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 434ED21F8653 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 13:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.932
X-Spam-Level: 
X-Spam-Status: No, score=-105.932 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NJSivY0YiUpR for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 13:55:27 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id B906B21F864A for <ietf@ietf.org>; Fri, 21 Sep 2012 13:55:27 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q8LKsbXs019823 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 21 Sep 2012 13:54:37 -0700 (PDT)
Message-ID: <505CD40D.9040302@isi.edu>
Date: Fri, 21 Sep 2012 13:54:37 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120919223106.79603.qmail@joyce.lan> <505B2B75.9060803@isi.edu> <D455BDA3-A3B7-4A2C-9C61-3267323A7CB8@vigilsec.com>
In-Reply-To: <D455BDA3-A3B7-4A2C-9C61-3267323A7CB8@vigilsec.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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Sep 2012 20:55:28 -0000

Hi, Russ,

FWIW, you seem to be conveniently ignoring at least two issues:

1) all the IDs before March 1994
	which should not be published at all until
	permission is given (opt-in)

2) all the IDs published before boilerplate inclusion was required
	the IETF cannot merely assert its rights;
	authors need to consent (and if submission were consent
	then the IEEE, ACM, et al. wouldn't need the
	copyright transfer statements they regularly use)

Others have noted that click-based rights transfer may not be sufficient 
as well (the organizations above largely still use explicit signature 
agreements).

And, ultimately, this won't be determined by analysis, but by a court.

Joe

On 9/21/2012 1:28 PM, Russ Housley wrote:
> I believe that the IETF has all of the necessary rights to reproduce, distribute, and display publicly all Internet-Drafts.  Here is my analysis:
>
> In RFC 1310, March 1992, the IAB describes Internet-Drafts, but
> it does not define the rights that contributors grant.  As best I can
> determine, the very first I-D was posted shortly after this RFC
> was published.
>
> In RFC 1602, March 1994, the grant of rights becomes very
> explicit:
>
>     Contributor agrees to grant, and does grant to ISOC, a
>     perpetual, non-exclusive, royalty-free, world-wide right
>     and license under any copyrights in the contribution to
>     reproduce, distribute, perform or display publicly and
>     prepare derivative works that are based on or incorporate
>     all or part of the contribution, and to reproduce,
>     distribute and perform or display publicly any such
>     derivative works, in any form and in all languages, and to
>     authorize others to do so.
>
> In RFC 2026, BCP 9, October 1996, the explicit grant of rights
> is published in a consensus BCP:
>
>     Some works (e.g. works of the U.S. Government) are not subject to
>     copyright.  However, to the extent that the submission is or may
>     be subject to copyright, the contributor, the organization he
>     represents (if any) and the owners of any proprietary rights in
>     the contribution, grant an unlimited perpetual, non-exclusive,
>     royalty-free, world-wide right and license to the ISOC and the
>     IETF under any copyrights in the contribution.  This license
>     includes the right to copy, publish and distribute the
>     contribution in any way, and to prepare derivative works that are
>     based on or incorporate all or part of the contribution, the
>     license to such derivative works to be of the same scope as the
>     license of the original contribution.
>
> Internet-Drafts provide important historical records for the open and transparent operation of the IETF.  For this reason, removal of an I-D from the Public I-D Archive is a significant action.
>
> If someone posted an I-D under RFC 1310, when the grant was not explicit, and they want to have their Internet-Draft removed from the Public I-D Archive, then they ought to request that action from the IESG.  However, RFC 1602 and RFC 2026 are quite clear about the grant.  The request for removal of an Internet-Draft posted after March 1994 needs to be associated with some legal action or some form of abuse.
>
> Russ
>

From ned+ietf@mauve.mrochek.com  Fri Sep 21 14:09:55 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5A5B21E8039 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 14:09:55 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yYuYiIZHYJtj for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 14:09:55 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 669BD11E808D for <ietf@ietf.org>; Fri, 21 Sep 2012 14:09:55 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OKIQMHU2DC00ATB3@mauve.mrochek.com> for ietf@ietf.org; Fri, 21 Sep 2012 14:04:53 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJFFFOH4280006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 21 Sep 2012 14:04:50 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OKIQMG3PPO0006TF@mauve.mrochek.com>
Date: Fri, 21 Sep 2012 14:04:03 -0700 (PDT)
Subject: Re: Obsoletes/Updates in the abstract (Was: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07)
In-reply-to: "Your message dated Fri, 21 Sep 2012 15:25:24 -0500" <0021B4DD-870E-41A5-938D-75A1ED233BAC@estacado.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com> <505C866B.9050506@qualcomm.com> <505C8B52.6070603@qualcomm.com> <505C8D41.5080202@gmail.com> <505C925B.2060907@qualcomm.com> <0021B4DD-870E-41A5-938D-75A1ED233BAC@estacado.net>
To: Ben Campbell <ben@estacado.net>
Cc: Pete Resnick <presnick@qualcomm.com>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Sep 2012 21:09:55 -0000

> On Sep 21, 2012, at 11:14 AM, Pete Resnick <presnick@qualcomm.com> wrote:

> > [Changing the subject and removing GenArt and the document authors/chairs]
> >
> > On 9/21/12 10:52 AM, Glen Zorn wrote:
> >
> >>>> -- The abstract should mention that this obsoletes 5721
> >>
> >> Why?  There is a statement in the header, 10 lines above the abstract, that says "Obsoletes: 5721 (if approved)".
> >
> > The IESG put this into the nits check before my time. The Last Call and publication announcements normally contain only the abstract, not the metadata above, and I believe the thinking was that if you are a person who scans through those announcements, you probably would (and would want to) take notice of documents that purport to obsolete or update document that you recognize. We could probably change the tool to add the metadata to the announcements, but apparently quite a few people read "abstracting" services that grab the abstracts of newly published documents. Not much we can do for them.
> >
> > It's certainly useful to some folks. Necessary? (*Shrug*) Not enough wasted bits for me to care one way or the other.
> >

> As a Gen-ART reviewer, I called it out for exactly the reasons Pete mentions,
> and care about the same amount :-) But putting it there seems to hurt nothing,
> and maybe help just a little bit in some cases.

That's your opinion. Others, myself included, strongly disagree.

				Ned

From jari.arkko@piuha.net  Fri Sep 21 14:14:14 2012
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 6B50621F85B8; Fri, 21 Sep 2012 14:14: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MHXcfFgGhrBy; Fri, 21 Sep 2012 14:14:12 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 9C1BE21F8595; Fri, 21 Sep 2012 14:14:12 -0700 (PDT)
Received: from [10.240.109.231] (37-136-97-108.nat.bb.dnainternet.fi [37.136.97.108]) by p130.piuha.net (Postfix) with ESMTPSA id 0DE452CC56; Sat, 22 Sep 2012 00:14:09 +0300 (EEST)
Date: Sat, 22 Sep 2012 00:14:06 +0300
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF	Web Site
Message-ID: <3awvhk3ubkqjitoqo4exfal3.1348262046844@email.android.com>
From: Jari Arkko <jari.arkko@piuha.net>
To: IETF <ietf@ietf.org>, IETF Chair <chair@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Sep 2012 21:14:14 -0000

TG9va3MgZ29vZCB0byBtZS4KCkphcmk=


From stewe@stewe.org  Fri Sep 21 14:16:18 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43BD621E808D; Fri, 21 Sep 2012 14:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.139
X-Spam-Level: 
X-Spam-Status: No, score=-4.139 tagged_above=-999 required=5 tests=[AWL=-0.539, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYwPAe0FOPd6; Fri, 21 Sep 2012 14:16:17 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe003.messaging.microsoft.com [216.32.180.186]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD6111E8097; Fri, 21 Sep 2012 14:16:17 -0700 (PDT)
Received: from mail188-co1-R.bigfish.com (10.243.78.230) by CO1EHSOBE005.bigfish.com (10.243.66.68) with Microsoft SMTP Server id 14.1.225.23; Fri, 21 Sep 2012 21:16:15 +0000
Received: from mail188-co1 (localhost [127.0.0.1])	by mail188-co1-R.bigfish.com (Postfix) with ESMTP id CCCC41200EB; Fri, 21 Sep 2012 21:16:15 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -18
X-BigFish: PS-18(zz98dI1432Id6f1izz1202h1d1ah1d2ah1082kzz1033IL8275dhz2fh2a8h668h839h944he5bhf0ah107ah1220h1288h12a5h12a9h12bdh137ah1155h)
Received-SPF: pass (mail188-co1: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail188-co1 (localhost.localdomain [127.0.0.1]) by mail188-co1 (MessageSwitch) id 1348262170642928_32556; Fri, 21 Sep 2012 21:16:10 +0000 (UTC)
Received: from CO1EHSMHS029.bigfish.com (unknown [10.243.78.247])	by mail188-co1.bigfish.com (Postfix) with ESMTP id 9A116240043; Fri, 21 Sep 2012 21:16:10 +0000 (UTC)
Received: from BL2PRD0710HT005.namprd07.prod.outlook.com (157.56.240.133) by CO1EHSMHS029.bigfish.com (10.243.66.39) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 21 Sep 2012 21:16:09 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.165]) by BL2PRD0710HT005.namprd07.prod.outlook.com ([10.255.102.40]) with mapi id 14.16.0190.008; Fri, 21 Sep 2012 21:16:09 +0000
From: Stephan Wenger <stewe@stewe.org>
To: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Topic: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Thread-Index: AQHNmD5RcV1LOk4tg02ZT5wnVp24vQ==
Date: Fri, 21 Sep 2012 21:16:09 +0000
Message-ID: <CC822490.8D5E0%stewe@stewe.org>
In-Reply-To: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D35758FC4DC96442BFC0F9A8AF7459CD@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Sep 2012 21:16:18 -0000

Overall I like this--enough wiggle-room to deal with situations we cannot
foresee now, but still sufficient guidance for the IESGs to come.  One
small issue, inline.
Stephan

On 9.21.2012 13:45 , "IETF Chair" <chair@ietf.org> wrote:

>[...]
>
>When an I-D is removed from the Public I-D Archive, a copy will be kept
>in a location accessible only by the IETF Leadership and the IETF
>Secretariat. =20

It's quite likely, if there really were a court order to remove an I-D
from public access, that there is also a demand to destroy any copies.
The sentence above could be read that the IETF would keep a copy
nevertheless. =20

To cure this, you could insert a sentence "This copy will be removed only
based on a court order or a legal request of comparable strength.".

In other words, IESG common sense is enough to remove an I-D from the
publicly accessible archive, but it takes a court order to remove it for
good.

>[...]
>



From john-ietf@jck.com  Fri Sep 21 14:16:36 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE29C21E8092 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 14:16:36 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJEuhlPB4fTp for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 14:16:36 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 070FD11E808D for <ietf@ietf.org>; Fri, 21 Sep 2012 14:16: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 1TFAaJ-0006al-W8; Fri, 21 Sep 2012 17:16:27 -0400
Date: Fri, 21 Sep 2012 17:16:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ben Campbell <ben@estacado.net>, Pete Resnick <presnick@qualcomm.com>
Subject: Re: Obsoletes/Updates in the abstract (Was: Gen-ART LC Review of	draft-ietf-eai-rfc5721bis-07)
Message-ID: <3E05E850C65FB59990020F73@JcK-HP8200.jck.com>
In-Reply-To: <0021B4DD-870E-41A5-938D-75A1ED233BAC@estacado.net>
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com> <505C866B.9050506@qualcomm.com>	<505C8B52.6070603@qualcomm.com> <505C8D41.5080202@gmail.com>	<505C925B.2060907@qualcomm.com> <0021B4DD-870E-41A5-938D-75A1ED233BAC@estacado.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 List" <ietf@ietf.org>, rfc-editor@rfc-editor.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Sep 2012 21:16:36 -0000

--On Friday, September 21, 2012 15:25 -0500 Ben Campbell
<ben@estacado.net> wrote:

>> It's certainly useful to some folks. Necessary? (*Shrug*) Not
>> enough wasted bits for me to care one way or the other.
>> 
> 
> As a Gen-ART reviewer, I called it out for exactly the reasons
> Pete mentions, and care about the same amount :-) But putting
> it there seems to hurt nothing, and maybe help just a little
> bit in some cases.

Ben,

An observation as an individual rather than in any EAI capacity:

The scholarly publication and information science fields have
generally-accepted criteria for abstracts.  The devil is in the
details, of course, but, in general,  structural comments or
comments about relationships to earlier works are included only
if they are essential to understanding what the current document
is about.   I note that this comment is consistent with Dave
Crocker's earlier one, although I'd go a bit further.

There is an additional issue, which is that the RFC Editor
normally requires that citations of RFCs be treated as citations
and referenced but, consistent with those generally-accepted
practices, prohibits citations from abstracts.  Ending up with
"this obsoletes RFC NNNN" in an abstract sneaks by that
combination of rules, but borders on the unprofessional.

There are documents for which "this obsoletes that" really does
belong in the abstract because it is essential for understanding
the role of the document but in almost all cases, "that" won't
be an RFC reference but a topical one.  As an example in the RFC
series that might mean that the abstract for RFC 5378 might more
reasonably have said "This memo is effective XXXX and supercedes
all policies about rights in contributions prior to that date".

To the extent to which the issue is metadata information in
announcements, let's fix the announcement templates, not
introduce kludges to get around them.   The argument that there
is some other information that people might want to know that
doesn't appear when the abstract alone is posted is, by
contrast, completely bogus: people might want to know the date
of publication, the author's names, etc., but no one has
suggested that they be included in the abstract.

On the other hand, I'm a strong advocate of requiring text in
the document -- in the Introduction or a specially-identified
section-- that describes the relationship of the current
document to anything it updates, obsoletes, modifies,
criticizes, or is otherwise directly related to.  That is
important explanation, not a few words in the abstract that
partially identify a relationship without even hinting about
what it is about substantively.

FWIW, I believe this is ultimately an RFC Style issue and that
the community should expect guidance on it from the RFC Editor.  

Finally, as I have previously pointed out to the IESG, the
"requirement" for that sentence in the abstract made it into
IDnits without anything resembling a consensus call or
consultation of the RFC Editor.  While I'd rather see the
substantive issue addressed and have tried to do so above, we do
have rules about community consensus before requirements are
imposed and this hasn't made that test as a requirement.  If the
nits checker wanted to say "are you sure that the relationship
between this document and any predecessors are not significant
enough to justify inclusion in the abstract" I think that would
be fine, especially if it also generated a question of "are you
sure that the relationship between this document and any
predecessors are significant enough to justify putting text in
the abstract (and possibly cluttering it)" when the citation
does appear.  But, as a requirement, it is basically bogus
absent either a style requirement from the RFC Editor or a
consensus call.

   john


From paul.hoffman@vpnc.org  Fri Sep 21 14:48:43 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52ACB21F853B for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 14:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZYxbdVAzUJ1 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 14:48:43 -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 D383521F8527 for <ietf@ietf.org>; Fri, 21 Sep 2012 14:48:42 -0700 (PDT)
Received: from [10.20.30.108] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q8LLmeAn074003 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Sep 2012 14:48:40 -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.1 \(1498\))
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <505CD40D.9040302@isi.edu>
Date: Fri, 21 Sep 2012 14:48:40 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <F9F374AD-679A-4625-87BA-C04BBFFFD1C9@vpnc.org>
References: <20120919223106.79603.qmail@joyce.lan> <505B2B75.9060803@isi.edu> <D455BDA3-A3B7-4A2C-9C61-3267323A7CB8@vigilsec.com> <505CD40D.9040302@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1498)
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, 21 Sep 2012 21:48:43 -0000

On Sep 21, 2012, at 1:54 PM, Joe Touch <touch@isi.edu> wrote:

> And, ultimately, this won't be determined by analysis, but by a court.

These kinds of threats seem a bit over the top.

--Paul Hoffman

From touch@isi.edu  Fri Sep 21 15:16:49 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41B7B21F8596 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 15:16:49 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJM5awSG6nx5 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 15:16:48 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id A21D421F8523 for <ietf@ietf.org>; Fri, 21 Sep 2012 15:16:48 -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 q8LMGAhs009316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 21 Sep 2012 15:16:10 -0700 (PDT)
Message-ID: <505CE72A.1030506@isi.edu>
Date: Fri, 21 Sep 2012 15:16:10 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120919223106.79603.qmail@joyce.lan> <505B2B75.9060803@isi.edu> <D455BDA3-A3B7-4A2C-9C61-3267323A7CB8@vigilsec.com> <505CD40D.9040302@isi.edu> <F9F374AD-679A-4625-87BA-C04BBFFFD1C9@vpnc.org>
In-Reply-To: <F9F374AD-679A-4625-87BA-C04BBFFFD1C9@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 <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Sep 2012 22:16:49 -0000

On 9/21/2012 2:48 PM, Paul Hoffman wrote:
> On Sep 21, 2012, at 1:54 PM, Joe Touch <touch@isi.edu> wrote:
>
>> And, ultimately, this won't be determined by analysis, but by a court.
>
> These kinds of threats seem a bit over the top.

It was an observation, not a threat (at all).

No analysis of legal matters is ever decided until a court weighs in. 
Lawyers will say what they are willing to defend - pro and con - but 
their statements aren't fact. So even if they claim this is cut-and-dry, 
it isn't until case is decided.

Joe

From john-ietf@jck.com  Fri Sep 21 16:38:14 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83B1221F847C for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 16:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sArD7uyJJEVf for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 16:38:13 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BF1F921F846F for <ietf@ietf.org>; Fri, 21 Sep 2012 16:38:13 -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 1TFCnR-0006ry-5A; Fri, 21 Sep 2012 19:38:09 -0400
Date: Fri, 21 Sep 2012 19:38:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joe Touch <touch@isi.edu>, Russ Housley <housley@vigilsec.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <228602B82A348A1597730C91@JcK-HP8200.jck.com>
In-Reply-To: <505CD40D.9040302@isi.edu>
References: <20120919223106.79603.qmail@joyce.lan> <505B2B75.9060803@isi.edu> <D455BDA3-A3B7-4A2C-9C61-3267323A7CB8@vigilsec.com> <505CD40D.9040302@isi.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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, 21 Sep 2012 23:38:15 -0000

Joe,

While I've somewhat sympathetic to your position -- I don't
think the IETF should be supporting a public archival collection
of expired I-Ds, especially older ones, either-- I think you are
getting a little over the top.  Specifically...

--On Friday, September 21, 2012 13:54 -0700 Joe Touch
<touch@isi.edu> wrote:

> Hi, Russ,
> 
> FWIW, you seem to be conveniently ignoring at least two issues:
> 
> 1) all the IDs before March 1994
> 	which should not be published at all until
> 	permission is given (opt-in)

While I agree, I think that most of the reason for that has to
do with implicit or explicit IETF commitments to individuals
rather than legal constraints.  That is not to say the legal
constraints aren't there.  IANAL, much less a judge, and have no
opinion on that which anyone else should pay attention to.  

Suppose that, as a modified form of opt-out under the latest
proposed policy, you were to send a note to the IESG asking that
all of your old I-Ds be taken down from the public archive on
the grounds that having them public is abusive of commitments
you have good reason to believe were made to you.    If the IESG
said "nope, not abusive enough", you could then either appeal
(probably a more constructive way of airing things under our
rules than involving the legal process) or claim that the IETF
had no rights to keep a document posted to which you believe you
have retained copyright and get a DMCA take-down request issued.
Such a request would give the IESG and IETF Trust the
"opportunity" to consider how much risk they wanted to assume to
keep your documents posted and possibly to discuss that with the
community.  Sadly, they might consider the odds that you would
actually choose to sue in their risk assessment (see below).

That wouldn't let you made document availability decisions by
default for anyone else (e.g., by forcing opt-in), but would,
IMO, focus the discussion in a way that increasingly heated
comments on the IETF list would not.

>...
> And, ultimately, this won't be determined by analysis, but by
> a court.

Well, it would be determined by a court only if someone felt
strongly enough about a particular document or set of documents
to go to the expense of going down that path.  I am unhappy with
the current IPR regime, unhappy enough with current practices
that some things that would have been posted as I-Ds under the
policies as I understood them a decade or two ago just don't
make it into the system.  Perhaps that is A Good Thing, perhaps
not, but one of the inevitable consequences of an IPR policy
that gives the IETF more and more discretion over what to do
with ideas and "contributions" that aren't turned into standards
is that it will see fewer such contributions.  Only the
community can judge whether that is a good tradeoff -- a
judgment that is made more difficult by not being able to
ascertain what it isn't seeing.   But I'm not nearly unhappy
enough to try to drag the IETF into court over the issue,
partially because I know that doing so wouldn't cause the
documents to go away even if I won.

If no one feels mean-tempered enough to launch such a court
case, then the policy won't be settled by a judge, it will stand
because no one challenges it.

   john


From john-ietf@jck.com  Fri Sep 21 17:08:08 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 960A621E809F; Fri, 21 Sep 2012 17:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Evl9QfmHLgz5; Fri, 21 Sep 2012 17:08:08 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id F0F8E21F8495; Fri, 21 Sep 2012 17:08:07 -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 1TFDGL-0006uL-JY; Fri, 21 Sep 2012 20:08:01 -0400
Date: Fri, 21 Sep 2012 20:07:56 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ben Campbell <ben@nostrum.com>, draft-ietf-eai-popimap-downgrade.all@tools.ietf.org
Subject: Re: Gen-ART LC Review of draft-ietf-eai-popimap-downgrade-07
Message-ID: <C254F277BCB06461B223B6C1@JcK-HP8200.jck.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: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Sep 2012 00:08:08 -0000

--On Thursday, September 20, 2012 15:03 -0500 Ben Campbell
<ben@nostrum.com> wrote:

> Hi,
> 
> Email discussion about the simple downgrade draft made me
> think of a concern that I think I failed to mention in my
> review. In particular, the "tunneling" mechanism allows the
> creation of several new "Downgraded-*" header fields
> containing encoded content from the original message. Given
> that downgraded messages are primarily to be consumed by
> legacy clients, which we can assume do not know anything about
> this draft, why would we expect the clients to present those
> headers to the user, or otherwise notify the user of their
> existence?

Ben,

Many participants in the WG agree with you that the relatively
complex effort to preserve information represented by
popimap-downgrade isn't worth the trouble.  That is one of the
reasons the simple downgrade doc exists and why some
participants prefer "forklift or no message" strategies.

But I think you are missing an important part of the puzzle,
which is that the audience for those downgraded messages isn't a
client but a user.  A user who gets an obviously-bogus message
(weird headers, can't reply, etc.) will presumably do something.
If that "something" is to discard the message as trash, then
that user is no worse (or better) off than if the message had
been blocked or discarded earlier in the works.   If a server
operator can predict that behavior, then she is probably better
off configuring a "no downgrade" strategy.  But, if the user
enlists the help of other resources (organized help desks,
well-written FAQs, helpful relatives,...) having that resource
able to differentiate between these two downgrade models and
something random and then say for this case "better retrieve and
examine the full set of headers" actually is useful.   

That also means that having a relatively small number of
well-documented downgrade mechanisms is useful and maybe
important.  That, in turn, does raise the character of those
downgrade specs to "if you want to do this, do it this way"
standards rather than "this is how we think it could be done,
but do as you like" informational specs.  From my point of view,
that _is_ an interoperability issue, albeit interoperable with
users and their support structures not (merely) between server
and client.  

There are also some server-> legacy client (yes, one that
doesn't have a clue that UTF-8 headers might be
encountered/valid) interoperability issues on which the WG spent
a lot of energy because it would be pretty easy for a server to
send something to a legacy client that would break it, rather
than just creating a surrogate message that contains different
information (or differently-organized information) than the
original.  There was a lengthy discussion about alternative ways
to represent backward-pointing UTF-8 addresses that concluded
with the use of encoded words and group syntax because of just
that sort of interoperability consideration and the WG's
conviction that some other strategies would create much greater
risks.

YMMD, but I think the above fairly accurately represents the
rough consensus of the WG after lengthy discussion of the issues
involved, including good approximations to the ones you have
raised.  Unless you have something new to add (ideally after
reviewing the archives), I think we should put the topic to rest.

best.
   john


From touch@isi.edu  Fri Sep 21 17:28:05 2012
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6075621F84D7 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 17:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.799
X-Spam-Level: 
X-Spam-Status: No, score=-103.799 tagged_above=-999 required=5 tests=[AWL=-1.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f-tWhJScLEyr for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 17:28:04 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id AC95621F84EC for <ietf@ietf.org>; Fri, 21 Sep 2012 17:28:04 -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 q8M0Ridt013023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 21 Sep 2012 17:27:44 -0700 (PDT)
Message-ID: <505D0600.5010000@isi.edu>
Date: Fri, 21 Sep 2012 17:27:44 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <20120919223106.79603.qmail@joyce.lan> <505B2B75.9060803@isi.edu> <D455BDA3-A3B7-4A2C-9C61-3267323A7CB8@vigilsec.com> <505CD40D.9040302@isi.edu> <228602B82A348A1597730C91@JcK-HP8200.jck.com>
In-Reply-To: <228602B82A348A1597730C91@JcK-HP8200.jck.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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Sep 2012 00:28:05 -0000

On 9/21/2012 4:38 PM, John C Klensin wrote:
> Joe,
>
> While I've somewhat sympathetic to your position -- I don't
> think the IETF should be supporting a public archival collection
> of expired I-Ds, especially older ones, either-- I think you are
> getting a little over the top.  Specifically...
>
> --On Friday, September 21, 2012 13:54 -0700 Joe Touch
> <touch@isi.edu> wrote:
>
>> Hi, Russ,
>>
>> FWIW, you seem to be conveniently ignoring at least two issues:
>>
>> 1) all the IDs before March 1994
>> 	which should not be published at all until
>> 	permission is given (opt-in)
>
> While I agree, I think that most of the reason for that has to
> do with implicit or explicit IETF commitments to individuals
> rather than legal constraints.  That is not to say the legal
> constraints aren't there.  IANAL, much less a judge, and have no
> opinion on that which anyone else should pay attention to.

IMO, the IETF should not set an example of "post what you want, and take 
things down only on legal threat".

It's reasonable to post what the IETF has rights to. Posting things that 
the IETF *wants* but does *not* have explicit rights too seems a 
non-starter.

> Suppose that, as a modified form of opt-out under the latest
> proposed policy, you were to send a note to the IESG asking that
> all of your old I-Ds be taken down from the public archive on
> the grounds that having them public is abusive of commitments
> you have good reason to believe were made to you.    If the IESG
> said "nope, not abusive enough", you could then either appeal
> (probably a more constructive way of airing things under our
> rules than involving the legal process) or claim that the IETF
> had no rights to keep a document posted to which you believe you
> have retained copyright and get a DMCA take-down request issued.
> Such a request would give the IESG and IETF Trust the
> "opportunity" to consider how much risk they wanted to assume to
> keep your documents posted and possibly to discuss that with the
> community.  Sadly, they might consider the odds that you would
> actually choose to sue in their risk assessment (see below).

I expect that might be what transpires here, but if we're in an 
organization that does that I would seriously reconsider writing future 
contributions.

> That wouldn't let you made document availability decisions by
> default for anyone else (e.g., by forcing opt-in), but would,
> IMO, focus the discussion in a way that increasingly heated
> comments on the IETF list would not.

Sure, having the IETF step on authors' rights certainly focuses the 
discussion. I sincerely hope this organization understands its 
responsibility to the community better, and respects the rights of 
others in its action (not merely the cost of legal entanglements).
>> ...
>> And, ultimately, this won't be determined by analysis, but by
>> a court.
>
> Well, it would be determined by a court only if someone felt
> strongly enough about a particular document or set of documents
> to go to the expense of going down that path.

Agreed; I'm only noting that this is all conjecture, not fact.

...
> If no one feels mean-tempered enough to launch such a court
> case, then the policy won't be settled by a judge, it will stand
> because no one challenges it.

Perhaps. Perhaps those of us who feel the IETF is setting a bad example 
should just walk away. That solves the problem, right?

Joe

From dhc@dcrocker.net  Fri Sep 21 17:48:51 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DACE921E80C2; Fri, 21 Sep 2012 17:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.565
X-Spam-Level: 
X-Spam-Status: No, score=-6.565 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfjYUNgHHNmB; Fri, 21 Sep 2012 17:48:51 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 21FD921E80BF; Fri, 21 Sep 2012 17:48:51 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8M0mnqD032177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 21 Sep 2012 17:48:49 -0700
Message-ID: <505D0AE8.8060208@dcrocker.net>
Date: Fri, 21 Sep 2012 17:48:40 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: IETF Chair <chair@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org>
In-Reply-To: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 21 Sep 2012 17:48:50 -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: Sat, 22 Sep 2012 00:48:52 -0000

On 9/21/2012 1:45 PM, IETF Chair wrote:
> The IESG has updated the draft IESG Statement based on the many comments that have been received.  It is clear that the community wants the IESG to be able to remove an Internet-Draft from the Public I-D Archive without a court order to do so.  That said, the IESG firmly believes that the collection of I-Ds provide important historical records for the open and transparent operation of the IETF.  Therefore, removal of a I-D from the  Public I-D Archive should teated as a significant event.
>
> Comments from the community are solicited on the revised draft IESG statement.
>
> On behalf of the IESG,
> Russ
>
> --- DRAFT IESG STATEMENT ---
>
> SUBJECT: Removal of an Internet-Draft from the IETF Web Site
>
> Internet-Drafts (I-Ds) are working documents of the IETF.  I-Ds provide
> important historical records for the open and transparent operation of
> the IETF.  Other individuals and groups, including the IAB and IRTF
> Research Groups, have chosen to distribute working documents as I-Ds.

The IAB and IRTF are not part of the IETF?  The Independent stream also 
uses I-Ds.  Isn't it part of the IETF?


> I-Ds are stored in two places on the IETF web site.  First, current I-Ds
> are stored in the I-D Repository.  Second, current and past I-Ds are
> stored in a Public I-D Archive.
>
> While entries in the I-D Repository are subject to change or removal
> at any time,

They are?  Is this new?  I thought the only established removal policy 
was the regular 6-month timeout.


>                I-Ds generally remain in the Public I-D Archive to support
> easy comparison with previous versions.  This availability facilitates
> review, comment, and revision.
 >
> An entry in the I-D Repository is removed as part of normal process
> when it expires after six months, when it is replaced by a subsequent
> I-D, or when it is replaced by the publication of an RFC.  In all
> of these situations, the I-D remains in the Public I-D Archive.


The text up to this point mostly looks like a general set of policy 
assertions about I-Ds.  Those need to exist separately as a formal 
policy statement about the series and its archive(s).

That would leave the current statement to focus on its specific topic.


> An I-D will only be removed from the Public I-D Archive with consensus
> of the IESG.  There are two situations when the IESG will take this
> action.  First, to comply with a duly authorized court order.  Second,
> to resolve some form of abuse.

This second basis looks sufficiently broad and vague to invite its own 
abuse and certainly inconsistent application.  Did IETF counsel express 
comfort with this language?


>  If possible, a removed I-D will be
> replaced with a tombstone file that describes the reason that the I-D
> was removed from the Public I-D Archive.
>
> When an I-D is removed from the Public I-D Archive, a copy will be kept
> in a location accessible only by the IETF Leadership and the IETF
> Secretariat.  This private location may be searched by the IETF
> Leadership or the IETF Secretariat when responding to appeals,
> responding to subpoenas, or otherwise handling to legal matters.

Interesting.  An archive archive.

IETF "leadership" isn't a formal term.  Who does it include/exclude?  WG 
Chairs?  Why?  Why not?

Over time, given the number of people who hold various IETF leadership 
positions, this effectively gives access to a very large fraction of the 
IETF community.


> If you are aware of abuse that warrants removal of an I-D from the
> Public I-D Archive, please write to the iesg@ietf.org and explain the
> situation.  At its discretion, the IESG may consult counsel or the IETF
> community before taking any action on such requests.


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dwm@xpasc.com  Fri Sep 21 18:41:27 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 489AD21E80D9 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 18:41: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id neTl4azYEpvQ for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 18:41:26 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id D4F3921E8041 for <ietf@ietf.org>; Fri, 21 Sep 2012 18:41:26 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 301CB3F94B for <ietf@ietf.org>; Sat, 22 Sep 2012 01:41:26 +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 q8M1fP5t001913 for <ietf@ietf.org>; Fri, 21 Sep 2012 18:41:25 -0700
Date: Fri, 21 Sep 2012 18:41:25 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: IETF <ietf@ietf.org>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <505D0AE8.8060208@dcrocker.net>
Message-ID: <alpine.LRH.2.01.1209211838360.32592@egate.xpasc.com>
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@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, 22 Sep 2012 01:41:27 -0000

On Fri, 21 Sep 2012, Dave Crocker wrote:

 
> > While entries in the I-D Repository are subject to change or removal
> > at any time,
> 
> They are?  Is this new?  I thought the only established removal policy was the
> regular 6-month timeout.

Can't the author replace the repository version at any time AND can't that 
replacement effectively delete it by sending minimal boilerplate to
pass any format testing.

From dhc@dcrocker.net  Fri Sep 21 19:00:07 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A08B321E80F3 for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 19:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kha8HZWLV4Lr for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 19:00:06 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C923021E80F2 for <ietf@ietf.org>; Fri, 21 Sep 2012 19:00:06 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8M205qb001123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 21 Sep 2012 19:00:06 -0700
Message-ID: <505D1B9C.8020103@dcrocker.net>
Date: Fri, 21 Sep 2012 18:59:56 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net> <alpine.LRH.2.01.1209211838360.32592@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1209211838360.32592@egate.xpasc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 21 Sep 2012 19:00:06 -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: Sat, 22 Sep 2012 02:00:07 -0000

On 9/21/2012 6:41 PM, David Morris wrote:
>
>
> On Fri, 21 Sep 2012, Dave Crocker wrote:
>
>
>>> While entries in the I-D Repository are subject to change or removal
>>> at any time,
>>
>> They are?  Is this new?  I thought the only established removal policy was the
>> regular 6-month timeout.
>
> Can't the author replace the repository version at any time AND can't that
> replacement effectively delete it by sending minimal boilerplate to
> pass any format testing.


Fair point.

Except that 'replacing' seems a bit different than 'deleting'.

While yes it deletes the old version, the effect of a replacement seems 
significantly different than is intended by the text (and the topic of 
the Subject line.)

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From glenzorn@gmail.com  Fri Sep 21 20:37:37 2012
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 CF9FB21E80EF for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 20:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.265
X-Spam-Level: 
X-Spam-Status: No, score=-3.265 tagged_above=-999 required=5 tests=[AWL=0.334,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qL90u7S7nCJH for <ietf@ietfa.amsl.com>; Fri, 21 Sep 2012 20:37:37 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 42D1121E804D for <ietf@ietf.org>; Fri, 21 Sep 2012 20:37:37 -0700 (PDT)
Received: by pbbjt11 with SMTP id jt11so6458099pbb.31 for <ietf@ietf.org>; Fri, 21 Sep 2012 20:37:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=GflwqfhMoltiMV5Vi3T6K1gzT0uFM4UkKs6+o54QM9A=; b=FzNpp8vjX5suV69JSKPRrWVmwvkZNRbav8HiTCBcAwI2NJU7y6LHVsKqw+A+KrYKwG PIm9b1mNgd0oCaNxGjjq2N21BOUf7N3LZWpKKCgkEXAww1vdtY72KcemXScB2LGT4XUo N7rOIIOt0DyYTMnEHkc+52bW2ZN98SqYzs19Fj8ArqokwmT0uUNXbSv5uGdkyG+gXj3v hoXO+ZwLRE7jadWLpxqI6LlS5RSioZqk6S62o1RDBNAX7mPQdrMa7zUY7KF2Alrr5YuO tsvhCfudjUpMaqra+Q0M1fiBJynXXd8vjbH3YCgDP/jOjsVEUtLeYHV85e0ocjn6ZPh0 +LJg==
Received: by 10.68.221.168 with SMTP id qf8mr20280026pbc.37.1348285057068; Fri, 21 Sep 2012 20:37:37 -0700 (PDT)
Received: from [192.168.0.102] (ppp-110-169-206-48.revip5.asianet.co.th. [110.169.206.48]) by mx.google.com with ESMTPS id tt6sm6040390pbc.51.2012.09.21.20.37.34 (version=SSLv3 cipher=OTHER); Fri, 21 Sep 2012 20:37:36 -0700 (PDT)
Message-ID: <505D327C.9040609@gmail.com>
Date: Sat, 22 Sep 2012 10:37:32 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120830 Thunderbird/15.0
MIME-Version: 1.0
To: Ben Campbell <ben@estacado.net>
Subject: Re: Obsoletes/Updates in the abstract (Was: Gen-ART LC Review of draft-ietf-eai-rfc5721bis-07)
References: <8CE78C42-20B9-45BC-A872-90E7FBE27D24@nostrum.com>	<505C866B.9050506@qualcomm.com> <505C8B52.6070603@qualcomm.com> <505C8D41.5080202@gmail.com> <505C925B.2060907@qualcomm.com> <0021B4DD-870E-41A5-938D-75A1ED233BAC@estacado.net>
In-Reply-To: <0021B4DD-870E-41A5-938D-75A1ED233BAC@estacado.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Sep 2012 03:37:37 -0000

On 09/22/2012 03:25 AM, Ben Campbell wrote:

...

>>>>> -- The abstract  should mention that this obsoletes 5721
 >>>
 >>> Why? There is a statement in the header, 10 lines above the
 >>> abstract, that says "Obsoletes: 5721 (if approved)".
 >>
 >> The IESG put this into the nits check before my time. The Last Call
 >> and publication announcements normally contain only the abstract,
 >> not the metadata above, and I believe the thinking was that if you
 >> are a person who scans through those announcements, you probably
 >> would (and would want to) take notice of documents that purport to
 >> obsolete or update document that you recognize. We could probably
 >> change the tool to add the metadata to the announcements, but
 >> apparently quite a few people read "abstracting" services that grab
 >> the abstracts of newly published documents. Not much we can do for
 >> them.
 >>
 >> It's certainly useful to some folks. Necessary? (*Shrug*) Not
 >> enough wasted bits for me to care one way or the other.
 >>
 >
 > As a Gen-ART reviewer, I called it out for exactly the reasons Pete
 > mentions, and care about the same amount :-) But putting it there
 > seems to hurt nothing, and maybe help just a little bit in some
 > cases.

Hanging fuzzy dice from a car mirror doesn't hurt anything and might 
attract people who otherwise would pay no attention to the vehicle, but 
that doesn't mean that there should be a law requiring everyone to 
display said dice.


From presnick@qualcomm.com  Sat Sep 22 07:33:35 2012
Return-Path: <presnick@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 018D321F8581; Sat, 22 Sep 2012 07:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.543
X-Spam-Level: 
X-Spam-Status: No, score=-106.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFu+b+udfdHd; Sat, 22 Sep 2012 07:33:29 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE9D21F857D; Sat, 22 Sep 2012 07:33:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1348324409; x=1379860409; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; bh=31EklNGi7YxMPgqBwkfio/xuA6XnwZtF5+8ZG5I76gU=; b=Lhu3EC1ofrm5hdWpxS0pZElx6CCIQW+mqvxTTZtf7A/ZnFKCaaRuAnog jWG3GFhY+WZDqkMlx6i47dgcdcXz3iXkKZakC16EajK8fCmpvWaduNME4 DUfCp+ey1TewLWOg9Y7ePEwv6gOqz0mVv+cGuQouyse58Zbn+xwmVV4gT w=;
X-IronPort-AV: E=McAfee;i="5400,1158,6842"; a="237678059"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 22 Sep 2012 07:33:28 -0700
X-IronPort-AV: E=Sophos;i="4.80,467,1344236400"; d="scan'208";a="331302837"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 22 Sep 2012 07:33:25 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.1; Sat, 22 Sep 2012 07:33:25 -0700
Message-ID: <505DCC33.2070400@qualcomm.com>
Date: Sat, 22 Sep 2012 09:33:23 -0500
From: Pete Resnick <presnick@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: <dcrocker@bbiw.net>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net>
In-Reply-To: <505D0AE8.8060208@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Sep 2012 14:33:35 -0000

Answering two bits I happen know the answers to:

On 9/21/12 7:48 PM, Dave Crocker wrote:

>> --- DRAFT IESG STATEMENT ---
>> [...]
>> While entries in the I-D Repository are subject to change or removal
>> at any time,
>
> They are?  Is this new?  I thought the only established removal policy 
> was the regular 6-month timeout.

2026, section 2.2:

    An Internet-Draft is NOT a means of "publishing" a specification;
    specifications are published through the RFC mechanism described in
    the previous section.  Internet-Drafts have no formal status, and are
    subject to change or removal at any time.

That language dates back to RFC 1310 (March 1992). Not new.

>> An I-D will only be removed from the Public I-D Archive with consensus
>> of the IESG.  There are two situations when the IESG will take this
>> action.  First, to comply with a duly authorized court order.  Second,
>> to resolve some form of abuse.
>
> This second basis looks sufficiently broad and vague to invite its own 
> abuse and certainly inconsistent application.  Did IETF counsel 
> express comfort with this language?

Counsel actually wanted us to broaden the language, thinking "abuse" was 
too limiting.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From john-ietf@jck.com  Sat Sep 22 07:53:45 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF7C21F8678; Sat, 22 Sep 2012 07:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level: 
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WDQNMTYeM3DF; Sat, 22 Sep 2012 07:53:44 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DD0E121F859C; Sat, 22 Sep 2012 07:53:43 -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 1TFR5L-00090d-HO; Sat, 22 Sep 2012 10:53:35 -0400
Date: Sat, 22 Sep 2012 10:53:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qualcomm.com>, dcrocker@bbiw.net
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <1256B807AD171A76EA2CE738@JcK-HP8200.jck.com>
In-Reply-To: <505DCC33.2070400@qualcomm.com>
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net> <505DCC33.2070400@qualcomm.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 Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Sep 2012 14:53:45 -0000

--On Saturday, September 22, 2012 09:33 -0500 Pete Resnick
<presnick@qualcomm.com> wrote:

>...
>>> An I-D will only be removed from the Public I-D Archive with
>>> consensus of the IESG.  There are two situations when the
>>> IESG will take this action.  First, to comply with a duly
>>> authorized court order.  Second, to resolve some form of
>>> abuse.
>> 
>> This second basis looks sufficiently broad and vague to
>> invite its own  abuse and certainly inconsistent application.
>> Did IETF counsel  express comfort with this language?
> 
> Counsel actually wanted us to broaden the language, thinking
> "abuse" was too limiting.

Yeah.  I think the new language is a considerable improvement
and I can live with it, but only because I think "abuse" can be
interpreted very broadly should someone be able to convince the
IESG there is a problem or unfairness associated with leaving
things up.  My preference would be to go back to what I believe
was the spirit of the 2026 "...no formal status, and are subject
to change or removal at any time", leaving the IESG with
discretion to consider individual cases and decide what to do
without having to assign them to a category (whether "court
order" or "abuse").

Three observations in that context:

	-- Whatever the language of BCP 78/79, or even the IPR
	language of 2026, _permits_, doesn't imply that we
	should do it, only that we (perhaps) can
	
	-- I think the IESG should be more sympathetic to
	removal requests for earlier documents that were posted
	with the understanding that there would be no
	IETF-maintained authoritative public archive than to
	ones posted after the public archive became the
	practice.  That is not to suggest that all requests
	about early document should be approved or that all
	requests about later ones should be denied, but, as a
	general guideline, I think it would be helpful.  
	
	-- I also believe that the IESG should be more reluctant
	to remove a document whose successors are still under
	active development (especially the immediately-previous
	or otherwise very recent drafts for which diffs are
	important) than documents that are only of historical
	interest.   If nothing else, it is easy to make a case
	that having those recent documents with active
	successors in the archive is serving the needs of the
	IETF, while it is somewhat harder to defend keeping a
	document that is of historical interest only on that
	basis.

None of the above has to be written into a policy, but I believe
that the interests of the overall community and suitable respect
for the desires of authors, would be better served by such
guidelines than by, e.g., trying to figure out a specific and
yet sufficiently flexible definition of "abuse".

    john


From dcrocker@bbiw.net  Sat Sep 22 08:49:52 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA0D421F86C8; Sat, 22 Sep 2012 08:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id urDfctszPS0E; Sat, 22 Sep 2012 08:49:52 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5154721F86C7; Sat, 22 Sep 2012 08:49:51 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8MFnkIX012194 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 22 Sep 2012 08:49:46 -0700
Message-ID: <505DDE10.5050303@bbiw.net>
Date: Sat, 22 Sep 2012 08:49:36 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net> <505DCC33.2070400@qualcomm.com>
In-Reply-To: <505DCC33.2070400@qualcomm.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]); Sat, 22 Sep 2012 08:49:46 -0700 (PDT)
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Sep 2012 15:49:52 -0000

On 9/22/2012 7:33 AM, Pete Resnick wrote:
> Counsel actually wanted us to broaden the language, thinking "abuse" was
> too limiting.


Wow.  Well, that certainly satisfies the question I asked.

Thanks, I think.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From Henning.Schulzrinne@fcc.gov  Sun Sep 23 19:17:22 2012
Return-Path: <Henning.Schulzrinne@fcc.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 1232721F8470 for <ietf@ietfa.amsl.com>; Sun, 23 Sep 2012 19:17:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTB4XA1ie3j3 for <ietf@ietfa.amsl.com>; Sun, 23 Sep 2012 19:17:21 -0700 (PDT)
Received: from dmz-mail2.fcc.gov (dmz-mail2.fcc.gov [192.104.54.11]) by ietfa.amsl.com (Postfix) with ESMTP id 293B221F844B for <ietf@ietf.org>; Sun, 23 Sep 2012 19:17:20 -0700 (PDT)
Received: from P2PXMB13.fccnet.win.fcc.gov ([fe80::6593:6526:65f8:66b7]) by p2pxcas02.fccnet.win.fcc.gov ([fe80::2d69:114:8552:212f%13]) with mapi id 14.01.0379.000; Sun, 23 Sep 2012 22:17:19 -0400
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Large-scale measurement effort (re)started
Thread-Topic: Large-scale measurement effort (re)started
Thread-Index: Ac2Z+rkp0zQ3X6hcQ8azVSRM0K0Cnw==
Date: Mon, 24 Sep 2012 02:17:19 +0000
Message-ID: <E6A16181E5FD2F46B962315BB05962D00D9614E8@p2pxmb13.fccnet.win.fcc.gov>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.104.54.63]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Walter Johnston <Walter.Johnston@fcc.gov>, James Miller <James.Miller@fcc.gov>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Sep 2012 02:17:22 -0000

We just published an initial architecture and requirements draft on large-s=
cale performance measurement architectures at

http://datatracker.ietf.org/doc/draft-schulzrinne-lmap-requirements/

This is motivated by the FCC "Measuring Broadband America" effort [see http=
://www.fcc.gov/measuring-broadband-america/2012/july] and related efforts e=
lsewhere.

Comments on this new effort are appreciated on the LMAP mailing list [https=
://www.ietf.org/mailman/listinfo/lmap]

Henning

From warren@kumari.net  Mon Sep 24 00:47:33 2012
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA9FC21F8555 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 00:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.043
X-Spam-Level: 
X-Spam-Status: No, score=-101.043 tagged_above=-999 required=5 tests=[AWL=1.556, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6QQz-aATUT0 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 00:47:33 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5E921F8543 for <ietf@ietf.org>; Mon, 24 Sep 2012 00:47:32 -0700 (PDT)
Received: from [192.168.1.201] (unknown [62.50.236.58]) by vimes.kumari.net (Postfix) with ESMTPSA id 839101B4015B; Mon, 24 Sep 2012 03:47:31 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Subject: Re: [IETF] Large-scale measurement effort (re)started
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <E6A16181E5FD2F46B962315BB05962D00D9614E8@p2pxmb13.fccnet.win.fcc.gov>
Date: Mon, 24 Sep 2012 09:47:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0ADC5E6-9D82-47EC-B699-D85CC232A971@kumari.net>
References: <E6A16181E5FD2F46B962315BB05962D00D9614E8@p2pxmb13.fccnet.win.fcc.gov>
To: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
X-Mailer: Apple Mail (2.1486)
Cc: Walter Johnston <Walter.Johnston@fcc.gov>, James Miller <James.Miller@fcc.gov>, "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, 24 Sep 2012 07:47:34 -0000

On Sep 24, 2012, at 4:17 AM, Henning Schulzrinne =
<Henning.Schulzrinne@fcc.gov> wrote:

> We just published an initial architecture and requirements draft on =
large-scale performance measurement architectures at
>=20
> http://datatracker.ietf.org/doc/draft-schulzrinne-lmap-requirements/
>=20
> This is motivated by the FCC "Measuring Broadband America" effort [see =
http://www.fcc.gov/measuring-broadband-america/2012/july] and related =
efforts elsewhere.
>=20
> Comments on this new effort are appreciated on the LMAP mailing list =
[https://www.ietf.org/mailman/listinfo/lmap]

Just to confirm, this is the same list that was created on 13th April, =
with "I will be providing more details and background shortly,=85" and =
"Please join the discussion on the list if you're interested in this =
topic.".

And an (unanswered) question from  Stephane  on the same day?
And then, Fri, 15 Jun 2012 a (unanswered) request from Matthew Ford for =
more details and background?
And then (also unanswered) the same from me on Wed, 11 Jul 2012

Same list, yes?

W

>=20
> Henning
>=20


From julian.reschke@gmx.de  Mon Sep 24 05:03:53 2012
Return-Path: <julian.reschke@gmx.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 688FF21F8627 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 05:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.254
X-Spam-Level: 
X-Spam-Status: No, score=-102.254 tagged_above=-999 required=5 tests=[AWL=-1.144, BAYES_05=-1.11, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yt8Kmh-v7jKY for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 05:03:52 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 3C3FB21F8623 for <ietf@ietf.org>; Mon, 24 Sep 2012 05:03:52 -0700 (PDT)
Received: (qmail invoked by alias); 24 Sep 2012 12:03:46 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp002) with SMTP; 24 Sep 2012 14:03:46 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+cr+pH6fOcX/FXu7VRX7ZOwC6YoPzfSeWHgZhYku k8YzjwC6EUSogB
Message-ID: <50604C1A.7090901@gmx.de>
Date: Mon, 24 Sep 2012 14:03:38 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 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, 24 Sep 2012 12:03:53 -0000

FYI:

Quoting AvK in
<http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Sep/0297.html>:

> The plan is to obsolete the RFCs. But yes, I will add some references
> in the Goals section most likely. Similar to what has been done in the
> DOM Standard.

Note this is about RFC 3986, which is a Full Standard.

Best regards, Julian

From Henning.Schulzrinne@fcc.gov  Mon Sep 24 05:15:53 2012
Return-Path: <Henning.Schulzrinne@fcc.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 21ED221F863B for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 05:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.949
X-Spam-Level: 
X-Spam-Status: No, score=-5.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s1iRRy3aP9V0 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 05:15:52 -0700 (PDT)
Received: from dmz-mail1.fcc.gov (dmz-mail1.fcc.gov [192.104.54.105]) by ietfa.amsl.com (Postfix) with ESMTP id 91E5D21F8611 for <ietf@ietf.org>; Mon, 24 Sep 2012 05:15:52 -0700 (PDT)
Received: from P2PXMB13.fccnet.win.fcc.gov ([fe80::6593:6526:65f8:66b7]) by p2pxcas01.fccnet.win.fcc.gov ([fe80::1d27:de47:ad2e:9062%13]) with mapi id 14.01.0379.000; Mon, 24 Sep 2012 08:15:50 -0400
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: Warren Kumari <warren@kumari.net>
Subject: RE: [IETF] Large-scale measurement effort (re)started
Thread-Topic: [IETF] Large-scale measurement effort (re)started
Thread-Index: Ac2Z+rkp0zQ3X6hcQ8azVSRM0K0CnwAT6ayAAADqBFA=
Date: Mon, 24 Sep 2012 12:15:49 +0000
Message-ID: <E6A16181E5FD2F46B962315BB05962D00D96170B@p2pxmb13.fccnet.win.fcc.gov>
References: <E6A16181E5FD2F46B962315BB05962D00D9614E8@p2pxmb13.fccnet.win.fcc.gov>, <C0ADC5E6-9D82-47EC-B699-D85CC232A971@kumari.net>
In-Reply-To: <C0ADC5E6-9D82-47EC-B699-D85CC232A971@kumari.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.104.54.63]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Walter Johnston <Walter.Johnston@fcc.gov>, James Miller <James.Miller@fcc.gov>, "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, 24 Sep 2012 12:15:53 -0000

Yes, it's the same mailing list. Unfortunately, it took us a bit longer tha=
n we had hoped to pull together the draft - my apologies. It should answer =
many of the "what is this about" questions and I look forward to the discus=
sion on the list. I hope you can contribute to the work going forward.=0A=
=0A=
Henning=0A=
=0A=
________________________________________=0A=
From: Warren Kumari [warren@kumari.net]=0A=
Sent: Monday, September 24, 2012 3:47 AM=0A=
To: Henning Schulzrinne=0A=
Cc: Warren Kumari; ietf@ietf.org; Walter Johnston; James Miller=0A=
Subject: Re: [IETF] Large-scale measurement effort (re)started=0A=
=0A=
On Sep 24, 2012, at 4:17 AM, Henning Schulzrinne <Henning.Schulzrinne@fcc.g=
ov> wrote:=0A=
=0A=
> We just published an initial architecture and requirements draft on large=
-scale performance measurement architectures at=0A=
>=0A=
> http://datatracker.ietf.org/doc/draft-schulzrinne-lmap-requirements/=0A=
>=0A=
> This is motivated by the FCC "Measuring Broadband America" effort [see ht=
tp://www.fcc.gov/measuring-broadband-america/2012/july] and related efforts=
 elsewhere.=0A=
>=0A=
> Comments on this new effort are appreciated on the LMAP mailing list [htt=
ps://www.ietf.org/mailman/listinfo/lmap]=0A=
=0A=
Just to confirm, this is the same list that was created on 13th April, with=
 "I will be providing more details and background shortly,=85" and "Please =
join the discussion on the list if you're interested in this topic.".=0A=
=0A=
And an (unanswered) question from  Stephane  on the same day?=0A=
And then, Fri, 15 Jun 2012 a (unanswered) request from Matthew Ford for mor=
e details and background?=0A=
And then (also unanswered) the same from me on Wed, 11 Jul 2012=0A=
=0A=
Same list, yes?=0A=
=0A=
W=0A=
=0A=
>=0A=
> Henning=0A=
>=0A=
=0A=

From Martin.Stiemerling@neclab.eu  Mon Sep 24 05:26:07 2012
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 4C91121F852E; Mon, 24 Sep 2012 05:26:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.434
X-Spam-Level: 
X-Spam-Status: No, score=-102.434 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZitC73l53pt; Mon, 24 Sep 2012 05:26:06 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1066F21F84D7; Mon, 24 Sep 2012 05:26:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 7267C101F20; Mon, 24 Sep 2012 14:26:05 +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 GRCnb9-00kGc; Mon, 24 Sep 2012 14:26:05 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 572DB101F1D; Mon, 24 Sep 2012 14:25:50 +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; Mon, 24 Sep 2012 14:24:54 +0200
Message-ID: <50605139.4070907@neclab.eu>
Date: Mon, 24 Sep 2012 14:25:29 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: Songhaibin <haibin.song@huawei.com>
Subject: Re: [decade] DECADE WG to be closed
References: <50531AB3.6090601@neclab.eu> <E33E01DFD5BEA24B9F3F18671078951F23B31E95@szxeml534-mbx.china.huawei.com> <50583257.2080404@neclab.eu> <E33E01DFD5BEA24B9F3F18671078951F23B33FA6@szxeml534-mbx.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23B33FA6@szxeml534-mbx.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Cc: "decade@ietf.org" <decade@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, 24 Sep 2012 12:26:07 -0000

Dear Haibin,

It is really strange that you copy private emails between you, Richard, 
and me to the general public. Despite the fact that I do not mind about 
this, it is really odd.

I won't reply to this email.

   Martin

On 09/22/2012 08:52 AM, Songhaibin wrote:
> Dear Martin,
>
>> -----Original Message-----
>> From: Martin Stiemerling [mailto:martin.stiemerling@neclab.eu]
>> Sent: Tuesday, September 18, 2012 4:36 PM
>> To: Songhaibin
>> Cc: Richard Woundy
>> Subject: Re: DECADE WG to be closed
>>
>> Dear Haibin,
>>
>> On 09/17/2012 11:39 AM, Songhaibin wrote:
>>> Dear Martin,
>>>
>>> Hope everything goes well with you and thank you very much for your efforts
>> to reviewing the drafts in detail and giving guidance.
>>>
>>> As I agree with most of your comments to the DECADE requirements draft, but
>> I have to say IMO the architecture document is not that bad. This document gives
>> a clear description of the DECADE server/client components and
>> implementation/design principals which will be reflected in the protocols, IMO
>> this is what an architecture document should do.
>>>
>>> I do not agree there is lack of technical substances to design a base protocol
>> which can satisfy the transport and resource control requirements for content
>> distribution applications. Some detailed design choices are still not very clear, and
>> need efforts for them.
>>>
>>> And recently, the energy is growing, we recently received a lot of list discussion
>> including comments from Kostas about the requirements and architecture and
>> also a new individual draft for the service discovery was submitted.
>>
>> The energy has indeed grown in the WG since before the summer. But, I
>> indicated in my email from mid of June that I have doubts on the
>> technical quality of the DECADE drafts. These doubts have turned into
>> certainty, i.e., see the my AD reviews of the requirements and the
>> architecture.
>>
>> The technical quality of the drafts would be ok, if the WG would be at
>> the beginning of the process of discussing and writing those drafts, but
>> it is not acceptable at the end when the drafts are intended to become RFCs:
>> The technical base is just to weak to continue from, even after spending
>> time and effort of the WG participants for more than 2 years.
>
> The requirements document was accepted on Oct. 18, 2010, and the architecture draft was accepted on March 7, 2011.
>
>>
>> Another important data point, as mentioned earlier:
>> There has been public feedback from IETF community members, such as Dave
>> Crocker and Carsten Bormann, which questioned the technical base of
>> DECADE as a whole. This happened at the end of the 2011 and in the first
>> quarter of 2012.
>
>> The was no and still has not been an adequate response from the DECADE
>> WG to these reviews. For instance, the requirements did get a lot of
>> feedback from Dave Crocker, but this feedback was never addressed in an
>> email. I also have been unable to sort out what parts of the feedback
>> has been addressed in the updated draft and how, and what parts have not
>> been addressed.
>
> I believe all those comments were addressed in the current draft, as I joined the discussion with the authors to address the comments. Their efforts should be respected. The authors and I would like Dave and Carsten to check the draft with their comments, if they are interested. While I admit answering in the mailing list is a main method to resolve comments, but it is not the only method.
>
>>
>> I have also received much stronger feedback about the DECADE WG in
>> private emails to me. Again from long standing IETF community members
>> that send me feedback arguing that DECADE is not having a technical base
>> to build on top of.
>
> OK. But general rule for IETF is rough consensus, not private emails. Why not discuss their questions in the list?
>
>>
>> You have asked in your other email to give more time to the WG until the
>> next IETF meeting in November. This would be one possible way forward,
>> but I do know about the past 6 months after the IETF meeting in Paris.
>> Not a lot has happened during this period in order to improve the WG
>> drafts, in the sense that there is a solid technical base where DECADE
>> could continue to work from.
>
> I can answer If your question about the technical base can be more specific.
>
>>
>> Even if you and the whole WG would start to work full-time on the
>> drafts, it still would take longer than to the next IETF meeting to move
>> the requirements and architecture forward. My gut guessing is that it
>> will take at least until March 2013.
>
>> To give an example:
>> It is completely unclear how the resources on a DECADE server are
>> supposed to be managed and how this management is mapped to the protocol
>> split of SDT, DRP, and other management protocols.
>> Parts of it, such as setting the permissions of data objects clearly
>> belongs to the DRP, and it is sort of stated in a vague way in the
>> architecture, but it is not documented in a comprehensive way. Other
>> parts, such as the accounting is probably not part of the the DRP nor
>> SDT, but there is supposedly another interface that is needed for this.
>>
>> Has this been discussed at any point in the WG?
>
> I just read the email that Richard answered these questions with text from the current drafts. And I agree with his answers.
>
> While I respect that AD can make the decision of closing a WG, but I see a dozen of emails expressed their disappointment.
>
> BR,
> -Haibin
>
>
>> Given the above points and my summaries out of the last email and the
>> one of 6/12, the DECADE WG is going to be closed by today.
>>
>> The DECADE WG mailing list will remain open until the end of the year,
>> to let the people a chance to discuss how to go forward with the drafts.
>>
>> As suggest in my earlier email:
>> The participants are free to overhaul the drafts and to submit them as
>> individual submissions to the RFC Editor's Independent Stream.
>>
>>
>> The decisions to close the WG can be of course appealed via the IETF
>> appeal process:
>> See 'Appeals and PR-Actions' under http://www.ietf.org/iesg/ and RFC 2026.
>>
>>     Martin
>>
>>>
>>> BR,
>>> -Haibin
>>>
>>>
>>>> -----Original Message-----
>>>> From: Martin Stiemerling [mailto:martin.stiemerling@neclab.eu]
>>>> Sent: Friday, September 14, 2012 7:53 PM
>>>> To: Songhaibin; Richard Woundy
>>>> Subject: DECADE WG to be closed
>>>>
>>>> Dear Rich and Haibin,
>>>>
>>>> I have finally done my AD review for the DECADE architecture draft after
>>>> finishing the DECADE requirements draft.
>>>>
>>>> The first feedback for the DECADE architecture draft has been provided
>>>> in the datatracker and sent to the authors and you by email.
>>>>
>>>> Both drafts are in an extremely bad shape, i.e., they would require a
>>>> major overhaul and have been sent back to the working group due to lack
>>>> of technical quality.
>>>>
>>>> I have already expressed my concerns about the energy and the lack of
>>>> technical confidence in the group in my summary email of 6/12. The
>>>> requirements and architecture drafts got advanced towards the IESG
>>>> afterwards. The push for energy was good.
>>>>
>>>> However, after reviewing the two key drafts, requirements and
>>>> architecture, and receiving feedback from IETF community members, I have
>>>> come to the conclusion that the DECADE working group lacks a sound
>>>> technical ground.
>>>>
>>>> The DECADE group started its work in end of April 2010 and is now
>>>> working for more than 2 years on the milestones/drafts. The time isn't a
>>>> big deal, but after 2 years I would have expected that the documents are
>>>> on a good technical level where the WG can build on top of.
>>>>
>>>> The issues for the potential future protocol works is that if the basics
>>>> are not well understood and documented, how can the protocols be
>>>> designed in a comprehensive and technical sound way?
>>>> I cannot see this anymore.
>>>> This was also documented in my email on 6/12:
>>>> "
>>>> I have seen reviews for the ps, the reqs, and the architecture drafts
>>>> which go all in the same direction: where is the technical substance,
>>>> DECADE will built on?
>>>>
>>>> The last meeting in Paris was really discouraging with respect to the
>>>> technical substance...
>>>> Yet another sign of lack of energy in the WG...
>>>> "
>>>>
>>>> The WG did get a grace period starting after the IETF meeting in Paris
>>>> and had the chance to really show that it is moving in the right
>>>> direction. However, the current state does still not document this and
>>>> therefore the DECADE WG will be closed in the next week. I will inform
>>>> the WG on Tuesday afternoon CEST.
>>>>
>>>> The draft authors of the requirements, architecture, and also the
>>>> Integration Examples of DECADE System can submit the respective drafts
>>>> via the Independent Stream of the RFC editor (see
>>>> http://tools.ietf.org/html/rfc6548 for further information), if they
>>>> wish to.
>>>>
>>>> Regards,
>>>>
>>>>      Martin
>>>>
>>>> --
>>>> IETF Transport Area Director
>>>>
>>>> martin.stiemerling@neclab.eu
>>>>
>>>> NEC Laboratories Europe - Network Research Division NEC Europe Limited
>>>> Registered Office: NEC House, 1 Victoria Road, London W3 6BL
>>>> Registered in England 283
>>
>> --
>> martin.stiemerling@neclab.eu
>>
>> NEC Laboratories Europe - Network Research Division NEC Europe Limited
>> Registered Office: NEC House, 1 Victoria Road, London W3 6BL
>> Registered in England 283

-- 
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe - Network Research Division NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 283

From housley@vigilsec.com  Mon Sep 24 07:02:32 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8360D21F8783 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 07:02:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XkbkvkSJofp for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 07:02:31 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 668EF21F8782 for <ietf@ietf.org>; Mon, 24 Sep 2012 07:02:31 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id EE2859A4003; Mon, 24 Sep 2012 10:02:42 -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 6drIY8Ea6TLe; Mon, 24 Sep 2012 10:02:17 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C52839A4002; Mon, 24 Sep 2012 10:02:41 -0400 (EDT)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <505D0AE8.8060208@dcrocker.net>
Date: Mon, 24 Sep 2012 10:02:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB0202DA-1D59-4E63-BBD9-E40F917D91C1@vigilsec.com>
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
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, 24 Sep 2012 14:02:32 -0000

Dave:

>> The IESG has updated the draft IESG Statement based on the many =
comments that have been received.  It is clear that the community wants =
the IESG to be able to remove an Internet-Draft from the Public I-D =
Archive without a court order to do so.  That said, the IESG firmly =
believes that the collection of I-Ds provide important historical =
records for the open and transparent operation of the IETF.  Therefore, =
removal of a I-D from the  Public I-D Archive should teated as a =
significant event.
>>=20
>> Comments from the community are solicited on the revised draft IESG =
statement.
>>=20
>> On behalf of the IESG,
>> Russ
>>=20
>> --- DRAFT IESG STATEMENT ---
>>=20
>> SUBJECT: Removal of an Internet-Draft from the IETF Web Site
>>=20
>> Internet-Drafts (I-Ds) are working documents of the IETF.  I-Ds =
provide
>> important historical records for the open and transparent operation =
of
>> the IETF.  Other individuals and groups, including the IAB and IRTF
>> Research Groups, have chosen to distribute working documents as I-Ds.
>=20
> The IAB and IRTF are not part of the IETF?  The Independent stream =
also uses I-Ds.  Isn't it part of the IETF?

No.  The Independent Stream is not part of the IETF.  Like the IAB and =
the IRTF, the independent Stream has chosen to use I-Ds.

RFC 4844 says:

5.1.4.  Independent Submission Stream

   The RFC Series has always served a broader Internet technical
   community than the IETF.  The "Independent Submission" stream is
   defined to provide review and (possible) approval of documents that
   are outside the scope of the streams identified above.

   Generally speaking, approval of documents in this stream falls under
   the purview of the RFC Editor, and the RFC Editor seeks input to its
   review from the IESG.

   The process for reviewing and approving documents in the Independent
   Submission stream is defined by

   o  Independent Submissions to the RFC Editor (RFC 4846 [RFC4846]).

   o  The IESG and RFC Editor Documents: Procedures (RFC 3932
      [RFC3932]).

(Since RFC 4844 was written, RFC3932 was obsoleted by RFC 5742.)

>=20
>> I-Ds are stored in two places on the IETF web site.  First, current =
I-Ds
>> are stored in the I-D Repository.  Second, current and past I-Ds are
>> stored in a Public I-D Archive.
>>=20
>> While entries in the I-D Repository are subject to change or removal
>> at any time,
>=20
> They are?  Is this new?  I thought the only established removal policy =
was the regular 6-month timeout.

No, this is not new.  It goes back to RFC 1310 in March 1992.  If you =
publish draft-crocker-blah-blah-00.txt, is is very ofter replaced by =
-01.  The -00 is taken down before the six month expiration.

RFC 1310 said:

   An Internet Draft that is published as an RFC is removed from the
   Internet Draft directory.  A document that has remained unchanged
   in the Internet Drafts directory for more than six months without
   being recommended by the IESG for publication as an RFC is simply
   removed from the Internet Draft directory.  At any time, an
   Internet Draft may be replace by a more recent version of the same
   specification, restarting the six-month timeout period.

This remains today; the I-D boilerplate says:

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

>>               I-Ds generally remain in the Public I-D Archive to =
support
>> easy comparison with previous versions.  This availability =
facilitates
>> review, comment, and revision.
> >
>> An entry in the I-D Repository is removed as part of normal process
>> when it expires after six months, when it is replaced by a subsequent
>> I-D, or when it is replaced by the publication of an RFC.  In all
>> of these situations, the I-D remains in the Public I-D Archive.
>=20
> The text up to this point mostly looks like a general set of policy =
assertions about I-Ds.  Those need to exist separately as a formal =
policy statement about the series and its archive(s).
>=20
> That would leave the current statement to focus on its specific topic.

These were included to provide context for the policy statement.  As we =
have seen on this thread, there has been at least as much discussion =
about these background paragraphs as the policy.

>> An I-D will only be removed from the Public I-D Archive with =
consensus
>> of the IESG.  There are two situations when the IESG will take this
>> action.  First, to comply with a duly authorized court order.  =
Second,
>> to resolve some form of abuse.
>=20
> This second basis looks sufficiently broad and vague to invite its own =
abuse and certainly inconsistent application.  Did IETF counsel express =
comfort with this language?

Counsel has been consulted.  After exchanging several messages, this is =
the resulting text.  This text was never a part that was edited in the =
exchange.

>> If possible, a removed I-D will be
>> replaced with a tombstone file that describes the reason that the I-D
>> was removed from the Public I-D Archive.
>>=20
>> When an I-D is removed from the Public I-D Archive, a copy will be =
kept
>> in a location accessible only by the IETF Leadership and the IETF
>> Secretariat.  This private location may be searched by the IETF
>> Leadership or the IETF Secretariat when responding to appeals,
>> responding to subpoenas, or otherwise handling to legal matters.
>=20
> Interesting.  An archive archive.
>=20
> IETF "leadership" isn't a formal term.  Who does it include/exclude?  =
WG Chairs?  Why?  Why not?

I think it is fairly clear that the "leadership" is a party that would =
need access to this material when "responding to appeals, responding to =
subpoenas, or otherwise handling to legal matters."  I proposed this =
term because the parties that need access may well depend on the nature =
of the legal matter.
=20
> Over time, given the number of people who hold various IETF leadership =
positions, this effectively gives access to a very large fraction of the =
IETF community.

I envision a mechanism where the access is only granted to the specific =
files needed to address the appeal, subpoena, or other legal matter.

Russ


From dhc@dcrocker.net  Mon Sep 24 09:27:47 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0739A21F87FC for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 09:27:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.567
X-Spam-Level: 
X-Spam-Status: No, score=-6.567 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWxDU49Rwwso for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 09:27:46 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3405D21F87F1 for <ietf@ietf.org>; Mon, 24 Sep 2012 09:27:46 -0700 (PDT)
Received: from [192.168.1.8] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8OGRiCQ002310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Sep 2012 09:27:45 -0700
Message-ID: <506089F2.1090601@dcrocker.net>
Date: Mon, 24 Sep 2012 09:27:30 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net> <DB0202DA-1D59-4E63-BBD9-E40F917D91C1@vigilsec.com>
In-Reply-To: <DB0202DA-1D59-4E63-BBD9-E40F917D91C1@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]); Mon, 24 Sep 2012 09:27:45 -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: Mon, 24 Sep 2012 16:27:47 -0000

Russ,

On 9/24/2012 7:02 AM, Russ Housley wrote:
> Dave:
>
>>> The IESG has updated the draft IESG Statement based on the many
>>> comments that have been received.  It is clear that the community
>>> wants the IESG to be able to remove an Internet-Draft from the
>>> Public I-D Archive without a court order to do so.

I hadn't remembered that we have existing text that already covers this, 
in RFC 2026.   (It's also worth noting that, apparently, IETF counsel 
considers the existing RFC 2026 text sufficient.)

What isn't clear is why you are promoting additional language which 
seems to conflict with 2026, introduces some vague terminology (abuse, 
leadership), and covers only a subset of I-Ds.


>> The IAB and IRTF are not part of the IETF?  The Independent stream
>> also uses I-Ds.  Isn't it part of the IETF?
>
> No.  The Independent Stream is not part of the IETF.  Like the IAB
> and the IRTF, the independent Stream has chosen to use I-Ds.
>
> RFC 4844 says:
>
> 5.1.4.  Independent Submission Stream
>
> The RFC Series has always served a broader Internet technical
> community than the IETF.  The "Independent Submission" stream is
> defined to provide review and (possible) approval of documents that
> are outside the scope of the streams identified above.

First, I note that you didn't respond about the IRTF or the IAB.  And my 
original query should have included the RFC Editor (which happens to 
fall under the IAB.)

Apparently you consider the IRTF, IAB and RFC Editor all to be outside 
the IETF.

Second, it appears that you are taking the "served a broader Internet 
technical community than the IETF" language as the basis for declaring 
the Independent Stream also to be outside of the IETF.

I think you are confusing the source with the agency and result that 
produces the output.

By implication, your assessment seems to mean that the only target for 
the output of working groups are people who participate in the IETF.  Or 
that anyone who consumes the output of an IETF working group is 
automatically part of the IETF.

That is, you seem to be confusing the source of authors with the 
publication vehicle itself and the target audience(s) of the work.

Independent Stream authors well might not be "part of" the IETF -- 
always a strange line of thinking, given that the IETF doesn't have 
members -- but that doesn't mean that the Stream itself is outside the IETF.



>> This second basis looks sufficiently broad and vague to invite its
>> own abuse and certainly inconsistent application.  Did IETF counsel
>> express comfort with this language?
 >
> Counsel has been consulted.  After exchanging several messages, this
> is the resulting text.  This text was never a part that was edited in
> the exchange.

You are saying that IETF Counsel did not offer comment on this bit of text?

Actually, I note that you didn't actually answer my question:  Does the 
IETF Counsel like the text?


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From haibin.song@huawei.com  Fri Sep 21 23:53:06 2012
Return-Path: <haibin.song@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 4E1C221F884D; Fri, 21 Sep 2012 23:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.971
X-Spam-Level: 
X-Spam-Status: No, score=-5.971 tagged_above=-999 required=5 tests=[AWL=0.628,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ecJzOAZrwHIY; Fri, 21 Sep 2012 23:53:02 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3BBA921F884A; Fri, 21 Sep 2012 23:53:01 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKX96813; Sat, 22 Sep 2012 06:53:00 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 22 Sep 2012 07:51:48 +0100
Received: from SZXEML422-HUB.china.huawei.com (10.82.67.161) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sat, 22 Sep 2012 07:52:18 +0100
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.70]) by szxeml422-hub.china.huawei.com ([10.82.67.161]) with mapi id 14.01.0323.003; Sat, 22 Sep 2012 14:52:11 +0800
From: Songhaibin <haibin.song@huawei.com>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>
Subject: RE: DECADE WG to be closed
Thread-Topic: DECADE WG to be closed
Thread-Index: AQHNkm+beTF1FP7MtkORFrVdv9nRf5eNxdIggAGAV4CABqD7AA==
Date: Sat, 22 Sep 2012 06:52:10 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F23B33FA6@szxeml534-mbx.china.huawei.com>
References: <50531AB3.6090601@neclab.eu> <E33E01DFD5BEA24B9F3F18671078951F23B31E95@szxeml534-mbx.china.huawei.com> <50583257.2080404@neclab.eu>
In-Reply-To: <50583257.2080404@neclab.eu>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.123]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 24 Sep 2012 09:41:35 -0700
Cc: "decade@ietf.org" <decade@ietf.org>, Richard Woundy <Richard_Woundy@cable.comcast.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, 22 Sep 2012 06:53:06 -0000

Dear Martin,

> -----Original Message-----
> From: Martin Stiemerling [mailto:martin.stiemerling@neclab.eu]
> Sent: Tuesday, September 18, 2012 4:36 PM
> To: Songhaibin
> Cc: Richard Woundy
> Subject: Re: DECADE WG to be closed
>=20
> Dear Haibin,
>=20
> On 09/17/2012 11:39 AM, Songhaibin wrote:
> > Dear Martin,
> >
> > Hope everything goes well with you and thank you very much for your eff=
orts
> to reviewing the drafts in detail and giving guidance.
> >
> > As I agree with most of your comments to the DECADE requirements draft,=
 but
> I have to say IMO the architecture document is not that bad. This documen=
t gives
> a clear description of the DECADE server/client components and
> implementation/design principals which will be reflected in the protocols=
, IMO
> this is what an architecture document should do.
> >
> > I do not agree there is lack of technical substances to design a base p=
rotocol
> which can satisfy the transport and resource control requirements for con=
tent
> distribution applications. Some detailed design choices are still not ver=
y clear, and
> need efforts for them.
> >
> > And recently, the energy is growing, we recently received a lot of list=
 discussion
> including comments from Kostas about the requirements and architecture an=
d
> also a new individual draft for the service discovery was submitted.
>=20
> The energy has indeed grown in the WG since before the summer. But, I
> indicated in my email from mid of June that I have doubts on the
> technical quality of the DECADE drafts. These doubts have turned into
> certainty, i.e., see the my AD reviews of the requirements and the
> architecture.
>=20
> The technical quality of the drafts would be ok, if the WG would be at
> the beginning of the process of discussing and writing those drafts, but
> it is not acceptable at the end when the drafts are intended to become RF=
Cs:
> The technical base is just to weak to continue from, even after spending
> time and effort of the WG participants for more than 2 years.

The requirements document was accepted on Oct. 18, 2010, and the architectu=
re draft was accepted on March 7, 2011.=20

>=20
> Another important data point, as mentioned earlier:
> There has been public feedback from IETF community members, such as Dave
> Crocker and Carsten Bormann, which questioned the technical base of
> DECADE as a whole. This happened at the end of the 2011 and in the first
> quarter of 2012.

> The was no and still has not been an adequate response from the DECADE
> WG to these reviews. For instance, the requirements did get a lot of
> feedback from Dave Crocker, but this feedback was never addressed in an
> email. I also have been unable to sort out what parts of the feedback
> has been addressed in the updated draft and how, and what parts have not
> been addressed.

I believe all those comments were addressed in the current draft, as I join=
ed the discussion with the authors to address the comments. Their efforts s=
hould be respected. The authors and I would like Dave and Carsten to check =
the draft with their comments, if they are interested. While I admit answer=
ing in the mailing list is a main method to resolve comments, but it is not=
 the only method.

>=20
> I have also received much stronger feedback about the DECADE WG in
> private emails to me. Again from long standing IETF community members
> that send me feedback arguing that DECADE is not having a technical base
> to build on top of.

OK. But general rule for IETF is rough consensus, not private emails. Why n=
ot discuss their questions in the list?

>=20
> You have asked in your other email to give more time to the WG until the
> next IETF meeting in November. This would be one possible way forward,
> but I do know about the past 6 months after the IETF meeting in Paris.
> Not a lot has happened during this period in order to improve the WG
> drafts, in the sense that there is a solid technical base where DECADE
> could continue to work from.

I can answer If your question about the technical base can be more specific=
.

>=20
> Even if you and the whole WG would start to work full-time on the
> drafts, it still would take longer than to the next IETF meeting to move
> the requirements and architecture forward. My gut guessing is that it
> will take at least until March 2013.

> To give an example:
> It is completely unclear how the resources on a DECADE server are
> supposed to be managed and how this management is mapped to the protocol
> split of SDT, DRP, and other management protocols.
> Parts of it, such as setting the permissions of data objects clearly
> belongs to the DRP, and it is sort of stated in a vague way in the
> architecture, but it is not documented in a comprehensive way. Other
> parts, such as the accounting is probably not part of the the DRP nor
> SDT, but there is supposedly another interface that is needed for this.
>=20
> Has this been discussed at any point in the WG?

I just read the email that Richard answered these questions with text from =
the current drafts. And I agree with his answers.

While I respect that AD can make the decision of closing a WG, but I see a =
dozen of emails expressed their disappointment.

BR,
-Haibin


> Given the above points and my summaries out of the last email and the
> one of 6/12, the DECADE WG is going to be closed by today.
>=20
> The DECADE WG mailing list will remain open until the end of the year,
> to let the people a chance to discuss how to go forward with the drafts.
>=20
> As suggest in my earlier email:
> The participants are free to overhaul the drafts and to submit them as
> individual submissions to the RFC Editor's Independent Stream.
>=20
>=20
> The decisions to close the WG can be of course appealed via the IETF
> appeal process:
> See 'Appeals and PR-Actions' under http://www.ietf.org/iesg/ and RFC 2026=
.
>=20
>    Martin
>=20
> >
> > BR,
> > -Haibin
> >
> >
> >> -----Original Message-----
> >> From: Martin Stiemerling [mailto:martin.stiemerling@neclab.eu]
> >> Sent: Friday, September 14, 2012 7:53 PM
> >> To: Songhaibin; Richard Woundy
> >> Subject: DECADE WG to be closed
> >>
> >> Dear Rich and Haibin,
> >>
> >> I have finally done my AD review for the DECADE architecture draft aft=
er
> >> finishing the DECADE requirements draft.
> >>
> >> The first feedback for the DECADE architecture draft has been provided
> >> in the datatracker and sent to the authors and you by email.
> >>
> >> Both drafts are in an extremely bad shape, i.e., they would require a
> >> major overhaul and have been sent back to the working group due to lac=
k
> >> of technical quality.
> >>
> >> I have already expressed my concerns about the energy and the lack of
> >> technical confidence in the group in my summary email of 6/12. The
> >> requirements and architecture drafts got advanced towards the IESG
> >> afterwards. The push for energy was good.
> >>
> >> However, after reviewing the two key drafts, requirements and
> >> architecture, and receiving feedback from IETF community members, I ha=
ve
> >> come to the conclusion that the DECADE working group lacks a sound
> >> technical ground.
> >>
> >> The DECADE group started its work in end of April 2010 and is now
> >> working for more than 2 years on the milestones/drafts. The time isn't=
 a
> >> big deal, but after 2 years I would have expected that the documents a=
re
> >> on a good technical level where the WG can build on top of.
> >>
> >> The issues for the potential future protocol works is that if the basi=
cs
> >> are not well understood and documented, how can the protocols be
> >> designed in a comprehensive and technical sound way?
> >> I cannot see this anymore.
> >> This was also documented in my email on 6/12:
> >> "
> >> I have seen reviews for the ps, the reqs, and the architecture drafts
> >> which go all in the same direction: where is the technical substance,
> >> DECADE will built on?
> >>
> >> The last meeting in Paris was really discouraging with respect to the
> >> technical substance...
> >> Yet another sign of lack of energy in the WG...
> >> "
> >>
> >> The WG did get a grace period starting after the IETF meeting in Paris
> >> and had the chance to really show that it is moving in the right
> >> direction. However, the current state does still not document this and
> >> therefore the DECADE WG will be closed in the next week. I will inform
> >> the WG on Tuesday afternoon CEST.
> >>
> >> The draft authors of the requirements, architecture, and also the
> >> Integration Examples of DECADE System can submit the respective drafts
> >> via the Independent Stream of the RFC editor (see
> >> http://tools.ietf.org/html/rfc6548 for further information), if they
> >> wish to.
> >>
> >> Regards,
> >>
> >>     Martin
> >>
> >> --
> >> IETF Transport Area Director
> >>
> >> martin.stiemerling@neclab.eu
> >>
> >> NEC Laboratories Europe - Network Research Division NEC Europe Limited
> >> Registered Office: NEC House, 1 Victoria Road, London W3 6BL
> >> Registered in England 283
>=20
> --
> martin.stiemerling@neclab.eu
>=20
> NEC Laboratories Europe - Network Research Division NEC Europe Limited
> Registered Office: NEC House, 1 Victoria Road, London W3 6BL
> Registered in England 283

From housley@vigilsec.com  Mon Sep 24 10:16:07 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8E121F8829 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 10:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJHV8yyeECT4 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 10:16:07 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 0F82421F8821 for <ietf@ietf.org>; Mon, 24 Sep 2012 10:16:07 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 0E08B9A4005; Mon, 24 Sep 2012 13:16:08 -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 s9Fc1sMtyvRP; Mon, 24 Sep 2012 13:16:03 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 50CE19A4003; Mon, 24 Sep 2012 13:16:07 -0400 (EDT)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <506089F2.1090601@dcrocker.net>
Date: Mon, 24 Sep 2012 13:16:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA05E028-F2DF-40EF-BFCC-C485B85E636B@vigilsec.com>
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net> <DB0202DA-1D59-4E63-BBD9-E40F917D91C1@vigilsec.com> <506089F2.1090601@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
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, 24 Sep 2012 17:16:07 -0000

Dave:

>>> This second basis looks sufficiently broad and vague to invite its
>>> own abuse and certainly inconsistent application.  Did IETF counsel
>>> express comfort with this language?
> >
>> Counsel has been consulted.  After exchanging several messages, this
>> is the resulting text.  This text was never a part that was edited in
>> the exchange.
>=20
> You are saying that IETF Counsel did not offer comment on this bit of =
text?
>=20
> Actually, I note that you didn't actually answer my question:  Does =
the IETF Counsel like the text?

While counsel offered comment on other parts of the text, none were =
offered on the part you cite.  I am sure that comments would have been =
offered on the part you cite if it caused concern.

Russ=

From jnc@mercury.lcs.mit.edu  Mon Sep 24 10:53:03 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C326B21F8834 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 10:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.301
X-Spam-Level: 
X-Spam-Status: No, score=-6.301 tagged_above=-999 required=5 tests=[AWL=0.298,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MM4UMpx-nqx7 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 10:53:03 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 570C621F882D for <ietf@ietf.org>; Mon, 24 Sep 2012 10:53:03 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 68C3618C0E4; Mon, 24 Sep 2012 13:53:02 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Message-Id: <20120924175302.68C3618C0E4@mercury.lcs.mit.edu>
Date: Mon, 24 Sep 2012 13:53:02 -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: Mon, 24 Sep 2012 17:53:03 -0000

    > From: Dave Crocker <dhc@dcrocker.net>

    > Apparently you consider the IRTF, IAB and RFC Editor all to be outside
    > the IETF.

You apparently seem (from this) to think they're not? Wow.

	Noel

From stpeter@stpeter.im  Mon Sep 24 11:41:48 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B0921F8892 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 11:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B9MsttBIEBWq for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 11:41:47 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B2F3A21F8891 for <ietf@ietf.org>; Mon, 24 Sep 2012 11:41:45 -0700 (PDT)
Received: from [64.101.72.41] (unknown [64.101.72.41]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id AD9C140062; Mon, 24 Sep 2012 12:43:03 -0600 (MDT)
Message-ID: <5060A964.5060001@stpeter.im>
Date: Mon, 24 Sep 2012 12:41:40 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de>
In-Reply-To: <50604C1A.7090901@gmx.de>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: URI <uri@w3.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, 24 Sep 2012 18:41:48 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/24/12 6:03 AM, Julian Reschke wrote:
> FYI:
> 
> Quoting AvK in 
> <http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Sep/0297.html>:
>
> 
>> The plan is to obsolete the RFCs. But yes, I will add some
>> references in the Goals section most likely. Similar to what has
>> been done in the DOM Standard.
> 
> Note this is about RFC 3986, which is a Full Standard.

Hi Julian,

It's not completely clear to me what Anne meant there by saying "the
plan is to obsolete the RFCs" (naturally that is not something that
anyone outside the IETF can do, although they can ignore the RFCs).
It's also not clear to me what the WHATWG HTML Living Standard [1]
really means by "willful violation" [2] -- e.g., is it just an
allowance for APIs and browser software to not be completely strict
about processing some input for the sake of backward compatibility
with existing (messy) web content, or is it an active attempt at
redefining core protocols? However, it is interesting that the willful
violations are not limited to RFC 3986: the spec also mentions willful
violations of RFC 2046, RFC 2616, RFC 2781, RFC 5322, EcmaScript,
XPath, XSLT, and Unicode. Quite a list...

Peter

[1] http://www.whatwg.org/specs/web-apps/current-work/

[2]
http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#willful-violation

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBgqWQACgkQNL8k5A2w/vxD/QCeNTDVz/kaXkhROIm1/N9QB5Tf
QroAoPI96pCgHUCnjZqGLjmCrqLBQ1ym
=Nscu
-----END PGP SIGNATURE-----

From jnc@mercury.lcs.mit.edu  Mon Sep 24 12:11:12 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 828C721F88A3 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 12:11:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.351
X-Spam-Level: 
X-Spam-Status: No, score=-6.351 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OGdovPtnyKnb for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 12:11:12 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id E452C21F88A2 for <ietf@ietf.org>; Mon, 24 Sep 2012 12:11:11 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 0E4C518C0E2; Mon, 24 Sep 2012 15:11:11 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-gp-intarea-obsolete-ipv4-options-iana-02.txt> (Formally Deprecating some IPv4 Options) to Internet Standard
Message-Id: <20120924191111.0E4C518C0E2@mercury.lcs.mit.edu>
Date: Mon, 24 Sep 2012 15:11:11 -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: Mon, 24 Sep 2012 19:11:12 -0000

    > The IESG has received a request from an individual submitter to
    > consider the following document:
    > - 'Formally Deprecating some IPv4 Options'
    > ...
    > The IESG plans to make a decision in the next few weeks, and solicits
    > final comments on this action. 

This seems like a Good Thing to me. With one possible exception (below), all
of these are clearly not useful.

I personally might have left the 'Traceroute' one off the list, since it
seems well-designed/defined, but i) nobody uses it, and ii) it's easy enough
to resurrect it if we ever do decide we need it, so I don't object to its
inclusion in this list.

	Noel

From tglassey@earthlink.net  Mon Sep 24 12:30:02 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C34C21F88AE for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 12:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[AWL=-0.021,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6AvwgKnKvnZ for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 12:30:01 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 64C8F21F88B4 for <ietf@ietf.org>; Mon, 24 Sep 2012 12:30:01 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=XSnBPLNAp4ObX1otXpMvvTCKKwmKv5uF06bDBCxJaAmLv++kuhUyMTh3+IMNAE2O; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TGELw-00011w-RH for ietf@ietf.org; Mon, 24 Sep 2012 15:30:00 -0400
Message-ID: <5060B4B6.7070903@earthlink.net>
Date: Mon, 24 Sep 2012 12:29:58 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Large-scale measurement effort (re)started
References: <E6A16181E5FD2F46B962315BB05962D00D9614E8@p2pxmb13.fccnet.win.fcc.gov> <C0ADC5E6-9D82-47EC-B699-D85CC232A971@kumari.net>
In-Reply-To: <C0ADC5E6-9D82-47EC-B699-D85CC232A971@kumari.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7915b827768fabd8d97b5899d630785f9f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Sep 2012 19:30:02 -0000

On 9/24/2012 12:47 AM, Warren Kumari wrote:
> On Sep 24, 2012, at 4:17 AM, Henning Schulzrinne <Henning.Schulzrinne@fcc.gov> wrote:
>
>> We just published an initial architecture and requirements draft on large-scale performance measurement architectures at
>>
>> http://datatracker.ietf.org/doc/draft-schulzrinne-lmap-requirements/
>>
>> This is motivated by the FCC "Measuring Broadband America" effort [see http://www.fcc.gov/measuring-broadband-america/2012/july] and related efforts elsewhere.
>>
>> Comments on this new effort are appreciated on the LMAP mailing list [https://www.ietf.org/mailman/listinfo/lmap]
> Just to confirm, this is the same list that was created on 13th April, with "I will be providing more details and background shortly,…" and "Please join the discussion on the list if you're interested in this topic.".
>
> And an (unanswered) question from  Stephane  on the same day?
> And then, Fri, 15 Jun 2012 a (unanswered) request from Matthew Ford for more details and background?
> And then (also unanswered) the same from me on Wed, 11 Jul 2012
>
> Same list, yes?
>
> W
This is a long-time coming and its appropriate for a number of areas.

Todd
>
>> Henning
>>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2441/5288 - Release Date: 09/23/12
>
>
>


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


From tglassey@earthlink.net  Mon Sep 24 12:30:59 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 135ED21F88B4; Mon, 24 Sep 2012 12:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6mU0kFZxuxcO; Mon, 24 Sep 2012 12:30:58 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFAC21F88AE; Mon, 24 Sep 2012 12:30:58 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Mca7Y/nXyO9QQ7Z3iSLpAsmqRT4vThLU4khyMg/J2AEzSF2kormxYbNSheWZwIOo; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TGEMs-0000cc-2W; Mon, 24 Sep 2012 15:30:58 -0400
Message-ID: <5060B4EF.8010605@earthlink.net>
Date: Mon, 24 Sep 2012 12:30:55 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf <ietf@ietf.org>, IPR@ietf.org
Subject: Neutering the impending patent wars... this is something the IETF can actually have a role in...
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec791122f7a1a83b9c26d4938ab7c38e2a4e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Sep 2012 19:30:59 -0000

You folks want to end the wars over patents - including mine? - OK I
agree its something that needs to happen but how? Apple v Samsung and
Grail Semi v Mitsubishi have created even stronger walls in the patent
worlds and these are becoming more and more of a show-stopper type of
road-block to innovation.

The problem is how to make patents and the protection they provide
something that is more powerful and which has a cost of enforcement
responsibility so that unenforced patents cannot be used as a weapon to
stifle competition in the marketplaces...

The key to doing that is actually pretty simple and it is in
establishing a method of defining the worth to an unenforced patent, as
to why, most patents issued today are empty threats - they will not be
enforced no matter how many infringements there are against them and
functionally this only serves to neuter the value proposition for the
patents themselves.

This is true today because there is no need to actively manage the
patents because patent owners have gotten away for years by saying that
their patents have no value (a bold faced lie by the way) and as such
only have a positive value when an infringement that they choose to
enforce a claim against happens... i.e. its mine but it has no value...
so then isn't the real issue in this in developing a common and
open-framework for establishing a value for an unenforced patent?

As to why - tax bounty... pure and simple.

This is an offer to change the world - and it can and should happen from
within a GSO.

Does the IETF want to be that entity?

Todd Glassey

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


From tglassey@earthlink.net  Mon Sep 24 12:36:27 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A03CD21F88A1 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 12:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.617
X-Spam-Level: 
X-Spam-Status: No, score=-2.617 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zgRRNdxrHOC7 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 12:36:26 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1A221F8893 for <ietf@ietf.org>; Mon, 24 Sep 2012 12:36:26 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=djF2+aH5xeWBNydA6q5gO80z7KrhB6lr1o2KeZPd1VhJnGoqa7InHGVvGnNmyS38; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TGES9-0006mt-NA for ietf@ietf.org; Mon, 24 Sep 2012 15:36:25 -0400
Message-ID: <5060B637.6070704@earthlink.net>
Date: Mon, 24 Sep 2012 12:36:23 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net> <DB0202DA-1D59-4E63-BBD9-E40F917D91C1@vigilsec.com>
In-Reply-To: <DB0202DA-1D59-4E63-BBD9-E40F917D91C1@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79ce0d8486a4cd25e39b0ca54ce83b4538350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Sep 2012 19:36:27 -0000

On 9/24/2012 7:02 AM, Russ Housley wrote:
> Dave:
Russ - can the Independent Submission Stream (ISS) be used to create a 
fully franchised IETF Standard Process???

i.e. could I for instance through the ISS process submit a I-D and a 
RFC-Framework Proposal with that? In this case the framework proposal 
would define the 'canonization process' for this specific piece of IP 
and set the milestones for this independent stream standard???

This would be a very very good thing I think if it were to become possible.

>>> The IESG has updated the draft IESG Statement based on the many comments that have been received.  It is clear that the community wants the IESG to be able to remove an Internet-Draft from the Public I-D Archive without a court order to do so.
Which will apply to its publication and continued use rights how?

I still think we need to answer the specific question as to what this 
actually means to the previous licensing...
>>> That said, the IESG firmly believes that the collection of I-Ds provide important historical records for the open and transparent operation of the IETF.  Therefore, removal of a I-D from the  Public I-D Archive should teated as a significant event.
>>>
>>> Comments from the community are solicited on the revised draft IESG statement.
>>>
>>> On behalf of the IESG,
>>> Russ
>>>
>>> --- DRAFT IESG STATEMENT ---
>>>
>>> SUBJECT: Removal of an Internet-Draft from the IETF Web Site
>>>
>>> Internet-Drafts (I-Ds) are working documents of the IETF.  I-Ds provide
>>> important historical records for the open and transparent operation of
>>> the IETF.  Other individuals and groups, including the IAB and IRTF
>>> Research Groups, have chosen to distribute working documents as I-Ds.
>> The IAB and IRTF are not part of the IETF?  The Independent stream also uses I-Ds.  Isn't it part of the IETF?
> No.  The Independent Stream is not part of the IETF.  Like the IAB and the IRTF, the independent Stream has chosen to use I-Ds.
>
> RFC 4844 says:
>
> 5.1.4.  Independent Submission Stream
>
>     The RFC Series has always served a broader Internet technical
>     community than the IETF.  The "Independent Submission" stream is
>     defined to provide review and (possible) approval of documents that
>     are outside the scope of the streams identified above.
>
>     Generally speaking, approval of documents in this stream falls under
>     the purview of the RFC Editor, and the RFC Editor seeks input to its
>     review from the IESG.
>
>     The process for reviewing and approving documents in the Independent
>     Submission stream is defined by
>
>     o  Independent Submissions to the RFC Editor (RFC 4846 [RFC4846]).
>
>     o  The IESG and RFC Editor Documents: Procedures (RFC 3932
>        [RFC3932]).
>
> (Since RFC 4844 was written, RFC3932 was obsoleted by RFC 5742.)
>
>>> I-Ds are stored in two places on the IETF web site.  First, current I-Ds
>>> are stored in the I-D Repository.  Second, current and past I-Ds are
>>> stored in a Public I-D Archive.
>>>
>>> While entries in the I-D Repository are subject to change or removal
>>> at any time,
>> They are?  Is this new?  I thought the only established removal policy was the regular 6-month timeout.
> No, this is not new.  It goes back to RFC 1310 in March 1992.  If you publish draft-crocker-blah-blah-00.txt, is is very ofter replaced by -01.  The -00 is taken down before the six month expiration.
>
> RFC 1310 said:
>
>     An Internet Draft that is published as an RFC is removed from the
>     Internet Draft directory.  A document that has remained unchanged
>     in the Internet Drafts directory for more than six months without
>     being recommended by the IESG for publication as an RFC is simply
>     removed from the Internet Draft directory.  At any time, an
>     Internet Draft may be replace by a more recent version of the same
>     specification, restarting the six-month timeout period.
>
> This remains today; the I-D boilerplate says:
>
>     Internet-Drafts are draft documents valid for a maximum of six months
>     and may be updated, replaced, or obsoleted by other documents at any
>     time.  It is inappropriate to use Internet-Drafts as reference
>     material or to cite them other than as "work in progress."
>
>>>                I-Ds generally remain in the Public I-D Archive to support
>>> easy comparison with previous versions.  This availability facilitates
>>> review, comment, and revision.
>>>
>>> An entry in the I-D Repository is removed as part of normal process
>>> when it expires after six months, when it is replaced by a subsequent
>>> I-D, or when it is replaced by the publication of an RFC.  In all
>>> of these situations, the I-D remains in the Public I-D Archive.
>> The text up to this point mostly looks like a general set of policy assertions about I-Ds.  Those need to exist separately as a formal policy statement about the series and its archive(s).
>>
>> That would leave the current statement to focus on its specific topic.
> These were included to provide context for the policy statement.  As we have seen on this thread, there has been at least as much discussion about these background paragraphs as the policy.
>
>>> An I-D will only be removed from the Public I-D Archive with consensus
>>> of the IESG.  There are two situations when the IESG will take this
>>> action.  First, to comply with a duly authorized court order.  Second,
>>> to resolve some form of abuse.
>> This second basis looks sufficiently broad and vague to invite its own abuse and certainly inconsistent application.  Did IETF counsel express comfort with this language?
> Counsel has been consulted.  After exchanging several messages, this is the resulting text.  This text was never a part that was edited in the exchange.
>
>>> If possible, a removed I-D will be
>>> replaced with a tombstone file that describes the reason that the I-D
>>> was removed from the Public I-D Archive.
>>>
>>> When an I-D is removed from the Public I-D Archive, a copy will be kept
>>> in a location accessible only by the IETF Leadership and the IETF
>>> Secretariat.  This private location may be searched by the IETF
>>> Leadership or the IETF Secretariat when responding to appeals,
>>> responding to subpoenas, or otherwise handling to legal matters.
>> Interesting.  An archive archive.
>>
>> IETF "leadership" isn't a formal term.  Who does it include/exclude?  WG Chairs?  Why?  Why not?
> I think it is fairly clear that the "leadership" is a party that would need access to this material when "responding to appeals, responding to subpoenas, or otherwise handling to legal matters."  I proposed this term because the parties that need access may well depend on the nature of the legal matter.
>   
>> Over time, given the number of people who hold various IETF leadership positions, this effectively gives access to a very large fraction of the IETF community.
> I envision a mechanism where the access is only granted to the specific files needed to address the appeal, subpoena, or other legal matter.
>
> Russ
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2441/5288 - Release Date: 09/23/12
>
>
>


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


From housley@vigilsec.com  Mon Sep 24 12:55:21 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 109E121F88BF; Mon, 24 Sep 2012 12:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BRSNbgduN6Yw; Mon, 24 Sep 2012 12:55:20 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 91E2921F88BA; Mon, 24 Sep 2012 12:55:20 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id A22989A4005; Mon, 24 Sep 2012 15:55:31 -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 NmcERL7DrooT; Mon, 24 Sep 2012 15:55:08 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id E95889A4003; Mon, 24 Sep 2012 15:55:30 -0400 (EDT)
Subject: Re: Neutering the impending patent wars... this is something the IETF can actually have a role in...
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5060B4EF.8010605@earthlink.net>
Date: Mon, 24 Sep 2012 15:55:15 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <38ACC329-B7B1-4C23-A9FD-E05FED7B91B5@vigilsec.com>
References: <5060B4EF.8010605@earthlink.net>
To: tglassey <tglassey@earthlink.net>
X-Mailer: Apple Mail (2.1084)
Cc: ietf <ietf@ietf.org>, IPR@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Sep 2012 19:55:21 -0000

Todd:

The intended recipients are two public mail lists.  Given that situation =
the legend at the bottom of you message seems inappropriate to me.

Russ


On Sep 24, 2012, at 3:30 PM, tglassey wrote:

> [snip]
> Todd Glassey
>=20
> --=20
> //Confidential Mailing - Please destroy this if you are not the =
intended recipient.
>=20


From housley@vigilsec.com  Mon Sep 24 13:02:05 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C3BF21F88C9 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 13:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RxDSmYDg-Uwk for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 13:02:04 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 1081821F88C6 for <ietf@ietf.org>; Mon, 24 Sep 2012 13:02:04 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id CFE009A4005; Mon, 24 Sep 2012 16:02:20 -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 GJEFBeh8vZb6; Mon, 24 Sep 2012 16:01:53 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4A4869A4003; Mon, 24 Sep 2012 16:02:18 -0400 (EDT)
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5060B637.6070704@earthlink.net>
Date: Mon, 24 Sep 2012 16:01:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <22F55374-5A35-4952-A24E-32BF9B47DC3D@vigilsec.com>
References: <80FC9E19-6251-4E8E-8B26-853D0C36B38D@ietf.org> <505D0AE8.8060208@dcrocker.net> <DB0202DA-1D59-4E63-BBD9-E40F917D91C1@vigilsec.com> <5060B637.6070704@earthlink.net>
To: tglassey <tglassey@earthlink.net>
X-Mailer: Apple Mail (2.1084)
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, 24 Sep 2012 20:02:05 -0000

Todd:

The Independent Submission Stream cannot be used to produce standards =
track RFCs.

Russ


On Sep 24, 2012, at 3:36 PM, tglassey wrote:

> On 9/24/2012 7:02 AM, Russ Housley wrote:
>> Dave:
> Russ - can the Independent Submission Stream (ISS) be used to create a =
fully franchised IETF Standard Process???
>=20
> i.e. could I for instance through the ISS process submit a I-D and a =
RFC-Framework Proposal with that? In this case the framework proposal =
would define the 'canonization process' for this specific piece of IP =
and set the milestones for this independent stream standard???
>=20
> This would be a very very good thing I think if it were to become =
possible.
>=20
>>>> The IESG has updated the draft IESG Statement based on the many =
comments that have been received.  It is clear that the community wants =
the IESG to be able to remove an Internet-Draft from the Public I-D =
Archive without a court order to do so.
> Which will apply to its publication and continued use rights how?
>=20
> I still think we need to answer the specific question as to what this =
actually means to the previous licensing...
>>>> That said, the IESG firmly believes that the collection of I-Ds =
provide important historical records for the open and transparent =
operation of the IETF.  Therefore, removal of a I-D from the  Public I-D =
Archive should teated as a significant event.
>>>>=20
>>>> Comments from the community are solicited on the revised draft IESG =
statement.
>>>>=20
>>>> On behalf of the IESG,
>>>> Russ
>>>>=20
>>>> --- DRAFT IESG STATEMENT ---
>>>>=20
>>>> SUBJECT: Removal of an Internet-Draft from the IETF Web Site
>>>>=20
>>>> Internet-Drafts (I-Ds) are working documents of the IETF.  I-Ds =
provide
>>>> important historical records for the open and transparent operation =
of
>>>> the IETF.  Other individuals and groups, including the IAB and IRTF
>>>> Research Groups, have chosen to distribute working documents as =
I-Ds.
>>> The IAB and IRTF are not part of the IETF?  The Independent stream =
also uses I-Ds.  Isn't it part of the IETF?
>> No.  The Independent Stream is not part of the IETF.  Like the IAB =
and the IRTF, the independent Stream has chosen to use I-Ds.
>>=20
>> RFC 4844 says:
>>=20
>> 5.1.4.  Independent Submission Stream
>>=20
>>    The RFC Series has always served a broader Internet technical
>>    community than the IETF.  The "Independent Submission" stream is
>>    defined to provide review and (possible) approval of documents =
that
>>    are outside the scope of the streams identified above.
>>=20
>>    Generally speaking, approval of documents in this stream falls =
under
>>    the purview of the RFC Editor, and the RFC Editor seeks input to =
its
>>    review from the IESG.
>>=20
>>    The process for reviewing and approving documents in the =
Independent
>>    Submission stream is defined by
>>=20
>>    o  Independent Submissions to the RFC Editor (RFC 4846 [RFC4846]).
>>=20
>>    o  The IESG and RFC Editor Documents: Procedures (RFC 3932
>>       [RFC3932]).
>>=20
>> (Since RFC 4844 was written, RFC3932 was obsoleted by RFC 5742.)
>>=20
>>>> I-Ds are stored in two places on the IETF web site.  First, current =
I-Ds
>>>> are stored in the I-D Repository.  Second, current and past I-Ds =
are
>>>> stored in a Public I-D Archive.
>>>>=20
>>>> While entries in the I-D Repository are subject to change or =
removal
>>>> at any time,
>>> They are?  Is this new?  I thought the only established removal =
policy was the regular 6-month timeout.
>> No, this is not new.  It goes back to RFC 1310 in March 1992.  If you =
publish draft-crocker-blah-blah-00.txt, is is very ofter replaced by =
-01.  The -00 is taken down before the six month expiration.
>>=20
>> RFC 1310 said:
>>=20
>>    An Internet Draft that is published as an RFC is removed from the
>>    Internet Draft directory.  A document that has remained unchanged
>>    in the Internet Drafts directory for more than six months without
>>    being recommended by the IESG for publication as an RFC is simply
>>    removed from the Internet Draft directory.  At any time, an
>>    Internet Draft may be replace by a more recent version of the same
>>    specification, restarting the six-month timeout period.
>>=20
>> This remains today; the I-D boilerplate says:
>>=20
>>    Internet-Drafts are draft documents valid for a maximum of six =
months
>>    and may be updated, replaced, or obsoleted by other documents at =
any
>>    time.  It is inappropriate to use Internet-Drafts as reference
>>    material or to cite them other than as "work in progress."
>>=20
>>>>               I-Ds generally remain in the Public I-D Archive to =
support
>>>> easy comparison with previous versions.  This availability =
facilitates
>>>> review, comment, and revision.
>>>>=20
>>>> An entry in the I-D Repository is removed as part of normal process
>>>> when it expires after six months, when it is replaced by a =
subsequent
>>>> I-D, or when it is replaced by the publication of an RFC.  In all
>>>> of these situations, the I-D remains in the Public I-D Archive.
>>> The text up to this point mostly looks like a general set of policy =
assertions about I-Ds.  Those need to exist separately as a formal =
policy statement about the series and its archive(s).
>>>=20
>>> That would leave the current statement to focus on its specific =
topic.
>> These were included to provide context for the policy statement.  As =
we have seen on this thread, there has been at least as much discussion =
about these background paragraphs as the policy.
>>=20
>>>> An I-D will only be removed from the Public I-D Archive with =
consensus
>>>> of the IESG.  There are two situations when the IESG will take this
>>>> action.  First, to comply with a duly authorized court order.  =
Second,
>>>> to resolve some form of abuse.
>>> This second basis looks sufficiently broad and vague to invite its =
own abuse and certainly inconsistent application.  Did IETF counsel =
express comfort with this language?
>> Counsel has been consulted.  After exchanging several messages, this =
is the resulting text.  This text was never a part that was edited in =
the exchange.
>>=20
>>>> If possible, a removed I-D will be
>>>> replaced with a tombstone file that describes the reason that the =
I-D
>>>> was removed from the Public I-D Archive.
>>>>=20
>>>> When an I-D is removed from the Public I-D Archive, a copy will be =
kept
>>>> in a location accessible only by the IETF Leadership and the IETF
>>>> Secretariat.  This private location may be searched by the IETF
>>>> Leadership or the IETF Secretariat when responding to appeals,
>>>> responding to subpoenas, or otherwise handling to legal matters.
>>> Interesting.  An archive archive.
>>>=20
>>> IETF "leadership" isn't a formal term.  Who does it include/exclude? =
 WG Chairs?  Why?  Why not?
>> I think it is fairly clear that the "leadership" is a party that =
would need access to this material when "responding to appeals, =
responding to subpoenas, or otherwise handling to legal matters."  I =
proposed this term because the parties that need access may well depend =
on the nature of the legal matter.
>> =20
>>> Over time, given the number of people who hold various IETF =
leadership positions, this effectively gives access to a very large =
fraction of the IETF community.
>> I envision a mechanism where the access is only granted to the =
specific files needed to address the appeal, subpoena, or other legal =
matter.
>>=20
>> Russ
>>=20
>>=20
>>=20
>> -----
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2012.0.2221 / Virus Database: 2441/5288 - Release Date: =
09/23/12
>>=20
>>=20
>>=20
>=20
>=20
> --=20
> //Confidential Mailing - Please destroy this if you are not the =
intended recipient.
>=20


From paul.hoffman@vpnc.org  Mon Sep 24 13:12:51 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC20321F88DC for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 13:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ocjc0wHW39qG for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 13:12:51 -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 0624921F88DB for <ietf@ietf.org>; Mon, 24 Sep 2012 13:12:50 -0700 (PDT)
Received: from [10.20.30.108] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q8OKCndx025704 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Mon, 24 Sep 2012 13:12:50 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: On real-world use of protocols
Message-Id: <82A3CE69-5E82-4457-97CD-D55F40C56CED@vpnc.org>
Date: Mon, 24 Sep 2012 13:12:49 -0700
To: IETF list <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
X-Mailer: Apple Mail (2.1498)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Sep 2012 20:12:51 -0000

<http://xkcd.com/1112/>

This is as much about interesting uses of the protocols that the IETF =
develops as it is about chess. (Be sure to hover over the cartoon for a =
pop-up that is also relevant to our protocol development process.)


From tglassey@earthlink.net  Mon Sep 24 13:30:34 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8D521F88E4; Mon, 24 Sep 2012 13:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.616
X-Spam-Level: 
X-Spam-Status: No, score=-3.616 tagged_above=-999 required=5 tests=[AWL=0.983,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-sQLD7zfLk8; Mon, 24 Sep 2012 13:30:32 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 02AA91F0C3A; Mon, 24 Sep 2012 13:30:31 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=I2s++8xDw9kBxJDXDTwkVO7UMLR3kjCRYHU4V5CcEyeSfPy+fxHdUAHSXoLpCAJn; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TGFIV-0005w6-4x; Mon, 24 Sep 2012 16:30:31 -0400
Message-ID: <5060C2E4.604@earthlink.net>
Date: Mon, 24 Sep 2012 13:30:28 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Neutering the impending patent wars... this is something the IETF can actually have a role in...
References: <5060B4EF.8010605@earthlink.net> <38ACC329-B7B1-4C23-A9FD-E05FED7B91B5@vigilsec.com>
In-Reply-To: <38ACC329-B7B1-4C23-A9FD-E05FED7B91B5@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec793d74dbc52fd213077d8831187ac9a8ad350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
Cc: ietf <ietf@ietf.org>, IPR@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Sep 2012 20:30:34 -0000

On 9/24/2012 12:55 PM, Russ Housley wrote:
> Todd:
>
> The intended recipients are two public mail lists.  Given that situation the legend at the bottom of you message seems inappropriate to me.
>
> Russ
>
>
> On Sep 24, 2012, at 3:30 PM, tglassey wrote:
Agreed. Sorry, how about the one at the bottom of this letter? this also 
is a good thing to include in all IETF postings. We should add this to 
the recommendations in the BCP's as well I think.

Todd

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

//Submitted to IETF mailing list(s) under full NOTE-WELL COMPLIANCE
See  http://www.ietf.org/about/note-well.html


From sm@resistor.net  Mon Sep 24 14:32:17 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9BFC1F041D for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 14:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9GRJ+0duiWNg for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 14:32:13 -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 194351F0C5C for <ietf@ietf.org>; Mon, 24 Sep 2012 14:32:13 -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 q8OLW1pw020606; Mon, 24 Sep 2012 14:32:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1348522327; bh=reCyOmEzD5XbjLyar7HgaPsIBqhRfbN39NcULbFQyJQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Mp5f9HmQt0GGtQfkSbVOU1N94t/wJNjyZRzfiwULP573XXmiWReuIv3nIXmQdU7da MhN8BM8qxTAm9+cNIqUlkL2b0ZJNREyyT8zVKvKAgeV4+FkW8Yx3dAXuznTUOCRMgh x/Uq8Hz5OPIkfvgogue7pY359jjDqQmbymnGEsJM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1348522327; i=@resistor.net; bh=reCyOmEzD5XbjLyar7HgaPsIBqhRfbN39NcULbFQyJQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ND4YoduN0DPRM144XI6fu3uqIbHRkCzJOkcXku1BAY/7r2AZQMa3gRYLavEpjp0iJ 8aHnX1ZZ0RMxCCbnNi13d5wlqnPwYVxs0Zjis+pKa5rMzpU1om9ZTGO0tr/u0duthj pVQhD+QmcbD5FZaZfzncrJRXSahipzLOLIlOiOHM=
Message-Id: <6.2.5.6.2.20120924142604.0a5c6af8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 24 Sep 2012 14:31:27 -0700
To: Peter Saint-Andre <stpeter@stpeter.im>, Julian Reschke <julian.reschke@gmx.de>
From: SM <sm@resistor.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <5060A964.5060001@stpeter.im>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: URI <uri@w3.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, 24 Sep 2012 21:32:17 -0000

At 11:41 24-09-2012, Peter Saint-Andre wrote:
>It's not completely clear to me what Anne meant there by saying "the
>plan is to obsolete the RFCs" (naturally that is not something that
>anyone outside the IETF can do, although they can ignore the RFCs).
>It's also not clear to me what the WHATWG HTML Living Standard [1]
>really means by "willful violation" [2] -- e.g., is it just an

The following message was posted over a year ago: 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg03064.html

Regards,
-sm 


From brian.e.carpenter@gmail.com  Mon Sep 24 14:51:43 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32AF51F0C5C for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 14:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.576
X-Spam-Level: 
X-Spam-Status: No, score=-103.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIZzQXqCDXg5 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 14:51:42 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 503441F041D for <ietf@ietf.org>; Mon, 24 Sep 2012 14:51:41 -0700 (PDT)
Received: by iec9 with SMTP id 9so13506013iec.31 for <ietf@ietf.org>; Mon, 24 Sep 2012 14:51:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=mqtqR8nHD0nCwlOQxjbV/73hJ3+d1TibdOHP5FXKfm0=; b=pErIN0uvTAfnNGV2A8Huj+hMojyycgeC09JwgPtu4Gg5eCpSg92POxZhW2ZJn5kPUR W+nUh+C3rK8zYIKD+YYW7p0Z8A72szw+kGWK2mPYWZiKdUkVjSuhW2xTIFiUqYuvCyP6 8Xb5Am0U8iskvvi2hnQQ2MOAo5qLjAQWYmelXpL26scap8xrh/34tAGlgLJ05u0O9IRO x2Vdt4ia2kOmSm0SDBcVwTb3pGr+t855/dc3oc4zKelNuNb52IzdVDCIFgeopKmzSjMd O6L3tf/LN2Tkj7wetzZHTSzCIRHkP2a6OEH8D4AT7/O0hXvzrSFgODQCVZalz1wQx9E2 ZDyw==
Received: by 10.50.219.129 with SMTP id po1mr6426516igc.35.1348523500881; Mon, 24 Sep 2012 14:51:40 -0700 (PDT)
Received: from [10.255.25.102] (50-76-68-140-static.hfc.comcastbusiness.net. [50.76.68.140]) by mx.google.com with ESMTPS id uq6sm6643954igb.14.2012.09.24.14.51.39 (version=SSLv3 cipher=OTHER); Mon, 24 Sep 2012 14:51:40 -0700 (PDT)
Message-ID: <5060D5ED.8030509@gmail.com>
Date: Mon, 24 Sep 2012 22:51:41 +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: SM <sm@resistor.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on	2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <6.2.5.6.2.20120924142604.0a5c6af8@resistor.net>
In-Reply-To: <6.2.5.6.2.20120924142604.0a5c6af8@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Julian Reschke <julian.reschke@gmx.de>, URI <uri@w3.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, 24 Sep 2012 21:51:43 -0000

Mark Nottingham still being the IETF's liaison manager for the W3C liaison,
I assume we will be hearing from him what all this means and how it's
being coordinated.

Some of the "violations" are "motivated by a desire to handle legacy
content". That seems to be in the IETF spirit of "Be strict when sending and
tolerant when receiving" for the sake of backwards compatibility. Any of them
that damage interoperability and compatibility would be more worrisome.

Regards
   Brian

On 24/09/2012 22:31, SM wrote:
> At 11:41 24-09-2012, Peter Saint-Andre wrote:
>> It's not completely clear to me what Anne meant there by saying "the
>> plan is to obsolete the RFCs" (naturally that is not something that
>> anyone outside the IETF can do, although they can ignore the RFCs).
>> It's also not clear to me what the WHATWG HTML Living Standard [1]
>> really means by "willful violation" [2] -- e.g., is it just an
> 
> The following message was posted over a year ago:
> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg03064.html
> 
> Regards,
> -sm
> 

From john-ietf@jck.com  Mon Sep 24 19:55:05 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0321B21F8905 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 19:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level: 
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2njj8X3dl5Qy for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2012 19:55:04 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 835CC21F8904 for <ietf@ietf.org>; Mon, 24 Sep 2012 19:55:04 -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 1TGLIT-0004ZJ-Tu; Mon, 24 Sep 2012 22:54:53 -0400
Date: Mon, 24 Sep 2012 22:54:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, SM <sm@resistor.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on	2012-09-24	(public-whatwg-archive@w3.org from September 2012)
Message-ID: <278D3D58DBCAACAA9A237450@JcK-HP8200.jck.com>
In-Reply-To: <5060D5ED.8030509@gmail.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <6.2.5.6.2.20120924142604.0a5c6af8@resistor.net> <5060D5ED.8030509@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: Julian Reschke <julian.reschke@gmx.de>, URI <uri@w3.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: Tue, 25 Sep 2012 02:55:05 -0000

--On Monday, September 24, 2012 22:51 +0100 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
> Some of the "violations" are "motivated by a desire to handle
> legacy content". That seems to be in the IETF spirit of "Be
> strict when sending and tolerant when receiving" for the sake
> of backwards compatibility. Any of them that damage
> interoperability and compatibility would be more worrisome.

And some of it isn't.  As just one example, opinions may differ
about whether it is reasonable to impose restrictions on valid
email addresses because some legacy implementations did a sloppy
job, but one certainly cannot justify it on the basis of the
Robustness Principle.

    john





From abdussalambaryun@gmail.com  Tue Sep 25 08:50:54 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1DF821F880C for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 08:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.511
X-Spam-Level: 
X-Spam-Status: No, score=-3.511 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xwp0ZkEY2jAy for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 08:50:53 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 81A0C21F87E4 for <ietf@ietf.org>; Tue, 25 Sep 2012 08:50:53 -0700 (PDT)
Received: by iec9 with SMTP id 9so15808813iec.31 for <ietf@ietf.org>; Tue, 25 Sep 2012 08:50:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=4BLyYExd/nhAyEfwX13bQGmW4aZgYbSpc+k1QyhnABc=; b=SgruBfQa8NRvJo2NcqSw8zmNLFSRNNYunsDLeyz2d4fBAIBx6Y9Ifnfti+VjQckd6u TIZEHZGHzEiSmYI0ROHoGw5B0y5wE5CcsXQJo6AD9H38nvAbgL6pZ3I5PKRjuPWO5Ko0 M5pZqLR7MjNikS8sE47i5ybtwYTJVLcHu92VsNotL1BgyvSDfTkH6sW48Erhe4F05rDd IOCWppHLsfqRWNkCSdf4QIyzBN11LnYUzKTRngarzC47ZlW9RAlxyaqdi3Z6WT/Spk9G q6t/dQJMu3djFe5Oufs5dic74ysQEi7U1baW1HB8a8xr/NWg4RyxU4uo5IRTtq4C/OSs ovNA==
MIME-Version: 1.0
Received: by 10.50.104.202 with SMTP id gg10mr8549545igb.48.1348588252878; Tue, 25 Sep 2012 08:50:52 -0700 (PDT)
Received: by 10.64.25.46 with HTTP; Tue, 25 Sep 2012 08:50:52 -0700 (PDT)
Date: Tue, 25 Sep 2012 16:50:52 +0100
Message-ID: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: housley@vigilsec.com
Content-Type: multipart/alternative; boundary=e89a8f2354b1c2d92f04ca88abf5
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, 25 Sep 2012 15:50:55 -0000

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

Hi Russ,

I think that statement you made is very reasonable which I would prefer
groups work to the best of IETF purposes, but also we need to know the
reason why some individuals fail to convince an IETF WG. It is important
that individuals get to make input to new standards not only companies. I
am afraid that only companies are controlling the Internet standards which
seems bad and does not follow the IETF mission. Therefore, there SHOULD be
a procedure to make participants follow to convince WG and a procedure that
WGs follow to accept with reason, not just blocking excellent I-D because
they group think it is bad with no reason or knowledgable discussion. If
there is no procedure then individuals or other organisations will look for
another way to standards their work.

AB
---

 but is this Why not? I thought any I-D can be standard track,


>Todd:

>The Independent Submission Stream cannot be used to produce standards
track RFCs.

>Russ

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

<div>Hi Russ,</div><div>=A0</div><div>I think that statement you made is ve=
ry reasonable which I would prefer groups work to the best of IETF purposes=
, but also we need to know the reason why=A0some individuals fail to convin=
ce an IETF WG. It is important that individuals get to make input to new=A0=
standards not only companies. I am afraid that only companies are controlli=
ng the Internet standards which seems bad and does not follow the IETF miss=
ion. Therefore, there SHOULD be a procedure to make participants follow to =
convince WG and a procedure that WGs follow to accept with reason, not just=
=A0blocking=A0excellent I-D because they group think it is bad with no reas=
on or knowledgable discussion. If there is no procedure then individuals or=
 other organisations=A0will look for another way to standards their work.</=
div>
<div>=A0</div><div>AB</div><div>---</div><div>=A0</div><div>=A0but is this =
Why not? I thought any I-D can be standard track,</div><div>=A0</div><div>=
=A0</div><div>&gt;Todd:<br><br>&gt;The Independent Submission Stream cannot=
 be used to produce standards track RFCs.<br>
<br>&gt;Russ<br><br></div>

--e89a8f2354b1c2d92f04ca88abf5--

From abdussalambaryun@gmail.com  Tue Sep 25 09:03:04 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C0C1F0C97 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 09:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.515
X-Spam-Level: 
X-Spam-Status: No, score=-3.515 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5tPNu7Shg35p for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 09:03:04 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id D89BC1F0C86 for <ietf@ietf.org>; Tue, 25 Sep 2012 09:03:03 -0700 (PDT)
Received: by iec9 with SMTP id 9so15848418iec.31 for <ietf@ietf.org>; Tue, 25 Sep 2012 09:03:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=kt+TpztzjgOi0Yv+MZoUgNWnoYjV+aDHaYjbk9tnaaU=; b=kbEQBGDoCGD52ZW5qeYkwxekqiEr9iyxdFNSBkdCfTQqCXSmMLb5sq7YnxZVMwaU// 3vmCQAaNb7qzkChHBoVQr5xdSYuTajKQ+L6bUA7oCVYHBQqgXg3hXRUUzjlUduBD5679 JDR2FI9iQKQWW9IuDf3boz43Hue8LhxcrhxQxoecQkFLmlAhDun7hZUvIbIH0byrGTNo xAHdwVfhtR7fNlV5H/evJ0YG66PS1nT/GGfawLKWSY5GOFXeSmEuaPCHw82Cnt14f/3P Dl/wx5Hq69xSw++lja9xNkYi415OoIN9rtTTMdvlAs6H9gbOCUDtiqvirLp31oZMFpRD UjDQ==
MIME-Version: 1.0
Received: by 10.50.33.138 with SMTP id r10mr8729332igi.31.1348588983464; Tue, 25 Sep 2012 09:03:03 -0700 (PDT)
Received: by 10.64.25.46 with HTTP; Tue, 25 Sep 2012 09:03:03 -0700 (PDT)
Date: Tue, 25 Sep 2012 17:03:03 +0100
Message-ID: <CADnDZ88fjz0vXkNkGOMpa+0BHbESt_aEz4Smz1-h9CjrOsrUDw@mail.gmail.com>
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: dhc@dcrocker.net
Content-Type: multipart/alternative; boundary=f46d0447f05e4eb38704ca88d784
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, 25 Sep 2012 16:03:04 -0000

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

Hi Dave,

>Independent Stream authors well might not be "part of" the IETF -- always
a strange line of thinking, given that the IETF doesn't have members -- but
that doesn't mean that the Stream itself is outside the IETF.
Any I-D author MUST be part of IETF otherwise what is IETF then, how do we
define it? I think we should not make simple facts complicated. The most
important part of IETF is the participant that does volunteer his work
effort and time for the IETF. However I assume you agree with me because
you mentioned "might".

AB

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

<p><tt><font size=3D"3" face=3D"Times New Roman">

Hi Dave,</font></tt></p><tt><div style=3D"margin:0cm 0cm 10pt" class=3D"Mso=
Normal"><span style=3D"line-height:115%;font-family:&quot;Courier New&quot;=
;font-size:10pt"></span>=A0</div><div style=3D"margin:0cm 0cm 10pt" class=
=3D"MsoNormal">
<span style=3D"line-height:115%;font-family:&quot;Courier New&quot;;font-si=
ze:10pt">&gt;Independent Stream authors well might not be
&quot;part of&quot; the IETF -- always a strange line of </span><span style=
=3D"line-height:115%;font-family:&quot;Courier New&quot;;font-size:10pt">th=
inking, given that
the IETF doesn&#39;t have members -- but that doesn&#39;t mean that the Str=
eam itself
is outside the IETF.</span></div><div><font size=3D"3" face=3D"Times New Ro=
man">

Any I-D=A0author MUST be part of IETF otherwise what is IETF then, how do w=
e define it? I think we should not make simple facts=A0complicated. The mos=
t important part of IETF is the participant that does volunteer his work ef=
fort and time for the IETF. However I assume you agree with me because you =
mentioned &quot;might&quot;.</font></div>
<div><font size=3D"3" face=3D"Times New Roman"></font>=A0</div><div><font s=
ize=3D"3" face=3D"Times New Roman">AB</font></div></tt><div></div>

--f46d0447f05e4eb38704ca88d784--

From john-ietf@jck.com  Tue Sep 25 09:11:39 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4292721F8805 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 09:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a5Xp7eL+VXRw for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 09:11:38 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A6ED221F87F4 for <ietf@ietf.org>; Tue, 25 Sep 2012 09:11:38 -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 1TGXjT-0006La-Ig; Tue, 25 Sep 2012 12:11:35 -0400
Date: Tue, 25 Sep 2012 12:11:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, housley@vigilsec.com
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the	IETF Web Site
Message-ID: <88DDCACED7D92B4031CD65DC@JcK-HP8200.jck.com>
In-Reply-To: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com>
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Sep 2012 16:11:39 -0000

--On Tuesday, September 25, 2012 16:50 +0100 Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:

> I think that statement you made is very reasonable which I
> would prefer groups work to the best of IETF purposes, but
> also we need to know the reason why some individuals fail to
> convince an IETF WG. It is important that individuals get to
> make input to new standards not only companies.
>... 
> Therefore, there SHOULD be a procedure to make participants
> follow to convince WG and a procedure that WGs follow to
> accept with reason, not just blocking excellent I-D because
> they group think it is bad with no reason or knowledgable
> discussion. If there is no procedure then individuals or other
> organisations will look for another way to standards their
> work.

It seems to me that the above has nothing to do with the topic
of removing I-Ds from the archive.  As far as I know, the number
of I-Ds that have been taken down --or even expired early
without recourse-- in the history of the IETF because someone
didn't like the ideas has been zero.   More important, someone
who believes that a WG unreasonably rejected a useful idea or
who wishes to see the reasons for WG decisions documented has
several ways to accomplish that.   An Informational discussion
could be submitted as an individual submission to the IESG or as
an independent submission to the ISE.  My experience and
observation is that such analyses or critiques are almost always
published as RFCs --the really permanent, archival, form around
here-- if they are thoughtful and well-reasoned.  I've seen
rants rejected for RFC publication, but that is because they are
unsupported rants, not because they disagree with some community
conclusion.

   john

p.s. As someone who has spent far more of my IETF existence as
an individual rather than as someone supported by, much less
controlled by, a company, I see company domination as a risk but
not one that has been an actual problem in any but a very small
number of specific topics/areas.





From sm@resistor.net  Tue Sep 25 10:12:14 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20E6A1F0CA2 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 10:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qbFmxpQoqOfN for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 10:12:13 -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 622401F0C82 for <ietf@ietf.org>; Tue, 25 Sep 2012 10:12:13 -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 q8PHC4od016699; Tue, 25 Sep 2012 10:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1348593129; bh=sQ6OybA+7Z8zEwvMHH1/FmIJ61GViGUsJ9V9zhBGKXQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LU0QTM8sp1BbFWiy2edtxc/BeJ0xMasZO/o8YycRKzeMsbzTokzwiZ6NvpRo4117J 5aR2rf3FC20QqUl23gzXOpg3rzAvd2S3gPvPzM0/Qd93zOknonsi+C4sw7sMtnSSGX Sqz7b6aHuQg+ku2QNufR04K6Sn5EQ9hS63DvBdds=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1348593129; i=@resistor.net; bh=sQ6OybA+7Z8zEwvMHH1/FmIJ61GViGUsJ9V9zhBGKXQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Oj7EwCz8VCyOChJPlr8E6+iLdSm3QmgMpyO66vuqkEAeR9TdhT0SDLN1nrgWAQQLL eUv8M8r5WuNz8MIvROKOMqT7EcPiecxNu5p7Z6K53nnGaHf23JFCyEgAvxLCx2W8Un O0silQlRojKfLkzgmyMXaoO7AyZvET16adBi/mbY=
Message-Id: <6.2.5.6.2.20120925090332.09e8dd40@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 25 Sep 2012 10:08:43 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Failing to convince an IETF WG (was: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site)
In-Reply-To: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.g mail.com>
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 25 Sep 2012 17:12:14 -0000

Hi Abdussalam,
At 08:50 25-09-2012, Abdussalam Baryun wrote:
>I think that statement you made is very reasonable which I would 
>prefer groups work to the best of IETF purposes, but also we need to 
>know the reason why some individuals fail to convince an IETF WG. It 
>is important that individuals get to make input to

Failing to convince a WG can happen for any of the following reasons:

   (i)   The arguments are unconvincing.

   (ii)  The arguments are unrelated to the topic being discussed.

   (iii) The arguments look good on paper.  Unfortunately, they won't
         work in the real world.

   (iv)  The other individuals do not like the individual. :-)

The above reasons may not even be valid.

>Internet standards which seems bad and does not follow the IETF 
>mission. Therefore, there
>  SHOULD be a procedure to make participants follow to convince WG 
> and a procedure that
>  WGs follow to accept with reason, not just blocking excellent I-D 
> because they group think it is bad with no reason or knowledgable 
> discussion. If there is no procedure then

If the group thinks that an I-D is bad, you can either accept that 
conclusion or you can try to convince the group that it is wrong.  If 
you cannot convince the WG, there is always the Last Call where you 
get a second opportunity to raise your issues.  There are procedures 
if a third opportunity is necessary.

Around a month ago, Adrian Farrel asked the following question [1]:

   "May I have your permission to share this email with the
    document authors."

The answer [2] was:

   "Therefore, I don't want to give any permission to share with them, I will
    leave it to IESG. If IESG agrees to share any/all comments they received
    to any/all author(s), I will have no objection."

That's basically a no.  The above puts the IESG in an unenviable 
position to decide whether to share the email.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg74749.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg74749.html 


From abdussalambaryun@gmail.com  Tue Sep 25 10:19:15 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9130321F87E0 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 10:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.519
X-Spam-Level: 
X-Spam-Status: No, score=-3.519 tagged_above=-999 required=5 tests=[AWL=0.079,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V1s5aWFMd88L for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 10:19:14 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id B8D4A21F85A8 for <ietf@ietf.org>; Tue, 25 Sep 2012 10:19:14 -0700 (PDT)
Received: by iec9 with SMTP id 9so16084050iec.31 for <ietf@ietf.org>; Tue, 25 Sep 2012 10:19:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=scumbq7MHFKmGkHId/0kGdxqdihzFWN1xm/1p3eJwcg=; b=tpk/bzxoagQ/1nSOSEy0LuKQGMH0dX6CxUs0ujjE0iwmUfjEknNE2iQs8a21Th5RrQ ItdpNGWsqXD308Y4bbbbmkFPbaNN8J/LKAnfV50z58LTtTRCFp5nEunudPEc99rklexe NS8cBK6Sv/jOKhgibjbr0a5Sf2hmvtGwp4/RjIju77PBg/E66qL4k56idD+nQYAWs5Zw 7dMrN9MtctvZMRqUcAgzL0JlxKFHzojMpLoUZacREhExWJnzTv72wT0ypfhRSKyPmvfg 0ZKatEHXcMImWBxkgzwsIOCPvaOA4teebaM6t3ISOSzEkDx+BfUOzPPJjJLiWmoA+plh H6zA==
MIME-Version: 1.0
Received: by 10.50.183.135 with SMTP id em7mr8953212igc.31.1348593554250; Tue, 25 Sep 2012 10:19:14 -0700 (PDT)
Received: by 10.64.25.46 with HTTP; Tue, 25 Sep 2012 10:19:14 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120925090332.09e8dd40@resistor.net>
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net>
Date: Tue, 25 Sep 2012 18:19:14 +0100
Message-ID: <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com>
Subject: Re: Failing to convince an IETF WG (was: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=14dae9340749bf5bbe04ca89e77e
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, 25 Sep 2012 17:19:15 -0000

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

Hi SM,

I ment to say that if independent stream cannot submit a standard track
document, then do we have a procedure for the WG to accept or not consider?
The last call that you refered to was a WG not independent.

AB

On Tue, Sep 25, 2012 at 6:08 PM, SM <sm@resistor.net> wrote:

> Hi Abdussalam,
> At 08:50 25-09-2012, Abdussalam Baryun wrote:
>
>> I think that statement you made is very reasonable which I would prefer
>> groups work to the best of IETF purposes, but also we need to know the
>> reason why some individuals fail to convince an IETF WG. It is important
>> that individuals get to make input to
>>
>
> Failing to convince a WG can happen for any of the following reasons:
>
>   (i)   The arguments are unconvincing.
>
>   (ii)  The arguments are unrelated to the topic being discussed.
>
>   (iii) The arguments look good on paper.  Unfortunately, they won't
>         work in the real world.
>
>   (iv)  The other individuals do not like the individual. :-)
>
> The above reasons may not even be valid.
>
>  Internet standards which seems bad and does not follow the IETF mission.
>> Therefore, there
>>  SHOULD be a procedure to make participants follow to convince WG and a
>> procedure that
>>  WGs follow to accept with reason, not just blocking excellent I-D
>> because they group think it is bad with no reason or knowledgable
>> discussion. If there is no procedure then
>>
>
> If the group thinks that an I-D is bad, you can either accept that
> conclusion or you can try to convince the group that it is wrong.  If you
> cannot convince the WG, there is always the Last Call where you get a
> second opportunity to raise your issues.  There are procedures if a third
> opportunity is necessary.
>
> Around a month ago, Adrian Farrel asked the following question [1]:
>
>   "May I have your permission to share this email with the
>    document authors."
>
> The answer [2] was:
>
>   "Therefore, I don't want to give any permission to share with them, I
> will
>    leave it to IESG. If IESG agrees to share any/all comments they received
>    to any/all author(s), I will have no objection."
>
> That's basically a no.  The above puts the IESG in an unenviable position
> to decide whether to share the email.
>
> Regards,
> -sm
>
> 1. http://www.ietf.org/mail-**archive/web/ietf/current/**msg74749.html<http://www.ietf.org/mail-archive/web/ietf/current/msg74749.html>
> 2. http://www.ietf.org/mail-**archive/web/ietf/current/**msg74749.html<http://www.ietf.org/mail-archive/web/ietf/current/msg74749.html>
>

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

<div>Hi SM,</div><div>=A0</div><div>I ment to say that if independent strea=
m cannot submit a standard track document, then do we have a procedure for =
the WG to accept or not consider? The last call that you refered to was a W=
G not independent.</div>
<div>=A0</div><div>AB<br><br></div><div class=3D"gmail_quote">On Tue, Sep 2=
5, 2012 at 6:08 PM, SM <span dir=3D"ltr">&lt;<a href=3D"mailto:sm@resistor.=
net" target=3D"_blank">sm@resistor.net</a>&gt;</span> wrote:<br><blockquote=
 style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(2=
04,204,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_q=
uote">
Hi Abdussalam,<br>
At 08:<a href=3D"tel:50%2025-09-2012" target=3D"_blank" value=3D"+150250920=
12">50 25-09-2012</a>, Abdussalam Baryun 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">
I think that statement you made is very reasonable which I would prefer gro=
ups work to the best of IETF purposes, but also we need to know the reason =
why some individuals fail to convince an IETF WG. It is important that indi=
viduals get to make input to<br>

</blockquote>
<br>
Failing to convince a WG can happen for any of the following reasons:<br>
<br>
=A0 (i) =A0 The arguments are unconvincing.<br>
<br>
=A0 (ii) =A0The arguments are unrelated to the topic being discussed.<br>
<br>
=A0 (iii) The arguments look good on paper. =A0Unfortunately, they won&#39;=
t<br>
=A0 =A0 =A0 =A0 work in the real world.<br>
<br>
=A0 (iv) =A0The other individuals do not like the individual. :-)<br>
<br>
The above reasons may not even be valid.<br>
<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">
Internet standards which seems bad and does not follow the IETF mission. Th=
erefore, there<br>
=A0SHOULD be a procedure to make participants follow to convince WG and a p=
rocedure that<br>
=A0WGs follow to accept with reason, not just blocking excellent I-D becaus=
e they group think it is bad with no reason or knowledgable discussion. If =
there is no procedure then<br>
</blockquote>
<br>
If the group thinks that an I-D is bad, you can either accept that conclusi=
on or you can try to convince the group that it is wrong. =A0If you cannot =
convince the WG, there is always the Last Call where you get a second oppor=
tunity to raise your issues. =A0There are procedures if a third opportunity=
 is necessary.<br>

<br>
Around a month ago, Adrian Farrel asked the following question [1]:<br>
<br>
=A0 &quot;May I have your permission to share this email with the<br>
=A0 =A0document authors.&quot;<br>
<br>
The answer [2] was:<br>
<br>
=A0 &quot;Therefore, I don&#39;t want to give any permission to share with =
them, I will<br>
=A0 =A0leave it to IESG. If IESG agrees to share any/all comments they rece=
ived<br>
=A0 =A0to any/all author(s), I will have no objection.&quot;<br>
<br>
That&#39;s basically a no. =A0The above puts the IESG in an unenviable posi=
tion to decide whether to share the email.<br>
<br>
Regards,<br>
-sm<br>
<br>
1. <a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg74749.ht=
ml" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/ietf/curr=
ent/<u></u>msg74749.html</a><br>
2. <a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg74749.ht=
ml" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/ietf/curr=
ent/<u></u>msg74749.html</a> <br>
</blockquote></div><br>

--14dae9340749bf5bbe04ca89e77e--

From sm@resistor.net  Tue Sep 25 11:20:10 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBACF21F87A9 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 11:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s8jwdeHOs0lc for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 11:20:10 -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 1A97921F878A for <ietf@ietf.org>; Tue, 25 Sep 2012 11:20: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 q8PIJvCs014381; Tue, 25 Sep 2012 11:20:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1348597202; bh=pDkGQ+vF/QM5V/8zbWeR9dTlD68uVjKmG2u71Fkt4jw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gC94WEWqV8Di2AN3f2n/ZarbCnzpUUaIKbI0w3EZF0zAtb0cy1HJYV2c2ih5opZUb M+X4JH/xu3UI6ARlDALDCHf/Z60QwMD+GPnVJc6qnwv/nXzVENKj5aYwQyAk8exYhO Ai36/WUtLPK7Wdh7lQUFDqR33nnDaLR949ILlAJs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1348597202; i=@resistor.net; bh=pDkGQ+vF/QM5V/8zbWeR9dTlD68uVjKmG2u71Fkt4jw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mZ/Rc79QhrD5+G3qD22rrsVnmQPghCjXjvd0ezHsEIFJQ+IEDIoPn/cfRo81JtBdt p1pdbc0pwGkE557qx38ps6fddgdnAL8ZtD/3E4Mk/68ne07gsVl9dHELdGJzR3FiUr Esy1piIVu3SpCSrx8ZBLhjIrWcp2p1fT1+dUq5Ik=
Message-Id: <6.2.5.6.2.20120925103806.0989ff10@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 25 Sep 2012 11:15:40 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Failing to convince an IETF WG (was: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site)
In-Reply-To: <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.g mail.com>
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 25 Sep 2012 18:20:11 -0000

Hi Abdussalam,
At 10:19 25-09-2012, Abdussalam Baryun wrote:
>I ment to say that if independent stream cannot submit a standard 
>track document, then do we have a procedure for the WG to accept or 
>not consider? The last call that you refered to was a WG not independent.

There is no such thing as an Independent Stream submitting a 
Standards Track document.  An author can submit an I-D through the 
IETF Stream if the author would like the I-D to be published on the 
Standards Track.  A WG can adopt such an I-D.

Regards,
-sm

P.S. I read your message [1] again.  The first part seems to be about 
"the reason why some individuals fail to convince an IETF WG".  The 
last part seem to be about "a procedure to make participants follow 
to convince WG and a procedure that WGs follow to accept with 
reason".  There was then an "AB" and three hyphens on the next 
line.  It is followed by "but is this Why not? I thought any I-D can 
be standard track,".  It was difficult for me to understand [2] the message.

1. http://www.ietf.org/mail-archive/web/ietf/current/msg75097.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg60902.html  


From ben@nostrum.com  Tue Sep 25 11:28:03 2012
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE9B021F87FF; Tue, 25 Sep 2012 11:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXwI5iJsS5qj; Tue, 25 Sep 2012 11:28:03 -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 337FB21F87E5; Tue, 25 Sep 2012 11:28:03 -0700 (PDT)
Received: from [10.0.1.3] (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 q8PIS2fU093110 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 Sep 2012 13:28:02 -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-websec-strict-transport-sec-13
Date: Tue, 25 Sep 2012 13:28:05 -0500
Message-Id: <B5EE55DF-F2F6-467E-B1DD-D9192F0E91D3@nostrum.com>
To: "draft-ietf-websec-strict-transport-sec.all@tools.ietf.org" <draft-ietf-websec-strict-transport-sec.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
X-Mailer: Apple Mail (2.1498)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2012 18:28: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 wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-websec-strict-transport-sec-13
Reviewer: Ben Campbell
Review Date: 2012-09-25
IESG Telechat date: 2012-09-27

Note: This review is incremental to my Gen-ART review of version 11 at =
IETF LC.


Summary: This version is ready for publication as a proposed standard.  =
All of my concerns from the previous review have been addressed in the =
draft or through conversation.

Major issues: None

Minor issues: None

Nits/editorial comments: None.

From adrian@olddog.co.uk  Tue Sep 25 12:13:12 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DADB721F847D for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 12:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.37
X-Spam-Level: 
X-Spam-Status: No, score=-2.37 tagged_above=-999 required=5 tests=[AWL=0.229,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WveYxpsWa6Wn for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 12:13:12 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id B8DFC21F8469 for <ietf@ietf.org>; Tue, 25 Sep 2012 12:13:11 -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 q8PJDAQD003315 for <ietf@ietf.org>; Tue, 25 Sep 2012 20:13:10 +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 q8PJD9pQ003301 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 25 Sep 2012 20:13:10 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: FW: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document Shepherding Throughout a Document's Lifecycle) to Informational RFC
Date: Tue, 25 Sep 2012 20:13:07 +0100
Message-ID: <041e01cd9b51$cc632bc0$65298340$@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: Ac2bUcovVzszfmV4RQqX+WTjs1MmVQ==
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: Tue, 25 Sep 2012 19:13:13 -0000

Hi,
I don't understand the process for this document.

I read Russ's  words, but I don't glean the meaning :-(

This document is in IETF last call for publication in the IETF stream.
Yet any comments received will not necessarily be taken on board and the
document will not be published as having IETF consensus.
Why does that feel like Independent Stream to me?
And why is an RFC needed simply to record the thoughts of one person?

Is the purpose of the Last Call simply to help the IESG make its decision?

Thanks,
Adrian (Who has yet to read the document, but feels that he cannot make any
useful comments since the content is the opinion of one person and he has no
idea whether the document correctly reflects the opinion of that person.)

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 25 September 2012 15:41
> To: IETF-Announce
> Subject: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document
> Shepherding Throughout a Document's Lifecycle) to Informational RFC
> 
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Document Shepherding Throughout a Document's Lifecycle'
>   <draft-leiba-extended-doc-shepherd-00.txt> as Informational RFC
> 
> The author is documenting his own opinion, and he is presenting that
> opinion to the community for consideration.  The author is not
> proposing any formal change, but he is interested in community
> comments.  Since this is the authors opinions, changes to the document
> based on received comments be at the author's discretion.  As a
> result, the finished document will not claim to reflect IETF community
> consensus.
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-10-23. 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
> 
>    RFC 4858 talks about "Document Shepherding from Working Group Last
>    Call to Publication".  There's a significant part of a document's
>    life that happens before working group last call, starting, really,
>    at the time a working group begins discussing a version of the idea
>    that's been posted as an individual draft.  It seems reasonable and
>    helpful to begin shepherding when there's a call for adoption as a
>    working group document, and this document gives one Area Director's
>    view of how that extended shepherding function might work, and what
>    tasks might be involved throughout the document's lifecycle.
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/ballot/
> 
> No IPR declarations have been submitted directly on this I-D.



From abdussalambaryun@gmail.com  Tue Sep 25 12:31:09 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECBB421F8970 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 12:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.523
X-Spam-Level: 
X-Spam-Status: No, score=-3.523 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7e-HGnuhg4V for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 12:31:09 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2778121F8967 for <ietf@ietf.org>; Tue, 25 Sep 2012 12:31:09 -0700 (PDT)
Received: by qcac10 with SMTP id c10so6513998qca.31 for <ietf@ietf.org>; Tue, 25 Sep 2012 12:31:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Udm5pbOcTh0wjPNLuHxYri4TN2iOjN+/a3Rb4A/HbSg=; b=u8laBganCTseQNakdM+VIqPwURcSsa1hY5VMDL33jEVPK2ErAtfiU43DrWLst2NV9H NMsJC+8s1PnaU/ouPS/ikZKqp5+zPEpUmhXYTgiDA/PeHv3Z6zCxlhDTSnvHx3yC5Ivo kS2EvHObzX7C8LSTXNCgoLBtiaciznrvikY1njHfSaV8XwE4yr20DsZWQvFQ/w7FHwBI XgEJlbtZ2hKqu9pYuunx5KcyGqkdk0nenp2bHDyWyh9sRA22phCpN4kUrqmD+qpk4uHP zx456e4KZyJ6mZZX2laLqvxcaZxX7/kP/PTLK/y4FYfhTyGpzZzM+a//g44ZueVVXh2Q UYdQ==
MIME-Version: 1.0
Received: by 10.58.12.231 with SMTP id b7mr10208104vec.28.1348599800606; Tue, 25 Sep 2012 12:03:20 -0700 (PDT)
Received: by 10.220.2.83 with HTTP; Tue, 25 Sep 2012 12:03:20 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120925103806.0989ff10@resistor.net>
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net>
Date: Tue, 25 Sep 2012 20:03:20 +0100
Message-ID: <CADnDZ8-L+MSxVWV=goNrSC1xV69dxDBZ__kwt4NSmVbVZmfz6g@mail.gmail.com>
Subject: Re: Failing to convince an IETF WG (was: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=047d7b41bf320f2e7c04ca8b5c72
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, 25 Sep 2012 19:31:10 -0000

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

SM>There is no such thing as an Independent Stream submitting a Standards
Track document. An author can submit an I-D through the IETF Stream if the
author would like the I-D to be published on the Standards Track. A WG can
adopt such an I-D.

Russ>The Independent Submission Stream cannot be used to produce standards
track RFCs.

So if I follow the second input above, then independent submission cannot
be used to produce standard, then it should go through WG. The question was
if there was disagreement from WG to accept, is there a procedure for the
submitter to follow, or he must follow the WG and forget about his work
(many inventions in the world were not convined by groups/experts, but were
invented only when inventor didn't follow them but followed reasoning).
Sorry if not clear,

AB
On Tue, Sep 25, 2012 at 7:15 PM, SM <sm@resistor.net> wrote:

> Hi Abdussalam,
>
> At 10:19 25-09-2012, Abdussalam Baryun wrote:
>
>> I ment to say that if independent stream cannot submit a standard track
>> document, then do we have a procedure for the WG to accept or not consider?
>> The last call that you refered to was a WG not independent.
>>
>
> There is no such thing as an Independent Stream submitting a Standards
> Track document.  An author can submit an I-D through the IETF Stream if the
> author would like the I-D to be published on the Standards Track.  A WG can
> adopt such an I-D.
>
> Regards,
> -sm
>
> P.S. I read your message [1] again.  The first part seems to be about "the
> reason why some individuals fail to convince an IETF WG".  The last part
> seem to be about "a procedure to make participants follow to convince WG
> and a procedure that WGs follow to accept with reason".  There was then an
> "AB" and three hyphens on the next line.  It is followed by "but is this
> Why not? I thought any I-D can be standard track,".  It was difficult for
> me to understand [2] the message.
>
> 1. http://www.ietf.org/mail-**archive/web/ietf/current/**msg75097.html<http://www.ietf.org/mail-archive/web/ietf/current/msg75097.html>
> 2. http://www.ietf.org/mail-**archive/web/ietf/current/**msg60902.html<http://www.ietf.org/mail-archive/web/ietf/current/msg60902.html>
>

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

<div>SM&gt;There is no such thing as an Independent Stream submitting a Sta=
ndards Track document. An author can submit an I-D through the IETF Stream =
if the author would like the I-D to be published on the Standards Track.  A=
 WG can adopt such an I-D.</div>
<div>=A0</div><div>Russ&gt;The Independent Submission Stream cannot be used=
 to produce standards track RFCs.<br><br>So if I follow the second input ab=
ove, then independent submission cannot be used to produce standard, then i=
t should go through WG. The question was if there was disagreement from WG =
to accept, is there a procedure for the submitter to follow, or=A0he must f=
ollow the WG and forget about his work (many inventions in the world were n=
ot convined by groups/experts, but were invented=A0only when inventor didn&=
#39;t follow them but followed reasoning). Sorry if not clear,</div>
<div>=A0</div><div>AB<br></div><div class=3D"gmail_quote">On Tue, Sep 25, 2=
012 at 7:15 PM, SM <span dir=3D"ltr">&lt;<a href=3D"mailto:sm@resistor.net"=
 target=3D"_blank">sm@resistor.net</a>&gt;</span> wrote:<br><blockquote sty=
le=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,2=
04,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_quote=
">
Hi Abdussalam,<div class=3D"im"><br>
At 10:19 25-09-2012, Abdussalam Baryun 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">
I ment to say that if independent stream cannot submit a standard track doc=
ument, then do we have a procedure for the WG to accept or not consider? Th=
e last call that you refered to was a WG not independent.<br>
</blockquote>
<br></div>
There is no such thing as an Independent Stream submitting a Standards Trac=
k document. =A0An author can submit an I-D through the IETF Stream if the a=
uthor would like the I-D to be published on the Standards Track. =A0A WG ca=
n adopt such an I-D.<br>

<br>
Regards,<br>
-sm<br>
<br>
P.S. I read your message [1] again. =A0The first part seems to be about &qu=
ot;the reason why some individuals fail to convince an IETF WG&quot;. =A0Th=
e last part seem to be about &quot;a procedure to make participants follow =
to convince WG and a procedure that WGs follow to accept with reason&quot;.=
 =A0There was then an &quot;AB&quot; and three hyphens on the next line. =
=A0It is followed by &quot;but is this Why not? I thought any I-D can be st=
andard track,&quot;. =A0It was difficult for me to understand [2] the messa=
ge.<br>

<br>
1. <a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg75097.ht=
ml" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/ietf/curr=
ent/<u></u>msg75097.html</a><br>
2. <a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg60902.ht=
ml" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/ietf/curr=
ent/<u></u>msg60902.html</a> =A0<br>
</blockquote></div><br>

--047d7b41bf320f2e7c04ca8b5c72--

From tglassey@earthlink.net  Tue Sep 25 12:37:18 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 624C221F8979 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 12:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jmqiDMC1a5ln for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 12:37:17 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id 8483921F8976 for <ietf@ietf.org>; Tue, 25 Sep 2012 12:37:17 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=VlY3CizBsvHXhzT1IcMyqjhMay5/wq4dczYTbosPTv4oJY2xcU4tZ9hLQqjTh/kD; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TGawX-0001g8-1l for ietf@ietf.org; Tue, 25 Sep 2012 15:37:17 -0400
Message-ID: <506207EB.4040300@earthlink.net>
Date: Tue, 25 Sep 2012 12:37:15 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Failing to convince an IETF WG
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net>
In-Reply-To: <6.2.5.6.2.20120925103806.0989ff10@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec794850b0f7d06e93d91943ecdd20a5600a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2012 19:37:18 -0000

On 9/25/2012 11:15 AM, SM wrote:
> Hi Abdussalam,
> At 10:19 25-09-2012, Abdussalam Baryun wrote:
>> I ment to say that if independent stream cannot submit a standard 
>> track document, then do we have a procedure for the WG to accept or 
>> not consider? The last call that you refered to was a WG not 
>> independent.
>
> There is no such thing as an Independent Stream submitting a Standards 
> Track document.  An author can submit an I-D through the IETF Stream 
> if the author would like the I-D to be published on the Standards 
> Track.  A WG can adopt such an I-D.
>
> Regards,
> -sm
>
> P.S. I read your message [1] again.  The first part seems to be about 
> "the reason why some individuals fail to convince an IETF WG".  The 
> last part seem to be about "a procedure to make participants follow to 
> convince WG and a procedure that WGs follow to accept with reason".  
> There was then an "AB" and three hyphens on the next line.  It is 
> followed by "but is this Why not? I thought any I-D can be standard 
> track,".  It was difficult for me to understand [2] the message.
>
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg75097.html
> 2. http://www.ietf.org/mail-archive/web/ietf/current/msg60902.html
This is the problem we have - the IETF wants to be able to hold everyone 
hostage and force people to work inside from its operating models today. 
This is a fraud of the most obnoxious type - it is the GSO lying through 
its teeth about how transparent it is IMHO... but these things will all 
come out in the wash I think.

The IETF needs total transparency and a way to process alternative 
standards so that it is not actively involved in anything dark and covert.
Todd
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2441/5291 - Release Date: 09/25/12
>
>


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


From framefritti@gmail.com  Tue Sep 25 13:04:08 2012
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B628E1F0CE2 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 13:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level: 
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tv5IGFEfsQg7 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 13:04:07 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id CEC911F0CD4 for <ietf@ietf.org>; Tue, 25 Sep 2012 13:04:07 -0700 (PDT)
Received: by iec9 with SMTP id 9so16527082iec.31 for <ietf@ietf.org>; Tue, 25 Sep 2012 13:04:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=cQFAES33iNLzFH19zI5MEtFC2uVoThC2IkV0U6wQOng=; b=iEERwd80CxUewz3u8UreAIoE58UL5X1eeTxfJZkY4sRnlJOA7ZGd7C5+Zlcgv+jqJu RoP2LSODj0kEEF0u8jkEBZUvT2dRZg4lU5IGq+H6ih7nXPfWP9cWW1vR6BJbnFYUqWUT V4wqc7hk1n1EwXt9jWlYsAJPGOOd0i/NBYtASnIlQu3k/xPozIW9GwzeO/RCyEIAB0G5 +LJRsJTjDwegUFLfB4sjTy0+xXet55lfHotH4tu+4NXQfoyKnLAnQO0SmmseIcBzY4XC YEI/8T/WOsMyHK4LG4B4G/ZfCsL1D+syLVazhVPQkb6Mxkuyde3QcS7MaVf/PpvXoL0/ OZpw==
MIME-Version: 1.0
Received: by 10.50.196.231 with SMTP id ip7mr9216514igc.7.1348603440332; Tue, 25 Sep 2012 13:04:00 -0700 (PDT)
Received: by 10.64.166.72 with HTTP; Tue, 25 Sep 2012 13:04:00 -0700 (PDT)
Date: Tue, 25 Sep 2012 22:04:00 +0200
Message-ID: <CABSMSPWJ1zNg64U1m08vEQ6RoR7cyzYMHf7Ocbhjy50pPCTEpQ@mail.gmail.com>
Subject: FYI: Article on opensource.com about "The Modern Paradigm for Standards"
From: Riccardo Bernardini <framefritti@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=14dae93405d500fff104ca8c3520
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Sep 2012 20:04:08 -0000

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

I thought that maybe someone could be interested


http://opensource.com/government/12/9/five-major-standards-organizations-speak-out?sc_cid=701600000006R96AAE

Enjoy!

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

I thought that maybe someone could be interested<div><br></div><div>=A0=A0<=
a href=3D"http://opensource.com/government/12/9/five-major-standards-organi=
zations-speak-out?sc_cid=3D701600000006R96AAE">http://opensource.com/govern=
ment/12/9/five-major-standards-organizations-speak-out?sc_cid=3D70160000000=
6R96AAE</a></div>
<div><br></div><div>Enjoy!</div>

--14dae93405d500fff104ca8c3520--

From stpeter@stpeter.im  Tue Sep 25 13:51:21 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4361521F87C9 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 13:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HbVVJkLE233n for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 13:51:20 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id BC9BF21F87B6 for <ietf@ietf.org>; Tue, 25 Sep 2012 13:51:17 -0700 (PDT)
Received: from [64.101.72.41] (unknown [64.101.72.41]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1173B40062; Tue, 25 Sep 2012 14:52:40 -0600 (MDT)
Message-ID: <5062140F.7060807@stpeter.im>
Date: Tue, 25 Sep 2012 14:29:03 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: FW: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document Shepherding Throughout a Document's Lifecycle) to Informational RFC
References: <041e01cd9b51$cc632bc0$65298340$@olddog.co.uk>
In-Reply-To: <041e01cd9b51$cc632bc0$65298340$@olddog.co.uk>
X-Enigmail-Version: 1.4.4
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, 25 Sep 2012 20:51:21 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Good questions all.

IMHO, Independent Stream at most. Or a simple blog post would do. :)

On 9/25/12 1:13 PM, Adrian Farrel wrote:
> Hi, I don't understand the process for this document.
> 
> I read Russ's  words, but I don't glean the meaning :-(
> 
> This document is in IETF last call for publication in the IETF
> stream. Yet any comments received will not necessarily be taken on
> board and the document will not be published as having IETF
> consensus. Why does that feel like Independent Stream to me? And
> why is an RFC needed simply to record the thoughts of one person?
> 
> Is the purpose of the Last Call simply to help the IESG make its
> decision?
> 
> Thanks, Adrian (Who has yet to read the document, but feels that he
> cannot make any useful comments since the content is the opinion of
> one person and he has no idea whether the document correctly
> reflects the opinion of that person.)
> 
>> -----Original Message----- From: ietf-announce-bounces@ietf.org
>> [mailto:ietf-announce- bounces@ietf.org] On Behalf Of The IESG 
>> Sent: 25 September 2012 15:41 To: IETF-Announce Subject: Last
>> Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document 
>> Shepherding Throughout a Document's Lifecycle) to Informational
>> RFC
>> 
>> 
>> The IESG has received a request from an individual submitter to
>> consider the following document: - 'Document Shepherding
>> Throughout a Document's Lifecycle' 
>> <draft-leiba-extended-doc-shepherd-00.txt> as Informational RFC
>> 
>> The author is documenting his own opinion, and he is presenting
>> that opinion to the community for consideration.  The author is
>> not proposing any formal change, but he is interested in
>> community comments.  Since this is the authors opinions, changes
>> to the document based on received comments be at the author's
>> discretion.  As a result, the finished document will not claim to
>> reflect IETF community consensus.
>> 
>> The IESG plans to make a decision in the next few weeks, and
>> solicits final comments on this action. Please send substantive
>> comments to the ietf@ietf.org mailing lists by 2012-10-23.
>> 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
>> 
>> RFC 4858 talks about "Document Shepherding from Working Group
>> Last Call to Publication".  There's a significant part of a
>> document's life that happens before working group last call,
>> starting, really, at the time a working group begins discussing a
>> version of the idea that's been posted as an individual draft.
>> It seems reasonable and helpful to begin shepherding when there's
>> a call for adoption as a working group document, and this
>> document gives one Area Director's view of how that extended
>> shepherding function might work, and what tasks might be involved
>> throughout the document's lifecycle.
>> 
>> 
>> The file can be obtained via 
>> http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/
>>
>>
>> 
IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/ballot/
>>
>>
>> 
No IPR declarations have been submitted directly on this I-D.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBiFA8ACgkQNL8k5A2w/vwtegCfZ76DaVQwi7r0UsLPUI2ftPBj
69EAnijKdGdaQ3a5b47uwApIx5DEgMxf
=fxRK
-----END PGP SIGNATURE-----

From housley@vigilsec.com  Tue Sep 25 14:31:32 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB9421F867A for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 14:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w9yfoAjMzHBC for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 14:31:31 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id B5B4B21F85A1 for <ietf@ietf.org>; Tue, 25 Sep 2012 14:31:31 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id EF8279A4003; Tue, 25 Sep 2012 17:31:36 -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 DAw9LRDIxAkq; Tue, 25 Sep 2012 17:31:27 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 6CBE89A4002; Tue, 25 Sep 2012 17:31:34 -0400 (EDT)
Subject: Re: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document Shepherding Throughout a Document's Lifecycle) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <041e01cd9b51$cc632bc0$65298340$@olddog.co.uk>
Date: Tue, 25 Sep 2012 17:31:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <589E4C42-EC3E-4E27-8A9A-710940EFFB77@vigilsec.com>
References: <041e01cd9b51$cc632bc0$65298340$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1084)
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, 25 Sep 2012 21:31:32 -0000

I felt that the IETF Last Call would bring it to the attention of the =
community.  This seems worthwhile because the opinions are about an IETF =
process.

Russ


On Sep 25, 2012, at 3:13 PM, Adrian Farrel wrote:

> Hi,
> I don't understand the process for this document.
>=20
> I read Russ's  words, but I don't glean the meaning :-(
>=20
> This document is in IETF last call for publication in the IETF stream.
> Yet any comments received will not necessarily be taken on board and =
the
> document will not be published as having IETF consensus.
> Why does that feel like Independent Stream to me?
> And why is an RFC needed simply to record the thoughts of one person?
>=20
> Is the purpose of the Last Call simply to help the IESG make its =
decision?
>=20
> Thanks,
> Adrian (Who has yet to read the document, but feels that he cannot =
make any
> useful comments since the content is the opinion of one person and he =
has no
> idea whether the document correctly reflects the opinion of that =
person.)
>=20
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 25 September 2012 15:41
>> To: IETF-Announce
>> Subject: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> =
(Document
>> Shepherding Throughout a Document's Lifecycle) to Informational RFC
>>=20
>>=20
>> The IESG has received a request from an individual submitter to =
consider
>> the following document:
>> - 'Document Shepherding Throughout a Document's Lifecycle'
>>  <draft-leiba-extended-doc-shepherd-00.txt> as Informational RFC
>>=20
>> The author is documenting his own opinion, and he is presenting that
>> opinion to the community for consideration.  The author is not
>> proposing any formal change, but he is interested in community
>> comments.  Since this is the authors opinions, changes to the =
document
>> based on received comments be at the author's discretion.  As a
>> result, the finished document will not claim to reflect IETF =
community
>> consensus.
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2012-10-23. 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
>>   RFC 4858 talks about "Document Shepherding from Working Group Last
>>   Call to Publication".  There's a significant part of a document's
>>   life that happens before working group last call, starting, really,
>>   at the time a working group begins discussing a version of the idea
>>   that's been posted as an individual draft.  It seems reasonable and
>>   helpful to begin shepherding when there's a call for adoption as a
>>   working group document, and this document gives one Area Director's
>>   view of how that extended shepherding function might work, and what
>>   tasks might be involved throughout the document's lifecycle.
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/
>>=20
>> IESG discussion can be tracked via
>> =
http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/ballot/
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>=20
>=20


From barryleiba.mailing.lists@gmail.com  Tue Sep 25 14:37:53 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2771E1F0CBA for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 14:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.956
X-Spam-Level: 
X-Spam-Status: No, score=-102.956 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxm89YtCwSex for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 14:37:52 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 61EB81F0C55 for <ietf@ietf.org>; Tue, 25 Sep 2012 14:37:52 -0700 (PDT)
Received: by lbok13 with SMTP id k13so852224lbo.31 for <ietf@ietf.org>; Tue, 25 Sep 2012 14:37:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=fadew7DJ1wEQPG2XjOiP1qu/h0ITuDgxUmGgebyfxKM=; b=b+nmF7liBgLousQgRyQYNEN1AfV41KCydFjTZPbqQknXwdXC80Zxvpms9IAE6P3PfH k2CWZPsX2D2fPIz/vtY9YfAcLq4TeaeO3r63WgoUFOkZqEz5cmOTVQAR6eVEHdRrd9GD gLwBQ9wH6hzorR87TIAAsTgeOtR/rMZsfJBQLTh8OW63A3F6MzD6jrFPDBMAovPU6lZk wRY8FHTAkIgUqZXbd7FUdyZnEOTYoP7FWDjNb615bKi9GCdsLAFCOodSj9UYAh0C6AcQ eYUHGHZdxeqprm8RV1Ai6v3CPiiVQkVxrL80di7G0K3Hw8yEcHB3Yvv7oSx0DkDX22O6 NB6g==
MIME-Version: 1.0
Received: by 10.112.88.73 with SMTP id be9mr6050506lbb.72.1348609071307; Tue, 25 Sep 2012 14:37:51 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.91.33 with HTTP; Tue, 25 Sep 2012 14:37:51 -0700 (PDT)
In-Reply-To: <041e01cd9b51$cc632bc0$65298340$@olddog.co.uk>
References: <041e01cd9b51$cc632bc0$65298340$@olddog.co.uk>
Date: Tue, 25 Sep 2012 17:37:51 -0400
X-Google-Sender-Auth: Ml5LmfY33Anw9U3TNCHnmYxVY2M
Message-ID: <CAC4RtVDoRy7C=62dsDqiTzM5JTNGZm9YiO1EGvS69Jhq57+cGg@mail.gmail.com>
Subject: Re: FW: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document Shepherding Throughout a Document's Lifecycle) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: adrian@olddog.co.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: Tue, 25 Sep 2012 21:37:53 -0000

> I don't understand the process for this document.
>
> I read Russ's  words, but I don't glean the meaning :-(

Think of it like the documents where we republish something from
another organization:

   http://datatracker.ietf.org/doc/rfc6449/

....or publish something that describes how a product from a
particular company works:

   http://datatracker.ietf.org/doc/rfc6281/
   http://datatracker.ietf.org/doc/draft-claise-export-application-info-in-ipfix/

> Why does that feel like Independent Stream to me?

Russ thought that process-related stuff wasn't suitable for the
Independent Stream.

Barry

From sm@resistor.net  Tue Sep 25 15:18:09 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88D861F0C67 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 15:18:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s+9n+t2n6sEV for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 15:18: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 9D69621F8848 for <ietf@ietf.org>; Tue, 25 Sep 2012 15:18:08 -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 q8PMHwQi012662 for <ietf@ietf.org>; Tue, 25 Sep 2012 15:18:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1348611482; bh=g+YHyk1pc31ndeP3SmGLKl/hOxdN9siBer/Yh1TwIn0=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=TIPbRbpSomdVkOtHTfE4v7JG7/rebp0Nh+xe+g4VSTklbUvG8vSEvpO4tHG4y/qWu kChcz6fMk4b3hRKq4f6TgGU2m2r2kfAAXM+3rnptkSeWUi6eOThwHLey5vlfHVUDxW AinLUmlqZENsEO/arC4xVf2x5JaqAi8xRajZXyWQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1348611482; i=@resistor.net; bh=g+YHyk1pc31ndeP3SmGLKl/hOxdN9siBer/Yh1TwIn0=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=tw+q1lVViuxc5fv4xhTzD5vTqp08cl7KTKGqwFzL8UvWYAcU0XOs5Cn5RpWN4qTtt KoE57vcMHHmikcfxuSmZ85NHn7HVJJHNFpisVVb72mdaq6l2q5ACOnsQIGaLzxx+M+ t98bSvPVaEOMBQ4nRNMpggkWf1JtTE+4we4r/W+Q=
Message-Id: <6.2.5.6.2.20120925123724.0a05f978@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 25 Sep 2012 15:06:38 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document Shepherding Throughout a Document's Lifecycle) to Informational RFC
In-Reply-To: <20120925144038.19851.49608.idtracker@ietfa.amsl.com>
References: <20120925144038.19851.49608.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2012 22:18:09 -0000

At 07:40 25-09-2012, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Document Shepherding Throughout a Document's Lifecycle'
>   <draft-leiba-extended-doc-shepherd-00.txt> as Informational RFC
>
>The author is documenting his own opinion, and he is presenting that
>opinion to the community for consideration.  The author is not
>proposing any formal change, but he is interested in community
>comments.  Since this is the authors opinions, changes to the document
>based on received comments be at the author's discretion.  As a
>result, the finished document will not claim to reflect IETF community
>consensus.
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2012-10-23. Exceptionally, comments may be

This Last Call is highly unusual.  If the changes that are accepted 
is a matter of author discretion, why is there a Last Call and what 
is the role of the IESG here?

My reading of the draft is that it is a mix of RFC 4858 and the 
document life cycle (see RFC 6174).

In the Introduction Section:

   "It seems reasonable and helpful to begin shepherding at the time there's
    a call for adoption as a working group document, and this document
    gives one Area Director's view of how that extended shepherding
    function might work, and what tasks might be involved throughout the
    document's lifecycle."

This is good advice.  It is however problematic to implement in my 
humble opinion.  The shepherding process does not always work 
well.  There are diligent shepherds and absent shepherds.  Some 
authors end up with a bad IETF experience because of that.  In my 
humble opinion, it cannot be fixed through methodologies.  I don't 
know whether that problem can be solved.  Extended shepherding means 
more work.  It leaves less leeway for choosing a shepherd based on 
individual availability.

In Section 3.1:

   "This is the time to choose a Responsible Chair for the document, much
    as it will eventually have a Responsible Area Director later in its
    life."

With the introduction of "Responsible Chair" the other Chairs might 
consider themselves as spectators.  Whether a Chair should take the 
lead on a document is up to the Chairs to decide.  In simple terms, 
they have the latitude to decide how to get the work done.

   "Giving significant responsibility can be an excellent training
    exercise, preparing participants to take on future roles as
    Working Group Chairs."

Once a draft clears the AD review stage it won't get published if it 
is not kept "moving".   This is where the document shepherd can be 
useful.  I would suggest having someone with adequate experience 
instead of using this stage as a training exercise.  The IETF idea of 
a training exercise is sending someone to face live rounds without an 
instruction manual.

   "And in a busy working group, offloading work from the Chairs to
    senior, experienced people (perhaps former Chairs or former ADs)
    can prevent the Chairs from being overcommitted, enabling the work
    to move forward much more efficiently."

Yes.  This is less about document shepherding though.

   "The issue tracker can be used to record not just the issues
    themselves, but significant parts of the discussion on both sides,
    helping to make it clearer what the resolution was and why, and
    whether a particular request to re-open a closed issue really
    involves new points or is just a re-hash."

This is significant work.  It is also a matter of style.

   "And as RFC 4858 says, the Shepherd should also email the writeup to
    the working group's mailing list, so the working group is aware of it."

There is a fairly good write-up at 
http://www.ietf.org/mail-archive/web/precis/current/msg00327.html  :-)

The draft may be a better fit as Wiki material.  If the draft is 
meant to help shepherds, I suggest discussing cases where things 
could be improved.  For example, "documents spend *months* in AD 
Review state, largely because of lack of good shepherding".  How long 
should the shepherd wait before sending the AD a reminder?  "Use your 
judgement" only works if one is aware of existing 
practices.  Sometimes it helps to say "remind me in a week or 
two".  The dead zone is from AD review to IESG evaluation.  I suggest 
focusing on that part instead of creating an extended shepherding process.

If I could paraphrase the draft, I'd say that the intent is to change 
shepherding from a mechanical exercise into a information 
gathering/input for decision-making/process-stumbling avoidance 
exercise.  The hurdle is political inappropriateness.

Regards,
-sm  


From housley@vigilsec.com  Tue Sep 25 16:24:52 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 075981F0C59 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 16:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5M2ISd-W5tjb for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 16:24:51 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 6E20F1F0425 for <ietf@ietf.org>; Tue, 25 Sep 2012 16:24:51 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id AAF419A4003; Tue, 25 Sep 2012 19:24: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 G9zE-XZlzLnm; Tue, 25 Sep 2012 19:24:47 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 836169A4002; Tue, 25 Sep 2012 19:24:51 -0400 (EDT)
Subject: Re: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document Shepherding Throughout a Document's Lifecycle) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20120925123724.0a05f978@resistor.net>
Date: Tue, 25 Sep 2012 19:24:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CFC4AF85-53B0-4F83-B734-131F69987BFB@vigilsec.com>
References: <20120925144038.19851.49608.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120925123724.0a05f978@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
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, 25 Sep 2012 23:24:52 -0000

SM:

>> The IESG has received a request from an individual submitter to =
consider
>> the following document:
>> - 'Document Shepherding Throughout a Document's Lifecycle'
>>  <draft-leiba-extended-doc-shepherd-00.txt> as Informational RFC
>>=20
>> The author is documenting his own opinion, and he is presenting that
>> opinion to the community for consideration.  The author is not
>> proposing any formal change, but he is interested in community
>> comments.  Since this is the authors opinions, changes to the =
document
>> based on received comments be at the author's discretion.  As a
>> result, the finished document will not claim to reflect IETF =
community
>> consensus.
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2012-10-23. Exceptionally, comments =
may be
>=20
> This Last Call is highly unusual.  If the changes that are accepted is =
a matter of author discretion, why is there a Last Call and what is the =
role of the IESG here?

Since the document is about one person's opinion on IETF process, I felt =
it useful to bring the document to the attention of the community.  =
Others may agree or disagree.  Hopefully it will spur discussion.  =
Perhaps it will spur a group to propose a change to the process.

After the Last Call, the IESG will make a decision about publication of =
this document as an IETF Stream RFC.

Russ


From glenzorn@gmail.com  Tue Sep 25 18:03:11 2012
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 3A42721F8472; Tue, 25 Sep 2012 18:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.216
X-Spam-Level: 
X-Spam-Status: No, score=-3.216 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Ub7qmI-aPwl; Tue, 25 Sep 2012 18:03:10 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 762AE21F8425; Tue, 25 Sep 2012 18:03:10 -0700 (PDT)
Received: by danh15 with SMTP id h15so10769dan.31 for <multiple recipients>; Tue, 25 Sep 2012 18:03:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=nvhAs3Pg10fWPAU8MbM+lMbjkE+aYkedy9fhadOGw5o=; b=ILHvijeq3KI53TF8G71Sw7YzY/92UURIkmYWE4/oxwmNVHIm1mPbpMgA+QGa4gs/Kr 64YdAhi3ZmNVA8dnQb5XAjfw+4A9msTRYV49su7Wps6Y/dgGS18u71+iu/9qjNzfL/P9 QHMH/boIEGUUBjxufrlX2VONOzOnu3GPsygOTahXz5O4vYpCE8+cgRuUP4Y8kM9Wrhyy 3PkhQTpo6X1eRasu/eRJuCBys0SV5vCKbIRclwMuBwuojk2phazqmttzMGw7VLBTlxT2 hN1iaYpak31E8d9k68KhY7b/i7euWXG4twneJgZbzAJaDCOJNdoEVl3KBp/L9uzTfwFT zZPQ==
Received: by 10.68.189.164 with SMTP id gj4mr50287085pbc.48.1348621390179; Tue, 25 Sep 2012 18:03:10 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-120-227-192.revip2.asianet.co.th. [124.120.227.192]) by mx.google.com with ESMTPS id gf3sm1104098pbc.74.2012.09.25.18.03.06 (version=SSLv3 cipher=OTHER); Tue, 25 Sep 2012 18:03:09 -0700 (PDT)
Message-ID: <50625449.7010305@gmail.com>
Date: Wed, 26 Sep 2012 08:03:05 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120830 Thunderbird/15.0
MIME-Version: 1.0
To: Elwyn Davies <elwynd@dial.pipex.com>
Subject: Re: Gen-art LC review of draft-ietf-dime-erp-12
References: <5060D8AB.8010807@dial.pipex.com>
In-Reply-To: <5060D8AB.8010807@dial.pipex.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-dime-erp <draft-ietf-dime-erp@tools.ietf.org>, General Area Review Team <gen-art@ietf.org>, dime mailing list <dime@ietf.org>, draft-ietf-dime-erp.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: Wed, 26 Sep 2012 01:03:11 -0000

On 09/25/2012 05:03 AM, Elwyn Davies wrote:

> Gen-art LC review of  draft-ietf-dime-erp-12 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-dime-erp-12.txt Reviewer: Elwyn Davies Review
 > Date: 24 September 2012 IETF LC End Date: 24 September 2012 IESG
 > Telechat date: (if known) -
 >
 > Summary: Almost ready for the IESG. There are some minor wording
 > issues to sort out in s3, some advice on advertising domain names in
 > s5 and possibly some extra words needed in the security
 > considerations. In addition there a few minor nits.
 >
 > Major issues: None.
 >
 > Minor issues: s3: Both paragraphs use the phrase '...document assumes
 > the existence of at most one...'. Does this really mean 'exactly
 > one'?

Oddly enough, it means just what it says.

> If not, what happens if there  is exactly zero servers for either
 > type?

Both protocols will fail gracefully.

> What would the consequences of  there being more than one
 > logical server?

If the message is directed to a logical server not in possession of the 
rRK or rDSRK (depending upon where the server is located), ERP will fail 
inappropriately.

> Is this tied into the statement  in s4:
 > The ER server is located either in the home domain (same as EAP
 > server) or in the visited domain (same as authenticator, when it
 > differs from the home domain).

I don't think so.

> This would seem to imply that  the zero case means that it may not be
 > essential to have an ER server in a domain.

It's not.

>
 > S3, para 1:
 >> If multiple ER servers are deployed in the domain, we assume that
 >> they can be used interchangeably.
 > Are we talking physical servers here?

Yes.

> If not please refer to the
 > previous comment.
 >
 > s5, para 1: How would the authenticator advertise the domain name in
 > this context?

That is outside the scope of this draft.

>
 > s13: Looking at the various security considerations that are
 > imported, I wondered if some extra words were needed in respect of a
 > couple of the cases: - s8.4 of RFC 4072: (does distributing the
 > bootstrapping master key make things any worse here?) -

I don't think so.

> s8 of RFC
 > 6696 (does the DIME usage preserve the limited key scope?; is the
 > domino effect equally well avoided?)

Yes and yes.

>
 > Nits/editorial comments:
 >
 > s1: 'and re-use the Diameter EAP commands (DER/DEA).' : DER and DEA
 > ought to be expanded here. Or it might be less verbose to point at s2
 > where they are currently expanded, thus: 'and re-use the Diameter EAP
 > commands listed in Section 2.'

These are both defined in RFC 4072.

>
 > s2, para 2: Need to expand acronyms rRK and rDSRK.

rRK is defined in RFC 6696.

>
 > s4, para 7: Should explicitly say that the ERP/DEA message is sent to
 > the authenticator.

It's not: the authenticator is an EAP protocol entity.  The message is 
sent to the Diameter peer, like all Diameter answer messages.

>
 > s8.3.3: s/RGC 6696/RFC 6696/
 >
 >

Fixed, thanks.



From dwm@xpasc.com  Tue Sep 25 18:32:05 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80F5D1F0C90 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 18:32: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]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IomiwzYYcegy for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 18:32:04 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id CE0F51F0C6E for <ietf@ietf.org>; Tue, 25 Sep 2012 18:32:04 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 4DD94408AF for <ietf@ietf.org>; Wed, 26 Sep 2012 01:32:04 +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 q8Q1W4Nx005996 for <ietf@ietf.org>; Tue, 25 Sep 2012 18:32:04 -0700
Date: Tue, 25 Sep 2012 18:32:04 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Failing to convince an IETF WG
In-Reply-To: <506207EB.4040300@earthlink.net>
Message-ID: <alpine.LRH.2.01.1209251825130.5707@egate.xpasc.com>
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net> <506207EB.4040300@earthlink.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: Wed, 26 Sep 2012 01:32:05 -0000

On Tue, 25 Sep 2012, tglassey wrote:

> The IETF needs total transparency and a way to process alternative standards
> so that it is not actively involved in anything dark and covert.
> Todd

That makes no sense ... something can't be an IETF standard if it doesn't
get created and adopted using The IETF's processes. The word 'standard'
implies the approval of some organization/standards body. The independant
stream does allow publishing of alternatives to IETF Standards, but that
doesn't make tham alternative standards. For that some other recognized
group needs to declare it a standard and then it will be An XYZ Group
Standard, not an IETF Standard.

From glenzorn@gmail.com  Tue Sep 25 19:14:28 2012
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 D8F3B1F0C51 for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 19:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.312
X-Spam-Level: 
X-Spam-Status: No, score=-3.312 tagged_above=-999 required=5 tests=[AWL=0.288,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUDo7cUbSDkB for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 19:14:28 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4841F0C3A for <ietf@ietf.org>; Tue, 25 Sep 2012 19:14:28 -0700 (PDT)
Received: by pbbro8 with SMTP id ro8so1077646pbb.31 for <ietf@ietf.org>; Tue, 25 Sep 2012 19:14:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=aOezKEFXQwECeCz2sKOL0KaTK6avPigmaljAMbf5CT0=; b=RnABzTvRihKpuFGjnAgPp3iGJgpBChFOmPuomWt2hXs2J25uIONMfooRvkksRh4+Ht I69dJv7AVKfIkD1VjdkTUMU1WBz5WnaVPpnOO9vPn0sGhwV2xk5yczqYPWv9TFMkCmU3 O6TzcmaERG5ISGzIUtiWIWnx6LVnXUrDHkGfM6P3haBuYOklDiLRMTwAGjfNpjW7scoD NYSAWUwdp+/ES8wnnPlKNB2m7/lXwvk9xaxU1MkYXbyiL6mmCnvylQ9e1z+Cl3bh1Ea9 8GKI7ibsm+4L5Bmc8whTx8b6oZ2Wt40qU9f/c3iza07Q698mSdYa+Dm09T/ekILWFFgj 4lJA==
Received: by 10.66.84.6 with SMTP id u6mr45035790pay.75.1348625668116; Tue, 25 Sep 2012 19:14:28 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-120-227-192.revip2.asianet.co.th. [124.120.227.192]) by mx.google.com with ESMTPS id kt2sm1201124pbc.73.2012.09.25.19.14.25 (version=SSLv3 cipher=OTHER); Tue, 25 Sep 2012 19:14:27 -0700 (PDT)
Message-ID: <50626500.6060000@gmail.com>
Date: Wed, 26 Sep 2012 09:14:24 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120830 Thunderbird/15.0
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: FW: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document Shepherding Throughout a Document's Lifecycle) to Informational RFC
References: <041e01cd9b51$cc632bc0$65298340$@olddog.co.uk> <5062140F.7060807@stpeter.im>
In-Reply-To: <5062140F.7060807@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Sep 2012 02:14:29 -0000

On 09/26/2012 03:29 AM, Peter Saint-Andre wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Good questions all.
>
> IMHO, Independent Stream at most. Or a simple blog post would do. :)
On 9/25/12 1:13 PM, Adrian Farrel wrote:
>> Hi, I don't understand the process for this document.
>>
>> I read Russ's  words, but I don't glean the meaning :-(
>>
>> This document is in IETF last call for publication in the IETF
>> stream. Yet any comments received will not necessarily be taken on
>> board and the document will not be published as having IETF
>> consensus. Why does that feel like Independent Stream to me? And
>> why is an RFC needed simply to record the thoughts of one person?
>>
>> Is the purpose of the Last Call simply to help the IESG make its
>> decision?

Spoilsports!  Why shouldn't the IESG have its very own vanity 
publication house? ;-)

...

From tglassey@earthlink.net  Tue Sep 25 19:18:12 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6437E21F846E for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 19:18:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.373
X-Spam-Level: 
X-Spam-Status: No, score=-2.373 tagged_above=-999 required=5 tests=[AWL=-0.374, BAYES_00=-2.599, SARE_BAYES_5x7=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hm6hv4PJx-bW for <ietf@ietfa.amsl.com>; Tue, 25 Sep 2012 19:18:11 -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 9BEFC21F846D for <ietf@ietf.org>; Tue, 25 Sep 2012 19:18:11 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=oz2IAHjUjxs895y0ltrgAXMTnEK7YHKPh0RwVmahajBDeUPW0mH1HvWV1xxygpKv; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TGhCU-0006pm-Oq for ietf@ietf.org; Tue, 25 Sep 2012 22:18:10 -0400
Message-ID: <506265E0.1050800@earthlink.net>
Date: Tue, 25 Sep 2012 19:18:08 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Failing to convince an IETF WG
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net> <506207EB.4040300@earthlink.net> <alpine.LRH.2.01.1209251825130.5707@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1209251825130.5707@egate.xpasc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79633ecc86f2fd386ed9a62e6571150c0f350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Sep 2012 02:18:12 -0000

On 9/25/2012 6:32 PM, David Morris wrote:
>
> On Tue, 25 Sep 2012, tglassey wrote:
>
>> The IETF needs total transparency and a way to process alternative standards
>> so that it is not actively involved in anything dark and covert.
>> Todd
> That makes no sense ... something can't be an IETF standard if it doesn't
> get created and adopted using The IETF's processes. The word 'standard'
> implies the approval of some organization/standards body.
The problem is the IETF Process is not transparent. Most of the vetting 
happens between parties offlist and no capture of that or the underlying 
processes in the standards process is in place. When the IETF was a 
trailing-edge process this wasnt an issue but as it has morphed into a 
leading edge GSO it is now.
> The independant
> stream does allow publishing of alternatives to IETF Standards, but that
> doesn't make tham alternative standards.
And that is the problem.

The IETF process of today is based on a 'consensus' process from a 
membership of zero. That in and of itself flies in the face of reason 
and ethical clarity. If there were formal members who came together in a 
framework that the IETF administered it would be OK but the process 
today is too easily abused.
> For that some other recognized
> group needs to declare it a standard and then it will be An XYZ Group
> Standard, not an IETF Standard.
That is the point - the IETF cannot hold the world hostage - it must 
provide open, provably open at that, access to its processes.

The issue is how to remove the political BS which clouds so many 
initiatives. The answer is an alternative standard process which has 
some form or predefined completion such that the standard will just 
issue. There is no fiefdom here there is no magic castle of the 
technological demigod to sacrifice a first-borne too here there is just 
simple and transparent steps which can easily be tracked.

When the journey is completed the standard will automatically issue... 
no IESG no IAB pain no extra administrative overhead for a bunch of 
lifer type standards junkies...  Just simple and clean access to the 
standard process.

Todd
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2441/5292 - Release Date: 09/25/12
>
>


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


From ron.even.tlv@gmail.com  Tue Sep 25 20:03:24 2012
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 79A2A21F8503; Tue, 25 Sep 2012 20:03: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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNdjCZfuqMRL; Tue, 25 Sep 2012 20:03:23 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 37E5B21F8501; Tue, 25 Sep 2012 20:03:23 -0700 (PDT)
Received: by qaec10 with SMTP id c10so4884679qae.10 for <multiple recipients>; Tue, 25 Sep 2012 20:03:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=nsoGHA8FSIOfIdu21YXyLfzhYiZMPOJm986R7XxiBDw=; b=AGcjk80UFAOg3l6nPC+z+byVSArRtnbugLk8jG+bSImhPzXY3RgyxDFS43B0jfiJ9g figWQ3e06A81/uVn+m3MuqBYN4kzlyy0IcV/37WfLC9abrivKyQXEwMC4kyNklvyv5D2 u61VFxxkgZ9s9YSFoN7JrZev/+qSecZAAOlNyE70arCUdlMnJ1ZENYlKER+Aghn1R+rr t9Giv9CEcu3lVRc4pBjIwdmYaE1tHYOXsY+ESoBcNNF1z3Fa0GYjVZgd48pXSxfCE+Xw QCclHbO0qZHvc/pF+zOfT3zLMnde1yEboASE2U68lVEbXUrvkHDALTyIM0uPeYMr4uJ7 hmSQ==
Received: by 10.224.53.18 with SMTP id k18mr45274034qag.1.1348628602701; Tue, 25 Sep 2012 20:03:22 -0700 (PDT)
Received: from RoniE ([76.15.217.235]) by mx.google.com with ESMTPS id fl3sm3219521qab.3.2012.09.25.20.03.20 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 25 Sep 2012 20:03:22 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-6man-dad-proxy.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-6man-dad-proxy-05
Date: Wed, 26 Sep 2012 05:01:28 +0200
Message-ID: <00fc01cd9b93$3b0e1990$b12a4cb0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00FD_01CD9BA3.FE96E990"
X-Mailer: Microsoft Outlook 14.0
thread-index: Ac2bkwjOXz0tUM7gTKWvlt6x4CtAQA==
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, 26 Sep 2012 03:03:24 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00FD_01CD9BA3.FE96E990
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-6man-dad-proxy-05

Reviewer: Roni Even

Review Date:2012-9-25

IETF LC End Date: 2012-10-3

IESG Telechat date:

 

Summary: This draft is ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	In section 3.1 Duplicate Address Dectection should be Duplicate
Address Detection. 

 


------=_NextPart_000_00FD_01CD9BA3.FE96E990
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:941650575;
	mso-list-type:hybrid;
	mso-list-template-ids:821320272 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><o:p>&nbsp;</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"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span>draft-ietf-6man-dad-proxy-05<o:p></o:p></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:2012&#8211;9&#8211;25<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: 2012&#8211;10&#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:<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</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> a =
standard track </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>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'>In =
section 3.1 <span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New"'>Duplicate Address Dectection</span><span =
style=3D'font-family:"Courier New"'> should be </span><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New"'>Duplicate Address </span><span style=3D'font-family:"Courier =
New"'>Detection. </span><o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00FD_01CD9BA3.FE96E990--


From abdussalambaryun@gmail.com  Wed Sep 26 00:52:40 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0299F21F87E9 for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 00:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.526
X-Spam-Level: 
X-Spam-Status: No, score=-3.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Ta2eMAotFD3 for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 00:52:39 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5054121F87E3 for <ietf@ietf.org>; Wed, 26 Sep 2012 00:52:39 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so344698vbb.31 for <ietf@ietf.org>; Wed, 26 Sep 2012 00:52:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ofU2DBzrmh0pWn/yrUBMZHzibCrQUMk+rUx3LMSd1oM=; b=YY/xDF55zZ6H7kkkxyQ0jvMnCEWy88nTJsh4jpnXMLhckwCFHZHnGEdLFuuRHJvvkh Z2FO07inmhVGSBlnbTfNMqpm8zV+OJKRPcNI5mo6GS+bdxZJsGnklakhh9ZbhpapoNhW 17K+oxLppVy65+Bpjkbr0A9p6bNgB1mSSl6ESZSpXnqeM4odvvN73k+cSgEB43iEWRPi 48iz87KeWFYNpvjVpinqNcMJWTAwqf3YDykGgch6UnW04nA/jlnidD5sBqZ9NIuJbXrn jM+Es7YloLl++8N5J6jZoIjJdxpgdBhB6txIYnIFqVZzzie1KBsYmMwcypt+8RG0T+LR 0kFg==
MIME-Version: 1.0
Received: by 10.58.13.33 with SMTP id e1mr10600335vec.51.1348645958562; Wed, 26 Sep 2012 00:52:38 -0700 (PDT)
Received: by 10.220.2.83 with HTTP; Wed, 26 Sep 2012 00:52:38 -0700 (PDT)
In-Reply-To: <CADnDZ8-K71TT2UuufyTLy-vgTjnnNqxo3X-_xbeoFRRYK9mH1A@mail.gmail.com>
References: <CADnDZ8-K71TT2UuufyTLy-vgTjnnNqxo3X-_xbeoFRRYK9mH1A@mail.gmail.com>
Date: Wed, 26 Sep 2012 09:52:38 +0200
Message-ID: <CADnDZ8-FCKnpVhVRjVnOSfr-iA9MSgvXuTJvHk4MUxhNKCnW2A@mail.gmail.com>
Subject: Re: Failing to convince an IETF WG
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: dwm@xpasc.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: Wed, 26 Sep 2012 07:52:40 -0000

Hi Dave, and All,

The beauty of the IETF is that it includes all Internet USERS
(i.e.people or organisations) around the world, no one should use it
in their interest, it should progress in the Internet
Society/Community interest following the *open* engineering knowledge
and practice. Engineers in IETF cannot disagree covering their reason
or reference they SHOULD be open. Comments in line below:
-----------------------------------------------------------------------------------------------------
>> The IETF needs total transparency and a way to process alternative
>> standards
>> so that it is not actively involved in anything dark and covert.
>
> That makes no sense ... something can't be an IETF standard if it doesn't
> get created and adopted using The IETF's processes. The word 'standard'
> implies the approval of some organization/standards body. The independant
> stream does allow publishing of alternatives to IETF Standards, but that
> doesn't make tham alternative standards. For that some other recognized
> group needs to declare it a standard and then it will be An XYZ Group
> Standard, not an IETF Standard.
---------------------------------------------------------------------------------------------------
I agree that the best practice is standards through WGs, because
*knowledge* is the core reason for the GROUP, not *politics*. IMHO,
the best practice is continue *open-discussions* with engineering and
technical knowledge to give progress to WGs, but if some participants
don't want to accept to discuss (by ignoring input) or don't want to
listen to technical/research reasons in IETF documents or  in
publications out IETF, how can the WG progress? Still thoes
participant MAY continue disagree (without discussing why) when
calling for group consensus, what will be the best practice?, will it
be that the submitter has to stop even if his/her has better arguments
in terms of engineering.

Some may fail to convice an IETF WG just because some active
participants reply that they think it is bad, without replying
*reasonably* to discussions. When I read the IETF procedure, I see
that it makes decisions at the *WG-consensus* (with no relation to
discussions and arguments) which I think not enough for progress in
the eyes of IETF mission statement.

Suggest: that if any participant disagree in I-D adoption in a WG,
then he/she take a DISCUSS position (similar to IESG memebrs process,
cannot just disagree), which they MUST have to take and reply to
messages including their good reasons for their positions (you don't
reply this idea/I-D is BAD). Any participant (submitter or who
disagrees with adoption) SHOULD have an engineering reference(s) for
such input.

If I am mistaken please advise, because I need to discuss to
understand, so we can help together make IETF better for the world
users.

Best Regards
Abdussalam Baryun
++++++++++++++++
The mission of the Internet Engineering Task Force is to make the
Internet work better by producing high-quality and relevant technical
documents that influence the way people design, use, and manage the
Internet. See http://www.ietf.org.

From abdussalambaryun@gmail.com  Wed Sep 26 01:15:33 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7FD621F8668 for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 01:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.229
X-Spam-Level: 
X-Spam-Status: No, score=-3.229 tagged_above=-999 required=5 tests=[AWL=-0.230, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_BAYES_5x7=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2UAum1YZKDe for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 01:15:32 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1796A21F87A5 for <ietf@ietf.org>; Wed, 26 Sep 2012 01:15:32 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so366822vbb.31 for <ietf@ietf.org>; Wed, 26 Sep 2012 01:15:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MDlX7wWo6jVEGjLENpSYUlmSYkXYzqKMV3XWcxgHwIc=; b=JFuhDx7nQXoawrch6XeXocTfkbq6KzoXAPZq09vf393SehBCyVNSymuwvqYlqKLT6w Gozo0vwdlw93bqTRCSoxgFgCHMPgK2nb6pnfHR9GhfccurCnTAxYhwXBiArF1PWrQBYB 2iyoGcdDj0pZr8BEbX9vCo/O75arbwrjjTrD7FsR2J1Dco2XO74Kjeb3YltvkS39TKhm fCx18ZePkZPj8zo+9ZbDpVhpFIR5pjbKBJvSl6i/YMmlXFL95txUOx1Oz5iq/xS4LvZJ saL1gFL8dmu2LJA+cjXyl12fij+NPSwPEjKYJ2+5//sl582HQXlPInGNJkglL1t1bSRV IPDg==
MIME-Version: 1.0
Received: by 10.58.13.33 with SMTP id e1mr10627312vec.51.1348647331554; Wed, 26 Sep 2012 01:15:31 -0700 (PDT)
Received: by 10.220.2.83 with HTTP; Wed, 26 Sep 2012 01:15:31 -0700 (PDT)
In-Reply-To: <CADnDZ8-FCKnpVhVRjVnOSfr-iA9MSgvXuTJvHk4MUxhNKCnW2A@mail.gmail.com>
References: <CADnDZ8-K71TT2UuufyTLy-vgTjnnNqxo3X-_xbeoFRRYK9mH1A@mail.gmail.com> <CADnDZ8-FCKnpVhVRjVnOSfr-iA9MSgvXuTJvHk4MUxhNKCnW2A@mail.gmail.com>
Date: Wed, 26 Sep 2012 10:15:31 +0200
Message-ID: <CADnDZ88RaO5iWccJLXmjLNyhRFLsegxcpEyZJ3RTBWegfJdUQw@mail.gmail.com>
Subject: Re: Failing to convince an IETF WG
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: tglassey@earthlink.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: Wed, 26 Sep 2012 08:15:33 -0000

Hi Todd,

I agree on your concerns but disagree with few issues, read my
disagree reason below:

Todd> Most of the vetting happens between parties offlist and no capture .....
AB> any organisation may have this behavior, but what matters is as
long as you are participating to : monitoring input, questioning,
suggesting, convincing others, writing I-Ds for the IETF, and making
up your decisions.

Todd>The IETF process of today is based on a 'consensus' process from
a membership of zero. That in and of itself flies in the face of
reason and ethical clarity. If there were formal members who came
together in a framework that the IETF administered it would be OK but
the process today is too easily abused.

AB> it is greate that we are not memebrs, we are participants, because
we become equal to any other, if memebrship then we will have a memebr
for 10 years and a memeber for 5 years (not measuring efforts but
time), but with the IETF we are just participants, the value or
difference between us is only how much you participate and author I-Ds
or IETF RFCs. There MAY be abuse to the consensus process only if the
CHAIR does not consider the healthy discussion related. So we need
something to avoid this.

Todd> When the journey is completed the standard will automatically
issue... no IESG no IAB pain no extra administrative overhead for a
bunch of lifer type standards junkies... Just simple and clean access
to the standard process.

AB> standard process is greate as we have IESG and WG reviews, first
because the authors will have to discuss through many things with the
focused/expert IETF group, then secondly the IESG have a more general
review which includes many other affects of the I-D with other WGs in
IETF. Yes painful but healthy.

Best Regards
Abdussalam Baryun
++++++++++++++++
The mission of the Internet Engineering Task Force is to make the
Internet work better by producing high-quality and relevant technical
documents that influence the way people design, use, and manage the
Internet. See http://www.ietf.org.

From despres.remi@laposte.net  Wed Sep 26 01:28:07 2012
Return-Path: <despres.remi@laposte.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 C2C2721F881F for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 01:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.538
X-Spam-Level: 
X-Spam-Status: No, score=-1.538 tagged_above=-999 required=5 tests=[AWL=0.411,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJ3wu1m3HJb7 for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 01:28:07 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.22]) by ietfa.amsl.com (Postfix) with ESMTP id D69DB21F881D for <ietf@ietf.org>; Wed, 26 Sep 2012 01:28:06 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2317.sfr.fr (SMTP Server) with ESMTP id 5326A7000116; Wed, 26 Sep 2012 10:28:04 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2317.sfr.fr (SMTP Server) with ESMTP id AD74F7000078; Wed, 26 Sep 2012 10:28:03 +0200 (CEST)
X-SFR-UUID: 20120926082803710.AD74F7000078@msfrf2317.sfr.fr
Subject: Re: Failing to convince an IETF WG
Mime-Version: 1.0 (Apple Message framework v1084)
From: =?iso-8859-1?q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
In-Reply-To: <CADnDZ8-FCKnpVhVRjVnOSfr-iA9MSgvXuTJvHk4MUxhNKCnW2A@mail.gmail.com>
Date: Wed, 26 Sep 2012 10:28:03 +0200
Message-Id: <E64341DF-32E2-436C-A892-396BC2268B42@laposte.net>
References: <CADnDZ8-K71TT2UuufyTLy-vgTjnnNqxo3X-_xbeoFRRYK9mH1A@mail.gmail.com> <CADnDZ8-FCKnpVhVRjVnOSfr-iA9MSgvXuTJvHk4MUxhNKCnW2A@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
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, 26 Sep 2012 08:28:07 -0000

Le 2012-09-26 =E0 09:52, Abdussalam Baryun a =E9crit :

> Hi Dave, and All,
>=20
> The beauty of the IETF is that it includes all Internet USERS
> (i.e.people or organisations) around the world, no one should use it
> in their interest, it should progress in the Internet
> Society/Community interest following the *open* engineering knowledge
> and practice. Engineers in IETF cannot disagree covering their reason
> or reference they SHOULD be open. Comments in line below:
> =
--------------------------------------------------------------------------=
---------------------------
>>> The IETF needs total transparency and a way to process alternative
>>> standards
>>> so that it is not actively involved in anything dark and covert.
>>=20
>> That makes no sense ... something can't be an IETF standard if it =
doesn't
>> get created and adopted using The IETF's processes. The word =
'standard'
>> implies the approval of some organization/standards body. The =
independant
>> stream does allow publishing of alternatives to IETF Standards, but =
that
>> doesn't make tham alternative standards. For that some other =
recognized
>> group needs to declare it a standard and then it will be An XYZ Group
>> Standard, not an IETF Standard.
> =
--------------------------------------------------------------------------=
-------------------------
> I agree that the best practice is standards through WGs, because
> *knowledge* is the core reason for the GROUP, not *politics*. IMHO,
> the best practice is continue *open-discussions* with engineering and
> technical knowledge to give progress to WGs, but if some participants
> don't want to accept to discuss (by ignoring input) or don't want to
> listen to technical/research reasons in IETF documents or  in
> publications out IETF, how can the WG progress? Still thoes
> participant MAY continue disagree (without discussing why) when
> calling for group consensus, what will be the best practice?, will it
> be that the submitter has to stop even if his/her has better arguments
> in terms of engineering.
>=20
> Some may fail to convice an IETF WG just because some active
> participants reply that they think it is bad, without replying
> *reasonably* to discussions. When I read the IETF procedure, I see
> that it makes decisions at the *WG-consensus* (with no relation to
> discussions and arguments) which I think not enough for progress in
> the eyes of IETF mission statement.

Same concern.
Some participants have been seen to come up as opponents without having =
participated in previous debates.

> Suggest: that if any participant disagree in I-D adoption in a WG,
> then he/she take a DISCUSS position (similar to IESG memebrs process,
> cannot just disagree), which they MUST have to take and reply to
> messages including their good reasons for their positions (you don't
> reply this idea/I-D is BAD). Any participant (submitter or who
> disagrees with adoption) SHOULD have an engineering reference(s) for
> such input.

Support for this suggestion, adding that WG chairs should be clearly =
responsible for weighting arguments in their appreciation of rough =
consensus, in particular ignoring those that they find invalid.

Regards,
RD



>=20
> If I am mistaken please advise, because I need to discuss to
> understand, so we can help together make IETF better for the world
> users.
>=20
> Best Regards
> Abdussalam Baryun
> ++++++++++++++++
> The mission of the Internet Engineering Task Force is to make the
> Internet work better by producing high-quality and relevant technical
> documents that influence the way people design, use, and manage the
> Internet. See http://www.ietf.org.

From abdussalambaryun@gmail.com  Wed Sep 26 01:33:34 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF9E821F845C for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 01:33:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.22
X-Spam-Level: 
X-Spam-Status: No, score=-3.22 tagged_above=-999 required=5 tests=[AWL=-0.221,  BAYES_00=-2.599, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hAmKIpU0PgVP for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 01:33:34 -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 CFAF821F845B for <ietf@ietf.org>; Wed, 26 Sep 2012 01:33:33 -0700 (PDT)
Received: by vcbfl11 with SMTP id fl11so310890vcb.31 for <ietf@ietf.org>; Wed, 26 Sep 2012 01:33:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=9w5a+iEPj/SAOLUk+p3FPMe8Ty1OsxV3LIO6ZW0K8zc=; b=FOXB7/psD6910PeIeBGoK2HpQ0JPkFE4GsoG1FA47aZICR+w/7X2AOJXOFc0F7hswp cbEBjhpleofn9djMurpYnEq7Qvo+eoELjxBmWsrT0j7WMvoxIrvsaIDXcUkgHulguYnG pQGLY49WdNM95KEdK6RTcVpIc5XjYOg8J/wOY3ZGXlr23rUdlnhbsNtr8xAxDRuug2+f XlDCQydgKjc0DhS8N1V+yqyb+5FCeU1fmIHSfufsrQWhirdTx6eyx4J9O80nlZ/iAn9t VaTUsxSmgVrc0YegTwDyZaa2sEiMXeHxJnflT6z45ubT+mqnKubi+f4bgZfYBF/p/1cJ IK5w==
MIME-Version: 1.0
Received: by 10.220.154.17 with SMTP id m17mr10563016vcw.31.1348648413213; Wed, 26 Sep 2012 01:33:33 -0700 (PDT)
Received: by 10.220.2.83 with HTTP; Wed, 26 Sep 2012 01:33:33 -0700 (PDT)
In-Reply-To: <CADnDZ8_AeRwe0sDe1a-rCZyG6s0X-hNN7T-qHz0-Ay33C_OZvQ@mail.gmail.com>
References: <CADnDZ8_AeRwe0sDe1a-rCZyG6s0X-hNN7T-qHz0-Ay33C_OZvQ@mail.gmail.com>
Date: Wed, 26 Sep 2012 10:33:33 +0200
Message-ID: <CADnDZ8_C82yCKHKkXrAp05+jmq2TZXv5kefv80tnrNzNi2w0jg@mail.gmail.com>
Subject: Re: Is there: Discussions, Evaluations, Decisions, Acceptance, Progress?
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, 26 Sep 2012 08:33:34 -0000

I Suggest the following:

1) IF any participant disagree in I-D adoption in a WG or any other
decision, THEN, he/she takes a DISCUSS position.

2) Any participant with DISCUSS position related to a subject (he/she
refused)MUST have to take and reply to messages including their good
reasons for their positions, otherwise his/her disagreement has no
engineering value.

3) Any participant (submitter or who disagrees with adoption) SHOULD
have an engineering reference(s) for such input otherwise the Chair
MAY not accept his input in the meeting.

Best Regards
Abdussalam Baryun
++++++++++++++++
The mission of the Internet Engineering Task Force is to make the
Internet work better by producing high-quality and relevant technical
documents that influence the way people design, use, and manage the
Internet. See http://www.ietf.org.


On 8/24/12, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> Hi All,
>
> For any IETF WG discussion, we recommend reasons/references and equal
> recognistion for progress.
> For any IETF WG evaluation/review, we recommend two way discussions for
> progress.
> For any IETF WG decision, we recommend evaluation and then need rough
> consensus for progress.
> For any IESG decision, we recommend WG input and internet community input
> and their consensus.
>
> IMO, for any IETF-Participant's progress, he/she needs to know *why*
> through discussions/questions, and he/she should make *decisions* for
> the WG's I-Ds/RFCs with his/her community through rough consensus.
> Decisions are accepted by community only if they are discussed or they
> have clear reasons.
>
> Please advise if you agree/disagree, thanks,
>
> Best Regards
> AB
>

From stephen.farrell@cs.tcd.ie  Wed Sep 26 01:57:01 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73F9421F8792 for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 01:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.901
X-Spam-Level: 
X-Spam-Status: No, score=-102.901 tagged_above=-999 required=5 tests=[AWL=-1.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lq4W+ok6IgXI for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 01:56:57 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE3321F8610 for <ietf@ietf.org>; Wed, 26 Sep 2012 01:56:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id F0E42171484; Wed, 26 Sep 2012 09:56:54 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h=date :subject:from:x-mailer:message-id:content-type :content-transfer-encoding:mime-version:in-reply-to:references :received:received:x-virus-scanned; s=cs; t=1348649808; bh=HvoKB utRxI8CCG9AOGIpN4U/plRb2+cDOKD96lCg7aM=; b=IE1oqBRgqeiij7KFj94sS UfqhFrhd2NWQZIDj1w+cZNc06nFj1/cTpJ8GRXQb1q5egRBcHU3OL5jMzM+6y2CK EipRJPrGqDjBZRiqk0w2lg1047y4qRkCjiwbmAr4unspM/66KN2RZ1yC2aKMVM6v 6hfh7xS4zfa4UUJtsd/OkAlIa1FxquQ0JkNKNli27NeUoO4eKcg9UfwpUQxhReA3 0TH/rqSX+vX4jwGD2HMGTHpJ/e1SGT2QydoLqIKVVSZs/VJJ/9MBU37jXCsmp8AB FW4SQ1/rfMvkHZkyjig54t8hSxtzXvUShu2h6imxPGSCyVB8jv4HZe6s3cS5DKp4 A==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id USNFTRtZOBrE; Wed, 26 Sep 2012 09:56:48 +0100 (IST)
Received: from [10.87.48.6] (unknown [86.45.55.168]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 1C610171506; Wed, 26 Sep 2012 09:56:45 +0100 (IST)
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net> <506207EB.4040300@earthlink.net> <alpine.LRH.2.01.1209251825130.5707@egate.xpasc.com> <506265E0.1050800@earthlink.net>
In-Reply-To: <506265E0.1050800@earthlink.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <51A92AA7-26CD-4749-8717-155E65A5DCAA@cs.tcd.ie>
X-Mailer: iPhone Mail (9B206)
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Failing to convince an IETF WG
Date: Wed, 26 Sep 2012 09:55:35 +0100
To: tglassey <tglassey@earthlink.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: Wed, 26 Sep 2012 08:57:01 -0000

On 26 Sep 2012, at 03:18, tglassey <tglassey@earthlink.net> wrote:

> The issue is how to remove the political BS which clouds so many initiativ=
es.

Disagree that this is *the* issue. We also get technical BS and even stuff t=
hat's utterly incompressible if you can believe that,

S


From cabo@tzi.org  Wed Sep 26 02:01:57 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3940521F87AD for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 02:01:57 -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=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFQ9O8-tw0ME for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 02:01:56 -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 5590F21F8792 for <ietf@ietf.org>; Wed, 26 Sep 2012 02:01:55 -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.3/8.14.3) with ESMTP id q8Q91eCD002011; Wed, 26 Sep 2012 11:01:40 +0200 (CEST)
Received: from [192.168.217.105] (p54892CE7.dip.t-dialin.net [84.137.44.231]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 7C13E2DB; Wed, 26 Sep 2012 11:01:40 +0200 (CEST)
Subject: Re: Failing to convince an IETF WG
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <51A92AA7-26CD-4749-8717-155E65A5DCAA@cs.tcd.ie>
Date: Wed, 26 Sep 2012 11:01:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CBD3E35C-E82F-4123-B774-026571C8E478@tzi.org>
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net> <506207EB.4040300@earthlink.net> <alpine.LRH.2.01.1209251825130.5707@egate.xpasc.com> <506265E0.1050800@earthlink.net> <51A92AA7-26CD-4749-8717-155E65A5DCAA@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1498)
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, 26 Sep 2012 09:01:57 -0000

On Sep 26, 2012, at 10:55, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:

> stuff that's utterly incompressible

In the header compression WG (ROHC), we had that a lot.

(SCNR.  I'm not sure that this thread has any other but comedy value at =
this point, anyway.)

Gr=FC=DFe, Carsten


From abdussalambaryun@gmail.com  Wed Sep 26 02:11:16 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF98F21F8817; Wed, 26 Sep 2012 02:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level: 
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CuaUHqy4NOxg; Wed, 26 Sep 2012 02:11:16 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id C8EC321F87CF; Wed, 26 Sep 2012 02:11:15 -0700 (PDT)
Received: by vbbfc26 with SMTP id fc26so422453vbb.31 for <multiple recipients>; Wed, 26 Sep 2012 02:11:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lrhZSwGgDlAhowAg54/X/ckHbP3eAWTpJ5n4kGxRDJ0=; b=u3O2Aebqi+fQ8klMJp1OMgmYfv9y3kbhMFY0PJLjxnMNnVI5tpzYTdN9jcVJOPlw7u aP9rH03yovgveeco8UZYwJXwuUvfep2kK8z9gYjnUP35pX03DbLZUiCo8F0oQvtUr+vf a5CfhjObJ80Ha8e5GFzb2qdLTmGCN+W7oaJLFNejRIJa3Y3JBjdE9+sUKH28AzV/1Y6l +wR2aQqFLvz80Q9xC1swtUloABWZntAygvM0XdhgpaeL9r7qUySIqHs0ysvYtIoesLBa X6+V2f+LpCE6hjYvF+HSJmiKZXfgMMMEmMkljutVVl136aC498EPVXkfNTu0QA08TFX7 HgYw==
MIME-Version: 1.0
Received: by 10.52.70.72 with SMTP id k8mr8732131vdu.55.1348650668827; Wed, 26 Sep 2012 02:11:08 -0700 (PDT)
Received: by 10.220.2.83 with HTTP; Wed, 26 Sep 2012 02:11:08 -0700 (PDT)
In-Reply-To: <20120925144038.19851.49608.idtracker@ietfa.amsl.com>
References: <20120925144038.19851.49608.idtracker@ietfa.amsl.com>
Date: Wed, 26 Sep 2012 11:11:08 +0200
Message-ID: <CADnDZ88mbe9gyTvsuNt00FpOoqkppowq5_RfD=Z-GiK98ykD0A@mail.gmail.com>
Subject: Re: Last Call: <draft-leiba-extended-doc-shepherd-00.txt> (Document Shepherding Throughout a Document's Lifecycle) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "iesg@ietf.org" <iesg@ietf.org>
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: Wed, 26 Sep 2012 09:11:16 -0000

Dated: 26/09/2012                                      By: Abdussalam
Baryun (AB)
This is a reply to below request call.

Reviewer Related Comment: The General Area Individual input
++++++++++++++++++++++++++++++++++++++++++++

Overall the reviewer disagrees to accept the document only after
modifications mentioned below and with referencing discussions/surveys
if available. I will name the I-D as a reflection report, which is
helpful for organisations' progress. Comments below:

1) the Abstract and Title of the document should represent the real
purpose of the document, it is not understood from them that the
document is an opinion, or point of view, or two points of view, or is
this document argumental. Informational track document related to such
subject SHOULD include references to history and practices as the
author witnesses while his experience, as a reflection report.

2) How can an individual submitter make input to produce RFC relating
to the administrative work of IETF, this will be without community
agreement or consultant.

3) IF there was no consultant from community of the Internet by the
author, and the I-D concerns their process, THEN the I-D SHOULD
mention that clearly. IF there was a questionnair or survey done by
the author, THEN he/she should include in the I-D. IF no such survey
done, nor questionnair distributed to get feedback, THEN it SHUOLD be
stated that there was no survey, in addition to the above.

4) IF the document represents the authors views THEN the Absract of
the I-D SHOULD state clearly, that : "this document is only the
opinion of the author(s) and not the Community. IF not mentioned THEN
the author must show prove of such claims/understandings.

Best regards
AB

End of Reply
++++++++++++++++++++++++++++++++++++++++++++++++++++++

On 9/25/12, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Document Shepherding Throughout a Document's Lifecycle'
>   <draft-leiba-extended-doc-shepherd-00.txt> as Informational RFC
>
> The author is documenting his own opinion, and he is presenting that
> opinion to the community for consideration.  The author is not
> proposing any formal change, but he is interested in community
> comments.  Since this is the authors opinions, changes to the document
> based on received comments be at the author's discretion.  As a
> result, the finished document will not claim to reflect IETF community
> consensus.
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-10-23. 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
>
>    RFC 4858 talks about "Document Shepherding from Working Group Last
>    Call to Publication".  There's a significant part of a document's
>    life that happens before working group last call, starting, really,
>    at the time a working group begins discussing a version of the idea
>    that's been posted as an individual draft.  It seems reasonable and
>    helpful to begin shepherding when there's a call for adoption as a
>    working group document, and this document gives one Area Director's
>    view of how that extended shepherding function might work, and what
>    tasks might be involved throughout the document's lifecycle.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/ballot/
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

From stephen.farrell@cs.tcd.ie  Wed Sep 26 02:32:22 2012
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A76621F87C0 for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 02:32:22 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QbnlRaj28rGM for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 02:32:21 -0700 (PDT)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 8BD4821F8658 for <ietf@ietf.org>; Wed, 26 Sep 2012 02:32:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id D20A6171484; Wed, 26 Sep 2012 10:32:20 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h=date :subject:from:x-mailer:message-id:content-type :content-transfer-encoding:mime-version:in-reply-to:references :received:received:x-virus-scanned; s=cs; t=1348651940; bh=ilmkI HojptvhUXDkTfZ1BGJ1hZUML0OFGWZKdnCuV/A=; b=zUV2FAp4LzgpV77rjpkox gKKzK0gDIoV4zFZbUy7ojn3zAfAiYM3MVxpmmbuNPTi56D0pVhl7ygAh7Sbm4EMo 9FOirgZhTkpXL26BQmkqZob9f8vgsJ6NLzEi7YRujQ/rRmfmLUfC46tfBiRyV84/ UyxDc3Ke7vEurE7ngsUJwnrlZwbbLGm6iwIbv6VjeeXJ7Xl05lzKGIgoZ9U1LD9u U7aZV92vfr7qAW0EV9GFqwA0sDnjsxNN+yGWJK1+MwazOrbvjqkceTGGUMHynKeC 3mX/K8Nyj9eJ+QyUYcEXCcZydUpitE+tD79B1JAwmyRRvqgbWk5o3Q8MnUECWa1/ w==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id zDLJKa0nozV4; Wed, 26 Sep 2012 10:32:20 +0100 (IST)
Received: from [10.53.142.3] (mobileinternet4.o2.ie [62.40.32.14]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 3F289171477; Wed, 26 Sep 2012 10:32:18 +0100 (IST)
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net> <506207EB.4040300@earthlink.net> <alpine.LRH.2.01.1209251825130.5707@egate.xpasc.com> <506265E0.1050800@earthlink.net> <51A92AA7-26CD-4749-8717-155E65A5DCAA@cs.tcd.ie> <CBD3E35C-E82F-4123-B774-026571C8E478@tzi.org>
In-Reply-To: <CBD3E35C-E82F-4123-B774-026571C8E478@tzi.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <51643521-3E0C-4B37-B16E-75776043E501@cs.tcd.ie>
X-Mailer: iPhone Mail (9B206)
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Failing to convince an IETF WG
Date: Wed, 26 Sep 2012 10:31:01 +0100
To: Carsten Bormann <cabo@tzi.org>
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, 26 Sep 2012 09:32:22 -0000

On 26 Sep 2012, at 10:01, Carsten Bormann <cabo@tzi.org> wrote:

> On Sep 26, 2012, at 10:55, Stephen Farrell <stephen.farrell@cs.tcd.ie> wro=
te:
>=20
>> stuff that's utterly incompressible
>=20
> In the header compression WG (ROHC), we had that a lot.
>=20
> (SCNR.  I'm not sure that this thread has any other but comedy value at th=
is point, anyway.)
>=20

Oops - let's see if the phone spell checker gets incomprehensible right this=
 time:-)

S


> Gr=C3=BC=C3=9Fe, Carsten
>=20

From dromasca@avaya.com  Wed Sep 26 03:32:13 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E29521F87B3 for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 03:32:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.782
X-Spam-Level: 
X-Spam-Status: No, score=-102.782 tagged_above=-999 required=5 tests=[AWL=-0.183, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KUzg0mRLp+i3 for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 03:32:12 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id B5CDC21F8692 for <ietf@ietf.org>; Wed, 26 Sep 2012 03:32:12 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAI/YYlDGmAcF/2dsb2JhbAA/Br5YgQiCIAEBAQECARILEwo0CwUHBAIBCA0EBAEBCwYMBwQBBgFFCAEIAQEEARIIDA6HXQYLnG6dOosYJoUDYAOWfoRviieCaQ
X-IronPort-AV: E=Sophos;i="4.80,490,1344225600"; d="scan'208";a="28638424"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 26 Sep 2012 06:25:37 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 26 Sep 2012 06:24:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: FW: Last Call: <draft-leiba-extended-doc-shepherd-00.txt>(Document Shepherding Throughout a Document's Lifecycle) toInformational RFC
Date: Wed, 26 Sep 2012 12:32:08 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04081AB5CA@307622ANEX5.global.avaya.com>
In-Reply-To: <CAC4RtVDoRy7C=62dsDqiTzM5JTNGZm9YiO1EGvS69Jhq57+cGg@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: FW: Last Call: <draft-leiba-extended-doc-shepherd-00.txt>(Document Shepherding Throughout a Document's Lifecycle) toInformational RFC
Thread-Index: Ac2bZgo+0TE6DdHeSoeCtatgteb4yAAaLseQ
References: <041e01cd9b51$cc632bc0$65298340$@olddog.co.uk> <CAC4RtVDoRy7C=62dsDqiTzM5JTNGZm9YiO1EGvS69Jhq57+cGg@mail.gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Barry Leiba" <barryleiba@computer.org>, <adrian@olddog.co.uk>
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, 26 Sep 2012 10:32:13 -0000

Hi Barry,

There is a disconnect between what the Last Call is asking and what you
really seem to be asking as a feedback.=20

The Last Call question is:=20

> The IESG has received a request from an individual submitter to
consider the following document:
- 'Document Shepherding Throughout a Document's Lifecycle'
  <draft-leiba-extended-doc-shepherd-00.txt> as Informational RFC

> The author is documenting his own opinion, and he is presenting that
opinion to the community for consideration.  The author is not proposing
any formal change, but he is interested in community comments.  Since
this is the authors opinions, changes to the document based on received
comments be at the author's discretion.  As a result, the finished
document will not claim to reflect IETF community consensus.

> The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-10-23. 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.

The document Abstract says:=20

>  It seems reasonable and
   helpful to begin shepherding when there's a call for adoption as a
   working group document, and this document gives one Area Director's
   view of how that extended shepherding function might work, and what
   tasks might be involved throughout the document's lifecycle.

I understand that you are interested in the community comments. However
the Last Call speaks also about an action - publication of this document
as an Informational RFC. This does not seem to be in synch with 'changes
to the document based on comments be at the authors discussion'.=20

So what are we really debating?=20

- the early shepherding proposal contained in the document? , or
- the action to approve this I-D as an Informational RFC as part of the
IETF stream despite the fact that its content may not reflect the IETF
consensus?=20

I do not see any procedure breach in the way this Last Call is
submitted, but there is something that is unusual in the IETF practice.
An AD-sponsored document can be submitted to the IESG approval without
the need of community consensus expressed in IETF Last Call. However, in
many cases the sheperding AD prefers to consult with the community and
sends the document to Last Call. It is assumed or at least understood
that the comments are being considered and if the community rejects the
document or part of it it will not be published at the author's
discretion'. This document seems to be different.=20

Regards,

Dan
=20

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of
> Barry Leiba
> Sent: Tuesday, September 25, 2012 11:38 PM
> To: adrian@olddog.co.uk
> Cc: ietf@ietf.org
> Subject: Re: FW: Last Call: <draft-leiba-extended-doc-shepherd-
> 00.txt>(Document Shepherding Throughout a Document's Lifecycle)
> toInformational RFC
>=20
> > I don't understand the process for this document.
> >
> > I read Russ's  words, but I don't glean the meaning :-(
>=20
> Think of it like the documents where we republish something from
another
> organization:
>=20
>    http://datatracker.ietf.org/doc/rfc6449/
>=20
> ....or publish something that describes how a product from a
particular
> company works:
>=20
>    http://datatracker.ietf.org/doc/rfc6281/
>
http://datatracker.ietf.org/doc/draft-claise-export-application-info-
> in-ipfix/
>=20
> > Why does that feel like Independent Stream to me?
>=20
> Russ thought that process-related stuff wasn't suitable for the
> Independent Stream.
>=20
> Barry

From glenzorn@gmail.com  Wed Sep 26 03:52:35 2012
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 9AEB121F87F2 for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 03:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.407
X-Spam-Level: 
X-Spam-Status: No, score=-3.407 tagged_above=-999 required=5 tests=[AWL=0.192,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IPjEpROKOpsr for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 03:52:35 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 36F0B21F87ED for <ietf@ietf.org>; Wed, 26 Sep 2012 03:52:35 -0700 (PDT)
Received: by pbbro8 with SMTP id ro8so1723181pbb.31 for <ietf@ietf.org>; Wed, 26 Sep 2012 03:52:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=eplSjGUctr6egzEol8cLnKwgoc6O6/EMcvhkzUQrnS4=; b=lm2rtdA2h6paPOw3sFKc/4rTJVFlKIldCLQiR91sTioZ1xJkHHsRgqbcllwFIspP+X mRRjapDdVVohSkoXBdGhEVeAbmQqevNAxtmJS59jnIFACkROSetPY5UuFPn+6mpB/Kf0 ldx9KdrUsBHjAmYxs6+LycSWclXlQst6KBYNqZ+m3v1EiWBsfRehkcMIvpQy6In8sZSM IeS+qefAe7kc8U7hAW9hewur21zjkPJV28tJDxpaWgV/3dG984M0YnxMEZWSsFmefQ9N +Bg8ZINExLbqm8qx0PHxzJncmRoP4OSbW9KWSsc35xVWTLgqXLaFUSs17lseWrp+zKiE vGcA==
Received: by 10.66.9.2 with SMTP id v2mr211994paa.65.1348656754974; Wed, 26 Sep 2012 03:52:34 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-120-218-82.revip2.asianet.co.th. [124.120.218.82]) by mx.google.com with ESMTPS id nx5sm1888209pbb.49.2012.09.26.03.52.32 (version=SSLv3 cipher=OTHER); Wed, 26 Sep 2012 03:52:34 -0700 (PDT)
Message-ID: <5062DE6E.3080507@gmail.com>
Date: Wed, 26 Sep 2012 17:52:30 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120830 Thunderbird/15.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Failing to convince an IETF WG
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net> <506207EB.4040300@earthlink.net> <alpine.LRH.2.01.1209251825130.5707@egate.xpasc.com> <506265E0.1050800@earthlink.net> <51A92AA7-26CD-4749-8717-155E65A5DCAA@cs.tcd.ie> <CBD3E35C-E82F-4123-B774-026571C8E478@tzi.org>
In-Reply-To: <CBD3E35C-E82F-4123-B774-026571C8E478@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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, 26 Sep 2012 10:52:35 -0000

On 09/26/2012 04:01 PM, Carsten Bormann wrote:

> On Sep 26, 2012, at 10:55,  Stephen Farrell
 > <stephen.farrell@cs.tcd.ie> wrote:
 >
 >> stuff that's utterly incompressible
 >
 > In the header compression WG (ROHC), we had that a lot.
 >
 > (SCNR.

Signal to Clutter plus Noise Ratio?

> I'm not sure that this thread  has any other but comedy value at this
 > point, anyway.)
 >
 > Grüße, Carsten
 >



From simon.perreault@viagenie.ca  Wed Sep 26 05:50:34 2012
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6532921F883C for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 05:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y0yf2nEnORPC for <ietf@ietfa.amsl.com>; Wed, 26 Sep 2012 05:50:32 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA5E21F883A for <ietf@ietf.org>; Wed, 26 Sep 2012 05:50:32 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:c98e:5abc:db27:bf25]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 38EC1414A3 for <ietf@ietf.org>; Wed, 26 Sep 2012 08:50:31 -0400 (EDT)
Message-ID: <5062FA16.7040009@viagenie.ca>
Date: Wed, 26 Sep 2012 08:50:30 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120828 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Failing to convince an IETF WG
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net> <506207EB.4040300@earthlink.net> <alpine.LRH.2.01.1209251825130.5707@egate.xpasc.com> <506265E0.1050800@earthlink.net> <51A92AA7-26CD-4749-8717-155E65A5DCAA@cs.tcd.ie> <CBD3E35C-E82F-4123-B774-026571C8E478@tzi.org> <51643521-3E0C-4B37-B16E-75776043E501@cs.tcd.ie>
In-Reply-To: <51643521-3E0C-4B37-B16E-75776043E501@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Sep 2012 12:50:34 -0000

Le 2012-09-26 05:31, Stephen Farrell a Ã©crit :
>>> stuff that's utterly incompressible
>
> Oops - let's see if the phone spell checker gets incomprehensible right this time:-)

I understood "incompressible" as equivalent to "pure random noise", and 
it made sense! :)

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

From housley@vigilsec.com  Thu Sep 27 08:26:36 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7310D21F85AD for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 08:26:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MCHm1GLO-sXS for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 08:26:36 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id CA35E21F85A3 for <ietf@ietf.org>; Thu, 27 Sep 2012 08:26:35 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id B4A099A4007 for <ietf@ietf.org>; Thu, 27 Sep 2012 11:26:39 -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 QcXt6ISCp-Po for <ietf@ietf.org>; Thu, 27 Sep 2012 11:26:28 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 887CF9A4002 for <ietf@ietf.org>; Thu, 27 Sep 2012 11:26:34 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20120927150522.9680.50930.idtracker@ietfa.amsl.com>
Date: Thu, 27 Sep 2012 11:26:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com>
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Sep 2012 15:26:36 -0000

I agree that this sentence needs changed.  However, I think that one =
other sentence should be updated while we are dealing with the IAOC in =
this document.

RFC 3777 says:

   Member Recall: This is the process by which the behavior of a sitting
      member of the IESG or IAB may be questioned, perhaps resulting in
      the removal of the sitting member.

The community should also be able to recall an IAOC member.

Russ


On Sep 27, 2012, at 11:05 AM, The IESG wrote:

>=20
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'Update to RFC 3777 to Clarify Nominating Committee Eligibility of =
IETF
>   Leadership'
>  <draft-leiba-3777upd-eligibility-04.txt> as Best Current Practice
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-10-25. 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
> This document updates RFC 3777 by adding the IAOC to the list of
> bodies whose sitting members are ineligible to serve on the Nominating
> Committee (NomCom).  This document also clarifies that "sitting
> members" includes those in ex-officio positions; however, liaisons
> from other bodies are not excluded from serving on NomCom.
>=20
> This document reflects the way that the IETF has been working.  By
> making this update to RFC 3777, the documentation of the formal
> process is catching up to the way that NomCom is actually operated.
> This document actually updates a single sentence in RFC 3777.
>=20
> Abstract
>=20
>   RFC 3777 specifies that "sitting members" of the IAB and IESG "may
>   not volunteer to serve on the nominating commitee".  Since that
>   document was written the IAOC was formed, and that body is not
>   covered by RFC 3777.  There is also uncertainty about whether ex-
>   officio members and liaisons are included as "sitting members".  =
This
>   document updates RFC 3777 and clarifies those situations.
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility/ballot/
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20


From dhc@dcrocker.net  Thu Sep 27 09:19:24 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F94B21F8534 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 09:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.521
X-Spam-Level: 
X-Spam-Status: No, score=-6.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtbNmpMhsQbV for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 09:19:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AAB8E21F85A0 for <ietf@ietf.org>; Thu, 27 Sep 2012 09:19:23 -0700 (PDT)
Received: from [192.168.1.8] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8RGJL4o010215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 27 Sep 2012 09:19:22 -0700
Message-ID: <50647C77.5070805@dcrocker.net>
Date: Thu, 27 Sep 2012 09:19:03 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com> <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com>
In-Reply-To: <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@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]); Thu, 27 Sep 2012 09:19:22 -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: Thu, 27 Sep 2012 16:19:24 -0000

On 9/27/2012 8:26 AM, Russ Housley wrote:
> I agree that this sentence needs changed.  However, I think that one other sentence should be updated while we are dealing with the IAOC in this document.
>
> RFC 3777 says:
>
>     Member Recall: This is the process by which the behavior of a sitting
>        member of the IESG or IAB may be questioned, perhaps resulting in
>        the removal of the sitting member.
>
> The community should also be able to recall an IAOC member.


That alters the scope of the draft abit.  Hence the title of the draft 
would now need to be something like:

    Update to RFC 3777 to Clarify Aspects of Eligibility and Recall

As for the earlier discussion seeking to exclude paid staff, I think it 
odd to have criteria that would permit /any/ paid staff to sit on 
Nomcom.  We pay for a number of folk 'staff' folk to show up and IETF 
meetings and none of them should qualify for Nomcom, IMO.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From housley@vigilsec.com  Thu Sep 27 10:57:44 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED10321F861B for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 10:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id psmlsaYINfNj for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 10:57:44 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 346E521F85C6 for <ietf@ietf.org>; Thu, 27 Sep 2012 10:57:44 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 8ACE29A4007; Thu, 27 Sep 2012 13:58:00 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id JuQtvu4NAS0b; Thu, 27 Sep 2012 13:57:32 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C17719A4002; Thu, 27 Sep 2012 13:57:57 -0400 (EDT)
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <50647C77.5070805@dcrocker.net>
Date: Thu, 27 Sep 2012 13:57:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2D914B6-C0CD-4228-A7CA-5EA72CFF67E0@vigilsec.com>
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com> <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com> <50647C77.5070805@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
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, 27 Sep 2012 17:57:45 -0000

Dave:

>> I agree that this sentence needs changed.  However, I think that one =
other sentence should be updated while we are dealing with the IAOC in =
this document.
>>=20
>> RFC 3777 says:
>>=20
>>    Member Recall: This is the process by which the behavior of a =
sitting
>>       member of the IESG or IAB may be questioned, perhaps resulting =
in
>>       the removal of the sitting member.
>>=20
>> The community should also be able to recall an IAOC member.
>=20
>=20
> That alters the scope of the draft abit.  Hence the title of the draft =
would now need to be something like:
>=20
>   Update to RFC 3777 to Clarify Aspects of Eligibility and Recall
>=20
> As for the earlier discussion seeking to exclude paid staff, I think =
it odd to have criteria that would permit /any/ paid staff to sit on =
Nomcom.  We pay for a number of folk 'staff' folk to show up and IETF =
meetings and none of them should qualify for Nomcom, IMO.

Two things ...

(1) Yes, if my suggestion is accepted, updating two sentences (instead =
of just one) to include the IAOC does change the scope of the document, =
and the title should reflect the proper scope.

(2) Looking at the history (https://www.ietf.org/nomcom/committee.html), =
it does not seem that there has been an issue of 'staff' seeking NomCom =
spots.  Prior to IETF Last Call, a previous version of this document was =
discussed on this mail list and on the ietf-nomcom mailing list. It was =
also discussed by a design team made up of ex-NomCom Chairs,  My sense =
of those discussions is to exclude as few people as necessary to avoid a =
self-selecting leadership, and the current document reflects that =
perspective.

Russ=

From tglassey@earthlink.net  Thu Sep 27 11:16:15 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F44A21F8569 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:16:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.652
X-Spam-Level: 
X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5 tests=[AWL=-0.053, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Wf9RuquyidC for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:16:14 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6F021F855A for <ietf@ietf.org>; Thu, 27 Sep 2012 11:16:14 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=LC0CNZL79KU6+PurSryee3xPLnv9bSPbAOYd4vo/hYtAVst5Ud4bgHvVf9oBKaKU; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1THIdB-0003El-6L; Thu, 27 Sep 2012 14:16:13 -0400
Message-ID: <506497EA.5000004@earthlink.net>
Date: Thu, 27 Sep 2012 11:16:10 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Failing to convince an IETF WG
References: <CADnDZ89gwKbJKZDyMxBaqVJiPa2hVqwvvQ-Ay28ZmtM7xq7ipg@mail.gmail.com> <6.2.5.6.2.20120925090332.09e8dd40@resistor.net> <CADnDZ8_xw_dwDeg659vEEk0yYB1FWKSv9EaJiLtHsL7mNnxx8g@mail.gmail.com> <6.2.5.6.2.20120925103806.0989ff10@resistor.net> <506207EB.4040300@earthlink.net> <alpine.LRH.2.01.1209251825130.5707@egate.xpasc.com> <506265E0.1050800@earthlink.net> <51A92AA7-26CD-4749-8717-155E65A5DCAA@cs.tcd.ie>
In-Reply-To: <51A92AA7-26CD-4749-8717-155E65A5DCAA@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7942eb1675eb426188bde28bfd58c5ece2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
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, 27 Sep 2012 18:16:15 -0000

On 9/26/2012 1:55 AM, Stephen Farrell wrote:
>
> On 26 Sep 2012, at 03:18, tglassey <tglassey@earthlink.net> wrote:
>
>> The issue is how to remove the political BS which clouds so many initiatives.
> Disagree that this is *the* issue. We also get technical BS and even stuff that's utterly incompressible if you can believe that,
We (none of us as technologists) have any business in politics. Further 
the IETF is not a PAC and you dont want that level of review here AFAIK.

If the IETF becomes a PAC then the whole world changes. This is why it 
is not acceptable for the IETF to prevent any standards process from 
completing or interfere with any process. Its necessary to be provably 
fair and open (right?)...

Todd
>
> S
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2441/5292 - Release Date: 09/25/12
>
>
>


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


From dcrocker@bbiw.net  Thu Sep 27 11:21:58 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6254821F866A for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.44
X-Spam-Level: 
X-Spam-Status: No, score=-6.44 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dutMulGs9S4J for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:21:57 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC9321F85AF for <ietf@ietf.org>; Thu, 27 Sep 2012 11:21:57 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8RILufS012103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 27 Sep 2012 11:21:57 -0700
Message-ID: <50649932.6050801@bbiw.net>
Date: Thu, 27 Sep 2012 11:21:38 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com> <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com> <50647C77.5070805@dcrocker.net> <E2D914B6-C0CD-4228-A7CA-5EA72CFF67E0@vigilsec.com>
In-Reply-To: <E2D914B6-C0CD-4228-A7CA-5EA72CFF67E0@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]); Thu, 27 Sep 2012 11:21:57 -0700 (PDT)
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, 27 Sep 2012 18:21:58 -0000

On 9/27/2012 10:57 AM, Russ Housley wrote:
>> As for the earlier discussion seeking to exclude paid staff, I
>> think it odd to have criteria that would permit /any/ paid staff to
>> sit on Nomcom.  We pay for a number of folk 'staff' folk to show up
>> and IETF meetings and none of them should qualify for Nomcom, IMO.
...
> (2) Looking at the history
> (https://www.ietf.org/nomcom/committee.html), it does not seem that
> there has been an issue of 'staff' seeking NomCom spots.  Prior to
> IETF Last Call, a previous version of this document was discussed on
> this mail list and on the ietf-nomcom mailing list. It was also
> discussed by a design team made up of ex-NomCom Chairs,  My sense of
> those discussions is to exclude as few people as necessary to avoid a
> self-selecting leadership, and the current document reflects that
> perspective.


So, to provide a specific example, you would be OK with having someone 
from AMS on Nomcom?

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From tglassey@earthlink.net  Thu Sep 27 11:26:05 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1E421F8613 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level: 
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=-0.051, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h+XmK4U4ZV23 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:26:03 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id D98C621F8611 for <ietf@ietf.org>; Thu, 27 Sep 2012 11:26:02 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=YNs7nRF3qGGx3wWSBAQD2cto5Um1GJJC3z7DapEC7N/jnFvfdiDO1RWdwBBWP5z3; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1THImg-0007Bx-9S for ietf@ietf.org; Thu, 27 Sep 2012 14:26:02 -0400
Message-ID: <50649A37.8040405@earthlink.net>
Date: Thu, 27 Sep 2012 11:25:59 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <CADnDZ88fjz0vXkNkGOMpa+0BHbESt_aEz4Smz1-h9CjrOsrUDw@mail.gmail.com>
In-Reply-To: <CADnDZ88fjz0vXkNkGOMpa+0BHbESt_aEz4Smz1-h9CjrOsrUDw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070000000507070101020807"
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7931b758467503bd33ec92132f4c8781cf350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Sep 2012 18:26:05 -0000

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

On 9/25/2012 9:03 AM, Abdussalam Baryun wrote:
>
> Hi Dave,
>
> >Independent Stream authors well might not be "part of" the IETF -- always a strange line of 
> thinking, given that the IETF doesn't have members -- but that doesn't 
> mean that the Stream itself is outside the IETF.
> Any I-D author MUST be part of IETF otherwise what is IETF then, how 
> do we define it? I think we should not make simple facts complicated. 
> The most important part of IETF is the participant that does volunteer 
> his work effort and time for the IETF. However I assume you agree with 
> me because you mentioned "might".
> AB
No sir - the IETF is a GSO meaning it must be transparent. Otherwise it 
is a simple fraternal organization and it should not be allowed to stand 
as a GSO because of its refusal to be open and transparent.

As to the need for an open standards process as an alternative 
method...  everything you cite above is the reason that is so necessary.

Todd Glassey
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 2012.0.2221 / Virus Database: 2441/5291 - Release Date: 09/25/12
>


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


--------------070000000507070101020807
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 9/25/2012 9:03 AM, Abdussalam Baryun
      wrote:<br>
    </div>
    <blockquote
cite="mid:CADnDZ88fjz0vXkNkGOMpa+0BHbESt_aEz4Smz1-h9CjrOsrUDw@mail.gmail.com"
      type="cite">
      <p><tt><font face="Times New Roman" size="3">
            Hi Dave,</font></tt></p>
      <tt>
        <div style="margin:0cm 0cm 10pt" class="MsoNormal"><span
            style="line-height:115%;font-family:&quot;Courier
            New&quot;;font-size:10pt"></span>&nbsp;</div>
        <div style="margin:0cm 0cm 10pt" class="MsoNormal">
          <span style="line-height:115%;font-family:&quot;Courier
            New&quot;;font-size:10pt">&gt;Independent Stream authors
            well might not be
            "part of" the IETF -- always a strange line of </span><span
            style="line-height:115%;font-family:&quot;Courier
            New&quot;;font-size:10pt">thinking, given that
            the IETF doesn't have members -- but that doesn't mean that
            the Stream itself
            is outside the IETF.</span></div>
        <div><font face="Times New Roman" size="3">
            Any I-D&nbsp;author MUST be part of IETF otherwise what is IETF
            then, how do we define it? I think we should not make simple
            facts&nbsp;complicated. The most important part of IETF is the
            participant that does volunteer his work effort and time for
            the IETF. However I assume you agree with me because you
            mentioned "might".</font></div>
        <div>&nbsp;</div>
        <div><font face="Times New Roman" size="3">AB</font></div>
      </tt></blockquote>
    No sir - the IETF is a GSO meaning it must be transparent. Otherwise
    it is a simple fraternal organization and it should not be allowed
    to stand as a GSO because of its refusal to be open and transparent.
    <br>
    <br>
    As to the need for an open standards process as an alternative
    method...&nbsp; everything you cite above is the reason that is so
    necessary.<br>
    <br>
    Todd Glassey<br>
    <blockquote
cite="mid:CADnDZ88fjz0vXkNkGOMpa+0BHbESt_aEz4Smz1-h9CjrOsrUDw@mail.gmail.com"
      type="cite">
      <p class="" avgcert""="" color="#000000" align="left">No virus
        found in this message.<br>
        Checked by AVG - <a moz-do-not-send="true"
          href="http://www.avg.com">www.avg.com</a><br>
        Version: 2012.0.2221 / Virus Database: 2441/5291 - Release Date:
        09/25/12</p>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
//Confidential Mailing - Please destroy this if you are not the intended recipient. </pre>
  </body>
</html>

--------------070000000507070101020807--

From ted.ietf@gmail.com  Thu Sep 27 11:41:24 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FAC821F8658 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ynQggny3rCx for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:41:23 -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 6FABB21F8671 for <ietf@ietf.org>; Thu, 27 Sep 2012 11:41:23 -0700 (PDT)
Received: by vcbfl11 with SMTP id fl11so2588687vcb.31 for <ietf@ietf.org>; Thu, 27 Sep 2012 11:41:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BKqG+d08O/gUAZMHR3q80c58fmTO0pWLqyeBMLr8ITA=; b=JHnkJofVNsh3OJKmH9BZxKEWKOp9T6B6Zzu+WcD3GKk+iTI6UD/6CNk2I8GpAuQL2r 1utErkTOYKNXtJjbhmutdxtA+cz2zF0BoBsuTC3B7yoAGNDF7VpgMXQ3aiqck1gaMM32 1VROpl5fMA2DTDVvp4lTlrAe9bdAsSHcYP1ZbeNk1zQkp4xnoSYB6QlohoD+sWADkkP/ yu/tqAklxjLMezbsT+YhlIRnd0DKokkMEH5wK0uW9oVT0ot04K/uJ0jSyb8mGJwjA0lp IafPWAo43jACxorwsr++th8pc/3D3A1xmZELTuvOKVszt+i+58sT6xJwBl7tqUYBrlK6 z/3Q==
MIME-Version: 1.0
Received: by 10.220.238.148 with SMTP id ks20mr2727679vcb.5.1348771282598; Thu, 27 Sep 2012 11:41:22 -0700 (PDT)
Received: by 10.58.245.39 with HTTP; Thu, 27 Sep 2012 11:41:22 -0700 (PDT)
In-Reply-To: <50649932.6050801@bbiw.net>
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com> <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com> <50647C77.5070805@dcrocker.net> <E2D914B6-C0CD-4228-A7CA-5EA72CFF67E0@vigilsec.com> <50649932.6050801@bbiw.net>
Date: Thu, 27 Sep 2012 11:41:22 -0700
Message-ID: <CA+9kkMDVOevcpzejaMsj5+Y=j9j7-XGW6W1PBTxJiGdqOG4UEw@mail.gmail.com>
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
From: Ted Hardie <ted.ietf@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Sep 2012 18:41:24 -0000

On Thu, Sep 27, 2012 at 11:21 AM, Dave Crocker <dcrocker@bbiw.net> wrote:

>
> So, to provide a specific example, you would be OK with having someone from
> AMS on Nomcom?
>
>
> d/
>

If they met the NomCom eligibility requirements by being a _registered
attendee_ for the requisite number of meetings, then yes.  After all,
they operate an organization that uses some of the protocols we
develop and might have technical input into working groups related to
the web, or authorization, or messaging; in those cases they might
well choose to attend and participate as individual technical
contributors.  If they attend only as staff, then I don't think the
situation is the same, and perhaps we need to clarify 3777 to say that
the confirmation of attendance include a confirmation of registration
(though I have always assumed this was included in the confirmation of
eligibility).

As you may recall, when Neustar provided this service we had other
folks from Neustar who remained technical contributors (and held IETF
leadership positions).  I honestly don't recall if any of them served
on the NomCom as well, but a blanket prohibition on Neustar folks
serving would have seemed wrong to me at that point.

regards,

Ted Hardie

From adrian@olddog.co.uk  Thu Sep 27 12:07:23 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE74721F8685 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 12:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Level: 
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[AWL=0.231,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DVSoRQb3hZyp for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 12:07:23 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id D1F2221F8682 for <ietf@ietf.org>; Thu, 27 Sep 2012 12:07:22 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q8RJ7Lwd016907;  Thu, 27 Sep 2012 20:07:21 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q8RJ7KHP016901 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 27 Sep 2012 20:07:21 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: RE: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
Date: Thu, 27 Sep 2012 20:07:18 +0100
Message-ID: <080e01cd9ce3$50ec8700$f2c59500$@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: Ac2c400aDr7f6lUKQwuv7W83Mp9qQA==
Content-Language: en-gb
Cc: draft-leiba-3777upd-eligibility.all@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: Thu, 27 Sep 2012 19:07:23 -0000

I have participated in the discussions leading to this version of the
document, and support its publication as an RFC. However, I have two
small editorial proposals and two typos that I would like to see 
polished.

Thanks,
Adrian

---

Section 1

   RFC 3777 specifies that "sitting members" of the IAB and IESG "may
   not volunteer to serve on the nominating committee".  Since that
   document was written the IETF Administrative Oversight Committee
   (IAOC) was formed, and that body is not covered by RFC 3777.

The point here is not just the formation of the IAOC, it is the fact
that NomCom appoints people to the IAOC that is important. Can you
add this fact with the appropriate reference to the instructions to
NomCom for selecting IAOC members.

---

Section 2

There is a punctuation and ambiguity issue :-(
1. As punctuated looks like the exclusion is people who are
   simultaneously ISOC trustees and on the IAB, IESG, and IAOC!
2. It is not clear what bodies people might be serving in ex-officio
   positions.

Sometimes more is less. Suggest...

OLD
   15.  Members of the Internet Society Board of Trustees and sitting
   members of the IAB, the IESG, and the IAOC, including members in ex-
   officio positions, may not volunteer to serve as voting members of
   the nominating committee.  Liaisons to these bodies from other bodies
   or organizations are not excluded by this rule.
NEW
   15.  Any person who serves on any of the Internet Society Board of 
   Trustees, the IAB, the IESG, or the IAOC, including those who serve 
   on these bodies in ex-officio positions, may not volunteer to serve
   as voting members of the nominating committee.  Liaisons to these 
   bodies from other bodies or organizations are not excluded by this
   rule.
END

---

Section 1
   That said, it would be bad to eliminate people who have the
   experience necessary to understand of the IETF process:
s/of the/the/

---

Section 1
s/fulfill the roles/fill the roles/


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 27 September 2012 16:05
> To: IETF-Announce
> Subject: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC
3777 to
> Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current
> Practice
> 
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF
>    Leadership'
>   <draft-leiba-3777upd-eligibility-04.txt> as Best Current Practice


From barryleiba@gmail.com  Thu Sep 27 12:10:53 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B77521F869E for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 12:10:53 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pscdd0-Yq8Ql for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 12:10:52 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id C484A21F8665 for <ietf@ietf.org>; Thu, 27 Sep 2012 12:10:52 -0700 (PDT)
Received: by iec9 with SMTP id 9so6121015iec.31 for <ietf@ietf.org>; Thu, 27 Sep 2012 12:10:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:x-rim-org-msg-ref-id:message-id:reply-to:x-priority :sensitivity:importance:subject:to:cc:from:date:content-type :mime-version; bh=z28qCE4OweR0OO4OdqkffnTSLto33/7aTvGlU50ETCY=; b=D61tXEs1Ghv3X2tYe5HZS3ks5VLfhURY6X4ZfvEqRGQNC1tEIPVaWSeI6b1GdpQqWm IVJ007k0ov61lcpB2wxTE+KYKX7h0/k4wKNubfnWeo4QqWoYlNbh09e6WluoS6D3dHGH qD3MTaRN7fwFzpOSz8jls2NrYlc+5BWDyneZzmu654HhhPFBvzgA0pjSve1j8xh+0vm9 46VxKJ4TcCUt27jKC8ER4oYB2qI5Xo9WbcUTrZuGgc9wbD50wB9SRPEgLVb3DjK40QlG G13htqDBz72lttOosIiQ+LeJs0j7Lsg6hCLoSL40zGDClzaLRkJr3KX7MZFxcFAnEr4Y hKyg==
Received: by 10.50.41.129 with SMTP id f1mr15057000igl.57.1348773052470; Thu, 27 Sep 2012 12:10:52 -0700 (PDT)
Received: from 172.29.197.213 (bda-74-82-80-74.bis6.us.blackberry.com. [74.82.80.74]) by mx.google.com with ESMTPS id gz10sm5951308igc.9.2012.09.27.12.10.51 (version=SSLv3 cipher=OTHER); Thu, 27 Sep 2012 12:10:51 -0700 (PDT)
Sender: Barry Leiba <barryleiba@gmail.com>
X-rim-org-msg-ref-id: 160210623
Message-ID: <160210623-1348773049-cardhu_decombobulator_blackberry.rim.net-371686848-@b5.c4.bise6.blackberry>
X-Priority: Normal
Sensitivity: Normal
Importance: Normal
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
To: "Adrian Farrel" <adrian@olddog.co.uk>,ietf@ietf.org
From: "Barry Leiba" <barryleiba@computer.org>
Date: Thu, 27 Sep 2012 19:10:53 +0000
Content-Type: text/plain
MIME-Version: 1.0
Cc: draft-leiba-3777upd-eligibility.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: barryleiba@computer.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, 27 Sep 2012 19:10:53 -0000

Good on both points; I will change both.

Barry


From barryleiba.mailing.lists@gmail.com  Thu Sep 27 17:38:38 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED08321F8441 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 17:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.067
X-Spam-Level: 
X-Spam-Status: No, score=-103.067 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tUQKHghLMFd8 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 17:38:38 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 11A3F21F8442 for <ietf@ietf.org>; Thu, 27 Sep 2012 17:38:37 -0700 (PDT)
Received: by bkcjc3 with SMTP id jc3so2739607bkc.31 for <ietf@ietf.org>; Thu, 27 Sep 2012 17:38:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PTUFvgNGvfKvW2UPPHgcPuO30RrHMF46mdGkSQbceIs=; b=m/BiyhddwnDGnUyMnA9gRzcb6QLfulMQCetoiAB6aPZ4cyPpLto1IXXVr+HFALFwPq iVDiciA+C6T69x+QNyLK/0t8I2Rvlvl44MoRjFA9H1SBVmk+gfM0JmbHNfzk5JmTnVPA zQkSZ8TX2DrEtJvONXey3StgDpZwt0JSQJYWh5Ymz3WSMnHhm9LYAUIyGkcYUkSBAfz3 sK4B2np3Ay3djR5l0CeBlgKnA/SjMcMXzpKV0GY+i2GjgPdc8QgQZwszuhvQzF7XKZ2r w0fuOOhGuMWQvWlyFDYjqH0kXrt+xi/cySdPkRYErzQqTL6RgbHreEeRZi4I+1do90+y 68ew==
MIME-Version: 1.0
Received: by 10.152.48.111 with SMTP id k15mr4632122lan.17.1348792716808; Thu, 27 Sep 2012 17:38:36 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.91.33 with HTTP; Thu, 27 Sep 2012 17:38:36 -0700 (PDT)
In-Reply-To: <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com>
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com> <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com>
Date: Thu, 27 Sep 2012 20:38:36 -0400
X-Google-Sender-Auth: KPdSSDDCwKjmGHTH7vv2pk_0lCM
Message-ID: <CAC4RtVA4xNndP=ok7DzoZJRz14Ox8q7yCh57wwcUoS6QGHpf1Q@mail.gmail.com>
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
From: Barry Leiba <barryleiba@computer.org>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Sep 2012 00:38:39 -0000

> RFC 3777 says:
>
>    Member Recall: This is the process by which the behavior of a sitting
>       member of the IESG or IAB may be questioned, perhaps resulting in
>       the removal of the sitting member.
>
> The community should also be able to recall an IAOC member.

As Dave says, that alters the scope of the document:
The version that SM and I worked on jointly *did* include more changes
related to the IAOC (and it still didn't try to touch recall).  But
you asked that we trim it back to my original proposal to keep it
simple, and to avoid a lot of involved discussion.  If we add the
recall bit, there's a lot more that we'd really have to add, and I
don't think we want to do that.  It's not clear at all that we simply
want to lump the IAOC recall process in with the others.

For example, all IAB and IESG members are appointed by NomCom, while
only two IAOC members are; do we want the recall process to apply to
all IAOC members, or only the NomCom-appointed ones?  Maybe it should
be all, or maybe only the body that appointed them should be able to
remove them.  Whichever we decide, it's not just a simple matter of
adding another sentence into the draft.

I recommend that we don't go there in this document, and address that
issue in a more comprehensive update later.

Barry

From narten@us.ibm.com  Thu Sep 27 21:53:09 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C79321F8495 for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 21:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.216
X-Spam-Level: 
X-Spam-Status: No, score=-110.216 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-WcPKWO39OV for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 21:53:08 -0700 (PDT)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4D821F84C2 for <ietf@ietf.org>; Thu, 27 Sep 2012 21:53:07 -0700 (PDT)
Received: from /spool/local by e32.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, 27 Sep 2012 22:53:06 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 27 Sep 2012 22:53:05 -0600
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id D60373E40040 for <ietf@ietf.org>; Thu, 27 Sep 2012 22:53:02 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q8S4r4Uu256998 for <ietf@ietf.org>; Thu, 27 Sep 2012 22:53:04 -0600
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q8S4sdAD007844 for <ietf@ietf.org>; Thu, 27 Sep 2012 22:54:39 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q8S4sdOY007790 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 27 Sep 2012 22:54:39 -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 q8S4r3Md021769 for <ietf@ietf.org>; Fri, 28 Sep 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q8S4r2ju021745 for ietf@ietf.org; Fri, 28 Sep 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201209280453.q8S4r2ju021745@rotala.raleigh.ibm.com>
Date: Fri, 28 Sep 2012 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12092804-5406-0000-0000-000000A6A675
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Sep 2012 04:53:09 -0000

Total of 96 messages in the last 7 days.
 
script run at: Fri Sep 28 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.38% |    9 | 10.56% |    72567 | housley@vigilsec.com
  8.33% |    8 |  9.91% |    68084 | abdussalambaryun@gmail.com
  8.33% |    8 |  9.01% |    61930 | tglassey@earthlink.net
  6.25% |    6 |  6.35% |    43627 | john-ietf@jck.com
  6.25% |    6 |  6.29% |    43206 | sm@resistor.net
  5.21% |    5 |  5.01% |    34408 | glenzorn@gmail.com
  5.21% |    5 |  4.94% |    33934 | dhc@dcrocker.net
  4.17% |    4 |  3.94% |    27041 | presnick@qualcomm.com
  3.12% |    3 |  3.14% |    21602 | touch@isi.edu
  3.12% |    3 |  2.96% |    20326 | adrian@olddog.co.uk
  3.12% |    3 |  2.63% |    18078 | barryleiba@computer.org
  3.12% |    3 |  2.63% |    18055 | ben@estacado.net
  2.08% |    2 |  2.09% |    14351 | stpeter@stpeter.im
  2.08% |    2 |  1.84% |    12671 | stephen.farrell@cs.tcd.ie
  2.08% |    2 |  1.72% |    11832 | henning.schulzrinne@fcc.gov
  2.08% |    2 |  1.69% |    11614 | cabo@tzi.org
  2.08% |    2 |  1.62% |    11144 | dcrocker@bbiw.net
  2.08% |    2 |  1.52% |    10474 | dwm@xpasc.com
  2.08% |    2 |  1.42% |     9726 | paul.hoffman@vpnc.org
  2.08% |    2 |  1.32% |     9088 | jnc@mercury.lcs.mit.edu
  1.04% |    1 |  2.18% |    14990 | martin.stiemerling@neclab.eu
  1.04% |    1 |  2.14% |    14728 | haibin.song@huawei.com
  1.04% |    1 |  1.88% |    12887 | ron.even.tlv@gmail.com
  1.04% |    1 |  1.34% |     9172 | dromasca@avaya.com
  1.04% |    1 |  1.25% |     8590 | despres.remi@laposte.net
  1.04% |    1 |  1.09% |     7480 | chair@ietf.org
  1.04% |    1 |  1.04% |     7174 | narten@us.ibm.com
  1.04% |    1 |  1.03% |     7110 | stewe@stewe.org
  1.04% |    1 |  0.97% |     6665 | brian.e.carpenter@gmail.com
  1.04% |    1 |  0.95% |     6560 | ted.ietf@gmail.com
  1.04% |    1 |  0.91% |     6284 | ned+ietf@mauve.mrochek.com
  1.04% |    1 |  0.84% |     5787 | warren@kumari.net
  1.04% |    1 |  0.83% |     5695 | framefritti@gmail.com
  1.04% |    1 |  0.81% |     5552 | ben@nostrum.com
  1.04% |    1 |  0.78% |     5391 | simon.perreault@viagenie.ca
  1.04% |    1 |  0.71% |     4880 | julian.reschke@gmx.de
  1.04% |    1 |  0.63% |     4336 | jari.arkko@piuha.net
--------+------+--------+----------+------------------------
100.00% |   96 |100.00% |   687039 | Total


From vesely@tana.it  Fri Sep 28 00:22:19 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5FE21F8588 for <ietf@ietfa.amsl.com>; Fri, 28 Sep 2012 00:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.669
X-Spam-Level: 
X-Spam-Status: No, score=-4.669 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYmsNEFaXvbw for <ietf@ietfa.amsl.com>; Fri, 28 Sep 2012 00:22:18 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 7498721F8578 for <ietf@ietf.org>; Fri, 28 Sep 2012 00:22:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1348816936; bh=SSurzS+bfSCRtye38DwnWup5M5DwnVX+mdU3HmrLxEM=; l=2932; h=Message-ID:Date:From:MIME-Version:To:CC:References:In-Reply-To: Content-Transfer-Encoding; b=HMtjksUuoJSlNBr0c6bnBkPKQq+Gxv/oOFgDMwAQrZwrdCmixfxLx2TbFvCIO53/o PqmJRMlNTr4WTYof4ekoeHpYO1tGAUBGelzC/2PBiAD8+cryEbXTWpNULMGdOsV6IA OKQSmT9DTQXHnDTO8cta4RBjmYS5WUB/vWoeYTLg=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Fri, 28 Sep 2012 09:22:16 +0200 id 00000000005DC035.0000000050655028.00000EB2
Message-ID: <50655027.8010200@tana.it>
Date: Fri, 28 Sep 2012 09:22:15 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: "ietf" <ietf@ietf.org>
Subject: In person vs remote participation to meetings
References: <70D4276B-762C-4917-B0C9-53398A98D55E@isoc.org>
In-Reply-To: <70D4276B-762C-4917-B0C9-53398A98D55E@isoc.org>
X-Forwarded-Message-Id: <70D4276B-762C-4917-B0C9-53398A98D55E@isoc.org>
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: Fri, 28 Sep 2012 07:22:19 -0000

Dear IETF,

I'm happy that Meetecho is gradually improving our remote
participation experience.  However, as a matter of fact, that is still
not quite the same thing as in person participation.

Question:  Consider a WG which is really in need of a face to face
meeting.  A very important participant, such as the editor of the main
WG document, however, would only participate remotely, because he is
an independent consultant and lacks specific funds.  Can the WG --in
such case-- set up some arrangements, e.g. take a collection up from
the other participants, or anything to a similar effect?  Are there
provisions or limitations?

IMHO, participation of individuals and small businesses is not less
important than that of newcomers from emerging and developing economies.

TIA for any hint.
Ale

-------- Original Message --------
From: Steve Conte <conte@isoc.org>
Date: Tue, 18 Sep 2012 13:34:02 -0700
To: Alessandro Vesely <vesely@tana.it>
Cc: Leaders@InternetSociety.org, Public Software Mailing List
<pubsoft@elists.isoc.org>
Subject: Re: The Internet Society Fellowship to the IETF

Dear Mr. Vesely,

Thank you for your email regarding the ISOC Fellowship to the IETF
Programme.  This specific programme is designed to increase IETF
participation from emerging and developing economies.

The IETF has tools in which to participate remotely.  We encourage
those who are not able to physically attend an IETF meeting to utilize
those tools so as to remain active in their participation.

Sincerely,

Steve Conte

On Sep 5, 2012, at 4:38 AM, Alessandro Vesely <vesely@tana.it> wrote:

> Dear ISOC,
> one of the points for qualifying for the programme is:
> 
>   Originate from and reside in a emerging or developing economy,
>   which traditionally have low rates of participation in the IETF.
>                          http://www.internetsociety.org/node/9476
> 
> I understand the intent and the limits of the programme, but I also
> notice that the IETF "works for those who pay its members."[1]  That
> fact may imply unwanted consequences, as far as free development (free
> as in "free speech") of open standards is concerned.  Do you address
> such topic on the ISOC web site?
> 
> For example, I know the case of a guy who is the editor of a standard
> specification within a IETF working group, but doesn't participate to
> IETF meetings because he has no funds for that.  He is an US citizen,
> hence does not qualify for the programme because of the point quoted
> above.  Indeed, that situation is quite frequent for small companies
> and individuals.  Wouldn't it be possible to widen the participation,
> for the sake of a democratic development of the Internet?
> 
> Thanks for your attention
> Sincerely
> AV
> 
> [1] JFC Morfin - Mon Sep 3 16:20:27 PDT 2012
> [PubSoft] OpenStand and "modern" paradigms
> https://elists.isoc.org/mailman/private/pubsoft/2012-September/002307.html







From joelja@bogus.com  Fri Sep 28 01:25:46 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD7E821F84C5 for <ietf@ietfa.amsl.com>; Fri, 28 Sep 2012 01:25: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZZU3zqGtMtbZ for <ietf@ietfa.amsl.com>; Fri, 28 Sep 2012 01:25:46 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0E21821F84C2 for <ietf@ietf.org>; Fri, 28 Sep 2012 01:25:46 -0700 (PDT)
Received: from unknown-70-56-81-c1-ee-37.lan (ip56572456.direct-adsl.nl [86.87.36.86]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q8S8Pgch081545 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 28 Sep 2012 08:25:44 GMT (envelope-from joelja@bogus.com)
Message-ID: <50655F00.3050101@bogus.com>
Date: Fri, 28 Sep 2012 01:25:36 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20120905 Thunderbird/16.0
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: In person vs remote participation to meetings
References: <70D4276B-762C-4917-B0C9-53398A98D55E@isoc.org> <50655027.8010200@tana.it>
In-Reply-To: <50655027.8010200@tana.it>
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]); Fri, 28 Sep 2012 08:25:44 +0000 (UTC)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Sep 2012 08:25:47 -0000

There are abundant examples of successful document editors and authors 
and the occasional area director working at a distance, some cases are 
harder than others.

The part that is hard to replace is, the opportunity for collegiality,  
for cross pollination, and many fine lunches  and dinners.

Working group participants are free to do what they want of course.

On 9/28/12 12:22 AM, Alessandro Vesely wrote:
> Dear IETF,
>
> I'm happy that Meetecho is gradually improving our remote
> participation experience.  However, as a matter of fact, that is still
> not quite the same thing as in person participation.
>
> Question:  Consider a WG which is really in need of a face to face
> meeting.  A very important participant, such as the editor of the main
> WG document, however, would only participate remotely, because he is
> an independent consultant and lacks specific funds.  Can the WG --in
> such case-- set up some arrangements, e.g. take a collection up from
> the other participants, or anything to a similar effect?  Are there
> provisions or limitations?
>
> IMHO, participation of individuals and small businesses is not less
> important than that of newcomers from emerging and developing economies.
>
> TIA for any hint.
> Ale
>
> -------- Original Message --------
> From: Steve Conte <conte@isoc.org>
> Date: Tue, 18 Sep 2012 13:34:02 -0700
> To: Alessandro Vesely <vesely@tana.it>
> Cc: Leaders@InternetSociety.org, Public Software Mailing List
> <pubsoft@elists.isoc.org>
> Subject: Re: The Internet Society Fellowship to the IETF
>
> Dear Mr. Vesely,
>
> Thank you for your email regarding the ISOC Fellowship to the IETF
> Programme.  This specific programme is designed to increase IETF
> participation from emerging and developing economies.
>
> The IETF has tools in which to participate remotely.  We encourage
> those who are not able to physically attend an IETF meeting to utilize
> those tools so as to remain active in their participation.
>
> Sincerely,
>
> Steve Conte
>
> On Sep 5, 2012, at 4:38 AM, Alessandro Vesely <vesely@tana.it> wrote:
>
>> Dear ISOC,
>> one of the points for qualifying for the programme is:
>>
>>    Originate from and reside in a emerging or developing economy,
>>    which traditionally have low rates of participation in the IETF.
>>                           http://www.internetsociety.org/node/9476
>>
>> I understand the intent and the limits of the programme, but I also
>> notice that the IETF "works for those who pay its members."[1]  That
>> fact may imply unwanted consequences, as far as free development (free
>> as in "free speech") of open standards is concerned.  Do you address
>> such topic on the ISOC web site?
>>
>> For example, I know the case of a guy who is the editor of a standard
>> specification within a IETF working group, but doesn't participate to
>> IETF meetings because he has no funds for that.  He is an US citizen,
>> hence does not qualify for the programme because of the point quoted
>> above.  Indeed, that situation is quite frequent for small companies
>> and individuals.  Wouldn't it be possible to widen the participation,
>> for the sake of a democratic development of the Internet?
>>
>> Thanks for your attention
>> Sincerely
>> AV
>>
>> [1] JFC Morfin - Mon Sep 3 16:20:27 PDT 2012
>> [PubSoft] OpenStand and "modern" paradigms
>> https://elists.isoc.org/mailman/private/pubsoft/2012-September/002307.html
>
>
>
>
>


From john@jlc.net  Fri Sep 28 04:26:32 2012
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DACC121F85D5 for <ietf@ietfa.amsl.com>; Fri, 28 Sep 2012 04:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.301
X-Spam-Level: 
X-Spam-Status: No, score=-106.301 tagged_above=-999 required=5 tests=[AWL=0.298, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SSnCLgltYH5k for <ietf@ietfa.amsl.com>; Fri, 28 Sep 2012 04:26:32 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id E9E3421F85C2 for <ietf@ietf.org>; Fri, 28 Sep 2012 04:26:31 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 4898F33C21; Fri, 28 Sep 2012 07:26:31 -0400 (EDT)
Date: Fri, 28 Sep 2012 07:26:31 -0400
From: John Leslie <john@jlc.net>
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: In person vs remote participation to meetings
Message-ID: <20120928112631.GK21618@verdi>
References: <70D4276B-762C-4917-B0C9-53398A98D55E@isoc.org> <50655027.8010200@tana.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50655027.8010200@tana.it>
User-Agent: Mutt/1.4.1i
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, 28 Sep 2012 11:26:33 -0000

Alessandro Vesely <vesely@tana.it> wrote:
> 
> I'm happy that Meetecho is gradually improving our remote
> participation experience.  However, as a matter of fact, that is
> still not quite the same thing as in person participation.

   Well said! (I'll get back to this...)

> Question:  Consider a WG which is really in need of a face to face
> meeting.  A very important participant, such as the editor of the main
> WG document, however, would only participate remotely, because he is
> an independent consultant and lacks specific funds.

   This is becoming more common.

   (Of course, Document Editor isn't a good example of the problem --
that role can _better_ be done without the distractions of an IETF
week.)

   But there are many interactions which _do_ work much better in
person. Fresh in mind is the mostly-failed interaction started by
Barry Leiba in apps-discuss@ietf.org over the interpretation of
RFC 3864:

http://www.ietf.org/mail-archive/web/apps-discuss/current/msg07374.html

   I remain amazed how much failure-to-communicate happened in that
thread! I think we reached the right outcome; but I'm still not sure
what John Klensin was trying to say. In-person, such exchanges tend
to resolve in three minutes, not three days...

   The good news is that we _have_ learned how to resolve these things
via email -- and many of us remain committed to doing so.

   The bad news is that there are _so_ many issues floating around
that a lot of them die out before they can be resolved via email.

   It's hard to blame Working Group Chairs that aim to resolve issues
during IETF weeks -- but the result is rather slow progress and the
effective exclusion of some of the folks best able to find actual
common ground (the Document Editors' job).

> Can the WG --in such case-- set up some arrangements, e.g. take a
> collection up from the other participants, or anything to a similar
> effect? Are there provisions or limitations?

   There really aren't any such provisions -- or for that matter
limitations -- for such actions. IMHO, such actions aren't likely
to succeed. Participation in an IETF week tends to be $5,000 cold
cash in addition to the value of one's time (which not all of us
_can_ afford to donate).

> IMHO, participation of individuals and small businesses is not less
> important than that of newcomers from emerging and developing economies.

   I agree (of course!) that experienced folks generally have more
to offer than newcomers. I believe that -- in principle -- most
participants would agree.

   Returning to the first item:
>
> I'm happy that Meetecho is gradually improving our remote
> participation experience.  However, as a matter of fact, that is
> still not quite the same thing as in person participation.

   The whole Internet is not-quite-the-same-thing as the world before
Internet!

   "Quite-the-same-thing" is definitely the wrong metric here:
Internet enables many things which we couldn't do Before-Internet.
Instead of trying to squeeze these things onto the laptop we carry
to IETF week, why not learn to squeeze the interactions onto the
Internet and interact from our offices where we have _all_ of our
tools available?

   Granted, employers are generally looking for a more immediate
payback when sponsoring folks to IETF weeks -- not something
where the goal isn't even visible yet. We already have efforts
in this direction in RTCWEB and CLUE WGs; but the goals remain
indistinct to most IETF participants.

   And, of course, we have Paul Hoffman's work (which you can
follow on the VMEET list) for improving remote participation.

   I am acutely embarrassed that I won't even be able to attend
Atlanta in person. But I find that my overall IETF-week experiences
are in some ways more productive "participating" remotely from my
office. Jabber can be an effective interaction tool; I can keep
multiple screens active; I'm not limited to cookies to keep my
energy level up; et cetera.

   I suggest active participation in VMEET:

https://www.ietf.org/mailman/listinfo/vmeet

for all the experienced folks who find themselves unable to attend
IETF weeks in person.

--
John Leslie <john@jlc.net>

From tglassey@earthlink.net  Fri Sep 28 07:03:00 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E772421F85C2 for <ietf@ietfa.amsl.com>; Fri, 28 Sep 2012 07:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.647
X-Spam-Level: 
X-Spam-Status: No, score=-2.647 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 634sxq-uDkBB for <ietf@ietfa.amsl.com>; Fri, 28 Sep 2012 07:03:00 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id E0D2421F859A for <ietf@ietf.org>; Fri, 28 Sep 2012 07:02:59 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=emCUMgWmMh9kqLNeQKSOdWfbtDA1RX0Rh0nxAY6eE51PI6GHLjkhv49uXycdV+W4; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.1.103]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1THb9f-0005rd-Bv for ietf@ietf.org; Fri, 28 Sep 2012 10:02:59 -0400
Message-ID: <5065AE11.70003@earthlink.net>
Date: Fri, 28 Sep 2012 07:02:57 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: In person vs remote participation to meetings
References: <70D4276B-762C-4917-B0C9-53398A98D55E@isoc.org> <50655027.8010200@tana.it> <50655F00.3050101@bogus.com>
In-Reply-To: <50655F00.3050101@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79501d460a11f224cc53ab3e118841f000350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Sep 2012 14:03:01 -0000

On 9/28/2012 1:25 AM, joel jaeggli wrote:
> There are abundant examples of successful document editors and authors 
> and the occasional area director working at a distance, some cases are 
> harder than others.
>
> The part that is hard to replace is, the opportunity for 
> collegiality,  for cross pollination, and many fine lunches  and dinners.
>
> Working group participants are free to do what they want of course.
The problem you cite here is actually a profound one. That work - the 
colligiality as you put it is lost in the process. None of the internal 
workings of those sessions unless they are formally recorded and made a 
permanent part of the standards record are really included today in the 
process. No cross correlation of any decisions made therein and in fact 
the problem is the IETF members seem to feel that the recording of how 
they get to where they get is not important. The problem is it is... 
very very important.

Todd
>
> On 9/28/12 12:22 AM, Alessandro Vesely wrote:
>> Dear IETF,
>>
>> I'm happy that Meetecho is gradually improving our remote
>> participation experience.  However, as a matter of fact, that is still
>> not quite the same thing as in person participation.
>>
>> Question:  Consider a WG which is really in need of a face to face
>> meeting.  A very important participant, such as the editor of the main
>> WG document, however, would only participate remotely, because he is
>> an independent consultant and lacks specific funds.  Can the WG --in
>> such case-- set up some arrangements, e.g. take a collection up from
>> the other participants, or anything to a similar effect?  Are there
>> provisions or limitations?
>>
>> IMHO, participation of individuals and small businesses is not less
>> important than that of newcomers from emerging and developing economies.
>>
>> TIA for any hint.
>> Ale
>>
>> -------- Original Message --------
>> From: Steve Conte <conte@isoc.org>
>> Date: Tue, 18 Sep 2012 13:34:02 -0700
>> To: Alessandro Vesely <vesely@tana.it>
>> Cc: Leaders@InternetSociety.org, Public Software Mailing List
>> <pubsoft@elists.isoc.org>
>> Subject: Re: The Internet Society Fellowship to the IETF
>>
>> Dear Mr. Vesely,
>>
>> Thank you for your email regarding the ISOC Fellowship to the IETF
>> Programme.  This specific programme is designed to increase IETF
>> participation from emerging and developing economies.
>>
>> The IETF has tools in which to participate remotely.  We encourage
>> those who are not able to physically attend an IETF meeting to utilize
>> those tools so as to remain active in their participation.
>>
>> Sincerely,
>>
>> Steve Conte
>>
>> On Sep 5, 2012, at 4:38 AM, Alessandro Vesely <vesely@tana.it> wrote:
>>
>>> Dear ISOC,
>>> one of the points for qualifying for the programme is:
>>>
>>>    Originate from and reside in a emerging or developing economy,
>>>    which traditionally have low rates of participation in the IETF.
>>> http://www.internetsociety.org/node/9476
>>>
>>> I understand the intent and the limits of the programme, but I also
>>> notice that the IETF "works for those who pay its members."[1]  That
>>> fact may imply unwanted consequences, as far as free development (free
>>> as in "free speech") of open standards is concerned.  Do you address
>>> such topic on the ISOC web site?
>>>
>>> For example, I know the case of a guy who is the editor of a standard
>>> specification within a IETF working group, but doesn't participate to
>>> IETF meetings because he has no funds for that.  He is an US citizen,
>>> hence does not qualify for the programme because of the point quoted
>>> above.  Indeed, that situation is quite frequent for small companies
>>> and individuals.  Wouldn't it be possible to widen the participation,
>>> for the sake of a democratic development of the Internet?
>>>
>>> Thanks for your attention
>>> Sincerely
>>> AV
>>>
>>> [1] JFC Morfin - Mon Sep 3 16:20:27 PDT 2012
>>> [PubSoft] OpenStand and "modern" paradigms
>>> https://elists.isoc.org/mailman/private/pubsoft/2012-September/002307.html 
>>>
>>
>>
>>
>>
>>
>
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2677 / Virus Database: 2591/5795 - Release Date: 09/27/12
>
>


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


From sm@resistor.net  Sat Sep 29 12:57:30 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB32021F865D; Sat, 29 Sep 2012 12:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yW2SpyrY73OF; Sat, 29 Sep 2012 12:57:29 -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 E084821F844A; Sat, 29 Sep 2012 12:57:29 -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 q8TJvNdM009854; Sat, 29 Sep 2012 12:57:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1348948648; bh=idDss6fIzDbNTpB0vQSTw1fRPaXPtbV5b5Ss2SSvcj0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=bqyLHCoI26iPa5tmqQ8J5B/R5Vo0PVB9m6WXCBeyPC2DT+QQeU2eT/nV4bDkq34Ne KIk8rNz6ekAzzSnpN1A56erfWODDlX5u/I/Q3A40KFU12zgjvkgW2P6Ecs1+E7Gvoc AnfIHXmq2rQluUYbuSiHlf4w/mvt17Kkw1SoDS/k=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1348948648; i=@resistor.net; bh=idDss6fIzDbNTpB0vQSTw1fRPaXPtbV5b5Ss2SSvcj0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2vcZuTcnLUZ946gWnTPRYZUpMPpfTw9zkrT0z3e26OvGSluCZ7uegcbrBU/f736H5 IM7pUTvj3usnXKPeDtbMTgZXR4I1ja14sLTmvsxB+Ri/mLhrdb0k2KkyxlNW93PGq9 /rlG2UYztz1cMdK///V/+NaETYpV9uOwb2XIiTdA=
Message-Id: <6.2.5.6.2.20120929102841.0abec208@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 29 Sep 2012 12:42:25 -0700
To: iab@iab.org
From: SM <sm@resistor.net>
Subject: Re: Call for Comment: <draft-iab-modern-paradigm-01.txt> (Affirmation of the Modern Paradigm for Standards) to Informational RFC
In-Reply-To: <FB8EC2B2-4B08-46A3-9529-893F46D4C5BF@iab.org>
References: <FB8EC2B2-4B08-46A3-9529-893F46D4C5BF@iab.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: Sat, 29 Sep 2012 19:57:31 -0000

At 10:08 29-09-2012, IAB Chair wrote:
>This is an IETF-wide Call for Comment on an=20
>Affirmation of the Modern Paradigm for Standards=9D.
>
>The document is being considered for publication=20
>as an Informational RFC within the IAB stream,=20
>and is available for inspection here:

It was previously mentioned as an individual=20
comment that "this document is not being=20
considered for publication as an RFC (at least=20
within the IAB stream), so RFC 4845 does not=20
apply".  The IETF Chair has stated that there is=20
rough consensus [1] for signing the=20
Affirmation.  The press releases [2][3][4] have=20
been issued.  If the modern paradigm was used as=20
a measure, there wasn't broad consensus to sign=20
the Affirmation.  What's the use of this IETF-wide Call?

The press release was a "fait accompli".  It=20
would have been awkward to raise a concern about=20
it.  This document could be qualified as=20
spineless.  The document only highlights that the=20
IAB has consulted the IETF community after the fact.

Several years ago the following [5] was put=20
forward as requirements that enable open standards (this is non-IETF=
 material):

  1. Open Meeting - all may participate in the standards development=
 process.

  2. Consensus - all interests are discussed and=20
agreement found, no domination.

  3. Due Process - balloting and an appeals=20
process may be used to find resolution.

  4. Open IPR - how holders of IPR related to the=20
standard make available their IPR.

  5. One World - same standard for the same capability, world-wide.

  6. Open Change - all changes are presented and=20
agreed in a forum supporting the
     five requirements above.

  7. Open Documents - committee drafts and=20
completed standards documents are easily
     available for implementation and use.

  8. Open Interface - supports proprietary advantage (implementation); each
     interface is not hidden or controlled=20
(implementation); each interface of the
     implementation supports migration (use).

  9. Open Access - objective conformance=20
mechanisms for implementation testing and
     user evaluation.

  10. On-going Support - standards are supported=20
until user interest ceases rather
      than when implementer interest declines.

It was mentioned that "some recognized SSOs=20
(e.g., ITU) and many consortia (e.g., W3C) have a=20
pay-to-become-a-member policy".  To be fair, it=20
can also be argued that the IETF has a pay policy=20
for meetings.  Surprisingly, the IETF does not=20
meet Requirement 2 as the "Area Directors have a=20
dictatorial level of control over the=20
standardization decisions in their area".  It is=20
interesting to note that there are different interpretations of "consensus".

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg74753.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg74758.html
3. http://www.w3.org/2012/08/openstand.html.en
4. http://standards.ieee.org/news/2012/openstand.html
5. Credits to Ken Krechmer =20


From bortzmeyer@nic.fr  Sun Sep 30 12:18:13 2012
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 116FA21F86CE for <ietf@ietfa.amsl.com>; Sun, 30 Sep 2012 12:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.186
X-Spam-Level: 
X-Spam-Status: No, score=-100.186 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id whvDQ2CY5Q8C for <ietf@ietfa.amsl.com>; Sun, 30 Sep 2012 12:18:12 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) by ietfa.amsl.com (Postfix) with ESMTP id 06C0821F86C4 for <ietf@ietf.org>; Sun, 30 Sep 2012 12:18:07 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 3BFEF3A899; Sun, 30 Sep 2012 19:18:06 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 2E8BB19071E; Sun, 30 Sep 2012 21:13:40 +0200 (CEST)
Date: Sun, 30 Sep 2012 21:13:40 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: IETF <ietf@ietf.org>
Subject: Re: Leading Global Standards Organizations Endorse 'OpenStand' Principles that Drive Innovation and Borderless Commerce
Message-ID: <20120930191340.GA12770@sources.org>
References: <E822CC92-68B6-491A-B445-E587455650C5@ietf.org> <20120829080639.GA15710@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120829080639.GA15710@nic.fr>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 6.0.5
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, 30 Sep 2012 19:18:13 -0000

On Wed, Aug 29, 2012 at 10:06:39AM +0200,
 Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote 
 a message of 31 lines which said:

> Unfortunately, the actual text is very short on this matter
> ("Standards specifications are made accessible to all for
> implementation and deployment") and does not mention gratis access
> and redistribution, one of the big reasons of the success of the
> TCP/IP family (RFC 5218, section 2.1.5). Was it because the IEEE
> would not sign otherwise
> <http://www.ieee.org/publications_standards/index.html>?

I owe IEEE an apology. They are actually very good for publishing data
on the Internet :-)

http://ieeelog.com/
http://www.zdnet.com/ieee-admits-password-leak-says-problem-fixed-7000004804/

I hope that passwords at datatracker.ietf.org are not in the log file
:-)
