
From duerst@it.aoyama.ac.jp  Mon Jul  2 04:07:11 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 721E021F8ADF for <ietf@ietfa.amsl.com>; Mon,  2 Jul 2012 04:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.565
X-Spam-Level: 
X-Spam-Status: No, score=-99.565 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kY+VM5k5XKos for <ietf@ietfa.amsl.com>; Mon,  2 Jul 2012 04:07:08 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id C325421F8A59 for <ietf@ietf.org>; Mon,  2 Jul 2012 04:07:07 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q62B7BX8031238 for <ietf@ietf.org>; Mon, 2 Jul 2012 20:07:11 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 5310_211e_125f969c_c436_11e1_b6f9_001d096c5782; Mon, 02 Jul 2012 20:07:10 +0900
Received: from [IPv6:::1] ([133.2.210.1]:47255) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15DAEAB> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 2 Jul 2012 20:07:11 +0900
Message-ID: <4FF180DC.3090003@it.aoyama.ac.jp>
Date: Mon, 02 Jul 2012 20:07:08 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <4FE4E19F.2050400@cs.tcd.ie> <4FE83EF5.1050000@it.aoyama.ac.jp> <4FE85424.9000409@cs.tcd.ie> <4FE998E9.9010809@it.aoyama.ac.jp> <4FE99C75.9010309@cs.tcd.ie>
In-Reply-To: <4FE99C75.9010309@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.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, 02 Jul 2012 11:07:11 -0000

Hello Stephen,

On 2012/06/26 20:26, Stephen Farrell wrote:
>
> Hi again Martin,
>
> On 06/26/2012 12:11 PM, "Martin J. DÃ¼rst" wrote:
>> So the question is really, what's the use case, and what's just a
>> consequence of that use case. If confirmation of already available
>> resources (e.g. like a fingerprint) is the (main?) use case, and the
>> greater weight on "speakability" just a design consequence, then it
>> makes sense to have two separate things.
>
> Yes, confirmation is the main current use-case for nih as I understand
> it and have said previously.

I sincerely wish you had said this so clearly much, much earlier, or 
even better that it had been in the draft in cristal clear language. We 
could have avoided a lot of useless discussion.

> (Of course the resource might not yet
> be present, so "already available" isn't quite right, but that's a
> nit.)
>
> Have we beaten this to death sufficiently now? I hope so;-)
>
> If you want to suggest a sentence that says that, feel free.

I really don't think it should be my job to explain this. There are 
enough coauthors on the draft who should be in a much better position 
than myself to write such text :-(.

Anyway, here is a try:

- In the abstract, replace "and binary and human "speakable" formats for 
these names" by ", a binary form, and a form for confirming the presence 
(or absence) of resources".

- In the introduction, replace "and a
    human-speakable text form that could be used, e.g. for reading out
    (parts of) the name over a voice connection." with
    "and a form optimized for confirming the presence (or absence) of
    resources by humans.".

- Change the title of Section 7 from "Human-speakable Format" to "Format 
for Resource Confirmation"

- Replace the first sentence at the start of Section 7 to say:
There is often a need for humans to confirm that a particular resource, 
e.g. a public key, is already present, or to discover its absence.

- Change "("speaking" the value of an ni URI)" to "confirm the presence 
or absence of a resource")

- Nuke the second paragraph of section 7 (the one that starts with "The 
justification for using a URI"). The stuff it says about IDNs, for 
example, isn't really appropriate for IETF standardization.

- In the example section, change "Human-speakable form of a name" to
"Form for resource confirmation" (three occurrences).


I'd also change the "nih:" scheme to something like "fingerprint:", and 
allow the insertion of delimiter characters (allowing e.g. 
nih:3;5326-9057-e12f-e2b7-4ba0-7c89-2560a2;f instead of 
nih:3;53269057e12fe2b74ba07c892560a2;f because the former should be much 
easier to manipulate by humans), but I guess I'd again be shot down for 
"proposing something like this at such a late date" (I note we are still 
in IETF Last Call).


Regards,   Martin.

From stephen.farrell@cs.tcd.ie  Mon Jul  2 04:26:49 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 12F9221F8C22 for <ietf@ietfa.amsl.com>; Mon,  2 Jul 2012 04:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djjRqOUD5CRD for <ietf@ietfa.amsl.com>; Mon,  2 Jul 2012 04:26: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 3A5D321F8B67 for <ietf@ietf.org>; Mon,  2 Jul 2012 04:26:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id F1709154214; Mon,  2 Jul 2012 12:26:43 +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=1341228403; bh=y604yZpiUMmxvd /7E2p0g+qsR7xB63Ss7q1IAR8fBJ4=; b=Nked7e7ybWL+2jnrmLu4MxnEFD7lzx eWFFFGsYd9JuAxvAkiXSPTwXdAlB/Wml9V7iEGOhXADo/PmQYCPWxNSIUpArUlAe u1tZ693nsTrdG9K0FXhmw/J1aGiFzXTDqNgzF5fjQq5h2HfiJuWE6ECbPamzm8SU dIq2ASGXRs19eG5jT6cRRk/Rw/BFCyLGAvY2kEiFFDpQ/j70gU+kkbp7eEKXNfoz UHvBTisC309KAdb5av603AapuAFBObqCg+MhSDR4AW397ZH993nH/kiSOVVpdmPo S0wPQZpaHopbe5auf2fZJfzsAo8dYkrCVYZjguV/FyWEqJk5N5GtwBtw==
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 11iNhEi7OhFy; Mon,  2 Jul 2012 12:26:43 +0100 (IST)
Received: from [10.3.10.185] (unknown [193.1.186.252]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 94907154213; Mon,  2 Jul 2012 12:26:41 +0100 (IST)
Message-ID: <4FF18572.2000905@cs.tcd.ie>
Date: Mon, 02 Jul 2012 12:26:42 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <4FE4E19F.2050400@cs.tcd.ie> <4FE83EF5.1050000@it.aoyama.ac.jp> <4FE85424.9000409@cs.tcd.ie> <4FE998E9.9010809@it.aoyama.ac.jp> <4FE99C75.9010309@cs.tcd.ie> <4FF180DC.3090003@it.aoyama.ac.jp>
In-Reply-To: <4FF180DC.3090003@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: Graham Klyne <GK@ninebynine.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, 02 Jul 2012 11:26:49 -0000

Hi Martin,

On 07/02/2012 12:07 PM, "Martin J. Dürst" wrote:
> Hello Stephen,
> 
> On 2012/06/26 20:26, Stephen Farrell wrote:
>>
>> Hi again Martin,
>>
>> On 06/26/2012 12:11 PM, "Martin J. Dürst" wrote:
>>> So the question is really, what's the use case, and what's just a
>>> consequence of that use case. If confirmation of already available
>>> resources (e.g. like a fingerprint) is the (main?) use case, and the
>>> greater weight on "speakability" just a design consequence, then it
>>> makes sense to have two separate things.
>>
>> Yes, confirmation is the main current use-case for nih as I understand
>> it and have said previously.
> 
> I sincerely wish you had said this so clearly much, much earlier, or
> even better that it had been in the draft in cristal clear language. We
> could have avoided a lot of useless discussion.

I agree this has been harder than it ought have been for some
reason. I guess that just happens sometimes.

> 
>> (Of course the resource might not yet
>> be present, so "already available" isn't quite right, but that's a
>> nit.)
>>
>> Have we beaten this to death sufficiently now? I hope so;-)
>>
>> If you want to suggest a sentence that says that, feel free.
> 
> I really don't think it should be my job to explain this. There are
> enough coauthors on the draft who should be in a much better position
> than myself to write such text :-(.

Well, you seemed motivated:-)

> Anyway, here is a try:
> 
> - In the abstract, replace "and binary and human "speakable" formats for
> these names" by ", a binary form, and a form for confirming the presence
> (or absence) of resources".
> 
> - In the introduction, replace "and a
>    human-speakable text form that could be used, e.g. for reading out
>    (parts of) the name over a voice connection." with
>    "and a form optimized for confirming the presence (or absence) of
>    resources by humans.".
> 
> - Change the title of Section 7 from "Human-speakable Format" to "Format
> for Resource Confirmation"
> 
> - Replace the first sentence at the start of Section 7 to say:
> There is often a need for humans to confirm that a particular resource,
> e.g. a public key, is already present, or to discover its absence.
> 
> - Change "("speaking" the value of an ni URI)" to "confirm the presence
> or absence of a resource")
> 
> - Nuke the second paragraph of section 7 (the one that starts with "The
> justification for using a URI"). The stuff it says about IDNs, for
> example, isn't really appropriate for IETF standardization.
> 
> - In the example section, change "Human-speakable form of a name" to
> "Form for resource confirmation" (three occurrences).

I could live with more-or-less all of that. Will check if coauthors
can similarly. I think "human-speakable" still needs to be mentioned
though, since that's why its designed as it is, but I like those
changes generally.

> I'd also change the "nih:" scheme to something like "fingerprint:", and
> allow the insertion of delimiter characters (allowing e.g.
> nih:3;5326-9057-e12f-e2b7-4ba0-7c89-2560a2;f instead of
> nih:3;53269057e12fe2b74ba07c892560a2;f because the former should be much
> easier to manipulate by humans), 

Would rather not change the uri scheme name at this point, unless
a load of people prefer it, but the idea of optional "-" delimiters
seems useful all right.

> but I guess I'd again be shot down for
> "proposing something like this at such a late date" (I note we are still
> in IETF Last Call).

Just:-) But improvements don't stop at the end of IETF LC and your
suggestions above are, I think, improvements.

Any other opinions before I go make changes along these lines?

Cheers,
S.

> 
> 
> Regards,   Martin.
> 
> 


From david.black@emc.com  Fri Jun 29 12:23:43 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 A2E6521F88A3; Fri, 29 Jun 2012 12:23:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n8KxSv8lk2DY; Fri, 29 Jun 2012 12:23:42 -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 6A42821F889A; Fri, 29 Jun 2012 12:23:42 -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 q5TJNYLU021288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Jun 2012 15:23:35 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 29 Jun 2012 15:23:17 -0400
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q5TJNHdw022925; Fri, 29 Jun 2012 15:23:17 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub34.corp.emc.com ([::1]) with mapi; Fri, 29 Jun 2012 15:23:16 -0400
From: <david.black@emc.com>
To: <dworley@avaya.com>, <alan.b.johnston@gmail.com>
Date: Fri, 29 Jun 2012 15:23:15 -0400
Subject: RE: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-11
Thread-Index: Ac1WK/SS5AOXm0ZpSfqMaQa/q754dwAAIaQQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208D3A9A0@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com> <CAKhHsXEzQ9hrsRpkUsAMa2xaNwt8E7QM4ZVadTmqyX7hg0XJ1Q@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A1D0C@DC-US1MBEX4.global.avaya.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, 02 Jul 2012 06:15:59 -0700
Cc: mohsen.soroush@sylantro.com, ietf@ietf.org, gen-art@ietf.org, bliss@ietf.org, vvenkatar@gmail.com, david.black@emc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 19:23:44 -0000

VGhhdCB3b3JrcyBmb3IgbWUsIFRoYW5rcywgLS1EYXZpZA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+IEZyb206IFdvcmxleSwgRGFsZSBSIChEYWxlKSBbbWFpbHRvOmR3b3JsZXlA
YXZheWEuY29tXQ0KPiBTZW50OiBGcmlkYXksIEp1bmUgMjksIDIwMTIgMzoxOCBQTQ0KPiBUbzog
YWxhbi5iLmpvaG5zdG9uQGdtYWlsLmNvbQ0KPiBDYzogQmxhY2ssIERhdmlkOyBtb2hzZW4uc29y
b3VzaEBzeWxhbnRyby5jb207IGlldGZAaWV0Zi5vcmc7IGdlbi0NCj4gYXJ0QGlldGYub3JnOyBi
bGlzc0BpZXRmLm9yZzsgdnZlbmthdGFyQGdtYWlsLmNvbQ0KPiBTdWJqZWN0OiBSZTogR2VuLUFS
VCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1ibGlzcy1zaGFyZWQtYXBwZWFyYW5jZXMtMTENCj4gDQo+
IE9uIFRodSwgMjAxMi0wNi0yOCBhdCAyMDowNSAtMDUwMCwgQWxhbiBKb2huc3RvbiB3cm90ZToN
Cj4gPiA+DQo+ID4gPiA0LjEgLSBSRVEtMTY6DQo+ID4gPg0KPiA+ID4gICBpbiB0aGlzIGNhc2Us
IHNlaXppbmcgdGhlIGxpbmUgaXMgdGhlIHNhbWUgdGhpbmcgYXMgZGlhbGluZy4NCj4gPiA+DQo+
ID4gPiBUaGF0IHNlZW1zIHdyb25nIC0gSSB3b3VsZCBoYXZlIHRob3VnaHQgaXQgd2FzIGEgInBy
ZXJlcXVpc2l0ZSIgYXMNCj4gPiA+IG9wcG9zZWQgdG8gInRoZSBzYW1lIHRoaW5nIiBiZWNhdXNl
IHNlaXppbmcgdGhlIGxpbmUgaXMgaW1tZWRpYXRlbHkNCj4gPiA+IGZvbGxvd2VkIGJ5IGEgZGlh
bGluZyByZXF1ZXN0Lg0KPiA+DQo+ID4NCj4gPiBUaGlzIHJlcXVpcmVtZW50IGlzIGFib3V0IHNl
bmRpbmcgb25lIHJlcXVlc3QgdGhhdCBjYXVzZXMgYm90aCBhY3Rpb25zDQo+ID4gdG8gb2NjdXIu
ICBJbiBhIFBTVE4gcmluZ2Rvd24gY2lyY3VpdCAoYSB2ZXJ5IHNwZWNpYWxpemVkIGNpcmN1aXQs
DQo+ID4gdXNlZCBmb3IgImhvdGxpbmVzIiksIHRoZSB0d28gb3BlcmF0aW9ucyBhcmUgdGhlIHNh
bWUgdGhpbmcuICBCZXNpZGVzDQo+ID4gdGhpcyBzdGF0ZW1lbnQsIGlzIFJFUS0xNiBpdHNlbGYg
bm90IGNsZWFyPyAgUGVyaGFwcyBJIHNob3VsZCBqdXN0DQo+ID4gcmVtb3ZlIHRoaXMgc3RhdGVt
ZW50IGlmIGl0IGFkZHMgY29uZnVzaW9uIHJhdGhlciB0aGFuIGNsYXJpdHkgdG8gdGhlDQo+ID4g
cmVxdWlyZW1lbnQuDQo+IA0KPiBJTUhPLCBhIGdvb2QgZml4IGlzOg0KPiANCj4gICAgUkVRLTE2
IFRoZSBtZWNoYW5pc20gc2hvdWxkIHN1cHBvcnQgYSB3YXkgZm9yIGEgVUEgdG8gc2VpemUgYQ0K
PiAgICBwYXJ0aWN1bGFyIGFwcGVhcmFuY2UgbnVtYmVyIGFuZCBhbHNvIHNlbmQgdGhlIHJlcXVl
c3QgYXQgdGhlIHNhbWUNCj4gICAgdGltZS4gIFRoaXMgaXMgbmVlZGVkIHdoZW4gYW4gYXV0b21h
dGljIHJpbmdkb3duIGZlYXR1cmUgKGEgdGVsZXBob25lDQo+ICAgIGNvbmZpZ3VyZWQgdG8gaW1t
ZWRpYXRlbHkgZGlhbCBhIHBob25lIG51bWJlciB3aGVuIGl0IGdvZXMgb2ZmIGhvb2spDQo+ICAg
IGlzIGNvbWJpbmVkIHdpdGggc2hhcmVkIGFwcGVhcmFuY2VzIC0gaW4gdGhpcyBjYXNlLCBzZWl6
aW5nIHRoZSBsaW5lDQo+ICAgIGlzID4+PmludGVncmF0ZWQgd2l0aDw8PCBkaWFsaW5nLg0KPiAN
Cj4gRGFsZQ0KDQo=

From masahiro@isl.rdc.toshiba.co.jp  Sun Jul  1 21:53:16 2012
Return-Path: <masahiro@isl.rdc.toshiba.co.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 381DC11E8140; Sun,  1 Jul 2012 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.23
X-Spam-Level: 
X-Spam-Status: No, score=-2.23 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iOvUR7ljhZtY; Sun,  1 Jul 2012 21:53:13 -0700 (PDT)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id B785721F875C; Sun,  1 Jul 2012 21:53:11 -0700 (PDT)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp  with ESMTP id q624rEw6029770; Mon, 2 Jul 2012 13:53:14 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp  id q624rEbw017329; Mon, 2 Jul 2012 13:53:14 +0900 (JST)
Received: from unknown [133.199.192.144]  by arc1.toshiba.co.jp with ESMTP id PAA17327; Mon, 2 Jul 2012 13:53:13 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp  with ESMTP id q624rDL8014376; Mon, 2 Jul 2012 13:53:13 +0900 (JST)
Received: from snazzy.isl.rdc.toshiba.co.jp by toshiba.co.jp id q624rDwY005629; Mon, 2 Jul 2012 13:53:13 +0900 (JST)
Received: from maltesein.wide.toshiba.co.jp (unknown [202.249.10.100]) by snazzy.isl.rdc.toshiba.co.jp (Postfix) with ESMTP id 1FD7D3FE67; Mon,  2 Jul 2012 22:09:22 +0900 (JST)
Received: from malteseout.wide.toshiba.co.jp (maltese.wide.toshiba.co.jp [202.249.10.99]) by maltesein.wide.toshiba.co.jp (8.13.8/8.9.1) with ESMTP id q624rDah011480; Mon, 2 Jul 2012 13:53:13 +0900
Received: from tsbgw.wide.toshiba.co.jp (tsbgw.wide.toshiba.co.jp [202.249.10.123]) by malteseout.wide.toshiba.co.jp (8.13.8/8.9.1) with ESMTP id q624rD8M031112; Mon, 2 Jul 2012 13:53:13 +0900
Received: from localhost (localhost [127.0.0.1]) by tsbgw.wide.toshiba.co.jp (Postfix) with ESMTP id 444532E3F3; Mon,  2 Jul 2012 13:53:13 +0900 (JST)
Received: from tsbgw.wide.toshiba.co.jp ([127.0.0.1]) by localhost (tsbgw.wide.toshiba.co.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2UjfmBMVzlf; Mon,  2 Jul 2012 13:53:13 +0900 (JST)
Received: from grayswandir.isl.rdc.toshiba.co.jp (localhost [127.0.0.1]) by tsbgw.wide.toshiba.co.jp (Postfix) with ESMTP id E43132E3F2; Mon,  2 Jul 2012 13:53:12 +0900 (JST)
Date: Mon, 02 Jul 2012 13:53:11 +0900
Message-ID: <yd962a6bw7c.wl@grayswandir.isl.rdc.toshiba.co.jp>
From: Masahiro =Rhythm Drive= Ishiyama <masahiro@isl.rdc.toshiba.co.jp>
To: hartmans-ietf@mit.edu
Subject: Re: [secdir] secdir review of draft-sakane-dhc-dhcpv6-kdc-option
In-Reply-To: <tsl7gus37hu.fsf@mit.edu>
References: <21762_1337814743_q4NNCMPh008981_alpine.BSF.2.00.1205231837020.9762@fledge.watson.org> <1337881837.3279.45.camel@destiny.pc.cs.cmu.edu> <004a01cd4562$b7b338e0$4001a8c0@gateway.2wire.net> <tsl7gus37hu.fsf@mit.edu>
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) LIMIT/1.14.10 (Furuichi) APEL/10.7 Emacs/22.3 (i386-apple-darwin10.2.0) MULE/5.0 (SAKAKI)
Organization: Toshiba Corp. R&D Center.
Sender: Masahiro =Rhythm Drive= Ishiyama <masahiro@isl.rdc.toshiba.co.jp>
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Dispatcher: imput version 20100215(IM150)
Lines: 37
X-Mailman-Approved-At: Mon, 02 Jul 2012 06:15:59 -0700
Cc: draft-sakane-dhc-dhcpv6-kdc-option@tools.ietf.org, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2012 04:53:16 -0000

	At first I thought that it might be good to leave section 4.1,
	but now I changed my mind. I think the order of the preference
	might depend on the running environment: some people prefer
	"secured" one, some people prefer DNS...  So I'd like to make
	the order configurable and move section 4.1 to appendix, as a
	hint for implementation.

masahiro

>>>>> On Wed, 27 Jun 2012 15:00:29 -0400, Sam Hartman <hartmans-ietf@mit.edu> said:
 > 
>>>>> "t" == t p <daedulus@btconnect.com> writes:
t> Just to make public what I have hinted at privately, I think that steps
t> in section 4.1 may be somewhat underspecified.
 > 
t> A related issue is that section 4.1 prefers DNS to DHCP for Kerberos
t> information but the Security Considerations stress the weakness of
t> DHCP and recommend authenticating DHCP.  What if DHCP is secure
t> and DNS is not?  Should DNS still be preferred?
 > 
 > Yes probably.
 > DNS has been and will continue to be the dominant way to discover KDCs.
 > I see this as a specialized DHCP option for certain deployments, not
 > something you'll see in the enterprise for desktops or laptops as an
 > example.
 > I mean some people may deploy it, but I suspect that you won't see it in
 > most situations where DNS works well today.
 > So, basically in all cases, including preconfigured DNS servers, I'd
 > expect DNS to be preferred.
 > 
 > Note that choosing the right KDC does impact availability--if you have
 > the wrong KDC it won't work.
 > In general though, choosing the wrong KDC does not compromise
 > authentication. It's a bit more complex than that, but KDC location has
 > not generally been considered  security sensitive.
 > 

From touch@isi.edu  Mon Jul  2 14:09: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 76C9A21F861E for <ietf@ietfa.amsl.com>; Mon,  2 Jul 2012 14:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.702
X-Spam-Level: 
X-Spam-Status: No, score=-105.702 tagged_above=-999 required=5 tests=[AWL=0.897, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K59ggr6GUQNV for <ietf@ietfa.amsl.com>; Mon,  2 Jul 2012 14:09:42 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id BBFE421F8608 for <ietf@ietf.org>; Mon,  2 Jul 2012 14:09:38 -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 q62L8ura024895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 2 Jul 2012 14:08:56 -0700 (PDT)
Message-ID: <4FF20DE7.2080208@isi.edu>
Date: Mon, 02 Jul 2012 14:08:55 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4FE2715C.2090601@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
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: Mon, 02 Jul 2012 21:09:42 -0000

Hi,

On 6/20/2012 5:57 PM, Masataka Ohta wrote:
> Though the ID states:
> 
>     This
>     document underscores the point that not only is reassembly (and
>     possibly subsequent fragmentation) required for translation, it can
>     be used to avoid issues with IPv4 ID uniqueness.
> 
> according to RFC2765, which does not need port numbers for
> address mapping:
> 
>     If the IPv6 packet contains a Fragment header the header fields are
>     set as above with the following exceptions:
> 
>           Identification:
>                   Copied from the low-order 16-bits in the
>                   Identification field in the Fragment header.
> 
>           Flags:
>                   The More Fragments flag is copied from the M flag in
>                   the Fragment header.  The Don't Fragments flag is set
>                   to zero allowing this packet to be fragmented by IPv4
>                   routers.
> 
> the translated IPv4 packets are not atomic with 16bit IDs.
> 
> Note that the RFC is referred by NAT646 etc.
> 
> Then, aren't IPv6 nodes are required to rate limit packets
> they generate with fragment headers assuming 16bit IDs?
> 
> Or, are 6 to 4 translators are required to rate limit and
> drop rate-violating packets to make the "stateless"
> translators full of states.

I would expect that the translator would be responsible for this, though
there is the problem that multiple translators interfere with each other.

Regardless, this is outside the scope of the ipv4-id-update doc.

> Or?
> 
> 						Masataka Ohta
> 
> PS
> 
> As the RFC specifies ID=0 when DF is set 0, it should also
> be updated to conform to the robustness principle.

That is an error in this RFC, which also is outside the scope of the
ipv4-id-update doc.

Joe


From abdussalambaryun@gmail.com  Tue Jul  3 04:24:11 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 E1C9621F87EC; Tue,  3 Jul 2012 04:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.468
X-Spam-Level: 
X-Spam-Status: No, score=-3.468 tagged_above=-999 required=5 tests=[AWL=0.131,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k26AMwQ85M6R; Tue,  3 Jul 2012 04:24:09 -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 7C82E21F86FA; Tue,  3 Jul 2012 04:24:09 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so4536036vbb.31 for <multiple recipients>; Tue, 03 Jul 2012 04:24: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:cc:content-type :content-transfer-encoding; bh=m083XjFfH0EUxb6vgYU8i6j1omQNdjqvt27IPivW5Zw=; b=viY/egFGImJapOLlKWhl2U8A9AZCkAsnivzuEd4XwMsHaetUOPqByiUS5wFyd1Aa6y WYTNEOsysgPtlZObZhf/mfdKkYFD4tMK3NlLjtkn4pajR/x+QnX91S878vxm/gLFj5x2 anhNohIFMhAj22KoSk5/EBodAa412wlJsEzzu+o6ZElkEcd6Vvs3dD6o1yb8JtGU+Oib ruoymrtB+W9Q6cwYvsrN+2vhE1uhGvpLu9rYYlSFAQlQcfCm5BL04797PKz3Cl9wvdSp YtsO06XsE2aDpIPH+i4m8jIKzPf2hc09o/unLkUEuaXI8khp46MFmdTGZ5iOQCAeDup8 27ZQ==
MIME-Version: 1.0
Received: by 10.52.100.4 with SMTP id eu4mr6531999vdb.66.1341314656627; Tue, 03 Jul 2012 04:24:16 -0700 (PDT)
Received: by 10.220.110.130 with HTTP; Tue, 3 Jul 2012 04:24:16 -0700 (PDT)
Date: Tue, 3 Jul 2012 13:24:16 +0200
Message-ID: <CADnDZ89NQS+tFVDsBjb_TZ2B-jL-o95Gx2HA5AbpRf2a8CstSg@mail.gmail.com>
Subject: Re: [manet] MANET Terminology Update
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: manet <manet@ietf.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: roll <roll@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, 03 Jul 2012 11:24:12 -0000

Dear All

I completed the first version of draft on terminology and submited the
draft yesterday (with getting some techniq problem), but needed to
post to know the community feedback and advise. There are other terms
that was not yet included which will need some advise from you.
Thanking you,

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Abbreviations Used in The submitted Document

   AH   Authentication Header
   DAD  Duplicate Address Detection
   DPD  Duplicate Packet Detection
   DoS  Denial of Service
   ESP  Encapsulating Security Payload
   IP   IPv4 or IPv6
   ICMP Internet Control Message Protocol
   IIB  Interface Information Base
   ETX  Estimated Expected number of Transmission
   FIB  Forwarding Information Base
   LQI  Link Quality Indicator
   L2   Data Link Layer (i.e. 2nd layer in ISO model)
   L3   Internet Layer (i.e. 3rd layer in ISO model)
   LLN  Low power and Lossy Network
   MAC  Mediam Access Control
   MIB  Management Information Base
   MTU  Maximum Transmission Unit
   NBMA Non-Broadcast Multi-Access link
   NHDP Neighborhood Discovery Protocol
   ND   IP Neighbor Discovery
   OSPF Open Shortest Path First
   RIB  Routing Information Base
   SMF  Simplified Multicast Forwarding
   TCP  Transmission Control Protocol
   UDP  User Datagram Protocol

2.3 Definitions for MANET Terms

2.3.1 Terms Definition of MANET Communication:

Communications=92 Technology or Facility:
   The means employed by two or more devices/subsystems to transfer
   and/or receive information between them in one way or two way
   communication.  MANET communications often uses the wireless
   transmission medium(s) and MAY use some wired mediums (e.g. free
   space, air, water, antenna, coaxial cables, etc.)

Communication Medium:
   The transceiver system (e.g. such as L2 systems, IEEE802.11 systems,
   satellite system, etc.) that the routing device uses to communicates
   through the transmission medium(s), by providing connectionless and/or
   connection services that MAY be established. The system medium
   includes MAC layer and MAY include the physical Layer.

Communication Channel:
A subdivision of the physical communication medium (i.e. radio carrier
signal bandwidth, or the system bandwidth) allowing possibly shared
independent uses of the medium. Channels may be made available by
subdividing the medium into; distinct time slots, distinct spectral
bands, or coding sequence, etc.

MANET Protocol:
The communication system/subsystem that operates and maintains the
ad hoc communication technology or facility within MANET. MANET routing
Protocols often apply distributed algorithms/techniques to disseminate
or forward routing messages within a MANET routing domain.

Topology:
An abstract representation of a network (physical or logical), as a
graph (G) whose topology is defined by a set of routers/bridges (V) that
communicate through set of links (E), where the G =3D (V, E).

Physical-level Topology:
A topology of the communication medium networks consists of routing
devices and physical links. This topology information is updated by
devices=92 technology in the L2 information Base.

Network-level Topology:
A topology of the communication system networks consists of routers and
links. This topology information is updated by routers in its RIB.

Multihop MANET:
A MANET that its node(s) MAY need(s) more than one IP hop to reach the
destination.

Reactive Routing:
An on-demand based routing protocol that operates route discover and
maintainance the route(s), to reach the demanded destination(s).

Proactive Routing:
A topology RIB based routing protocol that operates routes and maintains
the network topology, to reach its known destination(s). Each router
maintains routes to all reachable destinations at all times, whether or
not there is currently any demand to deliver packets to those
destinations.

Upper Layer:
a protocol layer above IP layer (e.g. as TCP, UDP, OSPF).

MANET Domain: TBD

MANET Signaling:
Sending and exchanging some MANET messages/information.

2.3.2 Terms Definition of MANET Elements

Node:
A device/subsystem that MUST implement IP and SHOULD participate in
MANET signaling. It either runs a MANET routing protocol or participate
in MANET signaling.

Router:
A MANET node that MUST implement a MANET routing protocol and forwards
IP packets not explicitly addressed to itself.

Host:
A node that is not a router. All destinations in MANET that receive
delivered data are hosts.

Link:
A link between two node interfaces. This link may be Logical
(i.e. virtual) link or physical link. Logical links are between two
logical interfaces and physical links are between two physical
interfaces. Links are either unidirectional or bidirectional
(links may be on-link and off-link: see RFC4861).


Physical Link:
a communication facility or medium over which the nodes can
communicate at the link layer, i.e., the layer immediately below
IP. Physical interfaces are the nodes=92 attachment to physical links.
Physical Link types are point-to-point, NBMA, multicast capable,
and shared-media, etc (see link types in ND [RFC4861]).

Logical (virtual) Link:
a communication facility (at L3, or upper-layer) over which nodes can
communicate. This logical link is between two MANET interfaces exists
if either can be heard by the other.

Link MTU:
the maximum transmission unit (i.e. maximum unit size in octets), that
can be conveyed in one transmission unit over the link.


Node Interface:
A node's point of attachment to a link. Each node MUST have at least one
interface that SHOULD be assigned an IP address. If there is/are more
than one interface(s) per node then the additional interface(s) MAY be
assigned an IP address. If an interface is not assigned to an IP address
it MUST be identified by the MANET routing protocol. An interface MAY be
assigned one or more addresses.

MANET Interface:
A node interface that participate in; exchange MANET information used in
MANET routing or exchange information in MANET neighbor node discovery
(e.g as the term used in RFC6130). A MANET interface MUST be assigned to
least one  address to communicate. A router interface MUST be
assigned a routable address which is the main address for the interface.


2.3.3 Terms Definition of MANET Identifications:

An interface MAY be assigned one or more addresses. If the interface is
a logical interface it MAY be assigned to only logical addresses, but if
it is a physical interface MAY be assigned with physical address
(e.g. MAC address) and/or logical address(es) (e.g. IP addresses,
MANET addresses).


MANET Address
A MANET-subnet, node, or interface address. Node and interface addresses
are either IP addresses or RFC5444 addresses. All subnet addresses are
unicast IP addresses.

Address Block and TLV: as specified in RFC5444

Routable address:
A subnet address which can be a destination address. A router MUST be
able to distinguish a routable address from a non-routable address.
Broadcast, and multicast addresses, limited in scope to less than the
entire MANET, MUST NOT be considered as routable addresses. Anycast
addresses MAY be considered as routable addresses.

Main address
A routable address (MANET address) that is assigned to one router's
MANET interface.

Originator address:
A node address of the node that originated a MANET message (this message
MUST include the originator address). It MAY be a routable or an
unroutable address.

subnet prefix
A bit string that consists of some number of initial bits of an IP
address.

Interface identifier
the remaining low-order bits in the node's IP address after the subnet
prefix. A number used to identify a node's interface on a link.

2.3.4 Terms Definition of MANET exchange information formats:

Packet:
A MANET packet of a header plus payload. These packets are either
IP packets or RFC5444 packets. RFC5444 packet MUST be encapsulated
in IP packet. Packets are generated by nodes to be sent to
destination(s) through MANET or through the Internet. RFC5444 packets
information MAY not be used only by MANET routers.

Message:
A MANET data message or routing control message. Routing control
messages are either MANET routing protocol messages or/and RFC5444
messages.

Type Length Value coding (TLV):
A generic way to represent MANET information (as in [RFC5444] and
[RFC5497]).

Frame:
A L2 protocol TLV with a header and payload. In some technologies the L2
operates a MANET routing protocol as a local area networking system.
Frames MAY encapsulate MANET packets to be tunneled through a
telecommunication network.

Route Request Message (RREQ)
A message is used to discover a valid route to a particular
destination address, called the RREQ Target Node. When a router
processes a RREQ it learns routing information on how to Originator
Node.

Route Reply Message (RREP)
A message is used to disseminate routing information about
the RREP Target Node to the RREQ Originator Node and the intermediate
routers.

Route Error Message (RERR)
A message is used to disseminate the information that a route is
not available for one or more particular addresses. A RERR message is
used to indicate that a router does not have a forwarding route
to one or more particular addresses.

2.3.5 Terms Definition Related to MANET Protocol Operation:

Hop-by-hop Routing: (TBD)
A dynamic routing that routes to destination by routing table.

Source Routing: (TBD)
A dynamic routing that its route path is provided in the IP packet.

Route Discovery: TBD

Route Maintenance: TBD

Neighbor discovery: (TBD)
A node discovers neighbors only if the node receives from it's
neighbors.


Multipoint relay (MPR): (TBD)
A router X1 is an MPR for a router Y1, if router Y1 has indicated
its selection of router X1 as an MPR in a recent HELLO message.
Router X1 may be a flooding MPR for Y1 if it is indicated to
participate in the flooding process of messages received from
router Y1, or it may be a routing MPR for Y1, if it is indicated to
declare link-state information for the link from X1 to Y1. It may
also be both at the same time.

MPR selector:
A router, Y, is a flooding/routing MPR selector of router X if
router Y has selected router X as a flooding/routing MPR.

Router Parameters:
boolean or numerical values, specified for each router, and not
specific to an interface. A router MAY change router parameter
values at any time, subject to some MANET constraints.

MANET Routing Metric:
A MANET routing cost that is governed by specific rules and properties
defined by the MANET routing protocol which captures specific link or
node characteristics. Examples of basic metrics are hop-count, ETX, LQI,
etc.

Distance Vector Metric
A metric class related to rules of the MANET interface and MANET path
distance. The metric can be calculated by the distance vector routing
algorithm class used by the MANET routing protocol. A metric of the
distance a message or piece of information has traversed. The minimum
value of distance is the number of IP hops traversed.

Link State Metric
A metric type related to the MANET network-topology status and logical
links' states. This metric is calculated by the link state routing
algorithm class used by the MANET routing protocol. A metric type maybe
EXT, LQL, etc.

Link Metric: TBD

Neighbor Metric: TBD

Path accumulated:
The RREQ message accumulates intermediate routers that are in path to
destination(s).

Protocol Sequence Number:
A Sequence Number related to a MANET protocol that maintained by each
protocol subsystem process. This sequence number is used by other
subsystems to identify the temporal order of protocol information
generated.

Router Sequence Number:
A router sequence number is maintained by each router process. The
sequence number is used by other routers to identify the temporal
order of routing information generated and ensure loop-free routes.

MANET Information Base:
A collection of information (in Table or Cache structure) maintained
by MANET protocols and which is to be made available to MANET routing
protocols. An Information Base may be associated with a MANET router
or with MANET interface (e.g. route request table, IIB, RIB, FIB, MIB).

RIB Entry:
The RIB entry is a conceptual data structure. Implementations may use
any internal representation that conforms to the semantics of a route
as specified in the router specification.

3. IP Considerations and Terminology

   All MANET nodes MUST implement IP and all MANET routers MUST
   run/implement  at least one MANET routing protocol. The
   terminologies described in this document can be used for
   IPv4-MANET and IPv6-MANET. The IPv4 addresses MAY be used in IPv6
   packets but IPv6 addresses MUST not be in IPv4 packets.

   IP address:
   IPv4 addresses or IPv6 addresses.

   IP Packet:
   The packet header plus payload as specified in [RFC791] and [RFC2460]
   for IPv4 and IPv6 respectively. It can encapsulate RFC5444 packets as
   specified by RFC5498.

   Mobile IP considerations:
   Mobile IP terms are provided in [RFC6275], and this technology
   assists nodes while connected through the Internet domain(s). MANET
   is an infrastructure-less network that is able to communicate with
   the Internet (i.e. an IP infrastructure network).

4. Security Consideration and Terminology

   It is RECOMMENDED that MANET routing protocols consider security
   issues because the MANET's transmission medium is wireless which make
   it vulnerable to attacks [ANJUM][RFC4593]. In some situations the
   routing information while traversing the MANET MAY be used by an
   intruder node, to obtain MANET data traffic or/and attack the MANET
   [HERBERG]. Forwarding protocols that use DPD techniques MAY be
   vulnerable to DoS attacks such as [RFC6621]. MANETs MAY be secured
   by using IPsec, AH, DAD, and ESP techniques, and other. However,
   it is RECOMMENDED that MANET detects attackers and possible threats.

   The following are some terminology related to MANET threats and
   security.

Attacker: A node, present in the network and which intentionally seeks
to compromise information based in MANET router(s). The Attacker MAY be
a compromised MANET router if obtained MANET identity or routing
information.

Compromised MANET Router: An attacker router, present in MANET and
which generates syntactically correct routing control messages. Control
messages emitted by compromised router(s) may contain additional
information, or omit information, as compared to a control message
generated by a non-compromised router located in the same MANET
topological position.

Legitimate MANET Router: A MANET router, which is not a Compromised
MANET Router.

Jamming Attack:
The attacker transmits massive amounts of interfering radio traffic,
which will prevent legitimate traffic (e.g., routing and data traffic)
on all or part of the MANET. Indirect jamming attacks MAY occur by
influencing Legitimate MANET Router to transmit unnecessary information.

Eavesdropping:
Obtaining a copy by the attacker of the transmitted MANET routing
information or the transmitted data information from its neighbor's
transmitted radio packet. Attacker=92s processes MANY be used by attacker
to mislead routing. Eavesdropping does not pose a direct threat to the
MANET or to its routing.

Identity Spoofing:
Attacker sends routing messages, pretending to have the MANET identity
of another node.

Link Spoofing:
Compromised MANET router sends routing messages to neighbor node(s)
providing incorrect set of link information.

Replay Attack:
A Compromised router in one MANET region records control traffic
information and replays the recorded information in a different MANET
region (this type of attack is also called the Wormhole attack).

Broadcast Storm:
Compromised MANET router may attack the MANET by attempting to change
the MANET flooding algorithm(s) to increase routing overheads or/and to
increase the route discovery delay. Broadcast storm degrades the data
traffic delivery and MANET performance.

Falsification in MANET:
The compromised MANET router sends false routing information into MANET.
False routing information received in MANET, MAY create unrealistic
information bases.

ICMP Attacks:
The generation of ICMPv6 error messages may be used by compromised MANET
router to attempt DoS attacks by sending an error-causing source routing
header in back-to-back datagrams. As the ICMP messages are passed to the
upper-layer processes, it is possible to perform attacks on the upper
layer protocols (e.g., UDP, TCP). Protocols at the upper layers are
RECOMMENDED to perform some form of validation to ICMP messages (using
the information contained in the payload of the ICMP message) before
acting upon them.

Source Routing Attacks: TBD

Acknowledgments:

This work has used/modified terms of the following documents: RFC2462,
RFC2501, RFC3561, RFC3626, RFC3753, RFC4728, RFC4861, RFC5444,
RFC6130,  RFC6621, [AODVv2], [OLSRv2], and [HERBERG],
Gratefully acknowledge to the IETF community and all contributions.

Reference:
   [HERBERG] Herberg, U., Yi, J., Clausen, T.,"Security Threats for
             NHDP", Work in progress, March, 2012.
   [ANJUM]   Anjum, F. and Mouchtaris, P. "Security for Wireless Ad Hoc
             Networks", John Wiley & Sons, March 2007.
             ISBN: 978-0-471-75688-0.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I hope to get some advise from the Internet community to make the
definitions more suitable/accurate, because I MAY misunderstood.
Thanking you,

Best Regards

Abdussalam Baryun
University of Glamorgan, UK
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

From Dirk.Kutscher@neclab.eu  Tue Jul  3 05:03:43 2012
Return-Path: <Dirk.Kutscher@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 2C71221F8836 for <ietf@ietfa.amsl.com>; Tue,  3 Jul 2012 05:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.161
X-Spam-Level: 
X-Spam-Status: No, score=-2.161 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hiEfDHqWsnWc for <ietf@ietfa.amsl.com>; Tue,  3 Jul 2012 05:03:42 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id AF79921F84E6 for <ietf@ietf.org>; Tue,  3 Jul 2012 05:03:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 618D8101700; Tue,  3 Jul 2012 14:04:38 +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 gJHjqrPOPwmj; Tue,  3 Jul 2012 14:04:38 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 4272A1016FA; Tue,  3 Jul 2012 14:04:18 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.191]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Tue, 3 Jul 2012 14:04:25 +0200
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: =?utf-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: RE: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
Thread-Topic: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with	Hashes) to Proposed Standard
Thread-Index: AQHNQlz1ZNnl6dT9AkeZ9EQ8DKLEF5cG03OAgAQCy4CAABlBAIABgyeAgAAEO4CACWiCAIABwwDA
Date: Tue, 3 Jul 2012 12:04:24 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F524924D0B4E4@PALLENE.office.hd>
References: <20120604141804.23098.42455.idtracker@ietfa.amsl.com> <4FE4E19F.2050400@cs.tcd.ie> <4FE83EF5.1050000@it.aoyama.ac.jp> <4FE85424.9000409@cs.tcd.ie> <4FE998E9.9010809@it.aoyama.ac.jp> <4FE99C75.9010309@cs.tcd.ie> <4FF180DC.3090003@it.aoyama.ac.jp>
In-Reply-To: <4FF180DC.3090003@it.aoyama.ac.jp>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.2.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Graham Klyne <GK@ninebynine.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2012 12:03:43 -0000

SGkgTWFydGluLA0KDQp0aGFua3MgZm9yIHRoZSByZXZpZXcgYW5kIGFkdmljZS4NCg0KSSdkIGFn
cmVlIHRoYXQgdGhlICJjb25maXJtYXRpb24gdXNlIGNhc2UiIHNob3VsZCBiZSBoaWdobGlnaHRl
ZCAoZGVzY3JpYmVkIGJldHRlcikgLiBXaWxsIGRvIHRoYXQgYnkgYWRkaW5nIHNvbWUgdGV4dCBh
bG9uZyB0aGUgbGluZXMgeW91IG1lbnRpb25lZCB0byB0aGUgaW50cm8uDQoNCkhvdyBhYm91dCB0
aGlzOg0KLS0tLQ0KSW4gYWRkaXRpb24sIHdlIGFsc28gZGVmaW5lIGEgIi53ZWxsLWtub3duIiBV
UkwgZXF1aXZhbGVudCwgYW5kIGEgd2F5IHRvIGluY2x1ZGUgYSBoYXNoIGFzIGEgc2VnbWVudCBv
ZiBhbiBIVFRQIFVSTCwgYXMgd2VsbCBhcyBhIGJpbmFyeSBmb3JtYXQgZm9yIHVzZSBpbiBwcm90
b2NvbHMgdGhhdCByZXF1aXJlIG1vcmUgY29tcGFjdCBuYW1lcy4gIE1vcmVvdmVyLCB3ZSBkZWZp
bmUgYSBodW1hbi1zcGVha2FibGUgdGV4dCBmb3JtIHRoYXQgYWxsb3dzIGZvciByZWFkaW5nIG91
dCAoYW5kIHVuZGVyc3RhbmRpbmcpIG5hbWVzIHNvIHRoYXQgdGhleSBjYW4gYmUgdHJhbnNmZXJy
ZWQgb3ZlciB2b2ljZSBjb25uZWN0aW9ucywgd2hpY2ggY2FuIGJlIHVzZWQgZm9yIHZlcmlmeWlu
ZyB0aGUgcHJlc2VuY2Ugb2YgYW4gYWRlcXVhdGUgaGFzaCBvciBrZXkgaW5mb3JtYXRpb24uDQot
LS0tDQoNCkFzIHRvIHRoZSBkZXRhaWxlZCBzdWdnZXN0aW9ucywgSSBkb24ndCB0aGluayBpdCBp
cyByZWFsbHkgbmVjZXNzYXJ5IHRvIHJlbmFtZSAnbmloJyB0byAnZmluZ2VycHJpbnQnIGFuZCB0
byBnZXQgcmlkIG9mICJIdW1hbi1zcGVha2FibGUiIGFzIGEgZGVzY3JpcHRpb24gZm9yIGl0LiBJ
biB0aGUgZW5kLCB0aG9zZSBVUklzIGFyZSBlc3NlbnRpYWxseSAiaHVtYW4tc3BlYWthYmxlIiAt
LSBzbyB0aGF0IHRoZXkgY2FuIGJlIHVzZWQgZm9yIGNvbmZpcm1pbmcgdGhlIHByZXNlbmNlL2Fi
c2VuY2Ugb2YgcmVzb3VyY2VzLg0KDQpJIGRvbuKAmXQgbGlrZSAnZmluZ2VycHJpbnQnIGFzIGEg
c2NoZW1lIGlkZW50aWZpZXIsIGJlY2F1c2UgYSkgdGhvc2UgVVJJcywgdW5saWtlIFBLIGZpbmdl
cnByaW50cywgYWN0dWFsbHkgY29udGFpbiB0aGUgY29tcGxldGUgaGFzaCBpbmZvcm1hdGlvbiBh
bmQgYikgYmVjYXVzZSBpdCBkb2VzIG5vdCBjb252ZXkgdGhlIHJlbGF0aW9uc2hpcCB0byAnbmkn
LiBJIHRoaW5rIGl0J3MgZmluZSB0byBzdGljayB0byAnbmloJyBoZXJlLg0KDQpJIGFncmVlIHRo
YXQgdGhlIG5pZCBzZXBhcmF0b3JzIGNhbiBiZSB1c2VmdWwuIFdvdWxkIGJlIE9LIGZvciBtZSB0
byBzdGlsbCBhZGQgdGhlbS4NCg0KVGhhbmtzLA0KRGlyaw0KDQoNCi0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQpGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXRmLWJvdW5j
ZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiAiTWFydGluIEouIETDvHJzdCINClNlbnQ6IE1vbnRh
ZywgMi4gSnVsaSAyMDEyIDEzOjA3DQpUbzogU3RlcGhlbiBGYXJyZWxsDQpDYzogR3JhaGFtIEts
eW5lOyBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtZmFycmVs
bC1kZWNhZGUtbmktMDcudHh0PiAoTmFtaW5nIFRoaW5ncyB3aXRoIEhhc2hlcykgdG8gUHJvcG9z
ZWQgU3RhbmRhcmQNCg0KSGVsbG8gU3RlcGhlbiwNCg0KT24gMjAxMi8wNi8yNiAyMDoyNiwgU3Rl
cGhlbiBGYXJyZWxsIHdyb3RlOg0KPg0KPiBIaSBhZ2FpbiBNYXJ0aW4sDQo+DQo+IE9uIDA2LzI2
LzIwMTIgMTI6MTEgUE0sICJNYXJ0aW4gSi4gRMO8cnN0IiB3cm90ZToNCj4+IFNvIHRoZSBxdWVz
dGlvbiBpcyByZWFsbHksIHdoYXQncyB0aGUgdXNlIGNhc2UsIGFuZCB3aGF0J3MganVzdCBhIA0K
Pj4gY29uc2VxdWVuY2Ugb2YgdGhhdCB1c2UgY2FzZS4gSWYgY29uZmlybWF0aW9uIG9mIGFscmVh
ZHkgYXZhaWxhYmxlIA0KPj4gcmVzb3VyY2VzIChlLmcuIGxpa2UgYSBmaW5nZXJwcmludCkgaXMg
dGhlIChtYWluPykgdXNlIGNhc2UsIGFuZCB0aGUgDQo+PiBncmVhdGVyIHdlaWdodCBvbiAic3Bl
YWthYmlsaXR5IiBqdXN0IGEgZGVzaWduIGNvbnNlcXVlbmNlLCB0aGVuIGl0IA0KPj4gbWFrZXMg
c2Vuc2UgdG8gaGF2ZSB0d28gc2VwYXJhdGUgdGhpbmdzLg0KPg0KPiBZZXMsIGNvbmZpcm1hdGlv
biBpcyB0aGUgbWFpbiBjdXJyZW50IHVzZS1jYXNlIGZvciBuaWggYXMgSSB1bmRlcnN0YW5kIA0K
PiBpdCBhbmQgaGF2ZSBzYWlkIHByZXZpb3VzbHkuDQoNCkkgc2luY2VyZWx5IHdpc2ggeW91IGhh
ZCBzYWlkIHRoaXMgc28gY2xlYXJseSBtdWNoLCBtdWNoIGVhcmxpZXIsIG9yIGV2ZW4gYmV0dGVy
IHRoYXQgaXQgaGFkIGJlZW4gaW4gdGhlIGRyYWZ0IGluIGNyaXN0YWwgY2xlYXIgbGFuZ3VhZ2Uu
IFdlIGNvdWxkIGhhdmUgYXZvaWRlZCBhIGxvdCBvZiB1c2VsZXNzIGRpc2N1c3Npb24uDQoNCj4g
KE9mIGNvdXJzZSB0aGUgcmVzb3VyY2UgbWlnaHQgbm90IHlldA0KPiBiZSBwcmVzZW50LCBzbyAi
YWxyZWFkeSBhdmFpbGFibGUiIGlzbid0IHF1aXRlIHJpZ2h0LCBidXQgdGhhdCdzIGENCj4gbml0
LikNCj4NCj4gSGF2ZSB3ZSBiZWF0ZW4gdGhpcyB0byBkZWF0aCBzdWZmaWNpZW50bHkgbm93PyBJ
IGhvcGUgc287LSkNCj4NCj4gSWYgeW91IHdhbnQgdG8gc3VnZ2VzdCBhIHNlbnRlbmNlIHRoYXQg
c2F5cyB0aGF0LCBmZWVsIGZyZWUuDQoNCkkgcmVhbGx5IGRvbid0IHRoaW5rIGl0IHNob3VsZCBi
ZSBteSBqb2IgdG8gZXhwbGFpbiB0aGlzLiBUaGVyZSBhcmUgZW5vdWdoIGNvYXV0aG9ycyBvbiB0
aGUgZHJhZnQgd2hvIHNob3VsZCBiZSBpbiBhIG11Y2ggYmV0dGVyIHBvc2l0aW9uIHRoYW4gbXlz
ZWxmIHRvIHdyaXRlIHN1Y2ggdGV4dCA6LSguDQoNCkFueXdheSwgaGVyZSBpcyBhIHRyeToNCg0K
LSBJbiB0aGUgYWJzdHJhY3QsIHJlcGxhY2UgImFuZCBiaW5hcnkgYW5kIGh1bWFuICJzcGVha2Fi
bGUiIGZvcm1hdHMgZm9yIHRoZXNlIG5hbWVzIiBieSAiLCBhIGJpbmFyeSBmb3JtLCBhbmQgYSBm
b3JtIGZvciBjb25maXJtaW5nIHRoZSBwcmVzZW5jZSAob3IgYWJzZW5jZSkgb2YgcmVzb3VyY2Vz
Ii4NCg0KLSBJbiB0aGUgaW50cm9kdWN0aW9uLCByZXBsYWNlICJhbmQgYQ0KICAgIGh1bWFuLXNw
ZWFrYWJsZSB0ZXh0IGZvcm0gdGhhdCBjb3VsZCBiZSB1c2VkLCBlLmcuIGZvciByZWFkaW5nIG91
dA0KICAgIChwYXJ0cyBvZikgdGhlIG5hbWUgb3ZlciBhIHZvaWNlIGNvbm5lY3Rpb24uIiB3aXRo
DQogICAgImFuZCBhIGZvcm0gb3B0aW1pemVkIGZvciBjb25maXJtaW5nIHRoZSBwcmVzZW5jZSAo
b3IgYWJzZW5jZSkgb2YNCiAgICByZXNvdXJjZXMgYnkgaHVtYW5zLiIuDQoNCi0gQ2hhbmdlIHRo
ZSB0aXRsZSBvZiBTZWN0aW9uIDcgZnJvbSAiSHVtYW4tc3BlYWthYmxlIEZvcm1hdCIgdG8gIkZv
cm1hdCBmb3IgUmVzb3VyY2UgQ29uZmlybWF0aW9uIg0KDQotIFJlcGxhY2UgdGhlIGZpcnN0IHNl
bnRlbmNlIGF0IHRoZSBzdGFydCBvZiBTZWN0aW9uIDcgdG8gc2F5Og0KVGhlcmUgaXMgb2Z0ZW4g
YSBuZWVkIGZvciBodW1hbnMgdG8gY29uZmlybSB0aGF0IGEgcGFydGljdWxhciByZXNvdXJjZSwg
ZS5nLiBhIHB1YmxpYyBrZXksIGlzIGFscmVhZHkgcHJlc2VudCwgb3IgdG8gZGlzY292ZXIgaXRz
IGFic2VuY2UuDQoNCi0gQ2hhbmdlICIoInNwZWFraW5nIiB0aGUgdmFsdWUgb2YgYW4gbmkgVVJJ
KSIgdG8gImNvbmZpcm0gdGhlIHByZXNlbmNlIG9yIGFic2VuY2Ugb2YgYSByZXNvdXJjZSIpDQoN
Ci0gTnVrZSB0aGUgc2Vjb25kIHBhcmFncmFwaCBvZiBzZWN0aW9uIDcgKHRoZSBvbmUgdGhhdCBz
dGFydHMgd2l0aCAiVGhlIGp1c3RpZmljYXRpb24gZm9yIHVzaW5nIGEgVVJJIikuIFRoZSBzdHVm
ZiBpdCBzYXlzIGFib3V0IElETnMsIGZvciBleGFtcGxlLCBpc24ndCByZWFsbHkgYXBwcm9wcmlh
dGUgZm9yIElFVEYgc3RhbmRhcmRpemF0aW9uLg0KDQotIEluIHRoZSBleGFtcGxlIHNlY3Rpb24s
IGNoYW5nZSAiSHVtYW4tc3BlYWthYmxlIGZvcm0gb2YgYSBuYW1lIiB0byAiRm9ybSBmb3IgcmVz
b3VyY2UgY29uZmlybWF0aW9uIiAodGhyZWUgb2NjdXJyZW5jZXMpLg0KDQoNCkknZCBhbHNvIGNo
YW5nZSB0aGUgIm5paDoiIHNjaGVtZSB0byBzb21ldGhpbmcgbGlrZSAiZmluZ2VycHJpbnQ6Iiwg
YW5kIGFsbG93IHRoZSBpbnNlcnRpb24gb2YgZGVsaW1pdGVyIGNoYXJhY3RlcnMgKGFsbG93aW5n
IGUuZy4gDQpuaWg6Mzs1MzI2LTkwNTctZTEyZi1lMmI3LTRiYTAtN2M4OS0yNTYwYTI7ZiBpbnN0
ZWFkIG9mIG5paDozOzUzMjY5MDU3ZTEyZmUyYjc0YmEwN2M4OTI1NjBhMjtmIGJlY2F1c2UgdGhl
IGZvcm1lciBzaG91bGQgYmUgbXVjaCBlYXNpZXIgdG8gbWFuaXB1bGF0ZSBieSBodW1hbnMpLCBi
dXQgSSBndWVzcyBJJ2QgYWdhaW4gYmUgc2hvdCBkb3duIGZvciAicHJvcG9zaW5nIHNvbWV0aGlu
ZyBsaWtlIHRoaXMgYXQgc3VjaCBhIGxhdGUgZGF0ZSIgKEkgbm90ZSB3ZSBhcmUgc3RpbGwgaW4g
SUVURiBMYXN0IENhbGwpLg0KDQoNClJlZ2FyZHMsICAgTWFydGluLg0K

From alexey.melnikov@isode.com  Tue Jul  3 05:24:34 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12B3D21F8773; Tue,  3 Jul 2012 05:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.928
X-Spam-Level: 
X-Spam-Status: No, score=-102.928 tagged_above=-999 required=5 tests=[AWL=-0.329, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7batqi-v3dW0; Tue,  3 Jul 2012 05:24:32 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 6C3E821F8753; Tue,  3 Jul 2012 05:24:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1341318279; d=isode.com; s=selector; i=@isode.com; bh=gS2QKhb3YGUATdJ2yNj75vPECrB1nwsm73yUzjZJvi8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=FcxZWFT+vQNdjhIHWG67iVnm1eA7+QoYF3k/Tx6nYcdqNxShb11a/s4FzWbJtEeqjaUs1W jv385ww65UzpXmCSe6ghMUxWr329pgoviz2hreclYSGqwProcLSpa++Fb7qZOhJBewv+ss zslsIsFxFcMHyCWG6NYlsM8HXTLKN5g=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <T=LkgABPiC4C@statler.isode.com>; Tue, 3 Jul 2012 13:24:38 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4FF2E47C.80104@isode.com>
Date: Tue, 03 Jul 2012 13:24:28 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: draft-ietf-behave-lsn-requirements.all@tools.ietf.org
Subject: Gen-ART review of draft-ietf-behave-lsn-requirements-07
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2012 12:24:34 -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-behave-lsn-requirements-07
Reviewer: Alexey Melnikov
Review Date: 3-July-2012
IETF LC End Date: 10-July-2012
IESG Telechat date: Pending

Summary: The document is ready for publication as a BCP.

Major Issues: None

Minor Issues: None

Nits/editorial comments:

I found it is to be odd to have a requirements document as a BCP, but I 
am sure
you can sort the right status out with IESG.

I found the justification for REQ-6 hard to read/understand. Why does 
access to
servers being on the internal network need to go through CGN at all?


REQ-10:

Justification:  It is anticipated that CGNs will be primarily
       deployed in ISP networks where the need for management is
       critical.  This requirement is at the SHOULD level to acocunt for

typo: account

       the fact that some CGN operators may not need management
       functionality.

Oh really :-)? (Sorry, couldn't resist.)

From lars@netapp.com  Tue Jul  3 05:51:17 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 0F10B21F881F; Tue,  3 Jul 2012 05:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.409
X-Spam-Level: 
X-Spam-Status: No, score=-10.409 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CCpKElSr6u8l; Tue,  3 Jul 2012 05:51:15 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2EB21F8811; Tue,  3 Jul 2012 05:51:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,515,1336374000";  d="p7s'?scan'208";a="659642780"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 03 Jul 2012 05:51:23 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q63CpMrm028284; Tue, 3 Jul 2012 05:51:22 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.193]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0298.004; Tue, 3 Jul 2012 05:51:22 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Gen-ART review of draft-ietf-behave-lsn-requirements-07
Thread-Topic: Gen-ART review of draft-ietf-behave-lsn-requirements-07
Thread-Index: AQHNWRbbG9Hh1O9Yi0GAB8RHIR7tG5cX+DaA
Date: Tue, 3 Jul 2012 12:51:21 +0000
Message-ID: <2D34DBB5-543F-47A3-A649-BDDFF76A6438@netapp.com>
References: <4FF2E47C.80104@isode.com>
In-Reply-To: <4FF2E47C.80104@isode.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=_5AEA599C-34A1-4DBC-A7FB-3D6C36EEBC81"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<draft-ietf-behave-lsn-requirements.all@tools.ietf.org>" <draft-ietf-behave-lsn-requirements.all@tools.ietf.org>, "<gen-art@ietf.org>" <gen-art@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2012 12:51:17 -0000

--Apple-Mail=_5AEA599C-34A1-4DBC-A7FB-3D6C36EEBC81
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Jul 3, 2012, at 14:24, Alexey Melnikov wrote:
> I found it is to be odd to have a requirements document as a BCP, but =
I am sure
> you can sort the right status out with IESG.

+1

I fail to see why Informational wouldn't be the better status.

Lars=

--Apple-Mail=_5AEA599C-34A1-4DBC-A7FB-3D6C36EEBC81
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
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDcwMzEyNTExMlowIwYJKoZIhvcNAQkEMRYEFH+6
dLJWq7lohUN7+olTCktO3S1mMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAJd9wmNJ
PEIO6l3poA8xNILC2V/2PdYlaAKqaG8/ACoJPH4ycvyGpxn4jEGLCn3gdOX0gnQCbQke/GaExz+w
9apQR2bNHIa7vOPvObYanVCPT1v3AurNCBDUHorV3nUJHojQIsh9ci4DAiXK7ZZ6gpD2drT23FaM
QBbOsJHahlv1VnqPPNUQKc5Eqoo15oBUu+Da28FtFL/WuYjqWaowQBBoHasaT8BBl6C0F+iEWZNl
GJzUsd9DSkbpYCHIf1fvq+TcyTLVayqIPHNUQHiO7enbarDlEgBaSZwpG8aQif44IcSqsS1RNEN3
xvXsm77tpoGzti8pmOFiLwxwV8j23z4AAAAAAAA=

--Apple-Mail=_5AEA599C-34A1-4DBC-A7FB-3D6C36EEBC81--

From ben@nostrum.com  Tue Jul  3 15:25:50 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 07DD911E810B; Tue,  3 Jul 2012 15:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Utkp5-0tzcKB; Tue,  3 Jul 2012 15:25:49 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 7B5D911E8086; Tue,  3 Jul 2012 15:25:49 -0700 (PDT)
Received: from [10.0.1.33] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q63MPvDS003597 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 3 Jul 2012 17:25:57 -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-oauth-urn-sub-ns-05
Date: Tue, 3 Jul 2012 17:25:56 -0500
Message-Id: <E37785E2-6EAE-41CC-9717-E47CCB19600D@nostrum.com>
To: draft-ietf-oauth-urn-sub-ns.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
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>, 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: Tue, 03 Jul 2012 22:25: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-oauth-urn-sub-ns-05
Reviewer: Ben Campbell
Review Date: 2012-07-03
IETF LC End Date: 2012-07-11

Summary: Ready for publication as a proposed standard

Major issues: None

Minor issues: None

Nits/editorial comments:

-- section 2:

The RFC 2119 boilerplate is present, but I don't notice any 2119 =
normative language.

-- section 4, first sentence: "None not already inherent to using URNs."

Sentence Fragment.

-- section 5.1, last bullet, "... values subordinate to =
urn:ietf:params:oauth are of the from ..."

Missing word?=

From mehmet.ersue@nsn.com  Wed Jul  4 02:18:19 2012
Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F116E21F8620 for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 02:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.549
X-Spam-Level: 
X-Spam-Status: No, score=-106.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B89Tk3rW0iO9 for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 02:18:17 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id C661A21F85D5 for <ietf@ietf.org>; Wed,  4 Jul 2012 02:18:16 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q649IM5Y016198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 4 Jul 2012 11:18:22 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q649I8Va025904; Wed, 4 Jul 2012 11:18:21 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 4 Jul 2012 11:18:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD59C5.F24609AF"
Subject: RE: IETF Nominations Committee Chair - 2012 - 2013
Date: Wed, 4 Jul 2012 11:18:16 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6403FCE89E@DEMUEXC006.nsn-intra.net>
In-Reply-To: <33D4FA5C-3199-4769-B159-D528743614BB@isoc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IETF Nominations Committee Chair - 2012 - 2013
Thread-Index: Ac1ZWvM5Y8XS6zmwTBi6jL2n6tD/JAAZ1Qfw
References: <EA42D3B8-3347-4D4D-B8CE-65B8199F8968@isoc.org> <33D4FA5C-3199-4769-B159-D528743614BB@isoc.org>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 04 Jul 2012 09:18:17.0597 (UTC) FILETIME=[F286EAD0:01CD59C5]
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: 8738
X-purgate-ID: 151667::1341393503-00003CDD-00D77967/0-0/0-0
Cc: "ext Lynn St.Amour" <st.amour@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 09:18:19 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CD59C5.F24609AF
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

=20

it's time again for Nomcom. Congrats and good luck to Matt Lepinski.

I have to admit I don't know him. I assume this is my issue as I'm an
OPS guy and not much involved in atoca or geopriv.

=20

Having been active in two Nomcoms, I am wondering what a useful
selection criteria for a Nomcom chair could be.

Having experience as a WG chair or having been active as Nomcom voting
member?

I can imagine a retired AD would enjoy it and do an excellent job in
this position.

=20

Cheers,=20
Mehmet=20

=20

From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of ext Lynn St.Amour
Sent: Tuesday, July 03, 2012 10:31 PM
To: IETF Announcement list
Subject: IETF Nominations Committee Chair - 2012 - 2013

=20

To the IETF community,

One of the roles you entrusted to the Internet Society (ISOC) President
& CEO is to appoint the IETF Nominations Committee chair.   This is done
through consultation with the IETF community.

It gives me great pleasure to announce that Matt Lepinski has agreed to
serve as the 2012 - 2013 IETF Nominations Committee chair.

A Call for Nominations for this committee will be sent to the IETF
Announcement list; and a list of the IESG, IAB and IAOC/IETF Trust seats
to be filled will be published shortly.   Please give serious
consideration to volunteering for the Nominations Committee as well as
to possible candidates for the open positions.=20

The NomComm process is central to the IETF's success, and it is
important that it have the support of the IETF community.   In the
interim, feel free to make your suggestions known to Matt, who will
share them with the committee once it is seated.   Matt can be reached
at: Matthew Lepinski <mlepinski.ietf@gmail.com>

Thank you in advance for your support and a sincere thank you to Matt
for agreeing to take on this very significant responsibility.

Regards,

Lynn St. Amour

President & CEO
Internet Society (ISOC)

=20

=20


------_=_NextPart_001_01CD59C5.F24609AF
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Verdana","sans-serif";
	color:blue;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
it&#8217;s time again for Nomcom. Congrats and good luck to Matt =
Lepinski.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
I have to admit I don&#8217;t know him. I assume this is my issue as =
I&#8217;m an OPS guy and not much involved in atoca or =
geopriv.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Having been active in two Nomcoms, I am wondering what a useful =
selection criteria for a Nomcom chair could be.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Having experience as a WG chair or having been active as Nomcom voting =
member?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
I can imagine a retired AD would enjoy it and do an excellent job in =
this position.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Cheers,</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:blue'>=
 <br></span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Mehmet</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:blue'>=
 <o:p></o:p></span></p></div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid =
blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] =
<b>On Behalf Of </b>ext Lynn St.Amour<br><b>Sent:</b> Tuesday, July 03, =
2012 10:31 PM<br><b>To:</b> IETF Announcement list<br><b>Subject:</b> =
IETF Nominations Committee Chair - 2012 - =
2013<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><div><div><div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>To the IETF =
community,<br><br>One of the roles you entrusted to the Internet Society =
(ISOC) President &amp; CEO is to appoint the IETF Nominations Committee =
chair. &nbsp;&nbsp;This is done through consultation with the IETF =
community.<br><br>It gives me great pleasure to announce that Matt =
Lepinski has agreed to serve as the 2012 - 2013 IETF Nominations =
Committee chair.<br><br>A Call for Nominations for this committee will =
be sent to the IETF Announcement list; and a list of the IESG, IAB and =
IAOC/IETF Trust seats to be filled will be published shortly. =
&nbsp;&nbsp;Please give serious consideration to volunteering for the =
Nominations Committee as well as to possible candidates for the open =
positions. <br><br>The NomComm process is central to the IETF's success, =
and it is important that it have the support of the IETF community. =
&nbsp;&nbsp;In the interim, feel free to make your suggestions known to =
Matt, who will share them with the committee once it is seated. =
&nbsp;&nbsp;Matt can be reached at: Matthew Lepinski &lt;<a =
href=3D"mailto:mlepinski.ietf@gmail.com">mlepinski.ietf@gmail.com</a>&gt;=
<br><br>Thank you in advance for your support and a sincere thank you to =
Matt for agreeing to take on this very significant =
responsibility.<br><br>Regards,<br><br>Lynn St. Amour<br><br>President =
&amp; CEO<br>Internet Society (ISOC)<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------_=_NextPart_001_01CD59C5.F24609AF--

From mehmet.ersue@nsn.com  Wed Jul  4 02:34:50 2012
Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01CE821F87C9 for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 02:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.553
X-Spam-Level: 
X-Spam-Status: No, score=-106.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cgWjAXySYfNW for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 02:34:49 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 3066821F859F for <ietf@ietf.org>; Wed,  4 Jul 2012 02:34:48 -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 q649YsBe010271 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 4 Jul 2012 11:34:56 +0200
Received: from DEMUEXC047.nsn-intra.net ([10.159.32.93]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q649YrvX002149; Wed, 4 Jul 2012 11:34:54 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 4 Jul 2012 11:34:53 +0200
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: bits-n-bites: Exhibitors and product vendors hawking wares at anIETF meeting?
Date: Wed, 4 Jul 2012 11:34:51 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6403FCE8BB@DEMUEXC006.nsn-intra.net>
In-Reply-To: <BEB839C7-3189-4F40-9EBD-D414E0E378F7@vigilsec.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: bits-n-bites: Exhibitors and product vendors hawking wares at anIETF meeting?
Thread-Index: Ac1VXY2xsn7XJ80wTKWK02cZVubr9QEaGyzw
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com><CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com><CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com><6.2.5.6.2.20120620072437.0ad66a00@resistor.net><8F4E6FDD-33F9-4383-9DB0-9F6B17D9A5D9@vpnc.org><199FFAA6-FEC9-4454-901A-7DDFE78ED72A@lucidvision.com> <BEB839C7-3189-4F40-9EBD-D414E0E378F7@vigilsec.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Russ Housley" <housley@vigilsec.com>, "Thomas Nadeau" <tnadeau@lucidvision.com>, "IETF discussion list" <ietf@ietf.org>
X-OriginalArrivalTime: 04 Jul 2012 09:34:53.0795 (UTC) FILETIME=[444EAB30:01CD59C8]
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: 1019
X-purgate-ID: 151667::1341394498-0000425E-1E71E1EA/0-0/0-0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 09:34:50 -0000

Hi Russ, All,

was there also a discussion on the contribution?
$10**4 for two hours chat with potential customers does not look very
motivating.
As this is an experiment I would actually start with less obstacles and
see how it evolves.

Cheers,=20
Mehmet=20


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of ext Russ
> Housley
> Sent: Thursday, June 28, 2012 8:41 PM
> To: Thomas Nadeau
> Cc: IETF discussion list
> Subject: Re: bits-n-bites: Exhibitors and product vendors hawking
wares at anIETF
> meeting?
>=20
> There was a long discussion about this event prior to it being
scheduled.  Sorry you
> missed that discussion.
>=20
> We will have a discussion after the event to determine if we should do
it again.
>=20
> Russ
>=20
>=20
> On Jun 28, 2012, at 2:23 PM, Thomas Nadeau wrote:
>=20
> >
> > 	Has the IETF morphed into a conference/convention?
> >
> > http://www.ietf.org/meeting/84/bits-n-bites.html
> >
> >


From housley@vigilsec.com  Wed Jul  4 06:52:01 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 B28F321F87D8 for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 06:52:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.209
X-Spam-Level: 
X-Spam-Status: No, score=-102.209 tagged_above=-999 required=5 tests=[AWL=0.390, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JAQskWohBE1Y for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 06:52:01 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 28FD321F8594 for <ietf@ietf.org>; Wed,  4 Jul 2012 06:52:01 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 0BAF9F2403F; Wed,  4 Jul 2012 09:52: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 dDdo4s3e3fIq; Wed,  4 Jul 2012 09:52:04 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-39-25.washdc.fios.verizon.net [96.255.39.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 65DEAF2403A; Wed,  4 Jul 2012 09:52:15 -0400 (EDT)
Subject: Re: bits-n-bites: Exhibitors and product vendors hawking wares at anIETF meeting?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6403FCE8BB@DEMUEXC006.nsn-intra.net>
Date: Wed, 4 Jul 2012 09:52:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <27AA7B5C-F989-4C51-BFB1-1BE0316F6101@vigilsec.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com><CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com><CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com><6.2.5.6.2.20120620072437.0ad66a00@resistor.net><8F4E6FDD-33F9-4383-9DB0-9F6B17D9A5D9@vpnc.org><199FFAA6-FEC9-4454-901A-7DDFE78ED72A@lucidvision.com> <BEB839C7-3189-4F40-9EBD-D414E0E378F7@vigilsec.com> <80A0822C5E9A4440A5117C2F4CD36A6403FCE8BB@DEMUEXC006.nsn-intra.net>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 13:52:01 -0000

Mehmet:

This is the price that NANOG charges for a table at their Beer-n-Gear =
event.  I think that access to the IETF community is worth roughly the =
same price.  We can reevaluate the price once there is feedback on the =
experiment.  It might go up,  It might go down.

Russ


On Jul 4, 2012, at 5:34 AM, Ersue, Mehmet (NSN - DE/Munich) wrote:

> Hi Russ, All,
>=20
> was there also a discussion on the contribution?
> $10**4 for two hours chat with potential customers does not look very
> motivating.
> As this is an experiment I would actually start with less obstacles =
and
> see how it evolves.
>=20
> Cheers,=20
> Mehmet=20
>=20
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of ext Russ
>> Housley
>> Sent: Thursday, June 28, 2012 8:41 PM
>> To: Thomas Nadeau
>> Cc: IETF discussion list
>> Subject: Re: bits-n-bites: Exhibitors and product vendors hawking
> wares at anIETF
>> meeting?
>>=20
>> There was a long discussion about this event prior to it being
> scheduled.  Sorry you
>> missed that discussion.
>>=20
>> We will have a discussion after the event to determine if we should =
do
> it again.
>>=20
>> Russ
>>=20
>>=20
>> On Jun 28, 2012, at 2:23 PM, Thomas Nadeau wrote:
>>=20
>>>=20
>>> 	Has the IETF morphed into a conference/convention?
>>>=20
>>> http://www.ietf.org/meeting/84/bits-n-bites.html
>>>=20
>>>=20
>=20


From joelja@bogus.com  Wed Jul  4 07:01:09 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5427A21F87FC for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 07:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AT0VTV8wu7WT for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 07:01:08 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id D195521F87F5 for <ietf@ietf.org>; Wed,  4 Jul 2012 07:01:08 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (c-71-193-176-225.hsd1.wa.comcast.net [71.193.176.225]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q64E1Jdr001443 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 4 Jul 2012 14:01:19 GMT (envelope-from joelja@bogus.com)
Message-ID: <4FF44CA9.10702@bogus.com>
Date: Wed, 04 Jul 2012 07:01:13 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: bits-n-bites: Exhibitors and product vendors hawking wares at anIETF meeting?
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com><CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com><CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com><6.2.5.6.2.20120620072437.0ad66a00@resistor.net><8F4E6FDD-33F9-4383-9DB0-9F6B17D9A5D9@vpnc.org><199FFAA6-FEC9-4454-901A-7DDFE78ED72A@lucidvision.com> <BEB839C7-3189-4F40-9EBD-D414E0E378F7@vigilsec.com> <80A0822C5E9A4440A5117C2F4CD36A6403FCE8BB@DEMUEXC006.nsn-intra.net> <27AA7B5C-F989-4C51-BFB1-1BE0316F6101@vigilsec.com>
In-Reply-To: <27AA7B5C-F989-4C51-BFB1-1BE0316F6101@vigilsec.com>
X-Enigmail-Version: 1.4.2
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]); Wed, 04 Jul 2012 14:01:19 +0000 (UTC)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 14:01:09 -0000

On 7/4/12 06:52 , Russ Housley wrote:
> Mehmet:
> 
> This is the price that NANOG charges for a table at their Beer-n-Gear
> event.  I think that access to the IETF community is worth roughly
> the same price.  We can reevaluate the price once there is feedback
> on the experiment.  It might go up,  It might go down.

NANOG is around 500 attendees. I daresay exposure to the average nanog
attendee is worth more, but ultimately the best feedback in that regard
will likely come from the sponsors.

> Russ
> 
> 
> On Jul 4, 2012, at 5:34 AM, Ersue, Mehmet (NSN - DE/Munich) wrote:
> 
>> Hi Russ, All,
>> 
>> was there also a discussion on the contribution? $10**4 for two
>> hours chat with potential customers does not look very motivating. 
>> As this is an experiment I would actually start with less obstacles
>> and see how it evolves.
>> 
>> Cheers, Mehmet
>> 
>> 
>>> -----Original Message----- From: ietf-bounces@ietf.org
>>> [mailto:ietf-bounces@ietf.org] On Behalf
>> Of ext Russ
>>> Housley Sent: Thursday, June 28, 2012 8:41 PM To: Thomas Nadeau 
>>> Cc: IETF discussion list Subject: Re: bits-n-bites: Exhibitors
>>> and product vendors hawking
>> wares at anIETF
>>> meeting?
>>> 
>>> There was a long discussion about this event prior to it being
>> scheduled.  Sorry you
>>> missed that discussion.
>>> 
>>> We will have a discussion after the event to determine if we
>>> should do
>> it again.
>>> 
>>> Russ
>>> 
>>> 
>>> On Jun 28, 2012, at 2:23 PM, Thomas Nadeau wrote:
>>> 
>>>> 
>>>> Has the IETF morphed into a conference/convention?
>>>> 
>>>> http://www.ietf.org/meeting/84/bits-n-bites.html
>>>> 
>>>> 
>> 
> 
> 



From julian.reschke@gmx.de  Wed Jul  4 07:49:37 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 5307921F87C4 for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 07:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.878
X-Spam-Level: 
X-Spam-Status: No, score=-104.878 tagged_above=-999 required=5 tests=[AWL=-2.279, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VsgxkLvsnwra for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 07:49:36 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 5797C21F8814 for <ietf@ietf.org>; Wed,  4 Jul 2012 07:49:36 -0700 (PDT)
Received: (qmail invoked by alias); 04 Jul 2012 14:49:45 -0000
Received: from p54BB2CAC.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.44.172] by mail.gmx.net (mp070) with SMTP; 04 Jul 2012 16:49:45 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/S7y5dPALSG/xtL98p0MhreRpLCStKLmzms6+kWg fPvmiNNiVoZinY
Message-ID: <4FF45805.60702@gmx.de>
Date: Wed, 04 Jul 2012 16:49:41 +0200
From: Julian Reschke <julian.reschke@gmx.de>
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: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com> <4FE37DF1.2080407@gmail.com> <F96B6701-F6FF-41C1-BF81-81A00C76C450@vigilsec.com>
In-Reply-To: <F96B6701-F6FF-41C1-BF81-81A00C76C450@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 14:49:37 -0000

On 2012-06-21 23:08, Russ Housley wrote:
> This URL <http://www.ietf.org/tao> will bring up the current document.  It works exactly the same as <http://www.ietf.org/tao.html>.
>
> This means that <http://www.ietf.org/tao/archive> cannot be used as suggested on this thread.
 > ...

Sorry?

From housley@vigilsec.com  Wed Jul  4 07:59:06 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 1566021F8832 for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 07:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.271
X-Spam-Level: 
X-Spam-Status: No, score=-102.271 tagged_above=-999 required=5 tests=[AWL=0.328, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBqbLeByZgJx for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 07:59:05 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8F4CD21F8835 for <ietf@ietf.org>; Wed,  4 Jul 2012 07:59:05 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 55AF19A4729; Wed,  4 Jul 2012 10:59:26 -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 N6WJIG5fgy4i; Wed,  4 Jul 2012 10:59:13 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-39-25.washdc.fios.verizon.net [96.255.39.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2AD37F2403A; Wed,  4 Jul 2012 10:59:23 -0400 (EDT)
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FF45805.60702@gmx.de>
Date: Wed, 4 Jul 2012 10:52:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3CAEDB8A-46A5-4055-B0F4-BC0984463866@vigilsec.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com> <4FE37DF1.2080407@gmail.com> <F96B6701-F6FF-41C1-BF81-81A00C76C450@vigilsec.com> <4FF45805.60702@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
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: Wed, 04 Jul 2012 14:59:06 -0000

Julian:

Do you object to http://www.ietf.org/tao-archive for the old version of =
the Tao?

Russ


On Jul 4, 2012, at 10:49 AM, Julian Reschke wrote:

> On 2012-06-21 23:08, Russ Housley wrote:
>> This URL <http://www.ietf.org/tao> will bring up the current =
document.  It works exactly the same as <http://www.ietf.org/tao.html>.
>>=20
>> This means that <http://www.ietf.org/tao/archive> cannot be used as =
suggested on this thread.
> > ...
>=20
> Sorry?


From julian.reschke@gmx.de  Wed Jul  4 08:59:10 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 1B45121F861C for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 08:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.774
X-Spam-Level: 
X-Spam-Status: No, score=-104.774 tagged_above=-999 required=5 tests=[AWL=-2.175, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b81ew3qbc7ZZ for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 08:59:09 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 93A1B21F8611 for <ietf@ietf.org>; Wed,  4 Jul 2012 08:59:08 -0700 (PDT)
Received: (qmail invoked by alias); 04 Jul 2012 15:59:18 -0000
Received: from p54BB2CAC.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.44.172] by mail.gmx.net (mp041) with SMTP; 04 Jul 2012 17:59:18 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19vKeE1rRRvnXvVBnqnOCLfO3ojbdqTIZRQCJZ89R cV9f/LIZ9PPbcW
Message-ID: <4FF4684F.9030603@gmx.de>
Date: Wed, 04 Jul 2012 17:59:11 +0200
From: Julian Reschke <julian.reschke@gmx.de>
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: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com> <4FE37DF1.2080407@gmail.com> <F96B6701-F6FF-41C1-BF81-81A00C76C450@vigilsec.com> <4FF45805.60702@gmx.de> <3CAEDB8A-46A5-4055-B0F4-BC0984463866@vigilsec.com>
In-Reply-To: <3CAEDB8A-46A5-4055-B0F4-BC0984463866@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 15:59:10 -0000

On 2012-07-04 16:52, Russ Housley wrote:
> Julian:
>
> Do you object to http://www.ietf.org/tao-archive for the old version of the Tao?
>
> Russ

No, I was just trying to understand *why* the archive can't be at 
<http://www.ietf.org/tao/archive>.

Best regards, Julian

From sm@resistor.net  Wed Jul  4 09:30:27 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 F378E21F8715; Wed,  4 Jul 2012 09:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id atrpCMw6jYle; Wed,  4 Jul 2012 09:30:24 -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 ABC5B21F8710; Wed,  4 Jul 2012 09:30:24 -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 q64GUO6I025060; Wed, 4 Jul 2012 09:30:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1341419431; bh=076Nv2hHn6isCJFRWD4xiRYtxJnB1nSf9eqomnk2DOo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Sx3KgCfW39DVMirDwa52aNImGwUAENZN/SabuQhV6rZ3/SDUytbDTCaSUKdm1AevQ Nnw+UmmzjYQRnqs4R3AT7V4yypJnwpjS0Mpvp8UARhE+ccpx3+duJ+mn/zVe+DhrKR EyfGPS45lEQq6yKBnfKeUDp1iRZWpFnOU0z+vXFU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1341419431; i=@resistor.net; bh=076Nv2hHn6isCJFRWD4xiRYtxJnB1nSf9eqomnk2DOo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fNKfNR2eksNaGBTQaS2WNAlyTROtPvhIWxfwIwJdf/4rRkKJt9+9HB99JidQQvycF Dlx781hgOZRCOgH51gB/H10D5XogFrRpdotVCpA1GESNjs4nInLiWbhqwLclJO9+Ei BLdgThdNFlhhh8rTWz/0X8uzb3R+iBC0CKVzXHN8=
Message-Id: <6.2.5.6.2.20120704071517.09069f48@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 04 Jul 2012 09:13:52 -0700
To: urn@ietf.org
From: SM <sm@resistor.net>
Subject: Re: [urn] listed authors
In-Reply-To: <CAC4RtVBB=uPxnXB_0eFJUfxGTfBeewX+-Sud+fVjD40w9c=3nw@mail.g mail.com>
References: <4FF34B61.4050903@stpeter.im> <CAC4RtVBB=uPxnXB_0eFJUfxGTfBeewX+-Sud+fVjD40w9c=3nw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Barry Leiba <barryleiba@computer.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, 04 Jul 2012 16:30:27 -0000

Hi Barry,

[Cc to ietf@ as the question is pertinent to other working groups too]

At 06:47 04-07-2012, Barry Leiba wrote:
>Well, yes and no -- it's not that simple.

Agreed.

>First, I agree that the complete removal of the name of someone who
>contributed substantially to a document in any phase of its life
>(including a prior edition) would, indeed, be disrespectful... and
>unethical.

There was a message from Fred Baker on December 12, 2011 to ietf@ 
about a similar question:

  "Checking the acknowledgements, you'll see that I listed Warren and his
   professor as co-authors, although to be honest they at most made a few
   comments on the actual paper. Why? It is a variation on his original idea,
   and I'm giving him full credit for the idea. Tim and his student get
   mentioned as making a suggestion, because they did some work and it was a
   good suggestion. Others are listed as commenting, because they did."

We could diff a -bis document to determine whether the change is 
substantial or not.  That's more of a measure than an assessment of 
an idea.  Long-standing authors tend to "give credit where credit is 
due" whereas new authors tend to look at it in terms of lines of text provided.

>But:
>
>1. 2141bis (for example) is a product of the urnbis working group, and
>the chairs have complete control over who is listed at the top of the
>document.  They can remove someone's name for any defensible reason
>(subject, of course, to appeal), including that the person is no
>longer participating in the document's development.

There is a subtlety here.  The chairs have complete control on the 
selection of the document editor.  The document editor has editorial 
discretion.  I'll argue that the individual also has a say in keeping 
the name of the author of the previous version of the document.

>2. Everyone who appears at the top of the document has to be reachable
>and responsive during AUTH48.  An AD can override that, but we prefer
>to avoid that and to list only those who we *do* expect to handle the
>AUTH48 process promptly.

Yes.

>3. An "Authors" section can and should be added to recognize the
>contributions of those who are or were authors of some version of the
>document, but who are no longer listed at the top.  This is where we
>can give due respect to a former author who is no longer active.

You may have meant "Contributors" here.  There are RFC Editor 
guidelines about that ( http://www.rfc-editor.org/policy.html ).

>Of course, as Juha says, it would be reasonable to ask the authors of
>prior versions how they would like to be recognized (and, I'll add,
>whether they will be available to review the final version and sign
>off during AUTH48).  That can certainly be input to the chairs'
>decision.  And anyway, if contacting a former author might bring more
>experienced eyes on the document and get more reviews and input,
>that's a good thing.  If we specifically think a former author will
>disapprove of where we've gone, that is NOT a reason to exclude him...
>in fact, it's that much more of a reason to get the input for
>consideration.

The IETF has formal processes for listed authors due to IPR.  Given 
that I will not be provided any assistance when things go wrong, I 
prefer to follow the cautious path where I only add a person's name 
with their agreement.  There was a case where a listed author asked 
to have his name removed as author.  This may come as a surprise to 
some participants; some people prefer not to have their name attached 
to a bad idea as they consider that as more important than having a 
name on a RFC.

It's up to each and anyone to see whether it is worthwhile to make 
that good faith effort to contact the former author and have them 
involved in the work to update a specification.  It's better to do 
that early instead of having a "fait accompli" where the former 
author is not given much latitude to disapprove.

It is up to the author to assess whether getting more review and 
input is important.  Having a working group does not mean that the 
work will get adequate review.  Soliciting comments does not 
necessarily make it happen.  If everyone is listed as author, the 
question that comes to mind is who is going to review the work.

Regards,
-sm 


From mary.ietf.barnes@gmail.com  Wed Jul  4 10:24:09 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B29721F86AF for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 10:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.605
X-Spam-Level: 
X-Spam-Status: No, score=-103.605 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1vrypYF9B8NF for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 10:24:08 -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 C4A9921F86E5 for <ietf@ietf.org>; Wed,  4 Jul 2012 10:24:07 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so13511627obb.31 for <ietf@ietf.org>; Wed, 04 Jul 2012 10:24:18 -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=oEz3ZPqlU5ITAy3dAbAODB+lId/g69RRVrdT3+X1nqU=; b=qavfZdNylz/bJ/jJHGzymrOxFJwTust2O6gbFWEfNL3l4zuhR+Vu5D8NuGzEtGwADy jVnChAMiFzGfWPdbn4lDQ0hY1ULDYH1ttqGrGU6ZcT/cJGjMOwdWJYB6Ap4fYI2YHmGP FWKSTB23FRoaM0UcdLEJJpfeiOGhlzF0DkucOU/pQ5sJ6L05XLucbbOUjz0/Z1qCLwOv FXHVFYy5UjNjjMCB0oQRW2hgjTGsfkCppHO6nDGRKH1fqVC7p3RjnYVvPYPXY90+gKBV lc7iAZKuzf7UxVdJZTkjiE3YGF1lIIIigpai6BtYvW6g2VeGLMs6szjJXXyko09Q0280 almw==
MIME-Version: 1.0
Received: by 10.182.145.8 with SMTP id sq8mr17932537obb.50.1341422658683; Wed, 04 Jul 2012 10:24:18 -0700 (PDT)
Received: by 10.182.147.1 with HTTP; Wed, 4 Jul 2012 10:24:18 -0700 (PDT)
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6403FCE89E@DEMUEXC006.nsn-intra.net>
References: <EA42D3B8-3347-4D4D-B8CE-65B8199F8968@isoc.org> <33D4FA5C-3199-4769-B159-D528743614BB@isoc.org> <80A0822C5E9A4440A5117C2F4CD36A6403FCE89E@DEMUEXC006.nsn-intra.net>
Date: Wed, 4 Jul 2012 12:24:18 -0500
Message-ID: <CAHBDyN7FcwYespTTwvj_myV9E_AexmyLnbZbhWnwCGqM+pOSNA@mail.gmail.com>
Subject: Re: IETF Nominations Committee Chair - 2012 - 2013
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Content-Type: multipart/alternative; boundary=f46d044786c310833804c4044d9d
Cc: ietf@ietf.org, "ext Lynn St.Amour" <st.amour@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 17:24:09 -0000

--f46d044786c310833804c4044d9d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Mehmet,

In my experience, the most important characteristic for a nomcom chair is
the ability to lead a group of 10 volunteers (usually with a significant
variation of experience in IETF) through the process as defined by RFC
 3777 (and 5680).    It can be good for a chair to have past Nomcom
experience, but I do not believe that is a hard requirement (I had never
served on a Nomcom before I was chair).  It can be good for a Nomcom chair
to have been a WG chair as they can understand more about the process. BUT,
the chair is not the decision maker - the voting members are - the most
important thing is for the chair to be able to facilitate the process as
defined.  It's far more important for the voting members to have that
knowledge than the chair.   Now, it can be more challenging if a chair
hasn't been involved in IETF for a while, but AFAIK, Matt has been involved
in the RAI area (as a participant/contributor) for a while and if you
google you can find he's also been involved in the Security area on the
SECDIR. You can see the work he's been involved in here in authorstats:
http://www.arkko.com/tools/allstats/mattlepinski.html

Honestly, one of the most important aspect of the Nomcom process is for the
Nomcom to get community feedback. You can read my report from 2009-2010 and
that is an issue as the information that the nomcom is working with
typically is extremely incomplete.  Many nomcom voting members have little
experience with interviewing and hiring "employees".  You also have to keep
in mind that the past Nomcom chair serves as an advisor for the current
Nomcom chair, which dramatically reduces the risk in the case that the
appointed chair runs into problems.

I sincerely thank Matt for his willingness to take on this task as it
requires a tremendous time commitment and dedication to do well.

Regards,
Mary.

On Wed, Jul 4, 2012 at 4:18 AM, Ersue, Mehmet (NSN - DE/Munich) <
mehmet.ersue@nsn.com> wrote:

> Hi,****
>
> ** **
>
> it=92s time again for Nomcom. Congrats and good luck to Matt Lepinski.***=
*
>
> I have to admit I don=92t know him. I assume this is my issue as I=92m an=
 OPS
> guy and not much involved in atoca or geopriv.****
>
> ** **
>
> Having been active in two Nomcoms, I am wondering what a useful selection
> criteria for a Nomcom chair could be.****
>
> Having experience as a WG chair or having been active as Nomcom voting
> member?****
>
> I can imagine a retired AD would enjoy it and do an excellent job in this
> position.****
>
> ** **
>
> Cheers,
> Mehmet ****
>
> ** **
>
> *From:* ietf-announce-bounces@ietf.org [mailto:
> ietf-announce-bounces@ietf.org] *On Behalf Of *ext Lynn St.Amour
> *Sent:* Tuesday, July 03, 2012 10:31 PM
> *To:* IETF Announcement list
> *Subject:* IETF Nominations Committee Chair - 2012 - 2013****
>
> ** **
>
> To the IETF community,
>
> One of the roles you entrusted to the Internet Society (ISOC) President &
> CEO is to appoint the IETF Nominations Committee chair.   This is done
> through consultation with the IETF community.
>
> It gives me great pleasure to announce that Matt Lepinski has agreed to
> serve as the 2012 - 2013 IETF Nominations Committee chair.
>
> A Call for Nominations for this committee will be sent to the IETF
> Announcement list; and a list of the IESG, IAB and IAOC/IETF Trust seats =
to
> be filled will be published shortly.   Please give serious consideration =
to
> volunteering for the Nominations Committee as well as to possible
> candidates for the open positions.
>
> The NomComm process is central to the IETF's success, and it is important
> that it have the support of the IETF community.   In the interim, feel fr=
ee
> to make your suggestions known to Matt, who will share them with the
> committee once it is seated.   Matt can be reached at: Matthew Lepinski <
> mlepinski.ietf@gmail.com>
>
> Thank you in advance for your support and a sincere thank you to Matt for
> agreeing to take on this very significant responsibility.
>
> Regards,
>
> Lynn St. Amour
>
> President & CEO
> Internet Society (ISOC)****
>
> ** **
>
> ** **
>

--f46d044786c310833804c4044d9d
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Mehmet,<div><br></div><div>In my experience, the most important characteris=
tic for a nomcom chair is the ability to lead a group of 10 volunteers (usu=
ally with a significant variation of experience in IETF) through the proces=
s as defined by RFC =A03777 (and 5680). =A0 =A0It can be good for a chair t=
o have past Nomcom experience, but I do not believe that is a hard requirem=
ent (I had never served on a Nomcom before I was chair). =A0It can be good =
for a Nomcom chair to have been a WG chair as they can understand more abou=
t the process. BUT, the chair is not the decision maker - the voting member=
s are - the most important thing is for the chair to be able to facilitate =
the process as defined. =A0It&#39;s far more important for the voting membe=
rs to have that knowledge than the chair. =A0 Now, it can be more challengi=
ng if a chair hasn&#39;t been involved in IETF for a while, but AFAIK, Matt=
 has been involved in the RAI area (as a participant/contributor) for a whi=
le and if you google you can find he&#39;s also been involved in the Securi=
ty area on the SECDIR. You can see the work he&#39;s been involved in here =
in authorstats:</div>
<div><a href=3D"http://www.arkko.com/tools/allstats/mattlepinski.html">http=
://www.arkko.com/tools/allstats/mattlepinski.html</a></div><div><br></div><=
div>Honestly, one of the most important aspect of the Nomcom process is for=
 the Nomcom to get community feedback. You can read my report from 2009-201=
0 and that is an issue as the information that the nomcom is working with t=
ypically is extremely incomplete. =A0Many nomcom voting members have little=
 experience with interviewing and hiring &quot;employees&quot;. =A0You also=
 have to keep in mind that the past Nomcom chair serves as an advisor for t=
he current Nomcom chair, which dramatically reduces the risk in the case th=
at the appointed chair runs into problems.</div>
<div><br></div><div>I sincerely thank Matt for his willingness to take on t=
his task as it requires a tremendous time commitment and dedication to do w=
ell.</div><div><br></div><div>Regards,</div><div>Mary.=A0</div><div><div>
<br><div class=3D"gmail_quote">On Wed, Jul 4, 2012 at 4:18 AM, Ersue, Mehme=
t (NSN - DE/Munich) <span dir=3D"ltr">&lt;<a href=3D"mailto:mehmet.ersue@ns=
n.com" target=3D"_blank">mehmet.ersue@nsn.com</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;s=
ans-serif&quot;;color:blue">Hi,<u></u><u></u></span></p><p class=3D"MsoNorm=
al"><span style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;s=
ans-serif&quot;;color:blue"><u></u>=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:blue">it=92s time again for Nomcom=
. Congrats and good luck to Matt Lepinski.<u></u><u></u></span></p><p class=
=3D"MsoNormal">
<span style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,&quot;sans-=
serif&quot;;color:blue">I have to admit I don=92t know him. I assume this i=
s my issue as I=92m an OPS guy and not much involved in atoca or geopriv.<u=
></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:blue"><u></u>=A0<u></u></span></p>=
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:blue">Having been active in two No=
mcoms, I am wondering what a useful selection criteria for a Nomcom chair c=
ould be.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:blue">Having experience as a WG ch=
air or having been active as Nomcom voting member?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:blue">I can imagine a retired AD w=
ould enjoy it and do an excellent job in this position.<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:blue"><u></u>=A0<u></u></span></p>=
<div><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&qu=
ot;Verdana&quot;,&quot;sans-serif&quot;;color:blue">Cheers,</span><span sty=
le=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;;color:blue"> <br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Verdana&quot;,&quo=
t;sans-serif&quot;;color:blue">Mehmet</span><span style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blue"> <u></u=
><u></u></span></p>
</div><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&q=
uot;Verdana&quot;,&quot;sans-serif&quot;;color:blue"><u></u>=A0<u></u></spa=
n></p><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0c=
m 0cm 4.0pt">
<div><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt=
 0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span s=
tyle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&qu=
ot;"> <a href=3D"mailto:ietf-announce-bounces@ietf.org" target=3D"_blank">i=
etf-announce-bounces@ietf.org</a> [mailto:<a href=3D"mailto:ietf-announce-b=
ounces@ietf.org" target=3D"_blank">ietf-announce-bounces@ietf.org</a>] <b>O=
n Behalf Of </b>ext Lynn St.Amour<br>
<b>Sent:</b> Tuesday, July 03, 2012 10:31 PM<br><b>To:</b> IETF Announcemen=
t list<br><b>Subject:</b> IETF Nominations Committee Chair - 2012 - 2013<u>=
</u><u></u></span></p></div></div><div><div class=3D"h5"><p class=3D"MsoNor=
mal">
<u></u>=A0<u></u></p><div><div><div><div><div><div><p class=3D"MsoNormal" s=
tyle=3D"margin-bottom:12.0pt">To the IETF community,<br><br>One of the role=
s you entrusted to the Internet Society (ISOC) President &amp; CEO is to ap=
point the IETF Nominations Committee chair. =A0=A0This is done through cons=
ultation with the IETF community.<br>
<br>It gives me great pleasure to announce that Matt Lepinski has agreed to=
 serve as the 2012 - 2013 IETF Nominations Committee chair.<br><br>A Call f=
or Nominations for this committee will be sent to the IETF Announcement lis=
t; and a list of the IESG, IAB and IAOC/IETF Trust seats to be filled will =
be published shortly. =A0=A0Please give serious consideration to volunteeri=
ng for the Nominations Committee as well as to possible candidates for the =
open positions. <br>
<br>The NomComm process is central to the IETF&#39;s success, and it is imp=
ortant that it have the support of the IETF community. =A0=A0In the interim=
, feel free to make your suggestions known to Matt, who will share them wit=
h the committee once it is seated. =A0=A0Matt can be reached at: Matthew Le=
pinski &lt;<a href=3D"mailto:mlepinski.ietf@gmail.com" target=3D"_blank">ml=
epinski.ietf@gmail.com</a>&gt;<br>
<br>Thank you in advance for your support and a sincere thank you to Matt f=
or agreeing to take on this very significant responsibility.<br><br>Regards=
,<br><br>Lynn St. Amour<br><br>President &amp; CEO<br>Internet Society (ISO=
C)<u></u><u></u></p>
</div></div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div></div><=
/div><p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div></div></div></=
div></blockquote></div><br></div></div>

--f46d044786c310833804c4044d9d--

From housley@vigilsec.com  Wed Jul  4 10:54:22 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 A839B21F8731 for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 10:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.302
X-Spam-Level: 
X-Spam-Status: No, score=-102.302 tagged_above=-999 required=5 tests=[AWL=0.297, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IXL0N1WBgp9o for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 10:54:22 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8B521F8740 for <ietf@ietf.org>; Wed,  4 Jul 2012 10:54:22 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 851B69A472A; Wed,  4 Jul 2012 13:54:40 -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 XpzmutMdRcZA; Wed,  4 Jul 2012 13:54:25 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-39-25.washdc.fios.verizon.net [96.255.39.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id A58B59A4729; Wed,  4 Jul 2012 13:54:35 -0400 (EDT)
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4FF4684F.9030603@gmx.de>
Date: Wed, 4 Jul 2012 13:54:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <79A97772-4F3D-4BA0-9A1C-6881E6780FB1@vigilsec.com>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com> <4FE37DF1.2080407@gmail.com> <F96B6701-F6FF-41C1-BF81-81A00C76C450@vigilsec.com> <4FF45805.60702@gmx.de> <3CAEDB8A-46A5-4055-B0F4-BC0984463866@vigilsec.com> <4FF4684F.9030603@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
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: Wed, 04 Jul 2012 17:54:22 -0000

Julian:

> No, I was just trying to understand *why* the archive can't be at =
<http://www.ietf.org/tao/archive>.

I was told that we cannot have http://www.ietf.org/tao directed to the =
document and also be the directory containing the archive directory.

Russ=

From johnl@iecc.com  Wed Jul  4 11:49:46 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 2204021F8790 for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 11:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.106
X-Spam-Level: 
X-Spam-Status: No, score=-111.106 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PPPkqxqgM6hI for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 11:49:45 -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 30E3F21F8787 for <ietf@ietf.org>; Wed,  4 Jul 2012 11:49:44 -0700 (PDT)
Received: (qmail 43202 invoked from network); 4 Jul 2012 18:49:55 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 Jul 2012 18:49:55 -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=4ff49053.xn--i8sz2z.k1207; i=johnl@user.iecc.com; bh=xkfclF62GoRB4x/0ynHHRLHXs07Lf+i3m+pTueHNPVI=; b=UmAaHWFDyqJX8kPZDE3G1MrPU4ukoNPnFG0kO45PSyalWUU4wwsFDLDNQ9c/0FPqNdHgOJdYRBzUl2z41elNchIUUrZlHI3Qvm+/oulNfpNFuq9nFr8HwuZPASYqkIlfNJxRG1xiZM10h2HXYTYHaZwLYLW0ME7RFaDyEpzJC6g=
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=4ff49053.xn--i8sz2z.k1207; olt=johnl@user.iecc.com; bh=xkfclF62GoRB4x/0ynHHRLHXs07Lf+i3m+pTueHNPVI=; b=R7IregR3lw8wOa8IBTG7eoGUSLmHRI12tq46YuPTFYj2Hu5XMOx3u7N/Y66esZ+6IkZouLWFpHuVp+fYaK5v51n9t72cedy5cKu9d5mFabOq34wmTQFQdNd76rDLRS8Nx9ijkTNuUfMJZSbZr6d+e5aOP0jVbudT99KC0YV6iiI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 4 Jul 2012 18:49:33 -0000
Message-ID: <20120704184933.79868.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: bits-n-bites: Exhibitors and product vendors hawking wares at anIETF meeting?
In-Reply-To: <4FF44CA9.10702@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: Wed, 04 Jul 2012 18:49:46 -0000

>NANOG is around 500 attendees. I daresay exposure to the average nanog
>attendee is worth more, but ultimately the best feedback in that regard
>will likely come from the sponsors.

IETF is bigger, but on the other hand, IETF attendees probably spend
less per capita on equipment than NANOGers do.

It's an experiment, if we're turning away sponsors and people think it
was overall a success, we can raise the price.  If not, well, we can
do something else.

R's,
John

From joelja@bogus.com  Wed Jul  4 14:00:07 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 2207121F8627 for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 14:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fENXDtLNblPw for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 14:00:06 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1439721F8625 for <ietf@ietf.org>; Wed,  4 Jul 2012 14:00:06 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-71-193-176-225.hsd1.wa.comcast.net [71.193.176.225]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q64L0GBA003647 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 4 Jul 2012 21:00:17 GMT (envelope-from joelja@bogus.com)
Message-ID: <4FF4AEDB.5030209@bogus.com>
Date: Wed, 04 Jul 2012 14:00:11 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120619 Thunderbird/14.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: bits-n-bites: Exhibitors and product vendors hawking wares at anIETF meeting?
References: <20120704184933.79868.qmail@joyce.lan>
In-Reply-To: <20120704184933.79868.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 04 Jul 2012 21:00:17 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 21:00:07 -0000

On 7/4/12 11:49 AM, John Levine wrote:
>> NANOG is around 500 attendees. I daresay exposure to the average nanog
>> attendee is worth more, but ultimately the best feedback in that regard
>> will likely come from the sponsors.
> IETF is bigger, but on the other hand, IETF attendees probably spend
> less per capita on equipment than NANOGers do.
Yeah, that's what I said. ;)

If pitched correctly the folks that would be interested in the IETF 
community might not be equipment vendors. e.g. I* organizations, 
standards bodies doing outreach, contractors that provider services to 
organziations doing standards works, patent trolls with portfolios to 
sell and regular participants looking to rasie the visibility of their 
activities all seem like potential participants.
> It's an experiment, if we're turning away sponsors and people think it
> was overall a success, we can raise the price.  If not, well, we can
> do something else.
Indeed. A lot of things I might not be willing to support in the general 
case are fine in the guise of experiments.
> R's,
> John
>


From randy@psg.com  Wed Jul  4 16:26:02 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29A7411E808E for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 16:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Y9qSmyM9VJn for <ietf@ietfa.amsl.com>; Wed,  4 Jul 2012 16:26:01 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id BB81411E8088 for <ietf@ietf.org>; Wed,  4 Jul 2012 16:26:01 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SmYxX-0003f9-OX; Wed, 04 Jul 2012 23:26:12 +0000
Date: Thu, 05 Jul 2012 08:26:09 +0900
Message-ID: <m21ukr152m.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: IETF Nominations Committee Chair - 2012 - 2013
In-Reply-To: <CAHBDyN7FcwYespTTwvj_myV9E_AexmyLnbZbhWnwCGqM+pOSNA@mail.gmail.com>
References: <EA42D3B8-3347-4D4D-B8CE-65B8199F8968@isoc.org> <33D4FA5C-3199-4769-B159-D528743614BB@isoc.org> <80A0822C5E9A4440A5117C2F4CD36A6403FCE89E@DEMUEXC006.nsn-intra.net> <CAHBDyN7FcwYespTTwvj_myV9E_AexmyLnbZbhWnwCGqM+pOSNA@mail.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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>, Lynn St Amour <st.amour@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jul 2012 23:26:02 -0000

> I sincerely thank Matt for his willingness to take on this task 

<aol>

and you for when you served.

randy

From mehmet.ersue@nsn.com  Thu Jul  5 01:21:51 2012
Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D36521F85E0 for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 01:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.558
X-Spam-Level: 
X-Spam-Status: No, score=-106.558 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wgK0kCstqQyg for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 01:21:45 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 8245D21F85D6 for <ietf@ietf.org>; Thu,  5 Jul 2012 01:21:37 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q658Llnk006148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 5 Jul 2012 10:21:47 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q658Lhbk010973; Thu, 5 Jul 2012 10:21:47 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 5 Jul 2012 10:21:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD5A87.36DC1A59"
Subject: RE: IETF Nominations Committee Chair - 2012 - 2013
Date: Thu, 5 Jul 2012 10:21:44 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6403FCEC31@DEMUEXC006.nsn-intra.net>
In-Reply-To: <CAHBDyN7FcwYespTTwvj_myV9E_AexmyLnbZbhWnwCGqM+pOSNA@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IETF Nominations Committee Chair - 2012 - 2013
Thread-Index: Ac1aCdmUjJdVT+MTTZWD1l73qZF/LwAfNg2g
References: <EA42D3B8-3347-4D4D-B8CE-65B8199F8968@isoc.org><33D4FA5C-3199-4769-B159-D528743614BB@isoc.org><80A0822C5E9A4440A5117C2F4CD36A6403FCE89E@DEMUEXC006.nsn-intra.net> <CAHBDyN7FcwYespTTwvj_myV9E_AexmyLnbZbhWnwCGqM+pOSNA@mail.gmail.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Mary Barnes" <mary.ietf.barnes@gmail.com>
X-OriginalArrivalTime: 05 Jul 2012 08:21:45.0989 (UTC) FILETIME=[37625B50:01CD5A87]
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: 17844
X-purgate-ID: 151667::1341476507-00003CDD-35F80CEF/0-0/0-0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2012 08:21:52 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CD5A87.36DC1A59
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

> I sincerely thank Matt for his willingness to take on this task as it
requires a tremendous time commitment and dedication to do well.

=20

+1. It is indeed a huge effort for the Nomcom chair and all voting
members especially between September and January.

=20

Cheers,=20
Mehmet=20

=20

From: ext Mary Barnes [mailto:mary.ietf.barnes@gmail.com]=20
Sent: Wednesday, July 04, 2012 7:24 PM
To: Ersue, Mehmet (NSN - DE/Munich)
Cc: ietf@ietf.org; ext Lynn St.Amour
Subject: Re: IETF Nominations Committee Chair - 2012 - 2013

=20

Mehmet,

=20

In my experience, the most important characteristic for a nomcom chair
is the ability to lead a group of 10 volunteers (usually with a
significant variation of experience in IETF) through the process as
defined by RFC  3777 (and 5680).    It can be good for a chair to have
past Nomcom experience, but I do not believe that is a hard requirement
(I had never served on a Nomcom before I was chair).  It can be good for
a Nomcom chair to have been a WG chair as they can understand more about
the process. BUT, the chair is not the decision maker - the voting
members are - the most important thing is for the chair to be able to
facilitate the process as defined.  It's far more important for the
voting members to have that knowledge than the chair.   Now, it can be
more challenging if a chair hasn't been involved in IETF for a while,
but AFAIK, Matt has been involved in the RAI area (as a
participant/contributor) for a while and if you google you can find he's
also been involved in the Security area on the SECDIR. You can see the
work he's been involved in here in authorstats:

http://www.arkko.com/tools/allstats/mattlepinski.html

=20

Honestly, one of the most important aspect of the Nomcom process is for
the Nomcom to get community feedback. You can read my report from
2009-2010 and that is an issue as the information that the nomcom is
working with typically is extremely incomplete.  Many nomcom voting
members have little experience with interviewing and hiring "employees".
You also have to keep in mind that the past Nomcom chair serves as an
advisor for the current Nomcom chair, which dramatically reduces the
risk in the case that the appointed chair runs into problems.

=20

I sincerely thank Matt for his willingness to take on this task as it
requires a tremendous time commitment and dedication to do well.

=20

Regards,

Mary.=20

=20

On Wed, Jul 4, 2012 at 4:18 AM, Ersue, Mehmet (NSN - DE/Munich)
<mehmet.ersue@nsn.com> wrote:

Hi,

=20

it's time again for Nomcom. Congrats and good luck to Matt Lepinski.

I have to admit I don't know him. I assume this is my issue as I'm an
OPS guy and not much involved in atoca or geopriv.

=20

Having been active in two Nomcoms, I am wondering what a useful
selection criteria for a Nomcom chair could be.

Having experience as a WG chair or having been active as Nomcom voting
member?

I can imagine a retired AD would enjoy it and do an excellent job in
this position.

=20

Cheers,=20
Mehmet=20

=20

From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of ext Lynn St.Amour
Sent: Tuesday, July 03, 2012 10:31 PM
To: IETF Announcement list
Subject: IETF Nominations Committee Chair - 2012 - 2013

=20

To the IETF community,

One of the roles you entrusted to the Internet Society (ISOC) President
& CEO is to appoint the IETF Nominations Committee chair.   This is done
through consultation with the IETF community.

It gives me great pleasure to announce that Matt Lepinski has agreed to
serve as the 2012 - 2013 IETF Nominations Committee chair.

A Call for Nominations for this committee will be sent to the IETF
Announcement list; and a list of the IESG, IAB and IAOC/IETF Trust seats
to be filled will be published shortly.   Please give serious
consideration to volunteering for the Nominations Committee as well as
to possible candidates for the open positions.=20

The NomComm process is central to the IETF's success, and it is
important that it have the support of the IETF community.   In the
interim, feel free to make your suggestions known to Matt, who will
share them with the committee once it is seated.   Matt can be reached
at: Matthew Lepinski <mlepinski.ietf@gmail.com>

Thank you in advance for your support and a sincere thank you to Matt
for agreeing to take on this very significant responsibility.

Regards,

Lynn St. Amour

President & CEO
Internet Society (ISOC)

=20

=20

=20


------_=_NextPart_001_01CD5A87.36DC1A59
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Verdana","sans-serif";
	color:blue;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>&gt; I =
sincerely thank Matt for his willingness to take on this task as it =
requires a tremendous time commitment and dedication to do =
well.<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
+1. It is indeed a huge effort for the Nomcom chair and all voting =
members especially between September and =
January.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Cheers,</span><span lang=3DDE =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:blue'>=
 <br></span><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Mehmet</span><span lang=3DDE =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:blue'>=
 <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
<o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-left:solid =
blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ext Mary Barnes [mailto:mary.ietf.barnes@gmail.com] <br><b>Sent:</b> =
Wednesday, July 04, 2012 7:24 PM<br><b>To:</b> Ersue, Mehmet (NSN - =
DE/Munich)<br><b>Cc:</b> ietf@ietf.org; ext Lynn =
St.Amour<br><b>Subject:</b> Re: IETF Nominations Committee Chair - 2012 =
- 2013<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Mehmet,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>In my experience, the most important characteristic =
for a nomcom chair is the ability to lead a group of 10 volunteers =
(usually with a significant variation of experience in IETF) through the =
process as defined by RFC &nbsp;3777 (and 5680). &nbsp; &nbsp;It can be =
good for a chair to have past Nomcom experience, but I do not believe =
that is a hard requirement (I had never served on a Nomcom before I was =
chair). &nbsp;It can be good for a Nomcom chair to have been a WG chair =
as they can understand more about the process. BUT, the chair is not the =
decision maker - the voting members are - the most important thing is =
for the chair to be able to facilitate the process as defined. =
&nbsp;It's far more important for the voting members to have that =
knowledge than the chair. &nbsp; Now, it can be more challenging if a =
chair hasn't been involved in IETF for a while, but AFAIK, Matt has been =
involved in the RAI area (as a participant/contributor) for a while and =
if you google you can find he's also been involved in the Security area =
on the SECDIR. You can see the work he's been involved in here in =
authorstats:<o:p></o:p></p></div><div><p class=3DMsoNormal><a =
href=3D"http://www.arkko.com/tools/allstats/mattlepinski.html">http://www=
.arkko.com/tools/allstats/mattlepinski.html</a><o:p></o:p></p></div><div>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Honestly, one of the most important aspect of the =
Nomcom process is for the Nomcom to get community feedback. You can read =
my report from 2009-2010 and that is an issue as the information that =
the nomcom is working with typically is extremely incomplete. &nbsp;Many =
nomcom voting members have little experience with interviewing and =
hiring &quot;employees&quot;. &nbsp;You also have to keep in mind that =
the past Nomcom chair serves as an advisor for the current Nomcom chair, =
which dramatically reduces the risk in the case that the appointed chair =
runs into problems.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
sincerely thank Matt for his willingness to take on this task as it =
requires a tremendous time commitment and dedication to do =
well.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Regards,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Mary.&nbsp;<o:p></o:p></p></div><div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Wed, =
Jul 4, 2012 at 4:18 AM, Ersue, Mehmet (NSN - DE/Munich) &lt;<a =
href=3D"mailto:mehmet.ersue@nsn.com" =
target=3D"_blank">mehmet.ersue@nsn.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Hi,</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
it&#8217;s time again for Nomcom. Congrats and good luck to Matt =
Lepinski.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
I have to admit I don&#8217;t know him. I assume this is my issue as =
I&#8217;m an OPS guy and not much involved in atoca or =
geopriv.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Having been active in two Nomcoms, I am wondering what a useful =
selection criteria for a Nomcom chair could be.</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Having experience as a WG chair or having been active as Nomcom voting =
member?</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
I can imagine a retired AD would enjoy it and do an excellent job in =
this position.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
&nbsp;</span><o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Cheers,</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:blue'>=
 <br></span><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
Mehmet</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:blue'>=
 </span><o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'font-size:10.0pt;font-family:"Verdana","sans-serif";color:blue'>=
&nbsp;</span><o:p></o:p></p><div style=3D'border:none;border-left:solid =
blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a href=3D"mailto:ietf-announce-bounces@ietf.org" =
target=3D"_blank">ietf-announce-bounces@ietf.org</a> [mailto:<a =
href=3D"mailto:ietf-announce-bounces@ietf.org" =
target=3D"_blank">ietf-announce-bounces@ietf.org</a>] <b>On Behalf Of =
</b>ext Lynn St.Amour<br><b>Sent:</b> Tuesday, July 03, 2012 10:31 =
PM<br><b>To:</b> IETF Announcement list<br><b>Subject:</b> IETF =
Nominations Committee Chair - 2012 - =
2013</span><o:p></o:p></p></div></div><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><div><div><div><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'>To the IETF =
community,<br><br>One of the roles you entrusted to the Internet Society =
(ISOC) President &amp; CEO is to appoint the IETF Nominations Committee =
chair. &nbsp;&nbsp;This is done through consultation with the IETF =
community.<br><br>It gives me great pleasure to announce that Matt =
Lepinski has agreed to serve as the 2012 - 2013 IETF Nominations =
Committee chair.<br><br>A Call for Nominations for this committee will =
be sent to the IETF Announcement list; and a list of the IESG, IAB and =
IAOC/IETF Trust seats to be filled will be published shortly. =
&nbsp;&nbsp;Please give serious consideration to volunteering for the =
Nominations Committee as well as to possible candidates for the open =
positions. <br><br>The NomComm process is central to the IETF's success, =
and it is important that it have the support of the IETF community. =
&nbsp;&nbsp;In the interim, feel free to make your suggestions known to =
Matt, who will share them with the committee once it is seated. =
&nbsp;&nbsp;Matt can be reached at: Matthew Lepinski &lt;<a =
href=3D"mailto:mlepinski.ietf@gmail.com" =
target=3D"_blank">mlepinski.ietf@gmail.com</a>&gt;<br><br>Thank you in =
advance for your support and a sincere thank you to Matt for agreeing to =
take on this very significant =
responsibility.<br><br>Regards,<br><br>Lynn St. Amour<br><br>President =
&amp; CEO<br>Internet Society (ISOC)<o:p></o:p></p></div></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div></div></div></div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div></div></div></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></body></h=
tml>
------_=_NextPart_001_01CD5A87.36DC1A59--

From abdussalambaryun@gmail.com  Thu Jul  5 04:32: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 CCA0C21F85BB for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 04:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.453
X-Spam-Level: 
X-Spam-Status: No, score=-3.453 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LREaj-BT8vGU for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 04:32: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 9A64E21F85AA for <ietf@ietf.org>; Thu,  5 Jul 2012 04:32:14 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so5904682vbb.31 for <ietf@ietf.org>; Thu, 05 Jul 2012 04:32:27 -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 :content-transfer-encoding; bh=pp8kGclcV4R9pN3R9KeusRahzXYnLBJWhBDrsYbXOms=; b=Qpojl0mSGgiw6BnqU/F8KwpaRjyk6+CbT6h/kS0m4IY0BUT+aRnVCQCzmg5KH5OFmk BWWn96WQTuBMt72wgQY3Dy+QrzaOXRj/p5MRC4X3xBs6LkoJaLEzTKYV0/PgtNhcD/Bl +1U6YirAkiMjg67T7af739itTrA39mbrSOtMwt7/p45mrGTW5n35A+iS21SABwBbtOWX 13Psr399oOqU/5xB6XmVln6j3hFEf7aLuRauVwCDDjPtF8lAXWUqog+skCpGLXX+eiyZ qBYOLulv9V1rYfCVKYsXMNTcT5+5++4h1IijMAOCSkjB8ji/weDorx+LsxmFDAR0Uni0 t3gQ==
MIME-Version: 1.0
Received: by 10.52.90.196 with SMTP id by4mr10368235vdb.103.1341487947700; Thu, 05 Jul 2012 04:32:27 -0700 (PDT)
Received: by 10.220.110.130 with HTTP; Thu, 5 Jul 2012 04:32:27 -0700 (PDT)
Date: Thu, 5 Jul 2012 13:32:27 +0200
Message-ID: <CADnDZ8_XqN5SK+4nmJE4iTo96X-s9fy8cth_hFEUgWNG9+9+ug@mail.gmail.com>
Subject: Re: IETF Nominations Committee Chair - 2012 - 2013
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: mary.ietf.barnes@gmail.com
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: ietf <ietf@ietf.org>, mlepinski.ietf@gmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2012 11:32:15 -0000

+1

I agree to work with you, internet community and Mr.Matthew Lepinski,
to progress the process for nominations, and make it successful,

AB
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
If people work together as a team, best practices and success are reached
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>
> Mehmet,
>
>
> In my experience, the most important characteristic for a nomcom chair
> is the ability to lead a group of 10 volunteers (usually with a
> significant variation of experience in IETF) through the process as
> defined by RFC  3777 (and 5680).    It can be good for a chair to have
> past Nomcom experience, but I do not believe that is a hard
> requirement (I had never served on a Nomcom before I was chair).  It
> can be good for a Nomcom chair to have been a WG chair as they can
> understand more about the process. BUT, the chair is not the decision
> maker - the voting members are - the most important thing is for the
> chair to be able to facilitate the process as defined.  It's far more
> important for the voting members to have that knowledge than the
> chair.   Now, it can be more challenging if a chair hasn't been
> involved in IETF for a while, but AFAIK, Matt has been involved in the
> RAI area (as a participant/contributor) for a while and if you google
> you can find he's also been involved in the Security area on the
> SECDIR. You can see the work he's been involved in here in
> authorstats:
> http://www.arkko.com/tools/allstats/mattlepinski.html
>
>
> Honestly, one of the most important aspect of the Nomcom process is
> for the Nomcom to get community feedback. You can read my report from
> 2009-2010 and that is an issue as the information that the nomcom is
> working with typically is extremely incomplete.  Many nomcom voting
> members have little experience with interviewing and hiring
> "employees".  You also have to keep in mind that the past Nomcom chair
> serves as an advisor for the current Nomcom chair, which dramatically
> reduces the risk in the case that the appointed chair runs into
> problems.
>
>
> I sincerely thank Matt for his willingness to take on this task as it
> requires a tremendous time commitment and dedication to do well.
>
>
> Regards,
> Mary.
>
>
> On Wed, Jul 4, 2012 at 4:18 AM, Ersue, Mehmet (NSN - DE/Munich)
> <mehmet.ersue at nsn.com> wrote:
>
> Hi,
>
>
>
> it=92s time again for Nomcom. Congrats and good luck to Matt Lepinski.
>
> I have to admit I don=92t know him. I assume this is my issue as I=92m an
> OPS guy and not much involved in atoca or geopriv.
>
>
>
> Having been active in two Nomcoms, I am wondering what a useful
> selection criteria for a Nomcom chair could be.
>
> Having experience as a WG chair or having been active as Nomcom voting
> member?
>
> I can imagine a retired AD would enjoy it and do an excellent job in
> this position.
>
>
>
> Cheers,
> Mehmet
>

From john-ietf@jck.com  Thu Jul  5 07:43:28 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD96A21F84C9 for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 07:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aM2PllOptIiL for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 07:43:27 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 66ACE21F8554 for <ietf@ietf.org>; Thu,  5 Jul 2012 07:43:27 -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 1SmnCQ-0007Wm-Us for ietf@ietf.org; Thu, 05 Jul 2012 10:38:30 -0400
Date: Thu, 05 Jul 2012 10:43:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the	"Tao of the IETF" as a Web Page) to Informational RFC
Message-ID: <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com>
In-Reply-To: <20120615202915.11032.53296.idtracker@ietfa.amsl.com>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2012 14:43:29 -0000

--On Friday, June 15, 2012 13:29 -0700 The IESG
<iesg-secretary@ietf.org> wrote:

> The IESG has received a request from an individual submitter
> to consider the following document:
> - 'Publishing the "Tao of the IETF" as a Web Page'
>   <draft-hoffman-tao-as-web-page-02.txt> as Informational RFC

> The IESG plans to make a decision in the next few weeks, and
> solicits final comments on this action. Please send
> substantive comments to the ietf@ietf.org mailing lists by
> 2012-07-13.

Hi.

Just to make a pair of comments that I've sort of made in other
contexts in the particular context of the Last Call.   I won't
repeat the details.

(1) As a general strategy, doing the Tao as a web page seems
like exactly the right thing to do.  Some sort of staging
process and opportunity for review of working drafts by the
community as well as the IETF seems important.  As far as I can
tell, the document covers that adequately although some details
are not spelled out as well as some would perhaps prefer.

(2) The document itself mixes a historical discussion of how
things got to where they are with what is being done going
forward.   I believe it would be desirable to more clearly
separate that material, into either separate documents or into a
brief core document that focuses of the three questions of "what
is the Tao", "where can it be found", and "what is the revision/
update procedure" and an appendix that includes whatever else is
determined to be necessary.  In that regard, the abstract of the
core (or only) document should not concentrate on when
discussions occurred, etc., but simply on what the Tao is and
why it might be useful.  Liberal borrowing from the abstract of
RFC 4677 (or just copying it) would be, IMO, quite appropriate.  

This is less of a problem than it might otherwise be because the
document is so short, but a document that obsoletes RFC 4677 and
its predecessors should address the substances addressed by
4677, not serve as a historical summary of a few months of
community discussion.

Nits: 
(i) In recent years, the IESG has insisted on specific
documentation when one RFC obsoletes another.  This draft does
not mention the "obsoletes" relationship in the Abstract,
Introduction, or any other prominent place.

(ii) Second paragraph of current Introduction, first sentence,
should contain "discussion that led..." rather than "discussion
that lead...".  I believe that paragraph is part of the
historical discussion that belongs somewhere else.

thanks,
   john


From paul.hoffman@vpnc.org  Thu Jul  5 14:18:58 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 298E321F858A for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 14:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2VFsQ+457pO for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 14:18:57 -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 61B9C21F8547 for <ietf@ietf.org>; Thu,  5 Jul 2012 14:18:57 -0700 (PDT)
Received: from [10.20.30.102] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q65LJ8PU034145 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 5 Jul 2012 14:19:09 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the	"Tao of the IETF" as a Web Page) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com>
Date: Thu, 5 Jul 2012 14:19:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1278)
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, 05 Jul 2012 21:18:58 -0000

Based on many people's input (most recently, John's), I have updated the =
draft to more cleanly separate out the history of the Tao from the =
change that is happening.

--Paul Hoffman


A new version of I-D, draft-hoffman-tao-as-web-page-03.txt
has been successfully submitted by Paul Hoffman and posted to the
IETF repository.

Filename:	 draft-hoffman-tao-as-web-page
Revision:	 03
Title:		 Publishing the "Tao of the IETF" as a Web Page
Creation date:	 2012-07-05
WG ID:		 Individual Submission
Number of pages: 3
URL:             =
http://www.ietf.org/internet-drafts/draft-hoffman-tao-as-web-page-03.txt
Status:          =
http://datatracker.ietf.org/doc/draft-hoffman-tao-as-web-page
Htmlized:        =
http://tools.ietf.org/html/draft-hoffman-tao-as-web-page-03
Diff:            =
http://tools.ietf.org/rfcdiff?url2=3Ddraft-hoffman-tao-as-web-page-03

Abstract:
  This document describes how the "Tao of the IETF", which has been
  published as a series of RFCs in the past, will instead be published
  as a web page.


From john-ietf@jck.com  Thu Jul  5 14:34:54 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 DDBD221F864E for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 14:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PE8zA+V7kRjQ for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 14:34:54 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 336EA21F864D for <ietf@ietf.org>; Thu,  5 Jul 2012 14:34:54 -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 1Smtcb-00089j-V9; Thu, 05 Jul 2012 17:29:57 -0400
Date: Thu, 05 Jul 2012 17:34:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the	"Tao of the IETF" as a Web Page) to Informational RFC
Message-ID: <0055B78D874058F9ECEC6E10@JcK-HP8200.jck.com>
In-Reply-To: <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com> <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.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: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2012 21:34:55 -0000

--On Thursday, July 05, 2012 14:19 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

> Based on many people's input (most recently, John's), I have
> updated the draft to more cleanly separate out the history of
> the Tao from the change that is happening.

Paul,

While I'd prefer to see you go even further in that direction
(e.g., incorporating more of the RFC 4677 Abstract in this
abstract, constructing things so that changes in the details of
editing procedures doesn't require a revised RFC), this version
is, IMO, greatly improved.

thanks
   john



From tony@att.com  Thu Jul  5 14:46:14 2012
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4943221F865D for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 14:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ruZtiaILmL39 for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 14:46:13 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 67CD521F8653 for <ietf@ietf.org>; Thu,  5 Jul 2012 14:46:13 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 33b06ff4.0.396691.00-333.1070353.nbfkord-smmo07.seg.att.com (envelope-from <tony@att.com>);  Thu, 05 Jul 2012 21:46:28 +0000 (UTC)
X-MXL-Hash: 4ff60b341e72e5ec-7e10ca789386ff8ba3c380cff6935dd51706d0c8
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q65LkRAO020328 for <ietf@ietf.org>; Thu, 5 Jul 2012 17:46:27 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q65LkML8020279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 5 Jul 2012 17:46:22 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <ietf@ietf.org>; Thu, 5 Jul 2012 17:46:06 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q65Lk4u1012674 for <ietf@ietf.org>; Thu, 5 Jul 2012 17:46:05 -0400
Received: from mailgw1.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q65Lk0UO012322 for <ietf@ietf.org>; Thu, 5 Jul 2012 17:46:00 -0400
Received: from [135.91.110.142] (dn135-91-110-142.dhcpn.ugn.att.com[135.91.110.142]) by maillennium.att.com (mailgw1) with ESMTP id <20120705214150gw10060ltde> (Authid: tony); Thu, 5 Jul 2012 21:41:50 +0000
X-Originating-IP: [135.91.110.142]
Message-ID: <4FF60B17.1060600@att.com>
Date: Thu, 05 Jul 2012 17:45:59 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com> <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org>
In-Reply-To: <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=kKemRe_CjxUA:10 a=cgbV5Ep4loIA:10 a=djGLZF5izP]
X-AnalysisOut: [IA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:1]
X-AnalysisOut: [0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a=48vgC7mUAAAA:8 a=zQP7CpK]
X-AnalysisOut: [OAAAA:8 a=MKMf8MLE5J7xGxQKYugA:9 a=wPNLvfGTeEIA:10 a=2mLzD]
X-AnalysisOut: [uUFM-0A:10 a=Hz7IrDYlS0cA:10]
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, 05 Jul 2012 21:46:14 -0000

I've read this version and think it's an excellent revision.

Is there going to be a way of seeing a list of all the versions of the 
tao? Or links within tao.html to the previous version? Perhaps a 
www.ietf.org/tao/ should be maintained that has pointers to all the 
versions as well any proposed update.

     Tony Hansen
     tony@att.com

On 7/5/2012 5:19 PM, Paul Hoffman wrote:
> Based on many people's input (most recently, John's), I have updated the draft to more cleanly separate out the history of the Tao from the change that is happening.

From paul.hoffman@vpnc.org  Thu Jul  5 15:02:27 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 1218611E80D5 for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 15:02:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hyD7XnN9RJyg for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 15:02:26 -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 7B7D711E80AA for <ietf@ietf.org>; Thu,  5 Jul 2012 15:02:26 -0700 (PDT)
Received: from [10.20.30.102] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97] (may be forged)) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q65M2bJV040227 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 5 Jul 2012 15:02:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4FF60B17.1060600@att.com>
Date: Thu, 5 Jul 2012 15:02:37 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CAFCD98A-246D-482C-B8CD-6875D49ED94F@vpnc.org>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com> <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org> <4FF60B17.1060600@att.com>
To: Tony Hansen <tony@att.com>
X-Mailer: Apple Mail (2.1278)
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, 05 Jul 2012 22:02:27 -0000

On Jul 5, 2012, at 2:45 PM, Tony Hansen wrote:

> Is there going to be a way of seeing a list of all the versions of the =
tao? Or links within tao.html to the previous version? Perhaps a =
www.ietf.org/tao/ should be maintained that has pointers to all the =
versions as well any proposed update.


I think the Tao web page should point to RFC 4677 in a "well, how did I =
get here?" section, given that this is not the same as it ever was.

--Paul Hoffman


From tony@att.com  Thu Jul  5 20:22:40 2012
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0A0311E8095 for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 20:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WOqYM+K3A9U1 for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 20:22:39 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id ED9DA11E8073 for <ietf@ietf.org>; Thu,  5 Jul 2012 20:22:38 -0700 (PDT)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id d0a56ff4.0.1219994.00-495.3330728.nbfkord-smmo06.seg.att.com (envelope-from <tony@att.com>);  Fri, 06 Jul 2012 03:22:54 +0000 (UTC)
X-MXL-Hash: 4ff65a0e7411afcb-86ae353d258e9846fc6d6563f8778bb3698eeb9b
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q663MqV8001129 for <ietf@ietf.org>; Thu, 5 Jul 2012 20:22:53 -0700
Received: from fflint04.pst.cso.att.com (fflint04.pst.cso.att.com [150.234.39.64]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q663MgTS000977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 5 Jul 2012 20:22:47 -0700
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by fflint04.pst.cso.att.com (RSA Interceptor) for <ietf@ietf.org>; Thu, 5 Jul 2012 20:22:34 -0700
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q663MXRZ008902 for <ietf@ietf.org>; Thu, 5 Jul 2012 23:22:34 -0400
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q663MQiU008744 for <ietf@ietf.org>; Thu, 5 Jul 2012 23:22:27 -0400
Received: from [135.70.75.23] (vpn-135-70-75-23.vpn.swst.att.com[135.70.75.23]) by maillennium.att.com (mailgw1) with ESMTP id <20120706031816gw10060ltge> (Authid: tony); Fri, 6 Jul 2012 03:18:17 +0000
X-Originating-IP: [135.70.75.23]
Message-ID: <4FF659F0.1020104@att.com>
Date: Thu, 05 Jul 2012 23:22:24 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com> <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org> <4FF60B17.1060600@att.com> <CAFCD98A-246D-482C-B8CD-6875D49ED94F@vpnc.org>
In-Reply-To: <CAFCD98A-246D-482C-B8CD-6875D49ED94F@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=1.0 c=1 a=gpx8--TvblYA:10 a=cgbV5Ep4loIA:10 a=djGLZF5izP]
X-AnalysisOut: [IA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:1]
X-AnalysisOut: [0 a=xwOvzTHDVLE4u4nGvK72ag==:17 a=48vgC7mUAAAA:8 a=jUNm-l5]
X-AnalysisOut: [8s-UOBSoABZsA:9 a=wPNLvfGTeEIA:10 a=5IhAZet7BUoA:10]
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, 06 Jul 2012 03:22:40 -0000

I think my point was missed. Section 2 says:

All published versions will be archived using URLs of the form 
<http://www.ietf.org/tao-YYYYMMDD.html>.

My question is: Where is there a list of all of the tao version files? 
How would one be able to find out the name of the previous version so 
they could do a diff and see what has changed? How can I see a history 
of the files?

Here is a suggested addition to section 2:

     Each version of the Tao will also have a link to a history page of 
all versions.

Or something like that. The mechanics what that page looks like can be 
determined later -- it doesn't really matter right now, nor does it 
matter right now what the address is.

     Tony Hansen

On 7/5/2012 6:02 PM, Paul Hoffman wrote:
> On Jul 5, 2012, at 2:45 PM, Tony Hansen wrote:
>
>> Is there going to be a way of seeing a list of all the versions of the tao? Or links within tao.html to the previous version? Perhaps a www.ietf.org/tao/ should be maintained that has pointers to all the versions as well any proposed update.
>
> I think the Tao web page should point to RFC 4677 in a "well, how did I get here?" section, given that this is not the same as it ever was.

From john-ietf@jck.com  Thu Jul  5 20:57: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 DB1C121F8720 for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 20:57:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ah+81KXWZzDy for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 20:57:36 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3152821F871C for <ietf@ietf.org>; Thu,  5 Jul 2012 20:57: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 1Smzaw-0008YF-CI; Thu, 05 Jul 2012 23:52:38 -0400
Date: Thu, 05 Jul 2012 23:57:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tony Hansen <tony@att.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing	the "Tao of the IETF" as a Web Page) to Informational RFC
Message-ID: <9DF09405CDDF0E625FA03977@JcK-HP8200.jck.com>
In-Reply-To: <4FF659F0.1020104@att.com>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com> <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org> <4FF60B17.1060600@att.com> <CAFCD98A-246D-482C-B8CD-6875D49ED94F@vpnc.org> <4FF659F0.1020104@att.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 03:57:37 -0000

--On Thursday, July 05, 2012 23:22 -0400 Tony Hansen
<tony@att.com> wrote:

> I think my point was missed. Section 2 says:
> 
> All published versions will be archived using URLs of the form
> <http://www.ietf.org/tao-YYYYMMDD.html>.
> 
> My question is: Where is there a list of all of the tao
> version files? How would one be able to find out the name of
> the previous version so they could do a diff and see what has
> changed? How can I see a history of the files?
>...

Tony,

Mostly out of curiosity, why do you think it is important.   If
the Tao were a reference document that was authoritative on IETF
procedures or the like, it would be a different matter: I can
think of many reasons why it might be important to establish
exactly what the rules and procedures were at any given time.
But, given that it is a non-authoritative tutorial summary
description of how we do things, I have a certain amount of
trouble understanding why going to extra effort to maintain a
long-term back trace is actually important.

What am I missing?

    john


From tony@att.com  Thu Jul  5 21:29:03 2012
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09A2F11E809A for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 21:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gx5RwmDszWuj for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 21:29:02 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 1049511E808D for <ietf@ietf.org>; Thu,  5 Jul 2012 21:29:01 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id c9966ff4.0.1209519.00-450.3325220.nbfkord-smmo05.seg.att.com (envelope-from <tony@att.com>);  Fri, 06 Jul 2012 04:29:17 +0000 (UTC)
X-MXL-Hash: 4ff6699d295e890d-59e3acf5840743a0c537832b88ae2547fb41b4a8
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q664TGsi015105 for <ietf@ietf.org>; Fri, 6 Jul 2012 00:29:16 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q664TBse015102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 6 Jul 2012 00:29:12 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <ietf@ietf.org>; Fri, 6 Jul 2012 00:28:59 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q664Sxqn005088 for <ietf@ietf.org>; Fri, 6 Jul 2012 00:28:59 -0400
Received: from mailgw1.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q664SrsZ005018 for <ietf@ietf.org>; Fri, 6 Jul 2012 00:28:54 -0400
Received: from [135.70.75.23] (vpn-135-70-75-23.vpn.swst.att.com[135.70.75.23]) by maillennium.att.com (mailgw1) with ESMTP id <20120706042442gw10060lthe> (Authid: tony); Fri, 6 Jul 2012 04:24:43 +0000
X-Originating-IP: [135.70.75.23]
Message-ID: <4FF66982.70308@att.com>
Date: Fri, 06 Jul 2012 00:28:50 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com> <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org> <4FF60B17.1060600@att.com> <CAFCD98A-246D-482C-B8CD-6875D49ED94F@vpnc.org> <4FF659F0.1020104@att.com> <9DF09405CDDF0E625FA03977@JcK-HP8200.jck.com>
In-Reply-To: <9DF09405CDDF0E625FA03977@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=gpx8--TvblYA:10 a=cgbV5Ep4loIA:10 a=djGLZF5izP]
X-AnalysisOut: [IA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:1]
X-AnalysisOut: [0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a=zQP7CpKOAAAA:8 a=48vgC7m]
X-AnalysisOut: [UAAAA:8 a=gS9mA5k4ELG0p3x88G0A:9 a=wPNLvfGTeEIA:10 a=5IhAZ]
X-AnalysisOut: [et7BUoA:10 a=Hz7IrDYlS0cA:10]
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, 06 Jul 2012 04:29:03 -0000

Authoritative, no. But definitely referenced by many, many people and 
IMO worthy of a certain amount of care.

     Tony Hansen

On 7/5/2012 11:57 PM, John C Klensin wrote:
> --On Thursday, July 05, 2012 23:22 -0400 Tony Hansen
> <tony@att.com> wrote:
>
>> I think my point was missed. Section 2 says:
>>
>> All published versions will be archived using URLs of the form
>> <http://www.ietf.org/tao-YYYYMMDD.html>.
>>
>> My question is: Where is there a list of all of the tao
>> version files? How would one be able to find out the name of
>> the previous version so they could do a diff and see what has
>> changed? How can I see a history of the files?
>> ...
> Tony,
>
> Mostly out of curiosity, why do you think it is important.   If
> the Tao were a reference document that was authoritative on IETF
> procedures or the like, it would be a different matter: I can
> think of many reasons why it might be important to establish
> exactly what the rules and procedures were at any given time.
> But, given that it is a non-authoritative tutorial summary
> description of how we do things, I have a certain amount of
> trouble understanding why going to extra effort to maintain a
> long-term back trace is actually important.
>
> What am I missing?
>
>      john
>



From narten@us.ibm.com  Thu Jul  5 21:53:39 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 46DE521F873E for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 21:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TeGRBa4jU8QN for <ietf@ietfa.amsl.com>; Thu,  5 Jul 2012 21:53:38 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by ietfa.amsl.com (Postfix) with ESMTP id 3C99121F873D for <ietf@ietf.org>; Thu,  5 Jul 2012 21:53:38 -0700 (PDT)
Received: from /spool/local by e38.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, 5 Jul 2012 22:53:53 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 5 Jul 2012 22:53:51 -0600
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 8BC7C3E40054 for <ietf@ietf.org>; Fri,  6 Jul 2012 04:53:50 +0000 (WET)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q664rJXU271274 for <ietf@ietf.org>; Thu, 5 Jul 2012 22:53:35 -0600
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q664r42R002442 for <ietf@ietf.org>; Thu, 5 Jul 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q664r3U4002439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 5 Jul 2012 22:53:04 -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 q664r3wT002247 for <ietf@ietf.org>; Fri, 6 Jul 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q664r2VZ002233 for ietf@ietf.org; Fri, 6 Jul 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201207060453.q664r2VZ002233@rotala.raleigh.ibm.com>
Date: Fri, 06 Jul 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: 12070604-5518-0000-0000-000005CEAF78
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 04:53:39 -0000

Total of 41 messages in the last 7 days.
 
script run at: Fri Jul  6 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.32% |    3 | 12.21% |    44570 | mehmet.ersue@nsn.com
  7.32% |    3 | 11.14% |    40646 | abdussalambaryun@gmail.com
  7.32% |    3 |  9.25% |    33769 | david.black@emc.com
  7.32% |    3 |  5.15% |    18811 | housley@vigilsec.com
  7.32% |    3 |  5.01% |    18270 | john-ietf@jck.com
  4.88% |    2 |  6.16% |    22500 | alan.b.johnston@gmail.com
  4.88% |    2 |  4.17% |    15211 | tony@att.com
  4.88% |    2 |  3.54% |    12928 | joelja@bogus.com
  4.88% |    2 |  3.11% |    11368 | paul.hoffman@vpnc.org
  4.88% |    2 |  2.98% |    10872 | julian.reschke@gmx.de
  2.44% |    1 |  4.78% |    17462 | mary.ietf.barnes@gmail.com
  2.44% |    1 |  3.23% |    11790 | lars@netapp.com
  2.44% |    1 |  2.87% |    10461 | adrian@olddog.co.uk
  2.44% |    1 |  2.82% |    10275 | dirk.kutscher@neclab.eu
  2.44% |    1 |  2.64% |     9638 | stephen.farrell@cs.tcd.ie
  2.44% |    1 |  2.61% |     9514 | sm@resistor.net
  2.44% |    1 |  2.25% |     8209 | masahiro@isl.rdc.toshiba.co.jp
  2.44% |    1 |  2.23% |     8133 | duerst@it.aoyama.ac.jp
  2.44% |    1 |  2.18% |     7961 | narten@us.ibm.com
  2.44% |    1 |  1.89% |     6881 | dworley@avaya.com
  2.44% |    1 |  1.84% |     6717 | touch@isi.edu
  2.44% |    1 |  1.84% |     6707 | peter@akayla.com
  2.44% |    1 |  1.67% |     6085 | alexey.melnikov@isode.com
  2.44% |    1 |  1.61% |     5862 | johnl@taugh.com
  2.44% |    1 |  1.51% |     5503 | ben@nostrum.com
  2.44% |    1 |  1.33% |     4857 | randy@psg.com
--------+------+--------+----------+------------------------
100.00% |   41 |100.00% |   365000 | Total


From abdussalambaryun@gmail.com  Thu Jul  5 22:16:19 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 2B97821F87E4; Thu,  5 Jul 2012 22:16:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.464
X-Spam-Level: 
X-Spam-Status: No, score=-3.464 tagged_above=-999 required=5 tests=[AWL=0.135,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jFsyVLxbkmfX; Thu,  5 Jul 2012 22:16:18 -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 0095921F87E0; Thu,  5 Jul 2012 22:16:17 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so6446284vcq.31 for <multiple recipients>; Thu, 05 Jul 2012 22:16:33 -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=YycPJoQrjLEA8iAGzexnxeHUbLPX3CHokplDnvM2/cE=; b=xf9v0ur7ilUB4SUH0Z4LWSXJSqTHSriDX2B97JZE9SpmDhSZzDNLzcPmxsGy7Pe82Q ANxCBlg/dk4V3ZFP2bTJQCQZqfvwJ+r8rStfnDfaGITmp0vGhBufLP3H/jtfh+QXbnGO XpM7aQ4VURhGr2nGsSFDAYQuO98eedKhaztLi8T8kCHQHFEH5YXRBNz7w9PpftwlAkTY +s+NGvLFHVYOeXHWKXPc5Q0AXz2t+7vGjBm3CnSVSo2gVVT1NKWtPDsELxqqp3BEjVB7 CIFMnuPTNGmE5VOimr+nC+owOjjI0sBu2nx4zrNjbdq5pui1YEaRTnNwRBr10X6tvAqK Hf/A==
MIME-Version: 1.0
Received: by 10.52.90.144 with SMTP id bw16mr11551710vdb.129.1341551793022; Thu, 05 Jul 2012 22:16:33 -0700 (PDT)
Received: by 10.220.110.130 with HTTP; Thu, 5 Jul 2012 22:16:33 -0700 (PDT)
Date: Fri, 6 Jul 2012 07:16:33 +0200
Message-ID: <CADnDZ8-hoTgc=Q4AW0E7L+UeKqMQ0HVpW-6gDUzSkDNGLuieEA@mail.gmail.com>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: john-ietf@jck.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@ietf.org" <iesg@ietf.org>, ietf <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 05:16:19 -0000

+1

I support all your suggestions (i.e. point 1 and 2, and nits i and ii
) , and hope that iesg, and editor agrees, and that the community
considers them for progress. I seen the change in the
draft-document-03 which I think getting better but still not satisfied

The new vesion 3 draft (dated 5 July) does not include all your
suggestion, please read and comment on draft-03 (the subject refers to
draft-02, did you read draft-03?).
http://tools.ietf.org/html/draft-hoffman-tao-as-web-page-03

AB
=============================================
My previous input to the subject:
+++++++++++++++++++++++
http://www.ietf.org/mail-archive/web/ietf/current/msg73771.html
http://www.ietf.org/mail-archive/web/ietf/current/msg73776.html
http://www.ietf.org/mail-archive/web/ietf/current/msg73781.html
http://www.ietf.org/mail-archive/web/ietf/current/msg73782.html
http://www.ietf.org/mail-archive/web/ietf/current/msg73791.html
==============================================
>
>> The IESG has received a request from an individual submitter
>> to consider the following document:
>> - 'Publishing the "Tao of the IETF" as a Web Page'
>>   <draft-hoffman-tao-as-web-page-02.txt> as Informational RFC
>
>> The IESG plans to make a decision in the next few weeks, and
>> solicits final comments on this action. Please send
>> substantive comments to the ietf at ietf.org mailing lists by
>> 2012-07-13.
>
> Hi.
>
> Just to make a pair of comments that I've sort of made in other
> contexts in the particular context of the Last Call.   I won't
> repeat the details.
>
> (1) As a general strategy, doing the Tao as a web page seems
> like exactly the right thing to do.  Some sort of staging
> process and opportunity for review of working drafts by the
> community as well as the IETF seems important.  As far as I can
> tell, the document covers that adequately although some details
> are not spelled out as well as some would perhaps prefer.
>
> (2) The document itself mixes a historical discussion of how
> things got to where they are with what is being done going
> forward.   I believe it would be desirable to more clearly
> separate that material, into either separate documents or into a
> brief core document that focuses of the three questions of "what
> is the Tao", "where can it be found", and "what is the revision/
> update procedure" and an appendix that includes whatever else is
> determined to be necessary.  In that regard, the abstract of the
> core (or only) document should not concentrate on when
> discussions occurred, etc., but simply on what the Tao is and
> why it might be useful.  Liberal borrowing from the abstract of
> RFC 4677 (or just copying it) would be, IMO, quite appropriate.
>
> This is less of a problem than it might otherwise be because the
> document is so short, but a document that obsoletes RFC 4677 and
> its predecessors should address the substances addressed by
> 4677, not serve as a historical summary of a few months of
> community discussion.
>
> Nits:
> (i) In recent years, the IESG has insisted on specific
> documentation when one RFC obsoletes another.  This draft does
> not mention the "obsoletes" relationship in the Abstract,
> Introduction, or any other prominent place.
>
> (ii) Second paragraph of current Introduction, first sentence,
> should contain "discussion that led..." rather than "discussion
> that lead...".  I believe that paragraph is part of the
> historical discussion that belongs somewhere else.
>
> thanks,
>    john
>

From john-ietf@jck.com  Fri Jul  6 04:04: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 76E6A21F8701 for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 04:04: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0uBKHbIjAqqy for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 04:04:32 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 52CF021F8739 for <ietf@ietf.org>; Fri,  6 Jul 2012 04:04:32 -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 1Sn6G7-0009Ff-RB; Fri, 06 Jul 2012 06:59:35 -0400
Date: Fri, 06 Jul 2012 07:04:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tony Hansen <tony@att.com>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
Message-ID: <25428E776486D6F2DF98C25B@JcK-HP8200.jck.com>
In-Reply-To: <4FF66982.70308@att.com>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com> <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org> <4FF60B17.1060600@att.com> <CAFCD98A-246D-482C-B8CD-6875D49ED94F@vpnc.org> <4FF659F0.1020104@att.com> <9DF09405CDDF0E625FA03977@JcK-HP8200.jck.com> <4FF66982.70308@att.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 11:04:36 -0000

--On Friday, July 06, 2012 00:28 -0400 Tony Hansen
<tony@att.com> wrote:

> Authoritative, no. But definitely referenced by many, many
> people and IMO worthy of a certain amount of care.

No disagreement about care.  But it seems to me that adequate
care requires keeping track of a future version, a current
version, and a previous version (or maybe two).   The ability to
easily find and trace back through the entire history of the
document seems appropriate for something normative but well
beyond what is required for reasonable care with a document like
this.

Just my opinion, however.  I have trouble convincing myself that
the issue is really important enough to hold things up.

    john


From sm@resistor.net  Fri Jul  6 04:16: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 E9ABF21F87A0 for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 04:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uz+EwnlCjt-p for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 04:16:36 -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 C012721F879F for <ietf@ietf.org>; Fri,  6 Jul 2012 04:16:36 -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 q66BGj25025267; Fri, 6 Jul 2012 04:16:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1341573410; bh=tU0kBadnA2V1KU2KLvqEROkWV450eT96ZOLDUR0Dhuw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=EclpFkDKpAPlQp/q49aTqlEVSevwhkGqEvt2JvNtdtTMooYqtsyLerWImdp5aUMtU 8xeUAKbPvomLYzNiTs9t2VmrDRbhEkGTsBDtElMJzJh5Y8kBy1P4nwdGk1nTncR/8x OBE5BL5TWWC/glICvb96Iv8V1IsQaX80mQsqB2E0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1341573410; i=@resistor.net; bh=tU0kBadnA2V1KU2KLvqEROkWV450eT96ZOLDUR0Dhuw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=IZN/0pCejudeiKpQruQNmnalpKTvveo3PGJYR2DR6iuhvT6XsFwfdOaxBZdYmdcd8 qDmrmJkk29qnlTAyeU1qEXU5zvFiO4NMUdylYJhSfAbCf9CNAkicbhH70s1JUOEKZp ioLhlaWlPeBZF/IezdwXPq70mgiZH5kmVj8fkX2Q=
Message-Id: <6.2.5.6.2.20120706034122.0c180188@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 06 Jul 2012 04:12:37 -0700
To: Tony Hansen <tony@att.com>, Paul Hoffman <paul.hoffman@vpnc.org>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
In-Reply-To: <4FF659F0.1020104@att.com>
References: <20120615202915.11032.53296.idtracker@ietfa.amsl.com> <6F9AF4A4C9466A87A81F1823@JcK-HP8200.jck.com> <F404FCF4-3E55-4F5B-A17C-B6D85C84824C@vpnc.org> <4FF60B17.1060600@att.com> <CAFCD98A-246D-482C-B8CD-6875D49ED94F@vpnc.org> <4FF659F0.1020104@att.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, 06 Jul 2012 11:16:41 -0000

At 20:22 05-07-2012, Tony Hansen wrote:
>I think my point was missed. Section 2 says:
>
>All published versions will be archived using URLs of the form 
><http://www.ietf.org/tao-YYYYMMDD.html>.
>
>My question is: Where is there a list of all of the tao version 
>files? How would one be able to find out the name of the previous 
>version so they could do a diff and see what has changed? How can I 
>see a history of the files?

The interesting question is at 
http://www.ietf.org/mail-archive/web/ietf/current/msg73889.html  I 
did not ask Julian whether he was thinking about cool URIs [1].  The 
information about common HTTP implementation problems [2] may be 
relevant to the discussion.  After I read the message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg73892.html I 
could not understand why it was not possible as there is mod_rewrite.

I don't think that all this is important in a draft which is about of 
a tutorial.

Regards,
-sm

1. http://www.w3.org/Provider/Style/URI
2. http://www.w3.org/TR/chips/ 


From john-ietf@jck.com  Fri Jul  6 04:23:53 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 C89C621F8707 for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 04:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bDVs50VuE40z for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 04:23:53 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 719EC21F86FD for <ietf@ietf.org>; Fri,  6 Jul 2012 04:23: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 1Sn6Yk-0009Gw-SM; Fri, 06 Jul 2012 07:18:50 -0400
Date: Fri, 06 Jul 2012 07:23:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
Message-ID: <337C9F850CBEA220D0A03ED3@JcK-HP8200.jck.com>
In-Reply-To: <CADnDZ8-hoTgc=Q4AW0E7L+UeKqMQ0HVpW-6gDUzSkDNGLuieEA@mail.gmail.com>
References: <CADnDZ8-hoTgc=Q4AW0E7L+UeKqMQ0HVpW-6gDUzSkDNGLuieEA@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: Fri, 06 Jul 2012 11:23:53 -0000

--On Friday, July 06, 2012 07:16 +0200 Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:

> +1
> 
> I support all your suggestions (i.e. point 1 and 2, and nits i
> and ii ) , and hope that iesg, and editor agrees, and that the
> community considers them for progress. I seen the change in the
> draft-document-03 which I think getting better but still not
> satisfied
> 
> The new vesion 3 draft (dated 5 July) does not include all your
> suggestion, please read and comment on draft-03 (the subject
> refers to draft-02, did you read draft-03?).
> http://tools.ietf.org/html/draft-hoffman-tao-as-web-page-03

Abdussalam,

Paul's note about draft 03 indicates that he posted it partially
in response to my comments.  Those comments were based on 02.
>From my point of view, there is always a question about how much
energy a document like this is worth: it is not normative or
authoritative and, while I'd prefer to see it done differently
(and said so in a follow-up note after skimming -03), I've got
other IETF work to do and would prefer to see Paul and the IESG
working on the Tao text itself rather than fine-tuning this
document.

I personally believe that the document could be further improved
by moving it toward my earlier suggestions.   I believe that
more "what is this about" text belong in the Abstract and, in
particular, that the relationship of the Tao (whether as an RFC
or as a web page) deserves more explicit treatment than the
second sentence of the Introduction.  And I believe that forcing
another RFC if details of the revision process are changed is a
bad idea and so think that Section 2 (of -03) should talk about
an initial procedure and/or in much more general terms but
should then push details and changes off to the Tao itself
(perhaps as an appendix).  Ultimately, if we cannot trust the
IESG and the Editor to be careful and sensible about this
document, we are going to have problems that fine-tuning the RFC
text can't prevent.

But, if Paul and the IESG don't agree, I'm not convinced the
subject justifies a lot more energy.

best,
   john


From wesley.george@twcable.com  Fri Jul  6 09:51:06 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54F0E21F8600; Fri,  6 Jul 2012 09:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.195
X-Spam-Level: 
X-Spam-Status: No, score=-1.195 tagged_above=-999 required=5 tests=[AWL=0.268,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZgoDYlnpJ5A; Fri,  6 Jul 2012 09:51:05 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id F29E721F85C7; Fri,  6 Jul 2012 09:51:04 -0700 (PDT)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.77,539,1336363200"; d="scan'208";a="406312740"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 06 Jul 2012 12:50:24 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Fri, 6 Jul 2012 12:50:37 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 6 Jul 2012 12:50:36 -0400
Subject: RE: Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
Thread-Topic: Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
Thread-Index: Ac1bl3YdX1C7JyBWSKeRw6dAKK2Mcg==
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791745903045@PRVPEXVS03.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 16:51:06 -0000

I have a comment about this document related to some discussions that I've =
had with a number of ADs and WG chairs around the formation and charter of =
Sunset4 to determine what is and is not in scope for that WG.

For a while both BEHAVE and Sunset4 had this document in their milestones, =
which clearly won't work. Therefore the distinction made between work to be=
 done in BEHAVE and SUNSET4 was that BEHAVE was to focus more generically o=
n the concept of NAT and the things necessary to make all flavors of it wor=
k, such that BEHAVE outputs would equally apply to NAT444, NAT64, DSLite, e=
tc. By contrast, Sunset4 was supposed to focus more narrowly on IPv4-only i=
tems. The BEHAVE chairs were represented in these discussions, and they bel=
ieved that this document was in keeping with this distinction.
In the document's introduction, for example, that generic nature is implied=
:
  "It is not an IETF endorsement
   of CGN or a real specification for CGN, but rather just a minimal set
   of requirements that will increase the likelihood of applications
   working across CGNs."

However, this document states in section 2:
  "Note also that the CGN described in this document is IPv4-only.
   IPv6 address translation is not considered."
I see that this is a new change to the -07 version, so I hate to rehash the=
 discussion, but I think that this statement should be clearer.
In reading the document, I don't believe that the intent was to limit it to=
 being a discussion of NAT44[4], but that could be the way that this statem=
ent is interpreted. The distinction I might make to clarify is that since t=
he document is talking about behaviors that are necessary to make IPv4 addr=
ess-sharing work, it's specific to the IPv4 side of what could well be a du=
al-stack NAT, but it's not limited to simply NAT44[4].

I'm not advocating pulling this document back so that it can go to the "rig=
ht" working group, because I don't think that'll actually add any value to =
the document and I'm not a fan of process for process's sake. My concern is=
 really more about content and naming- if it is truly a IPv4-only NAT (NAT4=
4 or NAT444) requirements doc rather than a more generic CGN requirements d=
oc, it should be named to reflect that. If it's meant to be a generic LSN r=
equirements doc, the authors should make the appropriate changes to keep it=
 generic.

Thanks,

Wes George, at least partially wearing my Sunset4 chair hat



> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: Tuesday, June 26, 2012 12:59 PM
> To: IETF-Announce
> Cc: behave@ietf.org
> Subject: Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common
> requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
>
>
> The IESG has received a request from the Behavior Engineering for
> Hindrance Avoidance WG (behave) to consider the following document:
> - 'Common requirements for Carrier Grade NATs (CGNs)'
>   <draft-ietf-behave-lsn-requirements-07.txt> as Best Current Practice
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-10. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document defines common requirements for Carrier-Grade NAT
>    (CGN).  It updates RFC 4787.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-behave-lsn-requirements/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-behave-lsn-
> requirements/ballot/
>
>
> The following IPR Declarations may be related to this I-D:
>
>    http://datatracker.ietf.org/ipr/1648/
>
>


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

From tony@att.com  Fri Jul  6 12:28:25 2012
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2AD011E80AD for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 12:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ri8gQR5U5pb for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 12:28:25 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id C830A11E809F for <ietf@ietf.org>; Fri,  6 Jul 2012 12:28:24 -0700 (PDT)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 96c37ff4.0.1405902.00-299.3848573.nbfkord-smmo06.seg.att.com (envelope-from <tony@att.com>);  Fri, 06 Jul 2012 19:28:42 +0000 (UTC)
X-MXL-Hash: 4ff73c6a14ccd624-1cf3e8cfe264c425905c5318f5cb4e4aa6470f69
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q66JSetI025665 for <ietf@ietf.org>; Fri, 6 Jul 2012 12:28:40 -0700
Received: from fflint04.pst.cso.att.com (fflint04.pst.cso.att.com [150.234.39.64]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id q66JSWDb025529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 6 Jul 2012 12:28:37 -0700
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by fflint04.pst.cso.att.com (RSA Interceptor) for <ietf@ietf.org>; Fri, 6 Jul 2012 12:28:21 -0700
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q66JSH3S006336 for <ietf@ietf.org>; Fri, 6 Jul 2012 15:28:17 -0400
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q66JSA3M006154 for <ietf@ietf.org>; Fri, 6 Jul 2012 15:28:11 -0400
Received: from [135.70.23.220] (vpn-135-70-23-220.vpn.west.att.com[135.70.23.220]) by maillennium.att.com (mailgw1) with ESMTP id <20120706192358gw10060lu9e> (Authid: tony); Fri, 6 Jul 2012 19:24:00 +0000
X-Originating-IP: [135.70.23.220]
Message-ID: <4FF73C46.5090301@att.com>
Date: Fri, 06 Jul 2012 15:28:06 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Comments for <I-D of Publishing the "Tao of the IETF" as a Web Page>
References: <CADnDZ89XGzmqRTL61rc9MSYRJCjs3BgwSDcM=J+_sKvoR1muEw@mail.gmail.com> <CADnDZ88jqzUpFwkyr9rtGQsoq3fNea_j-g2wpfz2081VrUakZg@mail.gmail.com> <CADnDZ89fxJo_YbVMrVr+-Q_-nF72W9iG9vZapZNV+1O0gckpow@mail.gmail.com> <6.2.5.6.2.20120620072437.0ad66a00@resistor.net> <CADnDZ8-kndVu9=4hG=hKPuTu960gEorac2w5gO6XJaL96gGrJA@mail.gmail.com> <4FE37DF1.2080407@gmail.com> <F96B6701-F6FF-41C1-BF81-81A00C76C450@vigilsec.com> <4FF45805.60702@gmx.de> <3CAEDB8A-46A5-4055-B0F4-BC0984463866@vigilsec.com> <4FF4684F.9030603@gmx.de> <79A97772-4F3D-4BA0-9A1C-6881E6780FB1@vigilsec.com>
In-Reply-To: <79A97772-4F3D-4BA0-9A1C-6881E6780FB1@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=1.0 c=1 a=4gJJctRnecgA:10 a=cgbV5Ep4loIA:10 a=Ame4ncDcU6]
X-AnalysisOut: [EA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:1]
X-AnalysisOut: [0 a=xwOvzTHDVLE4u4nGvK72ag==:17 a=48vgC7mUAAAA:8 a=_U3kC29]
X-AnalysisOut: [hpD6cBnu11jcA:9 a=wPNLvfGTeEIA:10 a=2mLzDuUFM-0A:10]
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, 06 Jul 2012 19:28:26 -0000

Huh?
Make tao a directory.
Put the document in the directory as index.html.
Now www.ietf.org/tao will redirect to www.ietf.org/tao/ will redirect to 
www.ietf.org/tao/index.html.

     Tony Hansen

On 7/4/2012 1:54 PM, Russ Housley wrote:
> Julian:
>
>> No, I was just trying to understand *why* the archive can't be at <http://www.ietf.org/tao/archive>.
> I was told that we cannot have http://www.ietf.org/tao directed to the document and also be the directory containing the archive directory.
>
> Russ



From rbarnes@bbn.com  Fri Jul  6 14:43:54 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 C7E7921F85A8; Fri,  6 Jul 2012 14:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.245
X-Spam-Level: 
X-Spam-Status: No, score=-107.245 tagged_above=-999 required=5 tests=[AWL=0.754, BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_74=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cBj0cmI92Oc1; Fri,  6 Jul 2012 14:43:54 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id D8BB021F85A5; Fri,  6 Jul 2012 14:43:53 -0700 (PDT)
Received: from ros-dhcp192-1-51-6.bbn.com ([192.1.51.6]:62814) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SnGJr-000CGG-DG; Fri, 06 Jul 2012 17:44:07 -0400
From: Richard L. Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART review of draft-ietf-pkix-caa-10
Date: Fri, 6 Jul 2012 17:44:06 -0400
Message-Id: <3E091F6B-E823-4E0F-B34C-EB381C4F1F0F@bbn.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
Cc: gen-art@ietf.org, draft-ietf-pkix-caa.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, 06 Jul 2012 21:43:54 -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-pkix-caa-10
Reviewer: Richard Barnes
Review Date: 06-July-2012
IETF LC End Date: 17-July-2012
IESG Telechat date: TBD

Summary: Nearly ready, but has a couple of major issues, and would =
benefit from several clarifications

MAJOR:

General: Why not DANE?
It would help prevent confusion if this document could differentiate =
itself a little more clearly from the DANE/TLSA specifications, =
especially since the RRs have largely the same information content.  It =
seems to me that there are a few main reasons:
-- Authorization without exclusion.  A domain holder might wish to =
authorize an issuer to issue a certificate without invalidating any =
other certificates that it has deployed.
-- Avoiding confusion: Having a different RRtype helps avoid these =
authorizations being confused with DANE records by relying parties.
-- Incident reporting via the "iodef" type.

General: Tree walking
The tree walking algorithm specified in Section 3 seems like a really =
bad idea.  It saves the domain holder from having to deploy separate CAA =
records for every subdomain, but has some tricky consequences.  For =
example, because the algorithm stops at the first CAA it finds, =
authorizations don't flow all the way down the tree, just to the first =
CAA point, where they get replaced.  Likewise, if a domain holder =
doesn't agree with a parent domain's CAAs for his domain, he's forced to =
deploy a null CAA defensively.  Recommend removing the tree walking / =
Extended Issuer Authorization Set.

General: Public Delegation Points
The concept of a Public Delegation Point seems unhelpful here, because =
it is not well-defined. =20

Section 5.4. "... civil or criminal sanctions."
This is complete speculation, and highly contingent on legal matters =
that don't belong in a technical specification.  Suggested cutting this =
sentence off:
"It is thus unlikely that the attack would succeed."


MINOR:

Section 2. "CAA records MAY be used by Certificate Evaluators..."
This recommendation seems to contradict the sentence immediately =
preceding.  =46rom the perspective of deciding whether a certificate is =
valid, a Certificate Evaluator is the same as a Relying Party, so if RPs =
shouldn't use CAA, then neither should Certificate Evaluators.  (In =
general, the concept of a Certificate Evaluator seems unhelpful and =
confusing; I would suggest just using RP, if anything.)

Section 2.1. "express written authority"
Requiring "written" authority seems like it goes beyond the scope of a =
technical specification.

Section 4.1.1. "ASCII letter and numbers in lower case."
Is there any particular reason that this has to be lower case?  It might =
be helpful to specify ABNF for it, e.g.:
  tag =3D 1*(ALPHA/DIGIT)

Section 4.2. ABNF
This section should specify that IDNs MUST be represented in A-label =
form, with a reference to RFC 5890.

Section 4.2. "This form of issue restriction..."
It would be helpful to explain this a little more fully.  The major =
point of a "null CAA" record seems to (1) stop the tree-climbing in the =
CA processing, and (2) let CAs know that the domain owner understands =
CAA.  If the tree-climbing is removed (as suggested above), then is =
there really value in this beyond having no CAA at all?  (If not, then =
just make the "[domain]" above into "domain".)

Section 5.1.=20
It would be helpful to have a pointer to DANE here.


EDITORIAL:

Section 2. "issueance" -> "issuance"=20

Section 2. "Certificate Policy Statement"=20
Seems like "Certification Practices Statement" would be more appropriate =
here.

Section 2.1. "a Web service"
It would be helpful to have a reference to RFC 6546 at this point, =
instead of all the way at the end.

Section 3. Bullets
It would be helpful to describe the process for assembling the Extended =
Issuer Authorization Set.  Namely, something like the following:
1. Check for CAA records under the target domain name. =20
2. If they exist, then they are the EIAS.
3. Otherwise, remove a label from the name
4. If the name is now empty (the root), then the EIAS is empty
5. Otherwise go to step (1) with the new domain name

Section 5. "Observance of CAA records by issuers is subject to =
accountability controls."
This is obviously not true as written;even after this RFC is published, =
not every CA will have controls enforced on it.  Suggested text:
"An issuer's practices with regard to CAA records can be made subject to =
accountability  controls."
In a similar vein, further down, "Since  CA could have avoided ... is =
increased."  It doesn't seem useful to speculate on probability, but the =
possibility is good to point out.  Suggested text for this and the =
following sentence:
"Since CAs can have avoided the mis-issue by performing CAA processing, =
if a particular CA does not use CAA, it could cause other entities to =
regard it as less trustworthy.  For example, failure to observe CAA =
issue restrictions might be used as an objective criterion for excluding =
issuers from embedded trust anchor lists."

Section 5. "negligent CAs will likely increase" -> "negligent CAs may =
increase"






From abdussalambaryun@gmail.com  Fri Jul  6 15:16:25 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57B4021F86EF for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 15:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.464
X-Spam-Level: 
X-Spam-Status: No, score=-3.464 tagged_above=-999 required=5 tests=[AWL=0.135,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xhvUmuDjCmPd for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 15:16: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 7FD9E21F86E0 for <ietf@ietf.org>; Fri,  6 Jul 2012 15:16:24 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so6990476vcq.31 for <ietf@ietf.org>; Fri, 06 Jul 2012 15:16:41 -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=n9yZyaaEJ8Ptdo9FwTj8lOKUjGIQ8Y+DvTGujlsdiAw=; b=HnzF+8zGdsr/MgAdIZvr6H91gHfxhOYwU2KwBuo/zizLVpQXzGIuJY34Q5u3KgS+R0 4rKTxwVN/YwgsK4/IuQldRnsA4zGRUKkzSuR/8fAMOQWfGswRrJ6N/YjZdnCAAJeL81F 5zrkBSlZHfax5poLjG2bUO2Mj46ID6egHwi8k9dU26INdRWz4fYwcPO72o0aMLcI0iz4 6I5L1ppf0fVzRS1/7KN323zushl/Js+HOYyR6wKS7GUNkXKlEs77pooBjaRN1dNuDWw2 H6YxOFhwN/NlAKQnOfrYlJIwxZnm7hG5h8Jkw1v/IuUn+uonhKIEOYOihwGBuVMIA3KV bdsw==
MIME-Version: 1.0
Received: by 10.220.149.148 with SMTP id t20mr15273931vcv.12.1341613001688; Fri, 06 Jul 2012 15:16:41 -0700 (PDT)
Received: by 10.220.110.130 with HTTP; Fri, 6 Jul 2012 15:16:41 -0700 (PDT)
In-Reply-To: <337C9F850CBEA220D0A03ED3@JcK-HP8200.jck.com>
References: <CADnDZ8-hoTgc=Q4AW0E7L+UeKqMQ0HVpW-6gDUzSkDNGLuieEA@mail.gmail.com> <337C9F850CBEA220D0A03ED3@JcK-HP8200.jck.com>
Date: Sat, 7 Jul 2012 00:16:41 +0200
Message-ID: <CADnDZ88OPjcqidmV+0cM4C0uhSxYL5u943TUePkZQohs8wp48A@mail.gmail.com>
Subject: Re: Last Call: <draft-hoffman-tao-as-web-page-02.txt> (Publishing the "Tao of the IETF" as a Web Page) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 22:16:25 -0000

Hi John,

Let's wait for the iesg and I trust they will find the solution after
they read our comments. I beleive that your comments are sound, and
will be taken by the iesg. If things turn against your suggestions
there are some procedure-options to go forward, but I don't think will
be in that direction.

AB

On 7/6/12, John C Klensin <john-ietf@jck.com> wrote:
>
>
> --On Friday, July 06, 2012 07:16 +0200 Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>
>> +1
>>
>> I support all your suggestions (i.e. point 1 and 2, and nits i
>> and ii ) , and hope that iesg, and editor agrees, and that the
>> community considers them for progress. I seen the change in the
>> draft-document-03 which I think getting better but still not
>> satisfied
>>
>> The new vesion 3 draft (dated 5 July) does not include all your
>> suggestion, please read and comment on draft-03 (the subject
>> refers to draft-02, did you read draft-03?).
>> http://tools.ietf.org/html/draft-hoffman-tao-as-web-page-03
>
> Abdussalam,
>
> Paul's note about draft 03 indicates that he posted it partially
> in response to my comments.  Those comments were based on 02.
> >From my point of view, there is always a question about how much
> energy a document like this is worth: it is not normative or
> authoritative and, while I'd prefer to see it done differently
> (and said so in a follow-up note after skimming -03), I've got
> other IETF work to do and would prefer to see Paul and the IESG
> working on the Tao text itself rather than fine-tuning this
> document.
>
> I personally believe that the document could be further improved
> by moving it toward my earlier suggestions.   I believe that
> more "what is this about" text belong in the Abstract and, in
> particular, that the relationship of the Tao (whether as an RFC
> or as a web page) deserves more explicit treatment than the
> second sentence of the Introduction.  And I believe that forcing
> another RFC if details of the revision process are changed is a
> bad idea and so think that Section 2 (of -03) should talk about
> an initial procedure and/or in much more general terms but
> should then push details and changes off to the Tao itself
> (perhaps as an appendix).  Ultimately, if we cannot trust the
> IESG and the Editor to be careful and sensible about this
> document, we are going to have problems that fine-tuning the RFC
> text can't prevent.
>
> But, if Paul and the IESG don't agree, I'm not convinced the
> subject justifies a lot more energy.
>
> best,
>    john
>
>

From richard@shockey.us  Fri Jul  6 16:44:48 2012
Return-Path: <richard@shockey.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E84111E80BE for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 16:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.635
X-Spam-Level: 
X-Spam-Status: No, score=-98.635 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tbjt5qRgNmLe for <ietf@ietfa.amsl.com>; Fri,  6 Jul 2012 16:44:47 -0700 (PDT)
Received: from oproxy5-pub.bluehost.com (oproxy5.bluehost.com [IPv6:2605:dc00:100:2::a5]) by ietfa.amsl.com (Postfix) with SMTP id 9047811E80BC for <ietf@ietf.org>; Fri,  6 Jul 2012 16:44:47 -0700 (PDT)
Received: (qmail 3997 invoked by uid 0); 6 Jul 2012 23:45:05 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by cpoproxy2.bluehost.com with SMTP; 6 Jul 2012 23:45:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default;  h=Content-Type:MIME-Version:Message-ID:Date:Subject:Cc:To:From; bh=8dWfaBL1H9ltWXNxQaLlEAUWL23h1vzDglT9OAyDfmI=;  b=ApVv8Sydd+p+p49FBgd5PEUT5Cp9mMv4EHl6gdkk2PAHtyWjQRGuS1ItyxqEulHxFaa8Xj4/98MHTX0+9+kRGhoTt7ZjKPM1u/T/ZqT9U4P1kj5VqVCE+q3FuxrobIOh;
Received: from [71.191.243.130] (port=64977 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1SnICu-0002JG-2P; Fri, 06 Jul 2012 17:45:04 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'IETF-Discussion list'" <ietf@ietf.org>
Subject: The US Federal Communications Commission Technical Advisory Committee is discussing the end of POTS. 
Date: Fri, 6 Jul 2012 19:45:02 -0400
Message-ID: <00ec01cd5bd1$5d94fcb0$18bef610$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00ED_01CD5BAF.D6835CB0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1b0VxYtKZbVnbWTyq8slFdajhb+w==
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 authed with richard@shockey.us}
Cc: dispatch@ietf.org, sipcore@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Jul 2012 23:44:48 -0000

This is a multi-part message in MIME format.

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

 

Aka the PSTN transition . 

 

http://www.fcc.gov/encyclopedia/technological-advisory-council

 

http://transition.fcc.gov/bureaus/oet/tac/tacdocs/TAC-WG-Ques-5-9-12.pdf

 

Richard Shockey
Shockey Consulting
Chairman of the Board of Directors SIP Forum
PSTN Mobile: +1 703.593.2683
< <mailto:richard(at)shockey.us> mailto:richard(at)shockey.us>
skype-linkedin-facebook: rshockey101
http//www.sipforum.org

 


------=_NextPart_000_00ED_01CD5BAF.D6835CB0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Aka the PSTN =
transition &#8230; <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a =
href=3D"http://www.fcc.gov/encyclopedia/technological-advisory-council">h=
ttp://www.fcc.gov/encyclopedia/technological-advisory-council</a><o:p></o=
:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a =
href=3D"http://transition.fcc.gov/bureaus/oet/tac/tacdocs/TAC-WG-Ques-5-9=
-12.pdf">http://transition.fcc.gov/bureaus/oet/tac/tacdocs/TAC-WG-Ques-5-=
9-12.pdf</a><o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'>Richard =
Shockey<br>Shockey Consulting<br>Chairman of the Board of Directors SIP =
Forum<br>PSTN Mobile: +1 703.593.2683<br>&lt;<a =
href=3D"mailto:richard(at)shockey.us"><span =
style=3D'color:blue'>mailto:richard(at)shockey.us</span></a>&gt;<br>skype=
-linkedin-facebook: rshockey101<br>http//www.sipforum.org</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00ED_01CD5BAF.D6835CB0--


From housley@vigilsec.com  Sat Jul  7 10:11: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 C9E9721F85AD for <ietf@ietfa.amsl.com>; Sat,  7 Jul 2012 10:11:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.431
X-Spam-Level: 
X-Spam-Status: No, score=-102.431 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYnyOivoako3 for <ietf@ietfa.amsl.com>; Sat,  7 Jul 2012 10:11:36 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id CF84121F85A4 for <ietf@ietf.org>; Sat,  7 Jul 2012 10:11:35 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 347E39A473B for <ietf@ietf.org>; Sat,  7 Jul 2012 13:11:55 -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 hSart+SIHFUv for <ietf@ietf.org>; Sat,  7 Jul 2012 13:11:53 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-13-190.washdc.fios.verizon.net [96.255.13.190]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 27106F2C25C for <ietf@ietf.org>; Sat,  7 Jul 2012 10:25:26 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Fwd: NomCom 2012-13 Call for Volunteers
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20120706211533.3449.10225.idtracker@ietfa.amsl.com>
Date: Sat, 7 Jul 2012 10:25:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6666DF0-FBD1-4878-AD97-D8DFC049B1E7@vigilsec.com>
References: <20120706211533.3449.10225.idtracker@ietfa.amsl.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: Sat, 07 Jul 2012 17:11:37 -0000

The NomCom process is critical for the proper function of the IETF. =
Please volunteer if you are eligible.

Russ


-------- Original Message --------
Subject: NomCom 2012-13 Call for Volunteers
Date: Fri, 06 Jul 2012 14:15:33 -0700
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>

The IETF nominating committee process for 2012-13 has begun. The IETF
nominating committee appoints folks to fill the open slots on the
IAOC, the IAB, and the IESG. The 10 nominating committee members are
selected randomly from a pool of volunteers. The more volunteers, the
better chance we have of choosing a random yet representative cross
section of the IETF population.  The details of the operation of the
nomcom can be found in RFC 3777.

To be eligible, volunteers for the nomcom need to have attended 3 of
the past 5 IETF meetings as of the time this announcement goes out.
That is, 3 meetings from IETF 79 (Beijing) - IETF 83 (Paris). If you
qualify, and if you will not be seeking appointment to any of the open
positions that this nomcom will be filling, please consider
volunteering.

The list of people whose terms end with the March 2013 IETF meeting,
and thus the positions for which the nominating committee is
responsible for filling, are as follows:

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

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

IESG:
--------
Russ Housley (General Area)
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)

The primary activity for this nomcom will begin in August 2012 and
should be completed in January 2013. The nomcom will be collecting
requirements from the community, as well as talking to candidates and
obtaining feedback from community members about candidates. There will
be regularly scheduled conference calls to ensure progress. Thus,
being a nomcom member does require some time commitment.

Please volunteer by sending an email before 11:59 pm EDT (UTC - 4
hours) August 5, 2012 as follows:

To: mlepinski.ietf@gmail.com
Subject: Nomcom 2012-13 Volunteer

Please include the following information in the body:

<Your Full Name>  // As you enter in the IETF Registration Form,
                   // First/Given name followed by Last/Family Name
<Current Primary Affiliation>
               // typically what goes in the Company field
               //  in the IETF Registration Form
[<all email addresses used to Register for the past 5 IETF meetings>]
<Preferred email address>  //
<Telephone number>         // For confirmation if selected

Please expect an email response from me within 3 business days stating
whether or not you are qualified.  If you don't receive a response,
please re-send your email with the tag "RESEND:" added to the subject
line.

If you are not yet sure you would like to volunteer, please consider
that nomcom members play a very important role in shaping the
leadership of the IETF.  Ensuring the leadership of the IETF is fair
and balanced and comprised of those who can lead the IETF in the right
direction is an important responsibility that rests on the IETF
participants at large. Volunteering for the nomcom is a good way of
contributing toward that goal.

I will be publishing a more detailed timetable for nomcom activities,
as well as details of the randomness seeds to be used for the RFC 3797
selection process, within the next couple weeks.

Thank you,
Matthew Lepinski
mlepinski.ietf@gmail.com
nomcom-chair@ietf.org


From simon.perreault@viagenie.ca  Sat Jul  7 14:16:30 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 5CFFB21F8638; Sat,  7 Jul 2012 14:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jIyPvCuZmKvJ; Sat,  7 Jul 2012 14:16:24 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 1818921F8631; Sat,  7 Jul 2012 14:16:23 -0700 (PDT)
Received: from eeepc.viagenie.ca (211.17-ppp.3menatwork.com [72.0.211.17]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 15C1140109; Sat,  7 Jul 2012 17:16:41 -0400 (EDT)
Message-ID: <4FF891B7.1080504@viagenie.ca>
Date: Sat, 07 Jul 2012 12:44:55 -0700
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; OpenBSD i386; rv:9.0) Gecko/20120207 Thunderbird/9.0.1
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: Gen-ART review of draft-ietf-behave-lsn-requirements-07
References: <4FF2E47C.80104@isode.com> <2D34DBB5-543F-47A3-A649-BDDFF76A6438@netapp.com>
In-Reply-To: <2D34DBB5-543F-47A3-A649-BDDFF76A6438@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<draft-ietf-behave-lsn-requirements.all@tools.ietf.org>" <draft-ietf-behave-lsn-requirements.all@tools.ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, "<gen-art@ietf.org>" <gen-art@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jul 2012 21:16:30 -0000

On 07/03/12 05:51, Eggert, Lars wrote:
> On Jul 3, 2012, at 14:24, Alexey Melnikov wrote:
>> I found it is to be odd to have a requirements document as a BCP, but I am sure
>> you can sort the right status out with IESG.
>
> +1
>
> I fail to see why Informational wouldn't be the better status.

I don't care much about the status and will defer to the IESG, but I 
thought Informational didn't mix well with 2119 language...

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 simon.perreault@viagenie.ca  Sat Jul  7 14:21:55 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 3FEDF21F8638; Sat,  7 Jul 2012 14:21: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JOO9ZnkE+zXf; Sat,  7 Jul 2012 14:21:53 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id C4BAF21F861C; Sat,  7 Jul 2012 14:21:52 -0700 (PDT)
Received: from eeepc.viagenie.ca (211.17-ppp.3menatwork.com [72.0.211.17]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 6D8C041631; Sat,  7 Jul 2012 17:22:11 -0400 (EDT)
Message-ID: <4FF8A836.2090407@viagenie.ca>
Date: Sat, 07 Jul 2012 14:20:54 -0700
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; OpenBSD i386; rv:9.0) Gecko/20120207 Thunderbird/9.0.1
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
Subject: Re: Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
References: <DCC302FAA9FE5F4BBA4DCAD4656937791745903045@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791745903045@PRVPEXVS03.corp.twcable.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "behave@ietf.org" <behave@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jul 2012 21:21:55 -0000

Wes,

Here's my take on this...

CGN as defined in this document does not only include NAT444. It is more 
generic than that: it really means "multi-user NAT". Dave Thaler came up 
with the example use case of the NAT in a wifi hotspot. It's just NAT44, 
but it still fits with the draft's definition of CGN because you have 
multiple users potentially fighting for the same NAT resources. Remember 
that the main raison d'être of this draft is for the operator to be able 
to ensure fairness between NAT users. So in this view I think it is 
clearly behave material since the sunsetting of IPv4 really is 
orthogonal to multi-user NATs.

On the question of IPv6: I don't think we should talk about IPv6 simply 
because IPv6 NAT so far has not seen significant deployment in the 
context of multi-user NAT. And NPTv6 is stateless so there are no 
resources to fight for.

Back to your email, where you wrote:

> if it is truly a IPv4-only NAT (NAT44 or NAT444) requirements doc rather than a more generic CGN requirements doc, it should be named to reflect that.

How about "Common Requirements for IPv4 Carrier Grade NATs (CGNs)"?

Thanks,
Simon

On 07/06/12 09:50, George, Wes wrote:
> I have a comment about this document related to some discussions that I've had with a number of ADs and WG chairs around the formation and charter of Sunset4 to determine what is and is not in scope for that WG.
>
> For a while both BEHAVE and Sunset4 had this document in their milestones, which clearly won't work. Therefore the distinction made between work to be done in BEHAVE and SUNSET4 was that BEHAVE was to focus more generically on the concept of NAT and the things necessary to make all flavors of it work, such that BEHAVE outputs would equally apply to NAT444, NAT64, DSLite, etc. By contrast, Sunset4 was supposed to focus more narrowly on IPv4-only items. The BEHAVE chairs were represented in these discussions, and they believed that this document was in keeping with this distinction.
> In the document's introduction, for example, that generic nature is implied:
>    "It is not an IETF endorsement
>     of CGN or a real specification for CGN, but rather just a minimal set
>     of requirements that will increase the likelihood of applications
>     working across CGNs."
>
> However, this document states in section 2:
>    "Note also that the CGN described in this document is IPv4-only.
>     IPv6 address translation is not considered."
> I see that this is a new change to the -07 version, so I hate to rehash the discussion, but I think that this statement should be clearer.
> In reading the document, I don't believe that the intent was to limit it to being a discussion of NAT44[4], but that could be the way that this statement is interpreted. The distinction I might make to clarify is that since the document is talking about behaviors that are necessary to make IPv4 address-sharing work, it's specific to the IPv4 side of what could well be a dual-stack NAT, but it's not limited to simply NAT44[4].
>
> I'm not advocating pulling this document back so that it can go to the "right" working group, because I don't think that'll actually add any value to the document and I'm not a fan of process for process's sake. My concern is really more about content and naming- if it is truly a IPv4-only NAT (NAT44 or NAT444) requirements doc rather than a more generic CGN requirements doc, it should be named to reflect that. If it's meant to be a generic LSN requirements doc, the authors should make the appropriate changes to keep it generic.
>
> Thanks,
>
> Wes George, at least partially wearing my Sunset4 chair hat

-- 
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 wesley.george@twcable.com  Mon Jul  9 08:03:14 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27B111E8087; Mon,  9 Jul 2012 08:03:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.722
X-Spam-Level: 
X-Spam-Status: No, score=-0.722 tagged_above=-999 required=5 tests=[AWL=-0.259, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aL5MRFsC8WUY; Mon,  9 Jul 2012 08:03:13 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 339D911E8083; Mon,  9 Jul 2012 08:03:09 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.77,552,1336363200"; d="scan'208";a="389825164"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 09 Jul 2012 11:03:01 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Mon, 9 Jul 2012 11:03:34 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Date: Mon, 9 Jul 2012 11:03:32 -0400
Subject: RE: Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
Thread-Topic: Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
Thread-Index: Ac1chpQ7rIRV1kacS+6FyUAfZ7yjkQBXCS8A
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791745A1F0D4@PRVPEXVS03.corp.twcable.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791745903045@PRVPEXVS03.corp.twcable.com> <4FF8A836.2090407@viagenie.ca>
In-Reply-To: <4FF8A836.2090407@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2012 15:03:14 -0000

> From: Simon Perreault [mailto:simon.perreault@viagenie.ca]
> Sent: Saturday, July 07, 2012 5:21 PM
>
> Wes,
>
> Here's my take on this...
>
> CGN as defined in this document does not only include NAT444. It is more
> generic than that: it really means "multi-user NAT". Dave Thaler came up
> with the example use case of the NAT in a wifi hotspot. It's just NAT44,
> but it still fits with the draft's definition of CGN because you have
> multiple users potentially fighting for the same NAT resources. Remember
> that the main raison d'=EAtre of this draft is for the operator to be abl=
e
> to ensure fairness between NAT users. So in this view I think it is
> clearly behave material since the sunsetting of IPv4 really is
> orthogonal to multi-user NATs.
>
> On the question of IPv6: I don't think we should talk about IPv6 simply
> because IPv6 NAT so far has not seen significant deployment in the
> context of multi-user NAT. And NPTv6 is stateless so there are no
> resources to fight for.

[WEG] I agree with all of what you've said, but I think I need to make the =
point that I'm concerned with clearer, because the above doesn't exactly ad=
dress it. I wasn't saying anything about IPv6 NAT, or even IPv4 sunset. I w=
as saying that the current wording is unclear as to what you mean by "IPv4-=
only". While the NAT specified by this document itself may only act on IPv4=
 traffic, as you note above it's not limited to just NAT444 or even an IPv4=
-only *network*. The recommendations in this doc will work for an IPv4 NAT =
associated with DSLite just as easily as a more traditional IPv4 transport.=
 This is an important distinction, IMO.

>
> Back to your email, where you wrote:
>
> > if it is truly a IPv4-only NAT (NAT44 or NAT444) requirements doc
> rather than a more generic CGN requirements doc, it should be named to
> reflect that.
>
> How about "Common Requirements for IPv4 Carrier Grade NATs (CGNs)"?
[WEG] This helps, but only in conjunction with additional clarification abo=
ut the application - that is, just because the NAT is IPv4-only doesn't mea=
n that the network must also be IPv4-only.

Thanks
Wes George

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

From simon.perreault@viagenie.ca  Mon Jul  9 08:08:25 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 335D621F8517; Mon,  9 Jul 2012 08:08:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QB3rM8oax7sy; Mon,  9 Jul 2012 08:08:24 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 4B20021F8514; Mon,  9 Jul 2012 08:08:24 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c064:21aa:2a3f:6536:e26d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id D951D415DA; Mon,  9 Jul 2012 11:08:48 -0400 (EDT)
Message-ID: <4FFAF400.1030201@viagenie.ca>
Date: Mon, 09 Jul 2012 11:08:48 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
Subject: Re: Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
References: <DCC302FAA9FE5F4BBA4DCAD4656937791745903045@PRVPEXVS03.corp.twcable.com> <4FF8A836.2090407@viagenie.ca> <DCC302FAA9FE5F4BBA4DCAD4656937791745A1F0D4@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791745A1F0D4@PRVPEXVS03.corp.twcable.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "behave@ietf.org" <behave@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jul 2012 15:08:25 -0000

On 2012-07-09 11:03, George, Wes wrote:
>  While the NAT specified by this
> document itself may only act on IPv4 traffic, as you note above it's
> not limited to just NAT444 or even an IPv4-only *network*. The
> recommendations in this doc will work for an IPv4 NAT associated with
> DSLite just as easily as a more traditional IPv4 transport. This is
> an important distinction, IMO.

Right, I understand now. It's the logical NAT function that is 
IPv4-only, not the global use case. I'll add some text to make this 
clear, and I'll specifically point out the DS-Lite example.

>> How about "Common Requirements for IPv4 Carrier Grade NATs
>> (CGNs)"?
> [WEG] This helps, but only in conjunction with additional
> clarification about the application - that is, just because the NAT
> is IPv4-only doesn't mean that the network must also be IPv4-only.

Understood.

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 jnc@mercury.lcs.mit.edu  Mon Jul  9 08:17:30 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 0B99D11E80AA for <ietf@ietfa.amsl.com>; Mon,  9 Jul 2012 08:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.886
X-Spam-Level: 
X-Spam-Status: No, score=-4.886 tagged_above=-999 required=5 tests=[AWL=-0.887, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4E2NHWrJCDUS for <ietf@ietfa.amsl.com>; Mon,  9 Jul 2012 08:17:23 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 7B2CD11E80A4 for <ietf@ietf.org>; Mon,  9 Jul 2012 08:17:23 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id DEA9518C0C3; Mon,  9 Jul 2012 11:17:47 -0400 (EDT)
To: ietf@ietf.org
Subject: Patents and standards bodies
Message-Id: <20120709151747.DEA9518C0C3@mercury.lcs.mit.edu>
Date: Mon,  9 Jul 2012 11:17:47 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 15:17:30 -0000

FYI; this seems relevant to us:

  Tech Rivals Push Copycats Battle To The Hill
  http://www.politico.com/news/stories/0712/78219.html

Excerpts:

"Apple and Microsoft are telling regulators and lawmakers that not all patents
are created equal. They say patents that have been developed by companies with
the help of international standards bodies - such as those Motorola Mobility
holds for Wi-Fi and online video - should be available for licensing on a fair
and nondiscriminatory basis.
...
'Actions aimed at preventing the sale of products that rely on industry
standards threaten to raise the cost and reduce the availability of popular
electronics products such as mobile phones, Blu-ray players, wireless routers,
video game consoles, Internet-connected televisions, and computers, among
others - all of which are built upon standards that ensure interoperability'"

          Noel

From acooper@cdt.org  Mon Jul  9 11:27:29 2012
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2681811E811E; Mon,  9 Jul 2012 11:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.356
X-Spam-Level: 
X-Spam-Status: No, score=-102.356 tagged_above=-999 required=5 tests=[AWL=0.243, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g1tAXrdxrOcO; Mon,  9 Jul 2012 11:27:28 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 1F1CE11E8119; Mon,  9 Jul 2012 11:27:28 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Mon, 9 Jul 2012 14:27:51 -0400
Subject: Re: Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <20120709162848.23418.51856.idtracker@ietfa.amsl.com>
Date: Mon, 9 Jul 2012 14:27:49 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 18:27:29 -0000

(incorporating some responses to =
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg06599.html =
as a LC comment)

It would be helpful if this document could further motivate the need for =
proxies to generate static obfuscated tokens. These two lines in =
particular, from 6.3 and 8.3, respectively, seem a bit weak:

"The identifiers can
   be randomly generated for each request and do not need to be
   statically assigned to resources."

"When using such tokens, a static token per user would increase the
   possibility for external organizations to track separate users."

Is it possible to recommend that generated tokens have limited lifetimes =
(per-request or otherwise), and make the static case the exception? The =
first statement above gets at this, but it seems to me that the middle =
ground between random generation per request and permanent unique token =
is worth emphasizing if there will be proxies that want to keep =
per-client identifiers around for some limited amount of time that isn't =
forever.

It's also worth noting that the second statement above is equally true =
for statically provisioned client IP addresses.

Also, this statement in 8.3 is not really true and probably better left =
out:

"Proxies using this extension will preserve the information of a
   direct connection, which has an end-user privacy impact, if the end-
   user or deployer does not know or expect that this is the case."

There can certainly be a privacy impact whether the user or deployer has =
awareness/expectation or not.=20

Alissa

On Jul 9, 2012, at 12:28 PM, The IESG wrote:

>=20
> The IESG has received a request from the Applications Area Working =
Group
> WG (appsawg) to consider the following document:
> - 'Forwarded HTTP Extension'
>  <draft-ietf-appsawg-http-forwarded-06.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-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
>=20
>   This document standardizes an HTTP extension header field that =
allows
>   proxy components to disclose information lost in the proxying
>   process, for example, the originating IP address of a request or IP
>   address of the proxy on the user-agent-facing interface.  Given a
>   trusted path of proxying components, this makes it possible to
>   arrange it so that each subsequent component will have access to, =
for
>   example, all IP addresses used in the chain of proxied HTTP =
requests.
>=20
>   This document also specifies guidelines for a proxy administrator to
>   anonymize the origin of a request.
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-http-forwarded/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-ietf-appsawg-http-forwarded/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> A specific point for Last Call discussion, please:
> During AD Evaluation, the registration policy for the new "HTTP
> Forwarded parameters" registry (see Section 9) was changed to
> "Specification Required" from "RFC Required".  This needs further
> review during Last Call, for two reasons:
>=20
> 1. While RFC Required forces new registrations through the IETF RFC
> process, and might discourage registrations from individuals or
> organizations that are unfamiliar with or averse to that process,
> Specification Required necessitates the appointment of a Designated
> Expert to review the requests and associated specifications.  Each of
> these policies comes with baggage, and we have to make sure we're
> weighing it down with the *right* baggage.
>=20
> 2. If we stay with Specification Required we should include a short
> paragraph with rough guidelines for the Designated Expert: what to
> consider when approving registration requests.  If we want the DE to
> approve most requests, just checking the associated specifications for
> sanity, we need to say that.  If we want the DE to put some judgment
> into deciding whether the requested parameters make sense and fit into
> the usage model, or whatever, we should say something about that.=20
> Comments and proposed text for this are encouraged.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20



From sm@resistor.net  Mon Jul  9 14:22:01 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 086A411E8173; Mon,  9 Jul 2012 14:22:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FJXwMGFq2ulp; Mon,  9 Jul 2012 14:21:57 -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 B4BCA11E80E4; Mon,  9 Jul 2012 14:21:57 -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 q69LLx7m017297; Mon, 9 Jul 2012 14:22:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1341868925; bh=sQcyKrJ7hAmWjwTfm63Thdab5jqyPxDj7kbudVysXB8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Tokl53q1VxLDXSsTzhsNZwPJ4Nlp9jVwFdxuWWnauSs/RXKIYmeVWI2FHKYgk38y6 4GGp+xSwfls4CbOVJoFubTV646b+W/UJfy6HEyHPnBePU0xuEdcK8ZUC6FXxb4CasZ hchDhXNHycJYUfVCiEGvItnXhf8lQxTTkSzv2SdM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1341868925; i=@resistor.net; bh=sQcyKrJ7hAmWjwTfm63Thdab5jqyPxDj7kbudVysXB8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nGacxioge+UP4ZG5j5QRjkTzcBshZcNwxrqIBcO+7R/hXbs8dkw7op7x/ND+u1Jwo 8Doy5nyuolYxLBzL6gFcy8cIG10rSNN/Fxy6pn5QJnSMKLaSQ5HVkRdcvc6V7jmDn/ 51IBZvmDDsXVngdLAGmL+SOsfzID0NGFgyXQ5+Wk=
Message-Id: <6.2.5.6.2.20120709134136.0ad9ae18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 09 Jul 2012 13:59:43 -0700
To: IETF Discussion Mailing List <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
In-Reply-To: <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 21:22:01 -0000

At 11:27 09-07-2012, Alissa Cooper wrote:
>Is it possible to recommend that generated tokens have limited 
>lifetimes (per-request or otherwise), and make the static case the 
>exception? The first statement above gets at this, but it seems to 
>me that the middle ground between random generation per request and 
>permanent unique token is worth emphasizing if there will be proxies 
>that want to keep per-client identifiers around for some limited 
>amount of time that isn't forever.

Yes.

>It's also worth noting that the second statement above is equally 
>true for statically provisioned client IP addresses.
>
>Also, this statement in 8.3 is not really true and probably better left out:
>
>"Proxies using this extension will preserve the information of a
>    direct connection, which has an end-user privacy impact, if the end-
>    user or deployer does not know or expect that this is the case."

I suggest removing that statement.  The wording is not entirely 
clear.  I read it as diluting end-user privacy impact.

In Section 6.3:

   'To distinguish the obfuscated identifier from other identifiers,
    it MUST have a leading underscore "_".'

I suggest removing the requirement and using "can".  The implementer 
can decide what to put in that field.

Regards,
-sm 


From stephen.farrell@cs.tcd.ie  Mon Jul  9 14:48:37 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 E49F211E80D1; Mon,  9 Jul 2012 14:48:37 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s9APYT-dVnkz; Mon,  9 Jul 2012 14:48:36 -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 0D60611E80CD; Mon,  9 Jul 2012 14:48:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id BD5911714F8; Mon,  9 Jul 2012 22:49:00 +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=1341870540; bh=+DywMSR6z98hRJ F3D95Q1Q+d7NWe/iYIhuv4ZoRiefk=; b=hb4Nqv36nJWvP1mP0z/6iAHIEGmJLH 0Cotx7bBMK3gYJZTvui2lXovJoCcjsrTaxkZkwIHeNQtYlGRMRdw1SPbDmzckIL2 y/+YR73HKZGd2+nw7AB3kBxypmo/U+fd2Pg/CrYaVumYMhWWNtklWBJE4Do9r0QS 8YTXiH6ObGDMF8zRfjCA9RfmiJDma2rUwTS8JYbFcqvKL6BVwDVWgaTrZTs9xQKQ rJghL7Iv4ouMwdZfPS+/A3gJvYj3LinnWWsGTiHwe4nQivQ3hT3EW2WD/gxrNw8x U3TwUiBraZV7UNryaaAYJ2M/0R/Y/SXSzylz8PQURlpmm7IeHlke9Jpw==
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 imNGqDbZg-Sg; Mon,  9 Jul 2012 22:49:00 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.42.25.143]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id C8E5B1714F7; Mon,  9 Jul 2012 22:48:59 +0100 (IST)
Message-ID: <4FFB51CB.2070608@cs.tcd.ie>
Date: Mon, 09 Jul 2012 22:48:59 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com>
In-Reply-To: <20120709162848.23418.51856.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 21:48:38 -0000

So I have a question about this draft that wasn't
resolved on apps-discuss and is maybe more suited
for IETF LC anyway.

With geopriv, we've gone to a lot of trouble to
support end-users having some control over their
location privacy.

This HTTP header will be used by proxies to forward
on the IP address of a client, and that will be used
via geo-ip services to locate the HTTP client.

But in this case, there's no control whatsoever
for the end user, nor are they even told that
its happened.

That seems to me to be quite a disconnect, but
I'm not sure what if anything ought be done about
it, since in this case, there's a non-standard
header that's widely deployed that does this.

So if we did try encourage taking the geopriv
approach we'd presumably just be ignored.

Any ideas?

Ta,
S.


On 07/09/2012 05:28 PM, The IESG wrote:
> 
> The IESG has received a request from the Applications Area Working Group
> WG (appsawg) to consider the following document:
> - 'Forwarded HTTP Extension'
>   <draft-ietf-appsawg-http-forwarded-06.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-07-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
> 
> 
>    This document standardizes an HTTP extension header field that allows
>    proxy components to disclose information lost in the proxying
>    process, for example, the originating IP address of a request or IP
>    address of the proxy on the user-agent-facing interface.  Given a
>    trusted path of proxying components, this makes it possible to
>    arrange it so that each subsequent component will have access to, for
>    example, all IP addresses used in the chain of proxied HTTP requests.
> 
>    This document also specifies guidelines for a proxy administrator to
>    anonymize the origin of a request.
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-http-forwarded/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-http-forwarded/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> ====================================
> A specific point for Last Call discussion, please:
> During AD Evaluation, the registration policy for the new "HTTP
> Forwarded parameters" registry (see Section 9) was changed to
> "Specification Required" from "RFC Required".  This needs further
> review during Last Call, for two reasons:
> 
> 1. While RFC Required forces new registrations through the IETF RFC
> process, and might discourage registrations from individuals or
> organizations that are unfamiliar with or averse to that process,
> Specification Required necessitates the appointment of a Designated
> Expert to review the requests and associated specifications.  Each of
> these policies comes with baggage, and we have to make sure we're
> weighing it down with the *right* baggage.
> 
> 2. If we stay with Specification Required we should include a short
> paragraph with rough guidelines for the Designated Expert: what to
> consider when approving registration requests.  If we want the DE to
> approve most requests, just checking the associated specifications for
> sanity, we need to say that.  If we want the DE to put some judgment
> into deciding whether the requested parameters make sense and fit into
> the usage model, or whatever, we should say something about that. 
> Comments and proposed text for this are encouraged.
> ====================================
> 
> 


From robert@raszuk.net  Mon Jul  9 16:04:52 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 8566311E80C1 for <ietf@ietfa.amsl.com>; Mon,  9 Jul 2012 16:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.57
X-Spam-Level: 
X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x62X9zUv7W63 for <ietf@ietfa.amsl.com>; Mon,  9 Jul 2012 16:04:52 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id AFD3F11E8093 for <ietf@ietf.org>; Mon,  9 Jul 2012 16:04:51 -0700 (PDT)
Received: (qmail 2799 invoked by uid 399); 9 Jul 2012 23:05:17 -0000
Received: from unknown (HELO ?192.168.1.58?) (pbs:robert@raszuk.net@83.31.246.76) by mail1310.opentransfer.com with ESMTPM; 9 Jul 2012 23:05:17 -0000
X-Originating-IP: 83.31.246.76
Message-ID: <4FFB63AB.5020801@raszuk.net>
Date: Tue, 10 Jul 2012 01:05:15 +0200
From: Robert Raszuk <robert@raszuk.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: ipad/android ietf "stay current" tool ...
References: <20120709151747.DEA9518C0C3@mercury.lcs.mit.edu>
In-Reply-To: <20120709151747.DEA9518C0C3@mercury.lcs.mit.edu>
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
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: Mon, 09 Jul 2012 23:04:52 -0000

Apologies if this is too simple question, but is there any tool for ipad 
and/or android which would allow me to download for offline reading all 
ietf/irtf drafts submitted between any two dates ?

Ideally it would be great to also be able to filter by version or by 
string in the name to stay current on a given WG efforts or some 
specific document.

Just checking for prior art before even considering doing it myself ;)

Many thx,
R.

From andreas@sbin.se  Tue Jul 10 04:27:59 2012
Return-Path: <andreas@sbin.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 0E97121F877C; Tue, 10 Jul 2012 04:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v9SjoQi7l89n; Tue, 10 Jul 2012 04:27:58 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by ietfa.amsl.com (Postfix) with ESMTP id CC65721F8778; Tue, 10 Jul 2012 04:27:57 -0700 (PDT)
Received: from hetzer (oslo.jvpn.opera.com [213.236.208.46]) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6ABS4VC027449; Tue, 10 Jul 2012 11:28:04 GMT
Date: Tue, 10 Jul 2012 13:27:56 +0200
From: Andreas Petersson <andreas@sbin.se>
To: Alissa Cooper <acooper@cdt.org>
Subject: Re: Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Message-ID: <20120710132756.4dac582d@hetzer>
In-Reply-To: <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.6; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/cQ7oiqjeycRSnTQwYVporRt"; protocol="application/pgp-signature"
Cc: IETF Discussion Mailing List <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 11:27:59 -0000

--Sig_/cQ7oiqjeycRSnTQwYVporRt
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Mon, 9 Jul 2012 14:27:49 -0400
Alissa Cooper <acooper@cdt.org> wrote:

> (incorporating some responses to http://www.ietf.org/mail-archive/web/app=
s-discuss/current/msg06599.html as a LC comment)
>=20
> It would be helpful if this document could further motivate the need for =
proxies to generate static obfuscated tokens. These two lines in particular=
, from 6.3 and 8.3, respectively, seem a bit weak:
>=20
> "The identifiers can
>    be randomly generated for each request and do not need to be
>    statically assigned to resources."
>=20
> "When using such tokens, a static token per user would increase the
>    possibility for external organizations to track separate users."

Well, I think it gives a good hint to use dynamically assigned tokens.

> Is it possible to recommend that generated tokens have limited lifetimes =
(per-request or otherwise), and make the static case the exception?

I guess so.

> The first statement above gets at this, but it seems to me that the
> middle ground between random generation per request and permanent
> unique token is worth emphasizing if there will be proxies that want
> to keep per-client identifiers around for some limited amount of time
> that isn't forever.
>=20
> It's also worth noting that the second statement above is equally true fo=
r statically provisioned client IP addresses.
>=20
> Also, this statement in 8.3 is not really true and probably better left o=
ut:
>=20
> "Proxies using this extension will preserve the information of a
>    direct connection, which has an end-user privacy impact, if the end-
>    user or deployer does not know or expect that this is the case."
>=20
> There can certainly be a privacy impact whether the user or deployer has =
awareness/expectation or not.=20

Can you give some proof or at least some arguments for this statement?


Cheers,
 Andreas

--Sig_/cQ7oiqjeycRSnTQwYVporRt
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iQIcBAEBAgAGBQJP/BG8AAoJEEaYRbQUWNleLVEQAInv6B5HHjmH3y2JPWdu9MkL
/Zevq1r0fn/BvZOQzpv3fUCo+DH53ojogEfq5zVN8+dDT8yvFWn974s1GAmOi0vn
b/Ek/kJ00SwUOIu5K3Jhx6IrUq9yWx/PiqS8lZ5TzHV4PfxNYTS+FIjNvgQi9TYb
82hFoPJDbU5r1TwpfayGlddoRfp2St6We+kmRj32u1rTsJZ5zV4io7nH5bIyWydE
Kj7aMbLgMqxUEPOcEpltFZLtzpFikhLooufelOnPPDnuAkTE1mgKweC+acKAgqL5
9jFo7xPt5SJouyDSz932rAf2kEptPacLTKwfHBQolYwZsvM5Z/+LFBySpDf6CBK/
B52gm/qCaRHjPDKVYRbfGt2oI4/kqb0r2CBE+1RRf+/KC/nCSkQn3aN5WWKcBzFU
L0/oTroRYKmdxdHQEwqWeTkuQ2amkNM57x6vTa81OXnkPEtJfyxKwmRVhUPZ6bUA
PpiaDqpIzfsHcBVBREPxJ3KQ8GHTd6DCg9jqu1ygP2bXINZoq/RlijJpyLIq7a/B
sj8kxK9ZF83jKjhTsaKDmjLPGxvLYvaRHqloLdsk7mjegMeCGZ8zRLQUdjwt5aCe
6C0f/px5YWdKHjNM6Kf2qq/zci/UqSWOqMloWOK+EMQZnruh2luWw+QQdnO8nC+M
dtGufStm8LhsxSKK3iMl
=+E08
-----END PGP SIGNATURE-----

--Sig_/cQ7oiqjeycRSnTQwYVporRt--

From andreas@sbin.se  Tue Jul 10 04:28:07 2012
Return-Path: <andreas@sbin.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 D784C21F86E5; Tue, 10 Jul 2012 04:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id auXTmqOtmwgZ; Tue, 10 Jul 2012 04:28:07 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by ietfa.amsl.com (Postfix) with ESMTP id 869A921F8533; Tue, 10 Jul 2012 04:28:05 -0700 (PDT)
Received: from hetzer (oslo.jvpn.opera.com [213.236.208.46]) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6ABSUcP027586; Tue, 10 Jul 2012 11:28:31 GMT
Date: Tue, 10 Jul 2012 13:28:25 +0200
From: Andreas Petersson <andreas@sbin.se>
To: SM <sm@resistor.net>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Message-ID: <20120710132825.5141babe@hetzer>
In-Reply-To: <6.2.5.6.2.20120709134136.0ad9ae18@resistor.net>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org> <6.2.5.6.2.20120709134136.0ad9ae18@resistor.net>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.6; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/x./DVWCrO2BOpqozsj9whkc"; protocol="application/pgp-signature"
Cc: IETF Discussion Mailing List <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 11:28:08 -0000

--Sig_/x./DVWCrO2BOpqozsj9whkc
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Mon, 09 Jul 2012 13:59:43 -0700
SM <sm@resistor.net> wrote:
> >Also, this statement in 8.3 is not really true and probably better left =
out:
> >
> >"Proxies using this extension will preserve the information of a
> >    direct connection, which has an end-user privacy impact, if the end-
> >    user or deployer does not know or expect that this is the case."
>=20
> I suggest removing that statement.  The wording is not entirely=20
> clear.  I read it as diluting end-user privacy impact.

I interpret it the other way around.=20
It makes a deployer aware that there is also end user expectations
to take into considerations.
Removing it may work as well, but I think that less well reflects the
discussion on the apps-list.

> In Section 6.3:
>=20
>    'To distinguish the obfuscated identifier from other identifiers,
>     it MUST have a leading underscore "_".'
>=20
> I suggest removing the requirement and using "can".  The implementer=20
> can decide what to put in that field.

I think that will make parsing harder, and give no benefit at all.

Cheers,
 Andreas

--Sig_/x./DVWCrO2BOpqozsj9whkc
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iQIcBAEBAgAGBQJP/BHZAAoJEEaYRbQUWNleNmkP/R8EUtKqr2HnFZ9uLcF8CgX8
4tdKhbWVWwe1cc9iWM4IUMxHb5lIeNhguRXCQDlxDBGcxiy82y/G1TwNxsSBNNnk
xnFkrRf+lL6B8DXxsjr/fH1m+3lpCzVM53lVoImQW9dA0wR0yHs3yEffAMSXlBzE
mBcVgcajMtxUZmdZcm65uW8rmSS18kDABgQ2r8VzQOLz60j066oERaqoh8DerMOs
Ht9/Q5I0iLKckV4yppej/bRT9eLlhxVwHU2itL0lbHcUNtsLFs+cg8YVkIfvf20U
b4+7Sn6LoH6WzWN4kJtzjLX8K28TMDtO5ei5+eT3Qdi6lbqKyeP3fPjjVQpK7fAH
Sz59Bkci6jT+ve443rtY3b28VGTt5MD2CO/0wAzQHOHtXukWF814QCDRVMM1dPgd
q2thFK+Eq7Xfsi0TRHUKzGsNQtjS1cStJ8Bba373b4DfRfzuVU+BIInBFZi8SbVU
EpqQzZ+dM9O9Gn8yVGUgkhDXgc8M/t1BKJL8NXhl2oASUeSqLzxmS4S+S9zSnhw7
zP6hEZFXaehZSbV9KULNJ/6tRQtaUdxKUqprpBFCub+Y6b1O3T/7eQ65pavYgnYt
NpXJ2I/cuKW2r+x9MhCuAmK99un5/3eznHBJqoLst6pXNbcjfvfYlTcSBpRO/qE3
Qt8DJmLjXemuiI5tQjMa
=4dg6
-----END PGP SIGNATURE-----

--Sig_/x./DVWCrO2BOpqozsj9whkc--

From andreas@sbin.se  Tue Jul 10 04:28:23 2012
Return-Path: <andreas@sbin.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 DB89921F8724; Tue, 10 Jul 2012 04:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.449
X-Spam-Level: 
X-Spam-Status: No, score=-5.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LOAN=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hxufe8XOj792; Tue, 10 Jul 2012 04:28:23 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by ietfa.amsl.com (Postfix) with ESMTP id 448C621F8778; Tue, 10 Jul 2012 04:28:20 -0700 (PDT)
Received: from hetzer (oslo.jvpn.opera.com [213.236.208.46]) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6ABScLb027714; Tue, 10 Jul 2012 11:28:39 GMT
Date: Tue, 10 Jul 2012 13:28:33 +0200
From: Andreas Petersson <andreas@sbin.se>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Message-ID: <20120710132833.0d6d6b02@hetzer>
In-Reply-To: <4FFB51CB.2070608@cs.tcd.ie>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <4FFB51CB.2070608@cs.tcd.ie>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.6; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_//79PAU7YFrxOLtK521R19Cn"; protocol="application/pgp-signature"
Cc: ietf@ietf.org, Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 11:28:24 -0000

--Sig_//79PAU7YFrxOLtK521R19Cn
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Mon, 09 Jul 2012 22:48:59 +0100
Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:

>=20
> So I have a question about this draft that wasn't
> resolved on apps-discuss and is maybe more suited
> for IETF LC anyway.
>=20
> With geopriv, we've gone to a lot of trouble to
> support end-users having some control over their
> location privacy.

 "Location Object (LO):   An object used to convey location
 information together with Privacy Rules.  Geopriv supports both
 geodetic location data (latitude, longitude, altitude, etc.) and civic
 location data (street, city, state, etc.).  Either or both types
 of location information may be present in a single LO (see the
 considerations in [5] for LOs containing multiple locations).
 Location Objects typically include some sort of identifier of the
 Target."

I'm not really sure that an IP address fits into that description.
If the geopriv thought that an IP address is a LO, they should have
written so in the document.

But more important; I think it would be really unfortunate if the
IETF would encourage people to use IP addresses as location objects, it
is done already, and it works bad and breaks lot of stuff.


> This HTTP header will be used by proxies to forward
> on the IP address of a client, and that will be used
> via geo-ip services to locate the HTTP client.

IP addresses are also forwarded by ISP's routers, I am not
convinced about the big difference here.
It may also be relevant to note that a proxy may not proxy
HTTPS-requests, so in those cases it would be enough to
inline an element served over HTTPS to get the client IP address.
Is that also a privacy issue?


> But in this case, there's no control whatsoever
> for the end user, nor are they even told that
> its happened.

Since it is non-trivial for end users to protect their privacy, I think
education of the end users are the only way to go.
This education is, however, not within the scope of this document.

My point is: privacy and anonymization is hard and hairy, and an
uneducated end user will "never" get this right.


> That seems to me to be quite a disconnect, but
> I'm not sure what if anything ought be done about
> it, since in this case, there's a non-standard
> header that's widely deployed that does this.
>=20
> So if we did try encourage taking the geopriv
> approach we'd presumably just be ignored.

Yes.


Cheers,
 Andreas

--Sig_//79PAU7YFrxOLtK521R19Cn
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iQIcBAEBAgAGBQJP/BHhAAoJEEaYRbQUWNle4qwP/0HL1PSqEG0bo2T0eD2fshN0
NrUKejPJIVlBL3I1R4G5dyvYI8xHb4hqCXAEl25gqd7g8ycKCf12VR/RkLHs/FMT
ugqa5+Pd9yyt0oVxuO3gmw2rWCXH3IbAEKpdQ/CtH5w2E078dKRM8eDTuSIxHyVu
6foHbpKGngCMBqY5StKsZ4xXyC8W5F1Y/qgGDHmO4YmChBtV4icDwNSsinMxnXua
VJ3Y4Lfj7oTkF34KOa8OmYUXX2VlvVICWUPLDH5uwzxsuOsUrUhxwn3dDPZmcWk2
y+N2iucVi+EjvJ607gXT2/oaLPM2YIihqMtwFhK0QjwWLLbtJcul/B2q+YZGGPW4
lcoByweLQtaHbiWzEiXTY32SSLh33VWAF4RzOC8nJsftWh1PYRaRSQrIIO/t+hj1
K0Gic3YJAq74TNbULF8dztxv+GF65uE9EpA46cz6/enyquP/caMg+GNqy2jPv9BB
hbCv6KJfboa2WBndlEAsmY3mkOwlDA/cKDbjzC9KgpSDuZl17j5DlMEJrASlZWKi
3QKe8XYImi95cbJaALog1W9C+DlpDwYu5fDqFE8CV8avt29QHVBhxGXrZG8S68Ua
+5kjIj33fqkZYquHnmTQAGFi2QdJg0finkOO9pyV1GXto4lQGgknWzVUxOcnm1/G
h+nI8ZUFivt5/Ak8RAOV
=NIuv
-----END PGP SIGNATURE-----

--Sig_//79PAU7YFrxOLtK521R19Cn--

From andreas@sbin.se  Tue Jul 10 05:08:04 2012
Return-Path: <andreas@sbin.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 CD13D21F8554; Tue, 10 Jul 2012 05:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.455
X-Spam-Level: 
X-Spam-Status: No, score=-6.455 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEjB7eKVOhvC; Tue, 10 Jul 2012 05:08:04 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by ietfa.amsl.com (Postfix) with ESMTP id ACA3521F8557; Tue, 10 Jul 2012 05:08:03 -0700 (PDT)
Received: from hetzer (oslo.jvpn.opera.com [213.236.208.46]) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6AC8Twk010427; Tue, 10 Jul 2012 12:08:29 GMT
Date: Tue, 10 Jul 2012 14:08:24 +0200
From: Andreas Petersson <andreas@sbin.se>
To: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP	Extension) to Proposed Standard
Message-ID: <20120710140824.3c8b3b3d@hetzer>
In-Reply-To: <20120709162848.23418.51856.idtracker@ietfa.amsl.com>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.6; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/wVINaOYuz0h+C0VyMGBWLpf"; protocol="application/pgp-signature"
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, 10 Jul 2012 12:08:04 -0000

--Sig_/wVINaOYuz0h+C0VyMGBWLpf
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Mon, 09 Jul 2012 09:28:48 -0700
The IESG <iesg-secretary@ietf.org> wrote:

> 1. While RFC Required forces new registrations through the IETF RFC
> process, and might discourage registrations from individuals or
> organizations that are unfamiliar with or averse to that process,
> Specification Required necessitates the appointment of a Designated
> Expert to review the requests and associated specifications.  Each of
> these policies comes with baggage, and we have to make sure we're
> weighing it down with the *right* baggage.
>=20
> 2. If we stay with Specification Required we should include a short
> paragraph with rough guidelines for the Designated Expert: what to
> consider when approving registration requests.  If we want the DE to
> approve most requests, just checking the associated specifications for
> sanity, we need to say that.  If we want the DE to put some judgment
> into deciding whether the requested parameters make sense and fit into
> the usage model, or whatever, we should say something about that.=20
> Comments and proposed text for this are encouraged.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


After some discussion with Barry, he suggested the following text:

"To keep the registration process uncomplicated and to encourage
parameters that are in use to be registered, the designated expert
should set a low bar for new registrations, confirming mostly that the
specification is reasonably stable, readily available, and sufficient
to create interoperable implementations.  The parameter name ought to
make sense for the requested usage, being short but sufficiently
specific.  The specification needs to comply with this document and
the general HTTP specifications, and should address security and
privacy implications of the requested parameter."


I think that sounds good so that is what I suggest that we go with.


Cheers,
 Andreas



--Sig_/wVINaOYuz0h+C0VyMGBWLpf
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iQIcBAEBAgAGBQJP/Bs4AAoJEEaYRbQUWNlexycP/jRgICrKMv0ncwwGs1TtD8/+
J83umxpKtDlB0rLRUT8CWbeU2evgBxLFIQQnfGHoy7XgEgbu1iTDYAeenJ+lQBvE
IzvEDCYgrloc5qy8gqN9seFGkPBUzP+qrnnXEkA9SXv4XRMys2wGY0bG7pgFZzVu
Fx11f9RA0eazGVvVkExMF6yOl33VhmqVt+8IxhNcYWy0lpfOGbVZx3OKHOTsFoMS
hviop2q9Nrk9rIVmHVes9w/m6Bch74P3HQUzBoN8i01rr3iOIP4SU3TxY/JeXltn
UPOC3AOwEqJCwdWhzuIg+RQXzTjoPByQ35ZARPXiq6now171ocwn8lql76LmCFlA
83NP/nX/W17VTg6ftTmKSRG8Zt/uZt59CiqxzzQOslQUcNYCkgT+Ui6TevvYZzGA
XemYdCTdFEqnhxm1vDkhfr/k9OaFQEEGZPZT/Wlhn2jWgg9GfqX+up1V7JkmWR1v
YtyWTweEn4736qnDivLm2hmfqevv4ypDdSIqdngcCzrkIwrK6r1Iuk7pTCxl98yP
vEY8poT52cylZsAnwgapOj2hhcyW+Gm9bnBqwFDtMZFKEzHciImX/WoKRgpY16uP
fNlYU7rr0AfbEFxBWxEsq1gRfi4sGt1lu6fdsxXeyM+Rsl/LOsJKuakwx8fB+zM+
iKMw8WLPL2EQnI1ihzvw
=y4qy
-----END PGP SIGNATURE-----

--Sig_/wVINaOYuz0h+C0VyMGBWLpf--

From acooper@cdt.org  Tue Jul 10 07:54:32 2012
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 001C911E8088; Tue, 10 Jul 2012 07:54:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.373
X-Spam-Level: 
X-Spam-Status: No, score=-102.373 tagged_above=-999 required=5 tests=[AWL=0.226, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kyAz-EizSDH1; Tue, 10 Jul 2012 07:54:30 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 31B3111E807F; Tue, 10 Jul 2012 07:54:28 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Tue, 10 Jul 2012 10:54:54 -0400
Subject: Re: Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <20120710132756.4dac582d@hetzer>
Date: Tue, 10 Jul 2012 10:54:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C023E9BE-5183-4A36-8470-B206FFBF1746@cdt.org>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org> <20120710132756.4dac582d@hetzer>
To: Andreas Petersson <andreas@sbin.se>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion Mailing List <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 14:54:32 -0000

Hi Andreas,

On Jul 10, 2012, at 7:27 AM, Andreas Petersson wrote:
>> The first statement above gets at this, but it seems to me that the
>> middle ground between random generation per request and permanent
>> unique token is worth emphasizing if there will be proxies that want
>> to keep per-client identifiers around for some limited amount of time
>> that isn't forever.
>>=20
>> It's also worth noting that the second statement above is equally =
true for statically provisioned client IP addresses.
>>=20
>> Also, this statement in 8.3 is not really true and probably better =
left out:
>>=20
>> "Proxies using this extension will preserve the information of a
>>   direct connection, which has an end-user privacy impact, if the =
end-
>>   user or deployer does not know or expect that this is the case."
>>=20
>> There can certainly be a privacy impact whether the user or deployer =
has awareness/expectation or not.=20
>=20
> Can you give some proof or at least some arguments for this statement?
>=20

If the deployer has awareness/expectation but users do not, then users' =
expectations that their client addresses will not be shared will be =
violated.

But even if users have awareness/expectation that their client addresses =
will be shared, the implications of that sharing may not be obvious, and =
there is nothing preventing remote servers that receive the information =
from abusing it. Examples: a user who doesn't know that his address is =
static and can be used by a remote server to track and correlate all of =
his activity; a user who doesn't know that his ISP maintains records of =
customer identity tied to client addresses that may become subject to =
law enforcement request; a service that combines static addresses or =
tokens received via the header with other collected identifiers and =
shares them with other servers to enable more pervasive tracking.

The first half of the statement is basically a refinement of the =
previous sentence in the section ("The Forwarded HTTP header field, by =
design, exposes information that some users consider privacy =
sensitive"), so I don't see what is lost by eliminating it.

Alissa   =20

>=20
> Cheers,
> Andreas



From andreas@sbin.se  Tue Jul 10 09:07:33 2012
Return-Path: <andreas@sbin.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 3980F21F8600; Tue, 10 Jul 2012 09:07:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.471
X-Spam-Level: 
X-Spam-Status: No, score=-6.471 tagged_above=-999 required=5 tests=[AWL=0.128,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qHPQpXOCrWe8; Tue, 10 Jul 2012 09:07:27 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by ietfa.amsl.com (Postfix) with ESMTP id 096A521F85FD; Tue, 10 Jul 2012 09:07:26 -0700 (PDT)
Received: from hetzer (oslo.jvpn.opera.com [213.236.208.46]) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6AG7YXi021441; Tue, 10 Jul 2012 16:07:34 GMT
Date: Tue, 10 Jul 2012 18:07:29 +0200
From: Andreas Petersson <andreas@sbin.se>
To: Alissa Cooper <acooper@cdt.org>
Subject: Re: Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Message-ID: <20120710180729.42712860@hetzer>
In-Reply-To: <C023E9BE-5183-4A36-8470-B206FFBF1746@cdt.org>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org> <20120710132756.4dac582d@hetzer> <C023E9BE-5183-4A36-8470-B206FFBF1746@cdt.org>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.6; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/Ud9QdQTJVCQg_8F3d+zl=li"; protocol="application/pgp-signature"
Cc: IETF Discussion Mailing List <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 16:07:33 -0000

--Sig_/Ud9QdQTJVCQg_8F3d+zl=li
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Tue, 10 Jul 2012 10:54:53 -0400
Alissa Cooper <acooper@cdt.org> wrote:

> Hi Andreas,
>=20
> On Jul 10, 2012, at 7:27 AM, Andreas Petersson wrote:
> >> The first statement above gets at this, but it seems to me that the
> >> middle ground between random generation per request and permanent
> >> unique token is worth emphasizing if there will be proxies that want
> >> to keep per-client identifiers around for some limited amount of time
> >> that isn't forever.
> >>=20
> >> It's also worth noting that the second statement above is equally true=
 for statically provisioned client IP addresses.
> >>=20
> >> Also, this statement in 8.3 is not really true and probably better lef=
t out:
> >>=20
> >> "Proxies using this extension will preserve the information of a
> >>   direct connection, which has an end-user privacy impact, if the end-
> >>   user or deployer does not know or expect that this is the case."
> >>=20
> >> There can certainly be a privacy impact whether the user or deployer h=
as awareness/expectation or not.=20
> >=20
> > Can you give some proof or at least some arguments for this statement?
> >=20
>=20
> If the deployer has awareness/expectation but users do not, then users' e=
xpectations that their client addresses will not be shared will be violated.

I interpret the statement "which has an end-user privacy impact" to be
true if any of "end user" or "deployer" does not know about it.
So that should cover the case when the deployer knows, but not the end
user.


> But even if users have awareness/expectation that their client addresses =
will be shared, the implications of that sharing may not be obvious, and th=
ere is nothing preventing remote servers that receive the information from =
abusing it. Examples: a user who doesn't know that his address is static an=
d can be used by a remote server to track and correlate all of his activity=
; a user who doesn't know that his ISP maintains records of customer identi=
ty tied to client addresses that may become subject to law enforcement requ=
est; a service that combines static addresses or tokens received via the he=
ader with other collected identifiers and shares them with other servers to=
 enable more pervasive tracking.

Thanks for explaining.

Yes, I can agree on this.
I do not think that this header changes real life affect on end users
privacy very much, though.
The big issue here is that there is quite a lot of things that the end
user are aware of.

> The first half of the statement is basically a refinement of the previous=
 sentence in the section ("The Forwarded HTTP header field, by design, expo=
ses information that some users consider privacy sensitive"), so I don't se=
e what is lost by eliminating it.

See my answer to SM. I think it better explains that the expectations
of the end user are important to consider, even if these expectations
are wrong.

I don't think that text will have much impact on how the header field
is used in practice though, or any technical impact, so removing it is
fine with me.

It would be interesting to hear what Stephen Farrell thinks about it,
since he wrote that text.


Cheers,
 Andreas

--Sig_/Ud9QdQTJVCQg_8F3d+zl=li
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iQIcBAEBAgAGBQJP/FNBAAoJEEaYRbQUWNleQBwP/ROOAhhQcvRKlCfYGwcKFHRk
mkRAozQPgC9tBLOoX/Q4Cfhw+Qj+K2bnGZPvZNnKT9KuBXZq+l14CrJkQRTkpbZu
TDxvnAqklc9AaHd1N4FfOTFeZHRnkJQrS93YTmngXgSVYbMeo49tRo+ly6ksBiY7
sYbdjqobzSNI3laO0JgRSzjJWc37ZZ66rqGRFC0stfJbS58Zse5fMmLUorNQRjbV
Gy6TsLAdlYDQpstsMxHAiqcfEefMojwggtfjvIhz7OdryBr2rTN2g5+mhdArLGC8
yzRtWYCVqiMYk/mDpJURcxIOWuE4ivxQXJaEt61yK/GiSo0hTzbEDiXxgg3RPMGY
VPjlGnCNZJUTJFD4eYCWVx0CUbHMejomHaSANu93or3lTQ14CsNjl2sntbRGxE0F
E2XIcnpFbE4x31FKze4nY1PKdoajzCobMD3qOG2dmBdxtxySb3hAPMNORoJIi9HP
4YtuOFPRyiYMB1xiIQQcPUSjphmi6J+y6jFoZ3PCTPhvqLVBl8oawCTkfdskawWK
wZZGYgUFSPpXh3QXi9lEgEioSKWGXeDROupj6eiVTDPm4FwaiqqEl12SQBE/mUzO
wdTJk12nCqx3yhCHUVKteY3Y+bwETZ+akfrQ505mG2L3qCc9LllP6eOfrq8u1ex9
1SDDZV89Kht4eNEJUs8L
=bmit
-----END PGP SIGNATURE-----

--Sig_/Ud9QdQTJVCQg_8F3d+zl=li--

From acooper@cdt.org  Tue Jul 10 09:31:43 2012
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8830B11E8199; Tue, 10 Jul 2012 09:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.381
X-Spam-Level: 
X-Spam-Status: No, score=-102.381 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j1wzI4lCKouW; Tue, 10 Jul 2012 09:31:43 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id C2A2F11E8187; Tue, 10 Jul 2012 09:31:42 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Tue, 10 Jul 2012 12:32:09 -0400
Subject: Re: Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <20120710180729.42712860@hetzer>
Date: Tue, 10 Jul 2012 12:32:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <62148A5F-B5F0-4915-8064-F33A0ADCB311@cdt.org>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org> <20120710132756.4dac582d@hetzer> <C023E9BE-5183-4A36-8470-B206FFBF1746@cdt.org> <20120710180729.42712860@hetzer>
To: Andreas Petersson <andreas@sbin.se>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion Mailing List <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 16:31:43 -0000

On Jul 10, 2012, at 12:07 PM, Andreas Petersson wrote:
>> The first half of the statement is basically a refinement of the =
previous sentence in the section ("The Forwarded HTTP header field, by =
design, exposes information that some users consider privacy =
sensitive"), so I don't see what is lost by eliminating it.
>=20
> See my answer to SM. I think it better explains that the expectations
> of the end user are important to consider, even if these expectations
> are wrong.

Right, I'm not saying that user expectations are unimportant. I think =
characterizing their role accurately should be the goal. If there is a =
desire to leave this in, I would suggest something more along the lines =
of:

Proxies using this extension will preserve the information of a direct =
connection. In some cases, the user's and/or deployer's knowledge or =
expectation that this will occur can help to mitigate the associated =
privacy impact.

>=20
> I don't think that text will have much impact on how the header field
> is used in practice though, or any technical impact, so removing it is
> fine with me.

Even if that's the case having accurate documentation of the privacy =
implications can't hurt.

Alissa

>=20
> It would be interesting to hear what Stephen Farrell thinks about it,
> since he wrote that text.
>=20
>=20
> Cheers,
> Andreas



From sm@resistor.net  Tue Jul 10 09:52:36 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 63BDD21F8634; Tue, 10 Jul 2012 09:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0utcqN2F868; Tue, 10 Jul 2012 09:52: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 F0A8821F8645; Tue, 10 Jul 2012 09:52: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 q6AGqpjG004164; Tue, 10 Jul 2012 09:52:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1341939178; bh=mZPx3PeuH+bsY8/6i8Q9ReQPixfSnCVngOTlCFC4g48=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HUPVA5ygycSVm/Vkphj4tJIWoocS0uvgK/mo/aTzpxuUofkxRFS5Pvew0SiIj596f fYn/efZLpA6vO4FKNlGB36ZWt7dqF7xrI4Oet38Oj9ktkfVcI4OVN5NHBquGdH2PAt wbJYUvA/aGBVzpRbriqIEuD4I/Srg+HlhwEgisEk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1341939178; i=@resistor.net; bh=mZPx3PeuH+bsY8/6i8Q9ReQPixfSnCVngOTlCFC4g48=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UEhpWh2ADvZXDdl/p1BYr/wLXq/6Ex+e+r1lDzoZlWAwFMLZYtd0re3Wd6D4Dcs6f DnEn4wKOJZdU+ZmcGAGcwUmALaFMJeeQRhdsLz+7I/Py9MkY3BRfWuNVCMluKDDaLT sQWlUYSBpTlDOFWnCNCWxX07KtEP60GZrzkKQxLM=
Message-Id: <6.2.5.6.2.20120710081323.08c9bcf8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 10 Jul 2012 08:43:43 -0700
To: Andreas Petersson <andreas@sbin.se>
From: SM <sm@resistor.net>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
In-Reply-To: <20120710132825.5141babe@hetzer>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org> <6.2.5.6.2.20120709134136.0ad9ae18@resistor.net> <20120710132825.5141babe@hetzer>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF Discussion Mailing List <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 16:52:37 -0000

Hi Andreas,
At 04:28 10-07-2012, Andreas Petersson wrote:
>I interpret it the other way around.
>It makes a deployer aware that there is also end user expectations
>to take into considerations.
>Removing it may work as well, but I think that less well reflects the
>discussion on the apps-list.

There is a thread at 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg06592.html 
of the working group discussions.  There were views from three 
persons.  I am in agreement with Alissa on that text.  I'll "+1" her 
message at 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg06664.html

>I think that will make parsing harder, and give no benefit at all.

It allows for more random bits of information.

Regards,
-sm 


From simon.perreault@viagenie.ca  Tue Jul 10 10:50:16 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 46E3C21F86F0 for <ietf@ietfa.amsl.com>; Tue, 10 Jul 2012 10:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.45
X-Spam-Level: 
X-Spam-Status: No, score=-1.45 tagged_above=-999 required=5 tests=[AWL=-1.150,  BAYES_00=-2.599, MANGLED_GIRL=2.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gDCmp6SndgWi for <ietf@ietfa.amsl.com>; Tue, 10 Jul 2012 10:50:15 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 675C921F86DE for <ietf@ietf.org>; Tue, 10 Jul 2012 10:50:15 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:8e70:5aff:fec5:72e4]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 4D4CA415D9 for <ietf@ietf.org>; Tue, 10 Jul 2012 13:50:43 -0400 (EDT)
Message-ID: <4FFC6B72.2010401@viagenie.ca>
Date: Tue, 10 Jul 2012 13:50:42 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Gen-ART review of draft-ietf-behave-lsn-requirements-07
References: <4FF2E47C.80104@isode.com>
In-Reply-To: <4FF2E47C.80104@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 17:50:16 -0000

On 07/03/2012 08:24 AM, Alexey Melnikov wrote:
> I found the justification for REQ-6 hard to read/understand. Why does
> access to
> servers being on the internal network need to go through CGN at all?

Here's the thing: the server is not on the internal network. It's on the 
external network, but it is still managed by the ISP. The ISP's network 
includes the internal network and some part of the external network. 
Furthermore, in many cases an ISP may run multiple CGNs, so the ISP's 
network is actually multiple internal networks and some part of the 
external network. The servers in the external network are operated by 
the ISP and "know" the internal networks (have routes to them), and can 
reach them directly without translation. And since connections from 
subscribers to those servers may account for a lot of traffic, it is 
important to not spend NAT resources on them.

Now, I'm not sure how to alter the existing text to make it easier to 
understand. It seems to me that all the information is there, just not 
with the same order/emphasis as what I wrote above. If the above was 
useful for you to understand, could you please point out in the text 
below what change would have helped you understand?

    REQ-6:  It MUST be possible to administratively turn off translation
            for specific destination addresses and/or ports.

    Justification:  It is common for a CGN administrator to provide
       access for subscribers to servers installed in the ISP's network,
       in the external realm.  When such a server is able to reach the
       internal realm via normal routing (which is entirely controlled by
       the ISP), translation is unneeded.  In that case, the CGN may
       forward packets without modification, thus acting like a plain
       router.  This may represent an important efficiency gain.

       Figure 2 illustrates this use-case.


                  X1:x1            X1':x1'            X2:x2
                  +---+from X1:x1  +---+from X1:x1    +---+
                  | C |  to X2:x2  |   |  to X2:x2    | S |
                  | l |>>>>>>>>>>>>| C |>>>>>>>>>>>>>>| e |
                  | i |            | G |              | r |
                  | e |<<<<<<<<<<<<| N |<<<<<<<<<<<<<<| v |
                  | n |from X2:x2  |   |from X2:x2    | e |
                  | t |  to X1:x1  |   |  to X1:x1    | r |
                  +---+            +---+              +---+

                         Figure 2: CGN pass-through

Thanks,
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 hartmans@mit.edu  Tue Jul 10 11:16:00 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 DC0C521F8710; Tue, 10 Jul 2012 11:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.346
X-Spam-Level: 
X-Spam-Status: No, score=-103.346 tagged_above=-999 required=5 tests=[AWL=-1.081, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fxd2cRpF5pUz; Tue, 10 Jul 2012 11:16:00 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 22C6821F870B; Tue, 10 Jul 2012 11:15:59 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id F1726202D8; Tue, 10 Jul 2012 14:16:53 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id B9E1D41F0; Tue, 10 Jul 2012 14:16:17 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: secdir@ietf.org,ietf@ietf.org
Subject: secdir review of draft-ietf-behave-lsn-requirements
Date: Tue, 10 Jul 2012 14:16:17 -0400
Message-ID: <tslobnna3da.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=iso-8859-1
Content-Transfer-Encoding: 8bit
Cc: draft-ietf-behave-lsn-requirements@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 18:16:01 -0000

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

This is a document describing requirements for CGNs in order to maximize
interoperability. It's similar to other documents behave has already
published. One area where requirements are considered is security.

For the most part, this document looks very good. Unfortunately, I do
have two significant concerns.


Requirement 9 requires a Port Control Protocol (PCP) server. I think we
need to say somewhat more about that in order for PCP to be secure on a
CGN. In this
discussion I urge people to read section 17.1 (the simple thread model)
of draft-ietf-pcp-base. We want to be using the simple threat model
because there's no clear credential that CGN operators are guaranteed to
share with their customers. If we ask people to set up a credential and
configure an authentication mechanism to take advantage  of the CGN's
PCP server, people will either ignore our recommendations or CGN PCP will
be useless.

The cardinal rule of the simple threat model is do no harm:  make sure
that PCP cannot be used in a manner that makes security worse than
implicit NAT mappings. The CGN situation is a bit more complex than the
typical simple threat model. I spent this morning going over the CGN
case with Margaret Wasserman and based on that discussion, I believe the
following additional requirements are sufficient to use the simple
threat model for CGNs.

The PCP server MUST NOT permit the lifetime of a mapping to be reduced
beyond its current life, MUST NOT permit a NAT mapping to be created
with a lifetime less than the lifetime used for implicit mappings, MUST
not permit the delete opcode to be used, and MUST NOT support the
third-party option. The map opcode MAY be permitted if the
recommendation of endpoint independent filtering behavior described in
REQ-7 is adopted; the map opcode MUST NOT be permitted in other
circumstances. These constraints MAY be relaxed if a security mechanism
consistent with PCP's Advanced Threat Model (see Section 17.2 of
[I-D.ietf-pcp-base]) is used; this is expected to be rare for CGN
deployments. Mappings created by PCP MUST follow the same deallocation
behavion (REQ-8) as implicitly mapped traffic. 

justification: Most of the concern has to do with one customer device
interacting negatively with the security of another; this is of
particular concern when the devices belong to different customers, but
devices belonging to the same customer are in scope for the PCP security
analysis as well. Reducing a mapping lifetime or deleting a mapping
create DOS opportunities and can create an opportunity for one device to
intercept another device's traffic. If a device spoofs creation of a
mapping with less than the default lifetime, then that can create DOS or
packet capture opportunities. The third-party option creates significant
spoofing opportunities. The behavior of REQ-8 is critical to avoiding
packet capture attacks.

My second concern is with section 8.
This section says that spoofing is a concern of DOS, notes that ingress
filtering is a defense and makes no recommendation.

I believe spoofing is a significantly greater concern than DOS. As an
example, I can spoof traffic from you to create an inbound hole towards
one of your ports. This is particularly valuable if the filtering
behavior is endpoint independent as recommended in REQ-7. Spoofing is
particularly dangerous with PCP if the constraints I listed above are
not followed. The analysis of the impact of spoofing is a bit tricky,
because it depends on how spoofing is accomplished and on whether an
attacker can observe traffic destined for other customers as well. So, I
think the warning about spoofing needs to be increased.

I also think we need to make a specific recommendation that people
deploying CGNs deploy sufficient ingress filtering to avoid spoofing. I
understand this specification is mostly about building CGNs not about
deploying them. However this issue seems quite important to the security
of the network.

Thanks,

--Sam

From w@1wt.eu  Mon Jul  9 23:08:55 2012
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A2621F86A5; Mon,  9 Jul 2012 23:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.421
X-Spam-Level: 
X-Spam-Status: No, score=-4.421 tagged_above=-999 required=5 tests=[AWL=-2.378, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L3NIQLFDDiZ7; Mon,  9 Jul 2012 23:08:54 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 8E36621F8646; Mon,  9 Jul 2012 23:08:53 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id q6A69CDQ021452; Tue, 10 Jul 2012 08:09:12 +0200
Date: Tue, 10 Jul 2012 08:09:12 +0200
From: Willy Tarreau <w@1wt.eu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Message-ID: <20120710060912.GA19405@1wt.eu>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <4FFB51CB.2070608@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4FFB51CB.2070608@cs.tcd.ie>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Tue, 10 Jul 2012 12:17:49 -0700
Cc: ietf@ietf.org, Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 06:08:55 -0000

On Mon, Jul 09, 2012 at 10:48:59PM +0100, Stephen Farrell wrote:
> 
> So I have a question about this draft that wasn't
> resolved on apps-discuss and is maybe more suited
> for IETF LC anyway.
> 
> With geopriv, we've gone to a lot of trouble to
> support end-users having some control over their
> location privacy.
> 
> This HTTP header will be used by proxies to forward
> on the IP address of a client, and that will be used
> via geo-ip services to locate the HTTP client.

In practice, the real use for the header is in the reverse-proxy chain,
as many people already disable x-forwarded-for on outgoing proxies for
privacy concerns. And server-side generally ignores the untrustable
x-forwarded-for provided by clients anyway. In the abstract, the draft
says it's for use between trusted proxies, which generally means either
the client-side proxy chain for logging purposes, where the last one
will remove the info, or more generally the server side where everyone
appends itself.

Maybe a small paragraph on this might emphasize the intended purpose
and suggest use cases as well as software options to add/ignore/remove
the header depending on the proxy location in the chain.

Regards,
Willy


From chair@ietf.org  Tue Jul 10 12:26:17 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 134ED11E808E; Tue, 10 Jul 2012 12:26:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.342
X-Spam-Level: 
X-Spam-Status: No, score=-102.342 tagged_above=-999 required=5 tests=[AWL=0.257, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtsRRtGsoo9v; Tue, 10 Jul 2012 12:26:16 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 7ACB321F8694; Tue, 10 Jul 2012 12:26:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id CB56212CC8D; Tue, 10 Jul 2012 12:26:43 -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 c0mM-bAeelFe; Tue, 10 Jul 2012 12:26:43 -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 58D0012CC88; Tue, 10 Jul 2012 12:26:43 -0700 (PDT)
Subject: Announce Bits-N-Bites Sponsor Program
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: Tue, 10 Jul 2012 15:26:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B74CADE4-C1A1-4708-A581-AA1733B04532@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: Tue, 10 Jul 2012 19:26:17 -0000

We are pleased to announce Bits-N-Bites, a new community networking =
experimental event that will take place for the first time at IETF 84 in =
Vancouver. =20

This event 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.

Bits-N-Bites will be held Thursday evening, August 2nd, from 7:00 - 9:00 =
PM at the Hyatt Vancouver in the Plaza AB room.

The Inaugural Sponsors for this event include Juniper, Huawei, ICANN, =
and the Internet Society.  Inaugural sponsorship tables are still =
available!  For more information see =
<https://www.ietf.org/meeting/84/bits-n-bites.html> and contact Drew =
Dvorshak at dvorshak@isoc.org.

Please come, network, speak with the sponsors, and enjoy the =
complimentary beer, wine, and hors d'oeuvres. =20

   Russ Housley
   IETF Chair

   Bob Hinden
   IAOC Chair


From simon.perreault@viagenie.ca  Tue Jul 10 12:36:23 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 723EE21F86C5; Tue, 10 Jul 2012 12:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.456
X-Spam-Level: 
X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gPB+winjd+gD; Tue, 10 Jul 2012 12:36:22 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 6341121F86C4; Tue, 10 Jul 2012 12:36:22 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:8e70:5aff:fec5:72e4]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1D294414B1; Tue, 10 Jul 2012 15:36:48 -0400 (EDT)
Message-ID: <4FFC844F.3010207@viagenie.ca>
Date: Tue, 10 Jul 2012 15:36:47 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: secdir review of draft-ietf-behave-lsn-requirements
References: <tslobnna3da.fsf@mit.edu>
In-Reply-To: <tslobnna3da.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pcp@ietf.org, draft-ietf-behave-lsn-requirements@tools.ietf.org, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 19:36:23 -0000

(adding pcp@ietf.org to the recipients list...)

Sam,

Thanks for the review, comments inline...

On 07/10/2012 02:16 PM, Sam Hartman wrote:
> Requirement 9 requires a Port Control Protocol (PCP) server. I think we
> need to say somewhat more about that in order for PCP to be secure on a
> CGN. In this
> discussion I urge people to read section 17.1 (the simple thread model)
> of draft-ietf-pcp-base. We want to be using the simple threat model
> because there's no clear credential that CGN operators are guaranteed to
> share with their customers. If we ask people to set up a credential and
> configure an authentication mechanism to take advantage  of the CGN's
> PCP server, people will either ignore our recommendations or CGN PCP will
> be useless.
>
> The cardinal rule of the simple threat model is do no harm:  make sure
> that PCP cannot be used in a manner that makes security worse than
> implicit NAT mappings. The CGN situation is a bit more complex than the
> typical simple threat model. I spent this morning going over the CGN
> case with Margaret Wasserman and based on that discussion, I believe the
> following additional requirements are sufficient to use the simple
> threat model for CGNs.
>
> The PCP server MUST NOT permit the lifetime of a mapping to be reduced
> beyond its current life, MUST NOT permit a NAT mapping to be created
> with a lifetime less than the lifetime used for implicit mappings, MUST
> not permit the delete opcode to be used,

Unless I'm mistaken, there is no delete opcode in PCP. You just send a 
MAP request with lifetime=0. So I would propose saying:

MUST NOT permit the lifetime of a mapping to be reduced beyond its 
current life or be set to zero (deleted)

> and MUST NOT support the third-party option.

I think pcp-base-26 added restrictions to THIRD_PARTY so that it could 
be used in CGN scenarios. If that is right, wouldn't it then make sense 
to allow THIRD_PARTY on CGNs?

> The map opcode MAY be permitted if the
> recommendation of endpoint independent filtering behavior described in
> REQ-7 is adopted; the map opcode MUST NOT be permitted in other
> circumstances. These constraints MAY be relaxed if a security mechanism
> consistent with PCP's Advanced Threat Model (see Section 17.2 of
> [I-D.ietf-pcp-base]) is used; this is expected to be rare for CGN
> deployments. Mappings created by PCP MUST follow the same deallocation
> behavion (REQ-8) as implicitly mapped traffic.
>
> justification: Most of the concern has to do with one customer device
> interacting negatively with the security of another; this is of
> particular concern when the devices belong to different customers, but
> devices belonging to the same customer are in scope for the PCP security
> analysis as well. Reducing a mapping lifetime or deleting a mapping
> create DOS opportunities and can create an opportunity for one device to
> intercept another device's traffic. If a device spoofs creation of a
> mapping with less than the default lifetime, then that can create DOS or
> packet capture opportunities. The third-party option creates significant
> spoofing opportunities. The behavior of REQ-8 is critical to avoiding
> packet capture attacks.

Thanks for the full requirements text and justification. That going to 
make my editing just so much easier!

> My second concern is with section 8.
> This section says that spoofing is a concern of DOS, notes that ingress
> filtering is a defense and makes no recommendation.
>
> I believe spoofing is a significantly greater concern than DOS. As an
> example, I can spoof traffic from you to create an inbound hole towards
> one of your ports.

Is this a new attack vector introduced by CGN? Without NAT, there's no 
need for a "hole", anyone can send traffic to any of a subscriber's ports...

Thanks,
Simon

> This is particularly valuable if the filtering
> behavior is endpoint independent as recommended in REQ-7. Spoofing is
> particularly dangerous with PCP if the constraints I listed above are
> not followed. The analysis of the impact of spoofing is a bit tricky,
> because it depends on how spoofing is accomplished and on whether an
> attacker can observe traffic destined for other customers as well. So, I
> think the warning about spoofing needs to be increased.
>
> I also think we need to make a specific recommendation that people
> deploying CGNs deploy sufficient ingress filtering to avoid spoofing. I
> understand this specification is mostly about building CGNs not about
> deploying them. However this issue seems quite important to the security
> of the network.

-- 
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 simon.perreault@viagenie.ca  Tue Jul 10 13:31: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 E25B211E80A6; Tue, 10 Jul 2012 13:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9vJf1KENulu; Tue, 10 Jul 2012 13:31:36 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 110F121F84D3; Tue, 10 Jul 2012 13:31:36 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:8e70:5aff:fec5:72e4]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1B35A44B4E; Tue, 10 Jul 2012 16:32:04 -0400 (EDT)
Message-ID: <4FFC9143.40407@viagenie.ca>
Date: Tue, 10 Jul 2012 16:32:03 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [pcp] secdir review of draft-ietf-behave-lsn-requirements
References: <tslobnna3da.fsf@mit.edu> <4FFC844F.3010207@viagenie.ca> <tsl1ukj9ye1.fsf@mit.edu>
In-Reply-To: <tsl1ukj9ye1.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: secdir@ietf.org, pcp@ietf.org, draft-ietf-behave-lsn-requirements@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 20:31:37 -0000

On 07/10/2012 04:03 PM, Sam Hartman wrote:
>      >> and MUST NOT support the third-party option.
>
>      Simon> I think pcp-base-26 added restrictions to THIRD_PARTY so that it could
>      Simon> be used in CGN scenarios. If that is right, wouldn't it then make
>      Simon> sense to allow THIRD_PARTY on CGNs?
>
> I don't think you can describe an subscriber-facing network of an ISP as
> "fully trusted."
> The text added to 13.1 might permit third_party to be used by an
> administrative web service within an ISP  but certainly not by customers
> of that ISP.
> I'd be OK with "MUST NOT allow the third_party option for traffic
> recieved from customer-facing interfaces."
> or "MUST NOT allow the third_party option in requests received on the
> internal network."
> Then that still permits the case of third_party for administration
> motivating the text in 13.1.

Makes sense to me.

>      >> My second concern is with section 8.
>      >> This section says that spoofing is a concern of DOS, notes that ingress
>      >> filtering is a defense and makes no recommendation.
>      >>
>      >> I believe spoofing is a significantly greater concern than DOS. As an
>      >> example, I can spoof traffic from you to create an inbound hole towards
>      >> one of your ports.
>
>      Simon> Is this a new attack vector introduced by CGN? Without NAT, there's no
>      Simon> need for a "hole", anyone can send traffic to any of a subscriber's
>      Simon> ports...
>
> I find it difficult to answer that question. I'd say that it is likely
> an unexpected assumption for someone behind a NAT.  It is a
> vulnerability of CGNs over other NATs, but perhaps not a vulnerability
> of CGNs over no NAT or firewall at all.
> Why do we care whether it's new? Is it actually bad if we end up
> describing a related attack and recommending people deploy in a manner
> that avoids it?

The DoS part is new. If an evil subscriber creates mappings in your 
stead, you may be DoSed. This attack vector does not exist with neither 
single-user NAT nor no NAT at all. That's why we mention it in the 
security considerations.

I don't think it is useful to recommend ingress filtering to prevent 
unwanted traffic because it would rely on an unrealistic assumption of a 
new security benefit that a CGN would provide. CGN does not prevent a 
subscriber from receiving traffic from anyone. That's true even with 
ingress filtering.

How about adding a sentence like...

"CGN as described in this document does not provide any security 
benefits over either single-user NAT or no NAT at all."

I don't think we have any power to change a subscriber's unreasonable 
assumptions, but we can at least honestly say to operators that they're 
not buying any security with CGN.

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 miyakawa@nttv6.jp  Tue Jul 10 13:36:30 2012
Return-Path: <miyakawa@nttv6.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC6711E813D; Tue, 10 Jul 2012 13:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bepVbC6Z44RE; Tue, 10 Jul 2012 13:36:29 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [IPv6:2402:c800:ff06:144::148]) by ietfa.amsl.com (Postfix) with ESMTP id A0E9B11E80CB; Tue, 10 Jul 2012 13:36:29 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [115.69.228.212]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id E1838BDC18; Wed, 11 Jul 2012 05:36:54 +0900 (JST)
Received: from localhost (localhost [IPv6:::1]) by z.nttv6.jp (NTTv6MTA) with ESMTP id B66ACE169A; Wed, 11 Jul 2012 05:36:54 +0900 (JST)
Date: Wed, 11 Jul 2012 05:36:54 +0900 (JST)
Message-Id: <20120711.053654.193724485.miyakawa@nttv6.jp>
To: simon.perreault@viagenie.ca
Subject: Re: [pcp] secdir review of draft-ietf-behave-lsn-requirements
From: Shin Miyakawa <miyakawa@nttv6.jp>
In-Reply-To: <4FFC9143.40407@viagenie.ca>
References: <4FFC844F.3010207@viagenie.ca> <tsl1ukj9ye1.fsf@mit.edu> <4FFC9143.40407@viagenie.ca>
Organizaton: NTT Communications
X-Mailer: Mew version 6.3 on Emacs 23.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, secdir@ietf.org, pcp@ietf.org, hartmans-ietf@mit.edu, draft-ietf-behave-lsn-requirements@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 20:36:30 -0000

>> Then that still permits the case of third_party for administration
>> motivating the text in 13.1.
> 
> Makes sense to me.

+1

> How about adding a sentence like...
> 
> "CGN as described in this document does not provide any security
> benefits over either single-user NAT or no NAT at all."

I agree with Simon (also as one of the authors of this draft).

We think that CGN is not the machine to proveide security benefits
and the original intension of this draft is just to make CGN as neutral as possible...

Best wishes,

Shin Miyakawa

From miyakawa@nttv6.jp  Wed Jul 11 00:34:18 2012
Return-Path: <miyakawa@nttv6.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3B3121F858A; Wed, 11 Jul 2012 00:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.787
X-Spam-Level: 
X-Spam-Status: No, score=0.787 tagged_above=-999 required=5 tests=[AWL=-0.877,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ywl6ZuZRSUlV; Wed, 11 Jul 2012 00:34:18 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [IPv6:2402:c800:ff06:144::148]) by ietfa.amsl.com (Postfix) with ESMTP id 0AEE221F85DF; Wed, 11 Jul 2012 00:34:17 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [115.69.228.212]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id B1B75BDC1E; Wed, 11 Jul 2012 16:34:44 +0900 (JST)
Received: from localhost (localhost [IPv6:::1]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 853F7E169A; Wed, 11 Jul 2012 16:34:44 +0900 (JST)
Date: Wed, 11 Jul 2012 16:34:44 +0900 (JST)
Message-Id: <20120711.163444.104075113.miyakawa@nttv6.jp>
To: Tina.Tsou.Zouting@huawei.com
Subject: Re: [BEHAVE] [sunset4] Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
From: Shin Miyakawa <miyakawa@nttv6.jp>
In-Reply-To: <1DF204BC-FAD6-4A0E-90B0-64760CC1ECF9@huawei.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791745A1F0D4@PRVPEXVS03.corp.twcable.com> <4FFAF400.1030201@viagenie.ca> <1DF204BC-FAD6-4A0E-90B0-64760CC1ECF9@huawei.com>
Organizaton: NTT Communications
X-Mailer: Mew version 6.3 on Emacs 23.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-7
Content-Transfer-Encoding: base64
Cc: behave@ietf.org, ietf@ietf.org, sunset4@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jul 2012 07:34:18 -0000

VGluYSwNCg0KVGhhbmtzIGZvciB0aGUgY29tbWVudC4gDQoNCj4gRmlyc3QsIHRoZSBwb3J0IG51
bWJlcnMgdG8gYmUgYWxsb2NhdGVkIHRvIENQRS4gRXhjbHVkaW5nIFdlbGwga25vd24gcG9ydCBu
dW1iZXJzIHNob3VsZCBiZSBtZW50aW9uZWQuIA0KDQpJIHRoaW5rIHRoYXQgZXZlbiBpZiB3ZWxs
IGtub3cgcG9ydCBpcyBhbGxvY2F0ZWQgYXMgc3JjIGFkZHJlc3MsIA0KdGhlcmUgd291bGQgYmUg
bm8gcHJvYmxlbS4gDQpUaGUgZG9jdW1lbnQgaXMgYWltaW5nIGF0ICJtaW5pbWFsIiBzZXQgb2Yg
cmVxdWlyZW1lbnRzIHRvIG1ha2UgQ0dOIHRyYW5zcGFyZW50LCANCkkgYWdyZWUgd2l0aCB0aGF0
IHRoaXMgY291bGQgYmUgaGVscGZ1bCANCmJ1dCBJIGRvbid0IHRoaW5rIHRoaXMgaXMgYSBjcml0
aWNhbCBjb25kaXRpb24gdG8gbWFrZSB0aGlzIEktRCBhbiBSRkMsIGlzbid0IGl0ID8NCg0KPiBN
b3Jlb3ZlciBpZiBwb3J0IG51bWJlcnMgYXJlIGFsbG9jYXRlZCB0byBlYWNoIENQRSwgd2hhdCBp
cyB0aGUgY3JpdGVyaWEgZm9yIGFsbG9jYXRpb24uIA0KDQpJIHRoaW5rIHRoYXQgaXQncyBvcGVy
YXRvcnMnIGNob2ljZSA6LSkNCg0KPHNuaXA+DQoNCj4gU29tZSBhbW91bnQgb2YgY2xhcml0eSBp
biB0aGlzIHJlc3BlY3Qgd291bGQgYmUgaGVscGZ1bC4NCg0KSSBhbHNvIHRoaW5rIHRoaXMga2lu
ZCBvZiBpbmZvcm1hdGlvbiBpcyB1c3VmdWwsIGJ1dCANCnRoaXMgY291bGQgYmUgZGlzY3Vzc2Vk
IGluIG90aGVyIGRyYWZ0IGlzbid0IGl0ID8NCg0KPiBNb3Jlb3ZlciwgdGhlIGRvY3VtZW50IGFk
dm9jYXRlcyB0aGUgdXNlIG9mIEVuZHBvaW50IGluZGVwZW5kZW50IGZpbHRlcmluZy4gSWYgQUlE
IGlzIHVzZWQsIHRoZXJlIHdvdWxkIGJlIGEgZGVsYXkgb2YgMTIwIHNlY29uZHMgZm9yIGVhY2gg
cG9ydCByZWFsbG9jYXRpb24uIFNvIHNob3VsZCBFSUYgYmUgdXNlZCBvbmx5IHdpdGggdGhvc2Ug
YXBwbGljYXRpb25zIHRoYXQgY2FuonQgZnVuY3Rpb24gd2l0aG91dCBpdCwgaW5zdGVhZCBvZiBh
cHBseWluZyBpdCBmb3IgYWxsLg0KDQpJIHNlZS4uLiBFc3BlY2lhbGx5LCBTaW1vbiwgaG93IGRv
IHlvdSB0aGluayA/DQoNCj4gDQo+IFRoZSBuZWVkIHRvIG1haW50YWluIGEgcmVjb3JkIG9yIGRh
dGFiYXNlIG9mIHRoZSBhbGxvY2F0ZWQgcG9ydHMgYW5kIHRoZWlyIGxpZmV0aW1lIHdvdWxkIGJl
IGhlbHBmdWwuIA0KDQpGb3IgZXhhbXBsZSwgaWYgcG9ydCBpcyBzdGF0aWNhbGx5IGFzc2lnbmVk
LCB0aGVyZSBpcyBubyBuZWVkIHRvIGhhdmUgDQpzdWNoIHJlY29yZC4gU28sIGFnYWluLCBJIGFn
cmVlIHdpdGggdGhhdCB0aGlzIGlzIG9mIGNvdXJzZSBhIGNsdWUgdG8gDQpvcGVyYXRlIENHTiBi
ZXR0ZXIgaW4gY2VydGFpbiBlbnZpcm9ubWVudCwgYnV0IHN0aWxsIGlzIG5vdCBhIGNyaXRpY2Fs
LCBJIHRoaW5rLg0KDQpTbywgaG93IGFib3V0IHdlIGNvdWxkIGNyZWF0ZSBhIGRvY3VtZW50IHdp
dGggc3VjaCBhIGhpbnQgZm9yIENHTiBvcGVyYXRpb24gDQpzZXByYXRlbHkgdGhlbiBsZXQgdGhp
cyBJLUQgbW92ZSBmb3J3YXJkIG5vdyA/ID4gVGluYQ0KDQpCZXN0IHdpc2hlcywNCg0KU2hpbiBN
aXlha2F3YSANCg0K

From andreas@sbin.se  Wed Jul 11 06:41:37 2012
Return-Path: <andreas@sbin.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 D789C21F868A; Wed, 11 Jul 2012 06:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.494
X-Spam-Level: 
X-Spam-Status: No, score=-6.494 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xAgLYFxp3XCL; Wed, 11 Jul 2012 06:41:36 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by ietfa.amsl.com (Postfix) with ESMTP id D9F1121F8610; Wed, 11 Jul 2012 06:41:35 -0700 (PDT)
Received: from hetzer (oslo.jvpn.opera.com [213.236.208.46]) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6BDg3U0016854; Wed, 11 Jul 2012 13:42:03 GMT
Date: Wed, 11 Jul 2012 15:41:58 +0200
From: Andreas Petersson <andreas@sbin.se>
To: SM <sm@resistor.net>
Subject: Re: [apps-discuss] Last Call:  <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Message-ID: <20120711154158.60f6ecf0@hetzer>
In-Reply-To: <6.2.5.6.2.20120710081323.08c9bcf8@resistor.net>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org> <6.2.5.6.2.20120709134136.0ad9ae18@resistor.net> <20120710132825.5141babe@hetzer> <6.2.5.6.2.20120710081323.08c9bcf8@resistor.net>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.6; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/24HaJ_VUi=WtQuc0yxNxZLi"; protocol="application/pgp-signature"
Cc: IETF Discussion Mailing List <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 13:41:37 -0000

--Sig_/24HaJ_VUi=WtQuc0yxNxZLi
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Tue, 10 Jul 2012 08:43:43 -0700
SM <sm@resistor.net> wrote:
>>> In Section 6.3:
>>>=20
>>>    'To distinguish the obfuscated identifier from other identifiers,
>>>     it MUST have a leading underscore "_".'
>>>=20
>>> I suggest removing the requirement and using "can".  The implementer=20
>>> can decide what to put in that field. =20

>At 04:28 10-07-2012, Andreas Petersson wrote:
>>I think that will make parsing harder, and give no benefit at all.
>=20
> It allows for more random bits of information.
>=20

(adding context again)


Hi,

Can you substantiate a bit on this statement?
How is it "random bits of information" when the specifications says
that it MUST be underscore?

As far as I can think of, the only thing that it will tell is that the
implementation is following this specification.
So, on the contrary; the more "degrees of freedom" that is given to the
implementation, the easier it would be to do fingerprinting.


Cheers,
 Andreas

--Sig_/24HaJ_VUi=WtQuc0yxNxZLi
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iQIcBAEBAgAGBQJP/YKmAAoJEEaYRbQUWNleOrQP/3KbagZ5LLcXfHOrU9akrOiW
HE9mffoJXI5DDUNC0UKN0aFVB+3MYP8CnmewpvVCrSJqNhlt7rSgryTAaSRCyg2v
/pvW1RHPfiBLoQ17WoF5zSHmHgIMHRw4+TCyhZ6KSbWlANvOVz7dcDU918080u6u
eKLorbDfiZK/fRybBb10s+WDk5ju1YyFHyGGEXujymP5dI1iCrF6BA1Oy6FnPcwX
/N+1Wfx6g4hyFiuRKH4sWIsm1P2gcUng2+I1A0nNHom1XyVAfpuOk8rW/h9DrTPh
xcxtfqWzBk7+G3PGDyLALUOlxbfZXIpYn9imzpM347qwnwgXMYS/p9OOlpUxhUsU
r5sdqc7R+561DEmdhEI1LNFSr4e2D6+kAkAL1L985lYIMfVbV6259q/FU5l0ixqx
G/+kC8fg9iRj1tMKvTNOyICUiuKXoNI43EKv0mVOjfxFXMrksxMxGD2JJJomGqTo
U7Bf57qQPlbdNFY2g90lP473rFEHJZYgi8M5eHZ4cxG8EUkpWF6TCPCrokk4shwq
YueW61Ke/umE/UEjSF6LDJPnXiTyEkuePfTMrdXPCN/tOMw9kHUoaAhW/cFL1Tbt
aUXnC1W2k8rsN3dGrBgKEcDZV/zcZKd7sRHD6i1+QGcbO1KSZkHlqh4tbbTT8/ol
eXMNjqK8+3gfMKx+3W9j
=5zpM
-----END PGP SIGNATURE-----

--Sig_/24HaJ_VUi=WtQuc0yxNxZLi--

From simon.perreault@viagenie.ca  Wed Jul 11 07:00:44 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 C273221F8666; Wed, 11 Jul 2012 07:00:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ALqVd3apM04E; Wed, 11 Jul 2012 07:00:43 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id AD06621F865A; Wed, 11 Jul 2012 07:00:43 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:8e70:5aff:fec5:72e4]) by jazz.viagenie.ca (Postfix) with ESMTPSA id BC5CF414AC; Wed, 11 Jul 2012 10:01:11 -0400 (EDT)
Message-ID: <4FFD8727.4020207@viagenie.ca>
Date: Wed, 11 Jul 2012 10:01:11 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Subject: Re: [sunset4] Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
References: <DCC302FAA9FE5F4BBA4DCAD4656937791745903045@PRVPEXVS03.corp.twcable.com> <4FF8A836.2090407@viagenie.ca> <DCC302FAA9FE5F4BBA4DCAD4656937791745A1F0D4@PRVPEXVS03.corp.twcable.com>, <4FFAF400.1030201@viagenie.ca> <1DF204BC-FAD6-4A0E-90B0-64760CC1ECF9@huawei.com>
In-Reply-To: <1DF204BC-FAD6-4A0E-90B0-64760CC1ECF9@huawei.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "sunset4@ietf.org" <sunset4@ietf.org>, "behave@ietf.org" <behave@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 14:00:44 -0000

On 07/10/2012 10:43 PM, Tina TSOU wrote:
> First, the port numbers to be allocated to CPE. Excluding Well known
> port numbers should be mentioned.

As draft editor, I would ask for a justification. I can't add a 
requirement without a justification.

> Moreover if port numbers are allocated
> to each CPE, what is the criteria for allocation.

I don't know, I'm just an editor. What specific text in the draft do you 
think needs to be changed?

> As mentioned in the
> document : “ There should be no limit on the size of the address pool”,
> does this address pool imply the one that would be allocated to the CPE?

No. It refers to the external address pool used by the CGN.

> According to the requirement of the CPE, the pool should be allocated or
> a fixed number of addresses in the address pool should be allocated to
> each CPE?

Sorry, I don't understand this question.

> Moreover, the document advocates the use of Endpoint independent
> filtering. If AID is used, there would be a delay of 120 seconds for
> each port reallocation. So should EIF be used only with those
> applications that can’t function without it, instead of applying it for all.

The draft proposes a more conservative approach: use EIF for everything 
with ADF exceptions. I understand you propose the reverse: ADF for 
everything with EIF exceptions. And I understand that the justification 
would be scalability. However, it seems to me that ADF exceptions can be 
made for heavy use protocols such as HTTP and DNS to address that 
scalability concern. Why isn't that enough?

> The need to maintain a record or database of the allocated ports and
> their lifetime would be helpful.

How could any NAT work without such a database? I probably misunderstand 
what you're suggesting...

> If this is maintained, the ports that
> are near to expiring their lifetime would be considered first and
> allocated before and in a order. In such cases there will be less
> chances of the traffic being dropped due to ports not being available.

This seems to go against REQ-11 D.

    REQ-11:  When a CGN is unable to create a mapping due to resource
             constraints or administrative restrictions (i.e., quotas):

             D.  and it MUST NOT delete existing mappings in order to
                 "make room" for the new one.  (This only applies to
                 normal CGN behavior, not to manual operator
                 intervention.)

Are you suggesting that this requirement be dropped? If so, it would be 
necessary to demonstrate why the justification for this requirement, 
quoted below, is  invalid.

       Applications generally handle connection establishment failure
       better than established connection failure.  This is why dropping
       the packet initiating the new connection is preferred over
       deleting existing mappings.  See also the rationale in [RFC5508]
       section 6.

> There should be a definite lifetime defined, before connection is
> refused due to unavailability of ports. If there is a threshold of
> say,180 seconds, during which allocated ports database can be scanned
> and if any ports is recently available, can be allocated. This would
> lead to efficient use of ports.

I'm sorry, I don't understand this proposal. Maybe an example would help?

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 andreas@sbin.se  Wed Jul 11 07:41:15 2012
Return-Path: <andreas@sbin.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 398AF21F86C2; Wed, 11 Jul 2012 07:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.503
X-Spam-Level: 
X-Spam-Status: No, score=-6.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U3d3NxI2FZLE; Wed, 11 Jul 2012 07:41:14 -0700 (PDT)
Received: from smtp.opera.com (smtp.opera.com [213.236.208.81]) by ietfa.amsl.com (Postfix) with ESMTP id 521DF21F86A1; Wed, 11 Jul 2012 07:41:14 -0700 (PDT)
Received: from hetzer (oslo.jvpn.opera.com [213.236.208.46]) by smtp.opera.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6BEfOQQ004292; Wed, 11 Jul 2012 14:41:25 GMT
Date: Wed, 11 Jul 2012 16:41:11 +0200
From: Andreas Petersson <andreas@sbin.se>
To: Alissa Cooper <acooper@cdt.org>
Subject: Re: Last Call: <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension) to Proposed Standard
Message-ID: <20120711164111.1b9e86d5@hetzer>
In-Reply-To: <62148A5F-B5F0-4915-8064-F33A0ADCB311@cdt.org>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org> <20120710132756.4dac582d@hetzer> <C023E9BE-5183-4A36-8470-B206FFBF1746@cdt.org> <20120710180729.42712860@hetzer> <62148A5F-B5F0-4915-8064-F33A0ADCB311@cdt.org>
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.6; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/N.7js2fI0g5=4i9GE9p/OfJ"; protocol="application/pgp-signature"
Cc: IETF Discussion Mailing List <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 14:41:15 -0000

--Sig_/N.7js2fI0g5=4i9GE9p/OfJ
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Tue, 10 Jul 2012 12:32:08 -0400
Alissa Cooper <acooper@cdt.org> wrote:

> On Jul 10, 2012, at 12:07 PM, Andreas Petersson wrote:
> >> The first half of the statement is basically a refinement of the previ=
ous sentence in the section ("The Forwarded HTTP header field, by design, e=
xposes information that some users consider privacy sensitive"), so I don't=
 see what is lost by eliminating it.
> >=20
> > See my answer to SM. I think it better explains that the expectations
> > of the end user are important to consider, even if these expectations
> > are wrong.
>=20
> Right, I'm not saying that user expectations are unimportant. I think cha=
racterizing their role accurately should be the goal. If there is a desire =
to leave this in, I would suggest something more along the lines of:
>=20
> Proxies using this extension will preserve the information of a direct co=
nnection. In some cases, the user's and/or deployer's knowledge or expectat=
ion that this will occur can help to mitigate the associated privacy impact.

Off-list discussion with Alissa resulted in this suggestion:

"Proxies using this extension will preserve the information of a direct
connection. This has an end-user privacy impact regardless of whether
the end-user or deployer knows or expects that this is the case."


Cheers,
 Andreas

--Sig_/N.7js2fI0g5=4i9GE9p/OfJ
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

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

iQIcBAEBAgAGBQJP/ZCHAAoJEEaYRbQUWNleuyUQAMBhA6j3m1PwcQZ1ggSPHvLR
U3MqV01Xc8n6Wv0c2tCbDyV9B6vos8UxAaS3etvfNO1pR5pJVAidvdPho+04hxKm
4dL2wndkkphCLV/7Na9UeR/WkH2ZZ+XQ7wt1UyMvHMP0Qp6R0dZiscgO3hzJKZoF
8c92gsaIJwEN2SPRU898dUR7AkKn8PLr5cLWqD829I3frtsTJgaUfW+ogmJrP2iN
72DBXUIbwe/3O/nr3fkIcD5PeFAa62swPgAQYyEgWlmx0weWzuRc8u8GoN+WMH3V
oIs/KV3uBxpPgCZkA6hqfsX0wbRNfTuFZJbqd9zXXMKmT6HXfTPpYk4A5BwhHc1k
7X2GznToRILFNZcKzYdamcP6TsXUWP9sZBmB26w7/tFD5Fw4oPT9s7MufDPZ/vza
vM15ZGH8eeHR9jZPReTdc32q7V5ZZZnVbsMrXRwORbCPRR9WSu0mVBpSJXr3I2Jl
6YgIcDlfwCIgJgWUekAHXO1KV4icdOFoMJb6AZVXfmsMRC8mHfBliZyaaCkpycqQ
aonjHb8K6fGSHFS5+s+/idvV8QlEcIW/tUECg08PEHSUt7h5IMf3mPkMbQvFrDA0
CQz8hNI3xpG9wBI4uF4Qq/bnBm4PkKfvDKOprmGX0HWhNhNvamPHQx51wdXz6tcb
HwjnxJvz/zV0VBidbUx6
=XFt3
-----END PGP SIGNATURE-----

--Sig_/N.7js2fI0g5=4i9GE9p/OfJ--

From hartmans@painless-security.com  Tue Jul 10 13:03:31 2012
Return-Path: <hartmans@painless-security.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FC411E80BB; Tue, 10 Jul 2012 13:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.301
X-Spam-Level: 
X-Spam-Status: No, score=-103.301 tagged_above=-999 required=5 tests=[AWL=-1.036, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uC6L2XxaUAqr; Tue, 10 Jul 2012 13:03:31 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2CA3A21F86B4; Tue, 10 Jul 2012 13:03:31 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id F06E12043E; Tue, 10 Jul 2012 16:04:27 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id A323441F0; Tue, 10 Jul 2012 16:03:50 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Simon Perreault <simon.perreault@viagenie.ca>
Subject: Re: [pcp] secdir review of draft-ietf-behave-lsn-requirements
References: <tslobnna3da.fsf@mit.edu> <4FFC844F.3010207@viagenie.ca>
Date: Tue, 10 Jul 2012 16:03:50 -0400
In-Reply-To: <4FFC844F.3010207@viagenie.ca> (Simon Perreault's message of "Tue, 10 Jul 2012 15:36:47 -0400")
Message-ID: <tsl1ukj9ye1.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Wed, 11 Jul 2012 08:08:42 -0700
Cc: secdir@ietf.org, pcp@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, draft-ietf-behave-lsn-requirements@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 20:03:32 -0000

>>>>> "Simon" == Simon Perreault <simon.perreault@viagenie.ca> writes:




    Simon> MUST NOT permit the lifetime of a mapping to be reduced beyond its
    Simon> current life or be set to zero (deleted)
OK.

    >> and MUST NOT support the third-party option.

    Simon> I think pcp-base-26 added restrictions to THIRD_PARTY so that it could
    Simon> be used in CGN scenarios. If that is right, wouldn't it then make
    Simon> sense to allow THIRD_PARTY on CGNs?

I don't think you can describe an subscriber-facing network of an ISP as
"fully trusted."
The text added to 13.1 might permit third_party to be used by an
administrative web service within an ISP  but certainly not by customers
of that ISP.
I'd be OK with "MUST NOT allow the third_party option for traffic
recieved from customer-facing interfaces."
or "MUST NOT allow the third_party option in requests received on the
internal network."
Then that still permits the case of third_party for administration
motivating the text in 13.1.

    >> My second concern is with section 8.
    >> This section says that spoofing is a concern of DOS, notes that ingress
    >> filtering is a defense and makes no recommendation.
    >> 
    >> I believe spoofing is a significantly greater concern than DOS. As an
    >> example, I can spoof traffic from you to create an inbound hole towards
    >> one of your ports.

    Simon> Is this a new attack vector introduced by CGN? Without NAT, there's no
    Simon> need for a "hole", anyone can send traffic to any of a subscriber's
    Simon> ports...

I find it difficult to answer that question. I'd say that it is likely
an unexpected assumption for someone behind a NAT.  It is a
vulnerability of CGNs over other NATs, but perhaps not a vulnerability
of CGNs over no NAT or firewall at all.
Why do we care whether it's new? Is it actually bad if we end up
describing a related attack and recommending people deploy in a manner
that avoids it?

From Tina.Tsou.Zouting@huawei.com  Tue Jul 10 19:46:21 2012
Return-Path: <Tina.Tsou.Zouting@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 EA40C11E80E0; Tue, 10 Jul 2012 19:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.882
X-Spam-Level: 
X-Spam-Status: No, score=-5.882 tagged_above=-999 required=5 tests=[AWL=0.716,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G2PMY5Rk5pZ8; Tue, 10 Jul 2012 19:46:21 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id B5BAB11E8079; Tue, 10 Jul 2012 19:46:20 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHX50059; Tue, 10 Jul 2012 22:46:50 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 10 Jul 2012 19:43:30 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.208]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.003; Tue, 10 Jul 2012 19:43:30 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Subject: Re: [sunset4] Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
Thread-Topic: [sunset4] Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
Thread-Index: AQHNXeQa9cn4jo2TiUil16mU5pbaQpchgwsAgAHfFr4=
Date: Wed, 11 Jul 2012 02:43:30 +0000
Message-ID: <1DF204BC-FAD6-4A0E-90B0-64760CC1ECF9@huawei.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791745903045@PRVPEXVS03.corp.twcable.com> <4FF8A836.2090407@viagenie.ca> <DCC302FAA9FE5F4BBA4DCAD4656937791745A1F0D4@PRVPEXVS03.corp.twcable.com>, <4FFAF400.1030201@viagenie.ca>
In-Reply-To: <4FFAF400.1030201@viagenie.ca>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_1DF204BCFAD64A0E90B064760CC1ECF9huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Wed, 11 Jul 2012 08:08:42 -0700
Cc: "sunset4@ietf.org" <sunset4@ietf.org>, "behave@ietf.org" <behave@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 02:46:22 -0000

--_000_1DF204BCFAD64A0E90B064760CC1ECF9huaweicom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

There are few things that in my opinion should be added.

First, the port numbers to be allocated to CPE. Excluding Well known port n=
umbers should be mentioned. Moreover if port numbers are allocated to each =
CPE, what is the criteria for allocation. As mentioned in the document : =
=93 There should be no limit on the size of the address pool=94, does this =
address pool imply the one that would be allocated to the CPE? According to=
 the requirement of the CPE, the pool should be allocated or a fixed number=
 of addresses in the address pool should be allocated to each CPE? Some amo=
unt of clarity in this respect would be helpful.

Moreover, the document advocates the use of Endpoint independent filtering.=
 If AID is used, there would be a delay of 120 seconds for each port reallo=
cation. So should EIF be used only with those applications that can=92t fun=
ction without it, instead of applying it for all.

The need to maintain a record or database of the allocated ports and their =
lifetime would be helpful. If this is maintained, the ports that are near t=
o expiring their lifetime would be considered first and allocated before an=
d in a order. In such cases there will be less chances of the traffic being=
 dropped due to ports not being available. There should be a definite lifet=
ime defined, before connection is refused due to unavailability of ports. I=
f there is a threshold of say,180 seconds, during which allocated ports dat=
abase can be scanned and if any ports is recently available, can be allocat=
ed. This would lead to efficient use of ports.

Tina

On Jul 9, 2012, at 8:08 AM, "Simon Perreault" <simon.perreault@viagenie.ca<=
mailto:simon.perreault@viagenie.ca>> wrote:

On 2012-07-09 11:03, George, Wes wrote:
While the NAT specified by this
document itself may only act on IPv4 traffic, as you note above it's
not limited to just NAT444 or even an IPv4-only *network*. The
recommendations in this doc will work for an IPv4 NAT associated with
DSLite just as easily as a more traditional IPv4 transport. This is
an important distinction, IMO.

Right, I understand now. It's the logical NAT function that is IPv4-only, n=
ot the global use case. I'll add some text to make this clear, and I'll spe=
cifically point out the DS-Lite example.

How about "Common Requirements for IPv4 Carrier Grade NATs
(CGNs)"?
[WEG] This helps, but only in conjunction with additional
clarification about the application - that is, just because the NAT
is IPv4-only doesn't mean that the network must also be IPv4-only.

Understood.

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
_______________________________________________
sunset4 mailing list
sunset4@ietf.org<mailto:sunset4@ietf.org>
https://www.ietf.org/mailman/listinfo/sunset4

--_000_1DF204BCFAD64A0E90B064760CC1ECF9huaweicom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body bgcolor=3D"#FFFFFF">
<div>
<div><font>There are few things that in my opinion should be added.</font><=
/div>
<div>&nbsp;</div>
<div>First, the port numbers to be allocated to CPE. Excluding Well known p=
ort numbers should be mentioned. Moreover if port numbers are allocated to =
each CPE, what is the criteria for allocation. As mentioned in the document=
 : =93 There should be no limit on
 the size of the address pool=94, does this address pool imply the one that=
 would be allocated to the CPE? According to the requirement of the CPE, th=
e pool should be allocated or a fixed number of addresses in the address po=
ol should be allocated to each CPE?
 Some amount of clarity in this respect would be helpful.</div>
<div>&nbsp;</div>
<div>Moreover, the document advocates the use of Endpoint independent filte=
ring. If AID is used, there would be a delay of 120 seconds for each port r=
eallocation. So should EIF be used only with those applications that can=92=
t function without it, instead of
 applying it for all.</div>
<div>&nbsp;</div>
<div><font>The need to maintain a record or database of the allocated ports=
 and their lifetime would be helpful. If this is maintained, the ports that=
 are near to expiring their lifetime would be considered first and allocate=
d before and in a order. In such
 cases there will be less chances of the traffic being dropped due to ports=
 not being available. There should be a definite lifetime defined, before c=
onnection is refused due to unavailability of ports. If there is a threshol=
d of say,180 seconds, during which
 allocated ports database can be scanned and if any ports is recently avail=
able, can be allocated. This would lead to efficient use of ports.</font></=
div>
<br>
Tina</div>
<div><br>
On Jul 9, 2012, at 8:08 AM, &quot;Simon Perreault&quot; &lt;<a href=3D"mail=
to:simon.perreault@viagenie.ca">simon.perreault@viagenie.ca</a>&gt; wrote:<=
br>
<br>
</div>
<div></div>
<blockquote type=3D"cite">
<div><span>On 2012-07-09 11:03, George, Wes wrote:</span><br>
<blockquote type=3D"cite"><span>While the NAT specified by this</span><br>
</blockquote>
<blockquote type=3D"cite"><span>document itself may only act on IPv4 traffi=
c, as you note above it's</span><br>
</blockquote>
<blockquote type=3D"cite"><span>not limited to just NAT444 or even an IPv4-=
only *network*. The</span><br>
</blockquote>
<blockquote type=3D"cite"><span>recommendations in this doc will work for a=
n IPv4 NAT associated with</span><br>
</blockquote>
<blockquote type=3D"cite"><span>DSLite just as easily as a more traditional=
 IPv4 transport. This is</span><br>
</blockquote>
<blockquote type=3D"cite"><span>an important distinction, IMO.</span><br>
</blockquote>
<span></span><br>
<span>Right, I understand now. It's the logical NAT function that is IPv4-o=
nly, not the global use case. I'll add some text to make this clear, and I'=
ll specifically point out the DS-Lite example.</span><br>
<span></span><br>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>How about &quot;Common Requirements for IPv=
4 Carrier Grade NATs</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>(CGNs)&quot;?</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite"><span>[WEG] This helps, but only in conjunction w=
ith additional</span><br>
</blockquote>
<blockquote type=3D"cite"><span>clarification about the application - that =
is, just because the NAT</span><br>
</blockquote>
<blockquote type=3D"cite"><span>is IPv4-only doesn't mean that the network =
must also be IPv4-only.</span><br>
</blockquote>
<span></span><br>
<span>Understood.</span><br>
<span></span><br>
<span>Simon</span><br>
<span>-- </span><br>
<span>DTN made easy, lean, and smart --&gt; <a href=3D"http://postellation.=
viagenie.ca">
http://postellation.viagenie.ca</a></span><br>
<span>NAT64/DNS64 open-source &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--&=
gt; <a href=3D"http://ecdysis.viagenie.ca">http://ecdysis.viagenie.ca</a></=
span><br>
<span>STUN/TURN server &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--&gt; <a href=3D"http://numb.viagenie.ca">=
http://numb.viagenie.ca</a></span><br>
<span>_______________________________________________</span><br>
<span>sunset4 mailing list</span><br>
<span><a href=3D"mailto:sunset4@ietf.org">sunset4@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/sunset4">https://www=
.ietf.org/mailman/listinfo/sunset4</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_1DF204BCFAD64A0E90B064760CC1ECF9huaweicom_--

From dromasca@avaya.com  Wed Jul 11 09:15:54 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 69B2611E8096; Wed, 11 Jul 2012 09:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.166
X-Spam-Level: 
X-Spam-Status: No, score=-103.166 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYWfYyp0m4nI; Wed, 11 Jul 2012 09:15:53 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id AD6DB11E80C6; Wed, 11 Jul 2012 09:15:52 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAIil/U+HCzI1/2dsb2JhbABFt2qBB4IgAQEBAQIBAQIPHgo0CwUHBAIBCA0EBAEBCwYMBwQBBgEnHgkIAQEEEwgah2UGC6A+nSSLQBQHhHNgA5MRgzuEZooOgmGBVA
X-IronPort-AV: E=Sophos;i="4.77,569,1336363200"; d="scan'208";a="314661320"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 11 Jul 2012 12:13:01 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 11 Jul 2012 11:57:13 -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: Last Call: <draft-ietf-6lowpan-btle-08.txt> (Transmission of IPv6Packets over Bluetooth Low Energy) to Proposed Standard
Date: Wed, 11 Jul 2012 18:16:13 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407D540DA@307622ANEX5.global.avaya.com>
In-Reply-To: <20120627134954.8523.85676.idtracker@ietfa.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-ietf-6lowpan-btle-08.txt> (Transmission of IPv6Packets over Bluetooth Low Energy) to Proposed Standard
Thread-Index: Ac1Ua8dHAPPq85z/Qn2maxl+Cl5SIwLDac5g
References: <20120627134954.8523.85676.idtracker@ietfa.amsl.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ietf@ietf.org>
Cc: 6lowpan@ietf.org, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 16:15:54 -0000

Overall this is a good document and I support its approval. A few items
should be clarified before approval, please see below:=20

1. In the introduction:=20

>  In addition,
   IPv6 provides tools for autoconfiguration, which is particularly
   suitable for sensor network applications and nodes which have very
   limited processing power or a full-fledged operating system.

Did you actually mean to say 'nodes which have very limited processing
power or lack a full-fledged operating system'?=20

Also - what do you exactly mean by tools for autoconfiguration - is this
only about stateless IP-address autoconfiguration or (also) something
else?=20

2. In Section 2.1 - GAP stands for Generic Access Profile (as in the
text) or Generic Attribute Profile (as in the diagram)?=20

3. Section 2.3 we have=20

> ' A Bluetooth Smart device such as a sensor may use
   a public (obtained from IEEE Registration Authority) '

and then in 3.2.1=20


>  'The 48-bit public bluetooth
   address is globally unique and provided by the IEEE registration
   authority.'

These are slightly inaccurate. The individual addresses are not directly
assigned by the IEEE-RA. This authority only assigns OUIs to vendors
(first 24 bits of an address) which then are responsible on
administrating their own space (the last 24 bit) to generate unique
addresses. Actually another sentence in 2.3 gets it right when it says:=20

> ' The public address is created
   according to the IEEE 802-2001 standard [IEEE802-2001] and using a
   valid Organizationally Unique Identifier (OUI) obtained from the IEEE
   Registration Authority.  '

4. I do not believe that the requirement to BT SIG for the allocation of
an L2CAP channel ID needs to be mentioned in the IANA Considerations
section as it has nothing to do with IANA. =20

Regards,

Dan

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: Wednesday, June 27, 2012 4:50 PM
> To: IETF-Announce
> Cc: 6lowpan@lists.ietf.org
> Subject: Last Call: <draft-ietf-6lowpan-btle-08.txt> (Transmission of
> IPv6Packets over Bluetooth Low Energy) to Proposed Standard
>=20
>=20
> The IESG has received a request from the IPv6 over Low power WPAN WG
> (6lowpan) to consider the following document:
> - 'Transmission of IPv6 Packets over Bluetooth Low Energy'
>   <draft-ietf-6lowpan-btle-08.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-07-11. Exceptionally, comments may
> be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    Bluetooth Low Energy is a low power air interface technology
defined
>    by the Bluetooth Special Interest Group (BT-SIG).  The standard
>    Bluetooth radio has been widely implemented and available in mobile
>    phones, notebook computers, audio headsets and many other devices.
>    The low power version of Bluetooth is a new specification and
enables
>    the use of this air interface with devices such as sensors, smart
>    meters, appliances, etc.  The low power variant of Bluetooth is
>    commonly specified in revision 4.0 of the Bluetooth specifications
>    and commonly refered to as Bluetooth 4.0.  This document describes
>    how IPv6 is transported over Bluetooth Low Energy using 6LoWPAN
>    techniques.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-6lowpan-btle/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-6lowpan-btle/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20


From hartmans@mit.edu  Wed Jul 11 09:46:56 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 499F421F85F0; Wed, 11 Jul 2012 09:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.259
X-Spam-Level: 
X-Spam-Status: No, score=-103.259 tagged_above=-999 required=5 tests=[AWL=-0.994, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zbjGmE3-IRhU; Wed, 11 Jul 2012 09:46:55 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id D064321F85EF; Wed, 11 Jul 2012 09:46:55 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 13BA5203BA; Wed, 11 Jul 2012 12:47:54 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 5BCEA41F0; Wed, 11 Jul 2012 12:47:16 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Simon Perreault <simon.perreault@viagenie.ca>
Subject: Re: [sunset4] Last Call: <draft-ietf-behave-lsn-requirements-07.txt> (Common requirements for Carrier Grade NATs (CGNs)) to Best Current Practice
References: <DCC302FAA9FE5F4BBA4DCAD4656937791745903045@PRVPEXVS03.corp.twcable.com> <4FF8A836.2090407@viagenie.ca> <DCC302FAA9FE5F4BBA4DCAD4656937791745A1F0D4@PRVPEXVS03.corp.twcable.com> <4FFAF400.1030201@viagenie.ca> <1DF204BC-FAD6-4A0E-90B0-64760CC1ECF9@huawei.com> <4FFD8727.4020207@viagenie.ca>
Date: Wed, 11 Jul 2012 12:47:16 -0400
In-Reply-To: <4FFD8727.4020207@viagenie.ca> (Simon Perreault's message of "Wed, 11 Jul 2012 10:01:11 -0400")
Message-ID: <tsld3425jor.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: "behave@ietf.org" <behave@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 16:46:56 -0000

Hi. I'd like to speak in favor of maintaining endpoint independent
filtering as the default and maintaining requirement 11 D.  I think
requirement 11 D is important for avoiding some hard to analyze but
potentially very dangerous security problems. If I can trick a NAT into
replacing an existing mapping by causing resource exhaustion then I
could probably attack that.  Unfortunately such attacks tend to appear
minor or hard to exploit until someone puts together what turns out to
be a fairly reliable exploit against some equipment, then you have a
real mess.

I believe the stability of application argument argues for endpoint
independent filtering.

From sm@resistor.net  Wed Jul 11 17:08: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 6DE3311E8126; Wed, 11 Jul 2012 17:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level: 
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NMfCPE4hZM6f; Wed, 11 Jul 2012 17:08:33 -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 0574211E80C6; Wed, 11 Jul 2012 17:08: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 q6C08uE6014693; Wed, 11 Jul 2012 17:09:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342051743; bh=8w6mO/YQXx3NYsLSfj//f0S5H46KAMSfu2Mq5v3xCno=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pwycZV4ND2GWWVnF8oA0NLrwFb82XuZxk8V8y94fuBwxfyqtsXbOx639mZw7HDWq2 K+TVSL0AUWfW4VkfNQ9+ful+H8UYZrIDKtgzzUfGfXsaJGvimEYksLeHo4E8bqDTf3 HoiOiNZWqyePiXHltTidKgzUWiS3NtmdoHmTV0HI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342051743; i=@resistor.net; bh=8w6mO/YQXx3NYsLSfj//f0S5H46KAMSfu2Mq5v3xCno=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uZLyimhvx1eGhBHzzjLnPfgnsximRhfXir6pX3K4vQHLfxeLDu7gVsMRJXQvcPUBA qrBYIQtWwC+2ONfq44r66yQ8O63E4tzTzv+cnMl6DN7ec5ZjQg/+s5f3DSxNf1eLnN aLSyedRHmU2zYuSrRkLz5OLiDFYtPOA+DJFsBITE=
Message-Id: <6.2.5.6.2.20120711154825.09f09be8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 11 Jul 2012 16:48:19 -0700
To: Andreas Petersson <andreas@sbin.se>
From: SM <sm@resistor.net>
Subject: Re: [apps-discuss] Last Call:  <draft-ietf-appsawg-http-forwarded-06.txt> (Forwarded HTTP Extension)  to Proposed Standard
In-Reply-To: <20120711154158.60f6ecf0@hetzer>
References: <20120709162848.23418.51856.idtracker@ietfa.amsl.com> <22B6DCC8-3BBF-4C64-876E-13ABFBE6CB2F@cdt.org> <6.2.5.6.2.20120709134136.0ad9ae18@resistor.net> <20120710132825.5141babe@hetzer> <6.2.5.6.2.20120710081323.08c9bcf8@resistor.net> <20120711154158.60f6ecf0@hetzer>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IETF Discussion Mailing List <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 00:08:37 -0000

Hi Andreas,
At 06:41 11-07-2012, Andreas Petersson wrote:
>How is it "random bits of information" when the specifications says
>that it MUST be underscore?
>
>As far as I can think of, the only thing that it will tell is that the
>implementation is following this specification.
>So, on the contrary; the more "degrees of freedom" that is given to the
>implementation, the easier it would be to do fingerprinting.

I could use a hash.  If the hash has to begin with an underscore, I 
have to reserve storage space for it.  The ease for fingerprinting 
depends on how Section 6.3 is implemented (see reference I posted on 
WG mailing list about browser identification).  I am ok if you want 
to keep the requirement.

Regards,
-sm 


From shanna@juniper.net  Wed Jul 11 19:20:42 2012
Return-Path: <shanna@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB0511E810F; Wed, 11 Jul 2012 19:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xW-RVuNHosO1; Wed, 11 Jul 2012 19:20:42 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB7711E809A; Wed, 11 Jul 2012 19:20:33 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKT/40kb7m4HH3ifxxQIx3pl9X6T1R8V6z@postini.com; Wed, 11 Jul 2012 19:21:14 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 11 Jul 2012 19:19:36 -0700
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 11 Jul 2012 19:19:35 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 11 Jul 2012 22:19:35 -0400
From: Stephen Hanna <shanna@juniper.net>
To: "ietf@ietf.org" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>, "draft-ietf-6lowpan-btle.all@tools.ietf.org" <draft-ietf-6lowpan-btle.all@tools.ietf.org>
Date: Wed, 11 Jul 2012 22:19:33 -0400
Subject: secdir review of draft-ietf-6lowpan-btle-08
Thread-Topic: secdir review of draft-ietf-6lowpan-btle-08
Thread-Index: Ac1f1Ma24oacIUSEQV6zGZ0doNIaNw==
Message-ID: <AC6674AB7BC78549BB231821ABF7A9AEB833166881@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 02:20:43 -0000

I have reviewed this document as part of the security directorate's=20
ongoing effort to review all IETF documents being processed by the=20
IESG.  These comments were written primarily for the benefit of the=20
security area directors.  Document editors and WG chairs should treat=20
these comments just like any other last call comments.

This document describes how IPv6 is transported over Bluetooth
Low Energy (BT-LE).

As a proviso, I am not an expert in IPv6, 6LoWPAN, or Bluetooth.
Still, this document seemed to be a clear specification of the
intended subject matter. The Security Considerations section
says that the security concerns are similar to those for IPv6
over 802.15.4. That makes sense, I suppose.

I was happy to see that this document says "IPv6 over BT-LE
SHOULD be protected by using BT-LE Link Layer security", whereas
RFC 4944 (IPv6 over 802.15.4) does not include any normative
language on using link layer security. Also, this document says
that "Key management in BT-LE is provided by the Security Manager
Protocol (SMP)", whereas RFC 4944 says that no key management
is provided by 802.15.4. So this specification is apparently
more secure that RFC 4944. That's good.

So based on my review (admitting little knowledge of BT-LE),
this document seems to be an improvement over the current
state of the art for 6LoWPAN from a security perspective.
And the overall level of security seems reasonable.
I have no objection to the publication of this document.

I did notice two typos:

gateway^1s =3D> gateway's
respectively =3D> respectively

Thanks,

Steve


From alexey.melnikov@isode.com  Thu Jul 12 05:08:03 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4647121F85CD for <ietf@ietfa.amsl.com>; Thu, 12 Jul 2012 05:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.97
X-Spam-Level: 
X-Spam-Status: No, score=-102.97 tagged_above=-999 required=5 tests=[AWL=-0.371, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UyWvEILuMrrA for <ietf@ietfa.amsl.com>; Thu, 12 Jul 2012 05:08:02 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE9521F855B for <ietf@ietf.org>; Thu, 12 Jul 2012 05:08:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1342094914; d=isode.com; s=selector; i=@isode.com; bh=R2FI7GkDPMtvc/SOVXjzRx912BWIb9GfSb8IagcYKK4=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=surRj/6IsLzx8nOW89sJwcSUQ+MahrpvmhEUYiS7pd2gH5BJn2U1RP1+5myQz8xhMObFHA VPfQklOUjFAzWmamkliQ1/s2F2xDxGsAlzAnLGF1s9W5Mi2hC5uSZThRr7rrC9vtYWfP8K zcp6sNrHNsKu3P8tDzXN7ZwoZBQLIyA=;
Received: from [192.168.1.144] ((unknown) [62.3.217.253])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <T=6-QQBcm3-y@statler.isode.com>; Thu, 12 Jul 2012 13:08:34 +0100
X-SMTP-Protocol-Errors: NORDNS PIPELINING
Message-ID: <4FFEBE5A.6080406@isode.com>
Date: Thu, 12 Jul 2012 13:08:58 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-tunneling-02.txt>  (Tunneling of SMTP Message Transfer Priorities) to Experimental RFC
References: <20120604200531.8859.1367.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120605113303.0aa1b028@resistor.net>
In-Reply-To: <6.2.5.6.2.20120605113303.0aa1b028@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-melnikov-smtp-priority-tunneling@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 12:08:03 -0000

Hi SM,
Thank you for the comments.

On 06/06/2012 22:39, SM wrote:
> At 13:05 04-06-2012, The IESG wrote:
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Tunneling of SMTP Message Transfer Priorities'
>>   <draft-melnikov-smtp-priority-tunneling-02.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>
> In the Introduction section:
>
> Typo: scenarious.

Fixed, thanks.

> In Section 3.1:
>
>   "This specification inserts the following between steps 3 and 4 in
>    Section 4.1 of [SMTP-PRIORITY]:"
>
> The specification would be updating draft-melnikov-smtp-priority 
> according to the above.
>
>  "3b.  In absence of both the MT-PRIORITY MAIL FROM parameter and the
>         MT-Priority header field, other message header fields, such as
>         Priority [RFC2156] and X-Priority, MAY be used for determining
>         the priority under this "Priority Message Handling" SMTP
>         extension.  But note that the Importance [RFC2156] header field
>         MUST NOT be used for determining the priority under this
>         "Priority Message Handling" SMTP extension, as it has different
>         semantics: the Importance header field is aimed at the user
>         recipient and not at the nodes responsible for transferring the
>         message."
>
> X-Priority, for example, is undocumented.

Yes. Albeit widely used.

> If I understood the above correctly, the MTA chooses some higher 
> priority when it sees any of these header fields.

MT-Priority header field always takes precedence, but in its absence 
other header fields can be used.

> In Section 7:
>
>   "Thus it is important to ensure that an MTA receiving a message
>    containing the MT-Priority header field can trust that it
>    was set by an authorized agent.  Such trust can be realized, for
>    example, by using DKIM Section 7.1 to sign the MT-Priority header
>    field value, S/MIME, or by keeping a list of trusted senders (e.g.
>    within a close environment)."
>
> I don't see how DKIM can be used to ensure that the header field was 
> set by an authorized agent.  I assume that any SMTP client within the 
> (DKIM) signing domain could generate a MT-Priority header field as I 
> don't know the DKIM signing policy.  As an example, I consider that 
> msg-id 3D9B1776-6DFD-4B80-97C6-FA8774DB7BA9@ietf.org as was generated 
> by an authorized agent on behalf of the IETF Chair but I would not 
> describe it as trusted.

Ok, this text is wrong, I will try to rewrite it.
DKIM enables binding between a priority value and a signer. Recipient 
still needs to have a policy for deciding which signers are to be trusted.

>   "Message Submission Agents MUST implement a policy that only allows"
>
> I suggest using the same text as in draft-melnikov-smtp-priority.

Yes, I just updated my copy. The change will be in -03.

>   "To protect MT-Priority header field from modification or insertion,
>    MUAs, MSAs and MTAs inserting it into messages SHOULD use message
>    header protection mechanism such as DKIM [RFC6376]."
>
> I read Section 7.1 as a case for not following the above 
> recommendation.  Any attempt to change priority means breaking the 
> DKIM signature.

Correct. It is a trade-off.

> I am not proposing text to avoid a significant rewrite of the proposal.


From bill.wu@huawei.com  Thu Jul 12 00:58:41 2012
Return-Path: <bill.wu@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 CFF1321F8783; Thu, 12 Jul 2012 00:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.392
X-Spam-Level: 
X-Spam-Status: No, score=-4.392 tagged_above=-999 required=5 tests=[AWL=0.454,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rdZaBlePsaHN; Thu, 12 Jul 2012 00:58:41 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id E00F121F85B6; Thu, 12 Jul 2012 00:58:40 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHR53021; Thu, 12 Jul 2012 03:59:13 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jul 2012 00:56:58 -0700
Received: from SZXEML407-HUB.china.huawei.com (10.82.67.94) by dfweml403-hub.china.huawei.com (10.193.5.151) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jul 2012 00:57:03 -0700
Received: from w53375 (10.138.41.149) by szxeml407-hub.china.huawei.com (10.82.67.94) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jul 2012 15:56:54 +0800
Message-ID: <E54DAFE660B4438F9B14C185CF72200C@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: <ietf@ietf.org>
Subject: Fw: [xrblock] I-D Action:draft-ietf-xrblock-rtcp-xr-meas-identity-08.txt
Date: Thu, 12 Jul 2012 15:56:50 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Thu, 12 Jul 2012 11:12:10 -0700
Cc: Pete Resnick <presnick@qualcomm.com>, xrblock@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2012 07:58:42 -0000

DQpPbiAxMiBKdWx5ICwgMjAxMiAxNTo0NiBQTSwgSW50ZXJuZXQtRHJhZnRzQGlldGYub3JnIHdy
b3RlOg0KDQo+IA0KPiBBIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUgZnJvbSB0aGUg
b24tbGluZSBJbnRlcm5ldC1EcmFmdHMgZGlyZWN0b3JpZXMuDQo+IFRoaXMgZHJhZnQgaXMgYSB3
b3JrIGl0ZW0gb2YgdGhlIE1ldHJpYyBCbG9ja3MgZm9yIHVzZSB3aXRoIFJUQ1AncyBFeHRlbmRl
ZCBSZXBvcnQgRnJhbWV3b3JrIFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuDQo+IA0KPiBUaXRs
ZSAgICAgICAgICAgOiBNZWFzdXJlbWVudCBJZGVudGl0eSBhbmQgaW5mb3JtYXRpb24gUmVwb3J0
aW5nIHVzaW5nIFNERVMgaXRlbSBhbmQgWFIgQmxvY2sNCj4gQXV0aG9yKHMpICAgICAgIDogR2Vv
ZmYgSHVudA0KPiAgICAgICAgICAgICAgICAgICAgICAgICAgQWxhbiBDbGFyaw0KPiAgICAgICAg
ICAgICAgICAgICAgICAgICAgUWluIFd1DQo+IEZpbGVuYW1lICAgICAgICA6IGRyYWZ0LWlldGYt
eHJibG9jay1ydGNwLXhyLW1lYXMtaWRlbnRpdHktMDgudHh0DQo+IFBhZ2VzICAgICAgICAgICA6
IDE2DQo+IERhdGUgICAgICAgICAgICA6IDIwMTItMDctMDkNCj4gDQo+IEFic3RyYWN0Og0KPiAg
IFRoaXMgZG9jdW1lbnQgZGVmaW5lcyBhbiBSVFAgQ29udHJvbCBQcm90b2NvbCAoUlRDUCkgU291
cmNlDQo+ICAgRGVzY3JpcHRpb24gKFNERVMpIGl0ZW0gYW5kIGFuIFJUQ1AgRXh0ZW5kZWQgUmVw
b3J0IChYUikgQmxvY2sNCj4gICBjYXJyeWluZyBwYXJhbWV0ZXJzIHRoYXQgaWRlbnRpZnkgYW5k
IGRlc2NyaWJlIGEgbWVhc3VyZW1lbnQgcGVyaW9kLA0KPiAgIHRvIHdoaWNoIG9uZSBvciBtb3Jl
IG90aGVyIFJUQ1AgWFIgUmVwb3J0IEJsb2NrcyBtYXkgcmVmZXIuDQo+IA0KPiANCj4gVGhlIElF
VEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6DQo+IGh0dHBzOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYteHJibG9jay1ydGNwLXhyLW1lYXMt
aWRlbnRpdHkNCj4gDQo+IFRoZXJlJ3MgYWxzbyBhIGh0bWxpemVkIHZlcnNpb24gYXZhaWxhYmxl
IGF0Og0KPiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXhyYmxvY2stcnRj
cC14ci1tZWFzLWlkZW50aXR5LTA4DQoNCltRaW5dOiAgSnVzdCByZW1pbmQgeW91IHRoYXQgd2Ug
aGF2ZSBzdWJtaXR0ZWQgdGhlIE5ldyB2ZXJzaW9uICgtMDgpIG9mIG1lYXN1cmVtZW50IGlkZW50
aXR5IGRyYWZ0Lg0KVGhpcyB2ZXJzaW9uIGFkZHJlc3NlcyB0aGUgY29tbWVudHMgZHVyaW5nIElF
VEYgTEMgYmFzZWQgb24gd2hhdCB3ZSBkaXNjdXNzZWQNCmFuZCBhZ3JlZWQgb24gdGhlIGxpc3Qg
c28gZmFyLiBUaGFua3MgUGV0ZSwgQnJpYW4sIGFuZCBSb2JlcnQgZm9yIHlvdXIgdmFsdWFibGUg
Y29tbWVudHMuDQoNCj4gQSBkaWZmIGZyb20gcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUg
YXQ6DQo+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi14cmJs
b2NrLXJ0Y3AteHItbWVhcy1pZGVudGl0eS0wOA0KDQo=


From narten@us.ibm.com  Thu Jul 12 21:53:35 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 8ACA221F8652 for <ietf@ietfa.amsl.com>; Thu, 12 Jul 2012 21:53:35 -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, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gy1mbQOv5BPU for <ietf@ietfa.amsl.com>; Thu, 12 Jul 2012 21:53:34 -0700 (PDT)
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by ietfa.amsl.com (Postfix) with ESMTP id 7495521F8644 for <ietf@ietf.org>; Thu, 12 Jul 2012 21:53:33 -0700 (PDT)
Received: from /spool/local by e37.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 12 Jul 2012 22:54:07 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e37.co.us.ibm.com (192.168.1.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 12 Jul 2012 22:53:06 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id BB43A3E40049 for <ietf@ietf.org>; Fri, 13 Jul 2012 04:53:05 +0000 (WET)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q6D4r5jF266012 for <ietf@ietf.org>; Thu, 12 Jul 2012 22:53:05 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q6D4r43Q002876 for <ietf@ietf.org>; Thu, 12 Jul 2012 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q6D4r3ar002755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 12 Jul 2012 22:53:04 -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 q6D4r3Kp019072 for <ietf@ietf.org>; Fri, 13 Jul 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q6D4r2V2019038 for ietf@ietf.org; Fri, 13 Jul 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201207130453.q6D4r2V2019038@rotala.raleigh.ibm.com>
Date: Fri, 13 Jul 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: 12071304-7408-0000-0000-000006BB0E9C
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 04:53:35 -0000

Total of 48 messages in the last 7 days.
 
script run at: Fri Jul 13 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 14.58% |    7 | 14.77% |    53370 | andreas@sbin.se
 14.58% |    7 | 14.50% |    52367 | simon.perreault@viagenie.ca
  8.33% |    4 |  7.11% |    25667 | sm@resistor.net
  6.25% |    3 |  6.14% |    22184 | acooper@cdt.org
  6.25% |    3 |  6.04% |    21832 | hartmans-ietf@mit.edu
  4.17% |    2 |  4.95% |    17897 | wesley.george@twcable.com
  4.17% |    2 |  4.53% |    16378 | abdussalambaryun@gmail.com
  4.17% |    2 |  4.36% |    15761 | tony@att.com
  4.17% |    2 |  3.41% |    12330 | john-ietf@jck.com
  4.17% |    2 |  3.28% |    11832 | miyakawa@nttv6.jp
  2.08% |    1 |  3.75% |    13544 | tina.tsou.zouting@huawei.com
  2.08% |    1 |  2.71% |     9801 | rbarnes@bbn.com
  2.08% |    1 |  2.59% |     9358 | stephen.farrell@cs.tcd.ie
  2.08% |    1 |  2.56% |     9253 | dromasca@avaya.com
  2.08% |    1 |  2.45% |     8860 | richard@shockey.us
  2.08% |    1 |  2.44% |     8822 | housley@vigilsec.com
  2.08% |    1 |  2.42% |     8743 | alexey.melnikov@isode.com
  2.08% |    1 |  2.13% |     7683 | narten@us.ibm.com
  2.08% |    1 |  1.89% |     6835 | shanna@juniper.net
  2.08% |    1 |  1.88% |     6773 | bill.wu@huawei.com
  2.08% |    1 |  1.72% |     6207 | chair@ietf.org
  2.08% |    1 |  1.57% |     5687 | w@1wt.eu
  2.08% |    1 |  1.40% |     5066 | robert@raszuk.net
  2.08% |    1 |  1.38% |     4976 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |   48 |100.00% |   361226 | Total


From gonzalo.camarillo@ericsson.com  Thu Jul 12 23:43:05 2012
Return-Path: <gonzalo.camarillo@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 E57E621F86A7; Thu, 12 Jul 2012 23:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.214
X-Spam-Level: 
X-Spam-Status: No, score=-106.214 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAP-mTuS94-r; Thu, 12 Jul 2012 23:43:04 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 2596321F8466; Thu, 12 Jul 2012 23:43:03 -0700 (PDT)
X-AuditID: c1b4fb25-b7fb66d000003bb6-a0-4fffc39a255d
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 50.7F.15286.A93CFFF4; Fri, 13 Jul 2012 08:43:38 +0200 (CEST)
Received: from [131.160.126.248] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.264.0; Fri, 13 Jul 2012 08:43:37 +0200
Message-ID: <4FFFC399.8010506@ericsson.com>
Date: Fri, 13 Jul 2012 09:43:37 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [xrblock] Last Call: <draft-ietf-xrblock-rtcp-xr-meas-identity-06.txt> (Measurement	Identity and information Reporting using SDES item	and XR	Block) to Proposed Standard
References: <20120531125607.4884.38983.idtracker@ietfa.amsl.com>
In-Reply-To: <20120531125607.4884.38983.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOLMWRmVeSWpSXmKPExsUyM+Jvre6sw//9DTYcELV4tnE+i8WUC49Y HJg8liz5yRTAGMVlk5Kak1mWWqRvl8CV0bM3t+AAf8WbI7INjJd5uhg5OSQETCRW/bvIBmGL SVy4tx7I5uIQEjjFKDHz0FtGCGcto8T07hfsIFW8AtoSX49/ZgSxWQRUJWbv+QUWZxOwkNhy 6z4LiC0qECwxr/smC0S9oMTJmU/AbBEBZYkDM2+wgtjMApoSOxZNZgVZICywi1GifdtrZpCE kICDxNtb+5hAbE4BR4knT78zQpwnKXGvfTUbRLOexJSrLYwQtrzE9rdzoHq1JZY/a2GZwCg0 C8nuWUhaZiFpWcDIvIpRODcxMye93EgvtSgzubg4P0+vOHUTIzBwD275rbqD8c45kUOM0hws SuK81lv3+AsJpCeWpGanphakFsUXleakFh9iZOLglGpgbCm7yRvA9uTwH1fm27vOF2TPjd9Z 8cvkXEWMecSCPwWmdx76bKnO255+lO9TKMfPHn9um5W7JlyS5bsx/dSpFu466bntJxgDnF7L MHBZ1t52EIsLmBNldDJnzx3rpy9tLD6+PKN5THmOph7rjuO1XxpU5AxiA56cZm10vdMe/OdF zKzESafklFiKMxINtZiLihMB+tGPfyoCAAA=
Cc: "xrblock@ietf.org" <xrblock@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 06:43:06 -0000

Hi,

note that during the IESG evaluation of this document, the WG has
decided to use timestamps in the NTP format. You can see the diff
between 07 and 08 here:

http://tools.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-ietf-xrblock-rtcp-xr-meas-identity-08.txt

At this point, there are no remaining discusses. I intend to approve
this draft shortly.

http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-meas-identity/ballot/

Cheers,

Gonzalo


On 31/05/2012 3:56 PM, The IESG wrote:
> 
> The IESG has received a request from the Metric Blocks for use with
> RTCP's Extended Report Framework WG (xrblock) to consider the following
> document:
> - 'Measurement Identity and information Reporting using SDES item and XR
>    Block'
>   <draft-ietf-xrblock-rtcp-xr-meas-identity-06.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-06-14. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document defines an RTP Control Protocol (RTCP) Source
>    Description (SDES) item and an RTCP Extended Report (XR) Block
>    carrying parameters that identify and describe a measurement period,
>    to which one or more other RTCP XR Report Blocks may refer.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-meas-identity/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-xrblock-rtcp-xr-meas-identity/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
> 
> 


From sm@resistor.net  Fri Jul 13 12:42: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 87BBF11E80FF for <ietf@ietfa.amsl.com>; Fri, 13 Jul 2012 12:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qFTExzlKs+S2 for <ietf@ietfa.amsl.com>; Fri, 13 Jul 2012 12:42:02 -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 72B8F11E8101 for <ietf@ietf.org>; Fri, 13 Jul 2012 12:42:02 -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 q6DJgWC5022181; Fri, 13 Jul 2012 12:42:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342208557; bh=MaYNG94Tg1rLkq82CCeDY1xbmHH8r0BouW3YEmIlb4o=; h=Date:To:From:Subject:Cc; b=nb5JkqY61kreIUyMX6/euzPfD7KV9qEDeXQwNH/koYx74DPzJFK0z6fWG7stiX79N +yF9LhHhZK01ZVl6+Lpmu25VER29SXjBrkFvQpF3cqzWhOZwpJyKcumAF7XPKZ4JeG PA6hqDR+z4kpCmAWzQRmPtt+vVjnsFP7w4uaYxHY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342208557; i=@resistor.net; bh=MaYNG94Tg1rLkq82CCeDY1xbmHH8r0BouW3YEmIlb4o=; h=Date:To:From:Subject:Cc; b=bykHOnK1tConVvkq/YhbYyLCTUplWaF3w6q5bC9Z+4fdGPP60DDa9XkPod2JRL6qb iklTyRT4MH+z8MnbmTHKYDs4dBDJriK3tE44hnfq4R5DI8Fhyz5AwKmohxxMm+bSqC RUmixwm9WyQxs36ghm/fpCuFzTqqr60wO1nhK23s=
Message-Id: <6.2.5.6.2.20120713091055.099f8d78@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 13 Jul 2012 12:41:56 -0700
To: Jari Arkko <jari.arkko@piuha.net>
From: SM <sm@resistor.net>
Subject: Comments on draft-arkko-iesg-crossarea-01
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, 13 Jul 2012 19:42:06 -0000

Hi Jari,

In Section 3:

   "In other cases different organizations may have specific expertise
    that is helpful to solve a problem."

Did you mean individuals?

In Section 4:

   "Current IETF scheduling principle is centered around a sequences
    of meetings of working groups in the same area."

There are some area-wide groups meetings.  I'll list the area against 
the areas for the WGs meeting at the same time:

   APP - INT OPS RAI RTG TSV
   TSV - APP INT OPS RAI RTG
   INT - APP OPS RAI SEC TSV
   RTG - APP INT OPS RAI SEC
   SEC - INT OPS RAI RTG

APP and SEC can follow each other.  The other areas have more conflicts.

In Section 5:

   "Cross-area review.  Similarly, expertise is not brought in by an
    area designation, it is brought through the right people
    actually reading the specifications.  Encouraging cross-area
    review is therefore helpful, for instance through directorates
    assigned to review important documents from other areas."

How are important documents from other areas identified?  I rarely 
see messages saying "this might be of interest to your area" with an 
explanation to incite interest (excluding "please review my draft"). 
The cross-area review may be perceived by some people as a burden 
they could do away with.  There is the following question in the write-up:

  "Do portions of the document need review from a particular or from
   broader perspective?"

There are rarely cross-area comments in reply to that question.

The list of directorates and review teams is at 
http://www.ietf.org/iesg/directorate.html     Most of them rarely do 
reviews.  There was a draft with five (or more) listed authors.  None 
of them responded to the review.  The AD provided feedback.  There is 
a document shepherd for each draft.  Only a few of them are 
responsive.  The reviewer ends up trying to explain to the author(s) 
details which the document shepherd could have done.

There should be a checkbox somewhere which says "further review is 
discouraged".  Reviewers would not have to waste their time and 
effort reading a long draft.  They don't have any financial or other 
interest in it anyway.  So why bother?

   "Extensions for a specific application purpose (such as delivering
    location information) must be owned by some other working group that
    is chartered to develop those applications (such as the GEOPRIV WG
    in the Real-Time Applications Area)."

Stephen Farrell posted a question during a Last Call ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg73924.html ).  I 
didn't see any feedback from GEOPRIV on that.

   "Scheduling models for the IETF should take cross-area work into
    account in a better way.  Possible tools to improve this include
    ability to specify ADs from multiple areas as interested in a
    working group or the ability to specify entire areas as
    conflicts in the meeting request tool."

The above focuses on how to get the relevant ADs in the room.  It's 
more about AD scheduling than cross-area scheduling.

One could look at this in terms of the relation of the work with 
other areas.  There was a message from ADs in an area requesting a 
summary of what their WGs have been up to.  It's a way for the 
average participant to get a quick view of what has being discussed 
and what are the issues.  The person might also be able to identify 
topics of interest.  That's more fine-grained than area.  It might 
attract a larger number of participants.

I'll highlight an important point from the draft:

   "People matter, organizations do not.  The essence of most cross-
    area work is getting the right expertise to the room and to the
    list.  This does not happen through mere organizational forms,
    people have to be interested about the problem."

Let's take the IESG out of the equation.  How do you get people will 
the right expertise in the room and on the list?  The draft mentions 
"chair and advisor" selection.  That addresses the organizational 
form.  Most people are volunteers and do not have the time to keep up 
with more than a few mailing lists.  Some of them might end up 
following only Area WGs during a meeting.  There isn't much 
opportunity, or maybe it's a lack of incentive, to talk to people 
from outside the area.

The draft is well-written and it covers the challenges.  I am left 
with a sense that the recommendations are viewed more in terms of 
meetings and the IESG.

Regards,
-sm


From sm@elandsys.com  Fri Jul 13 09:09:26 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3356211E80D5 for <ietf@ietfa.amsl.com>; Fri, 13 Jul 2012 09:09:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=-0.069, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FZ8KKGVA06eJ for <ietf@ietfa.amsl.com>; Fri, 13 Jul 2012 09:09:22 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DB72211E80CD for <ietf@ietf.org>; Fri, 13 Jul 2012 09:09:21 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.235.253]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q6DG9jdS019278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 13 Jul 2012 09:09:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342195797; bh=LBuuTfL4bPQCSCJFl02pBOZkeW1ahpXX/50DUw0ncrU=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=Y1phWmesTLdymx4hQCwLNhDaxO0Mp4QEvab/76wv6Tp0QQ2NMevodtT99CWhNici+ HNXb9f2Ku1r0J0N46ygLyf6YkknZtJ/sy0PXY5q8amYhCfCtBVRX7f6xEXR0ffax2A QAWwgXXhWbholLC/RdIHrkNJyltOXN+itli9oD+c=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1342195797; i=@elandsys.com; bh=LBuuTfL4bPQCSCJFl02pBOZkeW1ahpXX/50DUw0ncrU=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=BqHR8nTt4mYC+//O2WWpMHDDpYTONwPTOH2Xnt26lgIjYZOXiFy+/Ln2jhcFNqRY8 fX3KnAScAKwB1f9TVFX6Ne3PEb4+6RSuPKOHFp76gDrnGcGpn8ChwtQYhTlt9efu+Q 9zKVtaCwyj0oZwHInrEPRubOG+kqDcmpXU2dbjwA=
Message-Id: <6.2.5.6.2.20120713083919.09925228@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 13 Jul 2012 08:41:24 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-vegoda-cotton-rfc5735bis-02.txt> (Special Use IPv4 Addresses) to Best Current Practice
In-Reply-To: <20120712224629.14063.15257.idtracker@ietfa.amsl.com>
References: <20120712224629.14063.15257.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Fri, 13 Jul 2012 13:45: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: Fri, 13 Jul 2012 16:09:26 -0000

At 15:46 12-07-2012, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Special Use IPv4 Addresses'
>   <draft-vegoda-cotton-rfc5735bis-02.txt> as Best Current Practice

Please see comments at 
http://www.ietf.org/mail-archive/web/ietf/current/msg73560.html

Regards,
S. Moonesamy 


From randy@psg.com  Fri Jul 13 16:20:41 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 798FF21F85B4; Fri, 13 Jul 2012 16:20:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zbXYuXyQZHqE; Fri, 13 Jul 2012 16:20:40 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id DD17321F858D; Fri, 13 Jul 2012 16:20:39 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SppAe-0006Wz-T0; Fri, 13 Jul 2012 23:21:13 +0000
Date: Sat, 14 Jul 2012 08:21:11 +0900
Message-ID: <m24npbckns.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>, The IESG <iesg-secretary@ietf.org>
Subject: Re: Last Call: <draft-vegoda-cotton-rfc5735bis-02.txt>	(Special Use IPv4 Addresses) to Best Current Practice
In-Reply-To: <20120712224629.14063.15257.idtracker@ietfa.amsl.com>
References: <20120712224629.14063.15257.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 23:20:42 -0000

> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Special Use IPv4 Addresses'
>    <draft-vegoda-cotton-rfc5735bis-02.txt> as Best Current Practice

read and support

randy

From weiler@watson.org  Sat Jul 14 04:17:39 2012
Return-Path: <weiler@watson.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 C68C421F8736; Sat, 14 Jul 2012 04:17: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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNWiQIFOoMio; Sat, 14 Jul 2012 04:17:39 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0D42D21F8735; Sat, 14 Jul 2012 04:17:38 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.5/8.14.5) with ESMTP id q6EBIHXH009866; Sat, 14 Jul 2012 07:18:17 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.5/8.14.5/Submit) with ESMTP id q6EBIHPj009863; Sat, 14 Jul 2012 07:18:17 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Sat, 14 Jul 2012 07:18:17 -0400 (EDT)
From: Samuel Weiler <weiler@watson.org>
To: ietf@ietf.org
Subject: Re: [dnsext] Last Call:	<draft-ietf-dnsext-dnssec-registry-update-03.txt> (DNS	Security (DNSSEC) DNSKEY Algorithm IANA Registry	Updates) to	Proposed Standard
In-Reply-To: <20120627135256.11457.74759.idtracker@ietfa.amsl.com>
Message-ID: <alpine.BSF.2.00.1207140715210.95821@fledge.watson.org>
References: <20120627135256.11457.74759.idtracker@ietfa.amsl.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Sat, 14 Jul 2012 07:18:17 -0400 (EDT)
Cc: dnsext@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jul 2012 11:17:39 -0000

General comment: no objection.

The table in section 2.2 is odd: in addition to the three entries 
being updated, it lists some BUT NOT ALL of the other assignments 
already made.  I suspect that's a historical artifact.  My suggestion: 
since the intro text in that section says "The list of .. registry 
entry changes is below", remove all entries that aren't changing. 
That will make the reader's job easier.

-- Sam Weiler


From huitema@microsoft.com  Sat Jul 14 12:17:27 2012
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0752B21F864E; Sat, 14 Jul 2012 12:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.521
X-Spam-Level: 
X-Spam-Status: No, score=-3.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sSccLwHIBhqb; Sat, 14 Jul 2012 12:17:26 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id 26D0E21F863C; Sat, 14 Jul 2012 12:17:26 -0700 (PDT)
Received: from mail62-ch1-R.bigfish.com (10.43.68.231) by CH1EHSOBE012.bigfish.com (10.43.70.62) with Microsoft SMTP Server id 14.1.225.23; Sat, 14 Jul 2012 19:18:05 +0000
Received: from mail62-ch1 (localhost [127.0.0.1])	by mail62-ch1-R.bigfish.com (Postfix) with ESMTP id 3C81A320400; Sat, 14 Jul 2012 19:18:05 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:131.107.125.8; KIP:(null); UIP:(null); IPV:NLI; H:TK5EX14HUBC106.redmond.corp.microsoft.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: VS-26(zz9371I542Mzz1202hzz1033IL8275dhz2fh2a8h668h839h944hd25hf0ah107ah)
Received-SPF: pass (mail62-ch1: domain of microsoft.com designates 131.107.125.8 as permitted sender) client-ip=131.107.125.8; envelope-from=huitema@microsoft.com; helo=TK5EX14HUBC106.redmond.corp.microsoft.com ; icrosoft.com ; 
Received: from mail62-ch1 (localhost.localdomain [127.0.0.1]) by mail62-ch1 (MessageSwitch) id 134229348424128_17155; Sat, 14 Jul 2012 19:18:04 +0000 (UTC)
Received: from CH1EHSMHS023.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.233])	by mail62-ch1.bigfish.com (Postfix) with ESMTP id 03F414A0047;	Sat, 14 Jul 2012 19:18:04 +0000 (UTC)
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.8) by CH1EHSMHS023.bigfish.com (10.43.70.23) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 14 Jul 2012 19:18:04 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.83]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.02.0309.003; Sat, 14 Jul 2012 19:18:02 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Randy Bush <randy@psg.com>, IETF Disgust <ietf@ietf.org>, The IESG <iesg-secretary@ietf.org>
Subject: RE: Last Call: <draft-vegoda-cotton-rfc5735bis-02.txt>	(Special Use IPv4 Addresses) to Best Current Practice
Thread-Topic: Last Call: <draft-vegoda-cotton-rfc5735bis-02.txt>	(Special Use	IPv4 Addresses) to Best Current Practice
Thread-Index: AQHNYU5CCMd3KY4dTEeMQABkPC5umpcpKB9Q
Date: Sat, 14 Jul 2012 19:18:02 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0BCF7C76@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <20120712224629.14063.15257.idtracker@ietfa.amsl.com> <m24npbckns.wl%randy@psg.com>
In-Reply-To: <m24npbckns.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jul 2012 19:17:27 -0000

Very useful document, certainly worth publishing. It is one of those docume=
nts that needs frequent updates.

RFC 6052, IPv6 Addressing of IPv4/IPv6 Translators, makes reference to a pr=
edecessor of this document, stating in section 3.1 that "The Well-Known Pre=
fix MUST NOT be used to represent non-global IPv4 addresses, such as those =
defined in [RFC1918] or listed in Section 3 of [RFC5735]." I assume that im=
plementers will automatically upgrade their code to reference the new versi=
on.

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ran=
dy Bush
Sent: Friday, July 13, 2012 4:21 PM
To: IETF Disgust; The IESG
Subject: Re: Last Call: <draft-vegoda-cotton-rfc5735bis-02.txt> (Special Us=
e IPv4 Addresses) to Best Current Practice

> The IESG has received a request from an individual submitter to=20
> consider the following document:
> - 'Special Use IPv4 Addresses'
>    <draft-vegoda-cotton-rfc5735bis-02.txt> as Best Current Practice

read and support

randy



From ron.even.tlv@gmail.com  Sun Jul 15 06:00:30 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 D277821F85A3; Sun, 15 Jul 2012 06:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=0.599,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bOOv+3nAAsqI; Sun, 15 Jul 2012 06:00:29 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id B537E21F85A8; Sun, 15 Jul 2012 06:00:28 -0700 (PDT)
Received: by wibhm11 with SMTP id hm11so1585028wib.13 for <multiple recipients>; Sun, 15 Jul 2012 06:01:09 -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=H2EoBUO8kLeX/MLpLbUDMbnFiv/eCy5m4iq+iNs0cjM=; b=j8LvMHKMESS53+j7IjBobufEP/686YWlVpcqTbbfBZr1x9N4E8xengmOvZ1J1NbgsB vNcEdHeSHVS3+6jZT5xa8S9J1GhHzYF88tui2IlzW30S9wt+PniKZV5WQ9DEDiclZq1j 5AzV4wpzl9KJA584B8MzcNx90PxMZ/TJDo7Fi7OnAu84b4kggNWKIC90zcIgA+8H0/HN FeaYHGXWIqjoVuFBKpQHFXuz5+TvtDi2fGie5t+GI5ioQvg9ezBGSmGkSmYc0PfYuWix RM8iTYzlEI8gvFWQZ450kQSTf7zUCtdZvu9iDQ1PTvlPZxDENrHkg7gJ7jPxBbeFDRMp 7XjQ==
Received: by 10.180.109.166 with SMTP id ht6mr10897352wib.11.1342357269842; Sun, 15 Jul 2012 06:01:09 -0700 (PDT)
Received: from RoniE (bzq-79-176-214-12.red.bezeqint.net. [79.176.214.12]) by mx.google.com with ESMTPS id y5sm15605150wiw.9.2012.07.15.06.01.07 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 15 Jul 2012 06:01:09 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-ipfix-ie-doctors.all@tools.ietf.org>
Subject: GenART LC review of draft-ietf-ipfix-ie-doctors-03
Date: Sun, 15 Jul 2012 16:00:26 +0200
Message-ID: <009701cd6292$311290e0$9337b2a0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0098_01CD62A2.F49C9960"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1iki+TBxbsG2rNRoSY8XYYwfuipQ==
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: Sun, 15 Jul 2012 13:00:31 -0000

This is a multipart message in MIME format.

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

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-ietf-ipfix-ie-doctors-03.

Reviewer: Roni Even

Review Date:2012-7-15

IETF LC End Date: 2012-7-17

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

1.       The registration procedure should mention NetFlow V9 expert review
for 0-128. I think that in the IANA section it will be good to suggest
update also for the Registration procedure and Reference of the IPFIX
Information Elements registry.

2.       Section 5.1 should reference RFC5226 and say if it clarifies
RFC5226 or adds some procedure.

3.       In section 5.2 is there a need for a specification to explain the
change. The text is not clear about it.

4.       Section 5.3 say "Names of deprecated or obsolete Information
Elements MUST NOT be reused." What about the elementID can it be re-used?

 

 

 

 

Nits/editorial comments:

 

1.       Section 4.2 third paragraph "applications can to use reduced-size"
should be "applications can use reduced-size"

2.       Section 4.8 first paragraph "enumerates those which Information
Elements" should be "enumerates those Information Elements"

3.       In section 10.1 "these are described in and Section 10.3" I did not
understand the "in and", I assume something is missing here.

 


------=_NextPart_000_0098_01CD62A2.F49C9960
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:1682120490;
	mso-list-type:hybrid;
	mso-list-template-ids:837580664 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1939020722;
	mso-list-type:hybrid;
	mso-list-template-ids:-792964054 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>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: =
draft-ietf-ipfix-ie-doctors-03.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;7&#8211;15<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;7&#8211;17<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 almost ready for publication as an Informational =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>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 =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The =
registration procedure should mention NetFlow V9 expert review for =
0-128. I think that in the IANA section it will be good to suggest =
update also for the Registration procedure and Reference of the IPFIX =
Information Elements registry.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section =
5.1 should reference RFC5226 and say if it clarifies RFC5226 or adds =
some procedure.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
5.2 is there a need for a specification to explain the change. The text =
is not clear about it.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section =
5.3 say &#8220;Names of deprecated or obsolete Information Elements MUST =
NOT be reused.&#8221; What about the elementID can it be =
re-used?<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in'><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"'><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"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section =
4.2 third paragraph &#8220;applications can to use reduced-size&#8221; =
should be &#8220;applications can use =
reduced-size&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section =
4.8 first paragraph &#8220;enumerates those which Information =
Elements&#8221; should be &#8220;enumerates those Information =
Elements&#8221;<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
10.1 &#8220;these are described in and Section 10.3&#8221; I did not =
understand the &#8220;in and&#8221;, I assume something is missing =
here.<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0098_01CD62A2.F49C9960--


From ron.even.tlv@gmail.com  Sun Jul 15 06:23:25 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 4A0F821F8517; Sun, 15 Jul 2012 06:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lR8dQ8BxvoPu; Sun, 15 Jul 2012 06:23:24 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 00D3321F8516; Sun, 15 Jul 2012 06:23:23 -0700 (PDT)
Received: by wibhm11 with SMTP id hm11so1593665wib.13 for <multiple recipients>; Sun, 15 Jul 2012 06:24:05 -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=btquNXpAdtEaJ6yvIbiPJsx0stGAnyNt3bqySKod9P4=; b=j3PUWq+/+M7cAskT+hoD0Obbkq9sCwIyOMCyi0wfYOTqqHOPi3me2TTUESxsw526jf 7YINyqTbdLWWfLj+9liuQj2DvFLZfYLk3gO6QNnfMRU7aN70JtePQP6FtO0X2nyFwm3J Icm9YzTAgVfyQn9WRXqCC5QO+coziyO4RaY5NZouIOLHaaeRlMEpKl32dAhjP03ev005 lMRdVR6cQn8NWGzKGtei5ON8GoJTRUHUJICjbKxsAr8SpmDYlHNsjPcqLg2pFaPTGn74 Wk2eZ0JRAzqUNeglzZdVmdVwoRvg+JoxQGs6GQJ1qb6Ka2IF7hAWmhvrEvSN3EECGMPr Ej7g==
Received: by 10.216.62.204 with SMTP id y54mr4456185wec.31.1342358645068; Sun, 15 Jul 2012 06:24:05 -0700 (PDT)
Received: from RoniE (bzq-79-176-214-12.red.bezeqint.net. [79.176.214.12]) by mx.google.com with ESMTPS id fb20sm23217407wid.1.2012.07.15.06.24.03 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 15 Jul 2012 06:24:04 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-claise-export-application-info-in-ipfix.all@tools.ietf.org>
Subject: genART  review of draft-claise-export-application-info-in-ipfix-09
Date: Sun, 15 Jul 2012 16:23:22 +0200
Message-ID: <009c01cd6295$64e8f410$2ebadc30$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_009D_01CD62A6.28726050"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac1ilWNsRHSs0XzzRU+w+ZsTBH54iQ==
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: Sun, 15 Jul 2012 13:23:25 -0000

This is a multipart message in MIME format.

------=_NextPart_000_009D_01CD62A6.28726050
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-claise-export-application-info-in-ipfix-09

Reviewer: Roni Even

Review Date:2012-7-15

IETF LC End Date: 2012-7-19

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

 


------=_NextPart_000_009D_01CD62A6.28726050
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;}
--></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>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><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 lang=3DFR =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-clais=
e-export-application-info-in-ipfix-09</span><span lang=3DFR =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;7&#8211;15<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-7-19<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational </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"'>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=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_009D_01CD62A6.28726050--


From housley@vigilsec.com  Sun Jul 15 08:38:34 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 07CDA21F84B9; Sun, 15 Jul 2012 08:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.471
X-Spam-Level: 
X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pC2ZuQCJ8igI; Sun, 15 Jul 2012 08:38:33 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5681D21F849D; Sun, 15 Jul 2012 08:38:33 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id E96C2F2403D; Sun, 15 Jul 2012 11:39: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 w1kWhdTXW3Jv; Sun, 15 Jul 2012 11:39:13 -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 D6B35F2403A; Sun, 15 Jul 2012 11:39:18 -0400 (EDT)
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <003c01cd6225$6f4cab60$4de60220$@akayla.com>
Date: Sun, 15 Jul 2012 11:39:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <72D7767E-8AE5-4A91-BE2C-4A949997C5CA@vigilsec.com>
References: <003c01cd6225$6f4cab60$4de60220$@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dnsop-dnssec-dps-framework.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: Sun, 15 Jul 2012 15:38:34 -0000

Peter:

Thanks for the review.  I've not read this document yet, but you review =
raises a question in my mind.

If a DNSSEC policy or practice statement is revised or amended, what =
actions are needed make other aware of the change?

Russ


On Jul 14, 2012, at 9:01 PM, Peter Yee 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>.
>=20
> This draft is ready for publication as an Informational RFC.
>=20
> Document: draft-ietf-dnsop-dnssec-dps-framework-08
> Reviewer: Peter Yee
> Review Date: 14-July-2012
> IETF LC End Date: 17-July-2012
> IESG Telechat date: Pending
>=20
> Summary: This draft provides a framework for the creation of DNSSEC =
Policies
> and Practice Statements.=20
>=20
> Major Issues: None
>=20
> Minor Issues:=20
>=20
> Section 4.4.5 discusses how to handle key compromise.  It might be =
useful to
> discuss here or somewhere else in the document how the compromise is
> prevented from recurring if there were no attenuating measures in =
place
> beforehand.  That might well lead to a revision of the DP or DPS.  The =
draft
> doesn't really discuss under what circumstances a document should be
> iterated or amended.  Of course, that might be considered a meta issue
> and outside of the scope of the DP or DPS proper.
>=20
> Nits/editorial comments:=20
>=20
> In Section 4.6, "behaviour" is spelt in the British manner.  While
> most assuredly not incorrect, you may wish to spell it in the
> American manner.
>=20
> Serial commas are used inconsistently.  Nothing as egregious as the
> following
> example, however. ;-)
> =
http://grammarnowtips.wordpress.com/2011/01/08/a-case-for-the-serial-comma=
/
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From david.black@emc.com  Fri Jul 13 15:24:34 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 D588211E80F2; Fri, 13 Jul 2012 15:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.482
X-Spam-Level: 
X-Spam-Status: No, score=-102.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gecG0an+kQNf; Fri, 13 Jul 2012 15:24:33 -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 B6DFE11E80EC; Fri, 13 Jul 2012 15:24:33 -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 q6DMP7gM018177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 13 Jul 2012 18:25:07 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 13 Jul 2012 18:24:52 -0400
Received: from mxhub31.corp.emc.com (mxhub31.corp.emc.com [128.222.70.171]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q6DMOoCO013417; Fri, 13 Jul 2012 18:24:51 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub31.corp.emc.com ([128.222.70.171]) with mapi; Fri, 13 Jul 2012 18:24:50 -0400
From: <david.black@emc.com>
To: <david.black@emc.com>, <alan.b.johnston@gmail.com>, <mohsen.soroush@sylantro.com>, <vvenkatar@gmail.com>, <gen-art@ietf.org>
Date: Fri, 13 Jul 2012 18:24:49 -0400
Subject: Gen-ART review of draft-ietf-bliss-shared-appearances-12
Thread-Topic: Gen-ART review of draft-ietf-bliss-shared-appearances-12
Thread-Index: Ac1Vb8Dn5IHpqMlJQDmiZm9plrtFJQL1mcsg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208DD8672@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE71208D3A7FD@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 16 Jul 2012 07:25:44 -0700
Cc: bliss@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 22:24:35 -0000

The -12 version of this draft resolves all of the comments in the
Gen-ART review of the -11 version.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Thursday, June 28, 2012 4:51 PM
> To: alan.b.johnston@gmail.com; mohsen.soroush@sylantro.com;
> vvenkatar@gmail.com; gen-art@ietf.org
> Cc: Black, David; Shida Schubert; bliss@ietf.org; IETF Discussion; Robert
> Sparks
> Subject: Gen-ART review of draft-ietf-bliss-shared-appearances-11
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-bliss-shared-appearances-11
> Reviewer: David L. Black
> Review Date: June 28, 2012
> IETF LC End Date: June 28, 2012
> IESG Telechat date: (if known)
>=20
> Summary:
>=20
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This draft describes support for shared appearances in support of multi-l=
ine
> and shared-line telephone often found in businesses.  All of the open iss=
ues
> are minor.  The draft is well-written and reasonably clear for the most p=
art,
> although significant SIP expertise is required to completely understand i=
t.
>=20
> Major issues:  None.
>=20
> Minor issues:
>=20
> 4.1 - REQ-16:
>=20
>    in this case, seizing the line is the same thing as dialing.
>=20
> That seems wrong - I would have thought it was a "prerequisite" as
> opposed to "the same thing" because seizing the line is immediately
> followed by a dialing request.
>=20
> 5.3.
>=20
>    A user may select an appearance number but then abandon placing a
>    call (go back on hook).  In this case, the UA MUST free up the
>    appearance number by removing the event state with a PUBLISH as
>    described in [RFC3903].
>=20
> What happens when that can't be done due to UA or network failure?
>=20
> 5.4.
>=20
>    A 400 response is returned if the chosen appearance number is invalid,
>=20
> Is that always a 400 (Bad Request) or is any 4xx response allowed?  If
> it's always 400, add the words "Bad Request" after "400".
>=20
>    If the Appearance Agent policy does not allow this, a 400 response
>    is returned.
>=20
> Same question.  In addition, is 403 Forbidden allowed here?
>=20
>    If an INVITE is sent by a member of the group to the shared AOR (i.e.
>    they call their own AOR), the Appearance Agent MUST assign two
>    appearance numbers.  The first appearance number will be the one
>    selected or assigned to the outgoing INVITE.  The second appearance
>    number will be another one assigned by the Appearance Agent for the
>    INVITE as it is forked back to the members of the group.
>=20
> How does that interact with the single appearance UAs in 8.1.1 that won't
> understand the second appearance number?  A warning that such a UA can't
> pick up its call to its own AOR would suffice, either here or in 8.1.1.
>=20
> 9.1
>=20
>    A UA that has no knowledge of appearances must will only have
>    appearance numbers for outgoing calls if assigned by the Appearance
>    Agent.  If the non-shared appearance UA does not support Join or
>    Replaces, all dialogs could be marked "exclusive" to indicate that
>    these options are not available.
>=20
> Should that "could be marked" be changed to "SHOULD be marked" ?
> Also, analogous questions for "could" in 9.2 and "can" in 9.3.
>=20
> All three of these affect interoperability.
>=20
> 12. Security Considerations
>=20
> In general, this section is weak on rationale - the second, third and
> fourth paragraphs should all explain more about the purpose of and/or
> rationale for their security requirements (e.g., what does the security
> mechanism protect against and when/why might that protection be desired
> and/or required?).
>=20
>    NOTIFY or PUBLISH message bodies that provide the dialog state
>    information and the dialog identifiers MAY be encrypted end-to-end
>    using the standard mechanisms.
>=20
> What are "the standard mechanisms"?  List them, and provide references,
> please.
>=20
> Please ensure that the section 6 XML and Section 7 ABNF are
> syntax-checked with actual tools.
>=20
> Nits/editorial comments:
>=20
> p.10:
>=20
>    The next section discusses the operations used to implement parts of
>    the shared appearance feature.
>=20
> "The following list describes the operations ..." would be better.
>=20
> 5.3.1.
>=20
>    A UA wanting to place a call but not have an appearance number
>    assigned publishes before sending the INVITE without an 'appearance'
>    element but with the 'shared' event package parameter present.
>=20
> I think I understand what was intended here, but this would be clearer
> if "publishes" was replaced with language about sending a PUBLISH.
> It's also not completely clear whether "without" applies to the
> INVITE or the PUBLISH, so this sentence probably needs to be reworded.
>=20
> 5.4. - Expand B2BUA acronym on first use.
>=20
> idnits 2.12.13 ran clean.
>=20
> 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-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From peter@akayla.com  Sat Jul 14 18:01:09 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 A388521F85EF for <ietf@ietfa.amsl.com>; Sat, 14 Jul 2012 18:01: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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAJW4yK4P7de for <ietf@ietfa.amsl.com>; Sat, 14 Jul 2012 18:01:08 -0700 (PDT)
Received: from p3plsmtpa08-01.prod.phx3.secureserver.net (p3plsmtpa08-01.prod.phx3.secureserver.net [173.201.193.102]) by ietfa.amsl.com (Postfix) with SMTP id CBA8721F85DD for <ietf@ietf.org>; Sat, 14 Jul 2012 18:01:08 -0700 (PDT)
Received: (qmail 23737 invoked from network); 15 Jul 2012 01:01:48 -0000
Received: from unknown (173.8.184.78) by p3plsmtpa08-01.prod.phx3.secureserver.net (173.201.193.102) with ESMTP; 15 Jul 2012 01:01:38 -0000
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-dnsop-dnssec-dps-framework.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Date: Sat, 14 Jul 2012 18:01:57 -0700
Message-ID: <003c01cd6225$6f4cab60$4de60220$@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: Ac1iHPxAQ3X+yUjHRlS1K0UX/TXCcw==
Content-Language: en-us
X-Mailman-Approved-At: Mon, 16 Jul 2012 07:25:43 -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: Sun, 15 Jul 2012 01:01:09 -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>.

This draft is ready for publication as an Informational RFC.

Document: draft-ietf-dnsop-dnssec-dps-framework-08
Reviewer: Peter Yee
Review Date: 14-July-2012
IETF LC End Date: 17-July-2012
IESG Telechat date: Pending

Summary: This draft provides a framework for the creation of DNSSEC Policies
and Practice Statements. 

Major Issues: None

Minor Issues: 

Section 4.4.5 discusses how to handle key compromise.  It might be useful to
discuss here or somewhere else in the document how the compromise is
prevented from recurring if there were no attenuating measures in place
beforehand.  That might well lead to a revision of the DP or DPS.  The draft
doesn't really discuss under what circumstances a document should be
iterated or amended.  Of course, that might be considered a meta issue
and outside of the scope of the DP or DPS proper.

Nits/editorial comments: 

In Section 4.6, "behaviour" is spelt in the British manner.  While
most assuredly not incorrect, you may wish to spell it in the
American manner.

Serial commas are used inconsistently.  Nothing as egregious as the
following
example, however. ;-)
http://grammarnowtips.wordpress.com/2011/01/08/a-case-for-the-serial-comma/



From scottr.nist@gmail.com  Mon Jul 16 07:25:27 2012
Return-Path: <scottr.nist@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C03D321F879D; Mon, 16 Jul 2012 07:25:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qf24VVimkVsP; Mon, 16 Jul 2012 07:25:26 -0700 (PDT)
Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id EB7D421F8790; Mon, 16 Jul 2012 07:25:25 -0700 (PDT)
Received: from WSGHUB1.xchange.nist.gov (129.6.42.34) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 16 Jul 2012 10:26:04 -0400
Received: from smtp.nist.gov (129.6.16.226) by smtp-g.nist.gov (129.6.42.33) with Microsoft SMTP Server id 14.1.355.2; Mon, 16 Jul 2012 10:26:06 -0400
Received: from 6-140.antd.nist.gov (6-140.antd.nist.gov [129.6.140.6])	by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id q6GEQ5A3010058; Mon, 16 Jul 2012 10:26:06 -0400
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-dnssec-registry-update-03.txt> (DNS	Security (DNSSEC) DNSKEY Algorithm IANA Registry	Updates) to	Proposed Standard
MIME-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_815F6DFD-0B17-462C-9D85-50F01FE1BAD1"
From: Scott Rose <scottr.nist@gmail.com>
In-Reply-To: <alpine.BSF.2.00.1207140715210.95821@fledge.watson.org>
Date: Mon, 16 Jul 2012 10:26:05 -0400
Message-ID: <D7CD7207-FCDD-46FF-85B3-501DD0558B13@gmail.com>
References: <20120627135256.11457.74759.idtracker@ietfa.amsl.com> <alpine.BSF.2.00.1207140715210.95821@fledge.watson.org>
To: <dnsext@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Mon, 16 Jul 2012 07:25:54 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jul 2012 14:25:27 -0000

--Apple-Mail=_815F6DFD-0B17-462C-9D85-50F01FE1BAD1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"

Thanks for the review. =20

The table in section 2.2 in the -03 draft only has the entries that need =
to be updated.  Besides the 3 entries that are now Reserved, but the =
references for some other entries have been fixed.  I removed the =
correct, unchanged entries for readability (the mnemonics for some of =
the entires skewed the table and made it difficult to read).

Scott=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Scott Rose
NIST
scott.rose@nist.gov
+1 301-975-8439
Google Voice: +1 571-249-3671
http://www.dnsops.gov/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On Jul 14, 2012, at 7:18 AM, Samuel Weiler wrote:

> General comment: no objection.
>=20
> The table in section 2.2 is odd: in addition to the three entries =
being updated, it lists some BUT NOT ALL of the other assignments =
already made.  I suspect that's a historical artifact.  My suggestion: =
since the intro text in that section says "The list of .. registry entry =
changes is below", remove all entries that aren't changing. That will =
make the reader's job easier.
>=20
> -- Sam Weiler
>=20
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext


--Apple-Mail=_815F6DFD-0B17-462C-9D85-50F01FE1BAD1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="us-ascii"

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Thanks for the review. &nbsp;<div><br></div><div>The table in section =
2.2 in the -03 draft only has the entries that need to be updated. =
&nbsp;Besides the 3 entries that are now Reserved, but the references =
for some other entries have been fixed. &nbsp;I removed the correct, =
unchanged entries for readability (the mnemonics for some of the entires =
skewed the table and made it difficult to =
read).</div><div><br></div><div>Scott&nbsp;<br><div><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Scott Rose<br>NIST<br><a =
href=3D"mailto:scott.rose@nist.gov">scott.rose@nist.gov</a><br>+1 =
301-975-8439<br>Google Voice: +1 =
571-249-3671<br>http://www.dnsops.gov/<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</=
div></span></span>
</div>
<br><div><div>On Jul 14, 2012, at 7:18 AM, Samuel Weiler wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>General=
 comment: no objection.<br><br>The table in section 2.2 is odd: in =
addition to the three entries being updated, it lists some BUT NOT ALL =
of the other assignments already made. &nbsp;I suspect that's a =
historical artifact. &nbsp;My suggestion: since the intro text in that =
section says "The list of .. registry entry changes is below", remove =
all entries that aren't changing. That will make the reader's job =
easier.<br><br>-- Sam =
Weiler<br><br>_______________________________________________<br>dnsext =
mailing list<br><a =
href=3D"mailto:dnsext@ietf.org">dnsext@ietf.org</a><br>https://www.ietf.or=
g/mailman/listinfo/dnsext<br></div></blockquote></div><br></div></div></bo=
dy></html>=

--Apple-Mail=_815F6DFD-0B17-462C-9D85-50F01FE1BAD1--

From jabley@hopcount.ca  Mon Jul 16 15:33:17 2012
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB96711E8321; Mon, 16 Jul 2012 15:33: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t0xZ5F414CTP; Mon, 16 Jul 2012 15:33:17 -0700 (PDT)
Received: from mail.hopcount.ca (mail.hopcount.ca [216.235.14.37]) by ietfa.amsl.com (Postfix) with ESMTP id 4219B11E813D; Mon, 16 Jul 2012 15:33:17 -0700 (PDT)
Received: from [199.212.90.56] by mail.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1SqtrW-000A1a-8G; Mon, 16 Jul 2012 22:33:55 +0000
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <72D7767E-8AE5-4A91-BE2C-4A949997C5CA@vigilsec.com>
Date: Mon, 16 Jul 2012 18:33:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <29BF6AF1-3924-42F0-B8BD-1B1250CAECD6@hopcount.ca>
References: <003c01cd6225$6f4cab60$4de60220$@akayla.com> <72D7767E-8AE5-4A91-BE2C-4A949997C5CA@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1278)
Cc: Peter Yee <peter@akayla.com>, gen-art@ietf.org, ietf@ietf.org, draft-ietf-dnsop-dnssec-dps-framework.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: Mon, 16 Jul 2012 22:33:17 -0000

Hi Russ,

On 2012-07-15, at 11:39, Russ Housley wrote:

> Peter:
>=20
> Thanks for the review.  I've not read this document yet, but you =
review raises a question in my mind.
>=20
> If a DNSSEC policy or practice statement is revised or amended, what =
actions are needed make other aware of the change?

Each DPS contains these kinds of details. Guidance for how to write the =
corresponding DPS sections is included in this draft:

4.2.  Publication and repositories

   The component describes the requirements for an entity to publish
   information regarding its practices, public keys, the current status
   of such keys together with details relating to the repositories in
   which the information is held.  This may include the responsibilities
   of publishing the DPS and of identifying documents that are not made
   publicly available owing to their sensitive nature, e.g. security
   controls, clearance procedures, or business information.

4.2.1.  Repositories

   This subcomponent describes the repository mechanisms used for making
   information available to the stakeholders, and may include:

   o  The locations of the repositories and the means by which they may
      be accessed;

   o  An identification of the entity or entities that operate
      repositories, such as a zone operator or a TLD Manager;

   o  Access control on published information objects.

   o  Any notification services which may be subscribed to by the
      stakeholders;


Joe


From alexey.melnikov@isode.com  Tue Jul 17 03:07:48 2012
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4CD221F86CF for <ietf@ietfa.amsl.com>; Tue, 17 Jul 2012 03:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.86
X-Spam-Level: 
X-Spam-Status: No, score=-101.86 tagged_above=-999 required=5 tests=[AWL=-1.561, BAYES_00=-2.599, MANGLED_GIRL=2.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fW7pEI6RgHSI for <ietf@ietfa.amsl.com>; Tue, 17 Jul 2012 03:07:48 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id CF9C621F86CE for <ietf@ietf.org>; Tue, 17 Jul 2012 03:07:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1342519714; d=isode.com; s=selector; i=@isode.com; bh=EksTNsMrBI9JsDmRo80XUJMmtiJKntybaesAIH8yfyI=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=b9KT41O5Eq6gemQPHnlXHoku7cB8Rp5Nvr8X+r6QWNJIFq7THwZylxG5bkCcH7BAn5F88f wT048pWJS7H1FKmKtxHGUFxSZd8Bh1RA2vmFttMBihXcvkfoZivwlJjukNyOvS0YIu8jmw HZlfWXVL9B9uL0pQT8ty48OUHXaEtAg=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <UAU5oQAdigx3@statler.isode.com>; Tue, 17 Jul 2012 11:08:34 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <500539A1.9060200@isode.com>
Date: Tue, 17 Jul 2012 11:08:33 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: Simon Perreault <simon.perreault@viagenie.ca>
Subject: Re: Gen-ART review of draft-ietf-behave-lsn-requirements-07
References: <4FF2E47C.80104@isode.com> <4FFC6B72.2010401@viagenie.ca>
In-Reply-To: <4FFC6B72.2010401@viagenie.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 10:07:49 -0000

Hi Simon,

On 10/07/2012 18:50, Simon Perreault wrote:
> On 07/03/2012 08:24 AM, Alexey Melnikov wrote:
>> I found the justification for REQ-6 hard to read/understand. Why does
>> access to
>> servers being on the internal network need to go through CGN at all?
>
> Here's the thing: the server is not on the internal network. It's on 
> the external network, but it is still managed by the ISP. The ISP's 
> network includes the internal network and some part of the external 
> network. Furthermore, in many cases an ISP may run multiple CGNs, so 
> the ISP's network is actually multiple internal networks and some part 
> of the external network. The servers in the external network are 
> operated by the ISP and "know" the internal networks (have routes to 
> them), and can reach them directly without translation. And since 
> connections from subscribers to those servers may account for a lot of 
> traffic, it is important to not spend NAT resources on them.
I like this longer explanation. I agree that once I understand what you 
are trying to say the shorter explanation in the document makes sense. 
But it is a bit cryptic. (I don't have specific suggestions, so if you 
can't improve existing text, that is Ok with me.)
> Now, I'm not sure how to alter the existing text to make it easier to 
> understand. It seems to me that all the information is there, just not 
> with the same order/emphasis as what I wrote above. If the above was 
> useful for you to understand, could you please point out in the text 
> below what change would have helped you understand?
>
>    REQ-6:  It MUST be possible to administratively turn off translation
>            for specific destination addresses and/or ports.
>
>    Justification:  It is common for a CGN administrator to provide
>       access for subscribers to servers installed in the ISP's network,
>       in the external realm.  When such a server is able to reach the
>       internal realm via normal routing (which is entirely controlled by
>       the ISP), translation is unneeded.  In that case, the CGN may
>       forward packets without modification, thus acting like a plain
>       router.  This may represent an important efficiency gain.
>
>       Figure 2 illustrates this use-case.
>
>
>                  X1:x1            X1':x1'            X2:x2
>                  +---+from X1:x1  +---+from X1:x1    +---+
>                  | C |  to X2:x2  |   |  to X2:x2    | S |
>                  | l |>>>>>>>>>>>>| C |>>>>>>>>>>>>>>| e |
>                  | i |            | G |              | r |
>                  | e |<<<<<<<<<<<<| N |<<<<<<<<<<<<<<| v |
>                  | n |from X2:x2  |   |from X2:x2    | e |
>                  | t |  to X1:x1  |   |  to X1:x1    | r |
>                  +---+            +---+              +---+
>
>                         Figure 2: CGN pass-through
>
> Thanks,
> Simon



From presnick@qualcomm.com  Tue Jul 17 11:56:36 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 9871B21F86A5; Tue, 17 Jul 2012 11:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.597
X-Spam-Level: 
X-Spam-Status: No, score=-106.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HNzoojX+JSig; Tue, 17 Jul 2012 11:56:36 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id E94A721F86A3; Tue, 17 Jul 2012 11:56:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1342551445; x=1374087445; 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=CzBtcgrpO154KuRXElj/az6LterkvxgvWMfez6/zo4A=; b=VWfRkUjipRmDBhs6usOD8P29TuVaLnr3C5MKKuBkrNWvVojORftsGtZF Y+ktjpEQaSCj/bf+eUpwQow0eLzZ4IeqIgERdWc7njUgxFm6AwqP0miwn WUABCkdr6oOySIUoUW2N6bIDq1g0FUZauhDjqUWxgPVIoPLEkFOlowJNT 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,6775"; a="209235368"
Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine02.qualcomm.com with ESMTP; 17 Jul 2012 11:57:23 -0700
X-IronPort-AV: E=Sophos;i="4.77,604,1336374000"; d="scan'208";a="121763451"
Received: from nasanexhc10.na.qualcomm.com ([172.30.48.3]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 17 Jul 2012 11:57:22 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc10.na.qualcomm.com (172.30.48.3) with Microsoft SMTP Server (TLS) id 14.2.309.2; Tue, 17 Jul 2012 11:57:21 -0700
Received: from Macintosh-5.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.309.2; Tue, 17 Jul 2012 11:57:21 -0700
Message-ID: <5005B58F.40608@qualcomm.com>
Date: Tue, 17 Jul 2012 13:57:19 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: Gen-ART review of draft-ietf-behave-lsn-requirements-07
References: <4FF2E47C.80104@isode.com> <2D34DBB5-543F-47A3-A649-BDDFF76A6438@netapp.com>
In-Reply-To: <2D34DBB5-543F-47A3-A649-BDDFF76A6438@netapp.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: draft-ietf-behave-lsn-requirements.all@tools.ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 18:56:36 -0000

On 7/3/12 7:51 AM, Eggert, Lars wrote:
> On Jul 3, 2012, at 14:24, Alexey Melnikov wrote:
>    
>> I found it is to be odd to have a requirements document as a BCP, but I am sure
>> you can sort the right status out with IESG.
>>      
> +1
>
> I fail to see why Informational wouldn't be the better status.
>
> Lars

Publicly reposting what I just put in my IESG ballot, just in case you 
all want to disagree with me publicly. :-)

Perhaps I'm just being contrarian today, but I *do* think this document 
should be BCP and not Informational. It is not a requirements document 
in the sense that it is laying out requirements for future protocol 
documents being developed by a WG; it is a consensus document listing 
the requirements for the operation and administration of a type of 
device. If that doesn't fall within the 2nd paragraph of RFC 2026 
section 5, I don't know what does.

pr

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


From john-ietf@jck.com  Tue Jul 17 15:14: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 288CC11E80AD; Tue, 17 Jul 2012 15:14:12 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aaz34PNAa2Kf; Tue, 17 Jul 2012 15:14:11 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9D24411E80A0; Tue, 17 Jul 2012 15:14: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 1SrFxC-000D8g-M5; Tue, 17 Jul 2012 18:09:14 -0400
Date: Tue, 17 Jul 2012 18:14:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qualcomm.com>, "Eggert, Lars" <lars@netapp.com>
Subject: Re: Gen-ART review of draft-ietf-behave-lsn-requirements-07
Message-ID: <CFDBFE9825F3FE036F1B296D@JcK-HP8200.jck.com>
In-Reply-To: <5005B58F.40608@qualcomm.com>
References: <4FF2E47C.80104@isode.com> <2D34DBB5-543F-47A3-A649-BDDFF76A6438@netapp.com> <5005B58F.40608@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: draft-ietf-behave-lsn-requirements.all@tools.ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 22:14:12 -0000

--On Tuesday, July 17, 2012 13:57 -0500 Pete Resnick
<presnick@qualcomm.com> wrote:

> Perhaps I'm just being contrarian today, but I *do* think this
> document should be BCP and not Informational. It is not a
> requirements document in the sense that it is laying out
> requirements for future protocol documents being developed by
> a WG; it is a consensus document listing the requirements for
> the operation and administration of a type of device. If that
> doesn't fall within the 2nd paragraph of RFC 2026 section 5, I
> don't know what does.

Just to be disagreeable...

I think "requirements for the operation and administration of a
type of device" puts it squarely into the "Applicability
Statement" range, in part of permit testing of those
requirements and advancement along the standards track.  Of
course, the precedent is RFCs 1122 and 1123 which requirements
for operation and administration as well as for protocol
conformance and are clearly applicability statements (and more
or less the prototype for that category).

    john




From presnick@qualcomm.com  Tue Jul 17 15:50:37 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 BE3E721F8501; Tue, 17 Jul 2012 15:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.597
X-Spam-Level: 
X-Spam-Status: No, score=-106.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NUZzhoUSG+7l; Tue, 17 Jul 2012 15:50:36 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 7A61C11E80A0; Tue, 17 Jul 2012 15:50:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1342565486; x=1374101486; 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=GyeeS6Eah8SMtqGqx8Y/t5zNNvOo9D0K4w28bwoNc84=; b=t5fEmpcQFBxIzCLmO/HnJ1z2oYcZ5RUWWTBOXu92hGqFuUmiTgN6N/5x x+zNLzVMJaG4xaDcUK7Df46vmpkgylxUdr65ndQAbaIKXv0DYuti25uFi 2lg4Is1z/rt73OhbNQyBQGh7DjP7DjU4e3Oj3+RR/lFm45Mm9Gb08iO3H w=;
X-IronPort-AV: E=McAfee;i="5400,1158,6775"; a="211657665"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 17 Jul 2012 15:51:25 -0700
X-IronPort-AV: E=Sophos;i="4.77,605,1336374000"; d="scan'208";a="286244610"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 17 Jul 2012 15:51:25 -0700
Received: from Macintosh-5.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.309.2; Tue, 17 Jul 2012 15:51:23 -0700
Message-ID: <5005EC6A.8030805@qualcomm.com>
Date: Tue, 17 Jul 2012 17:51:22 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Gen-ART review of draft-ietf-behave-lsn-requirements-07
References: <4FF2E47C.80104@isode.com>	<2D34DBB5-543F-47A3-A649-BDDFF76A6438@netapp.com>	<5005B58F.40608@qualcomm.com> <CFDBFE9825F3FE036F1B296D@JcK-HP8200.jck.com>
In-Reply-To: <CFDBFE9825F3FE036F1B296D@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: draft-ietf-behave-lsn-requirements.all@tools.ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 22:50:37 -0000

On 7/17/12 5:14 PM, John C Klensin wrote:

> --On Tuesday, July 17, 2012 13:57 -0500 Pete Resnick
> <presnick@qualcomm.com>  wrote:
>
>    
>> Perhaps I'm just being contrarian today, but I *do* think this
>> document should be BCP and not Informational. It is not a
>> requirements document in the sense that it is laying out
>> requirements for future protocol documents being developed by
>> a WG; it is a consensus document listing the requirements for
>> the operation and administration of a type of device. If that
>> doesn't fall within the 2nd paragraph of RFC 2026 section 5, I
>> don't know what does.
>>      
> Just to be disagreeable...
>
> I think "requirements for the operation and administration of a
> type of device" puts it squarely into the "Applicability
> Statement" range, in part of permit testing of those
> requirements and advancement along the standards track.  Of
> course, the precedent is RFCs 1122 and 1123 which requirements
> for operation and administration as well as for protocol
> conformance and are clearly applicability statements (and more
> or less the prototype for that category).
>    

Just to be somewhat agreeable... ;-)

Normally, I would be right with you and say, "This should be on the 
standards track." However, this document is about CGNs. It's about 
things that are almost by definition not nice interoperable players on 
the Internet. They are messy local devices for (albeit large) local 
networks. Indeed, there are many folks who think that horrific plagues 
be visited upon those who deploy CGNs and that they should be dismantled 
as soon as humanly possible, if not before. But in any event, this is 
not really a spec "for hardware and software required for computer 
communication across interconnected networks", but rather is a document 
for "networks operated by a great variety of organizations, with diverse 
goals and rules" to provide "operators and administrators of the 
Internet follow some common guidelines for policies and operations". Or 
at least I think a strong case can be made for that. I think that's why 
several other behave documents ended up being BCPs. I could make an 
argument for standards track, but I think BCP is a reasonable 
alternative conclusion to come to as well for this particular document.

pr

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


From housley@vigilsec.com  Tue Jul 17 16:06:00 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 5A76721F85C2; Tue, 17 Jul 2012 16:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.696
X-Spam-Level: 
X-Spam-Status: No, score=-102.696 tagged_above=-999 required=5 tests=[AWL=-0.097, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7mmVLY+fkkT; Tue, 17 Jul 2012 16:05:58 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id CAEE821F85C0; Tue, 17 Jul 2012 16:05:58 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id A41BAF2403F; Tue, 17 Jul 2012 19:07:04 -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 muoVV8rOdrNG; Tue, 17 Jul 2012 19:06:45 -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 BCF87F2403D; Tue, 17 Jul 2012 19:07:02 -0400 (EDT)
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <29BF6AF1-3924-42F0-B8BD-1B1250CAECD6@hopcount.ca>
Date: Tue, 17 Jul 2012 19:06:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <57D81A5A-B80B-4DC1-87FE-450E91A01A20@vigilsec.com>
References: <003c01cd6225$6f4cab60$4de60220$@akayla.com> <72D7767E-8AE5-4A91-BE2C-4A949997C5CA@vigilsec.com> <29BF6AF1-3924-42F0-B8BD-1B1250CAECD6@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1084)
Cc: Peter Yee <peter@akayla.com>, gen-art@ietf.org, ietf@ietf.org, draft-ietf-dnsop-dnssec-dps-framework.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 23:06:00 -0000

Joe:

I think you missed my point.  In a PKI, when the issuer significantly =
changes the policy, subsequent certificates have a different policy =
identifier.  I do not see a similar concept here.

Russ


On Jul 16, 2012, at 6:33 PM, Joe Abley wrote:

> Hi Russ,
>=20
> On 2012-07-15, at 11:39, Russ Housley wrote:
>=20
>> Peter:
>>=20
>> Thanks for the review.  I've not read this document yet, but you =
review raises a question in my mind.
>>=20
>> If a DNSSEC policy or practice statement is revised or amended, what =
actions are needed make other aware of the change?
>=20
> Each DPS contains these kinds of details. Guidance for how to write =
the corresponding DPS sections is included in this draft:
>=20
> 4.2.  Publication and repositories
>=20
>   The component describes the requirements for an entity to publish
>   information regarding its practices, public keys, the current status
>   of such keys together with details relating to the repositories in
>   which the information is held.  This may include the =
responsibilities
>   of publishing the DPS and of identifying documents that are not made
>   publicly available owing to their sensitive nature, e.g. security
>   controls, clearance procedures, or business information.
>=20
> 4.2.1.  Repositories
>=20
>   This subcomponent describes the repository mechanisms used for =
making
>   information available to the stakeholders, and may include:
>=20
>   o  The locations of the repositories and the means by which they may
>      be accessed;
>=20
>   o  An identification of the entity or entities that operate
>      repositories, such as a zone operator or a TLD Manager;
>=20
>   o  Access control on published information objects.
>=20
>   o  Any notification services which may be subscribed to by the
>      stakeholders;
>=20
>=20
> Joe
>=20


From jabley@hopcount.ca  Tue Jul 17 16:31:41 2012
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A90F11E80E7; Tue, 17 Jul 2012 16:31:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.996
X-Spam-Level: 
X-Spam-Status: No, score=-101.996 tagged_above=-999 required=5 tests=[AWL=0.604, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ptMAfmIsgB+8; Tue, 17 Jul 2012 16:31:40 -0700 (PDT)
Received: from mail.hopcount.ca (mail.hopcount.ca [216.235.14.37]) by ietfa.amsl.com (Postfix) with ESMTP id 825F211E80E5; Tue, 17 Jul 2012 16:31:40 -0700 (PDT)
Received: from [2001:4900:1042:100:f4a1:1904:f7f4:e19a] by mail.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1SrHFa-0000qK-Ku; Tue, 17 Jul 2012 23:32:20 +0000
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <57D81A5A-B80B-4DC1-87FE-450E91A01A20@vigilsec.com>
Date: Tue, 17 Jul 2012 19:32:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AAD9253-F597-4B57-9BA8-C067B3E3839D@hopcount.ca>
References: <003c01cd6225$6f4cab60$4de60220$@akayla.com> <72D7767E-8AE5-4A91-BE2C-4A949997C5CA@vigilsec.com> <29BF6AF1-3924-42F0-B8BD-1B1250CAECD6@hopcount.ca> <57D81A5A-B80B-4DC1-87FE-450E91A01A20@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1278)
Cc: Peter Yee <peter@akayla.com>, gen-art@ietf.org, ietf@ietf.org, draft-ietf-dnsop-dnssec-dps-framework.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2012 23:31:41 -0000

Hi Russ,

On 2012-07-17, at 19:06, Russ Housley wrote:

> I think you missed my point.  In a PKI, when the issuer significantly =
changes the policy, subsequent certificates have a different policy =
identifier.  I do not see a similar concept here.

You're right, I did miss your point, quite thoroughly :-)

I am guessing that the answer is that there's no corresponding facility =
in DNSSEC to for a policy identifier to be published with a DNSKEY RR, =
but I say that largely ignorant of X.509 and attendant CA policy and =
hence perhaps am still misunderstanding what you're looking for.=20


Joe


From sm@resistor.net  Tue Jul 17 17:51: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 B828C11E8102 for <ietf@ietfa.amsl.com>; Tue, 17 Jul 2012 17:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBVcNWT42gyn for <ietf@ietfa.amsl.com>; Tue, 17 Jul 2012 17:51:24 -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 2212011E8101 for <ietf@ietf.org>; Tue, 17 Jul 2012 17:51:24 -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 q6I0q7Kq027974; Tue, 17 Jul 2012 17:52:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342572732; bh=Xu+3EHWtJJPHd60nsjmW0cMzEVS25TUNiho+/QxuA28=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=leOjK7qHLSzzDRLHee+a4pzvSgWL1YLzY9bcZzZvlqD+O7m4Lt4QQ+xw/2KH9/MzF muEILF+s9UZSVkDyjKPkym1U3di+pnTy4eijUUZG2JNPcpb9Z6Bx/V8B23OiHywNCt QrQwg9W6zq/MtUo7f5ZQxjTQw8yVwsDvgPk/2/Is=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342572732; i=@resistor.net; bh=Xu+3EHWtJJPHd60nsjmW0cMzEVS25TUNiho+/QxuA28=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xQy9v5VOOmjX/smQDVDAGlV6wdovjLdfpvDaBju3dzkIw7eotSFK70eIW9ilijOG2 IGG+T6IZlXHovbOT9rdvSoNviFVga9vlvLKBJ7KBVY43YLtvP0EjZ1TuCb6RWNpPct LUaM5i2Vs1VVB4h0TaOqNl0EuIUdQ30dIq1wFHxg=
Message-Id: <6.2.5.6.2.20120717172251.09790e50@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 17 Jul 2012 17:50:43 -0700
To: Pete Resnick <presnick@qualcomm.com>
From: SM <sm@resistor.net>
Subject: Re: Gen-ART review of draft-ietf-behave-lsn-requirements-07
In-Reply-To: <5005B58F.40608@qualcomm.com>
References: <4FF2E47C.80104@isode.com> <2D34DBB5-543F-47A3-A649-BDDFF76A6438@netapp.com> <5005B58F.40608@qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-ietf-behave-lsn-requirements.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 00:51:32 -0000

Hi Pete,
At 11:57 17-07-2012, Pete Resnick wrote:
>Perhaps I'm just being contrarian today, but I *do* think this 
>document should be BCP and not Informational. It is not a 
>requirements document in the sense that it is laying out 
>requirements for future protocol documents being developed by a WG; 
>it is a consensus document listing the requirements for the 
>operation and administration of a type of device. If that doesn't 
>fall within the 2nd paragraph of RFC 2026 section 5, I don't know what does.

I don't recall seeing an IPR disclosure on a BCP.  Most new 
Informational RFCs are also consensus documents.  There are a few 
Informational RFCs which lists requirements for operation and 
administration.  I don't think that this document should be BCP as 
the status does not exercise the "must demonstrate at least two 
independent, separate and successful uses of the licensing process".

Regards,
-sm 


From mohta@necom830.hpcl.titech.ac.jp  Tue Jul 17 23:15:57 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A67711E813B for <ietf@ietfa.amsl.com>; Tue, 17 Jul 2012 23:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.007
X-Spam-Level: 
X-Spam-Status: No, score=-0.007 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7s79MLOEqlOa for <ietf@ietfa.amsl.com>; Tue, 17 Jul 2012 23:15:56 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 287A711E812F for <ietf@ietf.org>; Tue, 17 Jul 2012 23:15:55 -0700 (PDT)
Received: (qmail 89470 invoked from network); 18 Jul 2012 06:20:30 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 18 Jul 2012 06:20:30 -0000
Message-ID: <500654AB.7060500@necom830.hpcl.titech.ac.jp>
Date: Wed, 18 Jul 2012 15:16:11 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu>
In-Reply-To: <4FF20DE7.2080208@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 06:15:57 -0000

Joe Touch wrote:

>> Or, are 6 to 4 translators are required to rate limit and
>> drop rate-violating packets to make the "stateless"
>> translators full of states.
>
> I would expect that the translator would be responsible
> for this, though

Do you mean translators must rate limit, or translators
violate RFC2765:

>>            Identification:
>>                    Copied from the low-order 16-bits in the
>>                    Identification field in the Fragment header.

and use some other number as an ID?

> there is the problem that multiple translators interfere
> with each other.

Yes, even rate limiting translators may interfere each other,
which means rate limiting must be done at the IPv6 source
node.

> Regardless, this is outside the scope of the ipv4-id-update doc.

In the ID, there are a lot of references to IPv6.

For example, the following statement of the ID:

   Finally, the IPv6 ID field is
   32 bits, and required unique per source/destination address pair for
   IPv6, whereas for IPv4 it is only 16 bits and required unique per
   source/destination/protocol triple.

must be modified as:

   Finally, the IPv6 ID field is
   32 bits, but lower 16 bits are required unique per
   source/destination address pair for
   IPv6, whereas for IPv4 it is only 16 bits and required unique per
   source/destination/protocol triple.

						Masataka Ohta

From housley@vigilsec.com  Wed Jul 18 08:48:17 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 AF4B721F8567; Wed, 18 Jul 2012 08:48:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.721
X-Spam-Level: 
X-Spam-Status: No, score=-102.721 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xZIFIXao2wOF; Wed, 18 Jul 2012 08:48:17 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7A76121F8557; Wed, 18 Jul 2012 08:48:13 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9E07BF24043; Wed, 18 Jul 2012 11:49:17 -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 zzLMuwVCjBgh; Wed, 18 Jul 2012 11:48:59 -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 C74BCF2403F; Wed, 18 Jul 2012 11:49:16 -0400 (EDT)
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5AAD9253-F597-4B57-9BA8-C067B3E3839D@hopcount.ca>
Date: Wed, 18 Jul 2012 11:49:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E0BFBA85-85C2-46BA-8406-99990C204295@vigilsec.com>
References: <003c01cd6225$6f4cab60$4de60220$@akayla.com> <72D7767E-8AE5-4A91-BE2C-4A949997C5CA@vigilsec.com> <29BF6AF1-3924-42F0-B8BD-1B1250CAECD6@hopcount.ca> <57D81A5A-B80B-4DC1-87FE-450E91A01A20@vigilsec.com> <5AAD9253-F597-4B57-9BA8-C067B3E3839D@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1084)
Cc: Peter Yee <peter@akayla.com>, gen-art@ietf.org, ietf@ietf.org, draft-ietf-dnsop-dnssec-dps-framework.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, 18 Jul 2012 15:48:17 -0000

Joe:

>> I think you missed my point.  In a PKI, when the issuer significantly =
changes the policy, subsequent certificates have a different policy =
identifier.  I do not see a similar concept here.
>=20
> You're right, I did miss your point, quite thoroughly :-)
>=20
> I am guessing that the answer is that there's no corresponding =
facility in DNSSEC to for a policy identifier to be published with a =
DNSKEY RR, but I say that largely ignorant of X.509 and attendant CA =
policy and hence perhaps am still misunderstanding what you're looking =
for.=20

So a DNSSEC signer starts under one set of documents, and then for =
whatever reason, the policy changes and the parties validating the =
signature have no means to determine that the signer is following a new =
policy.  So I am missing the value of the policy to the parties that =
rely on these signatures.

Russ=

From kent@bbn.com  Wed Jul 18 08:54:53 2012
Return-Path: <kent@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 9BEBF21F8737; Wed, 18 Jul 2012 08:54:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.482
X-Spam-Level: 
X-Spam-Status: No, score=-106.482 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id unpnxIXVWj4v; Wed, 18 Jul 2012 08:54:53 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id F082521F8736; Wed, 18 Jul 2012 08:54:52 -0700 (PDT)
Received: from dhcp89-089-116.bbn.com ([128.89.89.116]:49414) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1SrWb2-000DuU-Ld; Wed, 18 Jul 2012 11:55:28 -0400
Message-ID: <5006DC70.7000500@bbn.com>
Date: Wed, 18 Jul 2012 11:55:28 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: jabley@hopcount.ca, russ housley <housley@vigilsec.com>,  Peter Yee <peter@akayla.com>, ietf@ietf.org, gen-art@ietf.org,  draft-ietf-dnsop-dnssec-dps-framework.all@tools.ietf.org
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
References: <003c01cd6225$6f4cab60$4de60220$@akayla.com> <72D7767E-8AE5-4A91-BE2C-4A949997C5CA@vigilsec.com> <29BF6AF1-3924-42F0-B8BD-1B1250CAECD6@hopcount.ca> <57D81A5A-B80B-4DC1-87FE-450E91A01A20@vigilsec.com> <5AAD9253-F597-4B57-9BA8-C067B3E3839D@hopcount.ca> <E0BFBA85-85C2-46BA-8406-99990C204295@vigilsec.com>
In-Reply-To: <E0BFBA85-85C2-46BA-8406-99990C204295@vigilsec.com>
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: Wed, 18 Jul 2012 15:54:53 -0000

Joe
>> You're right, I did miss your point, quite thoroughly :-)
>>
>> I am guessing that the answer is that there's no corresponding facility in DNSSEC to for a policy identifier to be published with a DNSKEY RR, but I say that largely ignorant of X.509 and attendant CA policy and hence perhaps am still misunderstanding what you're looking for.

In X.509 each cert can contain a policy OID that indicates the policy 
under which the cert was issued. Thus, when a CA changes it's policy it 
can issue certs under the new policy with the new policy OID. This makes 
it clear to relying parties what policy is in effect, and when a CA 
changes its policy, irrespective of
other changes, e.g., key rollover.

Steve



From jabley@hopcount.ca  Wed Jul 18 11:08:47 2012
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AAD521F8724; Wed, 18 Jul 2012 11:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.197
X-Spam-Level: 
X-Spam-Status: No, score=-102.197 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XpD+FE0CSn4J; Wed, 18 Jul 2012 11:08:46 -0700 (PDT)
Received: from mail.hopcount.ca (mail.hopcount.ca [216.235.14.37]) by ietfa.amsl.com (Postfix) with ESMTP id 808F421F8720; Wed, 18 Jul 2012 11:08:46 -0700 (PDT)
Received: from [2001:4900:1042:100:61c9:41b8:e996:fc8c] by mail.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1SrYgj-000NDl-AP; Wed, 18 Jul 2012 18:09:30 +0000
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <E0BFBA85-85C2-46BA-8406-99990C204295@vigilsec.com>
Date: Wed, 18 Jul 2012 14:09:26 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D2FB5989-E220-4E00-A760-84C85C88A56E@hopcount.ca>
References: <003c01cd6225$6f4cab60$4de60220$@akayla.com> <72D7767E-8AE5-4A91-BE2C-4A949997C5CA@vigilsec.com> <29BF6AF1-3924-42F0-B8BD-1B1250CAECD6@hopcount.ca> <57D81A5A-B80B-4DC1-87FE-450E91A01A20@vigilsec.com> <5AAD9253-F597-4B57-9BA8-C067B3E3839D@hopcount.ca> <E0BFBA85-85C2-46BA-8406-99990C204295@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1278)
Cc: Peter Yee <peter@akayla.com>, gen-art@ietf.org, ietf@ietf.org, draft-ietf-dnsop-dnssec-dps-framework.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, 18 Jul 2012 18:08:47 -0000

On 2012-07-18, at 11:49, Russ Housley wrote:

> So a DNSSEC signer starts under one set of documents, and then for =
whatever reason, the policy changes and the parties validating the =
signature have no means to determine that the signer is following a new =
policy.

They have means, they just don't have a way of deriving a specific =
policy from a specific DNSKEY. The available means are documented in the =
DPS.

> So I am missing the value of the policy to the parties that rely on =
these signatures.

Your suggestion is that if there's no way to the policy just from the =
contents of a DNSKEY RR, there's no point publishing a policy at all?


Joe=

From touch@isi.edu  Wed Jul 18 11:29:15 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 6861411E813B for <ietf@ietfa.amsl.com>; Wed, 18 Jul 2012 11:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.477
X-Spam-Level: 
X-Spam-Status: No, score=-105.477 tagged_above=-999 required=5 tests=[AWL=1.122, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IYlSjwKhvZUE for <ietf@ietfa.amsl.com>; Wed, 18 Jul 2012 11:29:15 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id E366011E8132 for <ietf@ietf.org>; Wed, 18 Jul 2012 11:29:14 -0700 (PDT)
Received: from c1-vpn9.isi.edu (c1-vpn9.isi.edu [128.9.176.39]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q6IITlou005551 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 18 Jul 2012 11:29:47 -0700 (PDT)
Subject: Re: Last Call: <draft-ietf-intarea-ipv4-id-update-05.txt> (Updated Specification of the IPv4 ID Field) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-2022-jp
From: Joe Touch <touch@isi.edu>
In-Reply-To: <500654AB.7060500@necom830.hpcl.titech.ac.jp>
Date: Wed, 18 Jul 2012 11:29:55 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F5CBE79-4540-4519-9F51-62B36686EE8C@isi.edu>
References: <20120531143816.30508.66250.idtracker@ietfa.amsl.com> <Pine.LNX.4.64.1205311957420.31608@shell4.bayarea.net> <4FC9585E.6010205@necom830.hpcl.titech.ac.jp> <4FE2715C.2090601@necom830.hpcl.titech.ac.jp> <4FF20DE7.2080208@isi.edu> <500654AB.7060500@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.1278)
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, 18 Jul 2012 18:29:15 -0000

On Jul 17, 2012, at 11:16 PM, Masataka Ohta wrote:

> Joe Touch wrote:
>=20
>>> Or, are 6 to 4 translators are required to rate limit and
>>> drop rate-violating packets to make the "stateless"
>>> translators full of states.
>>=20
>> I would expect that the translator would be responsible
>> for this, though
>=20
> Do you mean translators must rate limit, or translators
> violate RFC2765:

Translators violate RFC791. They cannot merely copy the low-order bits =
of the field, since that is insufficiently unique, and isn't specified =
as being generated at the IPv6 source in compliance with IPv4 =
requirements.

>> there is the problem that multiple translators interfere
>> with each other.
>=20
> Yes, even rate limiting translators may interfere each other,
> which means rate limiting must be done at the IPv6 source
> node.
>=20
>> Regardless, this is outside the scope of the ipv4-id-update doc.
>=20
> In the ID, there are a lot of references to IPv6.

It quotes IPv6 examples, but does not propose to change IPv6 processing. =
That may be needed, but that would be outside the scope of this doc.

> For example, the following statement of the ID:
>=20
>   Finally, the IPv6 ID field is
>   32 bits, and required unique per source/destination address pair for
>   IPv6, whereas for IPv4 it is only 16 bits and required unique per
>   source/destination/protocol triple.
>=20
> must be modified as:
>=20
>   Finally, the IPv6 ID field is
>   32 bits, but lower 16 bits are required unique per
>   source/destination address pair for
>   IPv6,

That's incorrect as per RFC2460. Other RFCs may violate that original =
spec, but that needs to be cleaned up separately.

Joe=

From Jeff.Hodges@KingsMountain.com  Wed Jul 18 11:59:33 2012
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B9C21F85D4 for <ietf@ietfa.amsl.com>; Wed, 18 Jul 2012 11:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.081
X-Spam-Level: 
X-Spam-Status: No, score=-98.081 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4s+fIsOK64FT for <ietf@ietfa.amsl.com>; Wed, 18 Jul 2012 11:59:32 -0700 (PDT)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [IPv6:2605:dc00:100:2::a2]) by ietfa.amsl.com (Postfix) with SMTP id C2DB821F85D0 for <ietf@ietf.org>; Wed, 18 Jul 2012 11:59:31 -0700 (PDT)
Received: (qmail 3961 invoked by uid 0); 18 Jul 2012 19:00:22 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy9.bluehost.com with SMTP; 18 Jul 2012 19:00:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=BD6b4wg+yA78JerXRfuUBR0xXEEI6lpuSpBKto6zsX0=;  b=SAx6wl+gI8ul7jTrz26W6a6J3ieC+zdSL+otfxQrb0HvmxCzIUBq/YZrwDSKB7U6kcSsvgUgpow3h9Zx9lvZN58bNbo1w7HU09ZOSEhZsY90Xi4cNFQ+VtfYA0OWtaI8;
Received: from [66.91.113.137] (port=49623 helo=[192.168.1.123]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1SrZTx-0002ho-EU for ietf@ietf.org; Wed, 18 Jul 2012 13:00:21 -0600
Message-ID: <500707B1.2090100@KingsMountain.com>
Date: Wed, 18 Jul 2012 12:00:01 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: IETF Discussion List <ietf@ietf.org>
Subject: wrt RL "Bob" Morgan
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 66.91.113.137 authed with jeff.hodges+kingsmountain.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, 18 Jul 2012 18:59:33 -0000

Hi,

I'm very sorry for repetition if you've already heard this, and sorrier still to 
feel compelled to bring it to you all's broad attention in any case...

RL "Bob" Morgan, long-time IETF participant (since at least the Stanford IETF-14 
in Summer 1989), passed away due to complications of cancer on 12-Jul-2012.

He is sorely missed, and IETF meetings/activities won't seem the same without 
his most trenchant perspectives, observations, contributions, and camaraderie.

For more information and tributes, see..

  https://spaces.internet2.edu/display/rlbob/


=JeffH


From anne-marie.eklund-lowinder@iis.se  Thu Jul 19 00:05:54 2012
Return-Path: <anne-marie.eklund-lowinder@iis.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 3261011E808A; Thu, 19 Jul 2012 00:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.948
X-Spam-Level: 
X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g0UXTCDWh8XH; Thu, 19 Jul 2012 00:05:53 -0700 (PDT)
Received: from relay2.iis.se (relay2.iis.se [IPv6:2a00:801:f0:211::147]) by ietfa.amsl.com (Postfix) with ESMTP id DA3AE21F8637; Thu, 19 Jul 2012 00:05:51 -0700 (PDT)
Received: from EXCH2K7HUB-RV.office.nic.se (exch2k7hub-rv.office.nic.se [212.247.204.21]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay2.iis.se (Postfix) with ESMTPS id 69C684001E4; Thu, 19 Jul 2012 07:06:41 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=iis.se; s=r2iis; t=1342681602; bh=YwC9oercfMPFO0ND13AauNzQ9fWCk6iY5xUpGLXQgyY=; h=From:To:CC:Date:Subject:Message-ID:Content-Type:MIME-Version; b=YOwCYpZ80deqqkzSI8RoTkIMlfoxwkHxbasPdv6sENhwhRcADqVCXB/ouVf3ysuwQ Em+f67jj+sUbutMt+PD75qLXdlrg2MtuZhN9+cdbd/fL+ybCnf1uhO75NzE+2Mtsrv OJbDWsz/qd3jMt+YCjLnKglAUgovPCMQQRtpz8sU=
Received: from Exchange2k7.office.nic.se ([fe80::a93a:5ab4:9dba:766f]) by EXCH2K7HUB-RV.office.nic.se ([fe80::99ce:dcd9:be8:9db2%10]) with mapi; Thu, 19 Jul 2012 09:06:40 +0200
From: =?iso-8859-1?Q?Anne-Marie_Eklund-L=F6winder?= <anne-marie.eklund-lowinder@iis.se>
To: Russ Housley <housley@vigilsec.com>, Peter Yee <peter@akayla.com>
Date: Thu, 19 Jul 2012 09:06:40 +0200
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Thread-Topic: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Thread-Index: Ac1ioAQ+ezuxdGX1RSGNXXYCntpGKwC3Qcnc
Message-ID: <E4C9784C-340B-4799-97BA-61B27051803E@iis.se>
Accept-Language: sv-SE
Content-Language: sv-SE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: sv-SE
Content-Type: multipart/alternative; boundary="_000_E4C9784C340B479997BA61B27051803Eiisse_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dnsop-dnssec-dps-framework.all@tools.ietf.org" <draft-ietf-dnsop-dnssec-dps-framework.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, 19 Jul 2012 07:05:54 -0000

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

As one of the co-authors I take the liberty to reply on your question. That=
 is a part of the content of the DPS to announce how updates and amendments=
 are communicated.

Anne-Marie

Sent from my HTC

----- Reply message -----
From: "Russ Housley" <housley@vigilsec.com>
To: "Peter Yee" <peter@akayla.com>
Cc: "draft-ietf-dnsop-dnssec-dps-framework.all@tools.ietf.org" <draft-ietf-=
dnsop-dnssec-dps-framework.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art=
@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-=
08
Date: Sun, Jul 15, 2012 18:39



Peter:

Thanks for the review.  I've not read this document yet, but you review rai=
ses a question in my mind.

If a DNSSEC policy or practice statement is revised or amended, what action=
s are needed make other aware of the change?

Russ


On Jul 14, 2012, at 9:01 PM, Peter Yee 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>.
>
> This draft is ready for publication as an Informational RFC.
>
> Document: draft-ietf-dnsop-dnssec-dps-framework-08
> Reviewer: Peter Yee
> Review Date: 14-July-2012
> IETF LC End Date: 17-July-2012
> IESG Telechat date: Pending
>
> Summary: This draft provides a framework for the creation of DNSSEC Polic=
ies
> and Practice Statements.
>
> Major Issues: None
>
> Minor Issues:
>
> Section 4.4.5 discusses how to handle key compromise.  It might be useful=
 to
> discuss here or somewhere else in the document how the compromise is
> prevented from recurring if there were no attenuating measures in place
> beforehand.  That might well lead to a revision of the DP or DPS.  The dr=
aft
> doesn't really discuss under what circumstances a document should be
> iterated or amended.  Of course, that might be considered a meta issue
> and outside of the scope of the DP or DPS proper.
>
> Nits/editorial comments:
>
> In Section 4.6, "behaviour" is spelt in the British manner.  While
> most assuredly not incorrect, you may wish to spell it in the
> American manner.
>
> Serial commas are used inconsistently.  Nothing as egregious as the
> following
> example, however. ;-)
> http://grammarnowtips.wordpress.com/2011/01/08/a-case-for-the-serial-comm=
a/
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


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

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style></head>
<body>
<style>
<!--
.EmailQuote
	{margin-left:1pt;
	padding-left:4pt;
	border-left:#800000 2px solid}
-->
</style><body>As one of the co-authors I take the liberty to reply on your =
question. That is a part of the content of the DPS to announce how updates =
and amendments are communicated. <br><br>Anne-Marie<br><br>Sent from my HTC=
<br><br><div id=3D"htc_header" style=3D"">----- Reply message -----<br>From=
: &quot;Russ Housley&quot; &lt;housley@vigilsec.com&gt;<br>To: &quot;Peter =
Yee&quot; &lt;peter@akayla.com&gt;<br>Cc: &quot;draft-ietf-dnsop-dnssec-dps=
-framework.all@tools.ietf.org&quot; &lt;draft-ietf-dnsop-dnssec-dps-framewo=
rk.all@tools.ietf.org&gt;, &quot;gen-art@ietf.org&quot; &lt;gen-art@ietf.or=
g&gt;, &quot;ietf@ietf.org&quot; &lt;ietf@ietf.org&gt;<br>Subject: [Gen-art=
] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08<br>Date: Sun, =
Jul 15, 2012 18:39<br><br></div><br><br></body>
<font size=3D"2"><div class=3D"PlainText">Peter:<br>
<br>
Thanks for the review.&nbsp; I've not read this document yet, but you revie=
w raises a question in my mind.<br>
<br>
If a DNSSEC policy or practice statement is revised or amended, what action=
s are needed make other aware of the change?<br>
<br>
Russ<br>
<br>
<br>
On Jul 14, 2012, at 9:01 PM, Peter Yee wrote:<br>
<br>
&gt; I am the assigned Gen-ART reviewer for this draft. For background on<b=
r>
&gt; Gen-ART, please see the FAQ at<br>
&gt; &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br>
&gt; <br>
&gt; This draft is ready for publication as an Informational RFC.<br>
&gt; <br>
&gt; Document: draft-ietf-dnsop-dnssec-dps-framework-08<br>
&gt; Reviewer: Peter Yee<br>
&gt; Review Date: 14-July-2012<br>
&gt; IETF LC End Date: 17-July-2012<br>
&gt; IESG Telechat date: Pending<br>
&gt; <br>
&gt; Summary: This draft provides a framework for the creation of DNSSEC Po=
licies<br>
&gt; and Practice Statements. <br>
&gt; <br>
&gt; Major Issues: None<br>
&gt; <br>
&gt; Minor Issues: <br>
&gt; <br>
&gt; Section 4.4.5 discusses how to handle key compromise.&nbsp; It might b=
e useful to<br>
&gt; discuss here or somewhere else in the document how the compromise is<b=
r>
&gt; prevented from recurring if there were no attenuating measures in plac=
e<br>
&gt; beforehand.&nbsp; That might well lead to a revision of the DP or DPS.=
&nbsp; The draft<br>
&gt; doesn't really discuss under what circumstances a document should be<b=
r>
&gt; iterated or amended.&nbsp; Of course, that might be considered a meta =
issue<br>
&gt; and outside of the scope of the DP or DPS proper.<br>
&gt; <br>
&gt; Nits/editorial comments: <br>
&gt; <br>
&gt; In Section 4.6, &quot;behaviour&quot; is spelt in the British manner.&=
nbsp; While<br>
&gt; most assuredly not incorrect, you may wish to spell it in the<br>
&gt; American manner.<br>
&gt; <br>
&gt; Serial commas are used inconsistently.&nbsp; Nothing as egregious as t=
he<br>
&gt; following<br>
&gt; example, however. ;-)<br>
&gt; <a href=3D"http://grammarnowtips.wordpress.com/2011/01/08/a-case-for-t=
he-serial-comma/">http://grammarnowtips.wordpress.com/2011/01/08/a-case-for=
-the-serial-comma/</a><br>
&gt; <br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; Gen-art mailing list<br>
&gt; Gen-art@ietf.org<br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/gen-art">https://www.=
ietf.org/mailman/listinfo/gen-art</a><br>
<br>
</div></font>
</body>
</html>

--_000_E4C9784C340B479997BA61B27051803Eiisse_--

From stephen.farrell@cs.tcd.ie  Thu Jul 19 03:56:27 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 B2CB121F8683; Thu, 19 Jul 2012 03:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4yOYI58lCSBg; Thu, 19 Jul 2012 03:56:27 -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 E40B521F85E3; Thu, 19 Jul 2012 03:56:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 715B4153663; Thu, 19 Jul 2012 11:57:19 +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=1342695438; bh=x3Edd7DmQxcE47 grygw+wUXF+aWkYdbPNwlOCDDhPrw=; b=kAktqkvOMcdKna49invQRiBHoN5A2e rh4Op1THOZtDsYXouf3oae0gpKmgr3YuuQYZ8FXy23bdp9I+DRYivewaxNQkWLRK ilzZfHGNP4adzpzBiMZQOGu9tYNOYJosuwKqmzcCANzJfTEEvQ139Mu2tFJ8NvrP NlankxrP3GQbzjkEFdglnRpWxhy2NkFRGDP7ASb5nWkFL6BuejmcZxQ77OKFqyaC QaqhvtPTG9XIf9lzLQbnYok4as5DHtxGxggxiGyqjARY680y/o0tBnw02+ayAzfn /VBR3HYinc5FsENizx7A3MdreDtzwNdqCfEL6HgIAURPjn3nBGrbzoew==
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 3xH0ujybs+ir; Thu, 19 Jul 2012 11:57:18 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.45.48.236]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 9E851153661; Thu, 19 Jul 2012 11:57:16 +0100 (IST)
Message-ID: <5007E80C.5070404@cs.tcd.ie>
Date: Thu, 19 Jul 2012 11:57:16 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-08.txt> (A GSS-API Mechanism for the Extensible Authentication Protocol) to Proposed Standard
References: <20120626165832.6142.66386.idtracker@ietfa.amsl.com> <tslk3yt6g2s.fsf@mit.edu>
In-Reply-To: <tslk3yt6g2s.fsf@mit.edu>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: abfab@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, 19 Jul 2012 10:56:27 -0000

Sorry, I should've asked this before but I'm sometimes dumb:-)

If I put in an RFC editor note adding a normative reference
to the new EAP applicability statement [1] would that sort
this out and not cause any problems for anyone?

S.

[1] http://tools.ietf.org/html/draft-winter-abfab-eapapplicability

On 06/26/2012 08:14 PM, Sam Hartman wrote:
> 
> EAP (RFC 3748) has a applicability statement  scoped very strictly to
> network access.
> This document  provides a mechanism that falls well outside that
> applicability statement and permits the use of EAP for general
> application authentication.
> 
> When ABFAB was chartered, there was a charter item to update the EAP
> applicability statement. I think A number of people in the room at the
> BOF, including myself, would have objected to the work being chartered
> had that charter item not been present.
> 
> I think that work is important because I believe there are a number of
> important concerns that apply to the use of EAP for authentication
> beyond network access that need to be documented.
> 
> Unfortunately, the technical specification has gotten ahead of the
> applicability statement update.
> I'm OK with that provided that we're still firmly committed to an
> applicability statement update. As part of approving this document now,
> I want to confirm that we have consensus at least within the ABFAB
> working group and the IESG to do that update.
> If there is any doubt I'd far prefer that this document be held until
> the applicability statement catches up.
> 
> --Sam
> 

From hartmans@mit.edu  Thu Jul 19 04:18:39 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 AA33321F8595; Thu, 19 Jul 2012 04:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.887
X-Spam-Level: 
X-Spam-Status: No, score=-102.887 tagged_above=-999 required=5 tests=[AWL=-0.622, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bqmP0YIiZZFb; Thu, 19 Jul 2012 04:18:39 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2A34E21F8594; Thu, 19 Jul 2012 04:18:39 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 31DB3204BA; Thu, 19 Jul 2012 07:19:50 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id F099441F0; Thu, 19 Jul 2012 07:19:04 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-08.txt> (A GSS-API Mechanism for the Extensible Authentication Protocol) to Proposed Standard
References: <20120626165832.6142.66386.idtracker@ietfa.amsl.com> <tslk3yt6g2s.fsf@mit.edu> <5007E80C.5070404@cs.tcd.ie>
Date: Thu, 19 Jul 2012 07:19:04 -0400
In-Reply-To: <5007E80C.5070404@cs.tcd.ie> (Stephen Farrell's message of "Thu,  19 Jul 2012 11:57:16 +0100")
Message-ID: <tsleho8j8wn.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: abfab@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 11:18:39 -0000

>>>>> "Stephen" == Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:

    Stephen> Sorry, I should've asked this before but I'm sometimes dumb:-)

    Stephen> If I put in an RFC editor note adding a normative reference
    Stephen> to the new EAP applicability statement [1] would that sort
    Stephen> this out and not cause any problems for anyone?

I don't object to that, but it does hold up the doc.  I'm happy letting
this doc go forward now so long as we're all on the same page on the
applicability stament.  I realize we run the risk that somehow the
applicability effort derails.  Personally, I'm willing to take that
risk, so long as we believe today we do intend to publish the
applicability statement.

If someone on the IESG or in the community wants that normative
reference, I support adding it.  I'm just not asking for it myself.

From fredrik@kirei.se  Thu Jul 19 00:41:30 2012
Return-Path: <fredrik@kirei.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 21B5C21F867D for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 00:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_SE=0.35, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KNhGzl9rXIXe for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 00:41:29 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [IPv6:2001:67c:394:15::9]) by ietfa.amsl.com (Postfix) with ESMTP id EC87521F8675 for <ietf@ietf.org>; Thu, 19 Jul 2012 00:41:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:subject:mime-version:content-type:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer; bh=FmFG1ZRnafaCZO56ZjDuyiZI2Py2+Md3jXH6H3wb+Ns=; b=xo4cMRD2uuxkHWBjiovv15tFs6V96r+udEAvXLwxCmffVKVWfGyqP60F4/QP2jWgJtp/Ekh8RsugK OtxgINDEObxJcLZX4gy+IBpiHH7ipzKAph/cFsc8THQ3zR09bauEFFYruuXj/cTwJp9457bOJk/pnx ovCAxOMswWQP0bhU=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Thu, 19 Jul 2012 09:42:16 +0200 (CEST)
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-dnsop-dnssec-dps-framework-08
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Fredrik Ljunggren <fredrik@kirei.se>
In-Reply-To: <57D81A5A-B80B-4DC1-87FE-450E91A01A20@vigilsec.com>
Date: Thu, 19 Jul 2012 09:42:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C51A593C-2280-436D-95BC-FD06DEAD3049@kirei.se>
References: <003c01cd6225$6f4cab60$4de60220$@akayla.com> <72D7767E-8AE5-4A91-BE2C-4A949997C5CA@vigilsec.com> <29BF6AF1-3924-42F0-B8BD-1B1250CAECD6@hopcount.ca> <57D81A5A-B80B-4DC1-87FE-450E91A01A20@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Thu, 19 Jul 2012 08:21:14 -0700
Cc: Peter Yee <peter@akayla.com>, gen-art@ietf.org, draft-ietf-dnsop-dnssec-dps-framework.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 07:41:30 -0000

On 2012-07-18, at 01:06, Russ Housley wrote:

> I think you missed my point.  In a PKI, when the issuer significantly =
changes the policy, subsequent certificates have a different policy =
identifier.  I do not see a similar concept here.

Russ, you are right. There is no such concept in DNSSEC (yet). Simply by =
looking at the signed data, there is no way of determining under what =
policy the data has been signed. Interested parties must stay informed =
using the process specified in section 1.4.3 (Specification change =
procedures) of the DPS.

Generally speaking, DNSSEC signatures are short-lived. =46rom the time a =
new policy is in effect, old signatures will be flushed out within days. =
However, if there are significant changes made to the policy which =
materially affect the security posture of the zone, there may be several =
reasons to roll the signing key(s) and to indicate this in the DPS. This =
way, the validating party will be able to determine under what policy a =
signature has been generated, and act accordingly.

- Fredrik=

From leifj@nordu.net  Thu Jul 19 05:35:07 2012
Return-Path: <leifj@nordu.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7AB121F8724; Thu, 19 Jul 2012 05:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.691
X-Spam-Level: 
X-Spam-Status: No, score=-0.691 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0dOnVVmrSkx; Thu, 19 Jul 2012 05:35:07 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 0B4FA21F8720; Thu, 19 Jul 2012 05:35:06 -0700 (PDT)
Received: from kerio.nordu.net (kerio.nordu.net [109.105.110.42]) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id q6JCZqnJ009192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Jul 2012 14:35:55 +0200 (CEST)
VBR-Info: md=nordu.net; mc=all; mv=dwl.spamhaus.org,swamid.se
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nordu.net; s=default; t=1342701356; bh=W94YJXv/AuY36AQ9QQ4EQCUCaZZ3qQTlVMqJu53+Zr8=; h=From:Subject:Content-Transfer-Encoding:Content-Type:Message-Id: Date:To:Mime-Version; b=E+Jgjn2Ba8QdKQUUjma/G2Wj6LRhgPQAucHGhthLTHhBgdne0GkRitupu6Bfai7ID LIyA6QjRmg3D/2V4+D9205DUAhBEg6ateenOqsq2LxyP/2jzwqMdh8Rl4q7Qyiz0Xl 16NK0G/aqYCQ+VnfewsELuojTtng6coqXI39kXYM=
X-Footer: bm9yZHUubmV0
Received: from [2.66.193.56] ([2.66.193.56]) by kerio.nordu.net; Thu, 19 Jul 2012 14:35:51 +0200
From: "Leif Johansson" <leifj@nordu.net>
Subject: Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-08.txt> (A GSS-API.Mechanism for the Extensible Authentication Protocol) to.Proposed Standard
References: <20120626165832.6142.66386.idtracker@ietfa.amsl.com> <tslk3yt6g2s.fsf@mit.edu> <5007E80C.5070404@cs.tcd.ie> <tsleho8j8wn.fsf@mit.edu>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <tsleho8j8wn.fsf@mit.edu>
Message-Id: <65C49A3B-434A-4782-AFB9-FD940E3B12EA@nordu.net>
Date: Thu, 19 Jul 2012 14:35:47 +0200
To: Sam Hartman <hartmans-ietf@mit.edu>
Mime-Version: 1.0 (1.0)
X-Mailman-Approved-At: Thu, 19 Jul 2012 08:21:13 -0700
Cc: "abfab@ietf.org" <abfab@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 12:41:28 -0000

fyi the applicability stmt version 00 was submitted by joe the other day.

19 jul 2012 kl. 13:19 skrev "Sam Hartman" <hartmans-ietf@mit.edu>:

>>>>>> "Stephen" == Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:
> 
>    Stephen> Sorry, I should've asked this before but I'm sometimes dumb:-)
> 
>    Stephen> If I put in an RFC editor note adding a normative reference
>    Stephen> to the new EAP applicability statement [1] would that sort
>    Stephen> this out and not cause any problems for anyone?
> 
> I don't object to that, but it does hold up the doc.  I'm happy letting
> this doc go forward now so long as we're all on the same page on the
> applicability stament.  I realize we run the risk that somehow the
> applicability effort derails.  Personally, I'm willing to take that
> risk, so long as we believe today we do intend to publish the
> applicability statement.
> 
> If someone on the IESG or in the community wants that normative
> reference, I support adding it.  I'm just not asking for it myself.
> _______________________________________________
> abfab mailing list
> abfab@ietf.org
> https://www.ietf.org/mailman/listinfo/abfab


From simon.perreault@viagenie.ca  Thu Jul 19 11:34:26 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 ED73321F868A; Thu, 19 Jul 2012 11:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.518
X-Spam-Level: 
X-Spam-Status: No, score=-2.518 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QmoWG7e5g+ob; Thu, 19 Jul 2012 11:34:25 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 269DB21F8683; Thu, 19 Jul 2012 11:34:25 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:18fd:ed02:dd69:c681]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 45F45414A1; Thu, 19 Jul 2012 14:35:18 -0400 (EDT)
Message-ID: <50085365.6050701@viagenie.ca>
Date: Thu, 19 Jul 2012 14:35:17 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [BEHAVE] [pcp] Fwd: Re: Martin Stiemerling's Discuss on draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
References: <CC2DB8AA.23DF4%ietfdbh@comcast.net>
In-Reply-To: <CC2DB8AA.23DF4%ietfdbh@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Sam Hartman <hartmans@painless-security.com>, pcp@ietf.org, "behave@ietf.org" <behave@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, 19 Jul 2012 18:34:26 -0000

Le 2012-07-19 14:20, David Harrington a écrit :
> The IETF could mandate a specific protocol to try to ensure
> interoperability, but doing this takes the decision out of the
> responsibility of the deployer to choose the best solution for the
> deployment environment, and out of the responsibility of the vendor to
> best meet their customers' demands.
> Some vendors already support an SNMP-based environment, and a CGN-NAT-MIB
> might best meet their needs.
> Some vendors might support a Netconf environment and desire a
> Netconf-based configuration solution.
> Some vendors already use AAA widely to control their environment, and
> Diameter NAT control might be preferable.

Careful here. The above protocols are not used between the CPE and the 
CGN. The requirement for PCP (or PCP-like) is justified by the need for 
subscribers to be able to control the CGN to some extent.

Note also that any of those protocols could also be supported in 
addition to PCP, up to the implementer and operator.

> Of course, if CGN is only an ipv4 exit strategy, as is asserted,

Not as asserted by the draft, I hope. We have tried making clear that 
CGN as defined in this document really stands for "multi-user NAT" and 
that there are use cases that have nothing to do with IPv4 sunset (e.g. 
the NAT function in a wifi hotspot is a CGN).

The CGN logical function may or may not be used as part of an IPv4 
sunset scenario. As such, it is is absolutely part of behave's core 
expertise. Sunset4 could have things to say about how CGN gets applied 
to IPv4 sunset, but how CGN behaves is up to behave.

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 iad@ietf.org  Thu Jul 19 11:59:22 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 A419C21F871D; Thu, 19 Jul 2012 11:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uw2CBjRHUNTL; Thu, 19 Jul 2012 11:59:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A450A21F8715; Thu, 19 Jul 2012 11:59:21 -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: Agenda Tool RFP Deadline Extended
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120719185921.19473.27600.idtracker@ietfa.amsl.com>
Date: Thu, 19 Jul 2012 11:59:21 -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, 19 Jul 2012 18:59:23 -0000

On 25 May 2012 the  IETF Administrative Oversight Committee (IAOC), on beha=
lf of the =

IETF, announced a Request for Proposals for an IETF Meeting Agenda Scheduli=
ng Tool. =

Proposals were due 9 July 2012.

Today the IAOC announces the deadline for the submission of proposals is ex=
tended until 31 =

August 2012.  Proposals must be received via email at agenda-tool@ietf-bids=
.org no later =

than 31 August.  =


The agenda tool will manage all meeting scheduling and space allocation ass=
ociated with =

interim meetings, Large Interim Meetings and regular IETF meetings. This in=
cludes =

working group sessions, leadership meetings, EDU sessions, BoFs, office hou=
rs, registration, =

breaks, and more.

Bidders may propose customization of an existing product(s), and/or develop=
ment of the =

solution.

The RFP can be found at: http://iaoc.ietf.org/rfpsrfis.html =


All questions/inquiries must be submitted in writing and must be received n=
o later than 10 =

August 2012.  Responses to questions and inquiries shall be posted online a=
t:  http://
iaoc.ietf.org/rfpsrfis.html by 17 August. =


The point of contact regarding this RFP is the IETF Administrative Director=
, Ray Pelletier, =

iad@ietf.org.

Ray Pelletier

From shimshamshimmy@gmail.com  Thu Jul 19 18:10:50 2012
Return-Path: <shimshamshimmy@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D49E111E80CE for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 18:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level: 
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSRPFmy-ol1K for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 18:10:50 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3201311E80A6 for <ietf@ietf.org>; Thu, 19 Jul 2012 18:10:50 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so3811783ggn.31 for <ietf@ietf.org>; Thu, 19 Jul 2012 18:11:44 -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:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=jUQ+HnvttCYGYGMZA6E+dQn8nQ/pn91lTi+LW6oOxXc=; b=WIgfO5XmHkJO8DBh79+/dHF4p/N+Q1DNajkZvjQpWX7vhPOrfb0+r9Zub7LiRKa9BN 9v1uEY62xiSHlazhg8N8k+zeSKi30I4DD4yKUKiGQaoulELlWCna22hN25ihEhOfCJYn 69So43bvfU2ziWmRH2h3BMD3PEFF7bdz6JNUFxl1/maGiRnvwhWHCgTglbkL0X2k5IW5 1RP5++5g6fMl7fv1k5NTASg8wnKKgtX/GAkxcTo9A1cfJ/02KuGsnYyrw9MjQPplIJqD /sZTmKBxQ0vsVPaU3bxZEdDD9psJDFaWWCcWLN4m/cff9chcvf6lS4KNlgVSSvrXskIN PY6A==
Received: by 10.66.74.36 with SMTP id q4mr7629298pav.13.1342746704409; Thu, 19 Jul 2012 18:11:44 -0700 (PDT)
MIME-Version: 1.0
Sender: shimshamshimmy@gmail.com
Received: by 10.68.136.68 with HTTP; Thu, 19 Jul 2012 18:11:21 -0700 (PDT)
In-Reply-To: <CA+k18nWeCCjaPDkfbYQ2k6kAyshu+VQnC9VEeEKTUU+jKmJ-kA@mail.gmail.com>
References: <CA+k18nWeCCjaPDkfbYQ2k6kAyshu+VQnC9VEeEKTUU+jKmJ-kA@mail.gmail.com>
From: Jun Murai <jun@wide.ad.jp>
Date: Fri, 20 Jul 2012 10:11:21 +0900
X-Google-Sender-Auth: QiI8wMO-m8Nn8r5wYBt67sjYxbI
Message-ID: <CA+k18nU6i0TDpmdBFxLLcbXMsBSF-pkOJAyRhAqi0=S9j3PZAw@mail.gmail.com>
Subject: Reminder of CFC FOR ITOJUN SERVICE AWARD
To: "ietf@ietf. org" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 01:10:51 -0000

Dear IETFers,
Here is a reminder of CFC on  Itojun Service Award.

We will have the final moment to complete the list of candidates in
Vancouver on Thursday.
Any of your recommendation and thoughts would be very much appreciated.
Because this is the award for 'IPv6 samurai'!

Thanks,
Jun Murai

=
List of the committee members you might see in Vancouver. See them to talk!;

Jun Murai
Hiroshi Esaki
Ole Jacobsen
Bob Hinden
Bill Manning
Tatuya Jinmei
Kazu Yamamoto
Kenjiro Cho
Erik Kline
Lorenzo Colitti
Bjoern A. Zeeb
Remi Despres




==
ANNOUNCING: CALL FOR CANDIDATES FOR ITOJUN SERVICE AWARD

The Itojun Service Award is presented every year to an individual or a
group who has made outstanding contributions in service to the IPv6
community.   The deadline for nominations for this year's award is
(extended to be on ) 2 August 2012.  The award will be presented at
the 85th meeting of the
IETF to be held in November 2012 in Atlanta, USA.

About the Award

The Itojun Service Award was established by the friends of Itojun and
administered by the Internet Society (ISOC), recognises and
commemorates the extraordinary dedication exercised by Itojun over the
course of IPv6 development.  The award includes a presentation
crystal, a US$3,000 honorarium, and a travel grant.

The award is focused on pragmatic technical contributions, especially
through development or operation, with the spirit of servicing the
Internet.  With respect to the spirit, the selection committee seeks
contributors to the Internet as a whole; open source developers are a
common example of such contributors, although this is not a
requirement for expected nominees.  While the committee primarily
consider practical contributions such as software development or
network operation, higher level efforts that help those direct
contributions will also be appreciated in this regard.  The
contribution should be substantial, but could be immature or ongoing;
this award aims to encourage the contributor to keep their efforts,
rather than just recognizing well established work.  Finally,
contributions of a group of individuals will be accepted as deployment
work is often done by a large project, not just a single outstanding
individual.

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

From sm@resistor.net  Thu Jul 19 18:13:04 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 06F2011E80CE; Thu, 19 Jul 2012 18:13:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cXEIDa4gxVcB; Thu, 19 Jul 2012 18:13:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A4A8611E80A6; Thu, 19 Jul 2012 18:13:01 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q6K1Do9i027742; Thu, 19 Jul 2012 18:13:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1342746835; bh=SQvZh6Kiq0SZTCEC7cFS0DiVVmKbqh6MRPhaHo5l2/E=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2qtp/W+OGJSkpWvxWOa6qh6APeyFFI3Huv4e0nItciJt/Oj+iZixqbd6cYrMm24q7 w9pba+DvK2Km2ZIvfQbBctG/e8zE02QSsInzthst84qJX+hdHecekvAXgjDYVRmYWh MA+T1VnidJjKzfqyybSlUP8hlPxoyvQEu98efTLA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1342746835; i=@resistor.net; bh=SQvZh6Kiq0SZTCEC7cFS0DiVVmKbqh6MRPhaHo5l2/E=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MkA/3QzukdKRMGlEwpcr83vH1gXV4T3tNHnvJ+USu55t2AfIAi9DRjcX12FfcCIuz SiV2odvOfpC7TF0h5KCrpXRKj9wznMgYuJ5EUuKncJfpk1No2yOF0x7aZsaDuXh2ly oWRAiVl2pHy2u54nokrLc7yEs6P7UYUjC+HEpVPk=
Message-Id: <6.2.5.6.2.20120719171949.0a4d0ad8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 19 Jul 2012 18:10:52 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-dnsop-dnssec-dps-framework-08.txt> (A Framework for DNSSEC Policies and DNSSEC Practice Statements) to Informational RFC
In-Reply-To: <20120703211559.31773.84433.idtracker@ietfa.amsl.com>
References: <20120703211559.31773.84433.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: dnsop@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 01:13:04 -0000

At 14:15 03-07-2012, The IESG wrote:
>The IESG has received a request from the Domain Name System Operations WG
>(dnsop) to consider the following document:
>- 'A Framework for DNSSEC Policies and DNSSEC Practice Statements'
>   <draft-ietf-dnsop-dnssec-dps-framework-08.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2012-07-17. Exceptionally, comments may be

This comment is after the deadline.  The draft is 
well-written.  Thanks to the authors and DNSOP WG Chairs for moving forward.

The question which Russ posted, e.g. Specification change procedures
  ( http://www.ietf.org/mail-archive/web/ietf/current/msg73975.html ) 
may be related to Section 4.1.4 of the draft.  A sentence could be 
added about specification change procedures.

Regards,
-sm




From narten@us.ibm.com  Thu Jul 19 21:52:12 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 CEDC021F863C for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 21:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.369
X-Spam-Level: 
X-Spam-Status: No, score=-110.369 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KV9kVgSf1l7g for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 21:52:12 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by ietfa.amsl.com (Postfix) with ESMTP id 0C07F21F8555 for <ietf@ietf.org>; Thu, 19 Jul 2012 21:52:11 -0700 (PDT)
Received: from /spool/local by e38.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, 19 Jul 2012 22:53:06 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 19 Jul 2012 22:53:05 -0600
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 134813E40026 for <ietf@ietf.org>; Fri, 20 Jul 2012 04:53:04 +0000 (WET)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q6K4r4oZ295334 for <ietf@ietf.org>; Thu, 19 Jul 2012 22:53:04 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q6K4r444005791 for <ietf@ietf.org>; Thu, 19 Jul 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q6K4r3FU005759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 19 Jul 2012 22:53:04 -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 q6K4r2XK020089 for <ietf@ietf.org>; Fri, 20 Jul 2012 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q6K4r2Dw020055 for ietf@ietf.org; Fri, 20 Jul 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201207200453.q6K4r2Dw020055@rotala.raleigh.ibm.com>
Date: Fri, 20 Jul 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: 12072004-5518-0000-0000-0000062C2684
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 04:52:13 -0000

Total of 36 messages in the last 7 days.
 
script run at: Fri Jul 20 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.56% |    2 | 11.13% |    29264 | ron.even.tlv@gmail.com
  8.33% |    3 |  8.28% |    21783 | sm@resistor.net
  8.33% |    3 |  7.65% |    20102 | housley@vigilsec.com
  8.33% |    3 |  6.52% |    17141 | jabley@hopcount.ca
  5.56% |    2 |  5.66% |    14878 | presnick@qualcomm.com
  2.78% |    1 |  4.58% |    12034 | anne-marie.eklund-lowinder@iis.se
  2.78% |    1 |  4.12% |    10825 | david.black@emc.com
  2.78% |    1 |  3.69% |     9715 | scottr.nist@gmail.com
  2.78% |    1 |  3.03% |     7975 | alexey.melnikov@isode.com
  2.78% |    1 |  2.93% |     7703 | jun@wide.ad.jp
  2.78% |    1 |  2.89% |     7592 | gonzalo.camarillo@ericsson.com
  2.78% |    1 |  2.86% |     7533 | narten@us.ibm.com
  2.78% |    1 |  2.82% |     7403 | huitema@microsoft.com
  2.78% |    1 |  2.72% |     7143 | stephen.farrell@cs.tcd.ie
  2.78% |    1 |  2.53% |     6662 | touch@isi.edu
  2.78% |    1 |  2.46% |     6458 | leifj@nordu.net
  2.78% |    1 |  2.44% |     6423 | simon.perreault@viagenie.ca
  2.78% |    1 |  2.44% |     6405 | fredrik@kirei.se
  2.78% |    1 |  2.35% |     6168 | mohta@necom830.hpcl.titech.ac.jp
  2.78% |    1 |  2.24% |     5887 | peter@akayla.com
  2.78% |    1 |  2.19% |     5753 | hartmans-ietf@mit.edu
  2.78% |    1 |  2.19% |     5750 | jeff.hodges@kingsmountain.com
  2.78% |    1 |  2.18% |     5725 | sm+ietf@elandsys.com
  2.78% |    1 |  2.16% |     5670 | john-ietf@jck.com
  2.78% |    1 |  2.12% |     5567 | kent@bbn.com
  2.78% |    1 |  2.05% |     5395 | iad@ietf.org
  2.78% |    1 |  2.01% |     5288 | weiler@watson.org
  2.78% |    1 |  1.79% |     4694 | randy@psg.com
--------+------+--------+----------+------------------------
100.00% |   36 |100.00% |   262936 | Total


From iad@ietf.org  Fri Jul 20 06:07:34 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 3873621F865E; Fri, 20 Jul 2012 06:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vGG1xjJsI3jP; Fri, 20 Jul 2012 06:07:33 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB38D21F8643; Fri, 20 Jul 2012 06:07:33 -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: Feedback Requested on Draft Fees Policy
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
Date: Fri, 20 Jul 2012 06:07:33 -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: Fri, 20 Jul 2012 13:07:34 -0000

The IAOC is seeking community feedback on a proposed policy by the IAOC to =
impose =

fees to produce information and authenticate documents in response to subpo=
enas and =

other legal requests.

The IETF receives requests for information, documentation, authentication o=
r other =

matters through subpoenas and less formal means that require manpower and m=
aterials =

to be expended.  These requests are on the rise. During the period 2005 to =
2010 the IETF =

responded to nine subpoenas.  Since 2011 the IETF has received five subpoen=
as and three =

other legal requests for authenticated documents.  =


Each such request is time sensitive and involves the IETF Counsel, the IAD,=
 and members =

of the IAOC, who together form the Legal Management Committee, to rapidly a=
nalyze and =

identify the means for satisfying the request.  Often there is a need to re=
tain outside counsel, =

especially in cases that might lead to depositions or court testimony. =


The IAOC believes a Schedule of Fees is an appropriate and reasonable means=
 to recover =

costs associated with such efforts.

The draft policy entitled Draft Fee Policy for Legal Requests can be found =

at: <http://iaoc.ietf.org/policyandprocedures.html>

Before adopting a policy the IAOC would like feedback on this before making=
 a =

decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.

Ray Pelletier
IETF Administrative Director

From ajs@anvilwalrusden.com  Fri Jul 20 06:22:15 2012
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6CF221F8629 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 06:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.281
X-Spam-Level: 
X-Spam-Status: No, score=-1.281 tagged_above=-999 required=5 tests=[AWL=-0.441, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fADMwa93nEZV for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 06:22:15 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 2DC6421F861B for <ietf@ietf.org>; Fri, 20 Jul 2012 06:22:15 -0700 (PDT)
Received: from mail.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 267CE8A031 for <ietf@ietf.org>; Fri, 20 Jul 2012 13:23:10 +0000 (UTC)
Date: Fri, 20 Jul 2012 09:23:03 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Feedback Requested on Draft Fees Policy
Message-ID: <20120720132302.GA3594@mail.yitter.info>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120720130733.14364.19024.idtracker@ietfa.amsl.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, 20 Jul 2012 13:22:16 -0000

On Fri, Jul 20, 2012 at 06:07:33AM -0700, IETF Administrative Director wrote:
> Before adopting a policy the IAOC would like feedback on this before making a 
> decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.

I think this is a perfectly legitimate policy, and I support it.  The
fees don't seem to be outrageous to me.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dworley@avaya.com  Fri Jul 20 06:51:49 2012
Return-Path: <dworley@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 A9CC021F861B for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 06:51:49 -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.431, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JXfsX3+Ley85 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 06:51:49 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA1A21F8617 for <ietf@ietf.org>; Fri, 20 Jul 2012 06:51:48 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAOhhCVDGmAcF/2dsb2JhbABFhXSyNYEXgQeCIAEBAQEDEhERVQIBCA0LAgImAgICMBUQAQEEGxqHawuhW4oekxqBII98MmADlliEaIoPgns
X-IronPort-AV: E=Sophos;i="4.77,623,1336363200"; d="scan'208";a="358193810"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 Jul 2012 09:49:07 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Jul 2012 09:48:57 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 20 Jul 2012 09:52:43 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 20 Jul 2012 09:52:43 -0400
Subject: Re: Feedback Requested on Draft Fees Policy
Thread-Topic: Feedback Requested on Draft Fees Policy
Thread-Index: Ac1mfu/l+y5GsejeQYiUL/3QgBiCKQ==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A1D8C@DC-US1MBEX4.global.avaya.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
In-Reply-To: <20120720130733.14364.19024.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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 13:51:49 -0000

T24gRnJpLCAyMDEyLTA3LTIwIGF0IDA2OjA3IC0wNzAwLCBJRVRGIEFkbWluaXN0cmF0aXZlIERp
cmVjdG9yIHdyb3RlOgo+IFRoZSBkcmFmdCBwb2xpY3kgZW50aXRsZWQgRHJhZnQgRmVlIFBvbGlj
eSBmb3IgTGVnYWwgUmVxdWVzdHMgY2FuIGJlIGZvdW5kIAo+IGF0OiA8aHR0cDovL2lhb2MuaWV0
Zi5vcmcvcG9saWN5YW5kcHJvY2VkdXJlcy5odG1sPgoKQXNzdW1pbmcgdGhhdCB0aGUgSUFPQyBo
YXMgc2V0IHRoZXNlIGZlZXMgdG8gYmUgY2xvc2UgdG8gdGhlIGFjdHVhbApjb3N0cyBvZiBzZXJ2
aWNpbmcgbGVnYWwgcmVxdWVzdHMsIEkgc2VlIG5vIG9iamVjdGlvbiB0byB0aGUgcG9saWN5LgoK
RGFsZQoK

From warren@kumari.net  Fri Jul 20 07:04:40 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 12BA921F8621; Fri, 20 Jul 2012 07:04:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.481
X-Spam-Level: 
X-Spam-Status: No, score=-106.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KTFdvYYaM308; Fri, 20 Jul 2012 07:04:39 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 7EBEE21F85A3; Fri, 20 Jul 2012 07:04:39 -0700 (PDT)
Received: from [192.168.0.12] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id BEB411B402E4; Fri, 20 Jul 2012 10:05:34 -0400 (EDT)
Subject: Re: Feedback Requested on Draft Fees Policy
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
Date: Fri, 20 Jul 2012 10:05:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
To: IETF Administrative Director <iad@ietf.org>
X-Mailer: Apple Mail (2.1278)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:04:40 -0000

On Jul 20, 2012, at 9:07 AM, IETF Administrative Director wrote:

> The IAOC is seeking community feedback on a proposed policy by the =
IAOC to impose=20
> fees to produce information and authenticate documents in response to =
subpoenas and=20
> other legal requests.
>=20
> The IETF receives requests for information, documentation, =
authentication or other=20
> matters through subpoenas and less formal means that require manpower =
and materials=20
> to be expended.  These requests are on the rise. During the period =
2005 to 2010 the IETF=20
> responded to nine subpoenas.  Since 2011 the IETF has received five =
subpoenas and three=20
> other legal requests for authenticated documents. =20
>=20
> Each such request is time sensitive and involves the IETF Counsel, the =
IAD, and members=20
> of the IAOC, who together form the Legal Management Committee, to =
rapidly analyze and=20
> identify the means for satisfying the request.  Often there is a need =
to retain outside counsel,=20
> especially in cases that might lead to depositions or court testimony.=20=

>=20
> The IAOC believes a Schedule of Fees is an appropriate and reasonable =
means to recover=20
> costs associated with such efforts.
>=20
> The draft policy entitled Draft Fee Policy for Legal Requests can be =
found=20
> at: <http://iaoc.ietf.org/policyandprocedures.html>
>=20
> Before adopting a policy the IAOC would like feedback on this before =
making a=20
> decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.
>=20
> Ray Pelletier
> IETF Administrative Director
>=20


LGTM++.

Seems like a grand idea -- who knows, may even help avoid nuisance suits =
(although the fees are so small (compared to all the other costs) that I =
don't hold much hope of this=85).

W

--
For every complex problem, there is a solution that is simple, neat, and =
wrong.
                -- H. L. Mencken




From rbarnes@bbn.com  Fri Jul 20 07:07:54 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 1929C21F862F; Fri, 20 Jul 2012 07:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjkiUZJNPuzT; Fri, 20 Jul 2012 07:07:53 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 67D6521F862B; Fri, 20 Jul 2012 07:07:53 -0700 (PDT)
Received: from ros-dhcp192-1-51-20.bbn.com ([192.1.51.20]:65431) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SsDsr-000JqX-E6; Fri, 20 Jul 2012 10:08:45 -0400
Subject: Re: Feedback Requested on Draft Fees Policy
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=windows-1252
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net>
Date: Fri, 20 Jul 2012 10:08:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1278)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:07:54 -0000

+1

Although I wonder whether radical openness would be cheaper in the long =
run: Put everything online and have an auto-responder at =
subpoena@ietf.org that says "Go look it up yourself."

--Richard



On Jul 20, 2012, at 10:05 AM, Warren Kumari wrote:

>=20
> On Jul 20, 2012, at 9:07 AM, IETF Administrative Director wrote:
>=20
>> The IAOC is seeking community feedback on a proposed policy by the =
IAOC to impose=20
>> fees to produce information and authenticate documents in response to =
subpoenas and=20
>> other legal requests.
>>=20
>> The IETF receives requests for information, documentation, =
authentication or other=20
>> matters through subpoenas and less formal means that require manpower =
and materials=20
>> to be expended.  These requests are on the rise. During the period =
2005 to 2010 the IETF=20
>> responded to nine subpoenas.  Since 2011 the IETF has received five =
subpoenas and three=20
>> other legal requests for authenticated documents. =20
>>=20
>> Each such request is time sensitive and involves the IETF Counsel, =
the IAD, and members=20
>> of the IAOC, who together form the Legal Management Committee, to =
rapidly analyze and=20
>> identify the means for satisfying the request.  Often there is a need =
to retain outside counsel,=20
>> especially in cases that might lead to depositions or court =
testimony.=20
>>=20
>> The IAOC believes a Schedule of Fees is an appropriate and reasonable =
means to recover=20
>> costs associated with such efforts.
>>=20
>> The draft policy entitled Draft Fee Policy for Legal Requests can be =
found=20
>> at: <http://iaoc.ietf.org/policyandprocedures.html>
>>=20
>> Before adopting a policy the IAOC would like feedback on this before =
making a=20
>> decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.
>>=20
>> Ray Pelletier
>> IETF Administrative Director
>>=20
>=20
>=20
> LGTM++.
>=20
> Seems like a grand idea -- who knows, may even help avoid nuisance =
suits (although the fees are so small (compared to all the other costs) =
that I don't hold much hope of this=85).
>=20
> W
>=20
> --
> For every complex problem, there is a solution that is simple, neat, =
and wrong.
>                -- H. L. Mencken
>=20
>=20
>=20


From scott.brim@gmail.com  Fri Jul 20 07:13:42 2012
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 686F021F8681; Fri, 20 Jul 2012 07:13:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTyxW+7Y3lzX; Fri, 20 Jul 2012 07:13:41 -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 43AD121F864B; Fri, 20 Jul 2012 07:13:41 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so6471590pbc.31 for <multiple recipients>; Fri, 20 Jul 2012 07:14:34 -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=FlEJgWCzhVDBxNmXFhly4LbID15IR3dQxh1C2/Wh910=; b=R6BkLQ1paXkGI38nILY6KD7cW96qRiUJOyxjjljXwwJnQa2rj4wX3sPVIVGDB48xm6 ynntQjtzV3SkSCP8TG8Q5WyqEMjvwAj9H8CZq0VxPPL+yiHjFC2z0HT9aKLmNNfds8fw GRbutttOr3biGC0OfhSGd1uDXpePX9vGO7D8SHsmyULUR1Qw683kndms4z48jrlm4q8q 6wbxV4zWPGTsRVhE2TuF633o3bl6nrw76huuR2P1YBJQ3vyEsPgkiSbmU9MuaK/f+3SE EbfIs2/d8DKny73HgiFvgSeTqubvPPCvwDJtaz423eVsRZwBZ61dtbyOB1S5fRUDX3jk MdBQ==
MIME-Version: 1.0
Received: by 10.68.129.168 with SMTP id nx8mr14076758pbb.112.1342793674128; Fri, 20 Jul 2012 07:14:34 -0700 (PDT)
Received: by 10.68.220.132 with HTTP; Fri, 20 Jul 2012 07:14:34 -0700 (PDT)
In-Reply-To: <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com>
Date: Fri, 20 Jul 2012 07:14:34 -0700
Message-ID: <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com>
Subject: Re: Feedback Requested on Draft Fees Policy
From: Scott Brim <scott.brim@gmail.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: multipart/alternative; boundary=047d7b10cb6ff3fe1504c54383ba
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:13:43 -0000

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

>
> > On Jul 20, 2012, at 9:07 AM, IETF Administrative Director wrote:
> >> The draft policy entitled Draft Fee Policy for Legal Requests can be
> found
> >> at: <http://iaoc.ietf.org/policyandprocedures.html>
>

Fine idea.

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&gt; On Jul 20, 2012, at 9:07 AM, IETF Admin=
istrative Director wrote:<br>&gt;&gt; The draft policy entitled Draft Fee P=
olicy for Legal Requests can be found<br>

&gt;&gt; at: &lt;<a href=3D"http://iaoc.ietf.org/policyandprocedures.html" =
target=3D"_blank">http://iaoc.ietf.org/policyandprocedures.html</a>&gt;<br>=
</blockquote><div><br></div><div>Fine idea.=A0</div>

--047d7b10cb6ff3fe1504c54383ba--

From sob@harvard.edu  Fri Jul 20 07:16:15 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 9C88221F8682; Fri, 20 Jul 2012 07:16:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.449
X-Spam-Level: 
X-Spam-Status: No, score=-103.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TWOUOoCiaa-L; Fri, 20 Jul 2012 07:16:15 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id B04AA21F8672; Fri, 20 Jul 2012 07:16:14 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000000.university.harvard.edu [10.35.2.151]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id E032EE8F93; Fri, 20 Jul 2012 10:17:09 -0400 (EDT)
Received: from ENTWHUBT0000007.university.harvard.edu (192.168.236.27) by ENTWEDGE0000000.university.harvard.edu (10.35.2.151) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 20 Jul 2012 10:16:31 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.84]) by ENTWHUBT0000007.university.harvard.edu ([192.168.236.29]) with mapi id 14.01.0355.002; Fri, 20 Jul 2012 10:17:09 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Feedback Requested on Draft Fees Policy
Thread-Topic: Feedback Requested on Draft Fees Policy
Thread-Index: AQHNZoJYmCUNzXWKXEamw9YDfsScmw==
Date: Fri, 20 Jul 2012 14:17:08 +0000
Message-ID: <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com> <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com>
In-Reply-To: <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [140.247.60.212]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F116CA1E3E6C1F4EA70EDB95FAAF80DE@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:16:16 -0000

great idea - just does not jive with the legal system which often need auth=
enticated=20
copies of documents

Scott

On Jul 20, 2012, at 10:14 AM, Scott Brim wrote:

> > On Jul 20, 2012, at 9:07 AM, IETF Administrative Director wrote:
> >> The draft policy entitled Draft Fee Policy for Legal Requests can be f=
ound
> >> at: <http://iaoc.ietf.org/policyandprocedures.html>
>=20
> Fine idea.=20




From rbarnes@bbn.com  Fri Jul 20 07:24:22 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 5460021F865D; Fri, 20 Jul 2012 07:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.59
X-Spam-Level: 
X-Spam-Status: No, score=-106.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHSbDcNzi8F8; Fri, 20 Jul 2012 07:24:21 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 9D73B21F8659; Fri, 20 Jul 2012 07:24:21 -0700 (PDT)
Received: from ros-dhcp192-1-51-20.bbn.com ([192.1.51.20]:65533) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SsE8f-000Caa-Qa; Fri, 20 Jul 2012 10:25:05 -0400
Subject: Re: Feedback Requested on Draft Fees Policy
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu>
Date: Fri, 20 Jul 2012 10:25:03 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com> <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com> <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu>
To: "Bradner, Scott" <sob@harvard.edu>
X-Mailer: Apple Mail (2.1278)
Cc: wgchairs@ietf.org, iab@iab.org, ietf@ietf.org, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:24:22 -0000

[assuming you mean the "go look it up" idea]

We have the technology.  Surely a CMS signed object (or even just an =
HTTPS download) would provide adequate authentication that it came from =
the IETF.  And it doesn't seem like we would have a problem providing =
authenticated documents to the world.




On Jul 20, 2012, at 10:17 AM, Bradner, Scott wrote:

> great idea - just does not jive with the legal system which often need =
authenticated=20
> copies of documents
>=20
> Scott
>=20
> On Jul 20, 2012, at 10:14 AM, Scott Brim wrote:
>=20
>>> On Jul 20, 2012, at 9:07 AM, IETF Administrative Director wrote:
>>>> The draft policy entitled Draft Fee Policy for Legal Requests can =
be found
>>>> at: <http://iaoc.ietf.org/policyandprocedures.html>
>>=20
>> Fine idea.=20
>=20
>=20
>=20


From brian.e.carpenter@gmail.com  Fri Jul 20 07:38:28 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 B639A21F852B; Fri, 20 Jul 2012 07:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.332
X-Spam-Level: 
X-Spam-Status: No, score=-101.332 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iWxGcbbQHEeJ; Fri, 20 Jul 2012 07:38:28 -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 213AE21F852C; Fri, 20 Jul 2012 07:38:26 -0700 (PDT)
Received: by wibhr14 with SMTP id hr14so494104wib.13 for <multiple recipients>; Fri, 20 Jul 2012 07:39:22 -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=X+RCIWgVBQZ0JYybN+L+nVe3mMc5nQbFMckE14DPA38=; b=uKagygbVWNSD9Bm2xyPAKCWIVw5m8vfMmI8KKr1Ni5MjdeYEnwyX2xoQeOvjtXWh5B 9acU7fADFo2TadoT0E78u8o23iHMtHsnPdj+Q4H0x6T7fWwql5yiRhQn1pPGohjRlbMz Sb7oNVyyuvskuyWRlut81K6MsZPMNQiAEQ5BzdAnGPSWlR5ECZikrvsx94/uOn1zdtaU LLgMMadRRbQXNFXn76oSbxGQMsonP8n3vw5jOGsvecP/SHUC2lpK76lj/EoRqXMF6N20 GRVPzDD/cZ2Hk89tsHpjf0/t6gzLuPFJoWflq6dCIsxgaeUN6eYmWQHnCB2reyDk0uet KuIA==
Received: by 10.180.14.8 with SMTP id l8mr15095605wic.6.1342795162556; Fri, 20 Jul 2012 07:39:22 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-72.as13285.net. [2.102.218.72]) by mx.google.com with ESMTPS id e43sm14960795eep.4.2012.07.20.07.39.20 (version=SSLv3 cipher=OTHER); Fri, 20 Jul 2012 07:39:21 -0700 (PDT)
Message-ID: <50096DA3.6080800@gmail.com>
Date: Fri, 20 Jul 2012 15:39:31 +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: IETF Administrative Director <iad@ietf.org>
Subject: Re: Feedback Requested on Draft Fees Policy
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
In-Reply-To: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: iesg@ietf.org, iaoc@ietf.org, iab@iab.org, IETF discussion list <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: Fri, 20 Jul 2012 14:38:29 -0000

On 20/07/2012 14:07, IETF Administrative Director wrote:
> The IAOC is seeking community feedback on a proposed policy by the IAOC to impose 
> fees to produce information and authenticate documents in response to subpoenas and 
> other legal requests.

Do it. This will dissuade trivial requests and will be a drop in the ocean
of costs for serious lawsuits.

Don't forget to appropriately update http://iaoc.ietf.org/subpoena.html.

 Brian

From john-ietf@jck.com  Fri Jul 20 07:39:18 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 4EA7221F8530 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 07:39:18 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCqGFnoLu0qY; Fri, 20 Jul 2012 07:39:17 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A941721F852E; Fri, 20 Jul 2012 07:39:17 -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 1SsEHt-000Hwq-M5; Fri, 20 Jul 2012 10:34:37 -0400
Date: Fri, 20 Jul 2012 10:40:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: IETF Administrative Director <iad@ietf.org>
Subject: Re: Feedback Requested on Draft Fees Policy
Message-ID: <CF472A8775DF4CDEEA6A1325@JcK-HP8200.jck.com>
In-Reply-To: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:39:18 -0000

--On Friday, July 20, 2012 06:07 -0700 IETF Administrative
Director <iad@ietf.org> wrote:

> The IAOC is seeking community feedback on a proposed policy by
> the IAOC to impose  fees to produce information and
> authenticate documents in response to subpoenas and  other
> legal requests.
>...
> Before adopting a policy the IAOC would like feedback on this
> before making a  decision.  Comments appreciated to
> ietf@ietf.org by 6 August 2012.

Seems entirely reasonable.  Knowing how much effort some of
these requests can produce, I do wonder if the fees are a bit
too low but trust that the IAOC has determined that they will at
least cover costs.

   john





From ynir@checkpoint.com  Fri Jul 20 08:42:56 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 2140121F8554 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 08:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.365
X-Spam-Level: 
X-Spam-Status: No, score=-10.365 tagged_above=-999 required=5 tests=[AWL=0.234, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZqzalZ0H2z8 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 08:42:55 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id F2C4D21F8550 for <ietf@ietf.org>; Fri, 20 Jul 2012 08:42:54 -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 q6KFhkLd030964; Fri, 20 Jul 2012 18:43:46 +0300
X-CheckPoint: {50097AC4-2-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, 20 Jul 2012 18:43:46 +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, 20 Jul 2012 18:43:44 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Date: Fri, 20 Jul 2012 18:43:43 +0300
Subject: Re: Feedback Requested on Draft Fees Policy
Thread-Topic: Feedback Requested on Draft Fees Policy
Thread-Index: Ac1mjnFjAnSZy7oMQYqnb2sydxw24w==
Message-ID: <7CB6858E-9F28-4BA7-8683-3903F521C2A0@checkpoint.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <CD5674C3CD99574EBA7432465FC13C1B22726A1D8C@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A1D8C@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 1121b2ac03bd1a7d5a2c11e8136fbfd8bd4fdfde5c
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 15:42:56 -0000

On Jul 20, 2012, at 4:52 PM, Worley, Dale R (Dale) wrote:

> On Fri, 2012-07-20 at 06:07 -0700, IETF Administrative Director wrote:
>> The draft policy entitled Draft Fee Policy for Legal Requests can be fou=
nd=20
>> at: <http://iaoc.ietf.org/policyandprocedures.html>
>=20
> Assuming that the IAOC has set these fees to be close to the actual
> costs of servicing legal requests, I see no objection to the policy.

It's hard to gauge the actual costs. What is an hour spent by a volunteer w=
orth? Counsel fees can be measured and covered, but the IAOC members are sp=
ending their own (or their employer's) resources on this.

Although a lot of the work is done by volunteers, in this case we're sellin=
g their work to others, and we should not sell it cheaply.

I support this policy.

Yoav



From johnl@iecc.com  Fri Jul 20 08:50:45 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 D371C21F85C2 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 08:50:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.137
X-Spam-Level: 
X-Spam-Status: No, score=-111.137 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oym3qoyvrm+w for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 08:50:45 -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 AC1FF21F85C6 for <ietf@ietf.org>; Fri, 20 Jul 2012 08:50:44 -0700 (PDT)
Received: (qmail 94010 invoked from network); 20 Jul 2012 15:51:38 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Jul 2012 15:51:38 -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=50097e8a.xn--3zv.k1207; i=johnl@user.iecc.com; bh=lPG4I4oXrRpfl2n275VY5BTzZxLMSkIZWpouNoOUwuw=; b=SKJMg0/ei0+8Wo7PayIOleI/tXkB6j3TiBDXvvHj+K9mbuXIq2HZeh7GD7ONl9PEmc+uZQNFyOvR9ke11LSootdUAjAhEip9bv0WPbfKH7Rbhb88CTJAMiVAQ/8YKxfgsIt8KW1dr8G2f2c6sJHaQYeZAO0VhiTfDyVsH+M/GFE=
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=50097e8a.xn--3zv.k1207; olt=johnl@user.iecc.com; bh=lPG4I4oXrRpfl2n275VY5BTzZxLMSkIZWpouNoOUwuw=; b=MVs+w81RH0mXynThugo+NMJMqqeJULJ7K3cHvQxJaVTq039Vfj6ayE9F0yGjZk3Tv3KVWTvI56da5Q34AQBG7Gz0sFkaM3rf+DL7q0ThliihfE3dzqiq00LqflmR5dr7xfoOTyT8bXrZGFdsrXQ9ciUvdF3n7tR2nauJbf/s+IQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 20 Jul 2012 15:51:16 -0000
Message-ID: <20120720155116.91353.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Feedback Requested on Draft Fees Policy
In-Reply-To: <7CB6858E-9F28-4BA7-8683-3903F521C2A0@checkpoint.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 15:50:46 -0000

>>> The draft policy entitled Draft Fee Policy for Legal Requests can be found 
>>> at: <http://iaoc.ietf.org/policyandprocedures.html>

It seems fine to me, but I would add an hourly rate for research.

For requests for e-mail, do they typically provide pointers to the
specific archive entries, or do they ask for all mail from A on topic
B in month M?  In the latter case, a suitable hourly research fee
would likely persuade many lawyers to tell an associate to learn how
to use grep.

R's,
John

PS: Yes, I know it's volunteers.  The revenue would go into the cookies fund.



From dhc@dcrocker.net  Fri Jul 20 08:55:46 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 24FC021F8637; Fri, 20 Jul 2012 08:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2dKRuH09QZAc; Fri, 20 Jul 2012 08:55:45 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3884921F862F; Fri, 20 Jul 2012 08:55:45 -0700 (PDT)
Received: from [172.19.82.26] (64.125.189.90.t00817-23.above.net [64.125.189.90] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q6KFuaBN013392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 20 Jul 2012 08:56:37 -0700
Message-ID: <50097FAE.9060805@dcrocker.net>
Date: Fri, 20 Jul 2012 08:56:30 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Richard L. Barnes" <rbarnes@bbn.com>
Subject: Re: Feedback Requested on Draft Fees Policy
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com> <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com> <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu> <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.com>
In-Reply-To: <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.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, 20 Jul 2012 08:56:37 -0700 (PDT)
Cc: wgchairs@ietf.org, iab@iab.org, ietf@ietf.org, iaoc@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, 20 Jul 2012 15:55:46 -0000

On 7/20/2012 7:25 AM, Richard L. Barnes wrote:
> We have the technology.  Surely a CMS signed object (or even just an HTTPS download) would provide adequate authentication that it came from the IETF.  And it doesn't seem like we would have a problem providing authenticated documents to the world.


Do you know that these are acceptable to most/all courts?

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From iad@ietf.org  Fri Jul 20 09:06:26 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 8F1E621F85A4; Fri, 20 Jul 2012 09:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I0NF9I37cy6P; Fri, 20 Jul 2012 09:06:25 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5429521F857D; Fri, 20 Jul 2012 09:06:24 -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 95 Date Change
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
Date: Fri, 20 Jul 2012 09:06:24 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 16:06:26 -0000

The IAOC is seeking community feedback on a proposed date change for IETF 95
scheduled for March 2016.

Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is E=
aster.

The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and wou=
ld like =

feedback on those dates before making a decision.  Comments appreciated to =
ietf@ietf.org =

by 6 August 2012.

Ray Pelletier
IETF Administrative Director

From alexandru.petrescu@gmail.com  Fri Jul 20 09:27:12 2012
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DC8D21F855F for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 09:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.158
X-Spam-Level: 
X-Spam-Status: No, score=-9.158 tagged_above=-999 required=5 tests=[AWL=1.091,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lnkZf+PDxbD0 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 09:27:11 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) by ietfa.amsl.com (Postfix) with ESMTP id 108DC21F8617 for <ietf@ietf.org>; Fri, 20 Jul 2012 09:27:10 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id q6KGS6ei021315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 20 Jul 2012 18:28:06 +0200
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id q6KGS6iB016853 for <ietf@ietf.org>; Fri, 20 Jul 2012 18:28:06 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id q6KGS2qH025531 for <ietf@ietf.org>; Fri, 20 Jul 2012 18:28:06 +0200
Message-ID: <50098712.6070304@gmail.com>
Date: Fri, 20 Jul 2012 18:28:02 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed IETF 95 Date Change
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
In-Reply-To: <20120720160624.12163.25321.idtracker@ietfa.amsl.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, 20 Jul 2012 16:27:12 -0000

What a perspective refresher - March 2016!

My projects end 2013.  Those which have not yet started end 2015.

2015 is the deadline for fire detectors being mandatory in EU.

2018 - maybe a new metro line near where I live, but not known 
underground or above.

2016 new presidential elections here, but the precise date may not be set.

2016 is really far away.

Easter - there is almost always a multiple week difference between 
Catholic and Orthodox.

Yours,

Alex

Le 20/07/2012 18:06, IETF Administrative Director a Ã©crit :
> The IAOC is seeking community feedback on a proposed date change for IETF 95
> scheduled for March 2016.
>
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is Easter.
>
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and would like
> feedback on those dates before making a decision.  Comments appreciated to ietf@ietf.org
> by 6 August 2012.
>
> Ray Pelletier
> IETF Administrative Director
>
>



From joelja@bogus.com  Fri Jul 20 09:35:28 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 84D9321F84C9; Fri, 20 Jul 2012 09:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.375
X-Spam-Level: 
X-Spam-Status: No, score=-102.375 tagged_above=-999 required=5 tests=[AWL=0.224, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s91qL9eIDar2; Fri, 20 Jul 2012 09:35:28 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9F721F855E; Fri, 20 Jul 2012 09:35:28 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q6KGaNSI048081 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 20 Jul 2012 16:36:24 GMT (envelope-from joelja@bogus.com)
Message-ID: <50098901.7090009@bogus.com>
Date: Fri, 20 Jul 2012 09:36:17 -0700
From: Joel jaeggli <joelja@bogus.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 Administrative Director <iad@ietf.org>
Subject: Re: Proposed IETF 95 Date Change
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
In-Reply-To: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
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, 20 Jul 2012 16:36:24 +0000 (UTC)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 16:35:28 -0000

On 7/20/12 09:06 , IETF Administrative Director wrote:
> The IAOC is seeking community feedback on a proposed date change for IETF 95
> scheduled for March 2016.
> 
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is Easter.
> 
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and would like 
> feedback on those dates before making a decision.  Comments appreciated to ietf@ietf.org 
> by 6 August 2012.

20 march is palm sunday on the western calender.

If one's a conflict presumably the other is too...

> Ray Pelletier
> IETF Administrative Director
> 


From rbarnes@bbn.com  Fri Jul 20 09:39:56 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 59F1221F858E; Fri, 20 Jul 2012 09:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level: 
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bok80T1bdDRa; Fri, 20 Jul 2012 09:39:55 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 1740121F8555; Fri, 20 Jul 2012 09:39:55 -0700 (PDT)
Received: from ros-dhcp192-1-51-20.bbn.com ([192.1.51.20]:50094) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SsGFu-000E81-5l; Fri, 20 Jul 2012 12:40:42 -0400
Subject: Re: Feedback Requested on Draft Fees Policy
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <50097FAE.9060805@dcrocker.net>
Date: Fri, 20 Jul 2012 12:40:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FEE0CA44-A470-434A-9F25-88089411D0A6@bbn.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com> <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com> <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu> <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.com> <50097FAE.9060805@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1278)
Cc: wgchairs@ietf.org, iab@iab.org, ietf@ietf.org, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 16:39:56 -0000

On Jul 20, 2012, at 11:56 AM, Dave Crocker wrote:

> On 7/20/2012 7:25 AM, Richard L. Barnes wrote:
>> We have the technology.  Surely a CMS signed object (or even just an =
HTTPS download) would provide adequate authentication that it came from =
the IETF.  And it doesn't seem like we would have a problem providing =
authenticated documents to the world.
>=20
>=20
> Do you know that these are acceptable to most/all courts?
>=20
> d/


IANAL, so no.  But what else are we going to provide that's better?

--Richard


From fred@cisco.com  Fri Jul 20 10:28:47 2012
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBCE421F855E; Fri, 20 Jul 2012 10:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.485
X-Spam-Level: 
X-Spam-Status: No, score=-110.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kXYCIF8FkKEz; Fri, 20 Jul 2012 10:28:47 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 3478421F8557; Fri, 20 Jul 2012 10:28:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1069; q=dns/txt; s=iport; t=1342805384; x=1344014984; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=x754zcRlxpV+uc1rOl3s6GiycMJgtPDSMt6va2mhG68=; b=BGPoByu2K4FFXhVOE8ozKZjWOTxhd84YoCKwzrPt9BR4kSG4gB9y0GKW EY5+Dv/dvanJv2BCrrNcy1ZkGa23Z7lbbx5dXPgyDHjwTM/3p1tKr5CLm V6VWutdp6ZFAHOF0ZGaTtqLbegvTkAgsKjT8P8XBEwvpK76uHnKClucGG s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAKGUCVCtJXG//2dsb2JhbABFuUSBB4IgAQEBAwESASc/BQsCAQgYHhAyJQIEDgUUDodlBp5qoCSLToYAYAOVRY4kgWaCXw
X-IronPort-AV: E=Sophos;i="4.77,623,1336348800"; d="scan'208";a="103881861"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-8.cisco.com with ESMTP; 20 Jul 2012 17:29:43 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id q6KHThkD007032 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 20 Jul 2012 17:29:43 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.118]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0298.004; Fri, 20 Jul 2012 12:29:43 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: IETF Administrative Director <iad@ietf.org>
Subject: Re: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: AQHNZpGgHPezWzUAEUOyzRfpu5Ugb5cyskCAgAAO6gA=
Date: Fri, 20 Jul 2012 17:29:37 +0000
Message-ID: <D7593A6A-41F7-4004-9249-FBBA5030D1C4@cisco.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098901.7090009@bogus.com>
In-Reply-To: <50098901.7090009@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.32.244.221]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19052.005
x-tm-as-result: No--44.408800-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: <D039A9848B2C4F459BD1C6118F5D5DB5@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iaoc@ietf.org" <iaoc@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, 20 Jul 2012 17:28:48 -0000

On Jul 20, 2012, at 9:36 AM, Joel jaeggli wrote:

> On 7/20/12 09:06 , IETF Administrative Director wrote:
>> The IAOC is seeking community feedback on a proposed date change for IET=
F 95
>> scheduled for March 2016.
>>=20
>> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March i=
s Easter.
>>=20
>> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and =
would like=20
>> feedback on those dates before making a decision.  Comments appreciated =
to ietf@ietf.org=20
>> by 6 August 2012.
>=20
> 20 march is palm sunday on the western calender.
>=20
> If one's a conflict presumably the other is too...

I personally avoid being away from home on Easter, and would prefer that th=
e IETF meeting avoid it.

Yes, Palm Sunday is a question, but not quite on the same scale as Easter. =
I will note, however, that Good Friday (the Friday before Easter) is a nati=
onal holiday in a number of countries. People schedule vacations around tha=
t weekend.

My suggestion: take the week of April 3 or later.=

From lixia@cs.ucla.edu  Fri Jul 20 10:40:48 2012
Return-Path: <lixia@cs.ucla.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 A4BE021F8637; Fri, 20 Jul 2012 10:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3fsITZxTy4KS; Fri, 20 Jul 2012 10:40:47 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id EC5F621F85D3; Fri, 20 Jul 2012 10:40:46 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 6F74C39E800B; Fri, 20 Jul 2012 10:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RvY5FXTbaaeR; Fri, 20 Jul 2012 10:41:42 -0700 (PDT)
Received: from cs-211-24.cs.ucla.edu (Cs-211-24.CS.UCLA.EDU [131.179.211.24]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id A950739E8008; Fri, 20 Jul 2012 10:41:42 -0700 (PDT)
Subject: Re: Proposed IETF 95 Date Change
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
Date: Fri, 20 Jul 2012 10:41:43 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E14BAB4D-5F34-4800-A660-29026D225EB5@cs.ucla.edu>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
To: IETF Administrative Director <iad@ietf.org>
X-Mailer: Apple Mail (2.1278)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 17:40:48 -0000

On Jul 20, 2012, at 9:06 AM, IETF Administrative Director wrote:

> The IAOC is seeking community feedback on a proposed date change for =
IETF 95
> scheduled for March 2016.
>=20
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March =
is Easter.
>=20
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 =
and would like=20
> feedback on those dates before making a decision.  Comments =
appreciated to ietf@ietf.org=20
> by 6 August 2012.
>=20
> Ray Pelletier
> IETF Administrative Director

2016 is far away but UCLA has calendars that far out ;)
The new dates (20 - 25 March 2016) are much better, that is our spring =
break week.
Our spring 2016 teaching starts Monday 3/28/2016 (for all UC campuses =
except Berkeley, and perhaps other schools running quarter system), =
making it almost impossible to travel.

Lixia=20=

From agmalis@gmail.com  Fri Jul 20 10:43:47 2012
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5677E21F8630; Fri, 20 Jul 2012 10:43:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level: 
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[AWL=0.452,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozNQ6zu3TCds; Fri, 20 Jul 2012 10:43:46 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 85C5821F85E3; Fri, 20 Jul 2012 10:43:46 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so4653723ggn.31 for <multiple recipients>; Fri, 20 Jul 2012 10:44:42 -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=uIuWBLx7OkbZIUQ97LikouzruyqHRnniuXekoEEyWdU=; b=QULlTw2dRNTOsIsDJn6eqSenviMxf+Qk4nAEiSk8x5rDBREZe52WDdlCPFPRJaidkA DZMM0l791HRe3U8hF9aB8Bne4EVVh2trDQmQvnxfr3/iYLKrr03uX92dZ+X3f//V1+Hs koH97TULe0qmg1Kda/lBwuLe5JqYwZRRd9k0NMKAduFpCoUhxJgFW3xJEdPpYVAjcfOP amBTHe0p085RbC5XoWIMkgzYWMcWvJk+asIgOJKv05SiHM57cDNvAbmL1KD3bg3TfQ2u pQG8ZJ3PZTkYPmvy8SO21xXvp0RSwr90zYI7Ousbzyz21xnu+3LGa1415gi9Em8Y7wqS /+Mw==
Received: by 10.50.158.129 with SMTP id wu1mr5149004igb.33.1342806282410; Fri, 20 Jul 2012 10:44:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.90.229 with HTTP; Fri, 20 Jul 2012 10:44:21 -0700 (PDT)
In-Reply-To: <D7593A6A-41F7-4004-9249-FBBA5030D1C4@cisco.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098901.7090009@bogus.com> <D7593A6A-41F7-4004-9249-FBBA5030D1C4@cisco.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 20 Jul 2012 13:44:21 -0400
Message-ID: <CAA=duU0XK=gJJzS-7gDGP_NQz=dPxvR4G_xRUnPHNoa537YrxQ@mail.gmail.com>
Subject: Re: Proposed IETF 95 Date Change
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iaoc@ietf.org" <iaoc@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, 20 Jul 2012 17:43:47 -0000

As long as you don't go any later than the week of April 10 - the week
of April 17 runs into the start of Passover.

Thanks,
Andy

On Fri, Jul 20, 2012 at 1:29 PM, Fred Baker (fred) <fred@cisco.com> wrote:
>
> On Jul 20, 2012, at 9:36 AM, Joel jaeggli wrote:
>
>> On 7/20/12 09:06 , IETF Administrative Director wrote:
>>> The IAOC is seeking community feedback on a proposed date change for IETF 95
>>> scheduled for March 2016.
>>>
>>> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is Easter.
>>>
>>> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and would like
>>> feedback on those dates before making a decision.  Comments appreciated to ietf@ietf.org
>>> by 6 August 2012.
>>
>> 20 march is palm sunday on the western calender.
>>
>> If one's a conflict presumably the other is too...
>
> I personally avoid being away from home on Easter, and would prefer that the IETF meeting avoid it.
>
> Yes, Palm Sunday is a question, but not quite on the same scale as Easter. I will note, however, that Good Friday (the Friday before Easter) is a national holiday in a number of countries. People schedule vacations around that weekend.
>
> My suggestion: take the week of April 3 or later.

From bob.hinden@gmail.com  Fri Jul 20 10:52:37 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 BCA5011E8088; Fri, 20 Jul 2012 10:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.514
X-Spam-Level: 
X-Spam-Status: No, score=-103.514 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ubcpFc-QzQft; Fri, 20 Jul 2012 10:52:37 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id B7BF721F867E; Fri, 20 Jul 2012 10:52:36 -0700 (PDT)
Received: by wibhq12 with SMTP id hq12so773276wib.1 for <multiple recipients>; Fri, 20 Jul 2012 10:53:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=ut51MmnumkpjnvZvjWl9gV7t+OGEOB429NijOlkApnc=; b=Nd2OqG11XDP1AbbaejJYRcnKgiGm/0vN77teyt4IYFzp++sT7FKbx7wY5/Ox8mPaCN HqzjuYz7VRGt2J+35p4WJ1cmf90xdwePJxkNVXlhB8vlXeMng0T4iYOaCEJaFUGHQZHx 4wqyA1F60ZOaw6ruGMi5Xitu4W/oUTNXiK1wglPPvPBP7mqlcGnQrBOaeZA9lQdSYqQ/ UBQlcHJW/BkrrIctohxENWCJjIDMZTTkSQB+HPHnDln+m6wMv+btWNYRu0ACwAPcqxR1 6uWuXnIf+hiPm9Ss5iVFR/gr4JK5Cu5SMdd08gESQddyPy8uJ38HphDV20q6QLGUSswN GXrw==
Received: by 10.216.255.68 with SMTP id i46mr740877wes.35.1342806812449; Fri, 20 Jul 2012 10:53:32 -0700 (PDT)
Received: from ?IPv6:2601:9:4080:10:21e:c2ff:febb:8dfb? ([2601:9:4080:10:21e:c2ff:febb:8dfb]) by mx.google.com with ESMTPS id g46sm16142186eep.15.2012.07.20.10.53.30 (version=SSLv3 cipher=OTHER); Fri, 20 Jul 2012 10:53:31 -0700 (PDT)
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <FEE0CA44-A470-434A-9F25-88089411D0A6@bbn.com>
Date: Fri, 20 Jul 2012 10:53:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F47AEC1A-E11F-45C2-9371-61B4A52FBA9D@gmail.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com> <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com> <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu> <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.com> <50097FAE.9060805@dcrocker.net> <FEE0CA44-A470-434A-9F25-88089411D0A6@bbn.com>
To: Richard L. Barnes <rbarnes@bbn.com>
X-Mailer: Apple Mail (2.1084)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, iab@iab.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: Fri, 20 Jul 2012 17:52:37 -0000

Richard,

On Jul 20, 2012, at 9:40 AM, Richard L. Barnes wrote:

>=20
> On Jul 20, 2012, at 11:56 AM, Dave Crocker wrote:
>=20
>> On 7/20/2012 7:25 AM, Richard L. Barnes wrote:
>>> We have the technology.  Surely a CMS signed object (or even just an =
HTTPS download) would provide adequate authentication that it came from =
the IETF.  And it doesn't seem like we would have a problem providing =
authenticated documents to the world.
>>=20
>>=20
>> Do you know that these are acceptable to most/all courts?
>>=20
>> d/
>=20
>=20
> IANAL, so no.  But what else are we going to provide that's better?
>=20

We are doing things like signing internet-drafts and RFCs to make this =
possible, but it will be a long while before the courts catch up.  They =
are not exactly early adopters of things like this :-)

Bob


From rbarnes@bbn.com  Fri Jul 20 10:57:58 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 4EFE021F8681; Fri, 20 Jul 2012 10:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level: 
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8nFXmQkJwacI; Fri, 20 Jul 2012 10:57:57 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 8425021F8616; Fri, 20 Jul 2012 10:57:56 -0700 (PDT)
Received: from ros-dhcp192-1-51-20.bbn.com ([192.1.51.20]:50583) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1SsHTM-000OGD-20; Fri, 20 Jul 2012 13:58:40 -0400
Subject: Re: Proposed IETF 95 Date Change
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <CAA=duU0XK=gJJzS-7gDGP_NQz=dPxvR4G_xRUnPHNoa537YrxQ@mail.gmail.com>
Date: Fri, 20 Jul 2012 13:58:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <31E58CB3-05F6-4E74-ABD3-C87BB2662897@bbn.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098901.7090009@bogus.com> <D7593A6A-41F7-4004-9249-FBBA5030D1C4@cisco.com> <CAA=duU0XK=gJJzS-7gDGP_NQz=dPxvR4G_xRUnPHNoa537YrxQ@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: "iaoc@ietf.org" <iaoc@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, 20 Jul 2012 17:57:58 -0000

For convenience, the complete list:
<http://www.interfaithcalendar.org/2016.htm>


On Jul 20, 2012, at 1:44 PM, Andrew G. Malis wrote:

> As long as you don't go any later than the week of April 10 - the week
> of April 17 runs into the start of Passover.
>=20
> Thanks,
> Andy
>=20
> On Fri, Jul 20, 2012 at 1:29 PM, Fred Baker (fred) <fred@cisco.com> =
wrote:
>>=20
>> On Jul 20, 2012, at 9:36 AM, Joel jaeggli wrote:
>>=20
>>> On 7/20/12 09:06 , IETF Administrative Director wrote:
>>>> The IAOC is seeking community feedback on a proposed date change =
for IETF 95
>>>> scheduled for March 2016.
>>>>=20
>>>> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 =
March is Easter.
>>>>=20
>>>> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 =
and would like
>>>> feedback on those dates before making a decision.  Comments =
appreciated to ietf@ietf.org
>>>> by 6 August 2012.
>>>=20
>>> 20 march is palm sunday on the western calender.
>>>=20
>>> If one's a conflict presumably the other is too...
>>=20
>> I personally avoid being away from home on Easter, and would prefer =
that the IETF meeting avoid it.
>>=20
>> Yes, Palm Sunday is a question, but not quite on the same scale as =
Easter. I will note, however, that Good Friday (the Friday before =
Easter) is a national holiday in a number of countries. People schedule =
vacations around that weekend.
>>=20
>> My suggestion: take the week of April 3 or later.


From sarikaya2012@gmail.com  Fri Jul 20 11:36:21 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DEFA11E807F; Fri, 20 Jul 2012 11:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level: 
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XCUT0C+XyzX; Fri, 20 Jul 2012 11:36:20 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4E69411E8073; Fri, 20 Jul 2012 11:36:20 -0700 (PDT)
Received: by yenq13 with SMTP id q13so4706354yen.31 for <multiple recipients>; Fri, 20 Jul 2012 11:37:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=+aF9cE5YH5i/p4BHx7UlDylYuiswVa6Vwxpra1b69D8=; b=xT5yiB4MIrRwCpl1z/Rh7VEzEz/dxmUz7daKI/iw7JHFz2znP0hVjlXbpeTGLImBzW OsEfHQ5qujpVRMPpugXDeHSppHvqHgUGmSvj1epfHdVjClOp7iygSChZguXrCb5WmVey QiKkDpGQvvDgLMhRy3Np2nSRAWHSDb9pgSpp7vvaHpBW7nppsmMXb8n3Jjpsadw61ECH Ysht2Uq5F7AUaqlMdxdMmHy9Mi21Z2vYLJMkK93j+Ma3mlC95SRtlktBsNqFXr2p2qmK ofC3sN0cy9o9MPntjtbkthMSRyeUsAeb66KKPDRXAcbiqHxQME9SXpP2WpzafegGHCJl H8ZQ==
MIME-Version: 1.0
Received: by 10.50.6.229 with SMTP id e5mr5319566iga.9.1342809436421; Fri, 20 Jul 2012 11:37:16 -0700 (PDT)
Received: by 10.231.207.167 with HTTP; Fri, 20 Jul 2012 11:37:16 -0700 (PDT)
In-Reply-To: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
Date: Fri, 20 Jul 2012 13:37:16 -0500
Message-ID: <CAC8QAce9Gd8GkViAfukZQSQXfOm5tZsXgDTkRt_PDNOAGUSG0Q@mail.gmail.com>
Subject: Re: Proposed IETF 95 Date Change
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: IETF Administrative Director <iad@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.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: Fri, 20 Jul 2012 18:36:21 -0000

I don't understand why this issue is coming up.
Maybe you don't know, IETF 84 falls in the month of Ramadan for
Muslims and nobody asked to change it?

My 2 cents.

Behcet

On Fri, Jul 20, 2012 at 11:06 AM, IETF Administrative Director
<iad@ietf.org> wrote:
> The IAOC is seeking community feedback on a proposed date change for IETF 95
> scheduled for March 2016.
>
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is Easter.
>
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and would like
> feedback on those dates before making a decision.  Comments appreciated to ietf@ietf.org
> by 6 August 2012.
>
> Ray Pelletier
> IETF Administrative Director

From marshall.eubanks@gmail.com  Fri Jul 20 11:44:31 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB62211E80BD; Fri, 20 Jul 2012 11:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MQAPLxRdTfDo; Fri, 20 Jul 2012 11:44:31 -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 E049711E807F; Fri, 20 Jul 2012 11:44:29 -0700 (PDT)
Received: by bkty7 with SMTP id y7so3511183bkt.31 for <multiple recipients>; Fri, 20 Jul 2012 11:45:25 -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:content-transfer-encoding; bh=ycytE1loYRuQpsYgQfER3x77rLrWpg2/ub7uEB52t/I=; b=XCZrLQFDnUPE4jDqL1rVfVr3nZlDWrFwsQCpld4z++iMgJG0Qt/RDekbNM0Q+aUYYT 5YCC4wuCgWyj3x9nPIU8jSL6ob5uHHWAG+xydriiJ9UlnoYOF+pPfXWymCvTE5G6d2x6 o2EjdveZDb0Fb+cMhl+x6fZjt5olpc9brgGMWXULy0uMFnm4+fUw42olgYJYutXSnHWl 1JIO7R1YxMtR6ebpZdSGplAcvYC8eXSK7Kv8sFOSRY7UQdphtQzNbQvF9PwWKTLsTvmH fGU+dqSklCSeAIWONJQSARYMi5Yt9xKs1gaNu6za6XJrxcSuAnlhgMA22Gf5dbEG1DQF zMVw==
MIME-Version: 1.0
Received: by 10.204.152.136 with SMTP id g8mr3571991bkw.44.1342809925649; Fri, 20 Jul 2012 11:45:25 -0700 (PDT)
Received: by 10.205.119.137 with HTTP; Fri, 20 Jul 2012 11:45:25 -0700 (PDT)
In-Reply-To: <006801cd667a$d10b89d0$c801a8c0@computer>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <006801cd667a$d10b89d0$c801a8c0@computer>
Date: Fri, 20 Jul 2012 14:45:25 -0400
Message-ID: <CAJNg7V+GrzOcLKkHcVkxy07pjgvBjFuO8HOsyTSNQYjs-uoJ1A@mail.gmail.com>
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Jiankang Yao <yaojk@cnnic.cn>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 18:44:32 -0000

On Fri, Jul 20, 2012 at 9:23 AM, Jiankang Yao <yaojk@cnnic.cn> wrote:
>
>
> I have taken a look at this policy. but still not very clear about this
> policy.
>
> could you kindly show some  examples for charging the fee?
>
>

I looked at this before the policy was created.

Many internet companies do this.

Yahoo :
http://cryptome.org/isp-spy/yahoo-spy.pdf
=95	Basic subscriber records: approx. $20 for the first ID, $10 per ID ther=
eafter
 =95	Basic Group Information (including information about moderators):
approx. $20 for a group with a single moderator
=95	Contents of subscriber accounts, including email: approx. $30-$40
per user =95	Contents of Groups: approx. $40 - $80 per group

Verizon :
http://www.verizon.net/policies/civil_subpoena.asp

Verizon Online charges the following rates for compliance with civil
subpoenas and other legal process. For subpoenas and other legal
process that require substantial effort by Verizon Online, Verizon
Online reserves the right to charge a rate of $75 per hour (plus
overtime costs if necessary) and to collect an estimated fee in
advance. Except as set forth in the preceding sentence, Verizon
Online's subpoena compliance fees and charges are as follows:

$40.00 per IP record requested (unless overtime charges apply)
$22.00 per Federal Express or actual shipping charges if higher
$0.25 cents per copy

Sprint
http://info.publicintelligence.net/SprintSubpoenaManual.pdf

Lots of different fees. Minimum $50.00 administrative processing fee
for Civil requests.

AT&T
https://contact.bellsouth.com/subpoena/
Fees for Subpoena Processing: AT&T charges a fee for the processing of
civil subpoenas.

I do not think that the fees suggested here are at all out of line
with either the actual burden or with what other organizations do.

Regards
Marshall


>
> Jiankang Yao
>
> ----- 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>
> Sent: Friday, July 20, 2012 9:07 PM
> Subject: Feedback Requested on Draft Fees Policy
>
>
>
> The IAOC is seeking community feedback on a proposed policy by the IAOC t=
o
> impose
> fees to produce information and authenticate documents in response to
> subpoenas and
> other legal requests.
>
> The IETF receives requests for information, documentation, authentication=
 or
> other
> matters through subpoenas and less formal means that require manpower and
> materials
> to be expended.  These requests are on the rise. During the period 2005 t=
o
> 2010 the IETF
> responded to nine subpoenas.  Since 2011 the IETF has received five
> subpoenas and three
> other legal requests for authenticated documents.
>
> Each such request is time sensitive and involves the IETF Counsel, the IA=
D,
> and members
> of the IAOC, who together form the Legal Management Committee, to rapidly
> analyze and
> identify the means for satisfying the request.  Often there is a need to
> retain outside counsel,
> especially in cases that might lead to depositions or court testimony.
>
> The IAOC believes a Schedule of Fees is an appropriate and reasonable mea=
ns
> to recover
> costs associated with such efforts.
>
> The draft policy entitled Draft Fee Policy for Legal Requests can be foun=
d
> at: <http://iaoc.ietf.org/policyandprocedures.html>
>
> Before adopting a policy the IAOC would like feedback on this before maki=
ng
> a
> decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.
>
> Ray Pelletier
> IETF Administrative Director
>

From ietfdbh@comcast.net  Thu Jul 19 09:23:31 2012
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8BF21F85E3 for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 09:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.518
X-Spam-Level: 
X-Spam-Status: No, score=-101.518 tagged_above=-999 required=5 tests=[AWL=1.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SmH1i6QM7kr6 for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 09:23:30 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by ietfa.amsl.com (Postfix) with ESMTP id 37BEE21F85D8 for <ietf@ietf.org>; Thu, 19 Jul 2012 09:23:30 -0700 (PDT)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by QMTA11.westchester.pa.mail.comcast.net with comcast id cFqK1j0040mv7h05BGQSWV; Thu, 19 Jul 2012 16:24:26 +0000
Received: from [192.168.1.67] ([184.39.8.144]) by omta11.westchester.pa.mail.comcast.net with comcast id cGQ71j00b36TH603XGQAU1; Thu, 19 Jul 2012 16:24:19 +0000
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Thu, 19 Jul 2012 12:24:08 -0400
Subject: Re: [BEHAVE] Fwd: Re: Martin Stiemerling's Discuss on draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
From: David Harrington <ietfdbh@comcast.net>
To: "behave@ietf.org" <behave@ietf.org>
Message-ID: <CC2D8284.23C3C%ietfdbh@comcast.net>
Thread-Topic: [BEHAVE] Fwd: Re: Martin Stiemerling's Discuss on draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
In-Reply-To: <500802CB.5010908@viagenie.ca>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:06 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 16:23:31 -0000

Hi,

(I restricted this response to behave wg, since that is where
lsn-requirements is chartered, not pcp wg; I added ietf@ietf.org since
this is about a DISCUSS relating to ietf consensus).

I think we should mandate something if interoperability will break if it
is not done.
But if the port-control aspect can be achieved using proprietary protocols
with no impact on cgn operations, then a specific protocol should not be
mandated.

-- REQUIREMENTS for COMPLIANCE --

I frequently refer to the logic in the "Strong Security" BCP (RFC3365),
which makes a distinction between what MUST be implemented in a compliant
implementation, and what SHOULD be used by operators for interoperability
between network elements.
If an operator wants to set up a lsn-requirements-compliant CGN in a
multi-vendor environment, will it be problematic if vendor A uses A-style
port control, vendor B uses B-style port control, vendor C uses PCP,
vendor D uses MIDCOM-MIB, and vendor E uses Diameter NAT control?
If so, then there would seem to be justification to specify that **to be
compliant to the IETF lsn-requirements standard/BCP/InformationalRFC
recommendation** PCP MUST be implemented, so it is AVAILABLE if an
operator chooses to use it. If implementers don't implement it in product,
it won't be there for operators to use to achieve interoperability. Of
course, a similar argument might justify also requiring implementation of
Diameter NAT control and the MIDCOM-MIB.

Do we want to require one specific standard as THE solution required to be
compliant to this lsn-requirements standard, or do we want to provide a
toolkit of multiple must-implement standards plus advice about how to
combine them, and a deployer gets to choose which to use together, or do
we want to specify a toolkit of implementation-optional standards that
might be available and a deployer needs to figure out how to make the
available options work together?

Requiring PCP for compliance does not mean a vendor is required to
implement PCP, any more than a vendor is required to implement BGP, but if
a vendor claims to be BGP compliant, then there are aspects of BGP, or
other standards that BGP relies upon being present, that MUST be there. If
an implementer wants to claim compliance to the NAT-MIB, they MUST also
implement ifIndex (and presumably SNMP to access the MIB).
If a vendor claims to be compliant to the lsn-requirements standard (or
BCP or Informational RFCXXXX) then they MUST implement those aspects that
are required for compliance.

Now, in the security world, where security is a system-wide process, if
using multiple algorithms can create hard-to-detect security holes, there
is strong justification for REQUIRING specific protocols be used across
devices/vendors to avoid introducing such holes into the system. And, in
the security world, there is a whole community of attackers looking for
those holes so they can take advantage of such weaknesses in the overall
security system.

If CGN interoperability is not significantly impacted by having multiple
types of port forwarding or other middlebox algorithms rather than a
single algorithm, other than extra work for operators, then we probably
should not REQUIRE, but simply RECOMMEND a standards-based solution such
as PCP. We should NOT require it just because we want to see vendors use
our protocols; that is a market-driven decision to be made by vendors
based on customer demand.

--
David Harrington
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





On 7/19/12 8:51 AM, "Simon Perreault" <simon.perreault@viagenie.ca> wrote:

>Behaviers, PCPers,
>
>During IESG review of draft-ietf-behave-lsn-requirements, a DISCUSS was
>filed regarding the PCP requirement. Details below.
>
>I think this DISCUSS needs to be discussed. So please discuss.
>
>Please reply to behave@ietf.org.
>
>Thanks,
>Simon
>
>
>-------- Message original --------
>Sujet: Re: Martin Stiemerling's Discuss on
>draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
>Date : Thu, 19 Jul 2012 10:46:42 +0200
>De : Martin Stiemerling <martin.stiemerling@neclab.eu>
>Pour : Simon Perreault <simon.perreault@viagenie.ca>
>Copie =E0 : The IESG <iesg@ietf.org>, <behave-chairs@tools.ietf.org>,
><draft-ietf-behave-lsn-requirements@tools.ietf.org>
>
>Hi Simon, all,
>
>On 07/17/2012 11:11 PM, Simon Perreault wrote:
>> Le 2012-07-17 16:42, Martin Stiemerling a =E9crit :
>>>> Each and every CGN MUST have PCP and MUST follow the constraints. I'll
>>>> fix the text in a later revision.
>>>
>>> Can we mandate a specific protocol to be used for this or can we only
>>> mandate that such a type of protocol is being used? I don't see the
>>>IETF
>>> in the position to mandate this type of protocol for CGNs.
>>>
>>> There are other protocols out there which might be suitable. Note that
>>>I
>>> am co-author of some, but this isn't the reason for the question. I do
>>> not get any reward if I promote these protocols.
>>>
>>> It is more:
>>> do we need to constrain CGN deployments to a protocol (PCP) which is
>>> developed right now, or are we open to existing or future protocols, or
>>> whatever folks deploying this deem right?
>>>
>>> I would propose to change REQ-9 to :
>>> REQ-9: A CGN MUST include a middlebox control protocol that allows
>>> manipulation of CGN bindings with the following contstraints <list
>>>items
>>> A and B>
>>> REQ-9a: If PCP is used these contstraints MUST be applied in addition
>>>to
>>> contraints A and B:
>>> <list items C and D>
>>
>> That was discussed in IETF 81 (Qu=E9bec). Here's the extract from the
>> minutes:
>>
>>            Stuart Cheshire: ietf has one port forwarding protocol, which
>>            is PCP, so we should require it by name
>
>There are multiple middlebox control protocols published by the IETF
>(standards track and experimental) and I have not seen any call for
>consensus on what **the** IETF's middlebox control is, neither I have
>seen any RFC that states this.
>
>I do not see that an individual can declare IETF consensus based on his
>own opinion.
>
>
>>
>>            Dave Thaler: I agree. PCP doc is in final stages.
>
>Again, an opinion of an individual. Nothing wrong about it, but it does
>not state IETF consensus.
>
>>
>> There was consensus from the WG. In consequence, the text was changed
>> from this (-02):
>>
>>              A CGN SHOULD support a port forwarding protocol such as the
>>              Port Control Protocol [I-D.ietf-pcp-base].
>>
>> to this (-03):
>>
>>             A CGN SHOULD include a Port Control Protocol server
>>             [I-D.ietf-pcp-base].
>>
>> (That requirement later became a MUST, but that's orthogonal to what
>> protocol we require.)
>
>I do not see that the IETF can mandate what protocols are being used to
>control a device. The market will decide!
>
>For instance, the is no MUST required that routers implement BGP. It is
>good to do this, but if one decides to go for IS-IS (or whatever) that
>is just fine.
>
>Another example, there is also no MUST requirement that routers, or
>hosts in general, have to implement SNMP.
>
>However, I can see the immediate need to mandate that a CGN SHOULD/MUST
>support a middlebox control protocol that is able to install and
>maintain NAT bindings.
>
>   Martin
>
>--=20
>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
>
>
>_______________________________________________
>Behave mailing list
>Behave@ietf.org
>https://www.ietf.org/mailman/listinfo/behave



From ietfdbh@comcast.net  Thu Jul 19 09:37:29 2012
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 979EC21F87DB for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 09:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.329
X-Spam-Level: 
X-Spam-Status: No, score=-102.329 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7p4WJ41Zg1q0 for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 09:37:28 -0700 (PDT)
Received: from qmta02.emeryville.ca.mail.comcast.net (qmta02.emeryville.ca.mail.comcast.net [76.96.30.24]) by ietfa.amsl.com (Postfix) with ESMTP id DEEBC21F87B1 for <ietf@ietf.org>; Thu, 19 Jul 2012 09:37:27 -0700 (PDT)
Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta02.emeryville.ca.mail.comcast.net with comcast id cFt81j0050lTkoCA2GeHSh; Thu, 19 Jul 2012 16:38:17 +0000
Received: from [192.168.1.67] ([184.39.8.144]) by omta04.emeryville.ca.mail.comcast.net with comcast id cGdv1j00W36TH608QGdzdk; Thu, 19 Jul 2012 16:38:15 +0000
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Thu, 19 Jul 2012 12:37:55 -0400
Subject: draft-ietf-behave-lsn-requirements - BCP, STD, AS, or Informational?
From: David Harrington <ietfdbh@comcast.net>
To: Simon Perreault <simon.perreault@viagenie.ca>, "behave@ietf.org" <behave@ietf.org>
Message-ID: <CC2DADE3.23DB0%ietfdbh@comcast.net>
Thread-Topic: draft-ietf-behave-lsn-requirements - BCP, STD, AS, or Informational?
In-Reply-To: <500802CB.5010908@viagenie.ca>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:06 -0700
Cc: iesg@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, 19 Jul 2012 16:37:29 -0000

-- BCP or not? --

As previously-responsible AD for behave, I have had serious concerns about
this document being published as a BCP.
=20

In another email, I discussed whether PCP should be required to be
compliant to this BCP.

I think the IETF needs to decide whether lsn-requirements is something to
be compliant to. The title and BCP status seem rather misleading, in my
opinion.=20
Following RFC3365, MUST is for implementers; SHOULD is for deployers. If
we want to require vendors to implement specific features in a manner
COMPLIANT to this specification, then this really should be a standard,
not a BCP.=20
If we want to standardize implementation behaviors, then I think this
should be an explicit standard, not some other type of RFC that will
implicitly be a standard but with possibly less scrutiny than an explicit
standard would generate.


A BCP often carries similar weight to a standard, and I question whether
some of these requirements are best CURRENT practice, especially if PCP is
a MUST. It might be best DESIRED practice, or best RECOMMENDED practice,
but I doubt some of these requirements are best CURRENT practice. If we
simply want to document what some existing deployments are doing, then I
think an Applicability statement or an Informational RFC might be more
appropriate than a BCP. I think this should be a BCP only if there is a
strong consensus that this is the way deployments SHOULD be done, based on
actual deployment experience by a variety of operators using current
implementations - that would represent best CURRENT practices.


--
David Harrington
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





On 7/19/12 8:51 AM, "Simon Perreault" <simon.perreault@viagenie.ca> wrote:

>Behaviers, PCPers,
>
>During IESG review of draft-ietf-behave-lsn-requirements, a DISCUSS was
>filed regarding the PCP requirement. Details below.
>
>I think this DISCUSS needs to be discussed. So please discuss.
>
>Please reply to behave@ietf.org.
>
>Thanks,
>Simon
>
>
>-------- Message original --------
>Sujet: Re: Martin Stiemerling's Discuss on
>draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
>Date : Thu, 19 Jul 2012 10:46:42 +0200
>De : Martin Stiemerling <martin.stiemerling@neclab.eu>
>Pour : Simon Perreault <simon.perreault@viagenie.ca>
>Copie =E0 : The IESG <iesg@ietf.org>, <behave-chairs@tools.ietf.org>,
><draft-ietf-behave-lsn-requirements@tools.ietf.org>
>
>Hi Simon, all,
>
>On 07/17/2012 11:11 PM, Simon Perreault wrote:
>> Le 2012-07-17 16:42, Martin Stiemerling a =E9crit :
>>>> Each and every CGN MUST have PCP and MUST follow the constraints. I'll
>>>> fix the text in a later revision.
>>>
>>> Can we mandate a specific protocol to be used for this or can we only
>>> mandate that such a type of protocol is being used? I don't see the
>>>IETF
>>> in the position to mandate this type of protocol for CGNs.
>>>
>>> There are other protocols out there which might be suitable. Note that
>>>I
>>> am co-author of some, but this isn't the reason for the question. I do
>>> not get any reward if I promote these protocols.
>>>
>>> It is more:
>>> do we need to constrain CGN deployments to a protocol (PCP) which is
>>> developed right now, or are we open to existing or future protocols, or
>>> whatever folks deploying this deem right?
>>>
>>> I would propose to change REQ-9 to :
>>> REQ-9: A CGN MUST include a middlebox control protocol that allows
>>> manipulation of CGN bindings with the following contstraints <list
>>>items
>>> A and B>
>>> REQ-9a: If PCP is used these contstraints MUST be applied in addition
>>>to
>>> contraints A and B:
>>> <list items C and D>
>>
>> That was discussed in IETF 81 (Qu=E9bec). Here's the extract from the
>> minutes:
>>
>>            Stuart Cheshire: ietf has one port forwarding protocol, which
>>            is PCP, so we should require it by name
>
>There are multiple middlebox control protocols published by the IETF
>(standards track and experimental) and I have not seen any call for
>consensus on what **the** IETF's middlebox control is, neither I have
>seen any RFC that states this.
>
>I do not see that an individual can declare IETF consensus based on his
>own opinion.
>
>
>>
>>            Dave Thaler: I agree. PCP doc is in final stages.
>
>Again, an opinion of an individual. Nothing wrong about it, but it does
>not state IETF consensus.
>
>>
>> There was consensus from the WG. In consequence, the text was changed
>> from this (-02):
>>
>>              A CGN SHOULD support a port forwarding protocol such as the
>>              Port Control Protocol [I-D.ietf-pcp-base].
>>
>> to this (-03):
>>
>>             A CGN SHOULD include a Port Control Protocol server
>>             [I-D.ietf-pcp-base].
>>
>> (That requirement later became a MUST, but that's orthogonal to what
>> protocol we require.)
>
>I do not see that the IETF can mandate what protocols are being used to
>control a device. The market will decide!
>
>For instance, the is no MUST required that routers implement BGP. It is
>good to do this, but if one decides to go for IS-IS (or whatever) that
>is just fine.
>
>Another example, there is also no MUST requirement that routers, or
>hosts in general, have to implement SNMP.
>
>However, I can see the immediate need to mandate that a CGN SHOULD/MUST
>support a middlebox control protocol that is able to install and
>maintain NAT bindings.
>
>   Martin
>
>--=20
>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
>
>
>_______________________________________________
>Behave mailing list
>Behave@ietf.org
>https://www.ietf.org/mailman/listinfo/behave



From repenno@cisco.com  Thu Jul 19 10:11:14 2012
Return-Path: <repenno@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 1C2B921F87E6; Thu, 19 Jul 2012 10:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HvBoPqc2ZqYP; Thu, 19 Jul 2012 10:11:13 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id A18F521F87E4; Thu, 19 Jul 2012 10:11:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6502; q=dns/txt; s=iport; t=1342717926; x=1343927526; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=oZ69sJQqJFnfkClb8r4rg//vVjz1GD/GyO2Clxf7454=; b=KNmLZwWGuEqSL4iaa/Bi4w0w4xS59JLQ2PhJwX9/39souRqaLdQfnp96 j8Mdv5Fe2dEXBqYICz1qws58TEVPLW2AAPpG8tlb74kWNP9kObo08/Xfz RuYcMG25J3iSwpqiZ7vs4H3T8PK83me9yRi76uftC4CYpSJyqFCw5XaW/ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EABI/CFCtJV2b/2dsb2JhbABCA7lEgQeCIAEBAQQBAQEPAQpKBwYFEgEIDgpVCxQRAgQBDQUih1wDDAueRJYsCIlPBItMFASDV4MhA4gYjSyOI4Fmgl+BVgk
X-IronPort-AV: E=Sophos;i="4.77,615,1336348800"; d="scan'208";a="100515019"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 19 Jul 2012 17:12:05 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q6JHC54I002461 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 19 Jul 2012 17:12:05 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.177]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0298.004; Thu, 19 Jul 2012 12:12:03 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: David Harrington <ietfdbh@comcast.net>, Simon Perreault <simon.perreault@viagenie.ca>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [BEHAVE] draft-ietf-behave-lsn-requirements - BCP, STD, AS, or Informational?
Thread-Topic: [BEHAVE] draft-ietf-behave-lsn-requirements - BCP, STD, AS, or Informational?
Thread-Index: AQHNZdGd4VOtsRAYKkSfWXI2h7Ii2A==
Date: Thu, 19 Jul 2012 17:12:03 +0000
Message-ID: <CC2D8D42.8068%repenno@cisco.com>
In-Reply-To: <CC2DADE3.23DB0%ietfdbh@comcast.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.21.88.205]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19050.003
x-tm-as-result: No--63.367400-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <54530AFEEBC48B4C87F761F8FFCAEA48@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:06 -0700
Cc: "iesg@ietf.org" <iesg@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, 19 Jul 2012 17:11:14 -0000

Good point, some data in this regards:

All previous behave RFCs that 'standardized' NAT behavior are BCPs
(RFC4787, 5508, etc).

And they are have lots of MUSTs


On 7/19/12 9:37 AM, "David Harrington" <ietfdbh@comcast.net> wrote:

>-- BCP or not? --
>
>As previously-responsible AD for behave, I have had serious concerns about
>this document being published as a BCP.
>=20
>
>In another email, I discussed whether PCP should be required to be
>compliant to this BCP.
>
>I think the IETF needs to decide whether lsn-requirements is something to
>be compliant to. The title and BCP status seem rather misleading, in my
>opinion.=20
>Following RFC3365, MUST is for implementers; SHOULD is for deployers. If
>we want to require vendors to implement specific features in a manner
>COMPLIANT to this specification, then this really should be a standard,
>not a BCP.=20
>If we want to standardize implementation behaviors, then I think this
>should be an explicit standard, not some other type of RFC that will
>implicitly be a standard but with possibly less scrutiny than an explicit
>standard would generate.
>
>
>A BCP often carries similar weight to a standard, and I question whether
>some of these requirements are best CURRENT practice, especially if PCP is
>a MUST. It might be best DESIRED practice, or best RECOMMENDED practice,
>but I doubt some of these requirements are best CURRENT practice. If we
>simply want to document what some existing deployments are doing, then I
>think an Applicability statement or an Informational RFC might be more
>appropriate than a BCP. I think this should be a BCP only if there is a
>strong consensus that this is the way deployments SHOULD be done, based on
>actual deployment experience by a variety of operators using current
>implementations - that would represent best CURRENT practices.
>
>
>--
>David Harrington
>Internet Engineering Task Force (IETF)
>Ietfdbh@comcast.net
>+1-603-828-1401
>
>
>
>
>
>On 7/19/12 8:51 AM, "Simon Perreault" <simon.perreault@viagenie.ca> wrote:
>
>>Behaviers, PCPers,
>>
>>During IESG review of draft-ietf-behave-lsn-requirements, a DISCUSS was
>>filed regarding the PCP requirement. Details below.
>>
>>I think this DISCUSS needs to be discussed. So please discuss.
>>
>>Please reply to behave@ietf.org.
>>
>>Thanks,
>>Simon
>>
>>
>>-------- Message original --------
>>Sujet: Re: Martin Stiemerling's Discuss on
>>draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
>>Date : Thu, 19 Jul 2012 10:46:42 +0200
>>De : Martin Stiemerling <martin.stiemerling@neclab.eu>
>>Pour : Simon Perreault <simon.perreault@viagenie.ca>
>>Copie =E0 : The IESG <iesg@ietf.org>, <behave-chairs@tools.ietf.org>,
>><draft-ietf-behave-lsn-requirements@tools.ietf.org>
>>
>>Hi Simon, all,
>>
>>On 07/17/2012 11:11 PM, Simon Perreault wrote:
>>> Le 2012-07-17 16:42, Martin Stiemerling a =E9crit :
>>>>> Each and every CGN MUST have PCP and MUST follow the constraints.
>>>>>I'll
>>>>> fix the text in a later revision.
>>>>
>>>> Can we mandate a specific protocol to be used for this or can we only
>>>> mandate that such a type of protocol is being used? I don't see the
>>>>IETF
>>>> in the position to mandate this type of protocol for CGNs.
>>>>
>>>> There are other protocols out there which might be suitable. Note that
>>>>I
>>>> am co-author of some, but this isn't the reason for the question. I do
>>>> not get any reward if I promote these protocols.
>>>>
>>>> It is more:
>>>> do we need to constrain CGN deployments to a protocol (PCP) which is
>>>> developed right now, or are we open to existing or future protocols,
>>>>or
>>>> whatever folks deploying this deem right?
>>>>
>>>> I would propose to change REQ-9 to :
>>>> REQ-9: A CGN MUST include a middlebox control protocol that allows
>>>> manipulation of CGN bindings with the following contstraints <list
>>>>items
>>>> A and B>
>>>> REQ-9a: If PCP is used these contstraints MUST be applied in addition
>>>>to
>>>> contraints A and B:
>>>> <list items C and D>
>>>
>>> That was discussed in IETF 81 (Qu=E9bec). Here's the extract from the
>>> minutes:
>>>
>>>            Stuart Cheshire: ietf has one port forwarding protocol,
>>>which
>>>            is PCP, so we should require it by name
>>
>>There are multiple middlebox control protocols published by the IETF
>>(standards track and experimental) and I have not seen any call for
>>consensus on what **the** IETF's middlebox control is, neither I have
>>seen any RFC that states this.
>>
>>I do not see that an individual can declare IETF consensus based on his
>>own opinion.
>>
>>
>>>
>>>            Dave Thaler: I agree. PCP doc is in final stages.
>>
>>Again, an opinion of an individual. Nothing wrong about it, but it does
>>not state IETF consensus.
>>
>>>
>>> There was consensus from the WG. In consequence, the text was changed
>>> from this (-02):
>>>
>>>              A CGN SHOULD support a port forwarding protocol such as
>>>the
>>>              Port Control Protocol [I-D.ietf-pcp-base].
>>>
>>> to this (-03):
>>>
>>>             A CGN SHOULD include a Port Control Protocol server
>>>             [I-D.ietf-pcp-base].
>>>
>>> (That requirement later became a MUST, but that's orthogonal to what
>>> protocol we require.)
>>
>>I do not see that the IETF can mandate what protocols are being used to
>>control a device. The market will decide!
>>
>>For instance, the is no MUST required that routers implement BGP. It is
>>good to do this, but if one decides to go for IS-IS (or whatever) that
>>is just fine.
>>
>>Another example, there is also no MUST requirement that routers, or
>>hosts in general, have to implement SNMP.
>>
>>However, I can see the immediate need to mandate that a CGN SHOULD/MUST
>>support a middlebox control protocol that is able to install and
>>maintain NAT bindings.
>>
>>   Martin
>>
>>--=20
>>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
>>
>>
>>_______________________________________________
>>Behave mailing list
>>Behave@ietf.org
>>https://www.ietf.org/mailman/listinfo/behave
>
>
>_______________________________________________
>Behave mailing list
>Behave@ietf.org
>https://www.ietf.org/mailman/listinfo/behave


From ietfdbh@comcast.net  Thu Jul 19 11:20:52 2012
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41FC621F86B8 for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 11:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.383
X-Spam-Level: 
X-Spam-Status: No, score=-102.383 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tAf3f6xDnzxy for <ietf@ietfa.amsl.com>; Thu, 19 Jul 2012 11:20:51 -0700 (PDT)
Received: from qmta04.emeryville.ca.mail.comcast.net (qmta04.emeryville.ca.mail.comcast.net [76.96.30.40]) by ietfa.amsl.com (Postfix) with ESMTP id 3851821F867F for <ietf@ietf.org>; Thu, 19 Jul 2012 11:20:51 -0700 (PDT)
Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta04.emeryville.ca.mail.comcast.net with comcast id cJAj1j0011Y3wxoA4JMlNt; Thu, 19 Jul 2012 18:21:45 +0000
Received: from [192.168.1.67] ([184.39.8.144]) by omta15.emeryville.ca.mail.comcast.net with comcast id cJLu1j00K36TH608bJM1R5; Thu, 19 Jul 2012 18:21:39 +0000
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Thu, 19 Jul 2012 14:20:53 -0400
Subject: Re: [BEHAVE] [pcp] Fwd: Re: Martin Stiemerling's Discuss on draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
From: David Harrington <ietfdbh@comcast.net>
To: Sam Hartman <hartmans@painless-security.com>, Simon Perreault <simon.perreault@viagenie.ca>
Message-ID: <CC2DB8AA.23DF4%ietfdbh@comcast.net>
Thread-Topic: [BEHAVE] [pcp] Fwd: Re: Martin Stiemerling's Discuss on draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
In-Reply-To: <tslsjcnj446.fsf@mit.edu>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:06 -0700
Cc: pcp@ietf.org, "behave@ietf.org" <behave@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, 19 Jul 2012 18:20:52 -0000

On 7/19/12 9:02 AM, "Sam Hartman" <hartmans@painless-security.com> wrote:

>I think that behave-lsn-requirements is far more useful if it names a
>specific protocol by name.  By endorcing one of our middlebox protocols,
>we encourage interoperability.  If we don't pick a protocol by name, we
>don't really promote interoperability. It's not useful if your CGN does
>midcom and my client does PCP and I'm your customer.  The assumption
>behind LSN-requirements is that the CGN and the CPE are not
>controlled/purchased/whatever by the same entity.  So, mandating a
>specific protocol seems desirable.

The IETF could mandate a specific protocol to try to ensure
interoperability, but doing this takes the decision out of the
responsibility of the deployer to choose the best solution for the
deployment environment, and out of the responsibility of the vendor to
best meet their customers' demands.
Some vendors already support an SNMP-based environment, and a CGN-NAT-MIB
might best meet their needs.
Some vendors might support a Netconf environment and desire a
Netconf-based configuration solution.
Some vendors already use AAA widely to control their environment, and
Diameter NAT control might be preferable.
Some vendors might be implementing the (not yet IETF-approved) PCP
standard, and would prefer that solution.

>
>I think that the behave WG is the right place to make that decision.
>The IETF as a whole should be able to second guess behave, but we should
>need a fairly high bar  for  doing so.

I think that **within IETF**, behave wg might have the right expertise to
make this decision (technical comparison of middlebox protocols by
protocol designers). Of course, no current WG has much input from
proponents of the original MIDCOM WG strategy, and most Diameter
proponents are not very active in behave wg. And behave DOES have an
overlap between the PCP developers and behave solutions. So behave WG
might be rather biased toward a specific solution (not that the bias is
necessarily bad, but the bias should be recognized).

Of course, if CGN is only an ipv4 exit strategy, as is asserted, then
sunset4 would seem the appropriate choice, so we have one consistent ipv4
exit strategy.
We already recognize that different wgs are developing ipv4 exit
strategies that conflict; that's why a sunset4 wg has been approved.
And if CGN **is** only for ipv4-sunsetting, a "this IETF recommendation
becomes obsolete on such-and-such a date" might be appropriate for
lsn-requirements.
The right expertise might be in the sunset4 wg, which might have increased
operator input about a complete ipv4/ipv6 transition deployment strategy
rather than middlebox protocol design comparisons by middlebox protocol
designers.

While I would love to see consensus for a good interoperable solution, and
would support ***A*** standard that says "to be compliant to THIS
specification, use THIS middlebox proposal", I hesitate to say "this is
the ONLY middlebox standard that is recommended or usable within IETF
standards" - especially if that only recommended part has little or no
actual field experience to back up the RECOMMENDED, and little or no
documentation has been done of the suitability/useability in various
environments of the existing IETF standards that would become NOT
RECOMMENDED.

I think the right place to make the decision about which midcom solution
should be used in a particular environment is in the market.
My cable provider lets me purchase/control my cable router (to a degree),
but only certain routers are supported.
I can choose which cable router offers the additional
functionality/control I want for my environment.
My provider has input to the decision, and so do I (to a limited extent).
Of course, to a limited extent, I can also choose a different provider or
get less support from my provider.


>
>The claim that PCP is the IETF's only protocol in this space does seem a
>little bit on the wishful thinking side of things. So, I could
>understand if the IESG wanted to ask behave to spend a little more time
>on the question.

+1 (or ask sunset4 to spend a little more time on the question).


David Harrington
ietfdbh@comcast.net
+1-603-828-1401



From hartmans@painless-security.com  Thu Jul 19 13:16:08 2012
Return-Path: <hartmans@painless-security.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F80411E809B; Thu, 19 Jul 2012 13:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.857
X-Spam-Level: 
X-Spam-Status: No, score=-102.857 tagged_above=-999 required=5 tests=[AWL=-0.592, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GxAaKkdCMFMK; Thu, 19 Jul 2012 13:16:07 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 3172711E8099; Thu, 19 Jul 2012 13:16:06 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 69E72203BA; Thu, 19 Jul 2012 16:17:15 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 4B22541F0; Thu, 19 Jul 2012 16:16:31 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: David Harrington <ietfdbh@comcast.net>
Subject: Re: [BEHAVE] [pcp] Fwd: Re: Martin Stiemerling's Discuss on draft-ietf-behave-lsn-requirements-08: (with DISCUSS and COMMENT)
References: <CC2DB8AA.23DF4%ietfdbh@comcast.net>
Date: Thu, 19 Jul 2012 16:16:31 -0400
In-Reply-To: <CC2DB8AA.23DF4%ietfdbh@comcast.net> (David Harrington's message of "Thu, 19 Jul 2012 14:20:53 -0400")
Message-ID: <tsl4np3h5gg.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:06 -0700
Cc: pcp@ietf.org, "behave@ietf.org" <behave@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, 19 Jul 2012 20:16:08 -0000

>>>>> "David" == David Harrington <ietfdbh@comcast.net> writes:

    David> The IETF could mandate a specific protocol to try to ensure
    David> interoperability, but doing this takes the decision out of the
    David> responsibility of the deployer to choose the best solution for the
    David> deployment environment, and out of the responsibility of the vendor to
    David> best meet their customers' demands.


This doesn't make any sense to me at all.
It makes sense if   the vendor that the ISP is going to use (the CGN
vendor) is somehow related to the vendor that the customer is going to
use (the CPE vendor).

However, one of the explicitly stated assumptions in the behave-lsn
document is that is not the case.
The customer gets to choose a CPE vendor and the operator gets to choose
a CGN vendor.

The deployment environment here is the Internet.

In cases like this in the past we have chosen a technology.
I'm reasonably sure that host requirements mandate DNS as the name
service protocol. We don't want one isp to choose  some big LDAP
directory and one ISP  to choose DNS.
We want customers name resolution to continue to work (with the same CPE
they already have) as they move from one ISP to another.

The same arguments apply here .

Under the assumptions of this BCP, there is not a boundary between
deployment environments across which one deployment could use PCP and
another SNMP. (I am not aware of netconf schema that does anything
similar to PCP that has been standardized.)

Even obvious deployment environments like cable vs DSL don't make
sense. I can buy my own router and stick it behind either a cable modem
or a DSL router. People often do this. With some ISPs the configuration
gets a little tricky and you may introduce an extra level of
NAT. However, people deploy their own customer gateways on cable, DSL,
even in some cases mobile wireless.

BGP was held up as an example, namely that we don't mandate the
implementation of BGP.  Well, not all routers should implement BGP. My
little Linksys box has no need for it.  However, if we wrote
requirements for routers participating in the core routing
infrastructure--routers between large organizations and ISP--we'd almost
certainly mandate BGP.

Not all NATs need the same middlebox control protocol. However, this
document does not apply to all NATs. It applies to NATs that cross
organizational boundaries.  That's exactly the environment where saying
something like "this is an SNMP deployment," confuses me because I don't
think there will be uniform characterizations of the deployment.

From yaojk@cnnic.cn  Fri Jul 20 06:22:26 2012
Return-Path: <yaojk@cnnic.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 BFF5721F8685 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 06:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.184
X-Spam-Level: 
X-Spam-Status: No, score=-101.184 tagged_above=-999 required=5 tests=[AWL=1.414, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S4iv9ahNKyeq for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 06:22:26 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com (Postfix) with SMTP id 79DA121F867C for <ietf@ietf.org>; Fri, 20 Jul 2012 06:22:23 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown127.0.0.1 (HELO computer) (127.0.0.1) by 127.0.0.1 with SMTP; Fri, 20 Jul 2012 21:23:13 +0800
Message-ID: <006801cd667a$d10b89d0$c801a8c0@computer>
From: "Jiankang Yao" <yaojk@cnnic.cn>
To: "IETF Administrative Director" <iad@ietf.org>, "IETF Announcement List" <ietf-announce@ietf.org>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
Subject: Re: Feedback Requested on Draft Fees Policy
Date: Fri, 20 Jul 2012 21:23:12 +0800
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3664
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:06 -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: Fri, 20 Jul 2012 13:22:27 -0000

I have taken a look at this policy. but still not very clear about this 
policy.

could you kindly show some  examples for charging the fee?



Jiankang Yao

----- 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>
Sent: Friday, July 20, 2012 9:07 PM
Subject: Feedback Requested on Draft Fees Policy


The IAOC is seeking community feedback on a proposed policy by the IAOC to 
impose
fees to produce information and authenticate documents in response to 
subpoenas and
other legal requests.

The IETF receives requests for information, documentation, authentication or 
other
matters through subpoenas and less formal means that require manpower and 
materials
to be expended.  These requests are on the rise. During the period 2005 to 
2010 the IETF
responded to nine subpoenas.  Since 2011 the IETF has received five 
subpoenas and three
other legal requests for authenticated documents.

Each such request is time sensitive and involves the IETF Counsel, the IAD, 
and members
of the IAOC, who together form the Legal Management Committee, to rapidly 
analyze and
identify the means for satisfying the request.  Often there is a need to 
retain outside counsel,
especially in cases that might lead to depositions or court testimony.

The IAOC believes a Schedule of Fees is an appropriate and reasonable means 
to recover
costs associated with such efforts.

The draft policy entitled Draft Fee Policy for Legal Requests can be found
at: <http://iaoc.ietf.org/policyandprocedures.html>

Before adopting a policy the IAOC would like feedback on this before making 
a
decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.

Ray Pelletier
IETF Administrative Director


From amalis@gmail.com  Fri Jul 20 06:50:19 2012
Return-Path: <amalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAB2C21F8621 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 06:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.422
X-Spam-Level: 
X-Spam-Status: No, score=-103.422 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BX4LFJoLVgPZ for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 06:50:18 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 88CB721F861F for <ietf@ietf.org>; Fri, 20 Jul 2012 06:50:18 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so4366250ghb.31 for <ietf@ietf.org>; Fri, 20 Jul 2012 06:51: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:from:date:message-id:subject:to :content-type; bh=LJx2XAz6LcyQi+hMXVqMz7+NbetsqsPswAqXm/2/+3w=; b=Ph/V6a+49wa1/NxSCxYbZe0tSsSsmvHlyjus4FTNBK/iPLUYu5YXTJjqdUqU5IviCU CgujQcJxvXKlwyjeIoGqyXraN1XuqY12knI78etBEeSBuWnN6AdMJFAMBb6PIp47UtRy 1o15lBBmjc8O+5FULXKDOyS1CMNHZ+ZfDAzzbUUjSbQ8oh41BRW35Wwe++6JNwGmrmLl nP1Jakhel2wFk8G/03gF5uvzNJBMC1SarZ2S4TdRheokyxsiGNEm1FOjGJUyC2jMtawh kihUSRzZWvJWhbc9E0rZjZsgBxp3D3Wg3qrk8pkd33J8VJA4vH1KU9FcDLpzdm3EAwz8 CQTQ==
Received: by 10.60.154.232 with SMTP id vr8mr7166645oeb.30.1342792274190; Fri, 20 Jul 2012 06:51:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.76.168 with HTTP; Fri, 20 Jul 2012 06:50:54 -0700 (PDT)
In-Reply-To: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Fri, 20 Jul 2012 09:50:54 -0400
Message-ID: <CAK+d4xtwD+JjY7ZQzkB=x=iJMQadn8QF3Z=YcZuX_mNFJ6s9vw@mail.gmail.com>
Subject: Re: Feedback Requested on Draft Fees Policy
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:06 -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, 20 Jul 2012 13:50:19 -0000

I completely agree that it's reasonable to be able to recover these
costs, and trust the IAOC to set the fees to a level commensurate for
cost recovery. There's no reason why the IETF should be financially
burdened by lawsuits between external parties in which the IETF is not
a principal party to the suit.

Cheers,
Andy

On Fri, Jul 20, 2012 at 9:07 AM, IETF Administrative Director
<iad@ietf.org> wrote:
> The IAOC is seeking community feedback on a proposed policy by the IAOC to impose
> fees to produce information and authenticate documents in response to subpoenas and
> other legal requests.
>
> The IETF receives requests for information, documentation, authentication or other
> matters through subpoenas and less formal means that require manpower and materials
> to be expended.  These requests are on the rise. During the period 2005 to 2010 the IETF
> responded to nine subpoenas.  Since 2011 the IETF has received five subpoenas and three
> other legal requests for authenticated documents.
>
> Each such request is time sensitive and involves the IETF Counsel, the IAD, and members
> of the IAOC, who together form the Legal Management Committee, to rapidly analyze and
> identify the means for satisfying the request.  Often there is a need to retain outside counsel,
> especially in cases that might lead to depositions or court testimony.
>
> The IAOC believes a Schedule of Fees is an appropriate and reasonable means to recover
> costs associated with such efforts.
>
> The draft policy entitled Draft Fee Policy for Legal Requests can be found
> at: <http://iaoc.ietf.org/policyandprocedures.html>
>
> Before adopting a policy the IAOC would like feedback on this before making a
> decision.  Comments appreciated to ietf@ietf.org by 6 August 2012.
>
> Ray Pelletier
> IETF Administrative Director

From leifj@nordu.net  Fri Jul 20 08:32:25 2012
Return-Path: <leifj@nordu.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D26121F85E1; Fri, 20 Jul 2012 08:32:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.65
X-Spam-Level: 
X-Spam-Status: No, score=-0.65 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_BLANKS=0.041, RCVD_ILLEGAL_IP=1.908]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51DMdRQ4Xoyy; Fri, 20 Jul 2012 08:32:24 -0700 (PDT)
Received: from backup-server.nordu.net (backup-server.nordu.net [IPv6:2001:948:4:1::66]) by ietfa.amsl.com (Postfix) with ESMTP id 2F87321F849C; Fri, 20 Jul 2012 08:32:24 -0700 (PDT)
Received: from kerio.nordu.net (kerio.nordu.net [109.105.110.42]) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id q6KFXCrV007081 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Jul 2012 17:33:15 +0200 (CEST)
VBR-Info: md=nordu.net; mc=all; mv=dwl.spamhaus.org,swamid.se
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nordu.net; s=default; t=1342798398; bh=1iPcAh11llZAy1xl8gtasG3ntcLP+/iUYB0Q/L9FMd0=; h=From:Subject:Content-Transfer-Encoding:Content-Type:Message-Id: Date:To:Mime-Version; b=qok6xI4qgzngbHqULaeONst6GIFIz3OATMu6eRPXlItk9E0mCUq6G84/JFdJGtAzd aPA5UQsNrWkYdTh3VGHGdTmMgx0miM1iGgp59PxQlQ+RFzg0UK/71U0vtWHioMZXKt h0hqBm6Jx+NFjsayFF/JAdNhEmC1QD94YWpO4MFU=
X-Footer: bm9yZHUubmV0
Received: from [2.68.154.170] ([2.68.154.170]) by kerio.nordu.net; Fri, 20 Jul 2012 17:33:10 +0200
From: "Leif Johansson" <leifj@nordu.net>
Subject: Re: Feedback Requested on Draft Fees Policy
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset=utf-8
In-Reply-To: <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com>
Message-Id: <5DC517E1-12ED-4DCD-B1F1-8B67157727AA@nordu.net>
Date: Fri, 20 Jul 2012 17:33:01 +0200
To: "Richard L. Barnes" <rbarnes@bbn.com>
Mime-Version: 1.0 (1.0)
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:06 -0700
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 15:32:25 -0000

DQoNCjIwIGp1bCAyMDEyIGtsLiAxNjowOSBza3JldiAiUmljaGFyZCBMLiBCYXJuZXMiIDxyYmFy
bmVzQGJibi5jb20+Og0KDQo+ICsxDQo+IA0KPiBBbHRob3VnaCBJIHdvbmRlciB3aGV0aGVyIHJh
ZGljYWwgb3Blbm5lc3Mgd291bGQgYmUgY2hlYXBlciBpbiB0aGUgbG9uZyBydW46IFB1dCBldmVy
eXRoaW5nIG9ubGluZSBhbmQgaGF2ZSBhbiBhdXRvLXJlc3BvbmRlciBhdCBzdWJwb2VuYUBpZXRm
Lm9yZyB0aGF0IHNheXMgIkdvIGxvb2sgaXQgdXAgeW91cnNlbGYuIg0KPiANCg0KSSBjb3VsZCB0
aGluayBvZiBzb21lIG90aGVyIHRoaW5ncyBpdCBjb3VsZCBzYXkgdG9vLi4uDQoNCj4gLS1SaWNo
YXJkDQo+IA0KPiANCj4gDQo+IE9uIEp1bCAyMCwgMjAxMiwgYXQgMTA6MDUgQU0sIFdhcnJlbiBL
dW1hcmkgd3JvdGU6DQo+IA0KPj4gDQo+PiBPbiBKdWwgMjAsIDIwMTIsIGF0IDk6MDcgQU0sIElF
VEYgQWRtaW5pc3RyYXRpdmUgRGlyZWN0b3Igd3JvdGU6DQo+PiANCj4+PiBUaGUgSUFPQyBpcyBz
ZWVraW5nIGNvbW11bml0eSBmZWVkYmFjayBvbiBhIHByb3Bvc2VkIHBvbGljeSBieSB0aGUgSUFP
QyB0byBpbXBvc2UgDQo+Pj4gZmVlcyB0byBwcm9kdWNlIGluZm9ybWF0aW9uIGFuZCBhdXRoZW50
aWNhdGUgZG9jdW1lbnRzIGluIHJlc3BvbnNlIHRvIHN1YnBvZW5hcyBhbmQgDQo+Pj4gb3RoZXIg
bGVnYWwgcmVxdWVzdHMuDQo+Pj4gDQo+Pj4gVGhlIElFVEYgcmVjZWl2ZXMgcmVxdWVzdHMgZm9y
IGluZm9ybWF0aW9uLCBkb2N1bWVudGF0aW9uLCBhdXRoZW50aWNhdGlvbiBvciBvdGhlciANCj4+
PiBtYXR0ZXJzIHRocm91Z2ggc3VicG9lbmFzIGFuZCBsZXNzIGZvcm1hbCBtZWFucyB0aGF0IHJl
cXVpcmUgbWFucG93ZXIgYW5kIG1hdGVyaWFscyANCj4+PiB0byBiZSBleHBlbmRlZC4gIFRoZXNl
IHJlcXVlc3RzIGFyZSBvbiB0aGUgcmlzZS4gRHVyaW5nIHRoZSBwZXJpb2QgMjAwNSB0byAyMDEw
IHRoZSBJRVRGIA0KPj4+IHJlc3BvbmRlZCB0byBuaW5lIHN1YnBvZW5hcy4gIFNpbmNlIDIwMTEg
dGhlIElFVEYgaGFzIHJlY2VpdmVkIGZpdmUgc3VicG9lbmFzIGFuZCB0aHJlZSANCj4+PiBvdGhl
ciBsZWdhbCByZXF1ZXN0cyBmb3IgYXV0aGVudGljYXRlZCBkb2N1bWVudHMuICANCj4+PiANCj4+
PiBFYWNoIHN1Y2ggcmVxdWVzdCBpcyB0aW1lIHNlbnNpdGl2ZSBhbmQgaW52b2x2ZXMgdGhlIElF
VEYgQ291bnNlbCwgdGhlIElBRCwgYW5kIG1lbWJlcnMgDQo+Pj4gb2YgdGhlIElBT0MsIHdobyB0
b2dldGhlciBmb3JtIHRoZSBMZWdhbCBNYW5hZ2VtZW50IENvbW1pdHRlZSwgdG8gcmFwaWRseSBh
bmFseXplIGFuZCANCj4+PiBpZGVudGlmeSB0aGUgbWVhbnMgZm9yIHNhdGlzZnlpbmcgdGhlIHJl
cXVlc3QuICBPZnRlbiB0aGVyZSBpcyBhIG5lZWQgdG8gcmV0YWluIG91dHNpZGUgY291bnNlbCwg
DQo+Pj4gZXNwZWNpYWxseSBpbiBjYXNlcyB0aGF0IG1pZ2h0IGxlYWQgdG8gZGVwb3NpdGlvbnMg
b3IgY291cnQgdGVzdGltb255LiANCj4+PiANCj4+PiBUaGUgSUFPQyBiZWxpZXZlcyBhIFNjaGVk
dWxlIG9mIEZlZXMgaXMgYW4gYXBwcm9wcmlhdGUgYW5kIHJlYXNvbmFibGUgbWVhbnMgdG8gcmVj
b3ZlciANCj4+PiBjb3N0cyBhc3NvY2lhdGVkIHdpdGggc3VjaCBlZmZvcnRzLg0KPj4+IA0KPj4+
IFRoZSBkcmFmdCBwb2xpY3kgZW50aXRsZWQgRHJhZnQgRmVlIFBvbGljeSBmb3IgTGVnYWwgUmVx
dWVzdHMgY2FuIGJlIGZvdW5kIA0KPj4+IGF0OiA8aHR0cDovL2lhb2MuaWV0Zi5vcmcvcG9saWN5
YW5kcHJvY2VkdXJlcy5odG1sPg0KPj4+IA0KPj4+IEJlZm9yZSBhZG9wdGluZyBhIHBvbGljeSB0
aGUgSUFPQyB3b3VsZCBsaWtlIGZlZWRiYWNrIG9uIHRoaXMgYmVmb3JlIG1ha2luZyBhIA0KPj4+
IGRlY2lzaW9uLiAgQ29tbWVudHMgYXBwcmVjaWF0ZWQgdG8gaWV0ZkBpZXRmLm9yZyBieSA2IEF1
Z3VzdCAyMDEyLg0KPj4+IA0KPj4+IFJheSBQZWxsZXRpZXINCj4+PiBJRVRGIEFkbWluaXN0cmF0
aXZlIERpcmVjdG9yDQo+Pj4gDQo+PiANCj4+IA0KPj4gTEdUTSsrLg0KPj4gDQo+PiBTZWVtcyBs
aWtlIGEgZ3JhbmQgaWRlYSAtLSB3aG8ga25vd3MsIG1heSBldmVuIGhlbHAgYXZvaWQgbnVpc2Fu
Y2Ugc3VpdHMgKGFsdGhvdWdoIHRoZSBmZWVzIGFyZSBzbyBzbWFsbCAoY29tcGFyZWQgdG8gYWxs
IHRoZSBvdGhlciBjb3N0cykgdGhhdCBJIGRvbid0IGhvbGQgbXVjaCBob3BlIG9mIHRoaXPigKYp
Lg0KPj4gDQo+PiBXDQo+PiANCj4+IC0tDQo+PiBGb3IgZXZlcnkgY29tcGxleCBwcm9ibGVtLCB0
aGVyZSBpcyBhIHNvbHV0aW9uIHRoYXQgaXMgc2ltcGxlLCBuZWF0LCBhbmQgd3JvbmcuDQo+PiAg
ICAgICAgICAgICAgIC0tIEguIEwuIE1lbmNrZW4NCj4+IA0KPj4gDQo+PiANCj4gDQo=


From pthubert@cisco.com  Fri Jul 20 09:12:05 2012
Return-Path: <pthubert@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 DDF2721F85F2 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 09:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mAAfjCMmSu1a for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 09:12:05 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 7212A21F85D7 for <ietf@ietf.org>; Fri, 20 Jul 2012 09:12:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pthubert@cisco.com; l=1130; q=dns/txt; s=iport; t=1342800777; x=1344010377; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=BnvZrBmxtanXwoVSJSOH+hla+doB7jq2PvMbOBlj7RE=; b=Ua10Dl17eyjhoDKw/ogRogL8lqNvqtCigqVKDZ7iVnEUmTHxgL9lnx0O Vci8nkYQDc7EfegJ/PbozFW27yA5uty4tmXVxaDMRjjmp1OlIHOTcmT1O j8FuXTju6wbQZz+Rayyu4LrOYER6VeN3iJUQeMJePRHXb71+uVmahrlVv Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAJCCCVCtJXG9/2dsb2JhbABFhXSyNYEXgQeCIAEBAQQSARARUQQCAQgRBAEBAwIGHQMCAgIwFAEICAIEEwgMDodrnmSNGZMNgSCKLoVOMmADo2mBZoJf
X-IronPort-AV: E=Sophos;i="4.77,623,1336348800"; d="scan'208";a="103859163"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-8.cisco.com with ESMTP; 20 Jul 2012 16:12:56 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id q6KGCuKT029052 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Fri, 20 Jul 2012 16:12:56 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.219]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0298.004; Fri, 20 Jul 2012 11:12:56 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "IETF Discussion (ietf@ietf.org)" <ietf@ietf.org>
Subject: RE: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: AQHNZpHwRpWEMGWrnEG8/FDCgeyFUpcyVz5A
Date: Fri, 20 Jul 2012 16:12:55 +0000
Deferred-Delivery: Fri, 20 Jul 2012 16:12:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD807D3E99D@xmb-rcd-x01.cisco.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
In-Reply-To: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.88.111]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19052.005
x-tm-as-result: No--35.780200-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:05 -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, 20 Jul 2012 16:12:06 -0000

UmF5Og0KDQpJJ20gZmluZSB3aXRoIHRoZSBjaGFuZ2UNCg0KQ2hlZXJzLA0KDQpQYXNjYWwNCg0K
DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaWV0Zi1hbm5vdW5jZS1ib3VuY2Vz
QGlldGYub3JnIFttYWlsdG86aWV0Zi1hbm5vdW5jZS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YgSUVURiBBZG1pbmlzdHJhdGl2ZSBEaXJlY3Rvcg0KU2VudDogdmVuZHJlZGkgMjAganVp
bGxldCAyMDEyIDE4OjA2DQpUbzogSUVURiBBbm5vdW5jZW1lbnQgTGlzdA0KQ2M6IGlhb2NAaWV0
Zi5vcmc7IGlhYkBpYWIub3JnOyBpZXRmQGlldGYub3JnOyB3Z2NoYWlyc0BpZXRmLm9yZzsgaWVz
Z0BpZXRmLm9yZw0KU3ViamVjdDogUHJvcG9zZWQgSUVURiA5NSBEYXRlIENoYW5nZQ0KDQpUaGUg
SUFPQyBpcyBzZWVraW5nIGNvbW11bml0eSBmZWVkYmFjayBvbiBhIHByb3Bvc2VkIGRhdGUgY2hh
bmdlIGZvciBJRVRGIDk1IHNjaGVkdWxlZCBmb3IgTWFyY2ggMjAxNi4NCg0KQ3VycmVudGx5IElF
VEYgOTUgaXMgc2NoZWR1bGVkIGZvciAyNyBNYXJjaCB0byAxIEFwcmlsIDIwMTYuICAyNyBNYXJj
aCBpcyBFYXN0ZXIuDQoNClRoZSBJQU9DIGlzIHByb3Bvc2luZyBJRVRGIDk1IGJlIHJlc2NoZWR1
bGVkIGZvciAyMCAtIDI1IE1hcmNoIDIwMTYgYW5kIHdvdWxkIGxpa2UgZmVlZGJhY2sgb24gdGhv
c2UgZGF0ZXMgYmVmb3JlIG1ha2luZyBhIGRlY2lzaW9uLiAgQ29tbWVudHMgYXBwcmVjaWF0ZWQg
dG8gaWV0ZkBpZXRmLm9yZyBieSA2IEF1Z3VzdCAyMDEyLg0KDQpSYXkgUGVsbGV0aWVyDQpJRVRG
IEFkbWluaXN0cmF0aXZlIERpcmVjdG9yDQo=

From kathleen.moriarty@emc.com  Fri Jul 20 09:15:10 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E68FB21F8619 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 09:15: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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbQg94ol1RLI for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 09:15:08 -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 ABC9421F8630 for <ietf@ietf.org>; Fri, 20 Jul 2012 09:15:08 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q6KGG2fM010892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 20 Jul 2012 12:16:03 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor) for <ietf@ietf.org>; Fri, 20 Jul 2012 12:15:51 -0400
Received: from mxhub30.corp.emc.com (mxhub30.corp.emc.com [128.222.70.170]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q6KGFpPv008692 for <ietf@ietf.org>; Fri, 20 Jul 2012 12:15:51 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub30.corp.emc.com ([128.222.70.170]) with mapi; Fri, 20 Jul 2012 12:15:50 -0400
From: <kathleen.moriarty@emc.com>
To: <ietf@ietf.org>
Date: Fri, 20 Jul 2012 12:15:49 -0400
Subject: RE: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: Ac1mkgwdaftK5QZHQAmTyp9ZS2+LZQAAM7pw
Message-ID: <F5063677821E3B4F81ACFB7905573F2403B95A3E@MX15A.corp.emc.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
In-Reply-To: <20120720160624.12163.25321.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: Fri, 20 Jul 2012 11:59:06 -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, 20 Jul 2012 16:15:10 -0000

SSBzdXBwb3J0IHRoZSBjaGFuZ2UgYW5kIHdvdWxkIG5vdCBtYWtlIGl0IHRoZXJlIG9uIEVhc3Rl
ci4NCg0KVGhhbmsgeW91LA0KS2F0aGxlZW4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
CkZyb206IHdnY2hhaXJzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzp3Z2NoYWlycy1ib3VuY2Vz
QGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSUVURiBBZG1pbmlzdHJhdGl2ZSBEaXJlY3Rvcg0KU2Vu
dDogRnJpZGF5LCBKdWx5IDIwLCAyMDEyIDEyOjA2IFBNDQpUbzogSUVURiBBbm5vdW5jZW1lbnQg
TGlzdA0KQ2M6IGlhb2NAaWV0Zi5vcmc7IGlhYkBpYWIub3JnOyBpZXRmQGlldGYub3JnOyB3Z2No
YWlyc0BpZXRmLm9yZw0KU3ViamVjdDogUHJvcG9zZWQgSUVURiA5NSBEYXRlIENoYW5nZQ0KDQpU
aGUgSUFPQyBpcyBzZWVraW5nIGNvbW11bml0eSBmZWVkYmFjayBvbiBhIHByb3Bvc2VkIGRhdGUg
Y2hhbmdlIGZvciBJRVRGIDk1DQpzY2hlZHVsZWQgZm9yIE1hcmNoIDIwMTYuDQoNCkN1cnJlbnRs
eSBJRVRGIDk1IGlzIHNjaGVkdWxlZCBmb3IgMjcgTWFyY2ggdG8gMSBBcHJpbCAyMDE2LiAgMjcg
TWFyY2ggaXMgRWFzdGVyLg0KDQpUaGUgSUFPQyBpcyBwcm9wb3NpbmcgSUVURiA5NSBiZSByZXNj
aGVkdWxlZCBmb3IgMjAgLSAyNSBNYXJjaCAyMDE2IGFuZCB3b3VsZCBsaWtlIA0KZmVlZGJhY2sg
b24gdGhvc2UgZGF0ZXMgYmVmb3JlIG1ha2luZyBhIGRlY2lzaW9uLiAgQ29tbWVudHMgYXBwcmVj
aWF0ZWQgdG8gaWV0ZkBpZXRmLm9yZyANCmJ5IDYgQXVndXN0IDIwMTIuDQoNClJheSBQZWxsZXRp
ZXINCklFVEYgQWRtaW5pc3RyYXRpdmUgRGlyZWN0b3INCg0K

From John.Border@hughes.com  Fri Jul 20 09:52:22 2012
Return-Path: <John.Border@hughes.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D5A611E8073 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 09:52:22 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TGljU-Mh6WIV for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 09:52:21 -0700 (PDT)
Received: from mx0a-00115401.pphosted.com (mx0b-00115401.pphosted.com [67.231.153.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4916321F85E4 for <ietf@ietf.org>; Fri, 20 Jul 2012 09:52:14 -0700 (PDT)
Received: from pps.filterd (m0001191 [127.0.0.1]) by mx0b-00115401.pphosted.com (8.14.5/8.14.5) with SMTP id q6KGr9gQ011417 for <ietf@ietf.org>; Fri, 20 Jul 2012 12:53:10 -0400
Received: from hnse10.hns.com (hnse10.hns.com [208.236.67.252]) by mx0b-00115401.pphosted.com with ESMTP id 166t8p27yu-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 20 Jul 2012 12:53:10 -0400
Received: from mail.hughes.com (expexchub.hughes.com [139.85.54.35]) by hnse10.hns.com (Sentrion-MTA-4.2.0/Sentrion-MTA-4.2.0) with ESMTP id q6KGr9ET023811 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <ietf@ietf.org>; Fri, 20 Jul 2012 12:53:09 -0400
Received: from EXPEXCVS1.hughes.com ([139.85.54.30]) by expexchub2.hughes.com ([139.85.54.35]) with mapi; Fri, 20 Jul 2012 12:53:09 -0400
From: John Border <John.Border@hughes.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 20 Jul 2012 12:53:07 -0400
Subject: RE: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: Ac1mkfACLg2UlhOcSEW9OWqZvFv/LAABbVIA
Message-ID: <982B8F9A4E5BDC4B89FF7586464DD21901D03AF68449@EXPEXCVS1.hughes.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
In-Reply-To: <20120720160624.12163.25321.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-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855, 1.0.260, 0.0.0000 definitions=2012-07-20_03:2012-07-19, 2012-07-20, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1207120000 definitions=main-1207200165
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:06 -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, 20 Jul 2012 16:52:22 -0000

DQpJIHRoaW5rIGl0IHNob3VsZCBiZSBjaGFuZ2VkLiAgQnV0LCBpdCBzZWVtcyBsaWtlIHRoZSB3
ZWVrIGxhdGVyIHJhdGhlciB0aGFuIGVhcmxpZXIgd291bGQgYmUgYSBiZXR0ZXIgY2hvaWNlIGR1
ZSB0byB0aGUgZmFjdCB0aGF0IHRoZSB3ZWVrIGJlZm9yZSBFYXN0ZXIgaXMgb2Z0ZW4gU3ByaW5n
IGJyZWFrIGZvciBtYW55IHNjaG9vbHMsIGltcGFjdGluZyB0cmF2ZWwgYW5kIGluY3JlYXNpbmcg
dGhlIGxpa2VsaWhvb2Qgb2YgcGVyc29uYWwgY29uZmxpY3RzIGZvciBhdHRlbmRlZXMuICBJcyB0
aGVyZSBhIGNvbmZsaWN0IGZvciB0aGUgd2VlayBvZiBBcHJpbCAzIHRoYXQgbWFrZXMgaXQgbm90
IGFuIG9wdGlvbj8NCg0KDQpKb2huDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IGlldGYtYW5ub3VuY2UtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmlldGYtYW5ub3VuY2Ut
Ym91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIElFVEYgQWRtaW5pc3RyYXRpdmUgRGlyZWN0
b3INClNlbnQ6IEZyaWRheSwgSnVseSAyMCwgMjAxMiAxMjowNiBQTQ0KVG86IElFVEYgQW5ub3Vu
Y2VtZW50IExpc3QNCkNjOiBpYW9jQGlldGYub3JnOyBpYWJAaWFiLm9yZzsgaWV0ZkBpZXRmLm9y
Zzsgd2djaGFpcnNAaWV0Zi5vcmc7IGllc2dAaWV0Zi5vcmcNClN1YmplY3Q6IFByb3Bvc2VkIElF
VEYgOTUgRGF0ZSBDaGFuZ2UNCg0KVGhlIElBT0MgaXMgc2Vla2luZyBjb21tdW5pdHkgZmVlZGJh
Y2sgb24gYSBwcm9wb3NlZCBkYXRlIGNoYW5nZSBmb3IgSUVURiA5NSBzY2hlZHVsZWQgZm9yIE1h
cmNoIDIwMTYuDQoNCkN1cnJlbnRseSBJRVRGIDk1IGlzIHNjaGVkdWxlZCBmb3IgMjcgTWFyY2gg
dG8gMSBBcHJpbCAyMDE2LiAgMjcgTWFyY2ggaXMgRWFzdGVyLg0KDQpUaGUgSUFPQyBpcyBwcm9w
b3NpbmcgSUVURiA5NSBiZSByZXNjaGVkdWxlZCBmb3IgMjAgLSAyNSBNYXJjaCAyMDE2IGFuZCB3
b3VsZCBsaWtlIGZlZWRiYWNrIG9uIHRob3NlIGRhdGVzIGJlZm9yZSBtYWtpbmcgYSBkZWNpc2lv
bi4gIENvbW1lbnRzIGFwcHJlY2lhdGVkIHRvIGlldGZAaWV0Zi5vcmcgYnkgNiBBdWd1c3QgMjAx
Mi4NCg0KUmF5IFBlbGxldGllcg0KSUVURiBBZG1pbmlzdHJhdGl2ZSBEaXJlY3Rvcg0K

From keith.drage@alcatel-lucent.com  Fri Jul 20 07:27:13 2012
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7DEC21F8625; Fri, 20 Jul 2012 07:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.744
X-Spam-Level: 
X-Spam-Status: No, score=-109.744 tagged_above=-999 required=5 tests=[AWL=0.505, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3e6THmzY9tQ3; Fri, 20 Jul 2012 07:27:13 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id CB30D21F8608; Fri, 20 Jul 2012 07:27:12 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q6KERscc017507 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 20 Jul 2012 16:27:55 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.44]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Fri, 20 Jul 2012 16:27:54 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>, "Bradner, Scott" <sob@harvard.edu>
Date: Fri, 20 Jul 2012 16:27:54 +0200
Subject: RE: Feedback Requested on Draft Fees Policy
Thread-Topic: Feedback Requested on Draft Fees Policy
Thread-Index: Ac1mg5dvioxOXU28T0WsJOfvTEhayAAACVAg
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE240AE8700@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com> <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com> <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu> <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.com>
In-Reply-To: <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.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-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
X-Mailman-Approved-At: Fri, 20 Jul 2012 11:59:12 -0700
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "iab@iab.org" <iab@iab.org>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 14:27:14 -0000

Except that there is a cost of taking all the existing paper archives and m=
aking them available in such a manner. How many thousand pages are out ther=
e?

Keith

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of Richard L. Barnes
> Sent: 20 July 2012 15:25
> To: Bradner, Scott
> Cc: wgchairs@ietf.org; iab@iab.org; Scott Brim; ietf@ietf.org;
> iaoc@ietf.org
> Subject: Re: Feedback Requested on Draft Fees Policy
>=20
> [assuming you mean the "go look it up" idea]
>=20
> We have the technology.  Surely a CMS signed object (or even just an HTTP=
S
> download) would provide adequate authentication that it came from the IET=
F.
> And it doesn't seem like we would have a problem providing authenticated
> documents to the world.
>=20
>=20
>=20
>=20
> On Jul 20, 2012, at 10:17 AM, Bradner, Scott wrote:
>=20
> > great idea - just does not jive with the legal system which often need
> authenticated
> > copies of documents
> >
> > Scott
> >
> > On Jul 20, 2012, at 10:14 AM, Scott Brim wrote:
> >
> >>> On Jul 20, 2012, at 9:07 AM, IETF Administrative Director wrote:
> >>>> The draft policy entitled Draft Fee Policy for Legal Requests can be
> found
> >>>> at: <http://iaoc.ietf.org/policyandprocedures.html>
> >>
> >> Fine idea.
> >
> >
> >


From jmpolk@cisco.com  Fri Jul 20 12:00:31 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 ADEE921F851B; Fri, 20 Jul 2012 12:00:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.513
X-Spam-Level: 
X-Spam-Status: No, score=-110.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YueBR2CbSyNJ; Fri, 20 Jul 2012 12:00:28 -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 7027A21F8637; Fri, 20 Jul 2012 12:00:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1644; q=dns/txt; s=iport; t=1342810881; x=1344020481; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=mqA8am6TJTWCVLVeY6WZcLrqerjIl2I6dWsjMqb1LzU=; b=Y6fK6KDVxQeBfEKj1LXybEwJWoKYSZYgnEveXQM0L0X2kw3QjGRR6jL5 BCRYsIz5mNvsU3WJ5pCJsVEWqapf91do1TTstdIW86+VwUEG59r4789Wp 2IbASrEQK39MXaEJRfn3N4MQhILjLRHhKiubxG67CPC1gRd3dIRgqtAQY c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAPSpCVCrRDoI/2dsb2JhbABFuU6BB4IgAQEBBBIBJQI/EAcEGB4QGT4GARIUDodqDJ5aoCiLToZgA4hNmxyBZoJ9
X-IronPort-AV: E=Sophos;i="4.77,625,1336348800"; d="scan'208";a="49963128"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 20 Jul 2012 19:01:15 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8714.cisco.com [10.99.80.21]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q6KJ1Eaj030858; Fri, 20 Jul 2012 19:01:14 GMT
Message-Id: <201207201901.q6KJ1Eaj030858@mtv-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 20 Jul 2012 14:01:10 -0500
To: "Richard L. Barnes" <rbarnes@bbn.com>, "Andrew G. Malis" <agmalis@gmail.com>
From: James Polk <jmpolk@cisco.com>
Subject: Re: Proposed IETF 95 Date Change
In-Reply-To: <31E58CB3-05F6-4E74-ABD3-C87BB2662897@bbn.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098901.7090009@bogus.com> <D7593A6A-41F7-4004-9249-FBBA5030D1C4@cisco.com> <CAA=duU0XK=gJJzS-7gDGP_NQz=dPxvR4G_xRUnPHNoa537YrxQ@mail.gmail.com> <31E58CB3-05F6-4E74-ABD3-C87BB2662897@bbn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "iaoc@ietf.org" <iaoc@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, 20 Jul 2012 19:00:31 -0000

At 12:58 PM 7/20/2012, Richard L. Barnes wrote:
>For convenience, the complete list:
><http://www.interfaithcalendar.org/2016.htm>

outstanding - now we can't meet that whole year... ;-)



>On Jul 20, 2012, at 1:44 PM, Andrew G. Malis wrote:
>
> > As long as you don't go any later than the week of April 10 - the week
> > of April 17 runs into the start of Passover.
> >
> > Thanks,
> > Andy
> >
> > On Fri, Jul 20, 2012 at 1:29 PM, Fred Baker (fred) <fred@cisco.com> wrote:
> >>
> >> On Jul 20, 2012, at 9:36 AM, Joel jaeggli wrote:
> >>
> >>> On 7/20/12 09:06 , IETF Administrative Director wrote:
> >>>> The IAOC is seeking community feedback on a proposed date 
> change for IETF 95
> >>>> scheduled for March 2016.
> >>>>
> >>>> Currently IETF 95 is scheduled for 27 March to 1 April 
> 2016.  27 March is Easter.
> >>>>
> >>>> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 
> 2016 and would like
> >>>> feedback on those dates before making a decision.  Comments 
> appreciated to ietf@ietf.org
> >>>> by 6 August 2012.
> >>>
> >>> 20 march is palm sunday on the western calender.
> >>>
> >>> If one's a conflict presumably the other is too...
> >>
> >> I personally avoid being away from home on Easter, and would 
> prefer that the IETF meeting avoid it.
> >>
> >> Yes, Palm Sunday is a question, but not quite on the same scale 
> as Easter. I will note, however, that Good Friday (the Friday 
> before Easter) is a national holiday in a number of countries. 
> People schedule vacations around that weekend.
> >>
> >> My suggestion: take the week of April 3 or later.


From jmpolk@cisco.com  Fri Jul 20 12:03:02 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 30FD221F853B; Fri, 20 Jul 2012 12:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.515
X-Spam-Level: 
X-Spam-Status: No, score=-110.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WEV83yvoB-pt; Fri, 20 Jul 2012 12:03:01 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id C0BF321F853C; Fri, 20 Jul 2012 12:02:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1356; q=dns/txt; s=iport; t=1342811031; x=1344020631; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=fo0C0N8/c4MkCSEnqO3UXMuU8sldobiQYqkUBNXUkCA=; b=OgeUatKdJRm2SlCgzUniHUkxt0BdNgsuVw0gbGx0dh+f21uBQtdVEyXZ xO2SGWoREynRq5RfV2iH04hPlyA0LFaaBJ23ssSqaPjhRQq1OXAqJ+CJk wwywRA6uCHuhTGMtNDyD4KU6eiWjctvTQOJpNBjkQ62xnjec9nJDAFlbY E=;
X-IronPort-AV: E=Sophos;i="4.77,625,1336348800"; d="scan'208";a="52536637"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 20 Jul 2012 19:03:51 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8714.cisco.com [10.99.80.21]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q6KJ3ooZ028685; Fri, 20 Jul 2012 19:03:51 GMT
Message-Id: <201207201903.q6KJ3ooZ028685@mtv-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 20 Jul 2012 14:03:47 -0500
To: "Fred Baker (fred)" <fred@cisco.com>, IETF Administrative Director <iad@ietf.org>
From: James Polk <jmpolk@cisco.com>
Subject: Re: Proposed IETF 95 Date Change
In-Reply-To: <D7593A6A-41F7-4004-9249-FBBA5030D1C4@cisco.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098901.7090009@bogus.com> <D7593A6A-41F7-4004-9249-FBBA5030D1C4@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "iaoc@ietf.org" <iaoc@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, 20 Jul 2012 19:03:02 -0000

At 12:29 PM 7/20/2012, Fred Baker (fred) wrote:

>On Jul 20, 2012, at 9:36 AM, Joel jaeggli wrote:
>
> > On 7/20/12 09:06 , IETF Administrative Director wrote:
> >> The IAOC is seeking community feedback on a proposed date change 
> for IETF 95
> >> scheduled for March 2016.
> >>
> >> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 
> March is Easter.
> >>
> >> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 
> 2016 and would like
> >> feedback on those dates before making a decision.  Comments 
> appreciated to ietf@ietf.org
> >> by 6 August 2012.
> >
> > 20 march is palm sunday on the western calender.
> >
> > If one's a conflict presumably the other is too...
>
>I personally avoid being away from home on Easter, and would prefer 
>that the IETF meeting avoid it.
>
>Yes, Palm Sunday is a question, but not quite on the same scale as 
>Easter. I will note, however, that Good Friday (the Friday before 
>Easter) is a national holiday in a number of countries. People 
>schedule vacations around that weekend.
>
>My suggestion: take the week of April 3 or later.

I agree Easter is a date to avoid, but am not offering which way to 
move the meeting. April 3rd of later seems interesting, but does 
start to impact the interval between this meeting and the summer one.

James



From fred@cisco.com  Fri Jul 20 12:08:35 2012
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 364EE11E807F; Fri, 20 Jul 2012 12:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.604
X-Spam-Level: 
X-Spam-Status: No, score=-100.604 tagged_above=-999 required=5 tests=[AWL=-10.005, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, URIBL_SBL=20, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wV+oKD8pVAe; Fri, 20 Jul 2012 12:08:34 -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 20BCC21F84C5; Fri, 20 Jul 2012 12:08:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=3240; q=dns/txt; s=iport; t=1342811370; x=1344020970; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=k2VdECf0LNjHy2rXy0z4TA2Njh0tUnANI7qdMTNqy5k=; b=UYyRBZ/mJEdbNuPKg3am1VzOcdPCnd/5WGRuCLNhnO9PDbZB39Ixlvd1 DbHsYzqPcRGEDjY+t1voxXoUTCFSvb2JWPrnvsmsA/6P735mKutW0uQ1d qHBiCQu8aECT5QoEKPw8wdKIaeHZJT1i5nGd19d0Gxp7QCFK/nbAZIdve 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAA2sCVCtJV2c/2dsb2JhbAArGoV0skWBF4EHgiABAQEDARIBEBEyEwULAgEIGgImAgICMBUQAgQODhmHXAMGBgspnjKNGYF9hzQFiVaBIIouhU4yYAOVRYETjRGBZoJfbw
X-IronPort-AV: E=Sophos;i="4.77,625,1336348800"; d="scan'208";a="103882450"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-2.cisco.com with ESMTP; 20 Jul 2012 19:09:29 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id q6KJ9TRG007118 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 20 Jul 2012 19:09:29 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.118]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0298.004; Fri, 20 Jul 2012 14:09:29 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "<sarikaya@ieee.org>" <sarikaya@ieee.org>
Subject: Re: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: AQHNZpGgHPezWzUAEUOyzRfpu5Ugb5cy1A0AgAAI/oA=
Date: Fri, 20 Jul 2012 19:09:23 +0000
Message-ID: <80322321-0A40-4F3C-A180-B4AA6AFF4277@cisco.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <CAC8QAce9Gd8GkViAfukZQSQXfOm5tZsXgDTkRt_PDNOAGUSG0Q@mail.gmail.com>
In-Reply-To: <CAC8QAce9Gd8GkViAfukZQSQXfOm5tZsXgDTkRt_PDNOAGUSG0Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.32.244.221]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19054.001
x-tm-as-result: No--34.825600-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="utf-8"
Content-ID: <C63F4B545FB2B6498A1A0AE7EB211858@cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "iaoc@ietf.org" <iaoc@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, 20 Jul 2012 19:08:35 -0000

DQpPbiBKdWwgMjAsIDIwMTIsIGF0IDExOjM3IEFNLCBCZWhjZXQgU2FyaWtheWEgd3JvdGU6DQoN
Cj4gSSBkb24ndCB1bmRlcnN0YW5kIHdoeSB0aGlzIGlzc3VlIGlzIGNvbWluZyB1cC4NCj4gTWF5
YmUgeW91IGRvbid0IGtub3csIElFVEYgODQgZmFsbHMgaW4gdGhlIG1vbnRoIG9mIFJhbWFkYW4g
Zm9yDQo+IE11c2xpbXMgYW5kIG5vYm9keSBhc2tlZCB0byBjaGFuZ2UgaXQ/DQoNClR3byBjb21t
ZW50cywgYSBxdWVzdGlvbiwgYW5kIGEgc3VnZ2VzdGlvbi4gDQoNCk9uZSwgdGhlIG11c2xpbXMg
aW4gdGhlIGNyb3dkIGhhZCB0aGUgb3Bwb3J0dW5pdHksIGp1c3QgYXMgYW55b25lIGVsc2UgaW4g
dGhlIElFVEYgZGlkLiBJIGRvbid0IHBlcnNvbmFsbHkga2VlcCB0cmFjayBvZiBSYW1hZGFuLCBh
bmQgSSBkb24ndCBleHBlY3QgdGhlIG11c2xpbXMgdG8ga2VlcCB0cmFjayBvZiBFYXN0ZXIgZm9y
IG1lLiBJIHdhcyBnbGFkIHRvIGhlYXIgQW5keSdzIG1lbnRpb24gb2YgUGVzYWNoOyB0aGF0J3Mg
YW5vdGhlciBvbmUgSSB3b3VsZG4ndCBrbm93LiANCg0KVHdvIC0gdGhhdCdzIGEgbW9udGgsIG5v
dCBhIHdlZWtlbmQgb3IgYSBkYXkuIFRoZSBsYXJnZXIgdGhlIGludGVydmFsIHlvdSB3YW50IHRv
IHB1dCBvZmYgbGltaXRzLCB0aGUgbW9yZSBpbnRlcmFjdGlvbnMgaXQgaGFzLg0KDQoNCklmIHlv
dSBhcmUgcGVyc29uYWxseSBhIE11c2xpbSwgdGhpcyBpcyBhIHF1ZXN0aW9uIGZvciB5b3U7IGlm
IG5vdCwgdGhlbiBpdHMgYSBxdWVzdGlvbiBmb3IgdGhlIE11c2xpbXMgb24gdGhlIGxpc3QuDQoN
CkVhc3RlciBpcyBhIGRheSBpbiB3aGljaCBDaHJpc3RpYW5zIGRvIGxpdHRsZSBiZXNpZGVzIEVh
c3Rlci1yZWxhdGVkIHRoaW5ncyAtIHN1bnJpc2Ugc2VydmljZXMsIGVnZyBodW50cyAod2hpY2gg
SSBjYW4gZXhwbGFpbiBob3cgdGhleSByZWxhdGUgdG8gRWFzdGVyLCBidXQgeW91J2xsIGxhdWdo
LCBhcyBpdCBoYXMgbm90aGluZyB0byBkbyB3aXRoIHRoZSBjZW50cmFsIGlzc3VlIG9mIEVhc3Rl
ciksIGFuZCBnZW5lcmFsIGZhbWlseSB0aW1lLiBHb29kIEZyaWRheSB0aHJvdWdoIEVhc3Rlciwg
YXMgSSBtZW50aW9uZWQsIGlzIGEgY29tbW9uIHZhY2F0aW9uIHdlZWtlbmQgaW4gRXVyb3BlIGFw
YXJ0IGZyb20gcmVsaWdpb3VzIHNpZ25pZmljYW5jZS4gUGVzYWNoIChQYXNzb3Zlciwgd2hpY2gg
aXMgYSBkYXksIGFuZCB0aGUgZGF5cyBvZiB1bmxlYXZlbmVkIGJyZWFkLCB3aGljaCBhcmUgdGhl
IGZvbGxvd2luZyB3ZWVrKSBpcyBlaWdodCBkYXlzIHRoYXQgb2JzZXJ2aW5nIEpld3MgdXN1YWxs
eSBzcGVuZCBjbG9zZSB0byBob21lIC0gb3IgaW4gSmVydXNhbGVtIC0gZm9yIHZhcmlvdXMgcmVh
c29ucy4NCg0KVGVsbCBtZSBhYm91dCBSYW1hZGFuPyBNeSB1bmRlcnN0YW5kaW5nIChodHRwOi8v
d3d3Lndpa2lob3cuY29tL0NlbGVicmF0ZS1SYW1hZGFuKSBpcyB0aGF0IGR1cmluZyBSYW1hZGFu
IG9uZSB3YW50cyB0byBiZSBub3QgZmFyIGZyb20gYSBNb3NxdWUgYW5kIHdpbGwgd2FudCAgcmVz
dGF1cmFudHMgdGhhdCBjYXRlciB0byDhuKVhbMSBbCAod2hpY2ggYXJlIGdlbmVyYWxseSB0cnVl
IGFueXdheSkuIEhvd2V2ZXIsIHdoYXQgSSBmaW5kIG9uIHRoZSBuZXQgYW5kIGdldCBmcm9tIE11
c2xpbSBmcmllbmRzIGlzIG5vdCAiZG9uJ3QgdHJhdmVsIGR1cmluZyBSYW1hZGFuIjsgaXQncyAi
dHJhdmVsIHdpc2VseSBkdXJpbmcgUmFtYWRhbiIgKGh0dHA6Ly9pc2xhbS5hYm91dC5jb20vb2Qv
ZGlldGFyeWxhdy9hL2hhbGFsX3RyYXZlbC5odG0pLiBGYXN0aW5nIGhhcyBpdHMgaXNzdWVzLCBi
dXQgaWYgb25lIGlzIHByaW1hcmlseSBlYXRpbmcgYWZ0ZXIgc3VuZG93biwgTXVzbGltIHJlc3Rh
dXJhbnRzIHdpbGwgYmUgb3BlbiBhZnRlciBzdW5kb3duLCB3aGljaCBjb2luY2lkZW50YWxseSBp
cyB0aGUgdGltZSB0aGF0IHdlIHNldCBhc2lkZSBmb3IgZGlubmVyLg0KDQpJcyB0aGVyZSBhbiBl
eHBlY3RhdGlvbiBhbW9uZyBNdXNsaW1zIHRoYXQgdHJhdmVsIGlzIHRvIGJlIGF2b2lkZWQgZHVy
aW5nIFJhbWFkYW4/IEFyZSB0aGVyZSBzcGVjaWZpYyBkYXlzIGluIFJhbWFkYW4gdGhhdCBzaG91
bGQgYmUgc3BlbnQgYXQgaG9tZT8gDQoNCg0KSSdkIHN1Z2dlc3QgdGhhdCBNdXNsaW1zIG1hcmsg
dXAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmVnaXN0cmF0aW9uL01lZXRpbmdXaWtpL3dpa2kvaWV0
Zjg0LyB3aXRoIE1vc3F1ZSBsb2NhdGlvbnMgYW5kIOG4pWFsxIFsIHJlc3RhdXJhbnRzLg0KDQpo
dHRwOi8vd3d3LmlzbGFtaWNmaW5kZXIub3JnL3ByYXllckRldGFpbC5waHA/Y2l0eT1WYW5jb3V2
ZXImc3RhdGU9QkMmY291bnRyeT1jYW5hZGENCg0K

From mary.ietf.barnes@gmail.com  Fri Jul 20 12:41:54 2012
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34EDC11E80C7 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 12:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.572
X-Spam-Level: 
X-Spam-Status: No, score=-103.572 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ePE2PK87mJWJ for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 12:41:53 -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 4D1D611E80C4 for <ietf@ietf.org>; Fri, 20 Jul 2012 12:41:53 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so6185038obb.31 for <ietf@ietf.org>; Fri, 20 Jul 2012 12:42:49 -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=uYnOzApzyRibxwTIw8tzBKMi3aikr4LSvD3ptS1Wm+8=; b=RbkErFl1LGfHpe3eLP8meezdfGwMydE3fZfP8Bbr4SFhvTUzKOdZ00/VYFZwfHVArn jwJHKX7SrNjIK15RYp+C9ck4NwmcsmiSCOdN9Bd0wZ1vfuToq/oUmUuWn1jJ/o3DMzyT SIK54vYD3vmv29dw5Q/k4Z5IfQpckZGJoN0t6VbBcME+7RZFEFOq+LxV8g4gzL6fMNPn 3Eo7ffxomWXBVt9m2QsT5oJjMhFynE/u8BSASL+r+bfP3a3YsyMH5iRvUWb/immBdgLc B4a7pMf8lSXIGWtaBNb+fuNcVJT3nrkrXlfTtUUHlRZzB/KNBNDIL9tGnD7XaZxQvSzF YnoQ==
MIME-Version: 1.0
Received: by 10.182.152.97 with SMTP id ux1mr8779089obb.13.1342813369917; Fri, 20 Jul 2012 12:42:49 -0700 (PDT)
Received: by 10.182.147.1 with HTTP; Fri, 20 Jul 2012 12:42:49 -0700 (PDT)
In-Reply-To: <982B8F9A4E5BDC4B89FF7586464DD21901D03AF68449@EXPEXCVS1.hughes.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <982B8F9A4E5BDC4B89FF7586464DD21901D03AF68449@EXPEXCVS1.hughes.com>
Date: Fri, 20 Jul 2012 14:42:49 -0500
Message-ID: <CAHBDyN77p5UPJsb8Of_KZhcvpnkzAQ4t+L+7sUkm02d_GNuY_w@mail.gmail.com>
Subject: Re: Proposed IETF 95 Date Change
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: John Border <John.Border@hughes.com>
Content-Type: multipart/alternative; boundary=f46d04462c0ae9e1a304c54819da
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 19:41:54 -0000

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

I don't think we should try to factor in Spring Break.  Personally, I like
it when the meeting overlaps with Spring Break because that introduces the
possibility that my sons can travel with me depending upon the locale
(they're old enough to care for themselves during the day). Even if they
are at home, I am much comfortable with not having to worry about their
school activities while I am gone.  Also, the range of dates for Spring
Break is extremely broad in my experience.

So, this is very much a YMMV situation.   While I very much disliked not
being at home during Easter (and very much disliked missing Halloween when
kids were young), it has happened and while it's not ideal, it just comes
with a job that requires travel of an incredibly diverse group of people.
As was pointed out by Richard with the 2016 dates, it's impossible to avoid
religious holidays across the board (in particular given that many want the
week before and the week after religious holiday weeks for various
reasons).

Regards,
Mary.

On Fri, Jul 20, 2012 at 11:53 AM, John Border <John.Border@hughes.com>wrote:

>
> I think it should be changed.  But, it seems like the week later rather
> than earlier would be a better choice due to the fact that the week before
> Easter is often Spring break for many schools, impacting travel and
> increasing the likelihood of personal conflicts for attendees.  Is there a
> conflict for the week of April 3 that makes it not an option?
>
>
> John
>
>
> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:
> ietf-announce-bounces@ietf.org] On Behalf Of IETF Administrative Director
> Sent: Friday, July 20, 2012 12:06 PM
> To: IETF Announcement List
> Cc: iaoc@ietf.org; iab@iab.org; ietf@ietf.org; wgchairs@ietf.org;
> iesg@ietf.org
> Subject: Proposed IETF 95 Date Change
>
> The IAOC is seeking community feedback on a proposed date change for IETF
> 95 scheduled for March 2016.
>
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is
> Easter.
>
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and
> would like feedback on those dates before making a decision.  Comments
> appreciated to ietf@ietf.org by 6 August 2012.
>
> Ray Pelletier
> IETF Administrative Director
>

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

I don&#39;t think we should try to factor in Spring Break. =A0Personally, I=
 like it when the meeting overlaps with Spring Break because that introduce=
s the possibility that my sons can travel with me depending upon the locale=
 (they&#39;re old enough to care for themselves during the day). Even if th=
ey are at home, I am much comfortable with not having to worry about their =
school activities while I am gone. =A0Also, the range of dates for Spring B=
reak is extremely broad in my experience. =A0<div>
<br></div><div>So, this is very much a YMMV situation. =A0 While I very muc=
h disliked not being at home during Easter (and very much disliked missing =
Halloween when kids were young), it has happened and while it&#39;s not ide=
al, it just comes with a job that requires travel of an incredibly diverse =
group of people. =A0 As was pointed out by Richard with the 2016 dates, it&=
#39;s impossible to avoid religious holidays across the board (in particula=
r given that many want the week before and the week after religious holiday=
 weeks for various reasons).=A0</div>
<div><br></div><div>Regards,</div><div>Mary.=A0<br><br><div class=3D"gmail_=
quote">On Fri, Jul 20, 2012 at 11:53 AM, John Border <span dir=3D"ltr">&lt;=
<a href=3D"mailto:John.Border@hughes.com" target=3D"_blank">John.Border@hug=
hes.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
I think it should be changed. =A0But, it seems like the week later rather t=
han earlier would be a better choice due to the fact that the week before E=
aster is often Spring break for many schools, impacting travel and increasi=
ng the likelihood of personal conflicts for attendees. =A0Is there a confli=
ct for the week of April 3 that makes it not an option?<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
John<br>
</font></span><div class=3D"im HOEnZb"><br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:ietf-announce-bounces@ietf.org">ietf-announce-bounc=
es@ietf.org</a> [mailto:<a href=3D"mailto:ietf-announce-bounces@ietf.org">i=
etf-announce-bounces@ietf.org</a>] On Behalf Of IETF Administrative Directo=
r<br>

Sent: Friday, July 20, 2012 12:06 PM<br>
To: IETF Announcement List<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">Cc: <a href=3D"mailto:iaoc@ie=
tf.org">iaoc@ietf.org</a>; <a href=3D"mailto:iab@iab.org">iab@iab.org</a>; =
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a href=3D"mailto:wgcha=
irs@ietf.org">wgchairs@ietf.org</a>; <a href=3D"mailto:iesg@ietf.org">iesg@=
ietf.org</a><br>

Subject: Proposed IETF 95 Date Change<br>
<br>
The IAOC is seeking community feedback on a proposed date change for IETF 9=
5 scheduled for March 2016.<br>
<br>
Currently IETF 95 is scheduled for 27 March to 1 April 2016. =A027 March is=
 Easter.<br>
<br>
The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and wou=
ld like feedback on those dates before making a decision. =A0Comments appre=
ciated to <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> by 6 August 20=
12.<br>

<br>
Ray Pelletier<br>
IETF Administrative Director<br>
</div></div></blockquote></div><br></div>

--f46d04462c0ae9e1a304c54819da--

From joelja@bogus.com  Fri Jul 20 13:08:18 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 B0F6321F84AF for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 13:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.407
X-Spam-Level: 
X-Spam-Status: No, score=-102.407 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jldlsYLjbGXx for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 13:08:18 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id CAA5021F84A6 for <ietf@ietf.org>; Fri, 20 Jul 2012 13:08:15 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q6KK995K049671 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 20 Jul 2012 20:09:10 GMT (envelope-from joelja@bogus.com)
Message-ID: <5009BADF.9030602@bogus.com>
Date: Fri, 20 Jul 2012 13:09:03 -0700
From: Joel jaeggli <joelja@bogus.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: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Proposed IETF 95 Date Change
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <982B8F9A4E5BDC4B89FF7586464DD21901D03AF68449@EXPEXCVS1.hughes.com> <CAHBDyN77p5UPJsb8Of_KZhcvpnkzAQ4t+L+7sUkm02d_GNuY_w@mail.gmail.com>
In-Reply-To: <CAHBDyN77p5UPJsb8Of_KZhcvpnkzAQ4t+L+7sUkm02d_GNuY_w@mail.gmail.com>
X-Enigmail-Version: 1.4.3
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]); Fri, 20 Jul 2012 20:09:10 +0000 (UTC)
Cc: John Border <John.Border@hughes.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jul 2012 20:08:18 -0000

On 7/20/12 12:42 , Mary Barnes wrote:
>  Also, the range of
> dates for Spring Break is extremely broad in my experience.  

More than 6 months inclusive of the southern hemisphere.


From paul.hoffman@vpnc.org  Fri Jul 20 18:07:06 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 923C511E80B3 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 18:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PBxt6hEpRkf2 for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 18:07:06 -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 0907111E80A0 for <ietf@ietf.org>; Fri, 20 Jul 2012 18:07:05 -0700 (PDT)
Received: from [10.20.30.102] (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 q6L0GmaE066983 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 20 Jul 2012 17:16:49 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: Proposed IETF 95 Date Change
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
Date: Fri, 20 Jul 2012 18:08:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9261E011-DA3D-4BDA-A7AF-720C4539BAED@vpnc.org>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2012 01:07:06 -0000

On Jul 20, 2012, at 9:06 AM, IETF Administrative Director wrote:

> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 =
and would like=20
> feedback on those dates before making a decision.  Comments =
appreciated to ietf@ietf.org=20
> by 6 August 2012.


As much as I would love to see lots of people in their easter bonnets at =
the meet-and-greet, I think the move is a good one.

As for the Ramadan issue: we've had IETF meetings during Jewish holidays =
a few times, and folks dealt with it as best they can. If there are some =
accommodations that can be made at any IETF meeting for different =
holidays of major religions, I would bet that IETF Secretariat would be =
glad to hear them.

--Paul Hoffman


From fred@cisco.com  Fri Jul 20 18:29:20 2012
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B98F921F847E for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 18:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.492
X-Spam-Level: 
X-Spam-Status: No, score=-110.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X1tjJyvKvScM for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 18:29:20 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id F1F6B21F847C for <ietf@ietf.org>; Fri, 20 Jul 2012 18:29:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=428; q=dns/txt; s=iport; t=1342834217; x=1344043817; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=cD+CRylkhqYEzL6rEp0KuoTohJpzWKo+JV33TtIt9ZY=; b=XChG4e9DpL1gQqTPLpW673uxfmvcL9+9Q9gWYG56foZK3SMNu85fK/eK iN5a5Mf8nhd68gU7t24HPndqlI4ctgsQamEN7ztqr+afNAU/Y10UlOLu4 i8lBSEBh29L9n8tKi2+awY7K0IHqjTXiQpZa9SDq+wWYIp+SNUQZpzsA6 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EABwFClCtJXG+/2dsb2JhbABFuV2BB4IgAQEBAwESASc/BQsCAQg2EDIlAgQOJ4dlBp5pn32LToVzYAOVRY4kgWaCXw
X-IronPort-AV: E=Sophos;i="4.77,627,1336348800"; d="scan'208";a="103981353"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-8.cisco.com with ESMTP; 21 Jul 2012 01:30:17 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id q6L1UHQb017774 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 21 Jul 2012 01:30:17 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.118]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0298.004; Fri, 20 Jul 2012 20:30:17 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: AQHNZpGgHPezWzUAEUOyzRfpu5Ugb5czQTsAgAAGNAA=
Date: Sat, 21 Jul 2012 01:30:09 +0000
Message-ID: <1095943C-3926-4697-AF13-C4C4D7A5505E@cisco.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <9261E011-DA3D-4BDA-A7AF-720C4539BAED@vpnc.org>
In-Reply-To: <9261E011-DA3D-4BDA-A7AF-720C4539BAED@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.32.244.221]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19054.001
x-tm-as-result: No--30.032200-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: <6D8DD5EBF8E26C41B5D5F5E2ACA43437@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 01:29:20 -0000

On Jul 20, 2012, at 6:08 PM, Paul Hoffman wrote:

> As for the Ramadan issue: we've had IETF meetings during Jewish holidays =
a few times, and folks dealt with it as best they can. If there are some ac=
commodations that can be made at any IETF meeting for different holidays of=
 major religions, I would bet that IETF Secretariat would be glad to hear t=
hem.


It comes down to adding them to the clash list...=

From lear@cisco.com  Fri Jul 20 23:59:22 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 A22BB11E808D for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 23:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.523
X-Spam-Level: 
X-Spam-Status: No, score=-110.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ojQWbCNResOT for <ietf@ietfa.amsl.com>; Fri, 20 Jul 2012 23:59:22 -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 DAB5611E8073 for <ietf@ietf.org>; Fri, 20 Jul 2012 23:59:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=279; q=dns/txt; s=iport; t=1342854020; x=1344063620; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=6BFwhSB3y+gaA7gn++ClgdLONVBSlGvFQq4MLPAC4uQ=; b=SmENUDdH7BPmvIp2WT1ePx898Oy0u9Wcc3bgoXFgXQ+0ubZkNNhcE6B7 cOUGrsckI/oWloXSy2EX1OuRSZJYchJ3uGhNWW4v28NgG69jHDBlDAWMV NdnPS5AONgM/tryieg8K7vsR0yhldn4zy9yZUgXROdpROc0B5B95I3WF7 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAEdTClCQ/khR/2dsb2JhbABFhXKzbIEHgiEBAQQSARBVARALGgIFDAoLAgIJAwIBAgFFBg0BBwEBHodrnyWNGZJQgSCNWYIWgRIDlUaOJ4FmgmE
X-IronPort-AV: E=Sophos;i="4.77,628,1336348800"; d="scan'208";a="75458244"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 21 Jul 2012 07:00:12 +0000
Received: from dhcp-10-55-91-201.cisco.com (dhcp-10-55-91-201.cisco.com [10.55.91.201]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q6L70C7v017314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Jul 2012 07:00:12 GMT
Message-ID: <500A537E.7030505@cisco.com>
Date: Sat, 21 Jul 2012 09:00:14 +0200
From: Eliot Lear <lear@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: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Proposed IETF 95 Date Change
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com>
In-Reply-To: <50098712.6070304@gmail.com>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 06:59:22 -0000

I'd support a date change for IETF 95 but it should be the week of the
14th to take into account Palm Sunday and Good Friday.  As to Ramadan, I
too would like to understand if there is a need to take this holiday
into account, and what would be the practical way to do that?

From brian.e.carpenter@gmail.com  Sat Jul 21 00:14:47 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 791C421F851B for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 00:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.344
X-Spam-Level: 
X-Spam-Status: No, score=-101.344 tagged_above=-999 required=5 tests=[AWL=0.347, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6eLo-b7sLvdG for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 00:14:47 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id C135B21F846E for <ietf@ietf.org>; Sat, 21 Jul 2012 00:14:46 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so3036973wgb.13 for <ietf@ietf.org>; Sat, 21 Jul 2012 00:15:44 -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=nY3a+/CwcEi54qWik1q6oH2wCJyjfgIYMEeiKCnSOxA=; b=eHfZxv81uPgPgYDFF9qwTREGgkcs8wPjXhthtEPAlco4gc7ROogW7z1wOmpVvh/vXI vMHKjcEdmjKIHeGvk7dEjVJx34r37XiH978VvQeFeeIyeIuJ4JuTVUSI4+QQkT8/nrtc iU/0oTYRXBqBHkK/CFAQz7kKne3W1GYAJ/3VbPEqMzCRu3SE9OUEMQToGpw115oRdZJg bpXHexbD8pwMFagZpWDoaGQ9+dFvcK26HsG42F+RglmC3v0vmHGczATvhhfuOnjGZUeh B97DTYJAXdVCp1TF38cJ1bGFxdzEgNhArWsY0OB/ATHxWN2OuUCoe6NsGbzuFaOcUMGZ MQsw==
Received: by 10.180.87.199 with SMTP id ba7mr3536934wib.10.1342854943949; Sat, 21 Jul 2012 00:15:43 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-125.as13285.net. [2.102.216.125]) by mx.google.com with ESMTPS id fb20sm3781285wid.1.2012.07.21.00.15.42 (version=SSLv3 cipher=OTHER); Sat, 21 Jul 2012 00:15:43 -0700 (PDT)
Message-ID: <500A572C.3020003@gmail.com>
Date: Sat, 21 Jul 2012 08:15:56 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Proposed IETF 95 Date Change
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>	<9261E011-DA3D-4BDA-A7AF-720C4539BAED@vpnc.org> <1095943C-3926-4697-AF13-C4C4D7A5505E@cisco.com>
In-Reply-To: <1095943C-3926-4697-AF13-C4C4D7A5505E@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 07:14:47 -0000

On 21/07/2012 02:30, Fred Baker (fred) wrote:
> On Jul 20, 2012, at 6:08 PM, Paul Hoffman wrote:
> 
>> As for the Ramadan issue: we've had IETF meetings during Jewish holidays a few times, and folks dealt with it as best they can. If there are some accommodations that can be made at any IETF meeting for different holidays of major religions, I would bet that IETF Secretariat would be glad to hear them.
> 
> 
> It comes down to adding them to the clash list...

(which is at http://www.ietf.org/meeting/clash-list.html)

And we know that if we did that, on top of all the other technical meetings
that we have to avoid, the result would be overconstrained and scheduling
would become impossible. IMNSHO we need to treat all religious constraints
alike, and in practice that means ignoring them. For practical reasons, we
can't ignore major holidays - not because some of them are religious, but
because they block up hotels and airlines.

Finding the least bad solution is always going to be a compromise, and
I thank the IAOC for continuing to plan several years ahead.

   Brian



From glenzorn@gmail.com  Sat Jul 21 01:04:13 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 A9A9D21F85DF for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 01:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.436
X-Spam-Level: 
X-Spam-Status: No, score=-3.436 tagged_above=-999 required=5 tests=[AWL=0.162,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kA6cjLA76GP5 for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 01:04:13 -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 36FE921F8539 for <ietf@ietf.org>; Sat, 21 Jul 2012 01:04:13 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so7780513pbc.31 for <ietf@ietf.org>; Sat, 21 Jul 2012 01:05:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=BwCDtRMsMWTnrupl3GUajmjtg7OK+WO7/tsXfGbVBro=; b=LccX0evRccRlEmKdrTWPI+JhKjWaVlnBu+Hqvb3mLq5PpszATyaBFWwTO7XYBXRjLe YRsmLcYV7Dkr41ZIsf4WdAzYKg6eLrWGd3dXQ6LtdzjWeiIfepAH3jc+7wgKVcDez+ym y05YKIVWS3KYrc3aZxFYcqwX9/9p4ES4oiVNB3tKpsuTUjughkHqd21Wy+jNYNzsALZp 08poi3UsrzIP4xJC65AkQMtkAl2tzaS7NmsolkOtO1rz/h2XzqMJSfJPm32Hg2M87u7i +QkIx1f8SUILPnDt+21ruK3eWuJ3IaoxLO/TxuLdS1fGJeTnRLQ4HC1Jhuc3vT6JZP2C UaYw==
Received: by 10.68.233.103 with SMTP id tv7mr20161396pbc.124.1342857911413; Sat, 21 Jul 2012 01:05:11 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-122-249-129.revip2.asianet.co.th. [124.122.249.129]) by mx.google.com with ESMTPS id pp2sm5627413pbb.1.2012.07.21.01.05.06 (version=SSLv3 cipher=OTHER); Sat, 21 Jul 2012 01:05:10 -0700 (PDT)
Subject: Re: Proposed IETF 95 Date Change
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <1095943C-3926-4697-AF13-C4C4D7A5505E@cisco.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <9261E011-DA3D-4BDA-A7AF-720C4539BAED@vpnc.org> <1095943C-3926-4697-AF13-C4C4D7A5505E@cisco.com>
Content-Type: multipart/alternative; boundary="=-pfrfzb8i2N4LIoKeoE+A"
Organization: Network Zen
Date: Sat, 21 Jul 2012 15:05:02 +0700
Message-ID: <1342857902.7688.13.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jul 2012 08:04:13 -0000

--=-pfrfzb8i2N4LIoKeoE+A
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Sat, 2012-07-21 at 01:30 +0000, Fred Baker (fred) wrote:

> On Jul 20, 2012, at 6:08 PM, Paul Hoffman wrote:
> 
> > As for the Ramadan issue: we've had IETF meetings during Jewish holidays a few times, and folks dealt with it as best they can. If there are some accommodations that can be made at any IETF meeting for different holidays of major religions, I would bet that IETF Secretariat would be glad to hear them.
> 
> 
> It comes down to adding them to the clash list...


Wow, if I'd known that before I'd have added my daughter's birthday (9
Nov) to the list about 25 years ago; maybe I wouldn't have been at IETF
meetings for all but two...


--=-pfrfzb8i2N4LIoKeoE+A
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sat, 2012-07-21 at 01:30 +0000, Fred Baker (fred) wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On Jul 20, 2012, at 6:08 PM, Paul Hoffman wrote:

&gt; As for the Ramadan issue: we've had IETF meetings during Jewish holidays a few times, and folks dealt with it as best they can. If there are some accommodations that can be made at any IETF meeting for different holidays of major religions, I would bet that IETF Secretariat would be glad to hear them.


It comes down to adding them to the clash list...
</PRE>
</BLOCKQUOTE>
<BR>
Wow, if I'd known that before I'd have added my daughter's birthday (9 Nov) to the list about 25 years ago; maybe I wouldn't have been at IETF meetings for all but two...<BR>
<BR>
</BODY>
</HTML>

--=-pfrfzb8i2N4LIoKeoE+A--


From randy@psg.com  Sat Jul 21 02:45:07 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 1033721F867A for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 02:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.575
X-Spam-Level: 
X-Spam-Status: No, score=-2.575 tagged_above=-999 required=5 tests=[AWL=0.024,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j1fGjHB58X+c for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 02:45:06 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id ABFA921F85FB for <ietf@ietf.org>; Sat, 21 Jul 2012 02:45:06 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SsWG9-000Bzz-No; Sat, 21 Jul 2012 09:46:02 +0000
Date: Sat, 21 Jul 2012 10:46:00 +0100
Message-ID: <m2mx2tsazr.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Proposed IETF 95 Date Change
In-Reply-To: <9261E011-DA3D-4BDA-A7AF-720C4539BAED@vpnc.org>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <9261E011-DA3D-4BDA-A7AF-720C4539BAED@vpnc.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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 09:45:07 -0000

> As for the Ramadan issue

you deserve to deal with surly folk such as i when we have not eaten for
twelve hours.

randy

From duerst@it.aoyama.ac.jp  Sat Jul 21 04:37:35 2012
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB4521F85D0 for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 04:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.286
X-Spam-Level: 
X-Spam-Status: No, score=-100.286 tagged_above=-999 required=5 tests=[AWL=-0.496, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oyxh3VSUGFJC for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 04:37:35 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id F095721F85AC for <ietf@ietf.org>; Sat, 21 Jul 2012 04:37:34 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q6LBcPUa021206 for <ietf@ietf.org>; Sat, 21 Jul 2012 20:38:25 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 759a_e3b1_95087f5e_d328_11e1_af90_001d096c566a; Sat, 21 Jul 2012 20:38:24 +0900
Received: from [IPv6:::1] ([133.2.210.1]:48931) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15E57CE> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Sat, 21 Jul 2012 20:38:27 +0900
Message-ID: <500A94A6.6050801@it.aoyama.ac.jp>
Date: Sat, 21 Jul 2012 20:38:14 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-sparks-genarea-mailarch-05.txt> (IETF Email List	Archiving, Web-based Browsing and Search Tool Requirements) to Informational RFC
References: <20120716163020.29447.40928.idtracker@ietfa.amsl.com>
In-Reply-To: <20120716163020.29447.40928.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 11:37:35 -0000

I have read this document, and based on my experience with mailing lists 
both at the IETF and the W3C, it is adequate. I sincerely hope that 
support for Archived-At message header fields will be provided, because 
this can be extremely convenient to quickly reference a message in 
communication with third parties (starting with the mailing list proper).

Regards,   Martin.

On 2012/07/17 1:30, The IESG wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'IETF Email List Archiving, Web-based Browsing and Search Tool
>     Requirements'
>    <draft-sparks-genarea-mailarch-05.txt>  as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-13. 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
>
>
>     The IETF makes heavy use of email lists to conduct its work.
>     Participants frequently need to search and browse the archives of
>     these lists, and have asked for improved search capabilities.  The
>     current archive mechanism could also be made more efficient.  This
>     memo captures the requirements for improved email list archiving and
>     searching systems.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-sparks-genarea-mailarch/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-sparks-genarea-mailarch/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

From ynir@checkpoint.com  Sat Jul 21 06:54:42 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 5185D21F8646 for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 06:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.382
X-Spam-Level: 
X-Spam-Status: No, score=-10.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Di4pfysxbVNe for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 06:54:41 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 0E9B421F855B for <ietf@ietf.org>; Sat, 21 Jul 2012 06:54:40 -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 q6LDtUxP013014; Sat, 21 Jul 2012 16:55:30 +0300
X-CheckPoint: {500AB2D8-0-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sat, 21 Jul 2012 16:55:28 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Eliot Lear <lear@cisco.com>
Date: Sat, 21 Jul 2012 16:55:26 +0300
Subject: Re: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: Ac1nSHtj/ug8LLiHQL+ZMUXgcPaqFA==
Message-ID: <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com>
In-Reply-To: <500A537E.7030505@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 13:54:42 -0000

On Jul 21, 2012, at 10:00 AM, Eliot Lear wrote:

> I'd support a date change for IETF 95 but it should be the week of the
> 14th to take into account Palm Sunday and Good Friday.  As to Ramadan, I
> too would like to understand if there is a need to take this holiday
> into account, and what would be the practical way to do that?

My Moslem coworkers, some more observant, some less so, all come to work on=
 Ramadan. Ramadan lasts a whole month (well, a whole lunar cycle), and invo=
lves fasting from sunrise to sunset. This is relatively OK when Ramadan fal=
ls in winter, but more painful when it falls in summer.

This year Ramadan started yesterday, and ends on August 19. Moving the meet=
ing one week in either direction would not have helped.

Yoav=

From badimuh@gmail.com  Sat Jul 21 12:00:30 2012
Return-Path: <badimuh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFFD321F858E for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 12:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Vak5cZp2SBx for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 12:00:27 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 091C621F8566 for <ietf@ietf.org>; Sat, 21 Jul 2012 12:00:26 -0700 (PDT)
Received: by weyu54 with SMTP id u54so3779358wey.31 for <ietf@ietf.org>; Sat, 21 Jul 2012 12:01: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 :message-id:references:to:x-mailer; bh=9OdqDIFlZHDMIbodJWZyPQyEgDKLc/1C79w7wFWv6HI=; b=oeP14DcEKomh/qq3zgFqGF4FCGURQaaGEE4N9PWUhHpaJlTR/oyySKXYPqw789iUNZ XMOZI0Q2cD2bkT700oktE0c1ttnldW/7hT4VPO2IvfzkPMsh0QqIXMN6S5N246mnvYjz /h1Orm79+ODowe80evzOPFO4UcItdVWrH7JKOY2hxNFQrdeQ8NgmzM6ZYeXkhDjUuM3A Q7wdp/aM0hFCnG9GxukPjoEnN2/KMyauO4aMVF4MHZCD/QDC83fmtvpZwY8ST+lAhCsP oNtBOCPiVonMQru8Y4NPqqMO5QlE8f1yZ61V4QGnVw7W5U/xkUUpw+dtk/MoYamCAXpb sgpA==
Received: by 10.216.71.82 with SMTP id q60mr1968673wed.64.1342897285616; Sat, 21 Jul 2012 12:01:25 -0700 (PDT)
Received: from [172.16.20.18] ([95.172.204.26]) by mx.google.com with ESMTPS id ef5sm8927205wib.3.2012.07.21.12.01.24 (version=SSLv3 cipher=OTHER); Sat, 21 Jul 2012 12:01:25 -0700 (PDT)
Subject: Re: Proposed IETF 95 Date Change
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: multipart/alternative; boundary="Apple-Mail=_8FB8DF31-F28C-4AFD-BF71-60DDDDCCD5E3"
From: Muhammad Badi <badimuh@gmail.com>
In-Reply-To: <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com>
Date: Sat, 21 Jul 2012 22:01:22 +0300
Message-Id: <C7F4D01F-B0A0-4CBE-B68D-CEB68385CCAA@gmail.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1278)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 19:00:30 -0000

--Apple-Mail=_8FB8DF31-F28C-4AFD-BF71-60DDDDCCD5E3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

You can just plan one at anytime but in the early morning. This would =
help and will come before the tiring part is taking place.


Best Regards
Muhammad Badi

On Jul 21, 2012, at 4:55 PM, Yoav Nir wrote:

>=20
> On Jul 21, 2012, at 10:00 AM, Eliot Lear wrote:
>=20
>> I'd support a date change for IETF 95 but it should be the week of =
the
>> 14th to take into account Palm Sunday and Good Friday.  As to =
Ramadan, I
>> too would like to understand if there is a need to take this holiday
>> into account, and what would be the practical way to do that?
>=20
> My Moslem coworkers, some more observant, some less so, all come to =
work on Ramadan. Ramadan lasts a whole month (well, a whole lunar =
cycle), and involves fasting from sunrise to sunset. This is relatively =
OK when Ramadan falls in winter, but more painful when it falls in =
summer.
>=20
> This year Ramadan started yesterday, and ends on August 19. Moving the =
meeting one week in either direction would not have helped.
>=20
> Yoav


--Apple-Mail=_8FB8DF31-F28C-4AFD-BF71-60DDDDCCD5E3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>You can just plan one at anytime but in the early morning. This =
would help and will come before the tiring part is taking =
place.</div><div><br></div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Lucida Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: 'Lucida Sans'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span style=3D"color:=
 rgb(54, 95, 145); ">Best Regards<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; "><b><span style=3D"color: rgb(54, 95, 145); ">Muhammad =
Badi</span></b></div></div></div></span></span>
</div>
<br><div><div>On Jul 21, 2012, at 4:55 PM, Yoav Nir wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><br>On =
Jul 21, 2012, at 10:00 AM, Eliot Lear wrote:<br><br><blockquote =
type=3D"cite">I'd support a date change for IETF 95 but it should be the =
week of the<br></blockquote><blockquote type=3D"cite">14th to take into =
account Palm Sunday and Good Friday. &nbsp;As to Ramadan, =
I<br></blockquote><blockquote type=3D"cite">too would like to understand =
if there is a need to take this holiday<br></blockquote><blockquote =
type=3D"cite">into account, and what would be the practical way to do =
that?<br></blockquote><br>My Moslem coworkers, some more observant, some =
less so, all come to work on Ramadan. Ramadan lasts a whole month (well, =
a whole lunar cycle), and involves fasting from sunrise to sunset. This =
is relatively OK when Ramadan falls in winter, but more painful when it =
falls in summer.<br><br>This year Ramadan started yesterday, and ends on =
August 19. Moving the meeting one week in either direction would not =
have helped.<br><br>Yoav</div></blockquote></div><br></body></html>=

--Apple-Mail=_8FB8DF31-F28C-4AFD-BF71-60DDDDCCD5E3--

From martin.thomson@gmail.com  Sat Jul 21 13:24:39 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCD521F8549 for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 13:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.933
X-Spam-Level: 
X-Spam-Status: No, score=-3.933 tagged_above=-999 required=5 tests=[AWL=-0.334, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6HXnirI-+btS for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 13:24:38 -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 4FC7221F8528 for <ietf@ietf.org>; Sat, 21 Jul 2012 13:24:38 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so7022458lbb.31 for <ietf@ietf.org>; Sat, 21 Jul 2012 13:25:37 -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=TZGiC848mOA+0stwYOwjwgZmJRe1ZCEDjUs07qwOa/Q=; b=U3iadlA7VWib7VoX2xqTFvlkHLIrzsKEmtrjbNzkXage7Mz8SfJhS75cmBv/F4hf6M /UPbZC1E/qBTs45iStfZiBqp8ndg1gQZPvwRXQoKVrTgB7dGQhSUg/ka6GDtd/J+Hw2M Kk6mmvxk/43ZUToEoR7I77tDHIYw/gMDpd0j9gWTo5C6lrIlxVbDBgZ9yaqN+5ehqaHS Dg4Eepf9rkrfchS53IwWMJ6diy5JzD8mX25pyHfJ6YmgbHyIkrz8/mVRu/s54EQoT9Gu UAhACWKArSo6Tr0QNtuJqdci/nn5lRR0z8jJCBz7ZwU30w6rI3CWNgr4NZ7o6KnWWyoO hYqA==
MIME-Version: 1.0
Received: by 10.112.103.135 with SMTP id fw7mr5137023lbb.25.1342902337039; Sat, 21 Jul 2012 13:25:37 -0700 (PDT)
Received: by 10.112.95.40 with HTTP; Sat, 21 Jul 2012 13:25:36 -0700 (PDT)
In-Reply-To: <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com>
Date: Sat, 21 Jul 2012 13:25:36 -0700
Message-ID: <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com>
Subject: Re: Proposed IETF 95 Date Change
From: Martin Thomson <martin.thomson@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: text/plain; charset=UTF-8
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Jul 2012 20:24:39 -0000

On 21 July 2012 06:55, Yoav Nir <ynir@checkpoint.com> wrote:
> This year Ramadan started yesterday, and ends on August 19. Moving the meeting one week in either direction would not have helped.

But moving it to the southern hemisphere would have.

From jnc@mercury.lcs.mit.edu  Sat Jul 21 14:29:23 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EC3B21F8566 for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 14:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.079
X-Spam-Level: 
X-Spam-Status: No, score=-5.079 tagged_above=-999 required=5 tests=[AWL=-0.894, BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DmXf8b1y2o1H for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 14:29:22 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id D4DC521F8557 for <ietf@ietf.org>; Sat, 21 Jul 2012 14:29:22 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id A3E9618C0A3; Sat, 21 Jul 2012 17:30:21 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Proposed IETF 95 Date Change
Message-Id: <20120721213021.A3E9618C0A3@mercury.lcs.mit.edu>
Date: Sat, 21 Jul 2012 17:30:21 -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, 21 Jul 2012 21:29:23 -0000

    > From: James Polk <jmpolk@cisco.com>

    > outstanding - now we can't meet that whole year... ;-)

Particularly since in _my_ religion, our religious days consist of the set of
days which _aren't_ religious holidays in any other religion... :-)

	Noel

From glenzorn@gmail.com  Sat Jul 21 18:37:26 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 45AF221F8534 for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 18:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.468
X-Spam-Level: 
X-Spam-Status: No, score=-3.468 tagged_above=-999 required=5 tests=[AWL=0.130,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJEZ41GflRxx for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 18:37:25 -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 65E5121F852C for <ietf@ietf.org>; Sat, 21 Jul 2012 18:37:18 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so8899168pbc.31 for <ietf@ietf.org>; Sat, 21 Jul 2012 18:38:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=h0o4c7Gh69YOSb8BBGnWZS+X2uUHwbLQkBiDL4Rpzao=; b=PbvfWrprdmwhE7/3ebIwkN5QXQrExHI0+aPcoJNqrArK0aPNTZy9hqdVitpXSh1KRX ADLPBYzXHuDaVy7QHo4PpGu6f7FVC7scy9G0KLAbruSGih7S5k7Yk21gzreOT5keb9CY 0CExfM3nObimeLCW9IPraZtWH6CcdR1/auKVDisR8xPz52fS7xqyofOy1C741j+kZqfW 4vxamxvrsda8mCZnEX8Jm3Ns2QPD5pkZXIqbIfUGGCeygDxFeO0IfIN5TpwfeOc6WUmc craXU6drKF0Fp86tHkvb9vEj53+th1XnCH5kBqEKaSlbQMxmQJjZrvGSHbEY3uZNqUGK NXZA==
Received: by 10.66.75.202 with SMTP id e10mr21538631paw.55.1342921098612; Sat, 21 Jul 2012 18:38:18 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-122-249-129.revip2.asianet.co.th. [124.122.249.129]) by mx.google.com with ESMTPS id tv6sm6970277pbc.24.2012.07.21.18.38.16 (version=SSLv3 cipher=OTHER); Sat, 21 Jul 2012 18:38:18 -0700 (PDT)
Subject: Re: Proposed IETF 95 Date Change
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com> <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=-LB66lxkPyfwc2gEBCty4"
Organization: Network Zen
Date: Sun, 22 Jul 2012 08:38:13 +0700
Message-ID: <1342921093.7688.90.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2012 01:37:26 -0000

--=-LB66lxkPyfwc2gEBCty4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Sat, 2012-07-21 at 13:25 -0700, Martin Thomson wrote:

> On 21 July 2012 06:55, Yoav Nir <ynir@checkpoint.com> wrote:
> > This year Ramadan started yesterday, and ends on August 19. Moving the meeting one week in either direction would not have helped.
> 
> But moving it to the southern hemisphere would have.


How?


--=-LB66lxkPyfwc2gEBCty4
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sat, 2012-07-21 at 13:25 -0700, Martin Thomson wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 21 July 2012 06:55, Yoav Nir &lt;<A HREF="mailto:ynir@checkpoint.com">ynir@checkpoint.com</A>&gt; wrote:
&gt; This year Ramadan started yesterday, and ends on August 19. Moving the meeting one week in either direction would not have helped.

But moving it to the southern hemisphere would have.
</PRE>
</BLOCKQUOTE>
<BR>
How?<BR>
<BR>
</BODY>
</HTML>

--=-LB66lxkPyfwc2gEBCty4--


From cos@mip.polyamory.org  Sat Jul 21 18:41:18 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 4CB3D21F858F for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 18:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MyKxQBUHRt6R for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 18:41:17 -0700 (PDT)
Received: from mip.polyamory.org (mip.aaaaa.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id B916221F8534 for <ietf@ietf.org>; Sat, 21 Jul 2012 18:41:17 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id 6E72D10760; Sat, 21 Jul 2012 21:42:14 -0400 (EDT)
Date: Sat, 21 Jul 2012 21:42:14 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: Glen Zorn <glenzorn@gmail.com>
Subject: Re: Proposed IETF 95 Date Change
Message-ID: <20120722014214.GK335@mip.aaaaa.org>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com> <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com> <1342921093.7688.90.camel@gwz-laptop>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1342921093.7688.90.camel@gwz-laptop>
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: Sun, 22 Jul 2012 01:41:18 -0000

Glen Zorn <glenzorn@gmail.com> wrote:
> On Sat, 2012-07-21 at 13:25 -0700, Martin Thomson wrote:
> 
> > On 21 July 2012 06:55, Yoav Nir <ynir@checkpoint.com> wrote:
> > > This year Ramadan started yesterday, and ends on August 19. Moving the meeting one week in either direction would not have helped.
> > 
> > But moving it to the southern hemisphere would have.
> 
> How?

By cutting the sunrise-to-sunset fasting period of the day to a much
shorter period.
  -- Cos

From glenzorn@gmail.com  Sat Jul 21 20:52:34 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 8E7DB11E8073 for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 20:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[AWL=-1.612,  BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_IMAGE_ONLY_12=2.46, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ptnjbiual+dD for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 20:52:34 -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 1D26621F84E1 for <ietf@ietf.org>; Sat, 21 Jul 2012 20:52:34 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so9015575pbc.31 for <ietf@ietf.org>; Sat, 21 Jul 2012 20:53:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=RiadGesBhggYUTAZalGi6uNHZdKpDgFvepceRwwsLpA=; b=ax1Ze8DY1e4nEM2b9mFAgpFgTtBsaCutYyfuUJIcA/LvAAELTkqkyBn4r0PcvY5j5v omqua4YrGMaRLA4uiVPcRsZaRJYTJfsfXWrrYdey2zHjacG5iYigDKAydJXrwRTgjSa3 AEkJJw1RqiwKr4hPHM5QZmoY+o3mHy7ZrjurlzVvwT5Pa3wccpcjCAK4/RIujrKkI0G1 cd2QV8Kj0Zs/NxwS4vS+nPEwWrW0LRXq1snop5krXHKYiNDO9Jz9unmJG6A2wVhuTps5 pikxMtDo6R0LKV2F0xd4S72A0AGHr+e1cHA6u9BK9/gGSOFDge3CSOXE6YXKKns+43UX +MZw==
Received: by 10.68.229.2 with SMTP id sm2mr25275057pbc.57.1342929214486; Sat, 21 Jul 2012 20:53:34 -0700 (PDT)
Received: from [192.168.0.102] (ppp-124-122-249-129.revip2.asianet.co.th. [124.122.249.129]) by mx.google.com with ESMTPS id hz10sm7161399pbc.32.2012.07.21.20.53.31 (version=SSLv3 cipher=OTHER); Sat, 21 Jul 2012 20:53:33 -0700 (PDT)
Subject: Re: Proposed IETF 95 Date Change
From: Glen Zorn <glenzorn@gmail.com>
To: Ofer Inbar <cos@aaaaa.org>
In-Reply-To: <20120722014214.GK335@mip.aaaaa.org>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com> <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com> <1342921093.7688.90.camel@gwz-laptop> <20120722014214.GK335@mip.aaaaa.org>
Content-Type: multipart/related; type="multipart/alternative"; boundary="=-udLKsFcKVq6Jy13s57uh"
Organization: Network Zen
Date: Sun, 22 Jul 2012 10:53:30 +0700
Message-ID: <1342929210.7688.95.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
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, 22 Jul 2012 03:52:34 -0000

--=-udLKsFcKVq6Jy13s57uh
Content-Type: multipart/alternative; boundary="=-xsqIbqhpotYenuIylal+"


--=-xsqIbqhpotYenuIylal+
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Sat, 2012-07-21 at 21:42 -0400, Ofer Inbar wrote:

> Glen Zorn <glenzorn@gmail.com> wrote:
> > On Sat, 2012-07-21 at 13:25 -0700, Martin Thomson wrote:
> > 
> > > On 21 July 2012 06:55, Yoav Nir <ynir@checkpoint.com> wrote:
> > > > This year Ramadan started yesterday, and ends on August 19. Moving the meeting one week in either direction would not have helped.
> > > 
> > > But moving it to the southern hemisphere would have.
> > 
> > How?
> 
> By cutting the sunrise-to-sunset fasting period of the day to a much
> shorter period.


I see.  Well, look on the bright side: the meeting could have been in
Reykjavik ;-).


>   -- Cos



--=-xsqIbqhpotYenuIylal+
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sat, 2012-07-21 at 21:42 -0400, Ofer Inbar wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Glen Zorn &lt;<A HREF="mailto:glenzorn@gmail.com">glenzorn@gmail.com</A>&gt; wrote:
&gt; On Sat, 2012-07-21 at 13:25 -0700, Martin Thomson wrote:
&gt; 
&gt; &gt; On 21 July 2012 06:55, Yoav Nir &lt;<A HREF="mailto:ynir@checkpoint.com">ynir@checkpoint.com</A>&gt; wrote:
&gt; &gt; &gt; This year Ramadan started yesterday, and ends on August 19. Moving the meeting one week in either direction would not have helped.
&gt; &gt; 
&gt; &gt; But moving it to the southern hemisphere would have.
&gt; 
&gt; How?

By cutting the sunrise-to-sunset fasting period of the day to a much
shorter period.
</PRE>
</BLOCKQUOTE>
<BR>
I see.&nbsp; Well, look on the bright side: the meeting could have been in Reykjavik <IMG SRC="cid:1342929084.7688.93.camel@gwz-laptop" ALIGN="middle" ALT=";-)" BORDER="0">.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
  -- Cos
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-xsqIbqhpotYenuIylal+--

--=-udLKsFcKVq6Jy13s57uh
Content-ID: <1342929084.7688.93.camel@gwz-laptop>
Content-Disposition: attachment; filename="face-wink.png"
Content-Type: image/png; name="face-wink.png"
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAABHNCSVQICAgIfAhkiAAAAAlwSFlz
AAAN1wAADdcBQiibeAAAABl0RVh0U29mdHdhcmUAd3d3Lmlua3NjYXBlLm9yZ5vuPBoAAAAXdEVY
dEF1dGhvcgBMYXBvIENhbGFtYW5kcmVp35EaKgAAACl0RVh0RGVzY3JpcHRpb24AQmFzZWQgb2Yg
SmFrdWIgU3RlaW5lciBkZXNpZ26ghAVzAAADQUlEQVQ4jWWTW2jVdQCAv//t3HbqzF3cOluL1kWi
3DTP3NAt3bAeokKCXoISFHUEhQ9d3grxKWh0gYxJSAwSKQh8KAkqtcZWtqXTww562NnZpq6dTbdz
ds75337/36/Xhd/zx/f2aUopNnL6g96koRmvhw21F13bAYBUk26gXQxUcObgx6N3NvraxsDI+30H
o/EHvnhmZ0+4ofUhs6ahEZSislJgeWFRXB0fcyvl8juHPx07fV/g2/d2/dT65Pb+1MDzEc39By1U
gJAAFLgW+M0EViejP//o5DNTFwa//PtFAB3gm3d7B1se39rf1bs7EuROId1JVAL0xnq0xnpIKALn
L2T+a/YM7Iu0tD+1d+hIahBAP3Wsr80IRYd27Hoh4lwfRgZL6PEa9FgcFY5COMZKRefDr+ZQ/iJO
+iTP7XspaljhoeMHUm26L/xD27Z1h+X8BWRplttrNQyfLXH46BgyCNCUIp1eZvxKCQWIUh5u/c7u
nr5wEIhDZiC8/vqmh43VqfMIKUi2hnjjlU7erH8Uw7sBKKLYCLcKnocmJd7tyzQ9dsAIhNdvesro
iNc2UVnPk1mFijlLe9jFMDJIz0JDo6PJ58j+NpRTQXkCsT5LYmcST+gdpi800ykuIT2X7W11nL/h
8ev1LD3P1tH5dC0AIdvltZTEKThU130iro/vVPECZZq2XU3nb17tbjUTyHKJl7u3UrQ288v4FX77
M4eUCuFJasOSjmbYUiPA3MTM9GVc10mbTsClTPZmV0MsplvOPcrzacxNLewf2IMWq0Pay8jiHHpl
CYoFgqKLG4szlclIR3DJFIEauTZTeDvZbkS3BBIdB8dboFy4hdINLBNiBigRgO0iXUVOWYxdy7ue
0EeM8enC8rmRz0Nzd+2uemvNSiiBqRS6UoS0gJAUaI4PtotX8cnZOt9P69WSLT85ezH3nQ7QVEme
KHpW9tydZHVy1WRl3Yeyjbluo63ZuEWbf4uCiXsGZ7J11ZUq2WVj/sT/XjiaSlmVB+8eV0odeyRe
irREXa056gKwWA2xUA2rmWLcUWifNTibPxqemPDvuxHg1b72Th3/LQ2tN5DaEwCGrrIKNSqxTv7w
R25qo/8f4VCvV0QXv9gAAAAASUVORK5CYII=


--=-udLKsFcKVq6Jy13s57uh--


From johnl@iecc.com  Sat Jul 21 22:00: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 B4F3621F84D0 for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 22:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.128
X-Spam-Level: 
X-Spam-Status: No, score=-111.128 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tunQ+PJew6gu for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 22:00: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 DCFE421F84C8 for <ietf@ietf.org>; Sat, 21 Jul 2012 22:00:39 -0700 (PDT)
Received: (qmail 92227 invoked from network); 22 Jul 2012 05:01:40 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Jul 2012 05:01:40 -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=500b8934.xn--30v786c.k1207; i=johnl@user.iecc.com; bh=oRYRIc6FPio/9hrndvudj4q2rPNZb1p3Hv/1afS+cvk=; b=QPd72Heun6VAPO541/0wDJu5hGUAomcGp4H50Ma+TfrPlRSyOGlHD6H84DninyASx+wwbnJD/ZHaIwiDYOohSznAMgd8k9M756AURrwYubhBpiZNgCWdNtlsKV6uZ9yEa12yHjElZ95agz9xJN0ydeWOdWz0Fw1YpdGuMrnmkao=
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=500b8934.xn--30v786c.k1207; olt=johnl@user.iecc.com; bh=oRYRIc6FPio/9hrndvudj4q2rPNZb1p3Hv/1afS+cvk=; b=YEZMa1Jbd8CjW3SeVDNNkdx9QHnfPVB1L6/2MbAeEHgTG7/BfuBj6PEin4rRPprd0rE2UuvRBi6ewVvAniyIV1eyROQHs3bkabmCvHNnrqwkYqg34nuKtYWi4+KRHj5ohC0ZG8sCl8Q/7x+tFn3soYkwmy3ZULZpyrmzmm4UYTQ=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 22 Jul 2012 05:01:17 -0000
Message-ID: <20120722050117.5538.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Proposed IETF 95 Date Change
In-Reply-To: <1342929210.7688.95.camel@gwz-laptop>
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, 22 Jul 2012 05:00:40 -0000

>I see.  Well, look on the bright side: the meeting could have been in
>Reykjavik ;-).

Yes, that would have been bright, wouldn't it?

R's,
John

PS: sure like those hot dogs, though.

From yaakov_s@rad.com  Sat Jul 21 23:35:33 2012
Return-Path: <yaakov_s@rad.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A12B521F84D9 for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 23:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.853
X-Spam-Level: 
X-Spam-Status: No, score=-101.853 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21NyxJk8d6-x for <ietf@ietfa.amsl.com>; Sat, 21 Jul 2012 23:35:32 -0700 (PDT)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id 78F0221F84D6 for <ietf@ietf.org>; Sat, 21 Jul 2012 23:35:28 -0700 (PDT)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 22 Jul 2012 08:59:15 +0300
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.02.0298.004; Sun, 22 Jul 2012 09:36:27 +0300
From: Yaakov Stein <yaakov_s@rad.com>
To: Ofer Inbar <cos@aaaaa.org>, Glen Zorn <glenzorn@gmail.com>
Subject: RE: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: AQHNZpHJbsn8EH8oFUy5SF8V/Xp37ZcyKdUAgADzsQCAAHQBAIAAbQMAgABXWICAAAEfAIAAgfMw
Date: Sun, 22 Jul 2012 06:36:27 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC90451F5A8@EXRAD5.ad.rad.co.il>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com> <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com> <1342921093.7688.90.camel@gwz-laptop> <20120722014214.GK335@mip.aaaaa.org>
In-Reply-To: <20120722014214.GK335@mip.aaaaa.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.115.243.62]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Commtouch-Refid: str=0001.0A090202.500B9F6B.006F,ss=1,fgs=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: Sun, 22 Jul 2012 06:35:33 -0000

> By cutting the sunrise-to-sunset fasting period of the day to a much shor=
ter period.

Actually, the first day of this IETF (and the last of IETF54) were very int=
eresting=20
for those fasting on the 9th of Av fast day and having to travel westwards.

Flying west during the fast increases its duration,
for example from Jerusalem to Vancouver there is a 10 hour time zone differ=
ence,
so instead of 25 hours the fast increases to 35 hours without food or water=
.

Y(J)S


From ynir@checkpoint.com  Sun Jul 22 03:13:19 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 39CDA21F847F for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 03:13:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.396
X-Spam-Level: 
X-Spam-Status: No, score=-10.396 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cherIWheNuWZ for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 03:13:18 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id E32D721F8470 for <ietf@ietf.org>; Sun, 22 Jul 2012 03:13:17 -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 q6MADvuk011040; Sun, 22 Jul 2012 13:13:57 +0300
X-CheckPoint: {500BD05E-4-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sun, 22 Jul 2012 13:13:56 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Ofer Inbar <cos@aaaaa.org>
Date: Sun, 22 Jul 2012 13:13:58 +0300
Subject: Re: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: Ac1n8rNu7DhM/mopRgG3agg8UtjhdA==
Message-ID: <C8AEF564-5BAE-447B-9DBD-41192D1C0407@checkpoint.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com> <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com> <1342921093.7688.90.camel@gwz-laptop> <20120722014214.GK335@mip.aaaaa.org>
In-Reply-To: <20120722014214.GK335@mip.aaaaa.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 10:13:19 -0000

On Jul 22, 2012, at 4:42 AM, Ofer Inbar wrote:

> Glen Zorn <glenzorn@gmail.com> wrote:
>> On Sat, 2012-07-21 at 13:25 -0700, Martin Thomson wrote:
>>=20
>>> On 21 July 2012 06:55, Yoav Nir <ynir@checkpoint.com> wrote:
>>>> This year Ramadan started yesterday, and ends on August 19. Moving the=
 meeting one week in either direction would not have helped.
>>>=20
>>> But moving it to the southern hemisphere would have.
>>=20
>> How?
>=20
> By cutting the sunrise-to-sunset fasting period of the day to a much
> shorter period.

That, and although not relevant to Vancouver so much, going without water o=
n a hot summer day is much harder than doing the same on a winter day. It's=
 winter in the southern hemisphere.

Of course, Glen is in Bangkok, so it's hot any day of the year.

Yoav


From abdussalambaryun@gmail.com  Sun Jul 22 04:16:26 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 D34AA21F854D for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 04:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.464
X-Spam-Level: 
X-Spam-Status: No, score=-3.464 tagged_above=-999 required=5 tests=[AWL=0.135,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1FrIWZgKtWWM for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 04:16:26 -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 3C86921F8549 for <ietf@ietf.org>; Sun, 22 Jul 2012 04:16:26 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so4337693vcb.31 for <ietf@ietf.org>; Sun, 22 Jul 2012 04:17:27 -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=snHH7h2s7eWf+qXpy8KDZ8/Tf3j1NMVGArC+03xuq0A=; b=YM6HjOyqg+fES/yX3NxmZYt/cKvx+uC6K9a57KhlrDIg7CO3/BBdleK699IPNSf0W7 EGfnQ0Rfc4PLIqpMD275iSgjoxyH/WzvvrMXKSFWzJLrX648DRlSs8G+mhTgfSHt6Qju 5PRSPGrpk2u0RvqDaTe3pMvKuoa+1tOrScs5if2a6fxjJ34qBHjbMSb5v7z5z6Iv3Em0 MfEreJTIwxAW3VUzAk/m5F1Q34ufH8d6pgP0h4XutJ4Ahi7cfKMCTTrMDS0XuCbijU3e Up9uedGw4GEzETWxDs9ifeFdF5EdSUN3SivoS0jNYIZJwZT/Fi8e5PEEHgOOAMUtDd0F OxvA==
MIME-Version: 1.0
Received: by 10.220.242.73 with SMTP id lh9mr1929963vcb.4.1342955847169; Sun, 22 Jul 2012 04:17:27 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Sun, 22 Jul 2012 04:17:27 -0700 (PDT)
Date: Sun, 22 Jul 2012 13:17:27 +0200
Message-ID: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com>
Subject: Updating RFC2119
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 11:16:27 -0000

Hi All,

I am working on an I-D which is intended as proposed standard but need
some addition requirement language. Therefore, I want to propose to
write a draft to update RFC2119 to add some other language requirement
as below:

IF x, THEN y:

ELSE:

ELSE IF:

Please send your comments or advise, thanking you,

Regards

Abdussalam Baryun
University of Glamorgan, UK
+++++++++++++++++++++

From victor.kuarsingh@gmail.com  Sun Jul 22 07:08:46 2012
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3114221F85B4 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 07:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.827
X-Spam-Level: 
X-Spam-Status: No, score=-1.827 tagged_above=-999 required=5 tests=[AWL=0.376,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hidBwnaY7lrX for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 07:08:45 -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 89C6721F85AF for <ietf@ietf.org>; Sun, 22 Jul 2012 07:08:45 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so9245258obb.31 for <ietf@ietf.org>; Sun, 22 Jul 2012 07:09:47 -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=VBE/VPVvXE7nqrBlHZTH7J1GDi1qXDRZWv4hG5em3OA=; b=nv8+PjM10QqIdfRyX4NC0lbZHRgnvdxWZ+hPJW107B+O6fBxlAKvuHfm9g8c3DnJSw riNB2c7WKzGYjfkH62wjwJxyoq5pRka859t25fGvzShozYwfWicPQ4/XhMIsw97w3YIg Dh168VFaXP1QQsH/yR2ELecblS8sNTbrZWbDU+Gp8qxr08iAeOirkse/Z/rZWoNAS9VL w3QzFtl1N/Jl2iL/WUoFel+CFM2nUDHA+z0v3d9iVydzThkCMcdzyJGFMYlgMrGTD/D+ H3wVkRu5htgbYiCvBSQ+8HCyWnpccI8lyzjk4i3bYNeshGhDpV0EyR0NvhnaGvn+/LYp eMhA==
Received: by 10.50.237.1 with SMTP id uy1mr12518992igc.18.1342966186571; Sun, 22 Jul 2012 07:09:46 -0700 (PDT)
Received: from [192.168.100.200] ([67.224.83.162]) by mx.google.com with ESMTPS id ay5sm3685727igb.15.2012.07.22.07.09.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 22 Jul 2012 07:09:45 -0700 (PDT)
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com> <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com> <1342921093.7688.90.camel@gwz-laptop> <20120722014214.GK335@mip.aaaaa.org> <07F7D7DED63154409F13298786A2ADC90451F5A8@EXRAD5.ad.rad.co.il>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC90451F5A8@EXRAD5.ad.rad.co.il>
Mime-Version: 1.0 (iPad Mail 8J2)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <500447D9-AF64-4924-9DB1-0E5408318070@gmail.com>
X-Mailer: iPad Mail (8J2)
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
Subject: Re: Proposed IETF 95 Date Change
Date: Sun, 22 Jul 2012 10:10:39 -0400
To: Yaakov Stein <yaakov_s@rad.com>
Cc: Ofer Inbar <cos@aaaaa.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 14:08:46 -0000

It is my understanding that for these types of reasons (and others), folks w=
ho are adhering to Ramadan can eat while traveling and if they are sick.

And agreed to previous point that the southern hemisphere may have been less=
 impacting in this particular case (given overlap during IETF in northern he=
misphere In summer).  That said, moving the meeting further south would have=
 helped as well vs. How far north Vancouver is.

Victor K

Sent from my iPad

On 2012-07-22, at 2:36 AM, Yaakov Stein <yaakov_s@rad.com> wrote:

>=20
>> By cutting the sunrise-to-sunset fasting period of the day to a much shor=
ter period.
>=20
> Actually, the first day of this IETF (and the last of IETF54) were very in=
teresting=20
> for those fasting on the 9th of Av fast day and having to travel westwards=
.
>=20
> Flying west during the fast increases its duration,
> for example from Jerusalem to Vancouver there is a 10 hour time zone diffe=
rence,
> so instead of 25 hours the fast increases to 35 hours without food or wate=
r.
>=20
> Y(J)S
>=20

From hallam@gmail.com  Sun Jul 22 07:53:57 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 496E621F85CC; Sun, 22 Jul 2012 07:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.54
X-Spam-Level: 
X-Spam-Status: No, score=-5.54 tagged_above=-999 required=5 tests=[AWL=-1.941,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fJoRquHEZ4YU; Sun, 22 Jul 2012 07:53:56 -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 ED94921F859B; Sun, 22 Jul 2012 07:53:55 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so4404971vcb.31 for <multiple recipients>; Sun, 22 Jul 2012 07:54:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IaJ1A4lEFT4QHdDoBoWq58I5TLfm4lplc7qjRcAFtb8=; b=BQ1aIGp+0IlQMC2nPEfsCUvSsJLlKZMcrUywhtsP1HwJdjX35ai6C5iv8JDMz2Kxmi rTgcB1WqqiPYuOrw4utSu1jfT6kdytmA1nfB3dBSkQV5nLhbjfg6UlqXp8oKvPkM9+ZO 7vslKBva24DwEdXBET7GidBSi5INTBPPV/Z2wwmKPWBFASFHkW554zzDFJKqjHT+Dvlh /oMjqWkw7paKHzZJf7sXxnrylOY7Ql0+EvLTM07kX+TbNQ39lziyTFG/r4oizbOOxspX C9yXAg5/Utm+ecU7dA754UI+as7OkZSgMFJcwvUi4YDjweiy3nAlw8kj5Sq19u2N9VxO lUtw==
MIME-Version: 1.0
Received: by 10.52.240.178 with SMTP id wb18mr8568739vdc.100.1342968897511; Sun, 22 Jul 2012 07:54:57 -0700 (PDT)
Received: by 10.58.116.233 with HTTP; Sun, 22 Jul 2012 07:54:57 -0700 (PDT)
In-Reply-To: <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com> <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com> <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu> <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.com>
Date: Sun, 22 Jul 2012 10:54:57 -0400
Message-ID: <CAMm+Lwjv_x3qKW7xLQHpo24WQURrDqva2od+s1PmgxMW61t33A@mail.gmail.com>
Subject: Re: Feedback Requested on Draft Fees Policy
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, "Bradner, Scott" <sob@harvard.edu>, iab@iab.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 14:53:57 -0000

In theory yes, a signed document would be sufficient.

In practice it would then require an expert witness at $400/hr to
explain that it meant it was authentic.

The schedule of fees seems a reasonable response to a real cost being
imposed on the organization.

On Fri, Jul 20, 2012 at 10:25 AM, Richard L. Barnes <rbarnes@bbn.com> wrote:
> [assuming you mean the "go look it up" idea]
>
> We have the technology.  Surely a CMS signed object (or even just an HTTPS download) would provide adequate authentication that it came from the IETF.  And it doesn't seem like we would have a problem providing authenticated documents to the world.
>
>
>
>
> On Jul 20, 2012, at 10:17 AM, Bradner, Scott wrote:
>
>> great idea - just does not jive with the legal system which often need authenticated
>> copies of documents
>>
>> Scott
>>
>> On Jul 20, 2012, at 10:14 AM, Scott Brim wrote:
>>
>>>> On Jul 20, 2012, at 9:07 AM, IETF Administrative Director wrote:
>>>>> The draft policy entitled Draft Fee Policy for Legal Requests can be found
>>>>> at: <http://iaoc.ietf.org/policyandprocedures.html>
>>>
>>> Fine idea.
>>
>>
>>
>



-- 
Website: http://hallambaker.com/

From marshall.eubanks@gmail.com  Sun Jul 22 08:07:24 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D65C21F8656; Sun, 22 Jul 2012 08:07:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PIckbf72LMzC; Sun, 22 Jul 2012 08:07:23 -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 DD2F121F8653; Sun, 22 Jul 2012 08:07:18 -0700 (PDT)
Received: by bkty7 with SMTP id y7so4235592bkt.31 for <multiple recipients>; Sun, 22 Jul 2012 08:08:20 -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=nFFr8AHtjbPZI92uFb3gsZfT01KTOislxdSUc4ziaQk=; b=lV29QJ8afzM8hToywnZjRuDWG0uLvZ5d7goIjUDiXnk62+l9j511ZdHSLeQkGvDnZX bRpPP2KUaLBZbOrBTIVchdp/CW++uIteJD9eyuNZM7DWZoiTDl8ivnXjsRiJZ/f6UAhX QDR3EMfRapqUQ4zGsnYRqlnFeN0VK4ZN5bDdpinCUOadpuJWZB0xTbf0ISEJLyCn5sPb 2gZAduTQvbvVeUwry++Fnc1AqyRLcuNqDjk52FJekBRuVvaStzh/GBWNerSggv05zRVb FCtYniAsLWQdxvz8HH22zNgvy2BxQXr6K5hTXv/KEGA8+qKEbU1FB0EjqrEhHN3Rpb0Q mHQw==
MIME-Version: 1.0
Received: by 10.204.153.28 with SMTP id i28mr6015010bkw.19.1342969699932; Sun, 22 Jul 2012 08:08:19 -0700 (PDT)
Received: by 10.205.82.79 with HTTP; Sun, 22 Jul 2012 08:08:19 -0700 (PDT)
In-Reply-To: <CAMm+Lwjv_x3qKW7xLQHpo24WQURrDqva2od+s1PmgxMW61t33A@mail.gmail.com>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net> <9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com> <CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com> <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu> <1657B5B7-4680-4E32-991F-10BC70A84347@bbn.com> <CAMm+Lwjv_x3qKW7xLQHpo24WQURrDqva2od+s1PmgxMW61t33A@mail.gmail.com>
Date: Sun, 22 Jul 2012 11:08:19 -0400
Message-ID: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@mail.gmail.com>
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, "Bradner, Scott" <sob@harvard.edu>, iab@iab.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 15:07:25 -0000

On Sun, Jul 22, 2012 at 10:54 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> In theory yes, a signed document would be sufficient.
>
> In practice it would then require an expert witness at $400/hr to
> explain that it meant it was authentic.
>

The depositions are typically to state that the RFC's etc. posted on
line are, to the best of our knowledge and ability, the true RFC's,
etc. So, there would likely still need to be depositions stating that,
signed documents or no.

Remember the basic way that subpoenas work : The IETF is served with a
legal document _demanding_ something, backed by the force of law.

Yes, we typically then point out that much of what they want is
available on line, and frequently negotiate with opposing counsel to
moderate demands for depositions,  etc., but, in the end, we propose,
the judge and opposing counsel dispose. That  won't change.

Regards
Marshall

> The schedule of fees seems a reasonable response to a real cost being
> imposed on the organization.
>
> On Fri, Jul 20, 2012 at 10:25 AM, Richard L. Barnes <rbarnes@bbn.com> wrote:
>> [assuming you mean the "go look it up" idea]
>>
>> We have the technology.  Surely a CMS signed object (or even just an HTTPS download) would provide adequate authentication that it came from the IETF.  And it doesn't seem like we would have a problem providing authenticated documents to the world.
>>
>>
>>
>>
>> On Jul 20, 2012, at 10:17 AM, Bradner, Scott wrote:
>>
>>> great idea - just does not jive with the legal system which often need authenticated
>>> copies of documents
>>>
>>> Scott
>>>
>>> On Jul 20, 2012, at 10:14 AM, Scott Brim wrote:
>>>
>>>>> On Jul 20, 2012, at 9:07 AM, IETF Administrative Director wrote:
>>>>>> The draft policy entitled Draft Fee Policy for Legal Requests can be found
>>>>>> at: <http://iaoc.ietf.org/policyandprocedures.html>
>>>>
>>>> Fine idea.
>>>
>>>
>>>
>>
>
>
>
> --
> Website: http://hallambaker.com/

From johnl@iecc.com  Sun Jul 22 08:30:42 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 11D9721F863E for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 08:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.129
X-Spam-Level: 
X-Spam-Status: No, score=-111.129 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C81Z0vbsdM2q for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 08:30:41 -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 1B57021F863B for <ietf@ietf.org>; Sun, 22 Jul 2012 08:30:40 -0700 (PDT)
Received: (qmail 78305 invoked from network); 22 Jul 2012 15:31:41 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Jul 2012 15:31:41 -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=500c1cdd.xn--9vv.k1207; i=johnl@user.iecc.com; bh=zZH5BR+nmb8LKdUpdHq8FQvDfJsAfes6evQgwCRUepQ=; b=Vh0YFBasY8mWSGI3Sy+09ugHix6s3wz0xGHyuPcmVFfu0sKt1EzaPyCJjeA6GXvmJEHCyPFd48YBwQXtcAHbgxCBGEPV8SVVUS0IuSVRdT1u+BRjZIrAuQ2EKP2zP7HxxmN3UicIAqwzABjINL3eg8EXA5S0Tw8gFkM/pt8FR1I=
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=500c1cdd.xn--9vv.k1207; olt=johnl@user.iecc.com; bh=zZH5BR+nmb8LKdUpdHq8FQvDfJsAfes6evQgwCRUepQ=; b=Wi8wvjjzztEMRQ7GmnP6R/w/o0lG2UCWahayIN0b/T2/N4PBn4sBQMUA6FNYRwLqhshaZXOW+E2j/M3i274VM0ghnRlmJAg99rWun5DcRKM7LCaNBQ8HHkZt0bsbZ4Mv2WutRoEJv5XzzaJ69AZu5O6yRns/TJTUi2qFX2NQ/QE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 22 Jul 2012 15:31:18 -0000
Message-ID: <20120722153118.60473.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
In-Reply-To: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@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: Sun, 22 Jul 2012 15:30:42 -0000

> Yes, we typically then point out that much of what they want is
> available on line, and frequently negotiate with opposing counsel to
> moderate demands for depositions, etc., but, in the end, we propose,
> the judge and opposing counsel dispose. That won't change.

I'd want to set the depo rate high enough that if someone has to be
deposed, he or she will at least feel that the money makes up for
the hassle.

For people with unique skills or knowledge, $800/hr is not unusual.
So long as the rate is published ahead of time, you're not going to
get much argument.  ("Yes, we know it's high.  But we've already told
you how to download stuff yourself for free.")

R's,
John

From warren@kumari.net  Sun Jul 22 08:43:45 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 5A6DA21F85D7; Sun, 22 Jul 2012 08:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.443
X-Spam-Level: 
X-Spam-Status: No, score=-106.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lWP8DZKmRF26; Sun, 22 Jul 2012 08:43:44 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 1DEEA21F852B; Sun, 22 Jul 2012 08:43:41 -0700 (PDT)
Received: from [10.242.9.248] (m2d0f36d0.tmodns.net [208.54.15.45]) by vimes.kumari.net (Postfix) with ESMTPSA id 4CA4C1B405FA; Sun, 22 Jul 2012 11:44:42 -0400 (EDT)
Subject: Re: [IETF] Last Call: <draft-vegoda-cotton-rfc5735bis-02.txt>	(Special Use IPv4 Addresses) to Best Current Practice
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0BCF7C76@TK5EX14MBXC273.redmond.corp.microsoft.com>
Date: Sun, 22 Jul 2012 10:18:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D602BA3-CF79-4A3B-BDAD-3F0B6461075F@kumari.net>
References: <20120712224629.14063.15257.idtracker@ietfa.amsl.com> <m24npbckns.wl%randy@psg.com> <C91E67751B1EFF41B857DE2FE1F68ABA0BCF7C76@TK5EX14MBXC273.redmond.corp.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1278)
Cc: The IESG <iesg-secretary@ietf.org>, 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: Sun, 22 Jul 2012 15:43:45 -0000

On Jul 14, 2012, at 3:18 PM, Christian Huitema wrote:

> Very useful document, certainly worth publishing.

+1

> It is one of those documents that needs frequent updates.
>=20

+1

> RFC 6052, IPv6 Addressing of IPv4/IPv6 Translators, makes reference to =
a predecessor of this document, stating in section 3.1 that "The =
Well-Known Prefix MUST NOT be used to represent non-global IPv4 =
addresses, such as those defined in [RFC1918] or listed in Section 3 of =
[RFC5735]." I assume that implementers will automatically upgrade their =
code to reference the new version.
>=20

-1 -- I would not assume any such thing. I *might* guess that =
implementors will include the new version in new / updated code, but the =
not necessarily the "automatically" bit :-P

W

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Randy Bush
> Sent: Friday, July 13, 2012 4:21 PM
> To: IETF Disgust; The IESG
> Subject: [IETF] Re: Last Call: <draft-vegoda-cotton-rfc5735bis-02.txt> =
(Special Use IPv4 Addresses) to Best Current Practice
>=20
>> The IESG has received a request from an individual submitter to=20
>> consider the following document:
>> - 'Special Use IPv4 Addresses'
>>   <draft-vegoda-cotton-rfc5735bis-02.txt> as Best Current Practice
>=20
> read and support
>=20
> randy
>=20
>=20

--
"Working the ICANN process is like being nibbled to death by ducks,
it takes forever, it doesn't make sense, and in the end we're still dead =
in the water."=20
    -- Tom Galvin, VeriSign's vice president for government relations.




From scott.brim@gmail.com  Sun Jul 22 08:49:45 2012
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 669B221F865C for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 08:49:45 -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=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9J1eRgz0tLWH for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 08:49:44 -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 CF84821F8659 for <ietf@ietf.org>; Sun, 22 Jul 2012 08:49:44 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so9693032pbc.31 for <ietf@ietf.org>; Sun, 22 Jul 2012 08:50:46 -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=P9KVyEN2p+2Q3cE3iCMuQom4x8KZRuzf0c8v5RR9pvs=; b=FB8Q/TROH3GZ/p7/81ZLTAthbyT89D9dyT0oq18tleYXdZVM3gdgptXi6nq2gNuX9/ wCGmsRZIDjABFRqv/uTVJW8SDCw2A5bBQu5NxdBxcFfcuGmcnmAay4AXkYlfnaDb2qvK bcQXgdaGUPaXMu2HV4L0vv39MC2JYvP3Al8aIHuHWtp/gl09bpaWvfjARPnrI77jVijW TT10fclyfz8hLcquB3jj7hgFsQ8+lgW7tpudGBC1j3eZ4EE32zEb6CjQm+ZNosifWvkm FDgfytC2DJnOKjgtKZlzFdaHUQEXvnL3H17quy7XGV5Vmq1V4IO1mL93vpL+lQq4up+x duSQ==
Received: by 10.68.218.133 with SMTP id pg5mr28555648pbc.140.1342972246766; Sun, 22 Jul 2012 08:50:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.220.132 with HTTP; Sun, 22 Jul 2012 08:50:26 -0700 (PDT)
In-Reply-To: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com>
References: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Sun, 22 Jul 2012 11:50:26 -0400
Message-ID: <CAPv4CP95Rhma3reOvrWfrWQE_mqsyY8bL2EvkZq5hD6gbyf_ow@mail.gmail.com>
Subject: Re: Updating RFC2119
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 15:49:45 -0000

On Sun, Jul 22, 2012 at 7:17 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> Hi All,
>
> I am working on an I-D which is intended as proposed standard but need
> some addition requirement language. Therefore, I want to propose to
> write a draft to update RFC2119 to add some other language requirement
> as below:
>
> IF x, THEN y:
>
> ELSE:
>
> ELSE IF:
>
> Please send your comments or advise, thanking you,

That doesn't have to be in 2119.  Lots of RFCs have pseudocode at
various levels of rigor.  Just look around at some protocol specs for
examples.

From johnl@iecc.com  Sun Jul 22 09:03:57 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 71E6221F8671 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 09:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.13
X-Spam-Level: 
X-Spam-Status: No, score=-111.13 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHw9QIhnRKiq for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 09:03: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 71A7B21F866C for <ietf@ietf.org>; Sun, 22 Jul 2012 09:03:56 -0700 (PDT)
Received: (qmail 83086 invoked from network); 22 Jul 2012 16:04:57 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Jul 2012 16:04:57 -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=500c24a9.xn--3zv.k1207; i=johnl@user.iecc.com; bh=ECiMDY84UP91+AQ3SoNI2CaXCLH6jk0v1R/QzCqAoLo=; b=xkzLwPG8ur+izTEGILNBiWWZI8qR4l3Ucb5PxC4t5rQZG6Yg3l2EKNI9oMg1QP++7Nv2GlU4nXX2B4SgmUTKR4yJLyoRIe0STNcB6Ew6SunYKh3aZUggSiOp1kJPpvHb3sENKuA6+2JyQsE72snadSZxlM3m9ns3m3n3H7XkCwk=
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=500c24a9.xn--3zv.k1207; olt=johnl@user.iecc.com; bh=ECiMDY84UP91+AQ3SoNI2CaXCLH6jk0v1R/QzCqAoLo=; b=i5ZZiCUGKbd7cyTefqtwUeDsV59jJEKKITkJ1RjRoipugtHSeSecOg+mv4qejGlDgpMkfb1lpdIkoRgI+dgLQUoWNzZH4aUzrzKRYP5BpRUrf7/7rwgOU3d1Iq2G9xHLZCNm7wupSzGc4r5xrKek0FmQAbQYHzWJd1wWXsCN2f0=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 22 Jul 2012 16:04:35 -0000
Message-ID: <20120722160435.68743.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Proposed IETF 95 Date Change
In-Reply-To: <500447D9-AF64-4924-9DB1-0E5408318070@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, 22 Jul 2012 16:03:57 -0000

> That said, moving the meeting further south would
> have helped as well vs. How far north Vancouver is.

Summer daytime temperatures in Vancouver are typically 20c or lower,
while in the southern US they're usually over 30c.  I'm not sure
that would be an improvement.

You're not going to find cool temperatures again in July or August
unless you go as far south as Argentina or New Zealand.

R's,
John


From melinda.shore@gmail.com  Sun Jul 22 09:25:58 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA35D21F867A for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 09:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.566
X-Spam-Level: 
X-Spam-Status: No, score=-3.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jL51rej8DCwv for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 09:25: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 3F31C21F866C for <ietf@ietf.org>; Sun, 22 Jul 2012 09:25:58 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so9730067pbc.31 for <ietf@ietf.org>; Sun, 22 Jul 2012 09:27:00 -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=Bt5/s8dvqOlw39fcJax8fSnFMBvflufEp5BJPJMnAac=; b=0UUptMdlPi5uMTskQNa+pFPCqa8Qn2iDnj7Yyq+4QVy5W+ihenmd/mUUfsaXbEsUUY eyLOQnl/LibwghXh4LYcXeQ3LUmFfSmATGwL3ownSCXYVGjJKqQ2SV2zF7/yoA6bYXJg J8Qm01T0ZAFyLt0jIpFN6QNQ2s4eldQjqrtay8vqt1xvK7mVkM3yttCZC8K6Ra1hBVa0 GKb4dbFT2GOrBqOXEBp5+xzHEhgdJ29kflPkt0rLlFZHEyd8U/7I04p958Fjbxp5k/gg InmcTleKK4cNJ7BEUXxWzGEtdbqdfrDATGn16y5GNKNm2FuSCN66NmV9nf2xL8ZgBQzY u3JQ==
Received: by 10.68.222.40 with SMTP id qj8mr28627667pbc.139.1342974420287; Sun, 22 Jul 2012 09:27:00 -0700 (PDT)
Received: from spandex.local (66-230-87-150-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.87.150]) by mx.google.com with ESMTPS id pc6sm8155756pbc.47.2012.07.22.09.26.58 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 22 Jul 2012 09:26:59 -0700 (PDT)
Message-ID: <500C29D1.7070605@gmail.com>
Date: Sun, 22 Jul 2012 08:26:57 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Updating RFC2119
References: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com>
In-Reply-To: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 16:25:58 -0000

On 7/22/12 3:17 AM, Abdussalam Baryun wrote:
> IF x, THEN y:
>
> ELSE:
>
> ELSE IF:
>
> Please send your comments or advise, thanking you,

Yes: you might try to explain what problem you think you're
solving.

Melinda


From melinda.shore@gmail.com  Sun Jul 22 09:55:14 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 DF12D21F8666 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 09:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.568
X-Spam-Level: 
X-Spam-Status: No, score=-3.568 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTekM5uTw7DY for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 09:55:14 -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 566B921F84F5 for <ietf@ietf.org>; Sun, 22 Jul 2012 09:55:14 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so9760392pbc.31 for <ietf@ietf.org>; Sun, 22 Jul 2012 09:56:13 -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=O8HqdZAUsDJxHSAKA+OQZgPwF/6R1/YQOPX46uIKqqc=; b=OLuUk3ZLDN1qXpksWMuGW3V8wPstO3UP57VcwR2OfEqeYIz3J3/v4ZcuATGqGqdRCN ofnyih8E7sSobDwrYNQPBjNKcXWW/ZCjFWZlnWCCD8hdS+vG/yBaPOXSaRRW7gWb9Aew wQTByMiBjnOG26wjAVdmIt8E6+qyKsd3TzXYC8DTEAjUVfRujkNzwpD09JzMSSgfhMQ0 c5Q9FAjsV5jwHYTbLjohW2ZbUGAY36mbZ0hAiNW7hoj+FGp3scU1hCDuwJ8sgbJ8ocgK uKGn7bssxRz+WThrP/v1PoDMQMKjWU/Ju/3TZU1IlsTVS2GnOHRWKZSnLzI/4AmfKrap QAsw==
Received: by 10.66.88.68 with SMTP id be4mr25136201pab.23.1342976173097; Sun, 22 Jul 2012 09:56:13 -0700 (PDT)
Received: from spandex.local (66-230-87-150-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.87.150]) by mx.google.com with ESMTPS id pj10sm8192535pbb.46.2012.07.22.09.56.11 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 22 Jul 2012 09:56:12 -0700 (PDT)
Message-ID: <500C30AA.80101@gmail.com>
Date: Sun, 22 Jul 2012 08:56:10 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed IETF 95 Date Change
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com> <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com> <1342921093.7688.90.camel@gwz-laptop> <20120722014214.GK335@mip.aaaaa.org> <07F7D7DED63154409F13298786A2ADC90451F5A8@EXRAD5.ad.rad.co.il> <500447D9-AF64-4924-9DB1-0E5408318070@gmail.com>
In-Reply-To: <500447D9-AF64-4924-9DB1-0E5408318070@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 16:55:15 -0000

On 7/22/12 6:10 AM, Victor Kuarsingh wrote:
> It is my understanding that for these types of reasons (and others),
> folks who are adhering to Ramadan can eat while traveling and if they
> are sick.

I'd be a lot more comfortable with people describing/speaking up
for their own religious requirements.

> That said, moving the
> meeting further south would have helped as well vs. How far north
> Vancouver is.

I'm having to travel quite far south to get to Vancouver.  That
participants are spattered across the planet is part of the
scheduling challenge.

Melinda

From melinda.shore@gmail.com  Sun Jul 22 09:59: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 6E95421F86A5 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 09:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.57
X-Spam-Level: 
X-Spam-Status: No, score=-3.57 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gWYJPm7F4oNS for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 09:59:18 -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 A10D921F8697 for <ietf@ietf.org>; Sun, 22 Jul 2012 09:59:18 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so9764456pbc.31 for <ietf@ietf.org>; Sun, 22 Jul 2012 10:00:20 -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=jIzXtqh14FLJdyn8eK6+3eYrWeB8d6O0IIvUFY84YPg=; b=O/ObrrAITgwwu1kwTNV5jeLBQyVMy7i6aEWBJAmAp0vyixHtmDeeABi3yH9cuyWwtj fuHxn7cI+S1TiQylP7qg0uHkQ4TJsupaxTbmxSQPoXkQRU0C48o2YqRyAk0br2xXMobF ay/2RuPQiGBnnS6hDRSBhkXDM83EU4F2IcQeY9SSrpKVKrCB4ol4NsYbzTLYiBhNlY04 IVgmmUPLwcUVXKmNoDgybu7rjzlxBFCx6MTupWJqxEWbA5G46YSoz99V6d1d7VxnFFYo g7exy6o1P96r6lNa1O+/YaeNmlLP0aDJr/a8UXvHQB7KehSiUXUExslBBPU4O7ouKFI3 7K9A==
Received: by 10.68.238.135 with SMTP id vk7mr28832008pbc.80.1342976420712; Sun, 22 Jul 2012 10:00:20 -0700 (PDT)
Received: from spandex.local (66-230-87-150-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.87.150]) by mx.google.com with ESMTPS id kh1sm8201255pbc.23.2012.07.22.10.00.19 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 22 Jul 2012 10:00:19 -0700 (PDT)
Message-ID: <500C31A2.9050104@gmail.com>
Date: Sun, 22 Jul 2012 09:00:18 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed IETF 95 Date Change
References: <20120722160435.68743.qmail@joyce.lan>
In-Reply-To: <20120722160435.68743.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, 22 Jul 2012 16:59:19 -0000

On 7/22/12 8:04 AM, John Levine wrote:
> You're not going to find cool temperatures again in July or August
> unless you go as far south as Argentina or New Zealand.

Not only is there life north of the 60th parallel (N), there are
even hotels and restaurants and airports.  Anchorage is probably
large enough for an IETF meeting, although trying to hold a meeting
there during tourist season would almost certainly be a mistake.
But still.

Melinda


From ole@cisco.com  Sun Jul 22 10:21:42 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8117421F8557 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 10:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.525
X-Spam-Level: 
X-Spam-Status: No, score=-110.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OtQH9K3m4wOP for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 10:21:41 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id D7DAE21F8554 for <ietf@ietf.org>; Sun, 22 Jul 2012 10:21:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=971; q=dns/txt; s=iport; t=1342977764; x=1344187364; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=90XhBY/QDheSTJK+TXZELzWn69ZW0z0StbaBSBGZo7o=; b=XEoa0Nyjt0X2GTFxk5AloMXda6XvOO9ocy7ib9I1Iu51hsfL1lPRh7Hz 8p32Hlu/F7Cn5a6sp2qbCmskF/1CaPiB+VICb+m/wASkz0rqKrLRw2hzs qP1X54zOmC8gLxGTdf2DMdzeEfn3KwtDbJK12FIci1C8hDcVscf5hV5go w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFAFk2DFCrRDoH/2dsb2JhbABCA4UrtDGBB4IgAQEBAwESAQIlPwULCxguVwYTGQmHZQWfOYNIEJsgi00agxiDIQOITpJWhTKDGoEEYoJ/gT8
X-IronPort-AV: E=Sophos;i="4.77,633,1336348800"; d="scan'208";a="52684652"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 22 Jul 2012 17:22:43 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q6MHMhoo025364; Sun, 22 Jul 2012 17:22:43 GMT
Date: Sun, 22 Jul 2012 10:22:43 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Proposed IETF 95 Date Change
In-Reply-To: <500C31A2.9050104@gmail.com>
Message-ID: <alpine.OSX.2.01.1207221021190.83495@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20120722160435.68743.qmail@joyce.lan> <500C31A2.9050104@gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 17:21:42 -0000

I think you should look into the possibility. January maybe, or 
February, give our attendees some sense of what "cold and dark"
really means :-) Much more productive when you can't leave the
building...

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Sun, 22 Jul 2012, Melinda Shore wrote:

> On 7/22/12 8:04 AM, John Levine wrote:
> > You're not going to find cool temperatures again in July or August
> > unless you go as far south as Argentina or New Zealand.
> 
> Not only is there life north of the 60th parallel (N), there are
> even hotels and restaurants and airports.  Anchorage is probably
> large enough for an IETF meeting, although trying to hold a meeting
> there during tourist season would almost certainly be a mistake.
> But still.
> 
> Melinda
> 
> 
> 

From paul.hoffman@vpnc.org  Sun Jul 22 11:47:39 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 D993D21F863D for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 11:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UonNPwIdeWRm for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 11:47:39 -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 64F5E21F8648 for <ietf@ietf.org>; Sun, 22 Jul 2012 11:47:39 -0700 (PDT)
Received: from [10.20.30.102] (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 q6MHvOP8087682 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sun, 22 Jul 2012 10:57:25 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: Proposed IETF 95 Date Change
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <500C30AA.80101@gmail.com>
Date: Sun, 22 Jul 2012 11:48:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B69FC36D-4EE1-4132-9E43-D730093DD9AD@vpnc.org>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098712.6070304@gmail.com> <500A537E.7030505@cisco.com> <65992FFB-CEE6-4D0A-B6EC-9379063F4FAC@checkpoint.com> <CABkgnnUawpB6Z_jec+wwHk3SpNU=Tkt5J+YYNsME2YWWUHk4aA@mail.gmail.com> <1342921093.7688.90.camel@gwz-laptop> <20120722014214.GK335@mip.aaaaa.org> <07F7D7DED63154409F13298786A2ADC90451F5A8@EXRAD5.ad.rad.co.il> <500447D9-AF64-4924-9DB1-0E5408318070@gmail.com> <500C30AA.80101@gmail.com>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jul 2012 18:47:40 -0000

On Jul 22, 2012, at 9:56 AM, Melinda Shore wrote:

> I'd be a lot more comfortable with people describing/speaking up
> for their own religious requirements.

That's no fun. We're much more loquacious when we're talking about other =
peoples religions, other people's laws, other people's gender issues, =
other people's food sensitivities, and so on.=

From johnl@iecc.com  Sun Jul 22 12:24:41 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 BCDE621F863D for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:24:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.132
X-Spam-Level: 
X-Spam-Status: No, score=-111.132 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wFEpzodgsJQ for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:24:41 -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 A189321F862B for <ietf@ietf.org>; Sun, 22 Jul 2012 12:24:40 -0700 (PDT)
Received: (qmail 12559 invoked from network); 22 Jul 2012 19:25:41 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Jul 2012 19:25:41 -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=500c53b5.xn--hew.k1207; i=johnl@user.iecc.com; bh=sIQtB/CsrtXeBsY82MySa2RtQu/W/Jhx19IY756PpYU=; b=Mnamn33myjv2nb3oArt+H2wy6tKXmWUmv3nGrDjDqkHufK1vwlCoW+lYCeS/Ph7ck+dNvtl7/GIuwCIUsK3CdeZl3QLRu+Jx87IMN2YvJvIFYoAknG1e4MqZtKv+7JFToGsBATo+zlm//t0fdhbtQOtoNTdYIVfg+uyhTclJnZE=
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=500c53b5.xn--hew.k1207; olt=johnl@user.iecc.com; bh=sIQtB/CsrtXeBsY82MySa2RtQu/W/Jhx19IY756PpYU=; b=jAOS/cDr9++OkG1y+O6rhDdWugXYoefOh9BgLQlzJsuX/TMtlpTZbWabeUjbepinvSiJwvPDgOt4cpuBvjESP+yC2N7eyA2000ORgzYC6CFdUz7Ap0G93QRCUXMxLancZV+MStfNjKLxS+aNDHcuG7oqN1N1ajNKdJ1jIQkflIM=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 22 Jul 2012 19:25:19 -0000
Message-ID: <20120722192519.18622.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Proposed IETF 95 Date Change
In-Reply-To: <500C31A2.9050104@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, 22 Jul 2012 19:24:41 -0000

>> You're not going to find cool temperatures again in July or August
>> unless you go as far south as Argentina or New Zealand.
>
>Not only is there life north of the 60th parallel (N), there are
>even hotels and restaurants and airports.  Anchorage is probably
>large enough for an IETF meeting, although trying to hold a meeting
>there during tourist season would almost certainly be a mistake.
>But still.

I believe it, but remember that the issue was to minimize daylight fasting
during the North American summer.

Reykjavik is big enough, too, and has the advantage of being roughly
equally inconvenient to get to from North America and Europe.  We
could have the social event at the Blue Lagoon.

R's,
John

From marshall.eubanks@gmail.com  Sun Jul 22 12:37:03 2012
Return-Path: <marshall.eubanks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 138DA21F86A2 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:37:03 -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=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GDDLqzqpc+iP for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:37:02 -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 2D91C21F86A4 for <ietf@ietf.org>; Sun, 22 Jul 2012 12:37:02 -0700 (PDT)
Received: by bkty7 with SMTP id y7so4326042bkt.31 for <ietf@ietf.org>; Sun, 22 Jul 2012 12:38:03 -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=eZEmfVRo+Fq13jAe968ZwpWuA+P2loj5VEMd2+SqDUk=; b=def70tNilx4VLfQA9JPaD81qqGmMGkkD8+K4AK3tA/gBoIryBM2RTgBuXho4P34m5U 83JgZxWhmX5ncJ69/FATxGnYwW8+pdUNJhgi99kTZU1ITKsjFQvOkhiZdoX0kMumRUoP NSbE+w0WDyMc7+pkGEUR/lBhnns90PWL3jnujxi0EcnYwUvwKHKYw2cjHS79H1zq0Ahg 5FCuZvyZz8cVv7OAj4wquaaqh1F6XKSk/r8+g1zPqsw8ATOpp8YAy0z6xR76tATKu55Z pgPazUyUZS4ONTz8ReirrfILdW/jiLcRXXCV2E+tZV4kEc2t3+PD7c30x95k1fFQAZ+o RaBg==
MIME-Version: 1.0
Received: by 10.204.151.81 with SMTP id b17mr6489903bkw.95.1342985883780; Sun, 22 Jul 2012 12:38:03 -0700 (PDT)
Received: by 10.205.82.79 with HTTP; Sun, 22 Jul 2012 12:38:03 -0700 (PDT)
In-Reply-To: <20120722153118.60473.qmail@joyce.lan>
References: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@mail.gmail.com> <20120722153118.60473.qmail@joyce.lan>
Date: Sun, 22 Jul 2012 15:38:03 -0400
Message-ID: <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com>
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 19:37:03 -0000

On Sun, Jul 22, 2012 at 11:31 AM, John Levine <johnl@taugh.com> wrote:
>> Yes, we typically then point out that much of what they want is
>> available on line, and frequently negotiate with opposing counsel to
>> moderate demands for depositions, etc., but, in the end, we propose,
>> the judge and opposing counsel dispose. That won't change.
>
> I'd want to set the depo rate high enough that if someone has to be
> deposed, he or she will at least feel that the money makes up for
> the hassle.
>
> For people with unique skills or knowledge, $800/hr is not unusual.
> So long as the rate is published ahead of time, you're not going to
> get much argument.  ("Yes, we know it's high.  But we've already told
> you how to download stuff yourself for free.")
>

Please  note : out of pocket expenses (if someone has to travel to a
hearing, say) would be reimbursed, but
IETF volunteers will not be paid from these fees.

Regards
Marshall


> R's,
> John

From melinda.shore@gmail.com  Sun Jul 22 12:38:32 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 5AC1721F84D6 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.571
X-Spam-Level: 
X-Spam-Status: No, score=-3.571 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02En5h6zVlmL for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:38:31 -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 7667221F8496 for <ietf@ietf.org>; Sun, 22 Jul 2012 12:38:31 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so9923825pbc.31 for <ietf@ietf.org>; Sun, 22 Jul 2012 12:39:33 -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=v26V3nK+ZHeEkjYRTj7f54WY5Jy/3by3mUwoegLDxOI=; b=BIKufRXh05cE4/ySK7Q+nKM/mpvc5zPqDQz1PxUNNANITL495UaND0OO7+tE6kig2q sv0kutSsbB2HME1BWGTewtZPfNTmR6Cwd6xj+9fpgPsxhyMJCg6TkxRrOLcVvCtzsO+n OUTlktRn9ZU2tpO2iAi8k2yQqxro4fD2Pt8HK76wKEzarfcIYElrYuHARsmToDV9vniY x1OWcwI+hHr99Z3y+KbpYsCckZ9V3ZTIxED0UVungV7NKTVmcYJ8jXd0QixMW8yIvYJt NHN+m8hbCZAmbAdHV8LtSdnH7AMa2+YpoJaUlbFv6gfUyvTSFRtsOa8T+PBMW+iCSBXg Vk/w==
Received: by 10.68.225.231 with SMTP id rn7mr29612485pbc.13.1342985973841; Sun, 22 Jul 2012 12:39:33 -0700 (PDT)
Received: from spandex.local (66-230-87-150-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.87.150]) by mx.google.com with ESMTPS id sr8sm8387308pbc.61.2012.07.22.12.39.32 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 22 Jul 2012 12:39:33 -0700 (PDT)
Message-ID: <500C56F3.6090909@gmail.com>
Date: Sun, 22 Jul 2012 11:39:31 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Proposed IETF 95 Date Change
References: <20120722192519.18622.qmail@joyce.lan>
In-Reply-To: <20120722192519.18622.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 19:38:32 -0000

On 7/22/12 11:25 AM, John Levine wrote:
> I believe it, but remember that the issue was to minimize daylight fasting
> during the North American summer.

Moderate temperatures were thrown into the mix, which I guess provides
a pretty good illustration of the challenges of making everybody happy.
Frankly, I understand that some people have health challenges that
make it important to avoid very hot weather but for the most part I
think people should stop being such delicate flowers and just deal with
it (and I say this as someone who really, really dislikes hot weather).

At any rate, I'm really not sure what to do about the religious holiday
situation although I tend to agree that it might not be a terrible idea
to treat all religions equally, even if ultimately that means ignoring
all religious holidays for scheduling purposes.

Melinda

From cabo@tzi.org  Sun Jul 22 12:49:25 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 A867621F8683 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:49:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.468
X-Spam-Level: 
X-Spam-Status: No, score=-106.468 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1RA2cUSy5LD4 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:49:25 -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 D88A821F8681 for <ietf@ietf.org>; Sun, 22 Jul 2012 12:49:24 -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 q6MJoI4h015966; Sun, 22 Jul 2012 21:50:18 +0200 (CEST)
Received: from [192.168.217.117] (p54892CF3.dip.t-dialin.net [84.137.44.243]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C04E92C8; Sun, 22 Jul 2012 21:50:17 +0200 (CEST)
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com>
Date: Sun, 22 Jul 2012 21:50:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9EF2836F-B9C6-47BF-AAE9-87DE15574E95@tzi.org>
References: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@mail.gmail.com> <20120722153118.60473.qmail@joyce.lan> <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com>
To: Marshall Eubanks <marshall.eubanks@gmail.com>
X-Mailer: Apple Mail (2.1278)
Cc: 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: Sun, 22 Jul 2012 19:49:25 -0000

On Jul 22, 2012, at 21:38, Marshall Eubanks wrote:

> IETF volunteers will not be paid from these fees.

I've been following this discussion only with one ear, but, I can't =
figure out why somebody would volunteer to do this.

Gr=FC=DFe, Carsten


From johnl@taugh.com  Sun Jul 22 12:57:30 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 149A321F86A3 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:57:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level: 
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RexHUep+bEm9 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 12:57: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 3591321F866A for <ietf@ietf.org>; Sun, 22 Jul 2012 12:57:29 -0700 (PDT)
Received: (qmail 17024 invoked from network); 22 Jul 2012 19:58:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=427e.500c5b66.k1207; bh=WlzAtkYumyiUgSUaJ4HAkHea3Z9vkwuUMJgTmSbP7dc=; b=prXE6rF/HZ9EviCvwNAp9fuyuAFsQ5cM0pzc8jHLf57/ZKM/PwXNL9Xx/vdIpFg4HZuyDUdC4AmdNnm8YJ245jwtXZfNQ3lGIBVQnReJOaZN6+r6CxlwMeBTXAt4GEnOjIzHr45BlFuuo9pGZioZfdzk/DjsGgrjOQqYBpMnWZQ=
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=427e.500c5b66.k1207; bh=WlzAtkYumyiUgSUaJ4HAkHea3Z9vkwuUMJgTmSbP7dc=; b=gaIlu3TNAAbWOjoP43Ib3Pd7NW4vBuEAcrSZgsm+9OTzub51fhRP3rwAsAou8OfSoPFn7Xl8tw8vOtF33dKYkHIVRlPTDnAwcfINEij+Eeh9AnLSRKIeFfakWa0+Lp51UbY8toUl1kGnktxEFhPFYraIuRLx5upCea0g9fzMupU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 22 Jul 2012 19:58:08 -0000
Date: 22 Jul 2012 15:58:30 -0400
Message-ID: <alpine.BSF.2.00.1207221550590.17748@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Marshall Eubanks" <marshall.eubanks@gmail.com>
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
In-Reply-To: <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com>
References: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@mail.gmail.com> <20120722153118.60473.qmail@joyce.lan> <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 19:57:30 -0000

>> For people with unique skills or knowledge, $800/hr is not unusual.
>> So long as the rate is published ahead of time, you're not going to
>> get much argument.  ("Yes, we know it's high.  But we've already told
>> you how to download stuff yourself for free.")
>
> Please  note : out of pocket expenses (if someone has to travel to a
> hearing, say) would be reimbursed, but
> IETF volunteers will not be paid from these fees.

If you know, how often have people been deposed on behalf of the
IETF, and how long does it typically take?

My thought is that in a depo or trial, the other side pays both for the 
expenses and the time of the person being deposed, so it would be good 
idea to say up front here's what it'll cost if you want a live witness.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From johnl@taugh.com  Sun Jul 22 13:42:53 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 8AE1421F84F7 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 13:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CgJD7oz0pIRO for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 13:42:52 -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 80C3121F84F6 for <ietf@ietf.org>; Sun, 22 Jul 2012 13:42:52 -0700 (PDT)
Received: (qmail 25221 invoked from network); 22 Jul 2012 20:43:54 -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=6284.500c660a.k1207; bh=Q2fkoAyf6jDzrs1pKFZN+NmBkWNbzDQcwifL50mxWuY=; b=J9wBVY/1uE+cfVBbdohYNNQMFCMGRJ34heU0uOxujYR280ssDecu9t6Fn0QefRo8GJtLFAslOwdcMBpRBmFOVNo7iQW/j0obE1aqAYpHdeffu8iLnkGaIsXWWNK03hbr80bAijb1SSijY5pwxXKKpZ8QcKHVVkhvxho/zOn36fU=
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=6284.500c660a.k1207; bh=Q2fkoAyf6jDzrs1pKFZN+NmBkWNbzDQcwifL50mxWuY=; b=QsFz9ZduyPIOmz+LooDdTJ/qLybiQ2XsBUkjozi4F1cSEkAdFqPrLXyXhy7s6N5UIubVlwLAD0lOpXYtAWbUKeUR9uIa3kVsm8aFhjR/PoypBlfstXyjdQbOkvcdEFTZf8X7FMCDMsAsICKcDhuO7rrKiF+xR0nCTUgGYZiA8BM=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 22 Jul 2012 20:43:32 -0000
Date: 22 Jul 2012 16:43:54 -0400
Message-ID: <alpine.BSF.2.00.1207221642080.31418@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Scott O Bradner" <sob@sobco.com>
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
In-Reply-To: <06CAE00A-F7AF-4D6C-ACE4-0D8399C13F44@sobco.com>
References: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@mail.gmail.com> <20120722153118.60473.qmail@joyce.lan> <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com> <alpine.BSF.2.00.1207221550590.17748@joyce.lan> <06CAE00A-F7AF-4D6C-ACE4-0D8399C13F44@sobco.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: Sun, 22 Jul 2012 20:42:53 -0000

> I did it once - it took 2 or 3 hours *it was quite a while back and I do not remember)
>
> there were no significant expenses - the depo was in Boston & my only
> expense was a few hours parking - the depo was done in the office of the
> law firm that was providing the IETF with pro-bono legal services at the time

If the opposing party didn't pay you for your time in the depo, you did 
them an unnecessary favor.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From johnl@taugh.com  Sun Jul 22 13:57:00 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 C849221F8535 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 13:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kI7nEzMv5h+n for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 13:57:00 -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 C7A0C21F8534 for <ietf@ietf.org>; Sun, 22 Jul 2012 13:56:59 -0700 (PDT)
Received: (qmail 26804 invoked from network); 22 Jul 2012 20:58:01 -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=68b3.500c6959.k1207; bh=WrZJqeuCD7u1jQqHUvSYAKwFsGe72Vou7XnbhyylXKc=; b=ecoIHM5KuwEDGKHm9RYRj9m4MfOq7X1DBhDt2H4Ih/gAfZbJAq//2rK5AxRGGi/LFcJEa2E5NU3BXodxpKGH71xBpWl9bxwkDxBqtQq7F8UuxYqWd5owJPVFl3XVnbjFR0BnQXnzANHfVVREcrmDNcqmlJJW5G5opix+gUfTB6w=
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=68b3.500c6959.k1207; bh=WrZJqeuCD7u1jQqHUvSYAKwFsGe72Vou7XnbhyylXKc=; b=rPhDmhu0cNSyPNo3aNB905QAX8u3WDy3WsPfnh5ZFQGOXmsD62UzVOG1amlKIwJi53AzeFqoKHJD4GqHueklIMx1r+XJ/aX6MRiTdNOlfXpxSqBWR0qXyEB0e44MR/2Bv6CUx2shkdbpyUrFnQinS3tUitIb/bO8P+8R8u+rSxo=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 22 Jul 2012 20:57:39 -0000
Date: 22 Jul 2012 16:58:01 -0400
Message-ID: <alpine.BSF.2.00.1207221654200.31418@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Scott O Bradner" <sob@sobco.com>
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
In-Reply-To: <3B377A30-123B-4772-AAB8-FAA535FDD0BE@sobco.com>
References: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@mail.gmail.com> <20120722153118.60473.qmail@joyce.lan> <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com> <alpine.BSF.2.00.1207221550590.17748@joyce.lan> <06CAE00A-F7AF-4D6C-ACE4-0D8399C13F44@sobco.com> <alpine.BSF.2.00.1207221642080.31418@joyce.lan> <3B377A30-123B-4772-AAB8-FAA535FDD0BE@sobco.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: Sun, 22 Jul 2012 20:57:00 -0000

> I did not do them any favor - I did the IETF a favor (as the then ISOC VP for Standards)

Really, if you didn't make the opposing party pay for your time, you did 
them a favor. It's absolutely expected to pay hostile witnesses for their 
depo time. (If nobody mentioned it, why would they offer to pay if you 
were willing to do it for free?)

If it happens again, pick the highest rate you think you're worth and 
double it.  If you want, donate the money to the IETF trust and encourage 
them to use it for better cookies.

R's,
John

From dwm@xpasc.com  Sun Jul 22 14:00:42 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 014FE21F8587 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 14:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.985
X-Spam-Level: 
X-Spam-Status: No, score=-5.985 tagged_above=-999 required=5 tests=[AWL=-3.386, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OyPYRRBBEWqw for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 14:00:41 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2D621F854B for <ietf@ietf.org>; Sun, 22 Jul 2012 14:00:41 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id E0E8F40A22 for <ietf@ietf.org>; Sun, 22 Jul 2012 21:01:43 +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 q6ML1h7X005100 for <ietf@ietf.org>; Sun, 22 Jul 2012 14:01:43 -0700
Date: Sun, 22 Jul 2012 14:01:43 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
In-Reply-To: <alpine.BSF.2.00.1207221654200.31418@joyce.lan>
Message-ID: <alpine.LRH.2.01.1207221359180.5034@egate.xpasc.com>
References: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@mail.gmail.com> <20120722153118.60473.qmail@joyce.lan> <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com> <alpine.BSF.2.00.1207221550590.17748@joyce.lan> <06CAE00A-F7AF-4D6C-ACE4-0D8399C13F44@sobco.com> <alpine.BSF.2.00.1207221642080.31418@joyce.lan> <3B377A30-123B-4772-AAB8-FAA535FDD0BE@sobco.com> <alpine.BSF.2.00.1207221654200.31418@joyce.lan>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.52-geef5514
X-CLX-ID: a120AD3GD1et1vr-6M1401i
X-CLX-Spam: false
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: Sun, 22 Jul 2012 21:00:42 -0000

Yeah, with what the lawyers in the room are getting per hour, there is no
reason to volunteer as an expert wittness. Ever. Even if you are there
on behalf of the IETF, if the IETF prevails, they can only recover costs
they incurred and if they don't, make a donation. 

On Sun, 22 Jul 2012, John R Levine wrote:

> > I did not do them any favor - I did the IETF a favor (as the then ISOC VP
> > for Standards)
> 
> Really, if you didn't make the opposing party pay for your time, you did them
> a favor. It's absolutely expected to pay hostile witnesses for their depo
> time. (If nobody mentioned it, why would they offer to pay if you were willing
> to do it for free?)
> 
> If it happens again, pick the highest rate you think you're worth and double
> it.  If you want, donate the money to the IETF trust and encourage them to use
> it for better cookies.
> 
> R's,
> John
> 

From stephen.farrell@cs.tcd.ie  Sun Jul 22 15:34:00 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 3005321F864F; Sun, 22 Jul 2012 15:34:00 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZIEaLHbBcbVq; Sun, 22 Jul 2012 15:33:58 -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 B786E21F85C6; Sun, 22 Jul 2012 15:33:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id BA94F157E9A; Sun, 22 Jul 2012 23:33:54 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:subject:mime-version :user-agent:from:date:message-id:received:received: x-virus-scanned; s=cs; t=1342996434; bh=KFVm42J1lK5bRFuUh8JyZ+iM aTUN3CmIaI3V42VIhFk=; b=n2xboGdZhL8XK+WHpYCHdOqAnh2CtzMHjY5trY2h ULRxH3dnuEhInsUSoO0HxHPdolbSFVbActfFOYUwL2fDQsRiOxwY3mVGxDe5fm5+ U5Dq2kpc5QTuYIDbUjBOPd6CBYX2pZIxyHQDaJaPx6DvPIbQ8sc4dVMHhPw6yIHV U27UmZy8Xnj55tA0LRSA+C/mnULRWOdeKe1HhkVdcMOVgK67Khdj+RG/1IHNlXxs sCxyMTzeaqvdgMxv36NTGxmOmueI7Hmq7zjEh8tSOtsKZZsAR+xOd1EFsV5DWLbs KF/y3M0XQ766ZtF2R2vIleseywxIpvi0rThc/dpa9Z8/Kg==
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 HfbGbwtBY-eo; Sun, 22 Jul 2012 23:33:54 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.45.58.178]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 1C723157BFE; Sun, 22 Jul 2012 23:33:53 +0100 (IST)
Message-ID: <500C7FD1.4050408@cs.tcd.ie>
Date: Sun, 22 Jul 2012 23:33:53 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: "oauth@ietf.org" <oauth@ietf.org>, IETF-Discussion <ietf@ietf.org>
Subject: oauth-bearer and rfc 2617/httpbis authentication framework
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 22:34:00 -0000

Hi all,

I'd like to check that some recent minor changes to this
document [1] don't cause technical or process-grief.

The version [2] of the oauth bearer draft that underwent
IETF LC and IESG evaluation had a normative dependency
on the httpbis wg's authentication framework. [3]

After resolving IESG discuss positions the authors and
wg chairs felt that it would be better to replace the
normative reference to the httpbis wg draft [3] with one
to RFC 2617 [4] so that the OAuth drafts wouldn't be held
in the RFC editor queue waiting on the httpbis wg to get
done.

I believe there is no impact on interop resulting from
this change but there has been some disagreement about
making it and how it was made. After some offlist discussion
I think we now have an RFC editor note [5] that means that
the current scheme of referring to RFC 2617 is ok.

If there are no problems with this in the next week I'll
move the document [1] along as-is.

Thanks,
Stephen.

[1] http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer
[2] http://tools.ietf.org/html/draft-ietf-oauth-v2-bearer-18
[3] http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth
[4] http://tools.ietf.org/html/rfc2617
[5] https://datatracker.ietf.org/doc/draft-ietf-oauth-v2-bearer/writeup/


From stbryant@cisco.com  Mon Jul 23 00:39:03 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 8FC5921F86B3 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 00:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.568
X-Spam-Level: 
X-Spam-Status: No, score=-110.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kdA2oGPxBG5r for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 00:39:02 -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 B281F21F8691 for <ietf@ietf.org>; Mon, 23 Jul 2012 00:38:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=422; q=dns/txt; s=iport; t=1343029137; x=1344238737; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=jAaTUB6PMaPWfb+dMGgE6Cw7qZP8xxiWgrOsxYya9w4=; b=IAnB2/Mk0hwIDrigoRKF6eeoIzzUwjMPTgLh5rfL1QTzERlNnBr1deUZ CU1t24I3AsIvd7HTPkP72hyN8mk1hm2glwzE5t8FZeqFdHLbctR2O37ha kHIuTh4NIOs+Qx8vRteVhMweYfYXSKT/5JVyq1/UN03JEOoOE3kZoVimh Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFADb/DFCQ/khM/2dsb2JhbABFtVyDWIEHgiABAQEEEgECI0ARCxgJFg8JAwIBAgFFEwgBAR6Ha55yg0gQmzaLTYM3gxwDlUmFW4hMgQRigmA
X-IronPort-AV: E=Sophos;i="4.77,638,1336348800"; d="scan'208";a="75483844"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 23 Jul 2012 07:38:56 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q6N7cuqM018683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 23 Jul 2012 07:38:56 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q6N7csjc009315; Mon, 23 Jul 2012 08:38:55 +0100 (BST)
Message-ID: <500CFF8E.1090905@cisco.com>
Date: Mon, 23 Jul 2012 08:38:54 +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: ietf@ietf.org
Subject: Re: Updating RFC2119
References: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com> <500C29D1.7070605@gmail.com>
In-Reply-To: <500C29D1.7070605@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 07:39:03 -0000

On 22/07/2012 17:26, Melinda Shore wrote:
> On 7/22/12 3:17 AM, Abdussalam Baryun wrote:
>> IF x, THEN y:
>>
>> ELSE:
>>
>> ELSE IF:
>>
>> Please send your comments or advise, thanking you,
>
> Yes: you might try to explain what problem you think you're
> solving.
>
> Melinda
>
>
Preferable with a list of RFC text snippets that would have been
more readable if these keywords had been used.

Stewart

From ggx@gigix.net  Mon Jul 23 00:42:25 2012
Return-Path: <ggx@gigix.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D76621F86D5 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 00:42: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRmAyvCWBkyh for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 00:42:24 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id AC29821F86C5 for <ietf@ietf.org>; Mon, 23 Jul 2012 00:42:24 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so5639732ggn.31 for <ietf@ietf.org>; Mon, 23 Jul 2012 00:42:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=rVVsq80iddFjgv5s9tTW6vJZ842V/Y7X8n5O4i7xKPg=; b=WjYB6TVvTOEDH0VV+o2uEAoTFLnZkuVv/lgFyHi/S1GMd8F8Cd9bo1Q9HmakQwtLBG trBUitb1q+dCuB1EP/DEKwjOrCJ0Hj/qVAOMXMvROwzJxgPG+22hqu8xY4C3S0nOk3jR Rz5Pvltlk0PXYQQucSNf8r2sDWbEHKxndTrgrcQAjjYqdH+pzSMpZbr2Y8iSid3QconI 0g3hONIM3N3bUgQZ6Z3rRzzNZzA6rdcqpQZVMfFMhS4+P/8FLkL9qUDpPWHYkeu2iZUL AYJLhwF7pITfAZ56osICYV1twD2JTXvLU+CotKWwXaNVmQGku61tBJjJrqGO7vH/U9/j +5Nw==
Received: by 10.236.154.2 with SMTP id g2mr3255866yhk.29.1343029344188; Mon, 23 Jul 2012 00:42:24 -0700 (PDT)
Received: from ?IPv6:2001:660:330f:a4:81fa:61fc:b91:5f6? ([2001:660:330f:a4:81fa:61fc:b91:5f6]) by mx.google.com with ESMTPS id g15sm2112728anl.19.2012.07.23.00.42.22 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 23 Jul 2012 00:42:23 -0700 (PDT)
Subject: Re: Proposed IETF 95 Date Change
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <50098901.7090009@bogus.com>
Date: Mon, 23 Jul 2012 09:42:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <62E31CBF-190F-4FB3-94FC-1CEB318F6C84@gigix.net>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <50098901.7090009@bogus.com>
To: Joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1278)
X-Gm-Message-State: ALoCoQlB9CjyKizAptQpOMnM1NLsxJZLPAeS6FJ7cVyAl2b9/pYri43u4ap94ajvabcikXnTJLhW
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 07:42:25 -0000

On Jul 20, 2012, at 18:36 , Joel jaeggli wrote:

> On 7/20/12 09:06 , IETF Administrative Director wrote:
>> The IAOC is seeking community feedback on a proposed date change for =
IETF 95
>> scheduled for March 2016.
>>=20
>> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 =
March is Easter.
>>=20
>> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 =
and would like=20
>> feedback on those dates before making a decision.  Comments =
appreciated to ietf@ietf.org=20
>> by 6 August 2012.
>=20
> 20 march is palm sunday on the western calender.
>=20
> If one's a conflict presumably the other is too...
>=20

True, but if I can choose I would say 20-25 is better...

L.



>> Ray Pelletier
>> IETF Administrative Director
>>=20
>=20


From julian.reschke@gmx.de  Mon Jul 23 00:57:14 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 E875921F8694 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 00:57:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.136
X-Spam-Level: 
X-Spam-Status: No, score=-105.136 tagged_above=-999 required=5 tests=[AWL=-2.538, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8rtyr6jfN5z9 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 00:57:14 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id E827A21F8517 for <ietf@ietf.org>; Mon, 23 Jul 2012 00:57:13 -0700 (PDT)
Received: (qmail invoked by alias); 23 Jul 2012 07:57:12 -0000
Received: from p5DD97081.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.112.129] by mail.gmx.net (mp069) with SMTP; 23 Jul 2012 09:57:12 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+Cy2Bcl3+Crwy6BdDcCRFiSgTPGXsCs/AA/hZ6Ec yCG9btavvqelDY
Message-ID: <500D03C9.9030305@gmx.de>
Date: Mon, 23 Jul 2012 09:56:57 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [OAUTH-WG] oauth-bearer and rfc 2617/httpbis authentication framework
References: <500C7FD1.4050408@cs.tcd.ie>
In-Reply-To: <500C7FD1.4050408@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "oauth@ietf.org" <oauth@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 07:57:15 -0000

On 2012-07-23 00:33, Stephen Farrell wrote:
>
> Hi all,
>
> I'd like to check that some recent minor changes to this
> document [1] don't cause technical or process-grief.
>
> The version [2] of the oauth bearer draft that underwent
> IETF LC and IESG evaluation had a normative dependency
> on the httpbis wg's authentication framework. [3]
>
> After resolving IESG discuss positions the authors and
> wg chairs felt that it would be better to replace the
> normative reference to the httpbis wg draft [3] with one
> to RFC 2617 [4] so that the OAuth drafts wouldn't be held
> in the RFC editor queue waiting on the httpbis wg to get
> done.
>
> I believe there is no impact on interop resulting from
> this change but there has been some disagreement about
> making it and how it was made. After some offlist discussion
> I think we now have an RFC editor note [5] that means that
> the current scheme of referring to RFC 2617 is ok.
> ...

Quoting:

> NEW:
>
>    The "Authorization" header for this scheme follows the usage
>    of the Basic scheme [RFC2617]. Note that, as with Basic, this
>    is compatible with the the general authentication framework
>    being developed for HTTP 1.1 [I-D.ietf-httpbis-p7-auth], though
>    does not follow the preferred practice outlined therein in
>    order to reflect existing deployments. The syntax for Bearer
>    credentials is as follows:

That helps, but it still hides the fact that the syntax is not 
compatible with the RFC 2617 framework.

Also, s/header/header field/

Proposal:

"The syntax of the "Authorization" header field for this scheme follows 
the usage of the Basic scheme defined in Section 2 of [RFC2617]. Note 
that, as with Basic, it does not conform to the generic syntax defined 
in Section 1.2 of [RFC2617], but that it is compatible with the the 
general authentication framework being developed for HTTP 1.1 
[I-D.ietf-httpbis-p7-auth], although it does not follow the preferred 
practice outlined therein in order to reflect existing deployments.

The syntax for Bearer credentials is as follows: ..."

Best regards, Julian



From henk.uijterwaal@gmail.com  Mon Jul 23 01:08:26 2012
Return-Path: <henk.uijterwaal@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8DF921F86C3 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 01:08: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bX2uZTxbzrDb for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 01:08:26 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 000F321F8535 for <ietf@ietf.org>; Mon, 23 Jul 2012 01:08:25 -0700 (PDT)
Received: by yhq56 with SMTP id 56so5660004yhq.31 for <ietf@ietf.org>; Mon, 23 Jul 2012 01:08:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=N5cDSITB195FShimYxNt9g1YTRZAcYgEwiO1baZnxrg=; b=cQBfBiwVPKjo0YS6qZ9qmWgsmlm4RyuyW1KlmEqZoIJCOCyQdho6qW2AN6pwVjSzz8 wgFsAry1Lo5K6bUDWKt0qUH3IvGmu3fmmh9FZSf75XAj1DFZdPNEF56cwmHlfFL/7gK/ 1Ikl1k1CcZCy+vv7PB+ueXX8DnlOvxmyFSXvjBSYVvL6rg0SmndprolAW1K8upie+klr A4LPYLI1Oe2znSDy6NYyUA98Kmg/dtS8kPsyWsGTHw4qVqhKNGxKRt8vSJ7WCgrpZsyf /ONde1+5uhJnAAPt33zUgOay4PZhGZEIsGW7vWa+wjXXEizr+/2JG5ksuc08ipEhxFEy zP0g==
Received: by 10.236.145.40 with SMTP id o28mr13696760yhj.70.1343030905563; Mon, 23 Jul 2012 01:08:25 -0700 (PDT)
Received: from geir.local ([2001:980:1203:1:e6ce:8fff:fe11:e7a8]) by mx.google.com with ESMTPS id o25sm23938487yhm.14.2012.07.23.01.08.23 (version=SSLv3 cipher=OTHER); Mon, 23 Jul 2012 01:08:24 -0700 (PDT)
Message-ID: <500D0674.2090303@gmail.com>
Date: Mon, 23 Jul 2012 10:08:20 +0200
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed IETF 95 Date Change
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
In-Reply-To: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: henk@uijterwaal.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 08:08:27 -0000

On 20/07/2012 18:06, IETF Administrative Director wrote:
> The IAOC is seeking community feedback on a proposed date change for IETF 95
> scheduled for March 2016.
> 
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is Easter.
> 
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and would like 
> feedback on those dates before making a decision.  Comments appreciated to ietf@ietf.org 
> by 6 August 2012.
> 
> Ray Pelletier
> IETF Administrative Director

If March 27 is Easter, then I'm not sure if the change solves the problem.
Sunday March 20 is Palm Sunday, the Thursday and Friday before Easter (as
well as the Monday after) are religious holidays in many European countries.

If you want to avoid a clash with Easter and related days, then one will
have to move the meeting to either the week of 13-18 March, or the week of
3-8 April.

Henk



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

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

From glenzorn@gmail.com  Mon Jul 23 01:56: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 CEA4221F8687 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 01:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BlwPhFzSjCEL for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 01:56:25 -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 4082B21F8683 for <ietf@ietf.org>; Mon, 23 Jul 2012 01:56:25 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so10883330pbc.31 for <ietf@ietf.org>; Mon, 23 Jul 2012 01:56:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=NWmasZe67mDaoq71x9U5Vt2H8hLjtKXHHfsNsso2xYI=; b=cMWoBx+d/98TRhEA0pzqtdJ8gES3vLDebQk+2CnPvFRB7SF4b6fc5xNXDwl30+jfQa 0Eehv+dFPo0GF5ieiJ9lX8n3ghluVlL4ph9DC0dNEk9HH60edDSU7RvrGpqNQWlBZdi0 u3jxWkBUk3TpaGGU4lJogz+6TLt5ftuBnd6TX1euMpFtnVwdh3pe1DYRJ+cBwbfLoOvN xDe3AL5nODy/Rp1oOJpBDIvh2DsfZPKMMODd1jD7aCDh/TbFQt+32Vjptth/xjiB7+y5 tLxYqp8YGatVPdk98aS1T5WuhujcLCL0OvrXX25w5o2PHQTZN44FhMt+ZUncM3sRa9Iw hEng==
Received: by 10.68.138.169 with SMTP id qr9mr33460218pbb.27.1343033784944; Mon, 23 Jul 2012 01:56:24 -0700 (PDT)
Received: from [192.168.0.102] (ppp-110-169-218-132.revip5.asianet.co.th. [110.169.218.132]) by mx.google.com with ESMTPS id hf5sm9580016pbc.4.2012.07.23.01.56.21 (version=SSLv3 cipher=OTHER); Mon, 23 Jul 2012 01:56:23 -0700 (PDT)
Subject: Re: Proposed IETF 95 Date Change
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <500D0674.2090303@gmail.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <500D0674.2090303@gmail.com>
Content-Type: multipart/alternative; boundary="=-9/NdvaWGexJJxdWuH+C/"
Organization: Network Zen
Date: Mon, 23 Jul 2012 15:56:19 +0700
Message-ID: <1343033779.7688.131.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jul 2012 08:56:26 -0000

--=-9/NdvaWGexJJxdWuH+C/
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Mon, 2012-07-23 at 10:08 +0200, Henk Uijterwaal wrote:

> On 20/07/2012 18:06, IETF Administrative Director wrote:
> > The IAOC is seeking community feedback on a proposed date change for IETF 95
> > scheduled for March 2016.
> > 
> > Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is Easter.
> > 
> > The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and would like 
> > feedback on those dates before making a decision.  Comments appreciated to ietf@ietf.org 
> > by 6 August 2012.
> > 
> > Ray Pelletier
> > IETF Administrative Director
> 
> If March 27 is Easter, then I'm not sure if the change solves the problem.
> Sunday March 20 is Palm Sunday, the Thursday and Friday before Easter (as
> well as the Monday after) are religious holidays in many European countries.
> 
> If you want to avoid a clash with Easter and related days, then one will
> have to move the meeting to either the week of 13-18 March, or the week of
> 3-8 April.


I agree, and prefer the former.


> 
> Henk
> 
> 
> 



--=-9/NdvaWGexJJxdWuH+C/
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Mon, 2012-07-23 at 10:08 +0200, Henk Uijterwaal wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
On 20/07/2012 18:06, IETF Administrative Director wrote:
&gt; The IAOC is seeking community feedback on a proposed date change for IETF 95
&gt; scheduled for March 2016.
&gt; 
&gt; Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is Easter.
&gt; 
&gt; The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and would like 
&gt; feedback on those dates before making a decision.  Comments appreciated to <A HREF="mailto:ietf@ietf.org">ietf@ietf.org</A> 
&gt; by 6 August 2012.
&gt; 
&gt; Ray Pelletier
&gt; IETF Administrative Director

If March 27 is Easter, then I'm not sure if the change solves the problem.
Sunday March 20 is Palm Sunday, the Thursday and Friday before Easter (as
well as the Monday after) are religious holidays in many European countries.

If you want to avoid a clash with Easter and related days, then one will
have to move the meeting to either the week of 13-18 March, or the week of
3-8 April.
</PRE>
</BLOCKQUOTE>
<BR>
I agree, and prefer the former.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

Henk



</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-9/NdvaWGexJJxdWuH+C/--


From abdussalambaryun@gmail.com  Mon Jul 23 04:08:10 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D40321F8699 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 04:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.454
X-Spam-Level: 
X-Spam-Status: No, score=-3.454 tagged_above=-999 required=5 tests=[AWL=0.145,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzsYLG-Ytk8X for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 04:08:08 -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 57FBD21F8681 for <ietf@ietf.org>; Mon, 23 Jul 2012 04:08:08 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so4952465vcb.31 for <ietf@ietf.org>; Mon, 23 Jul 2012 04:08:07 -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:content-transfer-encoding; bh=j6cgDMjMxpHpArnYKQFFYzBcQ6SI/onWN3Nr797DaAY=; b=xLoH9RyHLBSH1OvlwXaGPcdRY2N4Io01S0mjGtiKGbeeHqp08HLXWaDHyBr1/PA3vJ bviRC2HDseLa/kWKi+cMcKvITXTLUhy5ca0qqEZ4BNdc/ZQB+fRxitugOVBxsDgL9sWt 32SjV7NwX5X+CvxM9wTOSpt0TcxrmzwwY7OC/o13NJmBD6/nAtP3ZqVO/j1VgOvd7HRF M5pdOeG+mp1D6y35HDoRBE66UHKFkys3fuiuFJsgUBmFODx6tZYlXjmzRS+y2Pw6exf4 zQB+pQ433NGlHNODYPZgRA74ZreiPH74gMTPye6rCYCZPfUj0hLaiwIXu4Xphwz+ka2Z 004w==
MIME-Version: 1.0
Received: by 10.220.150.138 with SMTP id y10mr11913370vcv.73.1343041687774; Mon, 23 Jul 2012 04:08:07 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Mon, 23 Jul 2012 04:08:07 -0700 (PDT)
In-Reply-To: <CAPv4CP95Rhma3reOvrWfrWQE_mqsyY8bL2EvkZq5hD6gbyf_ow@mail.gmail.com>
References: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com> <CAPv4CP95Rhma3reOvrWfrWQE_mqsyY8bL2EvkZq5hD6gbyf_ow@mail.gmail.com>
Date: Mon, 23 Jul 2012 13:08:07 +0200
Message-ID: <CADnDZ89uM25K=8M5KmkFva0V4SHQGUQ2e7nksiv26Pt=WpSrWA@mail.gmail.com>
Subject: Re: Updating RFC2119
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 11:08:10 -0000

Hi Stewart,

Usually the (IF x, THEN y) means if x happens then y is a MUST, so I
don't see the important reflection of a MUST in many documentation
when using *if*. That is why I prefer to find requirements more easily
while skimming any IETF document, the MUST, SHOULD, and IF, these are
important requirement words in specifications. Please see below as
examples per your requested.

---------------------------------------------------------------------------=
---------------------------
RFC4861>page36> IMO suggest to use IF, THEN

If no entry exists, the sender creates one, sets its state
to INCOMPLETE, initiates Address Resolution, and then queues the data
packet pending completion of address resolution.
---------------------------------------------------------------------------=
---------------------------
RFC4861>page 49> IMO suggest to use IF and ELSE IF

If the router already has a Neighbor Cache entry for the
solicitation=92s sender, the solicitation contains a Source Link-Layer
Address option, and the received link-layer address differs from that
already in the cache, then the link-layer address SHOULD be updated
in the appropriate Neighbor Cache entry, and its reachability state
MUST also be set to STALE. If there is no existing Neighbor Cache
entry for the solicitation=92s sender, the router creates one, installs
the link- layer address and sets its reachability state to STALE as
specified in Section 7.3.3. If there is no existing Neighbor Cache
entry and no Source Link-Layer Address option was present in the
solicitation, the router may respond with either a multicast or a
unicast router advertisement. Whether or not a Source Link-Layer
Address option is provided, if a Neighbor Cache entry for the
solicitation=92s sender exists (or is created) the entry=92s IsRouter
flag MUST be set to FALSE.
---------------------------------------------------------------------------=
-------
RFC5715>page 19>

If R changes before T, then a loop will form
around R, T, and S.
---------------------------------------------------------------------------=
--------
RFC6052> page 10> suggest delete *will* and to add as IF, THEN

If a packet bound to
192.0.2.33 reaches the translator, the destination address will be
translated to 2001:db8:122:344:c0:2:2100::, and the packet will be
routed towards R and then to A.
---------------------------------------------------------------------------=
--------

There are many examples that ignore the use of IF , THEN requirements,
which I suggest to be in the I-D update of RFC2119 that I working on
and will submit in 30 July,

Regards

Abdussalam Baryun
University of Glamorgan, UK
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D

>Preferable with a list of RFC text snippets that would have been
>more readable if these keywords had been used.

>Stewart


> On Sun, Jul 22, 2012 at 7:17 AM, Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>> Hi All,
>>
>> I am working on an I-D which is intended as proposed standard but need
>> some addition requirement language. Therefore, I want to propose to
>> write a draft to update RFC2119 to add some other language requirement
>> as below:
>>
>> IF x, THEN y:
>>
>> ELSE:
>>
>> ELSE IF:
>>
>> Please send your comments or advise, thanking you,
>
> That doesn't have to be in 2119.  Lots of RFCs have pseudocode at
> various levels of rigor.  Just look around at some protocol specs for
> examples.
>

From stephen.farrell@cs.tcd.ie  Mon Jul 23 04:26:58 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 B9D5621F86EF for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 04:26:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.71
X-Spam-Level: 
X-Spam-Status: No, score=-103.71 tagged_above=-999 required=5 tests=[AWL=-1.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9sngBl1U4pjE for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 04:26:58 -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 A211D21F84F2 for <ietf@ietf.org>; Mon, 23 Jul 2012 04:26:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 05A0A157E9C; Mon, 23 Jul 2012 12:26:57 +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=1343042816; bh=/xg7Q/jr/OizG7 tOnOg+78yhbwru0PksILx8TIU6n1Y=; b=ZLaQXCngLtGX68Yk/Vf9dH6f4U55+7 g2PXoiSzYXiB8ti0WKlZ1V0zs+0Ow+usoJNpv8VSRZfil01DAkA1UK8CC/v/HVo8 PQgp0TXnKv29qMz3STeKe0mcDqJDdvcdjanmHXwqJACRYaTSCvqY7OWffbhWeb0C +2mx7ak1hKaOt5HM8zqiHm4GSTNYObhX2DDc22HT6gdgzaQOisRvtR9ag32ICM+n JOmMwokKnnytzAsgW9FezXibzW0h8LrXmUANYSUaVCiQdFE7VG+4LdVkYISoIlqK H5CgZIn7vtCMCDErLIQFSshWHj1cGzBVR8ffW/P98F5qoCrmcvFV6Vsg==
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 zaQYqsopiuez; Mon, 23 Jul 2012 12:26:56 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.45.58.178]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 72715157B8D; Mon, 23 Jul 2012 12:26:56 +0100 (IST)
Message-ID: <500D3500.4080003@cs.tcd.ie>
Date: Mon, 23 Jul 2012 12:26:56 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Updating RFC2119
References: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com> <CAPv4CP95Rhma3reOvrWfrWQE_mqsyY8bL2EvkZq5hD6gbyf_ow@mail.gmail.com> <CADnDZ89uM25K=8M5KmkFva0V4SHQGUQ2e7nksiv26Pt=WpSrWA@mail.gmail.com>
In-Reply-To: <CADnDZ89uM25K=8M5KmkFva0V4SHQGUQ2e7nksiv26Pt=WpSrWA@mail.gmail.com>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 11:26:58 -0000

I'd encourage you to not try change 2119.

Instead, add whatever new definitions you feel
you need to your own draft that addresses some
technical, and not process, topic.

If people find your new definitions useful they'll
say and if enough of that happens they'll be
included in a 2119bis whenever that's done.

S.

On 07/23/2012 12:08 PM, Abdussalam Baryun wrote:
> Hi Stewart,
> 
> Usually the (IF x, THEN y) means if x happens then y is a MUST, so I
> don't see the important reflection of a MUST in many documentation
> when using *if*. That is why I prefer to find requirements more easily
> while skimming any IETF document, the MUST, SHOULD, and IF, these are
> important requirement words in specifications. Please see below as
> examples per your requested.
> 
> ------------------------------------------------------------------------------------------------------
> RFC4861>page36> IMO suggest to use IF, THEN
> 
> If no entry exists, the sender creates one, sets its state
> to INCOMPLETE, initiates Address Resolution, and then queues the data
> packet pending completion of address resolution.
> ------------------------------------------------------------------------------------------------------
> RFC4861>page 49> IMO suggest to use IF and ELSE IF
> 
> If the router already has a Neighbor Cache entry for the
> solicitation’s sender, the solicitation contains a Source Link-Layer
> Address option, and the received link-layer address differs from that
> already in the cache, then the link-layer address SHOULD be updated
> in the appropriate Neighbor Cache entry, and its reachability state
> MUST also be set to STALE. If there is no existing Neighbor Cache
> entry for the solicitation’s sender, the router creates one, installs
> the link- layer address and sets its reachability state to STALE as
> specified in Section 7.3.3. If there is no existing Neighbor Cache
> entry and no Source Link-Layer Address option was present in the
> solicitation, the router may respond with either a multicast or a
> unicast router advertisement. Whether or not a Source Link-Layer
> Address option is provided, if a Neighbor Cache entry for the
> solicitation’s sender exists (or is created) the entry’s IsRouter
> flag MUST be set to FALSE.
> ----------------------------------------------------------------------------------
> RFC5715>page 19>
> 
> If R changes before T, then a loop will form
> around R, T, and S.
> -----------------------------------------------------------------------------------
> RFC6052> page 10> suggest delete *will* and to add as IF, THEN
> 
> If a packet bound to
> 192.0.2.33 reaches the translator, the destination address will be
> translated to 2001:db8:122:344:c0:2:2100::, and the packet will be
> routed towards R and then to A.
> -----------------------------------------------------------------------------------
> 
> There are many examples that ignore the use of IF , THEN requirements,
> which I suggest to be in the I-D update of RFC2119 that I working on
> and will submit in 30 July,
> 
> Regards
> 
> Abdussalam Baryun
> University of Glamorgan, UK
> ==================================
> 
>> Preferable with a list of RFC text snippets that would have been
>> more readable if these keywords had been used.
> 
>> Stewart
> 
> 
>> On Sun, Jul 22, 2012 at 7:17 AM, Abdussalam Baryun
>> <abdussalambaryun@gmail.com> wrote:
>>> Hi All,
>>>
>>> I am working on an I-D which is intended as proposed standard but need
>>> some addition requirement language. Therefore, I want to propose to
>>> write a draft to update RFC2119 to add some other language requirement
>>> as below:
>>>
>>> IF x, THEN y:
>>>
>>> ELSE:
>>>
>>> ELSE IF:
>>>
>>> Please send your comments or advise, thanking you,
>>
>> That doesn't have to be in 2119.  Lots of RFCs have pseudocode at
>> various levels of rigor.  Just look around at some protocol specs for
>> examples.
>>
> 
> 

From stephen.farrell@cs.tcd.ie  Mon Jul 23 04:33:58 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 E89E721F8710; Mon, 23 Jul 2012 04:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.571
X-Spam-Level: 
X-Spam-Status: No, score=-103.571 tagged_above=-999 required=5 tests=[AWL=-0.972, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nA0NKqq9Q7Lj; Mon, 23 Jul 2012 04:33: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 3EDF721F8712; Mon, 23 Jul 2012 04:33:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 9CADA157E9D; Mon, 23 Jul 2012 12:33:56 +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=1343043236; bh=zlZVW7JnCAAOdA FCo3QjL6Cwgi5N0InfZKwshhb1c08=; b=Rz+B7GlBMZcglxfCDggSX5w/QjKA/j 4IeJEOb+ilqnziqo7EW42A6CASy1BzEZvCQrPphNIGj69ZoZ2Q0QrI2d3zZFvzwc 2NNeLApyqYoTo8UFoNh84WiuYN5p7IEBICyofrgl4Helh3qyylgmp4KJcTcEPzem tnid7Ot41Mq2a+GFsSeFMx/zafZRGWjemqDZ5kcUchp+CPaN3XzKqcQ5IBjLv1qR d8/YToOceD8HZ7oYznetIA1VZC3FQYSt7Boto+M7gWuf0/Zt9yuFCRugmOx1QAfA UUWh53HsLEm9tu4oy5KFCcPjGcaEXxyRU1lNpucAyZcOpJKiVFVtYRrQ==
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 eK+TMG3t9T04; Mon, 23 Jul 2012 12:33:56 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.45.58.178]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id B4F3A157B8D; Mon, 23 Jul 2012 12:33:49 +0100 (IST)
Message-ID: <500D369B.2070603@cs.tcd.ie>
Date: Mon, 23 Jul 2012 12:33:47 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [OAUTH-WG] oauth-bearer and rfc 2617/httpbis authentication framework
References: <500C7FD1.4050408@cs.tcd.ie> <500D03C9.9030305@gmx.de>
In-Reply-To: <500D03C9.9030305@gmx.de>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "oauth@ietf.org" <oauth@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 11:33:59 -0000

Hiya,

On 07/23/2012 08:56 AM, Julian Reschke wrote:
> On 2012-07-23 00:33, Stephen Farrell wrote:
>>
>> Hi all,
>>
>> I'd like to check that some recent minor changes to this
>> document [1] don't cause technical or process-grief.
>>
>> The version [2] of the oauth bearer draft that underwent
>> IETF LC and IESG evaluation had a normative dependency
>> on the httpbis wg's authentication framework. [3]
>>
>> After resolving IESG discuss positions the authors and
>> wg chairs felt that it would be better to replace the
>> normative reference to the httpbis wg draft [3] with one
>> to RFC 2617 [4] so that the OAuth drafts wouldn't be held
>> in the RFC editor queue waiting on the httpbis wg to get
>> done.
>>
>> I believe there is no impact on interop resulting from
>> this change but there has been some disagreement about
>> making it and how it was made. After some offlist discussion
>> I think we now have an RFC editor note [5] that means that
>> the current scheme of referring to RFC 2617 is ok.
>> ...
> 
> Quoting:
> 
>> NEW:
>>
>>    The "Authorization" header for this scheme follows the usage
>>    of the Basic scheme [RFC2617]. Note that, as with Basic, this
>>    is compatible with the the general authentication framework
>>    being developed for HTTP 1.1 [I-D.ietf-httpbis-p7-auth], though
>>    does not follow the preferred practice outlined therein in
>>    order to reflect existing deployments. The syntax for Bearer
>>    credentials is as follows:
> 
> That helps, but it still hides the fact that the syntax is not
> compatible with the RFC 2617 framework.

"hides" isn't a goal:-)

> Also, s/header/header field/
> 
> Proposal:
> 
> "The syntax of the "Authorization" header field for this scheme follows
> the usage of the Basic scheme defined in Section 2 of [RFC2617]. Note
> that, as with Basic, it does not conform to the generic syntax defined
> in Section 1.2 of [RFC2617], but that it is compatible with the the
> general authentication framework being developed for HTTP 1.1
> [I-D.ietf-httpbis-p7-auth], although it does not follow the preferred
> practice outlined therein in order to reflect existing deployments.
> 
> The syntax for Bearer credentials is as follows: ..."

That looks better. I've updated the RFC editor note to
use your text.

Thanks,
S.

> 
> Best regards, Julian
> 
> 
> 
> 

From abdussalambaryun@gmail.com  Mon Jul 23 05:14: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 61BD921F8683 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 05:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.454
X-Spam-Level: 
X-Spam-Status: No, score=-3.454 tagged_above=-999 required=5 tests=[AWL=0.145,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7R-Hrhjq4O00 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 05:14:14 -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 DAB9621F8616 for <ietf@ietf.org>; Mon, 23 Jul 2012 05:14:13 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so5008618vcb.31 for <ietf@ietf.org>; Mon, 23 Jul 2012 05:14:13 -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:content-transfer-encoding; bh=XqD8LRG5GHvd2FNZ+9jHZyE+6S8AnFZL1RzlEt2OyNg=; b=RUx26pDc4YoQzEOEsUPc0tqs4saK79CNFgDQrM8sx8oPWxWgO7BeYrB/NpleSLUo1n Lwh+pqBAq+hK0TsQBhkZJwv2EH6NyYThXFa/s8jgLJqq251zgyxj5Wx8mFWXrSg7nOTc IXAwkP3VZjXCeiu4qD0Ippzt25PCoO3dqZWvUfxoQF2wgJyK5Eza0iUDlnkgIyXYdriR BcqIvMiO+bY2MUzi0FSF2b9oFcpBs3Kw9C8w7w5t7Ck1n2X/cGDvTVMTWcL5J1r3kFcO UglJz/urHrdZlP91e2GVIDnLe55whfHpO44grXMn3GbLReigDnGokf/NRwKhUeqD9qWC k16A==
MIME-Version: 1.0
Received: by 10.220.149.131 with SMTP id t3mr12135870vcv.1.1343045653318; Mon, 23 Jul 2012 05:14:13 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Mon, 23 Jul 2012 05:14:13 -0700 (PDT)
In-Reply-To: <500D3500.4080003@cs.tcd.ie>
References: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com> <CAPv4CP95Rhma3reOvrWfrWQE_mqsyY8bL2EvkZq5hD6gbyf_ow@mail.gmail.com> <CADnDZ89uM25K=8M5KmkFva0V4SHQGUQ2e7nksiv26Pt=WpSrWA@mail.gmail.com> <500D3500.4080003@cs.tcd.ie>
Date: Mon, 23 Jul 2012 14:14:13 +0200
Message-ID: <CADnDZ89XLoQ6spu7aVyWj8SHE4POEcFVjykAimBnQMUHbwVoyg@mail.gmail.com>
Subject: Re: Updating RFC2119
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=windows-1252
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: Mon, 23 Jul 2012 12:14:15 -0000

comments in line
>
> I'd encourage you to not try change 2119.

thanks for your comment
>
> Instead, add whatever new definitions you feel
> you need to your own draft that addresses some
> technical, and not process, topic.
>
I agree that I will need to add to the technical draft for now.

> If people find your new definitions useful they'll
> say and if enough of that happens they'll be
> included in a 2119bis whenever that's done.
>

this is the reason for this thread to see the feedback of the
community including me (at this time and the comings) and IMO the
submission of the I-D to update RFC2119 that includes new definition
may help the discussion, in the end the community will decide

AB
=3D=3D=3D
>
> On 07/23/2012 12:08 PM, Abdussalam Baryun wrote:
>> Hi Stewart,
>>
>> Usually the (IF x, THEN y) means if x happens then y is a MUST, so I
>> don't see the important reflection of a MUST in many documentation
>> when using *if*. That is why I prefer to find requirements more easily
>> while skimming any IETF document, the MUST, SHOULD, and IF, these are
>> important requirement words in specifications. Please see below as
>> examples per your requested.
>>
>> ------------------------------------------------------------------------=
------------------------------
>> RFC4861>page36> IMO suggest to use IF, THEN
>>
>> If no entry exists, the sender creates one, sets its state
>> to INCOMPLETE, initiates Address Resolution, and then queues the data
>> packet pending completion of address resolution.
>> ------------------------------------------------------------------------=
------------------------------
>> RFC4861>page 49> IMO suggest to use IF and ELSE IF
>>
>> If the router already has a Neighbor Cache entry for the
>> solicitation=92s sender, the solicitation contains a Source Link-Layer
>> Address option, and the received link-layer address differs from that
>> already in the cache, then the link-layer address SHOULD be updated
>> in the appropriate Neighbor Cache entry, and its reachability state
>> MUST also be set to STALE. If there is no existing Neighbor Cache
>> entry for the solicitation=92s sender, the router creates one, installs
>> the link- layer address and sets its reachability state to STALE as
>> specified in Section 7.3.3. If there is no existing Neighbor Cache
>> entry and no Source Link-Layer Address option was present in the
>> solicitation, the router may respond with either a multicast or a
>> unicast router advertisement. Whether or not a Source Link-Layer
>> Address option is provided, if a Neighbor Cache entry for the
>> solicitation=92s sender exists (or is created) the entry=92s IsRouter
>> flag MUST be set to FALSE.
>> ------------------------------------------------------------------------=
----------
>> RFC5715>page 19>
>>
>> If R changes before T, then a loop will form
>> around R, T, and S.
>> ------------------------------------------------------------------------=
-----------
>> RFC6052> page 10> suggest delete *will* and to add as IF, THEN
>>
>> If a packet bound to
>> 192.0.2.33 reaches the translator, the destination address will be
>> translated to 2001:db8:122:344:c0:2:2100::, and the packet will be
>> routed towards R and then to A.
>> ------------------------------------------------------------------------=
-----------
>>
>> There are many examples that ignore the use of IF , THEN requirements,
>> which I suggest to be in the I-D update of RFC2119 that I working on
>> and will submit in 30 July,
>>
>> Regards
>>
>> Abdussalam Baryun
>> University of Glamorgan, UK
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>>> Preferable with a list of RFC text snippets that would have been
>>> more readable if these keywords had been used.
>>
>>> Stewart
>>
>>
>>> On Sun, Jul 22, 2012 at 7:17 AM, Abdussalam Baryun
>>> <abdussalambaryun@gmail.com> wrote:
>>>> Hi All,
>>>>
>>>> I am working on an I-D which is intended as proposed standard but need
>>>> some addition requirement language. Therefore, I want to propose to
>>>> write a draft to update RFC2119 to add some other language requirement
>>>> as below:
>>>>
>>>> IF x, THEN y:
>>>>
>>>> ELSE:
>>>>
>>>> ELSE IF:
>>>>
>>>> Please send your comments or advise, thanking you,
>>>
>>> That doesn't have to be in 2119.  Lots of RFCs have pseudocode at
>>> various levels of rigor.  Just look around at some protocol specs for
>>> examples.
>>>
>>
>>
>

From cabo@tzi.org  Mon Jul 23 06:46:29 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 960FA21F868A; Mon, 23 Jul 2012 06:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.462
X-Spam-Level: 
X-Spam-Status: No, score=-106.462 tagged_above=-999 required=5 tests=[AWL=-0.213, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KE8o0zEx7Rg2; Mon, 23 Jul 2012 06:46:28 -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 531C521F85F9; Mon, 23 Jul 2012 06:46:27 -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 q6NDkKQY009884; Mon, 23 Jul 2012 15:46:20 +0200 (CEST)
Received: from [192.168.217.105] (p54893609.dip.t-dialin.net [84.137.54.9]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id BB0F36CC; Mon, 23 Jul 2012 15:46:19 +0200 (CEST)
Subject: Re: Proposed IETF 95 Date Change
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE240AE8B63@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Date: Mon, 23 Jul 2012 15:46:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEAC0B5D-DC0D-4198-BA42-B4E7329395B8@tzi.org>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <EDC0A1AE77C57744B664A310A0B23AE240AE8B63@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1278)
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 13:46:30 -0000

On Jul 23, 2012, at 14:28, DRAGE, Keith (Keith) wrote:

> you need to take into account at least both the Friday and Monday in =
some countries.

+1

In much of Europe, the Easter holidays run from Good Friday to Easter =
Monday, and exhibit
-- strong travel activity
-- zero to reduced opening times of various essential facilities
-- reduced public transport schedules (*)

When meeting in Europe, avoid both weeks around Easter.

(Clearly, we need to have IETF95 in Bali. :-)

Gr=FC=DFe, Carsten

(*) A bit counterintuitive -- the reason is that public transport =
agencies tend to cater to their employees as opposed to their customers, =
and these employees want to enjoy the holidays, too.
Since everybody knows that public transport is overcrowded on these long =
weekends, there isn't even any backlash.


From rpelletier@isoc.org  Mon Jul 23 07:04:18 2012
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C39CB11E8072 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 07:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.274
X-Spam-Level: 
X-Spam-Status: No, score=-103.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wsHlQFHEXg-o for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 07:04:18 -0700 (PDT)
Received: from smtp117.iad.emailsrvr.com (smtp117.iad.emailsrvr.com [207.97.245.117]) by ietfa.amsl.com (Postfix) with ESMTP id 2A45111E808A for <ietf@ietf.org>; Mon, 23 Jul 2012 07:04:18 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp41.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 31B6B290B83; Mon, 23 Jul 2012 10:04:17 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp41.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id F308E290B2D;  Mon, 23 Jul 2012 10:04:16 -0400 (EDT)
Subject: Re: Proposed IETF 95 Date Change
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Pelletier Ray <rpelletier@isoc.org>
In-Reply-To: <500D0674.2090303@gmail.com>
Date: Mon, 23 Jul 2012 10:04:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F9C6238-8DA8-4BB1-AF4E-1ABB9F4B4A80@isoc.org>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <500D0674.2090303@gmail.com>
To: henk@uijterwaal.nl
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, 23 Jul 2012 14:04:18 -0000

On Jul 23, 2012, at 4:08 AM, Henk Uijterwaal wrote:

> On 20/07/2012 18:06, IETF Administrative Director wrote:
>> The IAOC is seeking community feedback on a proposed date change for =
IETF 95
>> scheduled for March 2016.
>>=20
>> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 =
March is Easter.
>>=20
>> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 =
and would like=20
>> feedback on those dates before making a decision.  Comments =
appreciated to ietf@ietf.org=20
>> by 6 August 2012.
>>=20
>> Ray Pelletier
>> IETF Administrative Director
>=20
> If March 27 is Easter, then I'm not sure if the change solves the =
problem.
> Sunday March 20 is Palm Sunday, the Thursday and Friday before Easter =
(as
> well as the Monday after) are religious holidays in many European =
countries.
>=20
> If you want to avoid a clash with Easter and related days, then one =
will
> have to move the meeting to either the week of 13-18 March,

13 - 18 March 2016 are the dates for the IEEE-802 Plenary.

Ray


> or the week of
> 3-8 April.
>=20
> Henk
>=20
>=20
>=20
> --=20
> =
--------------------------------------------------------------------------=
----
> Henk Uijterwaal                           Email: henk(at)uijterwaal.nl
>                                          http://www.uijterwaal.nl
>                                          Phone: +31.6.55861746
> =
--------------------------------------------------------------------------=
----
>=20
> Read my blog at http://www.uijterwaal.nl/henks_hands.html


From richard@shockey.us  Mon Jul 23 07:11:23 2012
Return-Path: <richard@shockey.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA59C21F8598 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 07:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.822
X-Spam-Level: 
X-Spam-Status: No, score=-100.822 tagged_above=-999 required=5 tests=[AWL=1.443, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZvrOaJvhrlf for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 07:11:22 -0700 (PDT)
Received: from oproxy8-pub.bluehost.com (oproxy8-pub.bluehost.com [69.89.22.20]) by ietfa.amsl.com (Postfix) with SMTP id A2F5321F850D for <ietf@ietf.org>; Mon, 23 Jul 2012 07:11:22 -0700 (PDT)
Received: (qmail 618 invoked by uid 0); 23 Jul 2012 14:11:18 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy8.bluehost.com with SMTP; 23 Jul 2012 14:11:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=AI+dqLIFBZlQSG1peQvGwrBv314Gdg6Mc7KXC4UqK+I=;  b=VzYX49kRNQqmKEkm27KQDc8rqtD3HsUN1Dgf4dm2zZzLsWHu0LoeOI0U1YVe27CaKKbYm68GaxO+itH77cGpXyIvJB+W0GB/Varit4XLCJzOvNo+ohvOXahfSACtRoY/;
Received: from [71.191.243.130] (port=51752 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1StJLx-00084g-Sc; Mon, 23 Jul 2012 08:11:18 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Bradner, Scott'" <sob@harvard.edu>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>	<A29A24B6-4A07-46CC-902B-8A181F0541A3@kumari.net>	<9B2F2766-DB92-4B7B-88DC-1B90FF6707B7@bbn.com>	<CAPv4CP-zy1uUqXfXqNH9R1C-NTe+11pxgJ5ceZaR1=oU2E1T=A@mail.gmail.com> <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu>
In-Reply-To: <A4AF7C0C-B8FB-47CB-BF36-78F2686FA5E1@harvard.edu>
Subject: RE: Feedback Requested on Draft Fees Policy
Date: Mon, 23 Jul 2012 10:11:14 -0400
Message-ID: <009701cd68dd$06642560$132c7020$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHNZoJYmCUNzXWKXEamw9YDfsScm5c27F8g
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 authed with richard@shockey.us}
Cc: wgchairs@ietf.org, iab@iab.org, ietf@ietf.org, 'IETF Announcement List' <ietf-announce@ietf.org>, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 14:11:24 -0000

+1 Excellent idea in principle ..IMHO just a matter of working out details. 


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Bradner, Scott
Sent: Friday, July 20, 2012 10:17 AM
To: Scott Brim
Cc: wgchairs@ietf.org; ietf@ietf.org; iaoc@ietf.org; iab@iab.org; IETF
Announcement List
Subject: Re: Feedback Requested on Draft Fees Policy

great idea - just does not jive with the legal system which often need
authenticated copies of documents

Scott

On Jul 20, 2012, at 10:14 AM, Scott Brim wrote:

> > On Jul 20, 2012, at 9:07 AM, IETF Administrative Director wrote:
> >> The draft policy entitled Draft Fee Policy for Legal Requests can 
> >> be found
> >> at: <http://iaoc.ietf.org/policyandprocedures.html>
> 
> Fine idea. 




From dhc@dcrocker.net  Mon Jul 23 07:15:29 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 77AB811E808A for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 07:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.586
X-Spam-Level: 
X-Spam-Status: No, score=-6.586 tagged_above=-999 required=5 tests=[AWL=0.013,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LKT7n8hbSevM for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 07:15:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C11CE11E808D for <ietf@ietf.org>; Mon, 23 Jul 2012 07:15:27 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q6NEFPZC015820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 23 Jul 2012 07:15:25 -0700
Message-ID: <500D5C73.4000607@dcrocker.net>
Date: Mon, 23 Jul 2012 07:15:15 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Updating RFC2119
References: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com> <CAPv4CP95Rhma3reOvrWfrWQE_mqsyY8bL2EvkZq5hD6gbyf_ow@mail.gmail.com> <CADnDZ89uM25K=8M5KmkFva0V4SHQGUQ2e7nksiv26Pt=WpSrWA@mail.gmail.com> <500D3500.4080003@cs.tcd.ie>
In-Reply-To: <500D3500.4080003@cs.tcd.ie>
Content-Type: text/plain; charset=windows-1252; 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, 23 Jul 2012 07:15:26 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 14:15:29 -0000

On 7/23/2012 4:26 AM, Stephen Farrell wrote:
> I'd encourage you to not try change 2119.
>
> Instead, add whatever new definitions you feel
> you need to your own draft that addresses some
> technical, and not process, topic.
>
> If people find your new definitions useful they'll
> say and if enough of that happens they'll be
> included in a 2119bis whenever that's done.

+1

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From richard@shockey.us  Mon Jul 23 07:16:58 2012
Return-Path: <richard@shockey.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6326021F8703 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 07:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.629
X-Spam-Level: 
X-Spam-Status: No, score=-98.629 tagged_above=-999 required=5 tests=[AWL=-0.923, BAYES_50=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_BL_SPAMCOP_NET=1.96, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id chM-SdL4Aaii for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 07:16:57 -0700 (PDT)
Received: from oproxy10-pub.bluehost.com (oproxy10-pub.bluehost.com [67.222.39.61]) by ietfa.amsl.com (Postfix) with SMTP id B3C5E21F8598 for <ietf@ietf.org>; Mon, 23 Jul 2012 07:16:57 -0700 (PDT)
Received: (qmail 7203 invoked by uid 0); 23 Jul 2012 14:16:36 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy10.bluehost.com with SMTP; 23 Jul 2012 14:16:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=miVRhVIjrZkoy2K8EqfQoVrswdHwnVzUKcdiZax0Pvc=;  b=Svm/RGrn6n0vQEL5l1vE7AyGbn7klPniXiyI/pFk6KPooXISX+XZwMxjZHOJbcb/L7J+PteDeA2zpB3xcjJ7vmOvEUS28NHb7B2TtbU+yR9Tx1W+FIIVwPabSxAlLda9;
Received: from [71.191.243.130] (port=51883 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1StJR5-0002x4-Vk; Mon, 23 Jul 2012 08:16:36 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'John C Klensin'" <john-ietf@jck.com>, "'IETF Administrative Director'" <iad@ietf.org>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com> <CF472A8775DF4CDEEA6A1325@JcK-HP8200.jck.com>
In-Reply-To: <CF472A8775DF4CDEEA6A1325@JcK-HP8200.jck.com>
Subject: RE: Feedback Requested on Draft Fees Policy
Date: Mon, 23 Jul 2012 10:16:33 -0400
Message-ID: <009801cd68dd$c3e68ce0$4bb3a6a0$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1mhZYvBZTMSVTZRoWTTaEBgglMPACV+ofQ
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.191.243.130 authed with richard@shockey.us}
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, 23 Jul 2012 14:16:58 -0000

As a working assumption let's say at least 750 USD or Euros per hour to
calculate cost recovery.  


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of John
C Klensin
Sent: Friday, July 20, 2012 10:40 AM
To: IETF Administrative Director
Cc: ietf@ietf.org
Subject: Re: Feedback Requested on Draft Fees Policy



--On Friday, July 20, 2012 06:07 -0700 IETF Administrative Director
<iad@ietf.org> wrote:

> The IAOC is seeking community feedback on a proposed policy by  the 
>IAOC to impose  fees to produce information and  authenticate documents 
>in response to subpoenas and  other  legal requests.
>...
> Before adopting a policy the IAOC would like feedback on this  before 
>making a  decision.  Comments appreciated to  ietf@ietf.org by 6 August 
>2012.

Seems entirely reasonable.  Knowing how much effort some of these requests
can produce, I do wonder if the fees are a bit too low but trust that the
IAOC has determined that they will at least cover costs.

   john





From sob@sobco.com  Sun Jul 22 13:20:51 2012
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F385F21F85C9 for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 13:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.346
X-Spam-Level: 
X-Spam-Status: No, score=-0.346 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GjVqWIopCWx for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 13:20:50 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 00F3C21F852C for <ietf@ietf.org>; Sun, 22 Jul 2012 13:20:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 5D6E5347551B; Sun, 22 Jul 2012 16:21:51 -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 8BFKdcZ1f-Ds; Sun, 22 Jul 2012 16:21:48 -0400 (EDT)
Received: from [10.0.1.11] (173-166-5-69-newengland.hfc.comcastbusiness.net [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id A72603475504; Sun, 22 Jul 2012 16:21:48 -0400 (EDT)
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <alpine.BSF.2.00.1207221550590.17748@joyce.lan>
Date: Sun, 22 Jul 2012 16:22:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <06CAE00A-F7AF-4D6C-ACE4-0D8399C13F44@sobco.com>
References: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@mail.gmail.com> <20120722153118.60473.qmail@joyce.lan> <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com> <alpine.BSF.2.00.1207221550590.17748@joyce.lan>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Mon, 23 Jul 2012 09:24:51 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 20:20:51 -0000

I did it once - it took 2 or 3 hours *it was quite a while back and I do =
not remember)

there were no significant expenses - the depo was in Boston & my only
expense was a few hours parking - the depo was done in the office of the
law firm that was providing the IETF with pro-bono legal services at the =
time

Scott

On Jul 22, 2012, at 3:58 PM, John R Levine wrote:

>>> For people with unique skills or knowledge, $800/hr is not unusual.
>>> So long as the rate is published ahead of time, you're not going to
>>> get much argument.  ("Yes, we know it's high.  But we've already =
told
>>> you how to download stuff yourself for free.")
>>=20
>> Please  note : out of pocket expenses (if someone has to travel to a
>> hearing, say) would be reimbursed, but
>> IETF volunteers will not be paid from these fees.
>=20
> If you know, how often have people been deposed on behalf of the
> IETF, and how long does it typically take?
>=20
> My thought is that in a depo or trial, the other side pays both for =
the expenses and the time of the person being deposed, so it would be =
good idea to say up front here's what it'll cost if you want a live =
witness.
>=20
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.


From sob@sobco.com  Sun Jul 22 13:45:38 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 99AF021F851A for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 13:45:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.371
X-Spam-Level: 
X-Spam-Status: No, score=-0.371 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 82i08uwAUMSl for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 13:45:38 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1CB21F84FB for <ietf@ietf.org>; Sun, 22 Jul 2012 13:45:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 5AB923475D5F; Sun, 22 Jul 2012 16:46:40 -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 62dKk+4C3ILM; Sun, 22 Jul 2012 16:46:39 -0400 (EDT)
Received: from [10.0.1.11] (173-166-5-69-newengland.hfc.comcastbusiness.net [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id F1EE53475D4B; Sun, 22 Jul 2012 16:46:38 -0400 (EDT)
Subject: Re: [IAOC] Feedback Requested on Draft Fees Policy
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <alpine.BSF.2.00.1207221642080.31418@joyce.lan>
Date: Sun, 22 Jul 2012 16:46:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B377A30-123B-4772-AAB8-FAA535FDD0BE@sobco.com>
References: <CAJNg7VKqbdXeFXCe6iBRPe=X89q4NuSVcgvmc+C=t0826HRwiA@mail.gmail.com> <20120722153118.60473.qmail@joyce.lan> <CAJNg7VK9OJNdtBb4+F3ZepvgpwuXQ_30ung_Y91m--g1a+CpfA@mail.gmail.com> <alpine.BSF.2.00.1207221550590.17748@joyce.lan> <06CAE00A-F7AF-4D6C-ACE4-0D8399C13F44@sobco.com> <alpine.BSF.2.00.1207221642080.31418@joyce.lan>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Mon, 23 Jul 2012 09:24:51 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 20:45:38 -0000

I did not do them any favor - I did the IETF a favor (as the then ISOC =
VP for Standards)

Scott

On Jul 22, 2012, at 4:43 PM, John R Levine wrote:

>> I did it once - it took 2 or 3 hours *it was quite a while back and I =
do not remember)
>>=20
>> there were no significant expenses - the depo was in Boston & my only
>> expense was a few hours parking - the depo was done in the office of =
the
>> law firm that was providing the IETF with pro-bono legal services at =
the time
>=20
> If the opposing party didn't pay you for your time in the depo, you =
did them an unnecessary favor.
>=20
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.


From keith.drage@alcatel-lucent.com  Mon Jul 23 05:31:37 2012
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9A321F867D; Mon, 23 Jul 2012 05:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.779
X-Spam-Level: 
X-Spam-Status: No, score=-109.779 tagged_above=-999 required=5 tests=[AWL=0.470, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gd86wxYFhBL8; Mon, 23 Jul 2012 05:31:35 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id D86CA21F8668; Mon, 23 Jul 2012 05:31:30 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q6NCT6ID017830 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 23 Jul 2012 14:31:26 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.44]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 23 Jul 2012 14:30:47 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: IETF Administrative Director <iad@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Date: Mon, 23 Jul 2012 14:28:45 +0200
Subject: RE: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: Ac1mkgugs2pN3305ScqOJTSML5WOpwCMvHow
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE240AE8B63@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com>
In-Reply-To: <20120720160624.12163.25321.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
X-Mailman-Approved-At: Mon, 23 Jul 2012 09:24:51 -0700
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@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: Mon, 23 Jul 2012 12:31:37 -0000

Let's forget the religious discussion that seems to have broken out as a re=
sult of this.

While Easter may be a major Christian festival, I don't believe the issue i=
s such (I can think of no reasons why Christians would have a doctrinal rea=
son other than those that apply to any other Sunday and those obligations c=
ould mostly be met at the venue rather than at home). Rather it is Easter t=
he secular public holiday that happens to occur in many countries.

This is the set of days when schools take an extended break, parents take s=
aid children off on short holidays; cheap air tickets cease to be available=
; when you get on the plane, it is full of screaming children; local transp=
ort all works to a reduced timetable; for those IETFers who end up wishing =
to travel by train, they find themselves moving to busses to cater for the =
engineering works which a 4 day weekend seems to encourage.

So my advice would be, change the dates if it looks like you are going to h=
old the meeting in a country that takes such holidays, or where a significa=
nt number of people would need to transit through such a country. If so you=
 need to take into account at least both the Friday and Monday in some coun=
tries.

Keith

P.S. Trying to avoid every religious and public holiday is an impossible ta=
sk. Do what other organizations have done and concentrate on the impact of =
such holidays on holding the meeting in any location.

> -----Original Message-----
> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> Behalf Of IETF Administrative Director
> Sent: 20 July 2012 17:06
> To: IETF Announcement List
> Cc: iaoc@ietf.org; iab@iab.org; ietf@ietf.org; wgchairs@ietf.org
> Subject: Proposed IETF 95 Date Change
>=20
> The IAOC is seeking community feedback on a proposed date change for IETF
> 95
> scheduled for March 2016.
>=20
> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is
> Easter.
>=20
> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and
> would like
> feedback on those dates before making a decision.  Comments appreciated t=
o
> ietf@ietf.org
> by 6 August 2012.
>=20
> Ray Pelletier
> IETF Administrative Director

From jmpolk@cisco.com  Mon Jul 23 10:04:41 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 7FF3411E80D7; Mon, 23 Jul 2012 10:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.523
X-Spam-Level: 
X-Spam-Status: No, score=-110.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eu89dBD4mX8s; Mon, 23 Jul 2012 10:04:41 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id BE5DC11E80D5; Mon, 23 Jul 2012 10:04:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=2757; q=dns/txt; s=iport; t=1343063080; x=1344272680; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=w4icnHtpjmaCqF+h7AbCuvKvhJaN2UjTqmA5yKRpYYU=; b=kZ0JWkcq1B9uLb5jEcfhyFOdB2xNVfkzZJV0F76JqGHpEEU2wdHC9sg1 BuJor4HgVy3OAGapMGGpMd93vdfVJAwhTfcMtS+ZwQ8zWfGTMjyCU+RLE 3bEKL48flMS4Wz2GnpYwb2YvYF7GFA5jRdx5sozBsONfbSFLA+cZJZBnT 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAJqDDVCrRDoI/2dsb2JhbABFuTmBB4IgAQEBBBIBJQI/DAQHBBEEAQEBFQkJBxktCQgGARIUDodqnSmPFpBOi00kgweCSGADiE6bIoFmgn0
X-IronPort-AV: E=Sophos;i="4.77,639,1336348800"; d="scan'208";a="49667487"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 23 Jul 2012 17:04:40 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8714.cisco.com [10.99.80.21]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q6NH4dtB025884; Mon, 23 Jul 2012 17:04:39 GMT
Message-Id: <201207231704.q6NH4dtB025884@mtv-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 23 Jul 2012 12:04:39 -0500
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, IETF Administrative Director <iad@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
From: James Polk <jmpolk@cisco.com>
Subject: RE: Proposed IETF 95 Date Change
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE240AE8B63@FRMRSSXCHMBSC3.dc -m.alcatel-lucent.com>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <EDC0A1AE77C57744B664A310A0B23AE240AE8B63@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@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: Mon, 23 Jul 2012 17:04:41 -0000

At 07:28 AM 7/23/2012, DRAGE, Keith (Keith) wrote:
>Let's forget the religious discussion that seems to have broken out 
>as a result of this.
>
>While Easter may be a major Christian festival, I don't believe the 
>issue is such (I can think of no reasons why Christians would have a 
>doctrinal reason other than those that apply to any other Sunday and 
>those obligations could mostly be met at the venue rather than at 
>home). Rather it is Easter the secular public holiday that happens 
>to occur in many countries.
>
>This is the set of days when schools take an extended break, parents 
>take said children off on short holidays; cheap air tickets cease to 
>be available; when you get on the plane, it is full of screaming children;

kinda like we're all going to experience at next year's IETF86 timed 
exactly in the middle of US spring break going to/from Orlando (home 
to 4(?) amusement parks including Disneyworld)?

Air travel will be crazy (families book tickets many months - like 6 
- in advance), and depending on which hotel we're in, it could be 
worse than staying at the airport each day.

-j

>local transport all works to a reduced timetable; for those IETFers 
>who end up wishing to travel by train, they find themselves moving 
>to busses to cater for the engineering works which a 4 day weekend 
>seems to encourage.
>
>So my advice would be, change the dates if it looks like you are 
>going to hold the meeting in a country that takes such holidays, or 
>where a significant number of people would need to transit through 
>such a country. If so you need to take into account at least both 
>the Friday and Monday in some countries.
>
>Keith
>
>P.S. Trying to avoid every religious and public holiday is an 
>impossible task. Do what other organizations have done and 
>concentrate on the impact of such holidays on holding the meeting in 
>any location.
>
> > -----Original Message-----
> > From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
> > Behalf Of IETF Administrative Director
> > Sent: 20 July 2012 17:06
> > To: IETF Announcement List
> > Cc: iaoc@ietf.org; iab@iab.org; ietf@ietf.org; wgchairs@ietf.org
> > Subject: Proposed IETF 95 Date Change
> >
> > The IAOC is seeking community feedback on a proposed date change for IETF
> > 95
> > scheduled for March 2016.
> >
> > Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March is
> > Easter.
> >
> > The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and
> > would like
> > feedback on those dates before making a decision.  Comments appreciated to
> > ietf@ietf.org
> > by 6 August 2012.
> >
> > Ray Pelletier
> > IETF Administrative Director


From weiler@watson.org  Mon Jul 23 11:39:26 2012
Return-Path: <weiler@watson.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 1240611E80E7 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 11:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rPjJcFTqLEy1; Mon, 23 Jul 2012 11:39:25 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id 42CBD11E80CC; Mon, 23 Jul 2012 11:39:25 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.5/8.14.5) with ESMTP id q6NIdNTG029059; Mon, 23 Jul 2012 14:39:23 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.5/8.14.5/Submit) with ESMTP id q6NIdNqa029056; Mon, 23 Jul 2012 14:39:23 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Mon, 23 Jul 2012 14:39:23 -0400 (EDT)
From: Samuel Weiler <weiler@watson.org>
To: IETF Administrative Director <iad@ietf.org>
Subject: Re: Feedback Requested on Draft Fees Policy
In-Reply-To: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
Message-ID: <alpine.BSF.2.00.1207230205230.12609@fledge.watson.org>
References: <20120720130733.14364.19024.idtracker@ietfa.amsl.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Mon, 23 Jul 2012 14:39:24 -0400 (EDT)
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, 23 Jul 2012 18:39:26 -0000

No objection.  Thank you for asking.

Just as with any project that you don't really want to take on, make 
sure the price is high enough that you're willing to do it should 
someone be foolish enough to pay the asking price.

Also consider adding an automatic fee escalation clause (e.g. permit 
the IAD to raise the fee by up to 5% per year without further IAOC 
action).

-- Sam


From weiler@watson.org  Mon Jul 23 12:04:37 2012
Return-Path: <weiler@watson.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 836B611E80CF for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 12:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zbfMvMwiSiTz for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 12:04:35 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id 5282A11E8093 for <ietf@ietf.org>; Mon, 23 Jul 2012 12:04:34 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.5/8.14.5) with ESMTP id q6NJ4MCO035519; Mon, 23 Jul 2012 15:04:22 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.5/8.14.5/Submit) with ESMTP id q6NJ4MfE035515; Mon, 23 Jul 2012 15:04:22 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Mon, 23 Jul 2012 15:04:22 -0400 (EDT)
From: Samuel Weiler <weiler@watson.org>
To: sarikaya@ieee.org
Subject: Re: Proposed IETF 95 Date Change
In-Reply-To: <CAC8QAce9Gd8GkViAfukZQSQXfOm5tZsXgDTkRt_PDNOAGUSG0Q@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.1207231441180.17130@fledge.watson.org>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <CAC8QAce9Gd8GkViAfukZQSQXfOm5tZsXgDTkRt_PDNOAGUSG0Q@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Mon, 23 Jul 2012 15:04:22 -0400 (EDT)
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, 23 Jul 2012 19:04:37 -0000

On Fri, 20 Jul 2012, Behcet Sarikaya wrote:

> I don't understand why this issue is coming up.
> Maybe you don't know, IETF 84 falls in the month of Ramadan for
> Muslims and nobody asked to change it?

I think focusing on the religious roots of the holiday is misguided. 
The question is what effect the holiday is likely to have on meeting 
attendance.  I think the IETF also tries to avoid secular holidays 
that would interfere with the attendance of a large number of typical 
IETF attendees.

Here's an example: we avoid the (secular) Thanksgiving holiday in the 
US -- it falls on a Thursday in late November, and it's common for 
people to take both the Thursday and Friday as holiday.  Thanksgiving 
is such a big deal in the US, and we get so many US attendees, that 
the IETF would avoid that holiday no matter where the meeting was 
being held.

Similarly, I think we would take into account local and regional 
holidays at our meeting sites, both religious and secular.  We would 
probably avoid having a meeting in Amsterdam's center (or, really, 
anywhere in the Netherlands) on Queen's Day.

Would overlapping with Easter draw down attendance enough to warrant 
avoiding it?  Probably.  It's a big enough risk that shifting a week 
seems sane.

While Ramadan is religiously very significant, I think it is observed 
by relatively few of our regular meeting attendees and even those 
that do observe it may be willing to travel during it.  Hence the 
difference in how they're being handled.

-- Sam

From mrex@sap.com  Mon Jul 23 13:26:04 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 69CAA21F8484 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 13:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.902
X-Spam-Level: 
X-Spam-Status: No, score=-9.902 tagged_above=-999 required=5 tests=[AWL=-0.253, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_65=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WT4Lywv0Pv45 for <ietf@ietfa.amsl.com>; Mon, 23 Jul 2012 13:26:04 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id AD05621F8483 for <ietf@ietf.org>; Mon, 23 Jul 2012 13:26:03 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q6NKPuJU018413 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 23 Jul 2012 22:26:01 +0200 (MEST)
Subject: Re: Proposed IETF 95 Date Change
In-Reply-To: <20120722192519.18622.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
Date: Mon, 23 Jul 2012 22:25: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: <20120723202556.0B8481A0E7@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 20:26:04 -0000

John Levine wrote:
[ Charset UTF-8 unsupported, converting... ]
> >> You're not going to find cool temperatures again in July or August
> >> unless you go as far south as Argentina or New Zealand.
> >
> >Not only is there life north of the 60th parallel (N), there are
> >even hotels and restaurants and airports.  Anchorage is probably
> >large enough for an IETF meeting, although trying to hold a meeting
> >there during tourist season would almost certainly be a mistake.
> >But still.
> 
> I believe it, but remember that the issue was to minimize daylight fasting
> during the North American summer.
> 
> Reykjavik is big enough, too, and has the advantage of being roughly
> equally inconvenient to get to from North America and Europe.  We
> could have the social event at the Blue Lagoon.

The issue with Reykjavik is more about is closeness to the Arctic circle.
You don't seem to have a lot of sunset&night there during the summer.

Take into account that ramadan is related to the lunar calender and
is 11 days earlier every year to the next (on the gregorian calendar)
then a hypothetical IETF meeting in Reykjavik, 22th June - 26th June 2015
could turn out "challenging" for some folks.  The currently scheduled
date for IETF 93 is 19-24 July, 2015, so I assume it will be after Ramadan.


-Martin

From bortzmeyer@nic.fr  Tue Jul 24 00:07:32 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 3FC9211E811E for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 00:07:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.88
X-Spam-Level: 
X-Spam-Status: No, score=-101.88 tagged_above=-999 required=5 tests=[AWL=0.369, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WGkv2D162S3f for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 00:07:31 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id A268811E8119 for <ietf@ietf.org>; Tue, 24 Jul 2012 00:07:31 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 2ACB228015E; Tue, 24 Jul 2012 09:06:56 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 2605D280151; Tue, 24 Jul 2012 09:06:56 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay2.nic.fr (Postfix) with ESMTP id 1ACB3B38004; Tue, 24 Jul 2012 09:06:26 +0200 (CEST)
Date: Tue, 24 Jul 2012 09:06:26 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: iab@iab.org
Subject: Re: IAB IPv6 privacy survey posted, response requested
Message-ID: <20120724070625.GA16477@nic.fr>
References: <078c01cd68ef$b35643e0$1a02cba0$@iab.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <078c01cd68ef$b35643e0$1a02cba0$@iab.org>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.2.0-2-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
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, 24 Jul 2012 07:07:32 -0000

On Mon, Jul 23, 2012 at 09:24:56AM -0700,
 IAB Chair <iab-chair@iab.org> wrote 
 a message of 95 lines which said:

> those familiar with OS IPv6 implementations are asked to complete a
> short survey
> <http://www.iab.org/wp-content/IAB-uploads/2012/07/IPv6-Privacy-Survey.doc>

Which RFC (or other open specification) describes the ".doc" format? 

And since when Microsoft software is required for IETF work?

[Don't ask me to try LibreOffice, it runs at 100 % CPU time for
*minutes* when opening this document.]

From ford@isoc.org  Tue Jul 24 02:45:43 2012
Return-Path: <ford@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B60921F8648 for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 02:45:43 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4NHOg99kuf+J for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 02:45:42 -0700 (PDT)
Received: from smtp167.dfw.emailsrvr.com (smtp167.dfw.emailsrvr.com [67.192.241.167]) by ietfa.amsl.com (Postfix) with ESMTP id 7B12221F8644 for <ietf@ietf.org>; Tue, 24 Jul 2012 02:45:42 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp16.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 0F990407D6 for <ietf@ietf.org>; Tue, 24 Jul 2012 05:45:42 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp16.relay.dfw1a.emailsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id A2C904045D for <ietf@ietf.org>; Tue, 24 Jul 2012 05:45:41 -0400 (EDT)
From: Matthew Ford <ford@isoc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IETF Journal - latest issue now available
Date: Tue, 24 Jul 2012 10:45:40 +0100
Message-Id: <9F5D6EC3-C796-4DDB-9A27-D2BA04F5A981@isoc.org>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jul 2012 09:45:43 -0000

Hi,

The latest issue of the IETF Journal (Volume 8, Issue 1) is now =
available online at:

http://internetsociety.org/ietfjournal

Among others it contains articles on implementing identity management =
solutions, IPv6, and problems in low-delay communication.

In addition you will find summary reports of the IETF 83 meeting held in =
Paris, regular columns submitted by the IETF, the IAB and the IRTF =
chairs, summaries of the plenary sessions, and an article on the =
fellowship to IETF.

You can read this publication online or choose to download the full =
issue in PDF format. You can also keep up to date with the latest issue =
by subscribing to the IETF Journal as an email edition or have it =
delivered to your postal address in hardcopy.

Many thanks to all our contributors. Please send any comments or =
suggestions for future issues to ietfjournal@isoc.org.

Kind Regards,

Mat Ford
Managing Editor
IETF Journal
http://internetsociety.org/ietfjournal=

From hannes.tschofenig@gmx.net  Tue Jul 24 02:56:30 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2BB21F8668 for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 02:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XJ+2x8bLdn3 for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 02:56:29 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id D814C21F8666 for <ietf@ietf.org>; Tue, 24 Jul 2012 02:56:28 -0700 (PDT)
Received: (qmail invoked by alias); 24 Jul 2012 09:56:27 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.110]) [88.115.216.191] by mail.gmx.net (mp038) with SMTP; 24 Jul 2012 11:56:27 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18MltV65lUMrhOApPIbrxRbymtLQ4IQXto5KJIgD6 eK33n6iN2l+1T8
Subject: Re: [IAB] IAB IPv6 privacy survey posted, response requested
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <20120724070625.GA16477@nic.fr>
Date: Tue, 24 Jul 2012 12:49:21 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF66243C-94EB-466E-8654-86032B14BC8B@gmx.net>
References: <078c01cd68ef$b35643e0$1a02cba0$@iab.org> <20120724070625.GA16477@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org, iab@iab.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 09:56:30 -0000

I put a RTF version of the document here:
=
http://www.iab.org/wp-content/IAB-uploads/2012/07/IPv6-Privacy-Survey1.rtf=


Does this work for you?=20

Ciao
Hannes

On Jul 24, 2012, at 10:06 AM, Stephane Bortzmeyer wrote:

> On Mon, Jul 23, 2012 at 09:24:56AM -0700,
> IAB Chair <iab-chair@iab.org> wrote=20
> a message of 95 lines which said:
>=20
>> those familiar with OS IPv6 implementations are asked to complete a
>> short survey
>> =
<http://www.iab.org/wp-content/IAB-uploads/2012/07/IPv6-Privacy-Survey.doc=
>
>=20
> Which RFC (or other open specification) describes the ".doc" format?=20=

>=20
> And since when Microsoft software is required for IETF work?
>=20
> [Don't ask me to try LibreOffice, it runs at 100 % CPU time for
> *minutes* when opening this document.]


From Chris.Dearlove@baesystems.com  Tue Jul 24 05:21:37 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 BA84521F8526 for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 05:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.216
X-Spam-Level: 
X-Spam-Status: No, score=-10.216 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zGuFmTqJd36E for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 05:21:36 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 85B8421F8608 for <ietf@ietf.org>; Tue, 24 Jul 2012 05:21:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,646,1336345200"; d="scan'208";a="258584603"
Received: from unknown (HELO baemasmds009.greenlnk.net) ([141.245.68.246]) by baemasmds003ir.sharelnk.net with ESMTP; 24 Jul 2012 13:21:36 +0100
Received: from GLKXH0002V.GREENLNK.net ([10.109.2.33]) by baemasmds009.greenlnk.net (Switch-3.4.4/Switch-3.4.4) with ESMTP id q6OCLZMY025940 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 24 Jul 2012 13:21:35 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.170]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.02.0309.002; Tue, 24 Jul 2012 13:21:35 +0100
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: AQHNZpHW2EdcKqKUpEmUR9VVNLwAI5cy3KUAgAAGLoCAAGCdAIAFG+0A
Date: Tue, 24 Jul 2012 12:21:34 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D24EAEFB3@GLKXM0002V.GREENLNK.net>
References: <20120720160624.12163.25321.idtracker@ietfa.amsl.com> <9261E011-DA3D-4BDA-A7AF-720C4539BAED@vpnc.org> <1095943C-3926-4697-AF13-C4C4D7A5505E@cisco.com> <500A572C.3020003@gmail.com>
In-Reply-To: <500A572C.3020003@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 12:21:37 -0000

I think the main (as in the one more people would care about) issue here (U=
K) isn't a religious clash, it's a public holiday clash (Friday and Monday)=
.

--=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 Bri=
an E Carpenter
Sent: 21 July 2012 08:16
To: Fred Baker (fred)
Cc: Paul Hoffman; IETF discussion list
Subject: Re: Proposed IETF 95 Date Change

----------------------! 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.
--------------------------------------------------------

On 21/07/2012 02:30, Fred Baker (fred) wrote:
> On Jul 20, 2012, at 6:08 PM, Paul Hoffman wrote:
>=20
>> As for the Ramadan issue: we've had IETF meetings during Jewish holidays=
 a few times, and folks dealt with it as best they can. If there are some a=
ccommodations that can be made at any IETF meeting for different holidays o=
f major religions, I would bet that IETF Secretariat would be glad to hear =
them.
>=20
>=20
> It comes down to adding them to the clash list...

(which is at http://www.ietf.org/meeting/clash-list.html)

And we know that if we did that, on top of all the other technical meetings
that we have to avoid, the result would be overconstrained and scheduling
would become impossible. IMNSHO we need to treat all religious constraints
alike, and in practice that means ignoring them. For practical reasons, we
can't ignore major holidays - not because some of them are religious, but
because they block up hotels and airlines.

Finding the least bad solution is always going to be a compromise, and
I thank the IAOC for continuing to plan several years ahead.

   Brian



********************************************************************
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 simon.perreault@viagenie.ca  Tue Jul 24 06:16:14 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 EB89021F8649 for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 06:16: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.074,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rnIOwfq77OCS for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 06:16:14 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 37A2F21F8602 for <ietf@ietf.org>; Tue, 24 Jul 2012 06:16:14 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:4464:6d77:4cf8:d25e]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 45A35415CD for <ietf@ietf.org>; Tue, 24 Jul 2012 09:16:13 -0400 (EDT)
Message-ID: <500EA01C.8060504@viagenie.ca>
Date: Tue, 24 Jul 2012 09:16:12 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAB IPv6 privacy survey posted, response requested
References: <078c01cd68ef$b35643e0$1a02cba0$@iab.org> <20120724070625.GA16477@nic.fr>
In-Reply-To: <20120724070625.GA16477@nic.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 13:16:15 -0000

Le 2012-07-24 03:06, Stephane Bortzmeyer a écrit :
> And since when Microsoft software is required for IETF work?

Even though I replied to the survey, this also irritated me. And I sense 
a trend here. It seems that the number of non-plain-text files coming 
from IAB has been increasing.

Suggestion: just put the content right in the body of the email. I see 
no need for any kind of attachment.

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 dworley@avaya.com  Tue Jul 24 06:45:58 2012
Return-Path: <dworley@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 B304F21F8617 for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 06:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.703
X-Spam-Level: 
X-Spam-Status: No, score=-102.703 tagged_above=-999 required=5 tests=[AWL=-0.104, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KZnb7fhrujw8 for <ietf@ietfa.amsl.com>; Tue, 24 Jul 2012 06:45:58 -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 2027121F8615 for <ietf@ietf.org>; Tue, 24 Jul 2012 06:45:57 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAIilDlDGmAcF/2dsb2JhbABFhXCyYoEYgQeCIAEBAQEDEgYLEUUQAgEIDQsCAiYCAgIwFRABAQQODRqHa54Oih6TKIEgkAwyYAObRooQgnuBQw
X-IronPort-AV: E=Sophos;i="4.77,646,1336363200"; d="scan'208";a="19349818"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 24 Jul 2012 09:40:58 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 24 Jul 2012 09:41:56 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Tue, 24 Jul 2012 09:45:55 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "simon.perreault@viagenie.ca" <simon.perreault@viagenie.ca>
Date: Tue, 24 Jul 2012 09:45:53 -0400
Subject: Re: IAB IPv6 privacy survey posted, response requested
Thread-Topic: IAB IPv6 privacy survey posted, response requested
Thread-Index: Ac1poqVqTl/kv7uNSKiB6uPPxXRInA==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A1DC2@DC-US1MBEX4.global.avaya.com>
References: <078c01cd68ef$b35643e0$1a02cba0$@iab.org> <20120724070625.GA16477@nic.fr>  <500EA01C.8060504@viagenie.ca>
In-Reply-To: <500EA01C.8060504@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2012 13:45:58 -0000

T24gVHVlLCAyMDEyLTA3LTI0IGF0IDA5OjE2IC0wNDAwLCBTaW1vbiBQZXJyZWF1bHQgd3JvdGU6
Cj4gRXZlbiB0aG91Z2ggSSByZXBsaWVkIHRvIHRoZSBzdXJ2ZXksIHRoaXMgYWxzbyBpcnJpdGF0
ZWQgbWUuIEFuZCBJIHNlbnNlIAo+IGEgdHJlbmQgaGVyZS4gSXQgc2VlbXMgdGhhdCB0aGUgbnVt
YmVyIG9mIG5vbi1wbGFpbi10ZXh0IGZpbGVzIGNvbWluZyAKPiBmcm9tIElBQiBoYXMgYmVlbiBp
bmNyZWFzaW5nLgo+IAo+IFN1Z2dlc3Rpb246IGp1c3QgcHV0IHRoZSBjb250ZW50IHJpZ2h0IGlu
IHRoZSBib2R5IG9mIHRoZSBlbWFpbC4gSSBzZWUgCj4gbm8gbmVlZCBmb3IgYW55IGtpbmQgb2Yg
YXR0YWNobWVudC4KCk9yIHRoZSBhdHRhY2htZW50IGNvdWxkIGJlIHRleHQvcGxhaW4uLi4KCkRh
bGUKCg==

From D.Malas@cablelabs.com  Mon Jul 23 15:01:28 2012
Return-Path: <D.Malas@cablelabs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADED511E808E; Mon, 23 Jul 2012 15:01:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.463
X-Spam-Level: 
X-Spam-Status: No, score=-100.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xxx4cRct6N0a; Mon, 23 Jul 2012 15:01:28 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 231B411E808C; Mon, 23 Jul 2012 15:01:27 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id q6NM1P0G007745; Mon, 23 Jul 2012 16:01:25 -0600
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Mon, 23 Jul 2012 16:01:25 -0600 (MDT)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Mon, 23 Jul 2012 16:01:25 -0600
From: Daryl Malas <D.Malas@cablelabs.com>
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, IETF Administrative Director <iad@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Date: Mon, 23 Jul 2012 16:01:22 -0600
Subject: Re: Proposed IETF 95 Date Change
Thread-Topic: Proposed IETF 95 Date Change
Thread-Index: Ac1pHrOT0fsvAUBmShaTl0OFDsvRug==
Message-ID: <CC3325CD.12C8B%d.malas@cablelabs.com>
In-Reply-To: <EDC0A1AE77C57744B664A310A0B23AE240AE8B63@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
X-Mailman-Approved-At: Tue, 24 Jul 2012 08:47:42 -0700
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "ietf@ietf.org" <ietf@ietf.org>, "wgchairs@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: Mon, 23 Jul 2012 22:01:28 -0000

+1

On 7/23/12 6:28 AM, "DRAGE, Keith (Keith)"
<keith.drage@alcatel-lucent.com> wrote:

>Let's forget the religious discussion that seems to have broken out as a
>result of this.
>
>While Easter may be a major Christian festival, I don't believe the issue
>is such (I can think of no reasons why Christians would have a doctrinal
>reason other than those that apply to any other Sunday and those
>obligations could mostly be met at the venue rather than at home). Rather
>it is Easter the secular public holiday that happens to occur in many
>countries.
>
>This is the set of days when schools take an extended break, parents take
>said children off on short holidays; cheap air tickets cease to be
>available; when you get on the plane, it is full of screaming children;
>local transport all works to a reduced timetable; for those IETFers who
>end up wishing to travel by train, they find themselves moving to busses
>to cater for the engineering works which a 4 day weekend seems to
>encourage.
>
>So my advice would be, change the dates if it looks like you are going to
>hold the meeting in a country that takes such holidays, or where a
>significant number of people would need to transit through such a
>country. If so you need to take into account at least both the Friday and
>Monday in some countries.
>
>Keith
>
>P.S. Trying to avoid every religious and public holiday is an impossible
>task. Do what other organizations have done and concentrate on the impact
>of such holidays on holding the meeting in any location.
>
>> -----Original Message-----
>> From: wgchairs-bounces@ietf.org [mailto:wgchairs-bounces@ietf.org] On
>> Behalf Of IETF Administrative Director
>> Sent: 20 July 2012 17:06
>> To: IETF Announcement List
>> Cc: iaoc@ietf.org; iab@iab.org; ietf@ietf.org; wgchairs@ietf.org
>> Subject: Proposed IETF 95 Date Change
>>=20
>> The IAOC is seeking community feedback on a proposed date change for
>>IETF
>> 95
>> scheduled for March 2016.
>>=20
>> Currently IETF 95 is scheduled for 27 March to 1 April 2016.  27 March
>>is
>> Easter.
>>=20
>> The IAOC is proposing IETF 95 be rescheduled for 20 - 25 March 2016 and
>> would like
>> feedback on those dates before making a decision.  Comments appreciated
>>to
>> ietf@ietf.org
>> by 6 August 2012.
>>=20
>> Ray Pelletier
>> IETF Administrative Director


From iad@ietf.org  Tue Jul 24 11:46:10 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 6477B21F8601; Tue, 24 Jul 2012 11:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jzUJesFuWEjd; Tue, 24 Jul 2012 11:46:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1FD821F85D5; Tue, 24 Jul 2012 11:46:08 -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: Co-Hosts Announced for IETF 86 in Orlando
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120724184608.32185.77247.idtracker@ietfa.amsl.com>
Date: Tue, 24 Jul 2012 11:46:08 -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: Tue, 24 Jul 2012 18:46:11 -0000

The IAOC is pleased to announce the Co-Hosts for IETF 86 in Orlando Florida=
, USA =

March 10 - 15, 2013.

The Co-Hosts are Comcast and NBCUniversal.  Comcast Hosted IETF 71 in Phila=
delphia, is =

sponsoring IETF 85 in Atlanta, and has sponsored meeting breaks and ice cre=
am socials at
other meetings.  <http://www.comcast.com>

NBCUniversal is Hosting its first meeting with the IETF.  <http://www.nbcun=
i.com/>

We want to thank our benefactors.  The IETF cannot support its technical st=
andards efforts, =

including the Secretariat and RFC Editor, without the generous support of i=
ts hosts and =

sponsors.

Interested in hosting or sponsoring an IETF meeting?  Contact Drew Dvorshak=
 at =

dvorshak@isoc.org.  The meeting schedule is here:  <https://www.ietf.org/me=
eting/
upcoming.html>

Thanks again to Comcast and NBCUniversal!

We are just days away from IETF 84 in Vancouver.  Registrations are open an=
d operators =

are standing by (so to speak).  Visit <https://www.ietf.org/meeting/84/inde=
x.html> and join
the 1,250 who have already registered.

Ray Pelletier
IETF Administrative Director

From ben@nostrum.com  Tue Jul 24 15:32: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 2233C11E808C; Tue, 24 Jul 2012 15:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qYsS9DsrbXqA; Tue, 24 Jul 2012 15:32:42 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 58EDB11E807F; Tue, 24 Jul 2012 15:32:42 -0700 (PDT)
Received: from [10.0.1.9] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q6OMWZNJ026040 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 24 Jul 2012 17:32:36 -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-websec-strict-transport-sec-11
Date: Tue, 24 Jul 2012 17:32:35 -0500
Message-Id: <46F33BDA-5F64-4980-B799-867F9A34982F@nostrum.com>
To: draft-ietf-websec-strict-transport-sec.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1280)
X-Mailer: Apple Mail (2.1280)
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>, 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: Tue, 24 Jul 2012 22:32:43 -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-websec-strict-transport-sec-11
Reviewer: Ben Campbell
Review Date: 2012-07-24
IETF LC End Date: 2012-07-25

Summary: This draft is almost ready for publication as a proposed =
standard, but there are a few issues that should be considered first.

*** Major issues:

None

*** Minor issues:

-- Does this draft update any other RFCs (e.g. 2616 or 2818)? If so, =
that should be explicitly flagged and mentioned in the abstract.

-- I did not find any guidance on how to handle UAs that do not =
understand this extension. I don't know if this needs to be normative, =
but the draft should at least mention the possibility and implications.

-- How should a UA handle potential conflicts between a the policy =
record that includes the includeSubdomain, and any records for =
subdomains that might have different parameters?

-- section 6.1:

The draft mentions that directives may be extended, but defers creation =
of an IANA registry to the time of first extension. IANA registries are =
not expensive; I suggest it be created now. If there's a good reason not =
to, then the draft should still address the specification policy for =
extensions.

Also, do you expect that some future directive might need to have a =
"required-to-understand" status? Given that this is a security-affecting =
extension, it seems likely. If so, then the mechanism for expressing =
that needs to be defined in this draft.

-- section 7.2:

Am I correct to assume that the server must never just serve the content =
over a non-secure connection? If so, it would be helpful to mention =
that, maybe even normatively.

-- section 8.4:

Does this imply a duty for compliant UAs to check for revocation one way =
or another?


*** Nits/editorial comments:

-- idnits reports an uncited reference:

  =3D=3D Unused Reference: 'RFC6376' is defined on line 1709, but no =
explicit
     reference was found in the text

-- section 1.2:

The description of indented notes is almost precisely the opposite of =
how they are described in the RFC editor's style guide. It describes =
them as "parenthetical" notes, which is how experienced RFC readers are =
likely to perceive them. While it doesn't say so explicitly, I think =
putting normative text in parenthetical notes should be avoided. If =
these are intended to be taken more strongly than that (and by the =
description, I take it they should be taken more strongly than the =
surrounding text), then I suggest choosing a stronger prefix than =
"NOTE:"

-- section 7:

Does the reference to I-D.ietf-tls-ssl-version3 indicate a requirement =
for SSL3? Also, that's a long expired draft, even for an informational =
reference.

-- section 8.2, paragraph 5 (first non-numbered paragraph after numbered =
list)

To be pedantic, this could be taken to mean a congruent match only =
applies if the includeSubdomains flag is not present. I assume it's =
intended to apply whether or not the flag is present.

-- section 12 and subsections:

I was surprised to see more apparently normative material after the =
non-normative guidance sections. I think it would improve the =
organization to put this closer to the normative rules for UAs.

-- section 14.1, 4th paragraph (first non-bulleted paragraph following =
bullet list)

This issue is only true for proxies that act as a TLS MiTM, right? Would =
proxies that tunnel TLS via the CONNECT method have this issue?

_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art=

From randy@qualcomm.com  Wed Jul 25 16:00:32 2012
Return-Path: <randy@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 2A4D521F8679 for <ietf@ietfa.amsl.com>; Wed, 25 Jul 2012 16:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8oQFzh5Il0n5 for <ietf@ietfa.amsl.com>; Wed, 25 Jul 2012 16:00:31 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3455C21F8639 for <ietf@ietf.org>; Wed, 25 Jul 2012 16:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1343257232; x=1374793232; h=message-id:x-mailer:x-priority:date:to:from:subject: mime-version:content-type:x-random-sig-tag: x-originating-ip; bh=4m1ZqraJsXMkw/5fM3xg9BgqyphdFvC3ySX7qxnUmrU=; b=NIsl+OgEBjSfnIRfofmp6gAiJ06mNmzftuLIcMh0Q3m5EfFZk8TwrtON JTAx4QqMUhwXZMCeJ7b37cv3oNufDVdSzKKS5wvijmYuRqtUQGU6QoHFr up43vFD7xuvK/eyIg1s9LhH6N01sKYrIETEDrWe4fEbB2kRGCwr3gbUfa g=;
X-IronPort-AV: E=McAfee;i="5400,1158,6783"; a="212203505"
Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine02.qualcomm.com with ESMTP; 25 Jul 2012 16:00:31 -0700
X-IronPort-AV: E=Sophos;i="4.77,655,1336374000"; d="scan'208";a="121868507"
Received: from nasanexhc06.na.qualcomm.com ([172.30.48.21]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 25 Jul 2012 16:00:31 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc06.na.qualcomm.com (172.30.48.21) with Microsoft SMTP Server (TLS) id 14.2.309.2; Wed, 25 Jul 2012 16:00:30 -0700
Received: from loud.pensive.org (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.309.2; Wed, 25 Jul 2012 16:00:29 -0700
Message-ID: <p06240602cc35e58c6dc4@loud.pensive.org>
X-Mailer: Eudora for Mac OS X
X-Priority: 2 (High)
Date: Wed, 25 Jul 2012 15:54:45 -0700
To: <ietf@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Anyone need a room at the Hyatt?
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.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, 25 Jul 2012 23:00:32 -0000

I may have a room at the Hyatt at CAD 194 (includes breakfast) for 
the full IETF week.  If anyone wants it, please let me know right 
away.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
The reliability of machinery is inversely proportional to the
number and significance of any persons watching it.

From dhc@dcrocker.net  Wed Jul 25 16:06:28 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 0C98C21F8629 for <ietf@ietfa.amsl.com>; Wed, 25 Jul 2012 16:06:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.587
X-Spam-Level: 
X-Spam-Status: No, score=-6.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Inv+jTBYoUL2 for <ietf@ietfa.amsl.com>; Wed, 25 Jul 2012 16:06:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 73F6621F8622 for <ietf@ietf.org>; Wed, 25 Jul 2012 16:06:27 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-55-201.dsl.pltn13.pacbell.net [67.127.55.201]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q6PN6QBL023736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 25 Jul 2012 16:06:27 -0700
Message-ID: <50107BEF.4040901@dcrocker.net>
Date: Wed, 25 Jul 2012 16:06:23 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Randall Gellens <randy@qualcomm.com>
Subject: Re: Anyone need a room at the Hyatt?
References: <p06240602cc35e58c6dc4@loud.pensive.org>
In-Reply-To: <p06240602cc35e58c6dc4@loud.pensive.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 25 Jul 2012 16:06:27 -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: Wed, 25 Jul 2012 23:06:28 -0000

On 7/25/2012 3:54 PM, Randall Gellens wrote:
> I may have a room at the Hyatt at CAD 194 (includes breakfast) for the
> full IETF week.  If anyone wants it, please let me know right away.


I could use a room at the Hyatt, but only for that Friday night.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From geoff.ietf@mulligan.com  Wed Jul 25 16:12:00 2012
Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07F7621F86C1 for <ietf@ietfa.amsl.com>; Wed, 25 Jul 2012 16:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYFDWuJ2p1XC for <ietf@ietfa.amsl.com>; Wed, 25 Jul 2012 16:11:59 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 81A9221F86AD for <ietf@ietf.org>; Wed, 25 Jul 2012 16:11:59 -0700 (PDT)
Received: from [199.233.92.4] (unknown [199.233.92.4]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 21A3D5F728; Wed, 25 Jul 2012 17:11:53 -0600 (MDT)
Message-ID: <50107D3E.2030902@mulligan.com>
Date: Wed, 25 Jul 2012 17:11:58 -0600
From: Geoff Mulligan <geoff.ietf@mulligan.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Anyone need a room at the Hyatt?
References: <p06240602cc35e58c6dc4@loud.pensive.org> <50107BEF.4040901@dcrocker.net>
In-Reply-To: <50107BEF.4040901@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Randall Gellens <randy@qualcomm.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, 25 Jul 2012 23:12:00 -0000

And I could possibly use a room for Thursday night...

On 07/25/2012 05:06 PM, Dave Crocker wrote:
>
>
> On 7/25/2012 3:54 PM, Randall Gellens wrote:
>> I may have a room at the Hyatt at CAD 194 (includes breakfast) for the
>> full IETF week.  If anyone wants it, please let me know right away.
>
>
> I could use a room at the Hyatt, but only for that Friday night.
>
> d/


From david.black@emc.com  Wed Jul 25 15:23:35 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 642AF21F860F; Wed, 25 Jul 2012 15:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level: 
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6sMlfx-ONYKB; Wed, 25 Jul 2012 15:23:34 -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 7776621F860D; Wed, 25 Jul 2012 15:23:34 -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 q6PMNXj2006170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 Jul 2012 18:23:33 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Wed, 25 Jul 2012 18:23:21 -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 q6PMNL4i021907; Wed, 25 Jul 2012 18:23:21 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Wed, 25 Jul 2012 18:23:21 -0400
From: <david.black@emc.com>
To: <ietf@ietf.org>
Date: Wed, 25 Jul 2012 18:23:19 -0400
Subject: RE: [storm] Last Call: <draft-ietf-storm-iscsi-sam-06.txt> (Internet	Small	Computer Systems Interface (iSCSI) SCSI Features	Update) to Proposed Standard
Thread-Topic: [storm] Last Call: <draft-ietf-storm-iscsi-sam-06.txt> (Internet	Small	Computer Systems Interface (iSCSI) SCSI Features	Update) to Proposed Standard
Thread-Index: Ac1jmPAUY2+NTO/yRKSSSk6Mu3Kr0wHGedfA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208DD9404@MX15A.corp.emc.com>
References: <20120716211939.22533.77051.idtracker@ietfa.amsl.com>
In-Reply-To: <20120716211939.22533.77051.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 26 Jul 2012 09:26:42 -0700
Cc: storm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2012 22:23:35 -0000

A number of the documents referenced by this draft are T10 (SCSI) standards
that are access-restricted to members of that organization unless a copy
is purchased - this requirement has been imposed by the parent organization
of T10; please do not complain to T10 about this.  As the official liaison
from T10 to the IETF, I am authorized to provide copies of these standards
to IETF participants for their personal use in IETF activity.

Of course, if you work for a company that is a T10 or T11 member, you can
get these documents directly, and I'd ask that you do so.

This applies to the following documents:

- Normative references:
-- T10
      [SAM2]      T10/1157D, SCSI Architecture Model - 2 (SAM-2).
      [SAM4]      ISO/IEC 14776-414, SCSI Architecture Model - 4 (SAM-4).

The Committee Drafts of [SAM5] and [SPC4] are public documents.  I can
help with access to them if there are problems.

If you would like copies of any of these standards, please send me an email
directly (please *don't* cc: either the IETF or STORM mailing lists) and
indicate which standards you would like copies of.

Of course, if you work for a company that is a T10 or T11 member, you can
obtain these documents directly, and I'd ask that you do so.


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
----------------------------------------------------

> -----Original Message-----
> From: storm-bounces@ietf.org [mailto:storm-bounces@ietf.org] On Behalf Of=
 The
> IESG
> Sent: Monday, July 16, 2012 5:20 PM
> To: IETF-Announce
> Cc: storm@ietf.org
> Subject: [storm] Last Call: <draft-ietf-storm-iscsi-sam-06.txt> (Internet
> Small Computer Systems Interface (iSCSI) SCSI Features Update) to Propose=
d
> Standard
>=20
>=20
> The IESG has received a request from the STORage Maintenance WG (storm)
> to consider the following document:
> - 'Internet Small Computer Systems Interface (iSCSI) SCSI Features
> Update'
>   <draft-ietf-storm-iscsi-sam-06.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-13. 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
> Please note the concurrent Last Call for draft-ietf-storm-iscsi-cons, as =
both
> drafts should be reviewed together.
>=20
> Abstract
>=20
>=20
>    Internet Small Computer Systems Interface (iSCSI) is a SCSI
>    transport protocol that maps the SCSI family of protocols onto
>    TCP/IP. The iSCSI protocol as specified in [draft-ietf-storm-
>    iscsi-cons-xx] (and as previously specified by the combination
>    of RFC 3720 and RFC 5048) is based on the SAM-2 (SCSI
>    Architecture Model - 2) version of the SCSI family of
>    protocols. This document defines enhancements to the iSCSI
>    protocol to support certain additional features of the SCSI
>    protocol that were defined in SAM-3, SAM-4, and SAM-5.
>=20
>    This document is a companion document to [draft-ietf-storm-
>    iscsi-cons-xx].
>=20
>       --------------------------------------------------------
>       RFC EDITORS NOTE: The above references to [draft-ietf-storm-
>       iscsi-cons-xx] should reference the RFC number assigned to
>       that document, and this note should be removed.
>       --------------------------------------------------------
>=20
> This last call explicitly identifies these downrefs in the normative
> references
> of this document:
>=20
>      [SAM2]      T10/1157D, SCSI Architecture Model - 2 (SAM-2).
>=20
>       [SAM4]      ISO/IEC 14776-414, SCSI Architecture Model - 4 (SAM-
>                   4).
>=20
>       [SAM5]      T10/2104D rev r04, SCSI Architecture Model - 5 (SAM-
>                   5), Committee Draft.
>=20
>       [SPC4]      T10/1731D rev r23, SCSI Primary Commands - 4 (SPC-4),
>                   Committee Draft.
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-storm-iscsi-sam/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-storm-iscsi-sam/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> storm mailing list
> storm@ietf.org
> https://www.ietf.org/mailman/listinfo/storm


From david.black@emc.com  Wed Jul 25 15:24:44 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 A823B21F8611; Wed, 25 Jul 2012 15:24:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zfi8HQEjKJI3; Wed, 25 Jul 2012 15:24:42 -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 8F03121F8605; Wed, 25 Jul 2012 15:24:42 -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 q6PMOJxs008981 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 Jul 2012 18:24:19 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Wed, 25 Jul 2012 18:24:07 -0400
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q6PMO6vC022621; Wed, 25 Jul 2012 18:24:06 -0400
Received: from mxhub38.corp.emc.com (128.222.70.105) by mxhub06.corp.emc.com (128.222.70.203) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 25 Jul 2012 18:24:06 -0400
Received: from mx15a.corp.emc.com ([169.254.1.189]) by mxhub38.corp.emc.com ([128.222.70.105]) with mapi; Wed, 25 Jul 2012 18:24:05 -0400
From: <david.black@emc.com>
To: <ietf@ietf.org>
Date: Wed, 25 Jul 2012 18:24:05 -0400
Subject: RE: [storm] Last Call: <draft-ietf-storm-iscsi-cons-06.txt> (iSCSI Protocol	(Consolidated)) to Proposed Standard
Thread-Topic: [storm] Last Call: <draft-ietf-storm-iscsi-cons-06.txt> (iSCSI Protocol	(Consolidated)) to Proposed Standard
Thread-Index: Ac1jmNrMAsNJQSnqTqmIPlssgGmhSQHGIIiQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71208DD9405@MX15A.corp.emc.com>
References: <20120716211850.4308.53226.idtracker@ietfa.amsl.com>
In-Reply-To: <20120716211850.4308.53226.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 26 Jul 2012 09:26:51 -0700
Cc: storm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jul 2012 22:24:44 -0000

A number of the documents referenced by this draft are T10 (SCSI) and T11 (=
FC)
standards that are access-restricted to members of those organizations unle=
ss
a copy is purchased - this requirement has been imposed by the parent organ=
ization
of T10 and T11; please do not complain to T10 or T11 about this.  As the
official liaison from both T10 and T11 to the IETF, I am authorized to prov=
ide
copies of these standards to IETF participants for their personal use in
IETF activity.

This applies to the following documents:

- Normative references:
-- T10
     [SAM2] T10/1157-D, SCSI Architecture Model - 2 (SAM-2).
     [SAM3] T10/1561-D, SCSI Architecture Model - 3 (SAM-3).
     [SAM4] T10/1683-D, SCSI Architecture Model - 4 (SAM-4).
     [SBC2] NCITS.405-205, SCSI Block Commands - 2 (SBC-2).
     [SPC3] T10/1416-D, SCSI Primary Commands-3.

-- T11
     [FC-FS] INCITS 373-2003, Fibre Channel Framing and Signaling
       Interface (FC-FS).

- Informative References
-- T10
     [SAS] INCITS 376-2003, Serial Attached SCSI (SAS).
     [SRP] INCITS 365-2002, SCSI RDMA Protocol (SRP).


If you would like copies of any of these standards, please send me an email
directly (please *don't* cc: either the IETF or STORM mailing lists) and
indicate which standards you would like copies of.

Of course, if you work for a company that is a T10 or T11 member, you can
get these documents directly, and I'd ask that you do so.

Thanks,
--David


> -----Original Message-----
> From: storm-bounces@ietf.org [mailto:storm-bounces@ietf.org] On Behalf Of=
 The
> IESG
> Sent: Monday, July 16, 2012 5:19 PM
> To: IETF-Announce
> Cc: storm@ietf.org
> Subject: [storm] Last Call: <draft-ietf-storm-iscsi-cons-06.txt> (iSCSI
> Protocol (Consolidated)) to Proposed Standard
>=20
>=20
> The IESG has received a request from the STORage Maintenance WG (storm)
> to consider the following document:
> - 'iSCSI Protocol (Consolidated)'
>   <draft-ietf-storm-iscsi-cons-06.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-13. 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
> Please note the concurrent Last Call for draft-ietf-storm-iscsi-sam, as b=
oth
> drafts should be reviewed together.
>=20
> Abstract
>=20
>=20
>   This document describes a transport protocol for SCSI that works
>   on top of TCP. The iSCSI protocol aims to be fully compliant with
>   the standardized SCSI Architecture Model (SAM-2). RFC 3720
>   defined the original iSCSI protocol. RFC 3721 discusses iSCSI
>   Naming examples and discovery techniques. Subsequently, RFC 3980
>   added an additional naming format to iSCSI protocol. RFC 4850
>   followed up by adding a new public extension key to iSCSI. RFC
>   5048 offered a number of clarifications and a few improvements and
>   corrections to the original iSCSI protocol.
>=20
>=20
>   This document obsoletes RFCs 3720, 3980, 4850 and 5048 by
>   consolidating them into a single document and making additional
>   updates to the consolidated specification. This document also
>   updates RFC 3721 and RFC 3723. The text in this document thus
>   supersedes the text in all the noted RFCs wherever there is a
>   difference in semantics.
>=20
> This last call explicitly identifies these downrefs in the normative
> references
> of this document:
>      [EUI] "Guidelines for 64-bit Global Identifier (EUI-64)",
>        http://standards.ieee.org/regauth/oui/tutorials/EUI64.html
>=20
>      [FC-FS] INCITS 373-2003, Fibre Channel Framing and Signaling
>        Interface (FC-FS).
>=20
>      [OUI] "IEEE OUI and Company_Id Assignments",
>        http://standards.ieee.org/regauth/oui
>=20
>     [SAM2] T10/1157-D, SCSI Architecture Model - 2 (SAM-2).
>=20
>      [SAM3] T10/1561-D, SCSI Architecture Model - 3 (SAM-3).
>=20
>      [SAM4] T10/1683-D, SCSI Architecture Model - 4 (SAM-4).
>=20
>      [SBC2] NCITS.405-205, SCSI Block Commands - 2 (SBC-2).
>=20
>      [SPC3] T10/1416-D, SCSI Primary Commands-3.
>=20
>      [UML]   ISO/IEC 19501, Unified Modeling Language
>        Specification Version 1.4.2.
>=20
>      [UNICODE] Unicode Standard Annex #15, "Unicode Normalization
>        Forms", http://www.unicode.org/unicode/reports/tr15
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-storm-iscsi-cons/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-storm-iscsi-cons/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> storm mailing list
> storm@ietf.org
> https://www.ietf.org/mailman/listinfo/storm


From narten@us.ibm.com  Thu Jul 26 21:53:48 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 94CEF11E80A3 for <ietf@ietfa.amsl.com>; Thu, 26 Jul 2012 21:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.107
X-Spam-Level: 
X-Spam-Status: No, score=-109.107 tagged_above=-999 required=5 tests=[AWL=-1.108, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+L715F1Z9T0 for <ietf@ietfa.amsl.com>; Thu, 26 Jul 2012 21:53:47 -0700 (PDT)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 87EE311E8073 for <ietf@ietf.org>; Thu, 26 Jul 2012 21:53:47 -0700 (PDT)
Received: from /spool/local by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 26 Jul 2012 22:53:45 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 26 Jul 2012 22:53:05 -0600
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 849691FF001B for <ietf@ietf.org>; Fri, 27 Jul 2012 04:53:02 +0000 (WET)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q6R4r4NH134108 for <ietf@ietf.org>; Thu, 26 Jul 2012 22:53:04 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q6R4r4nR031677 for <ietf@ietf.org>; Thu, 26 Jul 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q6R4r3Ie031642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 26 Jul 2012 22:53:04 -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 q6R4r3MB012071 for <ietf@ietf.org>; Fri, 27 Jul 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q6R4r3tR012045 for ietf@ietf.org; Fri, 27 Jul 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201207270453.q6R4r3tR012045@rotala.raleigh.ibm.com>
Date: Fri, 27 Jul 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: 12072704-1780-0000-0000-000007C829FA
X-IBM-ISS-SpamDetectors: 
X-IBM-ISS-DetailInfo: BY=3.00000288; HX=3.00000193; KW=3.00000007; PH=3.00000001; SC=3.00000006; SDB=6.00160141; UDB=6.00036172; UTC=2012-07-27 04:53:41
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 04:53:48 -0000

Total of 116 messages in the last 7 days.
 
script run at: Fri Jul 27 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.90% |    8 |  6.19% |    47718 | johnl@taugh.com
  3.45% |    4 |  4.06% |    31272 | glenzorn@gmail.com
  2.59% |    3 |  4.20% |    32317 | ietfdbh@comcast.net
  3.45% |    4 |  3.12% |    24019 | rbarnes@bbn.com
  3.45% |    4 |  3.11% |    23984 | melinda.shore@gmail.com
  2.59% |    3 |  3.12% |    24019 | stephen.farrell@cs.tcd.ie
  2.59% |    3 |  3.09% |    23786 | abdussalambaryun@gmail.com
  2.59% |    3 |  2.91% |    22444 | marshall.eubanks@gmail.com
  2.59% |    3 |  2.83% |    21837 | jmpolk@cisco.com
  2.59% |    3 |  2.80% |    21607 | fred@cisco.com
  2.59% |    3 |  2.33% |    17939 | ynir@checkpoint.com
  2.59% |    3 |  2.08% |    16036 | dhc@dcrocker.net
  2.59% |    3 |  2.01% |    15474 | iad@ietf.org
  1.72% |    2 |  2.67% |    20578 | david.black@emc.com
  1.72% |    2 |  1.85% |    14287 | keith.drage@alcatel-lucent.com
  1.72% |    2 |  1.67% |    12858 | richard@shockey.us
  1.72% |    2 |  1.66% |    12800 | warren@kumari.net
  1.72% |    2 |  1.63% |    12553 | brian.e.carpenter@gmail.com
  1.72% |    2 |  1.63% |    12547 | sob@sobco.com
  1.72% |    2 |  1.56% |    12019 | scott.brim@gmail.com
  1.72% |    2 |  1.50% |    11551 | weiler@watson.org
  1.72% |    2 |  1.49% |    11495 | cabo@tzi.org
  1.72% |    2 |  1.49% |    11480 | dworley@avaya.com
  1.72% |    2 |  1.41% |    10866 | paul.hoffman@vpnc.org
  1.72% |    2 |  1.39% |    10694 | joelja@bogus.com
  0.86% |    1 |  1.60% |    12334 | repenno@cisco.com
  0.86% |    1 |  1.42% |    10941 | mary.ietf.barnes@gmail.com
  0.86% |    1 |  1.29% |     9966 | badimuh@gmail.com
  0.86% |    1 |  1.10% |     8442 | ben@nostrum.com
  0.86% |    1 |  1.08% |     8307 | chris.dearlove@baesystems.com
  0.86% |    1 |  1.01% |     7795 | leifj@nordu.net
  0.86% |    1 |  1.01% |     7746 | narten@us.ibm.com
  0.86% |    1 |  0.99% |     7626 | d.malas@cablelabs.com
  0.86% |    1 |  0.96% |     7433 | hartmans-ietf@mit.edu
  0.86% |    1 |  0.90% |     6944 | john.border@hughes.com
  0.86% |    1 |  0.90% |     6918 | amalis@gmail.com
  0.86% |    1 |  0.89% |     6842 | duerst@it.aoyama.ac.jp
  0.86% |    1 |  0.88% |     6814 | victor.kuarsingh@gmail.com
  0.86% |    1 |  0.88% |     6771 | julian.reschke@gmx.de
  0.86% |    1 |  0.88% |     6752 | pthubert@cisco.com
  0.86% |    1 |  0.87% |     6696 | bob.hinden@gmail.com
  0.86% |    1 |  0.86% |     6648 | henk.uijterwaal@gmail.com
  0.86% |    1 |  0.86% |     6588 | hallam@gmail.com
  0.86% |    1 |  0.84% |     6501 | yaojk@cnnic.cn
  0.86% |    1 |  0.84% |     6436 | ggx@gigix.net
  0.86% |    1 |  0.83% |     6383 | agmalis@gmail.com
  0.86% |    1 |  0.82% |     6289 | rpelletier@isoc.org
  0.86% |    1 |  0.81% |     6212 | ole@cisco.com
  0.86% |    1 |  0.80% |     6166 | kathleen.moriarty@emc.com
  0.86% |    1 |  0.78% |     6046 | sob@harvard.edu
  0.86% |    1 |  0.78% |     6031 | stbryant@cisco.com
  0.86% |    1 |  0.78% |     6008 | alexandru.petrescu@gmail.com
  0.86% |    1 |  0.77% |     5912 | dwm@xpasc.com
  0.86% |    1 |  0.77% |     5902 | sarikaya2012@gmail.com
  0.86% |    1 |  0.76% |     5838 | lixia@cs.ucla.edu
  0.86% |    1 |  0.75% |     5776 | lear@cisco.com
  0.86% |    1 |  0.75% |     5748 | randy@qualcomm.com
  0.86% |    1 |  0.74% |     5736 | yaakov_s@rad.com
  0.86% |    1 |  0.74% |     5714 | mrex@sap.com
  0.86% |    1 |  0.73% |     5603 | ford@isoc.org
  0.86% |    1 |  0.72% |     5550 | hannes.tschofenig@gmx.net
  0.86% |    1 |  0.71% |     5474 | martin.thomson@gmail.com
  0.86% |    1 |  0.69% |     5348 | bortzmeyer@nic.fr
  0.86% |    1 |  0.66% |     5116 | john-ietf@jck.com
  0.86% |    1 |  0.66% |     5070 | simon.perreault@viagenie.ca
  0.86% |    1 |  0.65% |     5017 | cos@aaaaa.org
  0.86% |    1 |  0.64% |     4908 | geoff.ietf@mulligan.com
  0.86% |    1 |  0.63% |     4883 | ajs@anvilwalrusden.com
  0.86% |    1 |  0.60% |     4628 | randy@psg.com
  0.86% |    1 |  0.56% |     4295 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |  116 |100.00% |   770333 | Total


From joelja@bogus.com  Fri Jul 27 11:14:04 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 6216911E80A1; Fri, 27 Jul 2012 11:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HF+OKCuXck-G; Fri, 27 Jul 2012 11:14:03 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id DAC7B11E8096; Fri, 27 Jul 2012 11:14:03 -0700 (PDT)
Received: from dhcp-6624.meeting.ietf.org (dhcp-6624.meeting.ietf.org [130.129.102.36]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q6RIE3Lo098450 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 27 Jul 2012 18:14:03 GMT (envelope-from joelja@bogus.com)
Message-ID: <5012DA6B.5070501@bogus.com>
Date: Fri, 27 Jul 2012 11:14:03 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120717 Thunderbird/15.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [OPSAWG] Last Call: <draft-ietf-opsawg-automated-network-configuration-04.txt> (Problem Statement for the Automated Configuration of Large IP	Networks) to Informational RFC
References: <20120725181357.21674.65763.idtracker@ietfa.amsl.com>
In-Reply-To: <20120725181357.21674.65763.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 27 Jul 2012 18:14:03 +0000 (UTC)
Cc: opsawg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 18:14:04 -0000

The document spends more time on the taxonomy of the existing solutions 
then I think is really warranted for a document purportory to be a 
problem statement.

That said I think the document is a worst harmless, and describes the 
problem fairly well.

joel

On 7/25/12 11:13 AM, The IESG wrote:
> The IESG has received a request from the Operations and Management Area
> Working Group WG (opsawg) to consider the following document:
> - 'Problem Statement for the Automated Configuration of Large IP
> Networks'
>    <draft-ietf-opsawg-automated-network-configuration-04.txt> as
> Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-15. 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 memo discusses the steps required to bring a large number of
>     devices into service in IP networks in an automated fashion.  The
>     goal of this document is to list known solutions where they exist, to
>     point out approaches proven to be problematic, and to identify gaps
>     that require further specifications.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-automated-network-configuration/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-opsawg-automated-network-configuration/ballot/
>
>
> The following IPR Declarations may be related to this I-D:
>
>     http://datatracker.ietf.org/ipr/1706/
>     http://datatracker.ietf.org/ipr/1735/
>
>
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>


From chair@ietf.org  Fri Jul 27 14:28:38 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 4F6E611E8097 for <ietf@ietfa.amsl.com>; Fri, 27 Jul 2012 14:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTGCKfGn-523 for <ietf@ietfa.amsl.com>; Fri, 27 Jul 2012 14:28:37 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id C8CFD11E808A for <ietf@ietf.org>; Fri, 27 Jul 2012 14:28:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A705B12D0EC for <ietf@ietf.org>; Fri, 27 Jul 2012 14:28:38 -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 RV5wOywh+3lt for <ietf@ietf.org>; Fri, 27 Jul 2012 14:28:38 -0700 (PDT)
Received: from d142-058-230-001.wireless.sfu.ca (d142-058-230-001.wireless.sfu.ca [142.58.230.1]) by c8a.amsl.com (Postfix) with ESMTPSA id 8797112D0EA for <ietf@ietf.org>; Fri, 27 Jul 2012 14:28:37 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Memorial for RL "Bob" Morgan
From: IETF Chair <chair@ietf.org>
In-Reply-To: <500707B1.2090100@KingsMountain.com>
Date: Fri, 27 Jul 2012 17:28:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B751F7F-3AF8-4AF2-92C0-3D384FBCD4C4@ietf.org>
References: <500707B1.2090100@KingsMountain.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: Fri, 27 Jul 2012 21:28:38 -0000

The memorial service for RL "Bob" Morgan will take place on Sunday.  =
Since many of his friends will be in Vancouver for the IETF meeting, we =
have arranged a room at the Hyatt hotel to receive the broadcast from =
the the memorial as it takes place in Seattle.  If you want to =
participate, please come to Regency F from 11:00AM - 2:00PM on Sunday.

I miss RL "Bob" Morgan.  I am sure many others in the IETF community do =
as well.

Russ


On Jul 18, 2012, at 3:00 PM, =3DJeffH wrote:

> Hi,
>=20
> I'm very sorry for repetition if you've already heard this, and =
sorrier still to feel compelled to bring it to you all's broad attention =
in any case...
>=20
> RL "Bob" Morgan, long-time IETF participant (since at least the =
Stanford IETF-14 in Summer 1989), passed away due to complications of =
cancer on 12-Jul-2012.
>=20
> He is sorely missed, and IETF meetings/activities won't seem the same =
without his most trenchant perspectives, observations, contributions, =
and camaraderie.
>=20
> For more information and tributes, see..
>=20
> https://spaces.internet2.edu/display/rlbob/
>=20
>=20
> =3DJeffH
>=20


From paul.hoffman@vpnc.org  Fri Jul 27 14:42:06 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 A710011E80A5; Fri, 27 Jul 2012 14:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ZGDI-ho3W4T; Fri, 27 Jul 2012 14:42:06 -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 0117211E8080; Fri, 27 Jul 2012 14:42:05 -0700 (PDT)
Received: from sn87.proper.com (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q6RKop9K022921 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 27 Jul 2012 13:50:52 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: Memorial for RL "Bob" Morgan
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <0B751F7F-3AF8-4AF2-92C0-3D384FBCD4C4@ietf.org>
Date: Fri, 27 Jul 2012 14:42:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <11358423-A51A-4353-A883-C5BFA2BF13BC@vpnc.org>
References: <500707B1.2090100@KingsMountain.com> <0B751F7F-3AF8-4AF2-92C0-3D384FBCD4C4@ietf.org>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1278)
Cc: Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 21:42:06 -0000

On Jul 27, 2012, at 2:28 PM, IETF Chair wrote:

> The memorial service for RL "Bob" Morgan will take place on Sunday.  =
Since many of his friends will be in Vancouver for the IETF meeting, we =
have arranged a room at the Hyatt hotel to receive the broadcast from =
the the memorial as it takes place in Seattle.  If you want to =
participate, please come to Regency F from 11:00AM - 2:00PM on Sunday.
>=20
> I miss RL "Bob" Morgan.  I am sure many others in the IETF community =
do as well.

For those of you whom are only now finding out about Bob's death, here's =
a bit of background:

On Jul 26, 2012, at 3:06 PM, Michael R. Gettes wrote:

> The tribute web site has been updated with information about the =
Memorial for Bob to
> be held this Sunday @ 11 AM Pacific Time, 2PM Eastern, 7PM London and =
4AM Monday in Sydney.
>=20
> Please visit https://spaces.internet2.edu/display/rlbob/Home for more =
information.
>=20
> The event will be broadcast video with an accompanying twitter feed.
>=20
> Please consider a donation to the education of Bob's children or to a =
charity in his name.
> Information about donating can be found on his tribute web site.
>=20
> Please feel free to forward this email as you see fit to ensure =
everyone is aware of the event.



From paf@frobbit.se  Fri Jul 27 14:48:20 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 C9C4521F85C6; Fri, 27 Jul 2012 14:48:20 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nPt0d3mlkX1v; Fri, 27 Jul 2012 14:48:20 -0700 (PDT)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id EC20321F84EA; Fri, 27 Jul 2012 14:48:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id EBD9E14435BDC; Fri, 27 Jul 2012 23:48:18 +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 e9U8VnBTr8Ym; Fri, 27 Jul 2012 23:48:14 +0200 (CEST)
Received: from [192.165.72.14] (unknown [192.165.72.14]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 7087314435BCD; Fri, 27 Jul 2012 23:48:14 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: Re: Memorial for RL "Bob" Morgan
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <11358423-A51A-4353-A883-C5BFA2BF13BC@vpnc.org>
Date: Fri, 27 Jul 2012 23:48:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <45AB8A7A-0DF1-4FA0-AB90-1485F90F52AD@frobbit.se>
References: <500707B1.2090100@KingsMountain.com> <0B751F7F-3AF8-4AF2-92C0-3D384FBCD4C4@ietf.org> <11358423-A51A-4353-A883-C5BFA2BF13BC@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1485)
Cc: IETF <ietf@ietf.org>, Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jul 2012 21:48:20 -0000

27 jul 2012 kl. 23:42 skrev Paul Hoffman <paul.hoffman@vpnc.org>:

>> I miss RL "Bob" Morgan.  I am sure many others in the IETF community =
do as well.
>=20
> For those of you whom are only now finding out about Bob's death, =
here's a bit of background:

There is an article in the latest version of IETF Journal where he plays =
an important part, including photo of him.

=
http://www.internetsociety.org/articles/implementing-identity-management-s=
olutions

I am happy to see the addition to the article online that of course does =
not exist in the printed version.

   Patrik


From abdussalambaryun@gmail.com  Sat Jul 28 06:12:43 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 53AA421F85FC; Sat, 28 Jul 2012 06:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.458
X-Spam-Level: 
X-Spam-Status: No, score=-3.458 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGIJA5TRZNpG; Sat, 28 Jul 2012 06:12:42 -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 98E7A21F85FB; Sat, 28 Jul 2012 06:12:42 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so3630599vcb.31 for <multiple recipients>; Sat, 28 Jul 2012 06:12:42 -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=KnxBnpDOaDqDJhEyVQR8x5868a5ezOdOynm/6e7X8s8=; b=eogTPEJ2/WnuYaPvsg2da8lUGLkz2yM05yvdXffiogNJLI/eFLz/ynFEx9TZgAFtjR FqCJXhbaD8GLmqX0Fo/h0OFhpyHVx1g0EbihSEckGlSAm0NVOmy2LGbu5qt6RR0a1ZqM WUuk2OpRAw2GqhXGXKjYVtQWMxFnmPbwVevuPvnkl3uMD3jSKoMwekkxdfHcpUqkh5Rk +VvQfFQpx1Hcm3Oz8yN8Zdhg/y3Et0LsM1mm14BDIk943T10ZAnB8PwamRdHpY8E5DLT vvqCHf/okoqG9VDNWPVPNxcm5qOIKv+uz9LjOsAEO4FtVJj/mKCmXsql4DMqWBvh/7Iq O8Nw==
MIME-Version: 1.0
Received: by 10.220.204.212 with SMTP id fn20mr5510472vcb.43.1343481162020; Sat, 28 Jul 2012 06:12:42 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Sat, 28 Jul 2012 06:12:41 -0700 (PDT)
Date: Sat, 28 Jul 2012 15:12:41 +0200
Message-ID: <CADnDZ89c42DQ95OrHn+G-x3sLrHw7ktzwXvrwkBR+gQshzR_1A@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-opsawg-automated-network-configuration-04.txt> (Problem Statement for the Automated Configuration of Large IP Networks) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@ietf.org" <iesg@ietf.org>, tina.tsou.zouting@huawei.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jul 2012 13:12:43 -0000

The draft-04 states in page-8:
---------------------------------------------------------------------------------------------------------------
5.1. Establishment of Link Layer Connectivity
The protocol aspects of this phase are out of scope, since it
involves non-IETF protocols only. While some link-layer technologies
may provide authentication and access control, this cannot be assumed
to be available in the general case.
---------------------------------------------------------------------------------------------------------------

If Link protocol is a non-IETF why it will be out of scope while used
by the IP devices? in the end the IP is over link protocols and
interacts with the below protocols. Why we need
applicability-statements or problem-statements if we think the link
layer is out of scope of IETF-RFCs?

Regards
AB

From hallam@gmail.com  Sat Jul 28 15:33:54 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 65BF621F8667; Sat, 28 Jul 2012 15:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.646
X-Spam-Level: 
X-Spam-Status: No, score=-5.646 tagged_above=-999 required=5 tests=[AWL=-2.048, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bjL9XpTxEln6; Sat, 28 Jul 2012 15:33:53 -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 6203421F8604; Sat, 28 Jul 2012 15:33:53 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so7343111obb.31 for <multiple recipients>; Sat, 28 Jul 2012 15:33:53 -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=Igh2QTPuWVWzKYO9+2EZAfGqYSdb2ObBB9+TtSY5du8=; b=D5CM8F1cfMUBbyBCMkNzOCQFttgJkdeFdgWlN3uPhaWVgT0zjAINgpqvpsmDA95XTi 2LtDzMIHYPgD++WrDVvqeR5F1SZq/hGrS/zjcK1SDYphBcPta//ltEQ8YCZypZoRzMe+ V7SUL6vT8xJiu72IwqCkPgwHkW23shIIasrGuq5K0PCK+HMUWULcvOTyafXO9vTnsvV+ Xu7dOvZQmDO7s/F4U7qyHOTZjPFj9a8+lbW6+6fshElpNIJUQMAdnSk2dyIeKXMkH2Q6 84AJe9Y2M/gOSZbX+Yh3scLvTqUX3NiVs3ngLQLfmA0qA47s2EO3WwqZEwfGcYkJawg0 n44w==
MIME-Version: 1.0
Received: by 10.60.25.38 with SMTP id z6mr10184696oef.15.1343514832907; Sat, 28 Jul 2012 15:33:52 -0700 (PDT)
Received: by 10.76.71.169 with HTTP; Sat, 28 Jul 2012 15:33:52 -0700 (PDT)
In-Reply-To: <20120724184608.32185.77247.idtracker@ietfa.amsl.com>
References: <20120724184608.32185.77247.idtracker@ietfa.amsl.com>
Date: Sat, 28 Jul 2012 18:33:52 -0400
Message-ID: <CAMm+Lwg5YGiz+WCuTfM1Sv0DB9NSRvMr-YoLujCoBRrE8KQRbw@mail.gmail.com>
Subject: Re: Co-Hosts Announced for IETF 86 in Orlando
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Administrative Director <iad@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8ff253ae5daef704c5eb6c29
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>, "wgchairs@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: Sat, 28 Jul 2012 22:33:54 -0000

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

There must be a cheaper way for NBC commentators to work out who Sir Tim
Berners-Lee is.

Perhaps we should have someone give an innane commentary...


On Tuesday, July 24, 2012, IETF Administrative Director wrote:

> The IAOC is pleased to announce the Co-Hosts for IETF 86 in Orlando
> Florida, USA
> March 10 - 15, 2013.
>
> The Co-Hosts are Comcast and NBCUniversal.  Comcast Hosted IETF 71 in
> Philadelphia, is
> sponsoring IETF 85 in Atlanta, and has sponsored meeting breaks and ice
> cream socials at
> other meetings.  <http://www.comcast.com>
>
> NBCUniversal is Hosting its first meeting with the IETF.  <
> http://www.nbcuni.com/>
>
> We want to thank our benefactors.  The IETF cannot support its technical
> standards efforts,
> including the Secretariat and RFC Editor, without the generous support of
> its hosts and
> sponsors.
>
> Interested in hosting or sponsoring an IETF meeting?  Contact Drew
> Dvorshak at
> dvorshak@isoc.org <javascript:;>.  The meeting schedule is here:  <
> https://www.ietf.org/meeting/
> upcoming.html>
>
> Thanks again to Comcast and NBCUniversal!
>
> We are just days away from IETF 84 in Vancouver.  Registrations are open
> and operators
> are standing by (so to speak).  Visit <
> https://www.ietf.org/meeting/84/index.html> and join
> the 1,250 who have already registered.
>
> Ray Pelletier
> IETF Administrative Director
>


-- 
Website: http://hallambaker.com/

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

<div>There must be a cheaper way for NBC commentators to work out who Sir T=
im Berners-Lee is.</div><div><br></div><div>Perhaps we should have someone =
give an innane commentary...<span></span></div><br><br>On Tuesday, July 24,=
 2012, IETF Administrative Director  wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The IAOC is pleased to announce the Co-Hosts=
 for IETF 86 in Orlando Florida, USA<br>
March 10 - 15, 2013.<br>
<br>
The Co-Hosts are Comcast and NBCUniversal. =A0Comcast Hosted IETF 71 in Phi=
ladelphia, is<br>
sponsoring IETF 85 in Atlanta, and has sponsored meeting breaks and ice cre=
am socials at<br>
other meetings. =A0&lt;<a href=3D"http://www.comcast.com" target=3D"_blank"=
>http://www.comcast.com</a>&gt;<br>
<br>
NBCUniversal is Hosting its first meeting with the IETF. =A0&lt;<a href=3D"=
http://www.nbcuni.com/" target=3D"_blank">http://www.nbcuni.com/</a>&gt;<br=
>
<br>
We want to thank our benefactors. =A0The IETF cannot support its technical =
standards efforts,<br>
including the Secretariat and RFC Editor, without the generous support of i=
ts hosts and<br>
sponsors.<br>
<br>
Interested in hosting or sponsoring an IETF meeting? =A0Contact Drew Dvorsh=
ak at<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;dvorshak=
@isoc.org&#39;)">dvorshak@isoc.org</a>. =A0The meeting schedule is here: =
=A0&lt;<a href=3D"https://www.ietf.org/meeting/
upcoming.html" target=3D"_blank">https://www.ietf.org/meeting/<br>
upcoming.html</a>&gt;<br>
<br>
Thanks again to Comcast and NBCUniversal!<br>
<br>
We are just days away from IETF 84 in Vancouver. =A0Registrations are open =
and operators<br>
are standing by (so to speak). =A0Visit &lt;<a href=3D"https://www.ietf.org=
/meeting/84/index.html" target=3D"_blank">https://www.ietf.org/meeting/84/i=
ndex.html</a>&gt; and join<br>
the 1,250 who have already registered.<br>
<br>
Ray Pelletier<br>
IETF Administrative Director<br>
</blockquote><br><br>-- <br>Website: <a href=3D"http://hallambaker.com/">ht=
tp://hallambaker.com/</a><br><br>

--e89a8ff253ae5daef704c5eb6c29--

From hallam@gmail.com  Sat Jul 28 16:19:14 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 6B57621F8691; Sat, 28 Jul 2012 16:19:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level: 
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[AWL=-2.029, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o2q7LYKBMxY5; Sat, 28 Jul 2012 16:19:13 -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 6720521F860B; Sat, 28 Jul 2012 16:19:13 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so7398621obb.31 for <multiple recipients>; Sat, 28 Jul 2012 16:19:13 -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=8Jt+yMIE4VN0PhrvbjzXGu7wUWdPmuNs0Y0Z2vf+zes=; b=Uqhx75yUbf6Uh+w3mWTb5XAUcO/bz7/i4H20MAnQGM9oldVkfsJDdUNY+VTBhpoA6m lW3vqIZNxV0S30MVqBCT6T5eP9QLxZwpwZXJW9okCVGaeTF7jWUW8KzsAs/MU5Faierc OP2yqo4vUtEoXDEFIaMAsYx/QtQOOX1C2pjoQ0d5bONEQHvIx155cDnFV2RMsNXVlYZS r7gu2seJIXCyeoQDJRBJlkZUZHmprHYtO/oiiThcqMGvJm2pYakjFk+OVlRkMzeWHSW0 pGceB6QN79B2SWKvCOnLVEzodZdi+5VWQO8WPhPESIdJSQH9YDv5QGcch5U6Nhw+RbxQ wJnQ==
MIME-Version: 1.0
Received: by 10.182.50.98 with SMTP id b2mr10344293obo.28.1343517552968; Sat, 28 Jul 2012 16:19:12 -0700 (PDT)
Received: by 10.76.71.169 with HTTP; Sat, 28 Jul 2012 16:19:12 -0700 (PDT)
In-Reply-To: <20120724184608.32185.77247.idtracker@ietfa.amsl.com>
References: <20120724184608.32185.77247.idtracker@ietfa.amsl.com>
Date: Sat, 28 Jul 2012 19:19:12 -0400
Message-ID: <CAMm+LwjGoHMU_NGFJW9q_HEgn+NzVRGPx+eukN6u3-ZCrrmcWA@mail.gmail.com>
Subject: Re: Co-Hosts Announced for IETF 86 in Orlando
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Administrative Director <iad@ietf.org>
Content-Type: multipart/alternative; boundary=f46d044481d97e84a204c5ec0ef6
Cc: "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>, "wgchairs@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: Sat, 28 Jul 2012 23:19:14 -0000

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

There must be a cheaper way for NBC commentators to work out who Sir Tim
Berners-Lee is.

Perhaps we should have someone give an innane commentary...


On Tuesday, July 24, 2012, IETF Administrative Director wrote:

> The IAOC is pleased to announce the Co-Hosts for IETF 86 in Orlando
> Florida, USA
> March 10 - 15, 2013.
>
> The Co-Hosts are Comcast and NBCUniversal.  Comcast Hosted IETF 71 in
> Philadelphia, is
> sponsoring IETF 85 in Atlanta, and has sponsored meeting breaks and ice
> cream socials at
> other meetings.  <http://www.comcast.com>
>
> NBCUniversal is Hosting its first meeting with the IETF.  <
> http://www.nbcuni.com/>
>
> We want to thank our benefactors.  The IETF cannot support its technical
> standards efforts,
> including the Secretariat and RFC Editor, without the generous support of
> its hosts and
> sponsors.
>
> Interested in hosting or sponsoring an IETF meeting?  Contact Drew
> Dvorshak at
> dvorshak@isoc.org <javascript:;>.  The meeting schedule is here:  <
> https://www.ietf.org/meeting/
> upcoming.html>
>
> Thanks again to Comcast and NBCUniversal!
>
> We are just days away from IETF 84 in Vancouver.  Registrations are open
> and operators
> are standing by (so to speak).  Visit <
> https://www.ietf.org/meeting/84/index.html> and join
> the 1,250 who have already registered.
>
> Ray Pelletier
> IETF Administrative Director
>


-- 
Website: http://hallambaker.com/

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

<div>There must be a cheaper way for NBC commentators to work out who Sir T=
im Berners-Lee is.</div><div><br></div><div>Perhaps we should have someone =
give an innane commentary...<span></span></div><br><br>On Tuesday, July 24,=
 2012, IETF Administrative Director  wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The IAOC is pleased to announce the Co-Hosts=
 for IETF 86 in Orlando Florida, USA<br>
March 10 - 15, 2013.<br>
<br>
The Co-Hosts are Comcast and NBCUniversal. =A0Comcast Hosted IETF 71 in Phi=
ladelphia, is<br>
sponsoring IETF 85 in Atlanta, and has sponsored meeting breaks and ice cre=
am socials at<br>
other meetings. =A0&lt;<a href=3D"http://www.comcast.com" target=3D"_blank"=
>http://www.comcast.com</a>&gt;<br>
<br>
NBCUniversal is Hosting its first meeting with the IETF. =A0&lt;<a href=3D"=
http://www.nbcuni.com/" target=3D"_blank">http://www.nbcuni.com/</a>&gt;<br=
>
<br>
We want to thank our benefactors. =A0The IETF cannot support its technical =
standards efforts,<br>
including the Secretariat and RFC Editor, without the generous support of i=
ts hosts and<br>
sponsors.<br>
<br>
Interested in hosting or sponsoring an IETF meeting? =A0Contact Drew Dvorsh=
ak at<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;dvorshak=
@isoc.org&#39;)">dvorshak@isoc.org</a>. =A0The meeting schedule is here: =
=A0&lt;<a href=3D"https://www.ietf.org/meeting/
upcoming.html" target=3D"_blank">https://www.ietf.org/meeting/<br>
upcoming.html</a>&gt;<br>
<br>
Thanks again to Comcast and NBCUniversal!<br>
<br>
We are just days away from IETF 84 in Vancouver. =A0Registrations are open =
and operators<br>
are standing by (so to speak). =A0Visit &lt;<a href=3D"https://www.ietf.org=
/meeting/84/index.html" target=3D"_blank">https://www.ietf.org/meeting/84/i=
ndex.html</a>&gt; and join<br>
the 1,250 who have already registered.<br>
<br>
Ray Pelletier<br>
IETF Administrative Director<br>
</blockquote><br><br>-- <br>Website: <a href=3D"http://hallambaker.com/">ht=
tp://hallambaker.com/</a><br><br>

--f46d044481d97e84a204c5ec0ef6--

From adrian@olddog.co.uk  Sat Jul 28 21:43:44 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 CF62721F86A8; Sat, 28 Jul 2012 21:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ynR8JUwWVy29; Sat, 28 Jul 2012 21:43:44 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 0B97721F8666; Sat, 28 Jul 2012 21:43:42 -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 q6T4hd7a030362;  Sun, 29 Jul 2012 05:43:39 +0100
Received: from 950129200 ([130.129.68.110]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q6T4hYIu030151 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 29 Jul 2012 05:43:37 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized Link State Routing Protocol version 2) to Proposed Standard
Date: Sun, 29 Jul 2012 05:42:45 +0100
Message-ID: <024701cd6d44$b8d80160$2a880420$@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: Ac1tRJV354xo90DRS1egTZvG+nyJhQ==
Content-Language: en-gb
Cc: manet@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 04:43:45 -0000

All,
Please note this last call was re-started to handle a downref I missed first
time around.

Adrian

> -----Original Message-----
> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of
> The IESG
> Sent: 29 July 2012 00:28
> To: IETF-Announce
> Cc: manet@ietf.org
> Subject: [manet] Last Call: <draft-ietf-manet-olsrv2-15.txt> (The Optimized
Link
> State Routing Protocol version 2) to Proposed Standard
> 
> 
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'The Optimized Link State Routing Protocol version 2'
>   <draft-ietf-manet-olsrv2-15.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-08-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting. This last call
> period has been extended to handle the fact that it spans the IETF-84
> meeting.
> 
> This last call is being re-initiated to include a notice that this document
> includes a normative down reference to an Informational RFC:
> RFC5148, "Jitter considerations in MANETs".
> 
> Abstract
> 
>    This specification describes version 2 of the Optimized Link State
>    Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-manet-olsrv2/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From yaronf.ietf@gmail.com  Sun Jul 29 05:52:10 2012
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 921B521F8620 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 05:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D2fQm71wLTbq for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 05:52:10 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id BC28621F856D for <ietf@ietf.org>; Sun, 29 Jul 2012 05:52:09 -0700 (PDT)
Received: by weyu54 with SMTP id u54so3388811wey.31 for <ietf@ietf.org>; Sun, 29 Jul 2012 05:52:09 -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 :content-type:content-transfer-encoding; bh=Hc1YcN9WyLLbA8BHJ+EjE6FESaT/qh6Owz5JmNMF4IE=; b=OqGeuogTZFnpm5wM5pkompZ/KaK1GODs1Pn+xCpsNZ/VMS0qZKozJJ1Xyzd598BUTy OKIG8y88tOroG6+YZgsAbWI+Ble0YHolHw4On6L65zfbouAfky597+JAEW0ggNji1iLq NHTeGuUzTsPngQEAGjlrNnfdk+3Pqf7RtjqyVwHPZEgOBeRQFpb3XWHRE06brZgI8BPs XTn2pZ13O/MsWI9mHpoV/PzGRGCtVeElybSs4JXHHo7FslJZQTmBvXe96nYlR6NQ+ijJ wWsjACy/V9umyOP4Mi0cUJDmDPlrRG7W62VFjtKPn5OPgOp/6ZRZZZEe7et/Si6sqots yLEA==
Received: by 10.180.98.69 with SMTP id eg5mr35258682wib.3.1343566328963; Sun, 29 Jul 2012 05:52:08 -0700 (PDT)
Received: from [192.168.7.200] (93-173-131-118.bb.netvision.net.il. [93.173.131.118]) by mx.google.com with ESMTPS id o2sm15283466wiz.11.2012.07.29.05.52.08 (version=SSLv3 cipher=OTHER); Sun, 29 Jul 2012 05:52:08 -0700 (PDT)
Message-ID: <501531F7.5040404@gmail.com>
Date: Sun, 29 Jul 2012 15:52:07 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Oauth blog post
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: Sun, 29 Jul 2012 12:52:10 -0000

Hi,

this blog post ( 
http://hueniverse.com/2012/07/oauth-2-0-and-the-road-to-hell/) by the 
editor of OAuth 2.0 made the rounds of the geek news outlets: Slashdot, 
CNet etc. I am sure many people on this list have seen it. But I have 
seen no reactions on this list, nor on the SAAG list. Is this too 
unimportant to discuss? Is there nothing we, as an organization, can 
learn from it?

Thanks,
     Yaron


From randy@psg.com  Sun Jul 29 08:12:54 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 D9DC721F85C4 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 08:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jOttqMEq9Tay for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 08:12:52 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id A292121F85B8 for <ietf@ietf.org>; Sun, 29 Jul 2012 08:12:52 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SvVAp-000J9P-6R; Sun, 29 Jul 2012 15:12:51 +0000
Date: Sun, 29 Jul 2012 08:12:49 -0700
Message-ID: <m2pq7e7g9a.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Oauth blog post
In-Reply-To: <501531F7.5040404@gmail.com>
References: <501531F7.5040404@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.6 - "Maruoka")
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: Sun, 29 Jul 2012 15:12:55 -0000

http://www.scifac.ru.ac.za/cspt/hoare.htm

From sm@resistor.net  Sun Jul 29 08:23:20 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 8C17B21F861F for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 08:23:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ongeDv8gZWKQ for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 08:23:18 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFF621F8592 for <ietf@ietf.org>; Sun, 29 Jul 2012 08:23:18 -0700 (PDT)
Received: from sm-THINK.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 q6TFNDqC006530; Sun, 29 Jul 2012 08:23:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1343575394; bh=RmiXQA+FTO5vfPuluRfAusIuGKdmVn4RgXW0vpWptUs=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=1YSUOxQe3/ymfHmYZjMIAvUkB8GXUaL1GT1BRiiupCE4ISQUNXSclmrFmya1A/Sfh YzLYAEFz6iuNWL38n9AGv8iZ0ytXJanwJLPPvUpnfkJq+qtp6+w+FbjajIiLxG6LcU ssMxSUDnniCfCo0H3BRg1KED1OgqNlCbAZ0YPNgs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1343575394; i=@resistor.net; bh=RmiXQA+FTO5vfPuluRfAusIuGKdmVn4RgXW0vpWptUs=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=VRtY1JsOcwMHgRafAC5KjkZHZyaecrhm9YM4PFPbkZV0KOg/GxZK75iX3XWfRgEVS uYSDVLsliEA1B+65+w9njwRsvHrnSTH/p0dwB1Mn5bpSSgqoxznUr+Fuksd9P0s5H/ S1xnE1T7fPAVn5n0rv5ylsgquNzpVI2Q2OoWmX0s=
Message-Id: <6.2.5.6.2.20120729073422.06d8fe10@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 29 Jul 2012 08:20:03 -0700
To: Yaron Sheffer <yaronf.ietf@gmail.com>, ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Oauth blog post
In-Reply-To: <501531F7.5040404@gmail.com>
References: <501531F7.5040404@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 15:23:20 -0000

Hi Yaron,
At 05:52 AM 7/29/2012, Yaron Sheffer wrote:
>this blog post (=20
>http://hueniverse.com/2012/07/oauth-2-0-and-the-road-to-hell/)=20
>by the editor of OAuth 2.0 made the rounds of=20
>the geek news outlets: Slashdot, CNet etc. I am=20
>sure many people on this list have seen it. But=20
>I have seen no reactions on this list, nor on=20
>the SAAG list. Is this too unimportant to=20
>discuss? Is there nothing we, as an organization, can learn from it?

OAuth2 is more within Apps than SAAG.  People=20
discuss about topics they are interested instead=20
of what you or I would consider as important.  I=20
don't know whether the IETF learns anything from=20
its failures.  It can always redefine failure so=20
that it becomes known as success. :-)

It is to Eran's credit that he did not seek all=20
the credit when he could have done so.  What I=20
could learn from that is that "doing the right=20
thing" will be forgotten when it is convenient to=20
do so.  The WG Chairs did something unusual to=20
try and resolve the situation.  That's in the=20
mailing list archive for anyone to read if the=20
person thinks that it is important.

I'll highlight the following:

   "[the] working group at the IETF started with=20
strong web presence. But as the
    work dragged on (and on) past its first year,=20
those web folks left along with
    every member of the original 1.0 community.=20
The group that was left was largely
    all enterprise=85 and me."

It's not the first time that this occurs.  It is=20
up to the IETF to assess whether it is detrimental to have such an outcome.

Regards,
-sm


From hannes.tschofenig@nsn.com  Sun Jul 29 11:15:05 2012
Return-Path: <hannes.tschofenig@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 A347C21F8458 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 11:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.658
X-Spam-Level: 
X-Spam-Status: No, score=-106.658 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jU2dQ0CbpCgB for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 11:15:04 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id CF79F21F844A for <ietf@ietf.org>; Sun, 29 Jul 2012 11:15:03 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q6TIF0eZ001133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 29 Jul 2012 20:15:00 +0200
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q6TIF0hO030878; Sun, 29 Jul 2012 20:15:00 +0200
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 29 Jul 2012 20:15:00 +0200
Received: from 10.159.32.94 ([10.159.32.94]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) with Microsoft Exchange Server HTTP-DAV ;  Sun, 29 Jul 2012 18:14:59 +0000
MIME-Version: 1.0
Message-ID: <0d5301cd6db6$1076c605$5e209f0a@nsnintra.net>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Subject: RE: Oauth blog post
thread-topic: Oauth blog post
thread-index: Ac1tthB24Z6oQOqmRg+jcL4cpUQqOw==
Date: Sun, 29 Jul 2012 11:14:58 -0700
To: "ext SM" <sm@resistor.net>, "Yaron Sheffer" <yaronf.ietf@gmail.com>, <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="_76EBEBE8-A7CE-9131-53E1-9F03BF7D36DD_"; charset="iso-8859-1"
X-OriginalArrivalTime: 29 Jul 2012 18:15:00.0298 (UTC) FILETIME=[1128E2A0:01CD6DB6]
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: 5857
X-purgate-ID: 151667::1343585701-000055D8-527DA60A/0-0/0-0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 18:15:05 -0000

--_76EBEBE8-A7CE-9131-53E1-9F03BF7D36DD_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

We are going to respond to Eran's blog post. We would like to respond with =
some real content instead of vague statements.

I would find it useful if anyone of you who likes to agree or disagree to h=
ave at least read the OAuth specification. I had noticed that many of those=
 who share their valuable thoughts have not even spent the time to look at =
the document.=20

Hannes

Sent from my Windows Phone

-----Original Message-----
From: ext SM
Sent: 7/29/2012 8:23 AM
To: Yaron Sheffer; ietf@ietf.org
Subject: Re: Oauth blog post

Hi Yaron,
At 05:52 AM 7/29/2012, Yaron Sheffer wrote:
>this blog post (=20
>http://hueniverse.com/2012/07/oauth-2-0-and-the-road-to-hell/)=20
>by the editor of OAuth 2.0 made the rounds of=20
>the geek news outlets: Slashdot, CNet etc. I am=20
>sure many people on this list have seen it. But=20
>I have seen no reactions on this list, nor on=20
>the SAAG list. Is this too unimportant to=20
>discuss? Is there nothing we, as an organization, can learn from it?

OAuth2 is more within Apps than SAAG.  People=20
discuss about topics they are interested instead=20
of what you or I would consider as important.  I=20
don't know whether the IETF learns anything from=20
its failures.  It can always redefine failure so=20
that it becomes known as success. :-)

It is to Eran's credit that he did not seek all=20
the credit when he could have done so.  What I=20
could learn from that is that "doing the right=20
thing" will be forgotten when it is convenient to=20
do so.  The WG Chairs did something unusual to=20
try and resolve the situation.  That's in the=20
mailing list archive for anyone to read if the=20
person thinks that it is important.

I'll highlight the following:

   "[the] working group at the IETF started with=20
strong web presence. But as the
    work dragged on (and on) past its first year,=20
those web folks left along with
    every member of the original 1.0 community.=20
The group that was left was largely
    all enterprise=85 and me."

It's not the first time that this occurs.  It is=20
up to the IETF to assess whether it is detrimental to have such an outcome.

Regards,
-sm


--_76EBEBE8-A7CE-9131-53E1-9F03BF7D36DD_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"

<html><head><meta content=3D"text/html; charset=3Diso-8859-1" http-equiv=3D=
"Content-Type"></head><body><div><div style=3D"font-family: Calibri,sans-se=
rif; font-size: 11pt;">We are going to respond to Eran's blog post. We woul=
d like to respond with some real content instead of vague statements.<br><b=
r>I would find it useful if anyone of you who likes to agree or disagree to=
 have at least read the OAuth specification. I had noticed that many of tho=
se who share their valuable thoughts have not even spent the time to look a=
t the document. <br><br>Hannes<br><br>Sent from my Windows Phone<br></div><=
/div><hr><span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt; fo=
nt-weight: bold;">From: </span><span style=3D"font-family: Tahoma,sans-seri=
f; font-size: 10pt;">ext SM</span><br><span style=3D"font-family: Tahoma,sa=
ns-serif; font-size: 10pt; font-weight: bold;">Sent: </span><span style=3D"=
font-family: Tahoma,sans-serif; font-size: 10pt;">7/29/2012 8:23 AM</span><=
br><span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt; font-wei=
ght: bold;">To: </span><span style=3D"font-family: Tahoma,sans-serif; font-=
size: 10pt;">Yaron Sheffer; ietf@ietf.org</span><br><span style=3D"font-fam=
ily: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">Subject: </spa=
n><span style=3D"font-family: Tahoma,sans-serif; font-size: 10pt;">Re: Oaut=
h blog post</span><br><br>Hi Yaron,<br>At 05:52 AM 7/29/2012, Yaron Sheffer=
 wrote:<br>&gt;this blog post ( <br>&gt;http://hueniverse.com/2012/07/oauth=
-2-0-and-the-road-to-hell/) <br>&gt;by the editor of OAuth 2.0 made the rou=
nds of <br>&gt;the geek news outlets: Slashdot, CNet etc. I am <br>&gt;sure=
 many people on this list have seen it. But <br>&gt;I have seen no reaction=
s on this list, nor on <br>&gt;the SAAG list. Is this too unimportant to <b=
r>&gt;discuss? Is there nothing we, as an organization, can learn from it?<=
br><br>OAuth2 is more within Apps than SAAG.&nbsp; People <br>discuss about=
 topics they are interested instead <br>of what you or I would consider as =
important.&nbsp; I <br>don't know whether the IETF learns anything from <br=
>its failures.&nbsp; It can always redefine failure so <br>that it becomes =
known as success. :-)<br><br>It is to Eran's credit that he did not seek al=
l <br>the credit when he could have done so.&nbsp; What I <br>could learn f=
rom that is that "doing the right <br>thing" will be forgotten when it is c=
onvenient to <br>do so.&nbsp; The WG Chairs did something unusual to <br>tr=
y and resolve the situation.&nbsp; That's in the <br>mailing list archive f=
or anyone to read if the <br>person thinks that it is important.<br><br>I'l=
l highlight the following:<br><br>&nbsp;&nbsp; "[the] working group at the =
IETF started with <br>strong web presence. But as the<br>&nbsp;&nbsp;&nbsp;=
 work dragged on (and on) past its first year, <br>those web folks left alo=
ng with<br>&nbsp;&nbsp;&nbsp; every member of the original 1.0 community. <=
br>The group that was left was largely<br>&nbsp;&nbsp;&nbsp; all enterprise=
=85 and me."<br><br>It's not the first time that this occurs.&nbsp; It is <=
br>up to the IETF to assess whether it is detrimental to have such an outco=
me.<br><br>Regards,<br>-sm<br><br></body></html>=

--_76EBEBE8-A7CE-9131-53E1-9F03BF7D36DD_--

From hannes.tschofenig@gmx.net  Sun Jul 29 12:19:40 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E619C21F8768 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 12:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q11WXEBJMX7A for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 12:19:40 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id C003B21F8764 for <ietf@ietf.org>; Sun, 29 Jul 2012 12:19:39 -0700 (PDT)
Received: (qmail invoked by alias); 29 Jul 2012 19:19:19 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp010) with SMTP; 29 Jul 2012 21:19:19 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/ymmRpQgnyTmcpLUKtiq1uXzMBjMXfQ7ZdgGfBI7 pCWbpTP+C8cpyG
Subject: Re: Oauth blog post
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <6.2.5.6.2.20120729073422.06d8fe10@resistor.net>
Date: Sun, 29 Jul 2012 12:19:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 19:19:41 -0000

Just a minor comment on this one:=20

On Jul 29, 2012, at 8:20 AM, SM wrote:

>  "[the] working group at the IETF started with strong web presence. =
But as the
>   work dragged on (and on) past its first year, those web folks left =
along with
>   every member of the original 1.0 community. The group that was left =
was largely
>   all enterprise=85 and me."

The IETF allows open participation and, as such, everyone, including =
companies that develop enterprise software, are free to participate in =
the discussions.=20

Do you think open participation is wrong?=

From glenzorn@gmail.com  Sun Jul 29 13:17:53 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 2BB3D21F855F for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:17:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WGuDdBRsGa1t for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:17:52 -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 46B6721F847A for <ietf@ietf.org>; Sun, 29 Jul 2012 13:17:52 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so8569451pbc.31 for <ietf@ietf.org>; Sun, 29 Jul 2012 13:17:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=XEadlIjlhHumU+w0AyTGQUXXZUXRWrTI+V3RtI1RwJk=; b=XWsErg4tekVLkgTybMyxYi2vZUHJOh3H0u4L2W6XiRGAPCniUhbvzXFdCNC7dxJLJU vYvWfNp1YAeBomhtyfH9NFcBX7wPZTdleea/vxLDrPRfNGCOWlpgl6eQmurwg/kH9+X5 xPFIIwmECrYMdqQfAGcXzpVga1u/lG/S/REMyg2TvrslYPjGe9x4d3vhR5SzA7Ki9xuJ mM++YW/U0s06lsJt9hDnwBnzl6pvLH8dEkEg1+NqH2NzdQ5KHm5f8+hDZiJ0WK73tK3t ZxSDT+/dCQWA4f8U5ofAPN+kbdS57fUryzWDxeZIpEsmIiq3EZYjKqVFttblAcVyp241 Jpcg==
Received: by 10.68.223.35 with SMTP id qr3mr30524218pbc.83.1343593072077; Sun, 29 Jul 2012 13:17:52 -0700 (PDT)
Received: from [10.0.1.195] (216-19-185-109.dyn.novuscom.net. [216.19.185.109]) by mx.google.com with ESMTPS id wh7sm2751828pbc.33.2012.07.29.13.17.50 (version=SSLv3 cipher=OTHER); Sun, 29 Jul 2012 13:17:51 -0700 (PDT)
Subject: Re: Oauth blog post
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net>
Content-Type: multipart/alternative; boundary="=-DqH7tn/1kuvBScQgoo+O"
Organization: Network Zen
Date: Mon, 30 Jul 2012 03:17:48 +0700
Message-ID: <1343593068.9245.0.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jul 2012 20:17:53 -0000

--=-DqH7tn/1kuvBScQgoo+O
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

On Sun, 2012-07-29 at 12:19 -0700, Hannes Tschofenig wrote:

> Just a minor comment on this one: 
> 
> On Jul 29, 2012, at 8:20 AM, SM wrote:
> 
> >  "[the] working group at the IETF started with strong web presence. But as the
> >   work dragged on (and on) past its first year, those web folks left along with
> >   every member of the original 1.0 community. The group that was left was largely
> >   all enterpriseâ€¦ and me."
> 
> The IETF allows open participation and, as such, everyone, including companies that develop enterprise software, are free to participate in the discussions. 
> 
> Do you think open participation is wrong?


Do you think that corporate domination of "open" standards development
is OK?


--=-DqH7tn/1kuvBScQgoo+O
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sun, 2012-07-29 at 12:19 -0700, Hannes Tschofenig wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Just a minor comment on this one: 

On Jul 29, 2012, at 8:20 AM, SM wrote:

&gt;  &quot;[the] working group at the IETF started with strong web presence. But as the
&gt;   work dragged on (and on) past its first year, those web folks left along with
&gt;   every member of the original 1.0 community. The group that was left was largely
&gt;   all enterprise&#8230; and me.&quot;

The IETF allows open participation and, as such, everyone, including companies that develop enterprise software, are free to participate in the discussions. 

Do you think open participation is wrong?
</PRE>
</BLOCKQUOTE>
<BR>
Do you think that corporate domination of &quot;open&quot; standards development is OK?<BR>
<BR>
</BODY>
</HTML>

--=-DqH7tn/1kuvBScQgoo+O--


From dworley@avaya.com  Sun Jul 29 13:20:26 2012
Return-Path: <dworley@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 0DB9821F856D for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.737
X-Spam-Level: 
X-Spam-Status: No, score=-102.737 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fMh6acPRe7s0 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:20:25 -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 4C5FB21F855F for <ietf@ietf.org>; Sun, 29 Jul 2012 13:20:25 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAEKaFVDGmAcF/2dsb2JhbABFuV6BB4IhAQEEEihPAgEIDSkQMiUBAQQbGodrnGicJJFSYAObRooQgns
X-IronPort-AV: E=Sophos;i="4.77,675,1336363200"; d="scan'208";a="20191547"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 29 Jul 2012 16:15:05 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 Jul 2012 16:16:06 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Sun, 29 Jul 2012 16:20:23 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Sun, 29 Jul 2012 16:18:40 -0400
Subject: RE: Oauth blog post
Thread-Topic: Oauth blog post
Thread-Index: Ac1tx0oBOtLj/WSaSjqY6zNySfmucwAAA290
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0BC7@DC-US1MBEX4.global.avaya.com>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net>, <1343593068.9245.0.camel@gwz-laptop>
In-Reply-To: <1343593068.9245.0.camel@gwz-laptop>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 20:20:26 -0000

Watching a play starting with the third act is always interesting but not i=
nformative.

If there's a dispute worthy of attention by the *whole IETF membership*, co=
uld someone please summarize it (in a reasonably unbiased way) to bring the=
 rest of us up to speed?

Dale

From hannes.tschofenig@gmx.net  Sun Jul 29 13:28:21 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D82921F8628 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:28: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AMF53oHxL50b for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:28:20 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 5F4FD11E8072 for <ietf@ietf.org>; Sun, 29 Jul 2012 13:28:20 -0700 (PDT)
Received: (qmail invoked by alias); 29 Jul 2012 20:28:15 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp036) with SMTP; 29 Jul 2012 22:28:15 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19i1pAnitViPl9xM9J38GpPJZhUKfUx14hKaHxpV7 mXnlZiy14uohra
Subject: Re: Oauth blog post
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <1343593068.9245.0.camel@gwz-laptop>
Date: Sun, 29 Jul 2012 13:28:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6EC0C8C6-3071-4DFD-8F4C-779A08D94D1E@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop>
To: Glen Zorn <glenzorn@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 20:28:21 -0000

>=20
> Do you think that corporate domination of "open" standards development =
is OK?
>=20

The barrier for participation is low since there are no membership fees, =
etc. Nevertheless, those who participate in standardization efforts have =
to spend their time. So, typically those who participate for a longer =
period of time need to have some incentives. These incentives often come =
from working for a specific company.

We cannot force anyone to participate in any of our working groups. In =
the OAuth case we have lots of other people participating but they =
typically ask questions and provide implementation feedback rather than =
trying to steer the standardization work.=20

Ciao
Hannes

PS: Eran was also working for a big corporation, namely Yahoo. I could =
imagine that Yahoo also had some incentives to pay Eran for his =
participation in this work.=20=

From hannes.tschofenig@gmx.net  Sun Jul 29 13:35:51 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0570321F852C for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:35:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZNGdsJhQSGY for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:35:50 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 15A3621F8526 for <ietf@ietf.org>; Sun, 29 Jul 2012 13:35:49 -0700 (PDT)
Received: (qmail invoked by alias); 29 Jul 2012 20:35:48 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp020) with SMTP; 29 Jul 2012 22:35:48 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/hwCdm08HhnHGK1ZAyB9Soj/rXlTEsz0blVhRdLx bMhWhkXJL758m0
Subject: Re: Oauth blog post
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0BC7@DC-US1MBEX4.global.avaya.com>
Date: Sun, 29 Jul 2012 13:35:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3C66C81-4FC8-4B26-94D4-C35407A3E265@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net>, <1343593068.9245.0.camel@gwz-laptop> <CD5674C3CD99574EBA7432465FC13C1B22726A0BC7@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 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: Sun, 29 Jul 2012 20:35:51 -0000

Eran, the editor of a specification in the OAuth working group, had =
decided to step down from his editor-role because the group did not =
agree with certain design decisions (particularly with a security design =
decision). That happens also in other groups. Nothing uncommon so far.=20=


He then wrote a blog post about his decision and made various claims =
about lack of interoperability, etc. =20
This blog post got picked up by the media and various people (who have =
in many cases not been involved in the IETF OAuth group) turned it into =
bashing the IETF overall.=20

On Jul 29, 2012, at 1:18 PM, Worley, Dale R (Dale) wrote:

> Watching a play starting with the third act is always interesting but =
not informative.
>=20
> If there's a dispute worthy of attention by the *whole IETF =
membership*, could someone please summarize it (in a reasonably unbiased =
way) to bring the rest of us up to speed?
>=20
> Dale


From ynir@checkpoint.com  Sun Jul 29 13:37:32 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 B311221F8552 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.273
X-Spam-Level: 
X-Spam-Status: No, score=-10.273 tagged_above=-999 required=5 tests=[AWL=0.326, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXYlMgybl5bU for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:37:31 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 5251D21F8526 for <ietf@ietf.org>; Sun, 29 Jul 2012 13:37:31 -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 q6TKbSiK026783; Sun, 29 Jul 2012 23:37:28 +0300
X-CheckPoint: {50159CA1-2-1B221DC2-4FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sun, 29 Jul 2012 23:37:27 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Glen Zorn <glenzorn@gmail.com>
Date: Sun, 29 Jul 2012 23:37:27 +0300
Subject: Re: Oauth blog post
Thread-Topic: Oauth blog post
Thread-Index: Ac1tyfepd0iemUnmRIq1orK92HU1YQ==
Message-ID: <1876CD0A-DD0A-4253-B559-0A4F041DA3DE@checkpoint.com>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop>
In-Reply-To: <1343593068.9245.0.camel@gwz-laptop>
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
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 20:37:32 -0000

On Jul 29, 2012, at 1:17 PM, Glen Zorn wrote:

> On Sun, 2012-07-29 at 12:19 -0700, Hannes Tschofenig wrote:
>>=20
>> Just a minor comment on this one:=20
>>=20
>> On Jul 29, 2012, at 8:20 AM, SM wrote:
>>=20
>> >  "[the] working group at the IETF started with strong web presence. Bu=
t as the
>> >   work dragged on (and on) past its first year, those web folks left a=
long with
>> >   every member of the original 1.0 community. The group that was left =
was largely
>> >   all enterprise=85 and me."
>>=20
>> The IETF allows open participation and, as such, everyone, including com=
panies that develop enterprise software, are free to participate in the dis=
cussions.=20
>>=20
>> Do you think open participation is wrong?
>=20
> Do you think that corporate domination of "open" standards development is=
 OK?

Hi

Like Dale, I haven't followed the play throughout the life of OAuth (the wo=
rking group)

Who are these corporations that dominate the working group?  Are they conte=
nt providers like Facebook, Twitter, or Disney?  Are they ISPs? Is it Gener=
al Motors?

If they are the people who are supposed to use these standards, their parti=
cipation is a good thing. I wish we had more users (corporate or others) in=
 the Security Area. So who are they?

Yoav=

From hannes.tschofenig@gmx.net  Sun Jul 29 13:50:55 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAD5F21F849D for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IEzFE0mgtNQI for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:50:55 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id A1ECD21F84E2 for <ietf@ietf.org>; Sun, 29 Jul 2012 13:50:50 -0700 (PDT)
Received: (qmail invoked by alias); 29 Jul 2012 20:50:48 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp027) with SMTP; 29 Jul 2012 22:50:48 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/tXuY4Jy7tVn+mxW4e3JXuDZTyCgKVpLPUrJwB58 SWDMHPfXobJkI5
Subject: Re: Oauth blog post
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <1876CD0A-DD0A-4253-B559-0A4F041DA3DE@checkpoint.com>
Date: Sun, 29 Jul 2012 13:50:45 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A096686-53B2-42C0-8A7B-CEDD691AB2AD@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop> <1876CD0A-DD0A-4253-B559-0A4F041DA3DE@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 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: Sun, 29 Jul 2012 20:50:55 -0000

Hi Yoav,=20

>=20
> Hi
>=20
> Like Dale, I haven't followed the play throughout the life of OAuth =
(the working group)
>=20
Barely anyone has done that.=20

> Who are these corporations that dominate the working group?  Are they =
content providers like Facebook, Twitter, or Disney?  Are they ISPs? Is =
it General Motors?

Eran claims that enterprise identity management equipment manufacturer =
dominate the discussion.=20

>=20
> If they are the people who are supposed to use these standards, their =
participation is a good thing.

Getting everyone who writes Web applications involved in the standards =
process is "a bit difficult".=20
If you look at the mailing list you see a mixture of small and big =
companies involved.=20

> I wish we had more users (corporate or others) in the Security Area. =
So who are they?
The OAuth group is more a consumer of security expertise rather than the =
source.=20

Ciao
Hannes

>=20
> Yoav


From glenzorn@gmail.com  Sun Jul 29 13:52:03 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 7637521F84F2 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pypSiv+P6RO6 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 13:52:03 -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 E762E21F849D for <ietf@ietf.org>; Sun, 29 Jul 2012 13:52:02 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so8599916pbc.31 for <ietf@ietf.org>; Sun, 29 Jul 2012 13:52:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=hKqcpFaqXKIPrpDK4+ptylt1o5JVJ20lZmsmTvUe92U=; b=pg4sXmHGN6w2NdrEDUHArH85tjARIM+xoMDFilrpA3z5/DTzgeKppeVOzR4qLnK61P 1IB+LtJFghdHhbrMyNolB5mCZA825wL1cE8wNAHZb6E7QdbfTcCmefwVSmvPqv63D7dd Zf7dVIib6uw7hCCdyenSRcRyJwZKZCVjbsnFPbc+hojdNfX0K3Q1U0zGApwcKJZyQrcf nh5m16WOaZgbGb6LcfmX+5KBOlOb4vbRVPnI2+uZ6+bkchMInmdbyPkekVyKOs1B21WO nA6zJUhy5debgugMGXHkelUYsZnc+B4RaCUq6xZBgf0DOye9ECo1ybGQLPTzCw5rrFaX tnRg==
Received: by 10.66.85.135 with SMTP id h7mr19858912paz.75.1343595122745; Sun, 29 Jul 2012 13:52:02 -0700 (PDT)
Received: from [10.0.1.195] (216-19-185-109.dyn.novuscom.net. [216.19.185.109]) by mx.google.com with ESMTPS id rg10sm6402508pbc.54.2012.07.29.13.52.01 (version=SSLv3 cipher=OTHER); Sun, 29 Jul 2012 13:52:02 -0700 (PDT)
Subject: Re: Oauth blog post
From: Glen Zorn <glenzorn@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
In-Reply-To: <1876CD0A-DD0A-4253-B559-0A4F041DA3DE@checkpoint.com>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop> <1876CD0A-DD0A-4253-B559-0A4F041DA3DE@checkpoint.com>
Content-Type: multipart/alternative; boundary="=-1wnUKJi9OY0vzDDNNXih"
Organization: Network Zen
Date: Sun, 29 Jul 2012 13:52:00 -0700
Message-ID: <1343595120.6354.2.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 20:52:03 -0000

--=-1wnUKJi9OY0vzDDNNXih
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Sun, 2012-07-29 at 23:37 +0300, Yoav Nir wrote:

...


> >> The IETF allows open participation and, as such, everyone, including companies that develop enterprise software, are free to participate in the discussions. 
> >> 
> >> Do you think open participation is wrong?
> > 
> > Do you think that corporate domination of "open" standards development is OK?
> 
> Hi
> 
> Like Dale, I haven't followed the play throughout the life of OAuth (the working group)
> 
> Who are these corporations that dominate the working group?  


The particulars are immaterial.  The question was as general (& I
suppose, philosophical) as Hannes'.


> Are they content providers like Facebook, Twitter, or Disney?  Are they ISPs? Is it General Motors?
> 
> If they are the people who are supposed to use these standards, their participation is a good thing. I wish we had more users (corporate or others) in the Security Area. So who are they?
> 
> Yoav



--=-1wnUKJi9OY0vzDDNNXih
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sun, 2012-07-29 at 23:37 +0300, Yoav Nir wrote:<BR>
<BR>
...<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
&gt;&gt; The IETF allows open participation and, as such, everyone, including companies that develop enterprise software, are free to participate in the discussions. 
&gt;&gt; 
&gt;&gt; Do you think open participation is wrong?
&gt; 
&gt; Do you think that corporate domination of &quot;open&quot; standards development is OK?

Hi

Like Dale, I haven't followed the play throughout the life of OAuth (the working group)

Who are these corporations that dominate the working group?&nbsp; 
</PRE>
</BLOCKQUOTE>
<BR>
The particulars are immaterial.&nbsp; The question was as general (&amp; I suppose, philosophical) as Hannes'.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
Are they content providers like Facebook, Twitter, or Disney?&nbsp; Are they ISPs? Is it General Motors?

If they are the people who are supposed to use these standards, their participation is a good thing. I wish we had more users (corporate or others) in the Security Area. So who are they?

Yoav
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-1wnUKJi9OY0vzDDNNXih--


From dworley@avaya.com  Sun Jul 29 14:14:47 2012
Return-Path: <dworley@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 7BA2911E80D9 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.733
X-Spam-Level: 
X-Spam-Status: No, score=-102.733 tagged_above=-999 required=5 tests=[AWL=-0.134, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q-S3Hx4+hOZU for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:14:47 -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 E53BE11E80BC for <ietf@ietf.org>; Sun, 29 Jul 2012 14:14:46 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAECnFVCHCzI1/2dsb2JhbAA8CblegQeCIAEBAQECARIoPwULAgEIDQghEDIlAQEEAQ0FCBqHXAMGBpxinCWKaHmFcWADm0aKEIJ7
X-IronPort-AV: E=Sophos;i="4.77,675,1336363200"; d="scan'208";a="20193865"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 29 Jul 2012 17:09:26 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 29 Jul 2012 16:55:05 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Sun, 29 Jul 2012 17:14:44 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Yoav Nir <ynir@checkpoint.com>
Date: Sun, 29 Jul 2012 17:13:07 -0400
Subject: RE: Oauth blog post
Thread-Topic: Oauth blog post
Thread-Index: Ac1ty96GmBWlAAc7RPuFiWG2QZFs5wAAxRs6
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0BCA@DC-US1MBEX4.global.avaya.com>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop> <1876CD0A-DD0A-4253-B559-0A4F041DA3DE@checkpoint.com>, <2A096686-53B2-42C0-8A7B-CEDD691AB2AD@gmx.net>
In-Reply-To: <2A096686-53B2-42C0-8A7B-CEDD691AB2AD@gmx.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 21:14:47 -0000

> From: Hannes Tschofenig [hannes.tschofenig@gmx.net]
>=20
> Eran claims that enterprise identity management equipment manufacturer do=
minate the discussion.

There's a common problem in the IETF that the development of a standard is =
dominated by companies that incorporate the standard into their products, w=
hereas the people who "really should" be involved in the development are th=
ose who will *use* the standard in operation.

Dale

From glenzorn@gmail.com  Sun Jul 29 14:35:45 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 9998621F8630 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q21n2as-Wty6 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:35:45 -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 1513521F8628 for <ietf@ietf.org>; Sun, 29 Jul 2012 14:35:44 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so8638659pbc.31 for <ietf@ietf.org>; Sun, 29 Jul 2012 14:35:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=zF9Gqm0xU2PknZf3U5+RcKHy9eOiR0ABhNoVzPMnDEk=; b=TT6zgdb6blKiA0q0GjNSh8IA181LdbZi1V0/QNPk5xJgKR6ZYZ2tKbFBtvdPzrg2VS dnJq+efuKoPIdeiggxZ35toVszFvNeD2IcTs5MN2p8Fnju9nIgRHv9wd3EseDn0Euwmv NEXI/3TMiI7sxLTrs9+/UysMo+KeUDqAL6nA6Yb8K2fwA3WczzWk9QyiJ/b978zrc1rd +kc5ARl5B4+s8sipTBqSyA+N7DSkT8V5x5y8DJEYLcibQcQbeXGTfLuEoF0tc5JqpYwY dhA5+R0q0J7JLrwgylJJdJZ++jYI3Xa0J2lzTGjdI5WO3bYP3FPQbh/FCiipQHQSIsor gp8g==
Received: by 10.66.77.169 with SMTP id t9mr20243984paw.70.1343597744787; Sun, 29 Jul 2012 14:35:44 -0700 (PDT)
Received: from [10.0.1.195] (216-19-185-109.dyn.novuscom.net. [216.19.185.109]) by mx.google.com with ESMTPS id wi6sm6462368pbc.35.2012.07.29.14.35.43 (version=SSLv3 cipher=OTHER); Sun, 29 Jul 2012 14:35:44 -0700 (PDT)
Subject: Re: Oauth blog post
From: Glen Zorn <glenzorn@gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <6EC0C8C6-3071-4DFD-8F4C-779A08D94D1E@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop> <6EC0C8C6-3071-4DFD-8F4C-779A08D94D1E@gmx.net>
Content-Type: multipart/alternative; boundary="=-4jFmvEm72hoO7XV1LCdj"
Organization: Network Zen
Date: Sun, 29 Jul 2012 14:02:20 -0700
Message-ID: <1343595740.6354.10.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
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, 29 Jul 2012 21:35:45 -0000

--=-4jFmvEm72hoO7XV1LCdj
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Sun, 2012-07-29 at 13:28 -0700, Hannes Tschofenig wrote:

> > 
> > Do you think that corporate domination of "open" standards development is OK?
> > 
> 
> The barrier for participation is low since there are no membership fees, etc. 


For participation, yes, all that is needed is an email account; if one
wishes to attend meetings (just the main ones - let's ignore interims),
the bar rises considerably.  The chances of dominating a WG or attaining
a leadership position in the IETF are very close to zero without meeting
attendance.  I spend about 10% of my gross income on travel, meeting
fees, etc. for IETF meetings; I don't consider that to be trivial.  

> Nevertheless, those who participate in standardization efforts have to spend their time. 


And somebody's money: I spend about 10% of my gross income on travel,
meeting fees, etc. for IETF meetings; I don't consider that to be
trivial. 


> So, typically those who participate for a longer period of time need to have some incentives. These incentives often come from working for a specific company.
> 
> We cannot force anyone to participate in any of our working groups. In the OAuth case we have lots of other people participating but they typically ask questions and provide implementation feedback rather than trying to steer the standardization work. 
> 
> Ciao
> Hannes
> 
> PS: Eran was also working for a big corporation, namely Yahoo. I could imagine that Yahoo also had some incentives to pay Eran for his participation in this work. 



--=-4jFmvEm72hoO7XV1LCdj
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Sun, 2012-07-29 at 13:28 -0700, Hannes Tschofenig wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
&gt; 
&gt; Do you think that corporate domination of &quot;open&quot; standards development is OK?
&gt; 

The barrier for participation is low since there are no membership fees, etc. 
</PRE>
</BLOCKQUOTE>
<BR>
For participation, yes, all that is needed is an email account; if one wishes to attend meetings (just the main ones - let's ignore interims), the bar rises considerably.&nbsp; The chances of dominating a WG or attaining a leadership position in the IETF are very close to zero without meeting attendance.&nbsp; I spend about 10% of my gross income on travel, meeting fees, etc. for IETF meetings; I don't consider that to be trivial.&nbsp; 
<BLOCKQUOTE TYPE=CITE>
<PRE>
Nevertheless, those who participate in standardization efforts have to spend their time. 
</PRE>
</BLOCKQUOTE>
<BR>
And somebody's money: I spend about 10% of my gross income on travel, meeting fees, etc. for IETF meetings; I don't consider that to be trivial. <BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
So, typically those who participate for a longer period of time need to have some incentives. These incentives often come from working for a specific company.

We cannot force anyone to participate in any of our working groups. In the OAuth case we have lots of other people participating but they typically ask questions and provide implementation feedback rather than trying to steer the standardization work. 

Ciao
Hannes

PS: Eran was also working for a big corporation, namely Yahoo. I could imagine that Yahoo also had some incentives to pay Eran for his participation in this work. 
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-4jFmvEm72hoO7XV1LCdj--


From yaronf.ietf@gmail.com  Sun Jul 29 14:39:48 2012
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE13721F8644 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0LzNuJs8zWrD for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:39:48 -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 44E3521F863B for <ietf@ietf.org>; Sun, 29 Jul 2012 14:39:48 -0700 (PDT)
Received: by wibhr14 with SMTP id hr14so954800wib.13 for <ietf@ietf.org>; Sun, 29 Jul 2012 14:39:47 -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 :content-type:content-transfer-encoding; bh=/Oe88iqAUUziaQY9w34YLrT2AGGmFUrcpPgwK6iLoTg=; b=ygrdXoeP2ccy6hvO6K/jAXdoxGF41mlsiTGcG/XGLEM/0c3/Iafs80qhLkaOTZAmdc n+OlX8U0kN+rYxM1+amRUAjCIt0znXLLyC98QCms1pwp9v1U2KljzvLZ5UjO5MUFe5x5 y1Xz6LxAol1tBzM9V4gSDK9EWe/Wwfp86AqO+GY9Y+eV4f0PqPt5X+TnaZpSgu0SAnP+ zzJnlEBpvg5suVo4Q5uUhtg/zU6budu0IKchWpHbLQ7dDB9xXhXqAWG1/qUYHFT30F8v 6byNLen1WoPWdmmm4QTADcEqkRtYyvKIeuMUyNihGMRcT39DOrGhpmPFgU7A7pFRMRcH EpPg==
Received: by 10.216.99.199 with SMTP id x49mr896928wef.171.1343597987378; Sun, 29 Jul 2012 14:39:47 -0700 (PDT)
Received: from [10.0.0.4] ([109.67.179.185]) by mx.google.com with ESMTPS id bc2sm18861486wib.0.2012.07.29.14.39.46 (version=SSLv3 cipher=OTHER); Sun, 29 Jul 2012 14:39:46 -0700 (PDT)
Message-ID: <5015ADA1.9010304@gmail.com>
Date: Mon, 30 Jul 2012 00:39:45 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Oauth blog post
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 21:39:49 -0000

Trying to step away from the "big vendors vs. users" discussion...

I admit I have not followed events in the oauth WG, but I did read 
Eran's post and his own follow-on comments, plus some others' who were 
burnt by our processes. Some may want to construe it as "IETF bashing", 
but what I'm reading is three concrete statements that IETF members can 
respond to, and (if we accept them as true) consider how to address in 
the future:

- A Web-focused protocol was forced to adopt enterprise use cases.
- The Security Area did not do a good job of providing the protocol with 
useful review/feedback/support. (The original wording is much harsher).
- The third statement is a cliché as far as SDOs, but we still need to 
face it: simple protocols coming into the IETF are made complex, 
sometime too complex, in the process.

Thanks,
     Yaron

PS: some background: OAuth is an important Web security protocol, very 
widely used (Wikipedia link here). The blog post was written by the 
person who has led (or co-led) the protocol for years, and actually 
brought it into the IETF.

From hannes.tschofenig@gmx.net  Sun Jul 29 14:52:40 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D708D21F84CE for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNwz1Xvl-sbZ for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:52:40 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id BBEA521F8463 for <ietf@ietf.org>; Sun, 29 Jul 2012 14:52:37 -0700 (PDT)
Received: (qmail invoked by alias); 29 Jul 2012 21:52:36 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp041) with SMTP; 29 Jul 2012 23:52:36 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18mMGN+03smdEP+MOnMgBEprfPgLby0Cg0dWX5Alr JFaZSM9dVEU2F1
Subject: Re: Oauth blog post
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <1343595740.6354.10.camel@gwz-laptop>
Date: Sun, 29 Jul 2012 14:52:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <510C5471-40D5-4B46-8AFA-680016021CDA@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop> <6EC0C8C6-3071-4DFD-8F4C-779A08D94D1E@gmx.net> <1343595740.6354.10.camel@gwz-laptop>
To: Glen Zorn <glenzorn@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2012 21:52:41 -0000

I certainly agree that the participation in the face-to-face meetings is =
indeed more costly. For leadership positions (as you call them) such =
participation is indeed important.=20

On Jul 29, 2012, at 2:02 PM, Glen Zorn wrote:

> On Sun, 2012-07-29 at 13:28 -0700, Hannes Tschofenig wrote:
>>=20
>> >=20
>> > Do you think that corporate domination of "open" standards =
development is OK?
>> >=20
>>=20
>> The barrier for participation is low since there are no membership =
fees, etc.=20
>=20
> For participation, yes, all that is needed is an email account; if one =
wishes to attend meetings (just the main ones - let's ignore interims), =
the bar rises considerably.  The chances of dominating a WG or attaining =
a leadership position in the IETF are very close to zero without meeting =
attendance.  I spend about 10% of my gross income on travel, meeting =
fees, etc. for IETF meetings; I don't consider that to be trivial.=20
>>=20
>> Nevertheless, those who participate in standardization efforts have =
to spend their time.=20
>=20
> And somebody's money: I spend about 10% of my gross income on travel, =
meeting fees, etc. for IETF meetings; I don't consider that to be =
trivial.=20
>=20
>> So, typically those who participate for a longer period of time need =
to have some incentives. These incentives often come from working for a =
specific company.
>>=20
>> We cannot force anyone to participate in any of our working groups. =
In the OAuth case we have lots of other people participating but they =
typically ask questions and provide implementation feedback rather than =
trying to steer the standardization work.=20
>>=20
>> Ciao
>> Hannes
>>=20
>> PS: Eran was also working for a big corporation, namely Yahoo. I =
could imagine that Yahoo also had some incentives to pay Eran for his =
participation in this work.=20
>=20


From hannes.tschofenig@gmx.net  Sun Jul 29 14:57:38 2012
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59D6B21F867F for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zh6SQaLekz7y for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 14:57:38 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 6676621F867C for <ietf@ietf.org>; Sun, 29 Jul 2012 14:57:20 -0700 (PDT)
Received: (qmail invoked by alias); 29 Jul 2012 21:57:19 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp035) with SMTP; 29 Jul 2012 23:57:19 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18mM/ph6hcmf7ZtEF/P05zpZ4ij6lgkVhT3f5RcOo RNwtMf0LwLdhKF
Subject: Re: Oauth blog post
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0BCA@DC-US1MBEX4.global.avaya.com>
Date: Sun, 29 Jul 2012 14:57:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <78374799-AF96-400D-8FB5-205D096CD113@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop> <1876CD0A-DD0A-4253-B559-0A4F041DA3DE@checkpoint.com>, <2A096686-53B2-42C0-8A7B-CEDD691AB2AD@gmx.net> <CD5674C3CD99574EBA7432465FC13C1B22726A0BCA@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 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: Sun, 29 Jul 2012 21:57:38 -0000

It sounds indeed great to involve those communities that use the =
technology. However, I don't see an easy way to accomplish that when we =
talk about a really large community.=20

For example, many people use TLS and they are not all in the TLS WG =
working group. I am not even talking about providing useful input to the =
work (since you would have to be a security expert and some people just =
want to get their application development done as quickly as possible). =
They just use the library.=20

OAuth is a bit similar in that direction. Ideally, we want Web =
application developers to just use a library and then add their =
application specific technology on top of it rather than having to read =
the IETF specification and to write the OAuth code themselves.=20

On Jul 29, 2012, at 2:13 PM, Worley, Dale R (Dale) wrote:

>> From: Hannes Tschofenig [hannes.tschofenig@gmx.net]
>>=20
>> Eran claims that enterprise identity management equipment =
manufacturer dominate the discussion.
>=20
> There's a common problem in the IETF that the development of a =
standard is dominated by companies that incorporate the standard into =
their products, whereas the people who "really should" be involved in =
the development are those who will *use* the standard in operation.
>=20
> Dale


From tbray@textuality.com  Sun Jul 29 20:00:50 2012
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06EFF21F8575 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 20:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.094
X-Spam-Level: 
X-Spam-Status: No, score=-5.094 tagged_above=-999 required=5 tests=[AWL=-2.117, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3vZNY1eAvON6 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 20:00:49 -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 267FB21F8568 for <ietf@ietf.org>; Sun, 29 Jul 2012 20:00:49 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so4464687vbb.31 for <ietf@ietf.org>; Sun, 29 Jul 2012 20:00:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=uPZtwDODroM8COigEdZ5kYE9zOWk9bTusE8U7jVlWdA=; b=W3WM38eAkAguKOP3CknwZQYoOJDxaFf6JU+x7c7spjNUHu+VRxzfMBew0DfxqfOPxn IkZBr4Xer0hWhedLyiDR4Dil76DrmXGEsFhuRU0JC9hwqD066OYQ8bH87sAJ1iRSMern /8ppIt0rDZDMgMv9QOx6qGmDCIaZyO/jvChcv/06hsdeqxpMClu1fJAk+kW/NMgQYiYZ JPSjXLnsLJL6rzzhrF7LZAaisgKl9fU/svfMZZYVqMLdxA2E4enkf5ImyHPQLJSjCg/d FC/y1qi1IOYDaK/6k2QLa3y6v9q5t84GlaDxGPHpNqkGpACYh5MXFf9kwkSetvXUG+2O MI5w==
MIME-Version: 1.0
Received: by 10.220.142.79 with SMTP id p15mr9543196vcu.24.1343617248379; Sun, 29 Jul 2012 20:00:48 -0700 (PDT)
Received: by 10.52.113.162 with HTTP; Sun, 29 Jul 2012 20:00:48 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <78374799-AF96-400D-8FB5-205D096CD113@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net> <1343593068.9245.0.camel@gwz-laptop> <1876CD0A-DD0A-4253-B559-0A4F041DA3DE@checkpoint.com> <2A096686-53B2-42C0-8A7B-CEDD691AB2AD@gmx.net> <CD5674C3CD99574EBA7432465FC13C1B22726A0BCA@DC-US1MBEX4.global.avaya.com> <78374799-AF96-400D-8FB5-205D096CD113@gmx.net>
Date: Sun, 29 Jul 2012 20:00:48 -0700
Message-ID: <CAHBU6isADXftAv91CCt-hxUabd6a++gPjuq7b4U4g_7HPsZ=Hg@mail.gmail.com>
Subject: Re: Oauth blog post
From: Tim Bray <tbray@textuality.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnhRcQnfSV/fYVdoLQ2fApLaEBKW5ZWLI9TE5fBf9IR9ETk7zQ6zXY1qg2UtOkBtZEBOiTa
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 03:00:50 -0000

I have not been involved in the OAuth design processes, but for the
last few months, I=92ve been a heavy user of production OAuth2 software.
Which I felt gave me a platform to comment  on the issue:
http://www.tbray.org/ongoing/When/201x/2012/07/28/Oauth2-dead

 -Tim

On Sun, Jul 29, 2012 at 2:57 PM, Hannes Tschofenig
<hannes.tschofenig@gmx.net> wrote:
> It sounds indeed great to involve those communities that use the technolo=
gy. However, I don't see an easy way to accomplish that when we talk about =
a really large community.
>
> For example, many people use TLS and they are not all in the TLS WG worki=
ng group. I am not even talking about providing useful input to the work (s=
ince you would have to be a security expert and some people just want to ge=
t their application development done as quickly as possible). They just use=
 the library.
>
> OAuth is a bit similar in that direction. Ideally, we want Web applicatio=
n developers to just use a library and then add their application specific =
technology on top of it rather than having to read the IETF specification a=
nd to write the OAuth code themselves.
>
> On Jul 29, 2012, at 2:13 PM, Worley, Dale R (Dale) wrote:
>
>>> From: Hannes Tschofenig [hannes.tschofenig@gmx.net]
>>>
>>> Eran claims that enterprise identity management equipment manufacturer =
dominate the discussion.
>>
>> There's a common problem in the IETF that the development of a standard =
is dominated by companies that incorporate the standard into their products=
, whereas the people who "really should" be involved in the development are=
 those who will *use* the standard in operation.
>>
>> Dale
>

From dworley@avaya.com  Sun Jul 29 21:11:08 2012
Return-Path: <dworley@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 008F421F85DF for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 21:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.229
X-Spam-Level: 
X-Spam-Status: No, score=-103.229 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3EjE6-cMMH+f for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 21:11:01 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 0D81121F85DB for <ietf@ietf.org>; Sun, 29 Jul 2012 21:11:00 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHcIFlDGmAcF/2dsb2JhbAAvFrlOgQeCIAEBAQECARJsCwIBCA0IFhshESUBAQQTCBqHXAMGBp0JklcNiU6KaGuFf2ADk3QBh1GFDYUDgns
X-IronPort-AV: E=Sophos;i="4.77,677,1336363200"; d="scan'208";a="317593010"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 30 Jul 2012 00:06:35 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 30 Jul 2012 00:06:39 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Mon, 30 Jul 2012 00:10:57 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 30 Jul 2012 00:10:57 -0400
Subject: RE: Oauth blog post
Thread-Topic: Oauth blog post
Thread-Index: Ac1t0rL2n4pTcA5bTcG1sD8GYJMJuwANbWwP
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0BCE@DC-US1MBEX4.global.avaya.com>
References: <5015ADA1.9010304@gmail.com>
In-Reply-To: <5015ADA1.9010304@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="Windows-1252"
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, 30 Jul 2012 04:11:08 -0000

> From: Yaron Sheffer [yaronf.ietf@gmail.com]
>=20
> [...] but what I'm reading is three concrete statements that IETF
> members can respond to, and (if we accept them as true) consider how
> to address in the future:
>=20
> - A Web-focused protocol was forced to adopt enterprise use cases.
> [...]

My first impulse is to say, yes, protocols that solve "enterprise"
problems are a lot more difficult than ones that solve individual-user
problems.  One that showed up in my field (SIP) was the concept of
"securely" identifying the party you have called.  If I normally call
John Smith at my bank to do business, and if John Smith is replaced at
his job by another person, and I call "John Smith at the bank", should
I authenticate that I am talking to John Smith, or should I
authenticate that I am talking to the person who holds the job at the
bank that John Smith used to have?

> Tim bray writes in an essay:
>=20
> Enterpriseyness =B7 One of Eran=92s central gripes is the immense
> difficulty of knitting "Enterprise" requirements into OAuth =97 or any
> other standards work, for that matter. He=92s right. The Web use cases
> may not be easy to solve, but they=92re easy to understand. [...]
>=20
> On the other hand, whenever I get into a conversation with someone on
> the Enterprise side, even when I think I understand the problem
> domain, I lose the plot, and fast. The requirements these people claim
> to have around both authentication and authorization are so arcane and
> subtle and legacy-laden that you have to be a full-time professional
> to even understand them.

Which reminds me that large organizations have the problem that every
new activity is necessarily a small change on a monstrous base of
current systems, and has to work harmoniously with them.  As someone
once observed:

> The reason God could create the Universe in six days is that He didn't
> have to make it upward compatible.

Dale

From Jeff.Hodges@KingsMountain.com  Sun Jul 29 22:30:15 2012
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AEE221F85D5 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 22:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.495
X-Spam-Level: 
X-Spam-Status: No, score=-100.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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SwXuqvJyQiBM for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 22:30:14 -0700 (PDT)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [IPv6:2605:dc00:100:2::a2]) by ietfa.amsl.com (Postfix) with SMTP id D7C6421F85D0 for <ietf@ietf.org>; Sun, 29 Jul 2012 22:30:13 -0700 (PDT)
Received: (qmail 1076 invoked by uid 0); 30 Jul 2012 05:30:13 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy9.bluehost.com with SMTP; 30 Jul 2012 05:30:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=xmKcfdIvb5LkKTijMpc7nGaIFTk7mCbkrfXaMyxYse4=;  b=nTdfKFh6mPLnoARRSpWzkjRa/18p9woCnGMt0xfpW/YhNEF0zfRCF4KS0pel+fMikZvz0A5sEeLj4sXTRSTtgff3VOXdpnFMSg51Ok4xH/3Rs7iH1uTdTbYXcJ6l0rPC;
Received: from [130.129.65.226] (port=37158) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1SviYO-0007ck-Gm; Sun, 29 Jul 2012 23:30:05 -0600
Message-ID: <50161BD5.7040901@KingsMountain.com>
Date: Sun, 29 Jul 2012 22:29:57 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-websec-strict-transport-sec-11
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 130.129.65.226 authed with jeff.hodges+kingsmountain.com}
Cc: General Area Review Team <gen-art@ietf.org>, IETF WebSec WG <websec@ietf.org>, draft-ietf-websec-strict-transport-sec.all@tools.ietf.org, IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 05:30:15 -0000

thanks for the review Ben.

 > 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-websec-strict-transport-sec-11 Reviewer: Ben Campbell
 > Review Date: 2012-07-24 IETF LC End Date: 2012-07-25
 >
 > Summary: This draft is almost ready for publication as a proposed standard,
 > but there are a few issues that should be considered first.
 >
 > *** Major issues:
 >
 > None
 >
 > *** Minor issues:
 >
 > -- Does this draft update any other RFCs (e.g. 2616 or 2818)? If so, that
 > should be explicitly flagged and mentioned in the abstract.

Good question, I don't believe we've discussed this possibility directly in the 
websec wg. In looking at the RFCs that do update RFC2616, it doesn't look like 
draft-ietf-websec-strict-transport-sec (HSTS) is of that ilk.

However, it nominally appears that an argument could be made that it'd be 
appropriate to update RFC2818 via draft-ietf-websec-strict-transport-sec, 
specifically with regards to Section 2.1.  Connection Initiation.

Though, RFC2818 is Informational, which may be an issue (?). Also, perhaps this 
is something to more appropriately do via a standards-track rfc2818bis, i.e., 
have the latter reference the HSTS spec.

this is something to discuss this coming week @IETF-84 Vancouver it seems.


 > -- I did not find any guidance on how to handle UAs that do not understand
 > this extension. I don't know if this needs to be normative, but the draft
 > should at least mention the possibility and implications.

Agreed. My -12 working copy now contains these new subsections..

###
10.  Server Implementation and Deployment Advice

    This section is non-normative.

10.1.  Non-Conformant User Agent Considerations

    Non-conformant UAs ignore the Strict-Transport-Security header field,
    thus non-conformant user agents do not address the threats described
    in Section 2.3.1 "Threats Addressed".  Please refer to Section 14.1
    "Non-Conformant User Agent Implications" for further discussion.

                        .
                        .

14.  Security Considerations
                        .
                        .
14.1.  Non-Conformant User Agent Implications

    Non-conformant UAs ignore the Strict-Transport-Security header field,
    thus non-conformant user agents do not address the threats described
    in Section 2.3.1 "Threats Addressed".

    This means that the web application and its users wielding non-
    conformant user agents will be vulnerable to both:

       Passive network attacks due to web site development and deployment
       bugs: For example, if the web application contains any insecure,
       non-"https", references to the web application server, and if not
       all of its cookies are flagged as "Secure", then its cookies will
       be vulnerable to passive network sniffing, and potentially
       subsequent misuse of user credentials.

       Active network attacks: If an attacker is able to place a man-in-
       the-middle, secure transport connection attempts will likely yield
       warnings to the user, but without HSTS Policy being enforced, the
       present common practice is to allow the user to "click-through"
       and proceed.  This renders the user and possibly the web
       application open to abuse by such an attacker.

    This is essentially the status-quo for all web applications and their
    users in the absence of HSTS Policy.
###

 >
 > -- How should a UA handle potential conflicts between a the policy record
 > that includes the includeSubdomain, and any records for subdomains that might
 > have different parameters?

this is in the draft. the short answer is that at policy enforcement time, 
"superdomain matches win".

At "noting an HSTS Host" time, the HSTS host's policy (if expressed) is noted 
regardless of whether there are superdomain HSTS hosts asserting 
"includeSubDomains".

perhaps this needs to be made more clear?


 >
 > -- section 6.1:
 >
 > The draft mentions that directives may be extended, but defers creation of an
 > IANA registry to the time of first extension. IANA registries are not
 > expensive; I suggest it be created now. If there's a good reason not to, then
 > the draft should still address the specification policy for extensions.
 >
 > Also, do you expect that some future directive might need to have a
 > "required-to-understand" status? Given that this is a security-affecting
 > extension, it seems likely. If so, then the mechanism for expressing that
 > needs to be defined in this draft.


These are good questions, and they beg the overall question of how complex this 
simple solution really needs to be and whether we really think we'll need any 
extensions. Something for us to discuss in the working group meeting on Tue 
morning I think.

 >
 > -- section 7.2:
 >
 > Am I correct to assume that the server must never just serve the content over
 > a non-secure connection? If so, it would be helpful to mention that, maybe
 > even normatively.

It's a SHOULD, see the Note in that section, so it's already effectively stated 
normatively, though one needs to understand HTTP workings to realize it in the 
way you stated it above.  Perhaps could add a simple statement as you suggest to 
the intro para for section 7 Server Processing Model, to address this concern?


 >
 > -- section 8.4:
 >
 > Does this imply a duty for compliant UAs to check for revocation one way or
 > another?

yes. though, per other relevant specifications, as duly cited. AFAIK the HSTS 
spec doesn't need to get into the details because the underlying security 
transport specs, namely TLS, already do this.



 >
 >
 > *** Nits/editorial comments:
 >
 > -- idnits reports an uncited reference:
 >
 > == Unused Reference: 'RFC6376' is defined on line 1709, but no explicit
 > reference was found in the text


fixed in my -12 working copy.


 > -- section 1.2:
 >
 > The description of indented notes is almost precisely the opposite of how
 > they are described in the RFC editor's style guide. It describes them as
 > "parenthetical" notes, which is how experienced RFC readers are likely to
 > perceive them. While it doesn't say so explicitly, I think putting normative
 > text in parenthetical notes should be avoided. If these are intended to be
 > taken more strongly than that (and by the description, I take it they should
 > be taken more strongly than the surrounding text), then I suggest choosing a
 > stronger prefix than "NOTE:"

As it turns out, almost all the Notes are parenthetical.

I'll render the one(s) that are normative as a regular paragraph(s) and leave 
the others as-is. Will that address your concern?


 >
 > -- section 7:
 >
 > Does the reference to I-D.ietf-tls-ssl-version3 indicate a requirement for
 > SSL3?

no, it's just that SSLv3 remains a fact of life and is referenced for 
completeness' sake.



 >
 > -- section 8.2, paragraph 5 (first non-numbered paragraph after numbered
 > list)
 >
 > To be pedantic, this could be taken to mean a congruent match only applies if
 > the includeSubdomains flag is not present. I assume it's intended to apply
 > whether or not the flag is present.

[ I am assuming you actually are referring to section 8.3, as section 8.2 
doesn't mention the includeSubdomains flag and does not contain a numbered list. ]

yes, a congruent match is intended to apply whether or not the flag is present.



 > -- section 12 and subsections:
 >
 > I was surprised to see more apparently normative material after the
 > non-normative guidance sections. I think it would improve the organization to
 > put this closer to the normative rules for UAs.

We can move section 12 up ahead of the non-normative guidance sections.


 >
 > -- section 14.1, 4th paragraph (first non-bulleted paragraph following bullet
 > list)
 >
 > This issue is only true for proxies that act as a TLS MiTM, right?

yes.


 > Would
 > proxies that tunnel TLS via the CONNECT method have this issue?

I don't think so in the general case.

I'm not sure what terminology to use to differentiate such proxies if this is a 
detail worth addressing.


thanks again,

=JeffH







From brian.e.carpenter@gmail.com  Mon Jul 30 02:04:37 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0800121F8753 for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 02:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.417
X-Spam-Level: 
X-Spam-Status: No, score=-101.417 tagged_above=-999 required=5 tests=[AWL=0.274, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6sC5UYTJczg for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 02:04:36 -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 48A2521F8752 for <ietf@ietf.org>; Mon, 30 Jul 2012 02:04:36 -0700 (PDT)
Received: by eaaa11 with SMTP id a11so998564eaa.31 for <ietf@ietf.org>; Mon, 30 Jul 2012 02:04:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=C84Iy72LXnl/9lHDjwWlreCcFURN4sAPIqzOZLQHaYg=; b=Af3CRaDH6J4eXqeFQwMM/jeV5Q3K0YjIQpMXU7vasjGA1dzsVoDtAWfCmVpua8P2WG 3G1z7ZoVCNBT3klRz/J1OGBFliHGzECn+v//Tn170dUhNi3yOgUtuzA866VIDVfncsUh keJaz7d1+YeHQklm+UBAdEFMtTn/iBb8ljGysPhOau3lY0YDNQtfDmf5ojeCaNtm6A7x cOP+5OqHN++dgnhgKRLpvMFaVXzlCTDABzQdoCOdEdwO7Ue/X22dSjzer7YxJiMK2WOt leazidiWFBDRB51bimTtZgFOuJLiie5oCowl4TUJRTg+QITn9micC6CbFifJ5GX9Rp1M 22DA==
Received: by 10.14.180.67 with SMTP id i43mr11220924eem.23.1343639075522; Mon, 30 Jul 2012 02:04:35 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-212.as13285.net. [2.102.216.212]) by mx.google.com with ESMTPS id g46sm26334069eep.15.2012.07.30.02.04.33 (version=SSLv3 cipher=OTHER); Mon, 30 Jul 2012 02:04:34 -0700 (PDT)
Message-ID: <50164E21.2040904@gmail.com>
Date: Mon, 30 Jul 2012 10:04:33 +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: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com>
In-Reply-To: <20120730082620.18701.51607.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 09:04:37 -0000

Under the long-standing IETF policy defined in RFC 2804, I trust
we will not be discussing this draft, or
draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.

Regards
   Brian Carpenter

On 30/07/2012 09:26, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
> 	Title           : Label-based Provider-Provisioned Lawful Intercept for L3 VPNs
> 	Author(s)       : Shankar Raman
>                           Balaji Venkat Venkataswami
>                           Gaurav Raina
>                           Vasan Srini
>                           Bhargav Bhikkaji
> 	Filename        : draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
> 	Pages           : 12
> 	Date            : 2012-07-30
> 
> Abstract:
>    In models of Single-AS and inter-provider Multi- Protocol Label
>    Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
>    Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
>    models like VPLS and the like do not have any provider provisioned
>    methods of lawful intercept that are comprehensive, quick and easy to
>    provision from one single point. More particularly the auto-
>    provisioning of lawful intercept for all sets of streams travelling
>    between VPN sites and consequent re-direction of these streams to the
>    appropriate government network has not been covered without multiple
>    instances of having to configure the intercept at various points in
>    the network both in the Single-AS case and the Inter-Provider VPN
>    case.
> 
>    this paper, we propose a technique which uses a set of pre-defined
>    labels called Lawful Intercept labels and a method for provisioning
>    lawful intercept amongst the various PE devices using these labels
>    both in the Single-AS and the inter-provider VPN cases. A single
>    point of configuration is the key to this idea. The intercepted
>    traffic is mirrored on a PE or a whole set of PEs or on all the PEs
>    participating in the VPN. A technique called the Domino-effect
>    provisioning of these Label-based Provider Provisioned Lawful
>    Intercept mechanism is also outlined.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-label-dis
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-dis-00
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

From randy@psg.com  Mon Jul 30 08:57:08 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 892BE21F85DD for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 08:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CNiSmOcGz7MY for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 08:57:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 35DB721F8609 for <ietf@ietf.org>; Mon, 30 Jul 2012 08:57:08 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SvsLD-000MHK-Q3; Mon, 30 Jul 2012 15:57:07 +0000
Date: Mon, 30 Jul 2012 08:57:07 -0700
Message-ID: <m2r4rtw8bw.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
In-Reply-To: <50164E21.2040904@gmail.com>
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com> <50164E21.2040904@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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 15:57:08 -0000

> Under the long-standing IETF policy defined in RFC 2804, I trust
> we will not be discussing this draft, or
> draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.

<aol>

From chair@ietf.org  Mon Jul 30 09:40:11 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 4A19821F8474; Mon, 30 Jul 2012 09:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZGTZ1CA3AmL; Mon, 30 Jul 2012 09:40:10 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id A644E21F846F; Mon, 30 Jul 2012 09:40:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A0A9912D745; Mon, 30 Jul 2012 09:40:10 -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 yZy2n6adSSA0; Mon, 30 Jul 2012 09:40:10 -0700 (PDT)
Received: from [IPv6:2001:df8::80:6233:4bff:fe20:eb18] (unknown [IPv6:2001:df8:0:80:6233:4bff:fe20:eb18]) by c8a.amsl.com (Postfix) with ESMTPSA id 6C99E12D740; Mon, 30 Jul 2012 09:40:10 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Draft IESG Statement Regarding Ethertype Requests
Mime-Version: 1.0 (Apple Message framework v1084)
From: IETF Chair <chair@ietf.org>
Date: Mon, 30 Jul 2012 12:40:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDF73C59-A8E8-43B4-B67D-34CFAF541DB6@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 16:40:11 -0000

Last week the IAB and the IESG met with the leadership of IEEE 802.  One =
of the things that was discussed was the IEEE policies for allocating =
EtherTypes, and the IESG is considering the attached IESG Statement to =
implement an IETF policy that aligns with the IEEE policy.

If you have an comments on this proposed policy, please raise them on =
ietf@ietf.org.

Russ

=3D =3D =3D =3D =3D =3D=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 an Ethertype to a
new IETF protocol specification that needs a new Ethertype until the
IESG has approved the 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 craemer@isoc.org  Sun Jul 29 16:33:20 2012
Return-Path: <craemer@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 3896221F8625 for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 16:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.162
X-Spam-Level: 
X-Spam-Status: No, score=-103.162 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rNajnOGp+Kqg for <ietf@ietfa.amsl.com>; Sun, 29 Jul 2012 16:33:19 -0700 (PDT)
Received: from smtp177.dfw.emailsrvr.com (smtp177.dfw.emailsrvr.com [67.192.241.177]) by ietfa.amsl.com (Postfix) with ESMTP id 6801221F8628 for <ietf@ietf.org>; Sun, 29 Jul 2012 16:33:19 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp17.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 9E2DE1881A0; Sun, 29 Jul 2012 19:33:18 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp17.relay.dfw1a.emailsrvr.com (Authenticated sender: craemer-AT-isoc.org) with ESMTPSA id 4585118819D;  Sun, 29 Jul 2012 19:33:18 -0400 (EDT)
From: Kevin Craemer <craemer@isoc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: ISOC@IETF 84 Briefing Panel -  World IPv6: Launched! 
Date: Sun, 29 Jul 2012 16:33:12 -0700
Message-Id: <F5021305-106D-4431-B10E-E76E90B193AA@isoc.org>
To: ietf@ietf.org, 84attendees@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Mon, 30 Jul 2012 09:42:02 -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: Sun, 29 Jul 2012 23:33:20 -0000

As a reminder, the Internet Society is organizing a briefing panel on =
Tuesday, 31 July, 11:45am - 12:45pm PDT, in conjunction with IETF 84 in =
Vancouver:

	 World IPv6: Launched!

On June 6, 2012, more than 50 access providers and thousands of websites =
around the globe joined together in establishing IPv6 as the "new =
normal" for the Internet. Participating content providers turned on IPv6 =
on their main sites -- for good.  Participating access providers are =
offering IPv6 by default to their customers, and have at least 1% of =
their traffic to major websites over IPv6.  At a high level, it is clear =
that this represents a significant, concrete step forward in the =
deployment of operational IPv6 in the Internet.  Uptake of IPv6 is not =
evenly distributed across all access networks for a variety of reasons =
and there is clearly still much work to do.  This panel will share more =
specific numbers and perspectives outlining the impact of World IPv6 =
Launch.

A limited number of seats are still available for the briefing.  =
Pre-registration is required and available by following the link at:
http://www.internetsociety.org/isoc-panel-ietf-84

For those unable to attend, we will provide a live audiocast at:
http://verilan.com/isoc.m3u

Kevin Craemer
Senior Events Manager
Internet Society
craemer@isoc.org


From sob@sobco.com  Mon Jul 30 09:34:00 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 2997B21F860B for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 09:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.336
X-Spam-Level: 
X-Spam-Status: No, score=-0.336 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIw5f8jT2HMl for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 09:33:59 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4CC21F85AC for <ietf@ietf.org>; Mon, 30 Jul 2012 09:33:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 888CD3551288; Mon, 30 Jul 2012 12:33:57 -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 tiDHdgAVwfyD; Mon, 30 Jul 2012 12:33:55 -0400 (EDT)
Received: from [136.248.127.172] (unknown [136.248.127.172]) by sobco.sobco.com (Postfix) with ESMTPSA id 3C0723551276; Mon, 30 Jul 2012 12:33:55 -0400 (EDT)
Subject: Re: I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <50164E21.2040904@gmail.com>
Date: Mon, 30 Jul 2012 12:33:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com>
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com> <50164E21.2040904@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Mon, 30 Jul 2012 09:42:18 -0700
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 16:34:00 -0000

2804 does not say not to talk about such things - or that such documents =
should
not be published as RFCs  - 2804 says that the IETF will not do =
standards work
in this area

Scott

On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:

> Under the long-standing IETF policy defined in RFC 2804, I trust
> we will not be discussing this draft, or
> draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
>=20
> Regards
>   Brian Carpenter
>=20
> On 30/07/2012 09:26, internet-drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>>=20
>>=20
>> 	Title           : Label-based Provider-Provisioned Lawful =
Intercept for L3 VPNs
>> 	Author(s)       : Shankar Raman
>>                          Balaji Venkat Venkataswami
>>                          Gaurav Raina
>>                          Vasan Srini
>>                          Bhargav Bhikkaji
>> 	Filename        : =
draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
>> 	Pages           : 12
>> 	Date            : 2012-07-30
>>=20
>> Abstract:
>>   In models of Single-AS and inter-provider Multi- Protocol Label
>>   Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
>>   Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
>>   models like VPLS and the like do not have any provider provisioned
>>   methods of lawful intercept that are comprehensive, quick and easy =
to
>>   provision from one single point. More particularly the auto-
>>   provisioning of lawful intercept for all sets of streams travelling
>>   between VPN sites and consequent re-direction of these streams to =
the
>>   appropriate government network has not been covered without =
multiple
>>   instances of having to configure the intercept at various points in
>>   the network both in the Single-AS case and the Inter-Provider VPN
>>   case.
>>=20
>>   this paper, we propose a technique which uses a set of pre-defined
>>   labels called Lawful Intercept labels and a method for provisioning
>>   lawful intercept amongst the various PE devices using these labels
>>   both in the Single-AS and the inter-provider VPN cases. A single
>>   point of configuration is the key to this idea. The intercepted
>>   traffic is mirrored on a PE or a whole set of PEs or on all the PEs
>>   participating in the VPN. A technique called the Domino-effect
>>   provisioning of these Label-based Provider Provisioned Lawful
>>   Intercept mechanism is also outlined.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> =
https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-l=
abel-dis
>>=20
>> There's also a htmlized version available at:
>> =
http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-d=
is-00
>>=20
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>=20


From eburger-l@standardstrack.com  Mon Jul 30 10:08:24 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 6ACDF11E80BA for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 10:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e-AIPNW9Dy50 for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 10:08:23 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.250.112]) by ietfa.amsl.com (Postfix) with ESMTP id BAB3E21F8577 for <ietf@ietf.org>; Mon, 30 Jul 2012 10:08:23 -0700 (PDT)
Received: from dhcp-910f.meeting.ietf.org ([130.129.9.15]:54630) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1SvtS4-0000S9-3c for ietf@ietf.org; Mon, 30 Jul 2012 10:08:16 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com>
Date: Mon, 30 Jul 2012 10:08:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4BC366A-7A75-40A8-86AB-5C2C2B8262F3@standardstrack.com>
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com> <50164E21.2040904@gmail.com> <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com>
To: IETF list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
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: Mon, 30 Jul 2012 17:08:24 -0000

We seem to be doing a lot of talking about the draft.

On Jul 30, 2012, at 9:33 AM, Scott O Bradner wrote:

> 2804 does not say not to talk about such things - or that such =
documents should
> not be published as RFCs  - 2804 says that the IETF will not do =
standards work
> in this area
>=20
> Scott
>=20
> On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:
>=20
>> Under the long-standing IETF policy defined in RFC 2804, I trust
>> we will not be discussing this draft, or
>> draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
>>=20
>> Regards
>>  Brian Carpenter
>>=20
>> On 30/07/2012 09:26, internet-drafts@ietf.org wrote:
>>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>>>=20
>>>=20
>>> 	Title           : Label-based Provider-Provisioned Lawful =
Intercept for L3 VPNs
>>> 	Author(s)       : Shankar Raman
>>>                         Balaji Venkat Venkataswami
>>>                         Gaurav Raina
>>>                         Vasan Srini
>>>                         Bhargav Bhikkaji
>>> 	Filename        : =
draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
>>> 	Pages           : 12
>>> 	Date            : 2012-07-30
>>>=20
>>> Abstract:
>>>  In models of Single-AS and inter-provider Multi- Protocol Label
>>>  Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
>>>  Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
>>>  models like VPLS and the like do not have any provider provisioned
>>>  methods of lawful intercept that are comprehensive, quick and easy =
to
>>>  provision from one single point. More particularly the auto-
>>>  provisioning of lawful intercept for all sets of streams travelling
>>>  between VPN sites and consequent re-direction of these streams to =
the
>>>  appropriate government network has not been covered without =
multiple
>>>  instances of having to configure the intercept at various points in
>>>  the network both in the Single-AS case and the Inter-Provider VPN
>>>  case.
>>>=20
>>>  this paper, we propose a technique which uses a set of pre-defined
>>>  labels called Lawful Intercept labels and a method for provisioning
>>>  lawful intercept amongst the various PE devices using these labels
>>>  both in the Single-AS and the inter-provider VPN cases. A single
>>>  point of configuration is the key to this idea. The intercepted
>>>  traffic is mirrored on a PE or a whole set of PEs or on all the PEs
>>>  participating in the VPN. A technique called the Domino-effect
>>>  provisioning of these Label-based Provider Provisioned Lawful
>>>  Intercept mechanism is also outlined.
>>>=20
>>>=20
>>> The IETF datatracker status page for this draft is:
>>> =
https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-l=
abel-dis
>>>=20
>>> There's also a htmlized version available at:
>>> =
http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-d=
is-00
>>>=20
>>>=20
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>=20
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>=20
>=20


From rbarnes@bbn.com  Mon Jul 30 10:18:41 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD2011E810C; Mon, 30 Jul 2012 10:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.608
X-Spam-Level: 
X-Spam-Status: No, score=-106.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gNO2LkCFCs+f; Mon, 30 Jul 2012 10:18:40 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 26FC911E80A4; Mon, 30 Jul 2012 10:18:39 -0700 (PDT)
Received: from [128.89.254.164] (port=54153) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Svtbp-00022u-Ux; Mon, 30 Jul 2012 13:18:22 -0400
Subject: Re: Gen-ART review of draft-ietf-dnsext-dnssec-bis-updates-18
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <20120619021211.GI32683@crankycanuck.ca>
Date: Mon, 30 Jul 2012 10:18:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A7F5D7E-C3A8-4118-ADA1-C9CB814CDF72@bbn.com>
References: <EBFB2D2E-78FF-46D6-B4FF-1F57FB8D769B@bbn.com> <20120619021211.GI32683@crankycanuck.ca>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1278)
Cc: draft-ietf-dnsext-dnssec-bis-updates@tools.ietf.org, ietf@ietf.org, dnsext@ietf.org, IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 17:18:41 -0000

Hey Andrew,

Thanks for following up, and sorry for the lag.  Thank goodness for IETF =
meetings giving us time to process email :)

Couple of responses inline.

>> MAJOR:
>>=20
>> 4.1. =20
>> It's not clear what the threat model is that this section is
>> designed to address.  If the zone operator is malicious, then it can
>> simulate the necessary zone cut and still prove the non-existence of
>> records in the child zone.
>=20
> The problem here is not a malicious parent operator, but "an NSEC or
> NSEC3 RR from an ancestor zone".  In the original specification, an
> attacker could use such an RR to prove the non-existence of some name
> in a subordinate zone.  That was the problem.  (Remember, in DNS there
> is a good chance that you are not talking to an authoritative server.)
> If you have suggestions on ways to make that clearer, it'd be welcome.
> The editors tried to come up with compact examples that would be
> anything other than mystifying, and were unsuccessful. =20

I guess I still don't understand this.  Aren't ancestors the only people =
that can generate a valid, signed NSEC or NSEC3 RR?  So if there were a =
bad NSEC[3], wouldn't it be the ancestor's fault?

If the provisioning is *intentional*, then as I noted before, then =
there's not really anything to be done, since the ancestor can provide =
whatever information he wants for the child zones (as above).  So are =
you worried about *inadvertent* provisioning of these bad records? =20



>> 5.10. =20
>> I find the recommendation of the "Accept Any Success" policy
>> troubling.  It deals very poorly with compromise (and other
>> roll-over scenarios): Suppose there are two trust anchors, one for
>> example.com and one for child.example.com.  If the private key
>> corresponding to the TA for child.example.com is compromised, but
>> the validator continues to trust it, this negates the benefit
>> provided by the parent (example.com) facilitating a rollover.
>> Suggest an alternative policy, "Highest Signer": Out of the set of
>> keys configured as TAs, the validator only uses a key as a TA (for
>> purposes of validation) if there does not exist a DNSSEC path from
>> it to any other TA.  This policy seems like more work to enforce
>> (because you have to do more backward chaining), but ISTM that the
>> validator should have the necessary DNSSEC records anyway, so it's
>> just a matter a couple of quick checks.
>=20
> First, the Working Group debated this matter at considerable length,
> several times.  The Accept Any Success policy provides greater
> robustness in the face of configuration errors, and is more likely to
> lead to continued resolution.  We believe, based on experience so far,
> that such configuration errors are vastly more likely than key
> compromise.  If we are to reopen this, we will need to go back to the
> WG again. =20
>=20
> Note that Appendix C does discuss other options and 5.10 explicitly
> suggests that this be configurable; but, because the biggest problem
> we have is resolution failure in the face of mucked up configurations,
> the consensus was that Accept Any Success was the best default.  That
> could, of course, change in future, at which time an update to the
> document would be advisable.
>=20
> The suggestion for "Highest Signer" is interesting but has never to my
> knowledge been previously mooted in relation to this draft.  I
> therefore think that including it in particular would require some
> review.  I don't know of any implementation that currently uses that
> approach, either (but since there are vast gaps in my knowledge even
> of what's on my desk, it wouldn't surprise me to learn that there were
> some).  Do you know of any?  If not, it seems to me that it would be a
> good idea to have some fielded experience with the approach before
> recommending it as default.  It's an intriguing idea, however, and
> seems to me to be worth pursuing.  I'm just not sure it should be in
> this draft.  I personally think it would be premature to recommend it
> as default, but if you take your position very firmly I am prepared to
> take the question up with the Working Group.

Ok, I can understand these considerations.  Typical usability/security =
trade-off.

As per the normal security MO, if you're going to recommend an approach =
with known security weaknesses, then you need to document them.  I think =
it would be helpful to note how this approach can lead to problems, =
e.g., by causing you to miss a roll-over of a compromised key.  The =
current text seems insufficient, especially because it's relegated to an =
appendix. Suggested text at the end of Section 5.10:
NEW:
"
This policy minimizes the likelihood that configuration errors in =
servers or resolvers will result in validation failures.  However, by =
the same token, a resolver following this policy is vulnerable to a =
broader set of attacks than one following a more restrictive policy.  =
For example, if the resolver has TAs for a parent domain and a child of =
that parent, and the child's key is compromised, then the resolver will =
continue to validate responses signed under the compromised key even if =
a new key for the child is published in a DS record signed by the =
parent. =20
"

May also be helpful to say something like "as we get more experience =
with validation, we may find that it's OK to be more restrictive".

If you're willing to, it might be helpful to document the "Highest =
signer" approach.  If so, let me know and I can provide text.

Thanks,
--Richard =20



From randy@psg.com  Mon Jul 30 10:33:56 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 9B84111E8182 for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 10:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5OtkfrdnC1DA for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 10:33:56 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE7D11E8180 for <ietf@ietf.org>; Mon, 30 Jul 2012 10:33:56 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Svtqr-000MYV-GR; Mon, 30 Jul 2012 17:33:53 +0000
Date: Mon, 30 Jul 2012 10:33:53 -0700
Message-ID: <m2ipd5w3um.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Scott O Bradner <sob@sobco.com>
Subject: Re: I-D Action:	draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
In-Reply-To: <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com>
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com> <50164E21.2040904@gmail.com> <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.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.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 17:33:56 -0000

> 2804 does not say not to talk about such things - or that such documents should
> not be published as RFCs  - 2804 says that the IETF will not do standards work
> in this area

for those of us who are easily confused, could you differentiate between
working on douments and publishing them as rfcs from doing standards
work?

randy

From brian.e.carpenter@gmail.com  Mon Jul 30 10:51:10 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7083A11E809B for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 10:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.421
X-Spam-Level: 
X-Spam-Status: No, score=-101.421 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ylyb0NrzYHxV for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 10:51:09 -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 56D6211E808D for <ietf@ietf.org>; Mon, 30 Jul 2012 10:51:09 -0700 (PDT)
Received: by eekb45 with SMTP id b45so1347594eek.31 for <ietf@ietf.org>; Mon, 30 Jul 2012 10:51:08 -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=OIDs+Hz0Ev48vBFiyD5EtAZ2Da/7RLJc+OisgnNww9c=; b=px10qAmm5ODH895Gw5LIDyM/sfhATUrujCuf+JkGe2OE4LyRBTAuyc439/ElNptfLl pN4N1LIxh9+GNqtZUWIB0nFo4jfIbifxG8E1pMGpOjk8qHQVExGP/Wbaae5o0xfzx5Eb xpM7oX8qprkASdY7Thn780T7nEjouFqOEpk0BrID3Xyj0+W9G/HF/cxht0d3aRVUUAYv T1CWRO/7KvMh/E0OfvaNFemDJ+Tdfns4/+oOyd2jp6mQZj0qtHIDeDL7DfdgC5U3HNTm WZRQ06fEciHUertM3YDKcXdE1atnA2KbFedGt4GZInGMNV2qp/Z5gAqakz9PLSfcoEYV M2dQ==
Received: by 10.14.198.131 with SMTP id v3mr13014725een.26.1343670668469; Mon, 30 Jul 2012 10:51:08 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-212.as13285.net. [2.102.216.212]) by mx.google.com with ESMTPS id t6sm30210847eeo.17.2012.07.30.10.51.05 (version=SSLv3 cipher=OTHER); Mon, 30 Jul 2012 10:51:06 -0700 (PDT)
Message-ID: <5016C98A.9020200@gmail.com>
Date: Mon, 30 Jul 2012 18:51:06 +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: Scott O Bradner <sob@sobco.com>
Subject: Re: I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com> <50164E21.2040904@gmail.com> <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com>
In-Reply-To: <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 17:51:10 -0000

Yes, Scott, that is correct, sorry for my poor phrasing.

   Brian

On 30/07/2012 17:33, Scott O Bradner wrote:
> 2804 does not say not to talk about such things - or that such documents should
> not be published as RFCs  - 2804 says that the IETF will not do standards work
> in this area
> 
> Scott
> 
> On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:
> 
>> Under the long-standing IETF policy defined in RFC 2804, I trust
>> we will not be discussing this draft, or
>> draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
>>
>> Regards
>>   Brian Carpenter
>>
>> On 30/07/2012 09:26, internet-drafts@ietf.org wrote:
>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>
>>>
>>> 	Title           : Label-based Provider-Provisioned Lawful Intercept for L3 VPNs
>>> 	Author(s)       : Shankar Raman
>>>                          Balaji Venkat Venkataswami
>>>                          Gaurav Raina
>>>                          Vasan Srini
>>>                          Bhargav Bhikkaji
>>> 	Filename        : draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
>>> 	Pages           : 12
>>> 	Date            : 2012-07-30
>>>
>>> Abstract:
>>>   In models of Single-AS and inter-provider Multi- Protocol Label
>>>   Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
>>>   Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
>>>   models like VPLS and the like do not have any provider provisioned
>>>   methods of lawful intercept that are comprehensive, quick and easy to
>>>   provision from one single point. More particularly the auto-
>>>   provisioning of lawful intercept for all sets of streams travelling
>>>   between VPN sites and consequent re-direction of these streams to the
>>>   appropriate government network has not been covered without multiple
>>>   instances of having to configure the intercept at various points in
>>>   the network both in the Single-AS case and the Inter-Provider VPN
>>>   case.
>>>
>>>   this paper, we propose a technique which uses a set of pre-defined
>>>   labels called Lawful Intercept labels and a method for provisioning
>>>   lawful intercept amongst the various PE devices using these labels
>>>   both in the Single-AS and the inter-provider VPN cases. A single
>>>   point of configuration is the key to this idea. The intercepted
>>>   traffic is mirrored on a PE or a whole set of PEs or on all the PEs
>>>   participating in the VPN. A technique called the Domino-effect
>>>   provisioning of these Label-based Provider Provisioned Lawful
>>>   Intercept mechanism is also outlined.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-label-dis
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-dis-00
>>>
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>
> 
> 

From stephen.farrell@cs.tcd.ie  Mon Jul 30 11:26: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 8AA0C21F86B2 for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 11:26: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WiDpupmAzEPe for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 11:26: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 8AB7021F869E for <ietf@ietf.org>; Mon, 30 Jul 2012 11:26:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id C51E1153B4E; Mon, 30 Jul 2012 19:26:40 +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=1343672800; bh=bho7Olimx/5Niu gSgRYfTS8fHbV/LITjk+MkVKBhQ44=; b=gMJPBl3J817CarwOtogVMeRS0l/D8g MDxdkbCMQZ8NCXs/sM6c/behWJ0uE5OD0lEYCxqW4wsWDPxqsyKdznYCvaD0bZKM jPRNhMk1kdPj2mwqih1mEEwju/rwX0BeTSG8LH9d3yqOIn1hT7TjPFy5tzefv2Ub dt+sD1vUIln7maqr5cIwGJGuN21vupupl+/0UsNESfEJwanrG71UUC04RSNw0ZwU +Xq0fSblJhYadVdV2wr1+8/EWFS4X5AzteBkMe/PwqbMvEC7t2QykR5zesIkE+9i QDT+GYEHS32XpCyfxIwcpAkj3Zp2A33rHtYC4/VjSAIZFRSEErZslTzg==
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 q-qKnnvQcro6; Mon, 30 Jul 2012 19:26:40 +0100 (IST)
Received: from [IPv6:2001:df8:0:32:5db4:9f98:9399:2014] (unknown [IPv6:2001:df8:0:32:5db4:9f98:9399:2014]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id D0E5F153953; Mon, 30 Jul 2012 19:26:38 +0100 (IST)
Message-ID: <5016D1DB.2040600@cs.tcd.ie>
Date: Mon, 30 Jul 2012 19:26:35 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com> <50164E21.2040904@gmail.com> <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com> <5016C98A.9020200@gmail.com>
In-Reply-To: <5016C98A.9020200@gmail.com>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Scott O Bradner <sob@sobco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 18:26:43 -0000

I agree with the comments about 2804.

I do note a lot of April 1 RFCs in the references
though, so maybe its all a joke.

S

On 07/30/2012 06:51 PM, Brian E Carpenter wrote:
> Yes, Scott, that is correct, sorry for my poor phrasing.
> 
>    Brian
> 
> On 30/07/2012 17:33, Scott O Bradner wrote:
>> 2804 does not say not to talk about such things - or that such documents should
>> not be published as RFCs  - 2804 says that the IETF will not do standards work
>> in this area
>>
>> Scott
>>
>> On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:
>>
>>> Under the long-standing IETF policy defined in RFC 2804, I trust
>>> we will not be discussing this draft, or
>>> draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
>>>
>>> Regards
>>>   Brian Carpenter
>>>
>>> On 30/07/2012 09:26, internet-drafts@ietf.org wrote:
>>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>>
>>>>
>>>> 	Title           : Label-based Provider-Provisioned Lawful Intercept for L3 VPNs
>>>> 	Author(s)       : Shankar Raman
>>>>                          Balaji Venkat Venkataswami
>>>>                          Gaurav Raina
>>>>                          Vasan Srini
>>>>                          Bhargav Bhikkaji
>>>> 	Filename        : draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
>>>> 	Pages           : 12
>>>> 	Date            : 2012-07-30
>>>>
>>>> Abstract:
>>>>   In models of Single-AS and inter-provider Multi- Protocol Label
>>>>   Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
>>>>   Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
>>>>   models like VPLS and the like do not have any provider provisioned
>>>>   methods of lawful intercept that are comprehensive, quick and easy to
>>>>   provision from one single point. More particularly the auto-
>>>>   provisioning of lawful intercept for all sets of streams travelling
>>>>   between VPN sites and consequent re-direction of these streams to the
>>>>   appropriate government network has not been covered without multiple
>>>>   instances of having to configure the intercept at various points in
>>>>   the network both in the Single-AS case and the Inter-Provider VPN
>>>>   case.
>>>>
>>>>   this paper, we propose a technique which uses a set of pre-defined
>>>>   labels called Lawful Intercept labels and a method for provisioning
>>>>   lawful intercept amongst the various PE devices using these labels
>>>>   both in the Single-AS and the inter-provider VPN cases. A single
>>>>   point of configuration is the key to this idea. The intercepted
>>>>   traffic is mirrored on a PE or a whole set of PEs or on all the PEs
>>>>   participating in the VPN. A technique called the Domino-effect
>>>>   provisioning of these Label-based Provider Provisioned Lawful
>>>>   Intercept mechanism is also outlined.
>>>>
>>>>
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-label-dis
>>>>
>>>> There's also a htmlized version available at:
>>>> http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-dis-00
>>>>
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> _______________________________________________
>>>> I-D-Announce mailing list
>>>> I-D-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>
>>
>>
> 
> 

From glenzorn@gmail.com  Mon Jul 30 11:36:01 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 899CB11E8087 for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 11:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vMx1pBddH7Pi for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 11:36:00 -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 ACB0A21F86E3 for <ietf@ietf.org>; Mon, 30 Jul 2012 11:36:00 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so10195401pbc.31 for <ietf@ietf.org>; Mon, 30 Jul 2012 11:36:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:from:to:cc:in-reply-to:references:content-type:organization :date:message-id:mime-version:x-mailer; bh=LW/KHnrKLIgZuwHhcdLZMIomZO9oic1Y7S1YuZJ7mbg=; b=i01kdqlm2zkTKLsg79Uyfi1AN4XVFx2rAMNvVBXsJMcArRlgw23q8NrWOZAQE97/wB z7kiN2i+PUo0J4taX/qxFUsHz/wpHdCig37B0BQj5fUHFBKgIRJXSYymndXbWtSugWBm 7eylBkIfMsbpWjZ+kysX/LARud40oTIE7BBDsuF5rgl9d7JVeRE2DDedF+iOSDBlJ6ns AtXloKEWpbQ0BNTDuhc9YAd+HMWt3VhFEicmaAWYiCdbpTr+CN0TV+CKEmeqIAX/SbHn e8WMCjTJcRw5XoCkGQ7AriA4cWC+5PF3za6DFkyid5HebuoEnBeG5m7fTEKIyd9qBRBw mU0A==
Received: by 10.68.227.163 with SMTP id sb3mr37910315pbc.74.1343673360396; Mon, 30 Jul 2012 11:36:00 -0700 (PDT)
Received: from [10.0.1.195] (216-19-185-109.dyn.novuscom.net. [216.19.185.109]) by mx.google.com with ESMTPS id mr1sm8378225pbb.62.2012.07.30.11.35.59 (version=SSLv3 cipher=OTHER); Mon, 30 Jul 2012 11:35:59 -0700 (PDT)
Subject: Re: I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
From: Glen Zorn <glenzorn@gmail.com>
To: ietf@ietf.org
In-Reply-To: <5016D1DB.2040600@cs.tcd.ie>
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com> <50164E21.2040904@gmail.com> <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com> <5016C98A.9020200@gmail.com>  <5016D1DB.2040600@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="=-epr5Zba9+0obElZoHqvb"
Organization: Network Zen
Date: Mon, 30 Jul 2012 11:35:57 -0700
Message-ID: <1343673357.26306.5.camel@gwz-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-1.fc14) 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2012 18:36:01 -0000

--=-epr5Zba9+0obElZoHqvb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

On Mon, 2012-07-30 at 19:26 +0100, Stephen Farrell wrote:

> I agree with the comments about 2804.
> 
> I do note a lot of April 1 RFCs in the references
> though, so maybe its all a joke.


Gotta be!


> 
> S
> 
> On 07/30/2012 06:51 PM, Brian E Carpenter wrote:
> > Yes, Scott, that is correct, sorry for my poor phrasing.
> > 
> >    Brian
> > 
> > On 30/07/2012 17:33, Scott O Bradner wrote:
> >> 2804 does not say not to talk about such things - or that such documents should
> >> not be published as RFCs  - 2804 says that the IETF will not do standards work
> >> in this area
> >>
> >> Scott
> >>
> >> On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:
> >>
> >>> Under the long-standing IETF policy defined in RFC 2804, I trust
> >>> we will not be discussing this draft, or
> >>> draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
> >>>
> >>> Regards
> >>>   Brian Carpenter
> >>>
> >>> On 30/07/2012 09:26, internet-drafts@ietf.org wrote:
> >>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >>>>
> >>>>
> >>>> 	Title           : Label-based Provider-Provisioned Lawful Intercept for L3 VPNs
> >>>> 	Author(s)       : Shankar Raman
> >>>>                          Balaji Venkat Venkataswami
> >>>>                          Gaurav Raina
> >>>>                          Vasan Srini
> >>>>                          Bhargav Bhikkaji
> >>>> 	Filename        : draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
> >>>> 	Pages           : 12
> >>>> 	Date            : 2012-07-30
> >>>>
> >>>> Abstract:
> >>>>   In models of Single-AS and inter-provider Multi- Protocol Label
> >>>>   Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
> >>>>   Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
> >>>>   models like VPLS and the like do not have any provider provisioned
> >>>>   methods of lawful intercept that are comprehensive, quick and easy to
> >>>>   provision from one single point. More particularly the auto-
> >>>>   provisioning of lawful intercept for all sets of streams travelling
> >>>>   between VPN sites and consequent re-direction of these streams to the
> >>>>   appropriate government network has not been covered without multiple
> >>>>   instances of having to configure the intercept at various points in
> >>>>   the network both in the Single-AS case and the Inter-Provider VPN
> >>>>   case.
> >>>>
> >>>>   this paper, we propose a technique which uses a set of pre-defined
> >>>>   labels called Lawful Intercept labels and a method for provisioning
> >>>>   lawful intercept amongst the various PE devices using these labels
> >>>>   both in the Single-AS and the inter-provider VPN cases. A single
> >>>>   point of configuration is the key to this idea. The intercepted
> >>>>   traffic is mirrored on a PE or a whole set of PEs or on all the PEs
> >>>>   participating in the VPN. A technique called the Domino-effect
> >>>>   provisioning of these Label-based Provider Provisioned Lawful
> >>>>   Intercept mechanism is also outlined.
> >>>>
> >>>>
> >>>> The IETF datatracker status page for this draft is:
> >>>> https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-label-dis
> >>>>
> >>>> There's also a htmlized version available at:
> >>>> http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-dis-00
> >>>>
> >>>>
> >>>> Internet-Drafts are also available by anonymous FTP at:
> >>>> ftp://ftp.ietf.org/internet-drafts/
> >>>>
> >>>> _______________________________________________
> >>>> I-D-Announce mailing list
> >>>> I-D-Announce@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/i-d-announce
> >>>> Internet-Draft directories: http://www.ietf.org/shadow.html
> >>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>>>
> >>
> >>
> > 
> > 



--=-epr5Zba9+0obElZoHqvb
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
On Mon, 2012-07-30 at 19:26 +0100, Stephen Farrell wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
I agree with the comments about 2804.

I do note a lot of April 1 RFCs in the references
though, so maybe its all a joke.
</PRE>
</BLOCKQUOTE>
<BR>
Gotta be!<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

S

On 07/30/2012 06:51 PM, Brian E Carpenter wrote:
&gt; Yes, Scott, that is correct, sorry for my poor phrasing.
&gt; 
&gt;    Brian
&gt; 
&gt; On 30/07/2012 17:33, Scott O Bradner wrote:
&gt;&gt; 2804 does not say not to talk about such things - or that such documents should
&gt;&gt; not be published as RFCs  - 2804 says that the IETF will not do standards work
&gt;&gt; in this area
&gt;&gt;
&gt;&gt; Scott
&gt;&gt;
&gt;&gt; On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:
&gt;&gt;
&gt;&gt;&gt; Under the long-standing IETF policy defined in RFC 2804, I trust
&gt;&gt;&gt; we will not be discussing this draft, or
&gt;&gt;&gt; draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
&gt;&gt;&gt;
&gt;&gt;&gt; Regards
&gt;&gt;&gt;   Brian Carpenter
&gt;&gt;&gt;
&gt;&gt;&gt; On 30/07/2012 09:26, <A HREF="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</A> wrote:
&gt;&gt;&gt;&gt; A New Internet-Draft is available from the on-line Internet-Drafts directories.
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt; 	Title           : Label-based Provider-Provisioned Lawful Intercept for L3 VPNs
&gt;&gt;&gt;&gt; 	Author(s)       : Shankar Raman
&gt;&gt;&gt;&gt;                          Balaji Venkat Venkataswami
&gt;&gt;&gt;&gt;                          Gaurav Raina
&gt;&gt;&gt;&gt;                          Vasan Srini
&gt;&gt;&gt;&gt;                          Bhargav Bhikkaji
&gt;&gt;&gt;&gt; 	Filename        : draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
&gt;&gt;&gt;&gt; 	Pages           : 12
&gt;&gt;&gt;&gt; 	Date            : 2012-07-30
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt; Abstract:
&gt;&gt;&gt;&gt;   In models of Single-AS and inter-provider Multi- Protocol Label
&gt;&gt;&gt;&gt;   Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
&gt;&gt;&gt;&gt;   Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
&gt;&gt;&gt;&gt;   models like VPLS and the like do not have any provider provisioned
&gt;&gt;&gt;&gt;   methods of lawful intercept that are comprehensive, quick and easy to
&gt;&gt;&gt;&gt;   provision from one single point. More particularly the auto-
&gt;&gt;&gt;&gt;   provisioning of lawful intercept for all sets of streams travelling
&gt;&gt;&gt;&gt;   between VPN sites and consequent re-direction of these streams to the
&gt;&gt;&gt;&gt;   appropriate government network has not been covered without multiple
&gt;&gt;&gt;&gt;   instances of having to configure the intercept at various points in
&gt;&gt;&gt;&gt;   the network both in the Single-AS case and the Inter-Provider VPN
&gt;&gt;&gt;&gt;   case.
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt;   this paper, we propose a technique which uses a set of pre-defined
&gt;&gt;&gt;&gt;   labels called Lawful Intercept labels and a method for provisioning
&gt;&gt;&gt;&gt;   lawful intercept amongst the various PE devices using these labels
&gt;&gt;&gt;&gt;   both in the Single-AS and the inter-provider VPN cases. A single
&gt;&gt;&gt;&gt;   point of configuration is the key to this idea. The intercepted
&gt;&gt;&gt;&gt;   traffic is mirrored on a PE or a whole set of PEs or on all the PEs
&gt;&gt;&gt;&gt;   participating in the VPN. A technique called the Domino-effect
&gt;&gt;&gt;&gt;   provisioning of these Label-based Provider Provisioned Lawful
&gt;&gt;&gt;&gt;   Intercept mechanism is also outlined.
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt; The IETF datatracker status page for this draft is:
&gt;&gt;&gt;&gt; <A HREF="https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-label-dis">https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-label-dis</A>
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt; There's also a htmlized version available at:
&gt;&gt;&gt;&gt; <A HREF="http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-dis-00">http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-dis-00</A>
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt; Internet-Drafts are also available by anonymous FTP at:
&gt;&gt;&gt;&gt; <A HREF="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</A>
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt; _______________________________________________
&gt;&gt;&gt;&gt; I-D-Announce mailing list
&gt;&gt;&gt;&gt; <A HREF="mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</A>
&gt;&gt;&gt;&gt; <A HREF="https://www.ietf.org/mailman/listinfo/i-d-announce">https://www.ietf.org/mailman/listinfo/i-d-announce</A>
&gt;&gt;&gt;&gt; Internet-Draft directories: <A HREF="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</A>
&gt;&gt;&gt;&gt; or <A HREF="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</A>
&gt;&gt;&gt;&gt;
&gt;&gt;
&gt;&gt;
&gt; 
&gt; 
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-epr5Zba9+0obElZoHqvb--


From randy@psg.com  Mon Jul 30 11:39:58 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D89C711E80E0; Mon, 30 Jul 2012 11:39:57 -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.115,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xnFWFhoIGELn; Mon, 30 Jul 2012 11:39:57 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 716C611E80C5; Mon, 30 Jul 2012 11:39:57 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Svusn-000Mlm-7e; Mon, 30 Jul 2012 18:39:57 +0000
Date: Mon, 30 Jul 2012 11:39:57 -0700
Message-ID: <m24nopw0si.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: [OPSAWG] Last Call:	<draft-ietf-opsawg-automated-network-configuration-04.txt>	(Problem	Statement for the Automated Configuration of Large	IP	Networks) to Informational RFC
In-Reply-To: <20120725181357.21674.65763.idtracker@ietfa.amsl.com>
References: <20120725181357.21674.65763.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: opsawg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2012 18:39:58 -0000

> The IESG has received a request from the Operations and Management Area
> Working Group WG (opsawg) to consider the following document:
> - 'Problem Statement for the Automated Configuration of Large IP
> Networks'
>   <draft-ietf-opsawg-automated-network-configuration-04.txt> as
> Informational RFC

in general, imiho the document is not particularly harmful.  but section
10 Conclusions makes recommendations which are inappropriate and
contentious and should be removed.

randy

From alexandru.petrescu@gmail.com  Mon Jul 30 13:14:56 2012
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFD821F8600 for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 13:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.216
X-Spam-Level: 
X-Spam-Status: No, score=-4.216 tagged_above=-999 required=5 tests=[AWL=-0.617, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EKh40OwK42Dv for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 13:14:55 -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 D1AE521F851E for <ietf@ietf.org>; Mon, 30 Jul 2012 13:14:55 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so10313079pbc.31 for <ietf@ietf.org>; Mon, 30 Jul 2012 13:14: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 :content-type:content-transfer-encoding; bh=EtbMNxWtuhnXj7YggHNGOTzxMxY6Kn+lMUj+DeaTG/s=; b=SOZHy7fkz5W0vxzxoJPFRYLGjBHVUTCyL8K4FqKNUDPrbGQwThdUqTndeV2sJIt+7z ypOo5AdgXDpJjAYlicE64qqzwfcAWg3KjCnfiioPH3lRs5RH/9rUGgtlA0Z7NBTcw+EH 2T/iJU13SmbJ1/CEIJdfOfClkr8d+8pLhVIttkKcG0UeenkptsA+EWrzG4X2ygm4tFIP l2TN0ZNgvZZ3+0rz3G5Evw2uin/uSqE1VnvcR9JgljkeL4DS/LFDrtT7YyFaIIsUxqGW xE1MsQ02GDbiI4tpVVtJiuX0vWdmTYDvImj5GSI1FdUgdB0m0ZAfRNuzeYtRwBCOJVU9 gpAg==
Received: by 10.68.116.203 with SMTP id jy11mr37533128pbb.129.1343679295614; Mon, 30 Jul 2012 13:14:55 -0700 (PDT)
Received: from [130.129.19.174] (dhcp-13ae.meeting.ietf.org. [130.129.19.174]) by mx.google.com with ESMTPS id tq4sm8526123pbc.11.2012.07.30.13.14.54 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 Jul 2012 13:14:55 -0700 (PDT)
Message-ID: <5016EB39.5020604@free.fr>
Date: Mon, 30 Jul 2012 13:14:49 -0700
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: bar BoF ITS Intelligent Transportation Systems, today 19h30-20h30, room Plaza C
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 20:14:56 -0000

Dear IETFers,

I invite to join us at the bar BoF ITS - IP for Intelligent
Transportation Systems

     today 30 july 2012
     19h30-20h30 Vancouver at Pacific time
     room Plaza C, 2nd floor
     email list its@ietf.org, https://www.ietf.org/mailman/listinfo/its
     webex
https://cea-list.webex.com/cea-list/j.php?ED=219289702&UID=0&PW=NOGFmZmI1MzA2&RT=NyM0
     password itsietf

During the previous IETF meeting in Paris, the first ITS informal
meeting took place; then several potential work items
were identified and presented (http://imara.inria.fr/ietf-its).

Since then we discussed scenarios, requirements and work items.

The goal of the meeting this evening is to better identify the scope of
potential work, problem and work items.  What would a Charter look like.

Yours,

Alex

From dromasca@avaya.com  Mon Jul 30 14:20:42 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 4327211E80DF for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 14:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.926
X-Spam-Level: 
X-Spam-Status: No, score=-102.926 tagged_above=-999 required=5 tests=[AWL=-0.327, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h0MY1Skv8-Eq for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 14:20:41 -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 9147411E80DB for <ietf@ietf.org>; Mon, 30 Jul 2012 14:20:41 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOD5FlCHCzI1/2dsb2JhbABFuVmBB4IgAQEBAQMSHgpLBAIBCA0EAQMBAQsGDAsBBgFFAwYIAQEEEwgah2sLnWSdHotQhilgA5ZdhGmKEIJh
X-IronPort-AV: E=Sophos;i="4.77,682,1336363200"; d="scan'208";a="20358569"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 30 Jul 2012 17:15:17 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 30 Jul 2012 17:00:58 -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: Draft IESG Statement Regarding Ethertype Requests
Date: Mon, 30 Jul 2012 23:20:38 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407E24097@307622ANEX5.global.avaya.com>
In-Reply-To: <CDF73C59-A8E8-43B4-B67D-34CFAF541DB6@ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Draft IESG Statement Regarding Ethertype Requests
Thread-Index: Ac1ucglK7XvYelX1TvqXeISuKMPP3AAJdJQA
References: <CDF73C59-A8E8-43B4-B67D-34CFAF541DB6@ietf.org>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "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, 30 Jul 2012 21:20:42 -0000

(I hope not to open some Pandora box or a long thread - my goal is to
make sure there is clarity in the language of the statement)

What 'IETF protocol specification' means here?=20

Pretty clear it covers protocols defined in IETF standards-track
documents.=20

Does it also cover protocols defined (described) in Informational RFCs
which are part of the IETF stream?=20

Dan


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of IETF Chair
> Sent: Monday, July 30, 2012 7:40 PM
> To: IETF Announce
> Cc: IETF
> Subject: Draft IESG Statement Regarding Ethertype Requests
>=20
> Last week the IAB and the IESG met with the leadership of IEEE 802.
One
> of the things that was discussed was the IEEE policies for allocating
> EtherTypes, and the IESG is considering the attached IESG Statement to
> implement an IETF policy that aligns with the IEEE policy.
>=20
> If you have an comments on this proposed policy, please raise them on
> ietf@ietf.org.
>=20
> Russ
>=20
> =3D =3D =3D =3D =3D =3D
>=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 an Ethertype to a
> new IETF protocol specification that needs a new Ethertype until the
> IESG has approved the 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.

From housley@vigilsec.com  Mon Jul 30 15:53:25 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2029121F85D8 for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 15:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9b9xOXJS8bK8 for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 15:53:24 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 3623F21F85FF for <ietf@ietf.org>; Mon, 30 Jul 2012 15:53:24 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9398CF24040; Mon, 30 Jul 2012 18:53:34 -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 cKMyV5cbSUQV; Mon, 30 Jul 2012 18:53:16 -0400 (EDT)
Received: from dhcp-55b9.meeting.ietf.org (dhcp-55b9.meeting.ietf.org [130.129.85.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D6ABEF2403B; Mon, 30 Jul 2012 18:53:30 -0400 (EDT)
Subject: Re: Draft IESG Statement Regarding Ethertype Requests
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0407E24097@307622ANEX5.global.avaya.com>
Date: Mon, 30 Jul 2012 18:53:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E526B78-44AD-44F3-A5FB-F42D3DBEE4B0@vigilsec.com>
References: <CDF73C59-A8E8-43B4-B67D-34CFAF541DB6@ietf.org> <EDC652A26FB23C4EB6384A4584434A0407E24097@307622ANEX5.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
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, 30 Jul 2012 22:53:25 -0000

Dan:

Only protocol specifications make use of Ethertypes.  The statement is =
intended to apply to any protocol specification on the IETF Stream =
(Standards Track RFC, Informational RFC, or Experimental RFC) that needs =
to allocate a new Ethertype.

Russ


On Jul 30, 2012, at 5:20 PM, Romascanu, Dan (Dan) wrote:

>=20
>=20
> (I hope not to open some Pandora box or a long thread - my goal is to
> make sure there is clarity in the language of the statement)
>=20
> What 'IETF protocol specification' means here?=20
>=20
> Pretty clear it covers protocols defined in IETF standards-track
> documents.=20
>=20
> Does it also cover protocols defined (described) in Informational RFCs
> which are part of the IETF stream?=20
>=20
> Dan
>=20
>=20
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of IETF Chair
>> Sent: Monday, July 30, 2012 7:40 PM
>> To: IETF Announce
>> Cc: IETF
>> Subject: Draft IESG Statement Regarding Ethertype Requests
>>=20
>> Last week the IAB and the IESG met with the leadership of IEEE 802.
> One
>> of the things that was discussed was the IEEE policies for allocating
>> EtherTypes, and the IESG is considering the attached IESG Statement =
to
>> implement an IETF policy that aligns with the IEEE policy.
>>=20
>> If you have an comments on this proposed policy, please raise them on
>> ietf@ietf.org.
>>=20
>> Russ
>>=20
>> =3D =3D =3D =3D =3D =3D
>>=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 an Ethertype to =
a
>> new IETF protocol specification that needs a new Ethertype until the
>> IESG has approved the 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.


From chair@ietf.org  Mon Jul 30 17:46:19 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 CB7D911E80BF; Mon, 30 Jul 2012 17:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6wNtchvGWn3X; Mon, 30 Jul 2012 17:46:19 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 5965511E80BA; Mon, 30 Jul 2012 17:46:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id F291112D7F5; Mon, 30 Jul 2012 17:46:19 -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 ckw2UP9iTrdx; Mon, 30 Jul 2012 17:46:19 -0700 (PDT)
Received: from [IPv6:2001:df8::80:6233:4bff:fe20:eb18] (unknown [IPv6:2001:df8:0:80:6233:4bff:fe20:eb18]) by c8a.amsl.com (Postfix) with ESMTPSA id BC1EE12D7F7; Mon, 30 Jul 2012 17:46:19 -0700 (PDT)
Subject: Open Internet Endowment Initial Campaign
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
X-Priority: 1 (Highest)
Date: Mon, 30 Jul 2012 20:46:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <04937337-1E47-4868-AF17-54DE98334D75@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 00:46:19 -0000

Today at IETF 84 in Vancouver, Lynn St. Amour and I announced the =
creation of the Open Internet Endowment and its initial campaign focused =
on ensuring the IETF's long-term financial health and continued =
independence. The web site is up and running.  It offers more =
information and accepts contributions.

	http://www.openinternetendowment.org

The Open Internet Endowment has been established by the Internet =
Society, with the support and direction of IETF leadership, based on =
discussions that have taken place over the past several years. This =
announcement is intended as a "family launch" to the IETF community. It =
gives our community an opportunity to be a "first supporter" of this =
effort.  The "family launch" will end when we make a public announcement =
in the near future.
=20
Please consider supporting this effort and making a donation today!
=20
Thanks for all you do for the Internet,
   Russ=

From barryleiba@gmail.com  Mon Jul 30 18:04:45 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 9DECC11E80EF for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 18:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.953
X-Spam-Level: 
X-Spam-Status: No, score=-102.953 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EbNEQs1PjA1n for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 18:04:45 -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 ED52611E80F2 for <ietf@ietf.org>; Mon, 30 Jul 2012 18:04:44 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id wy7so10658738pbc.31 for <ietf@ietf.org>; Mon, 30 Jul 2012 18:04:44 -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=5DZ/Am4MPWGeFK5CoQ3/P1N7SWB9rPfg/ZOPR3OGvIQ=; b=qz/oYdVpkVfxAqIYumpW3zXTKV9R58KXbHbf7EUcHjj3BAJXAZRIPtYd4ZxdQ3AJ/l HXJf1JdwMMX0pcq8e7C4xSsLJLOBb9rpozIBxpl8vaZepcEe/56FNIq4Ru2TqPsFo2OT JeWWyNlDxJIObZP2VauvSaf5V82iQFmnIiHrclKJ7EilNBA/M1MZiqXf08aKfmsRVJiw bDmB0SwwNjOc4SZ+vbsVLnBM+3NnkKQ4K6cBRea/LhOwlslrZY+B5XrkrXvk3MqGDF9C CKT5x9CnkMhjZbsG95LxruIHustSNee3bxJUHuObbqFh+v1szM2hBwQQpJLZYP1SsJ2q IMBQ==
MIME-Version: 1.0
Received: by 10.68.231.168 with SMTP id th8mr40318491pbc.14.1343696684843; Mon, 30 Jul 2012 18:04:44 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.68.64.103 with HTTP; Mon, 30 Jul 2012 18:04:44 -0700 (PDT)
In-Reply-To: <20120731005431.21591.33810.idtracker@ietfa.amsl.com>
References: <20120731005431.21591.33810.idtracker@ietfa.amsl.com>
Date: Mon, 30 Jul 2012 21:04:44 -0400
X-Google-Sender-Auth: gzecnkleAopd7HEvvB8qLKU3Tro
Message-ID: <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-00.txt
From: Barry Leiba <barryleiba@computer.org>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 01:04:45 -0000

I have just posted the draft cited below, to adjust the NomCom
eligibility rules to make the following change:

RFC 3777 excludes from eligibility as NomCom volunteers:
   - members of the ISOC Board of Trustees
   - "sitting members" of the IAB
   - "sitting members" of the IESG

The IAOC did not exist when that was written, and there are questions
about who, exactly, are "sitting members".

This draft excludes from eligibility as NomCom volunteers:
   - members of the ISOC Board of Trustees
   - "sitting members" of the IAB
   - "sitting members" of the IESG
   - "sitting members" of the IAOC

This draft clarifies that those exclusions:
   - DO include the ex-officio members
   - DO NOT include the liaisons (unless, of course, they're excluded
by another rule)

This draft also excludes from eligibility as NomCom volunteers paid employees:
   - the Secretariat
   - the RFC Editor

Comments, please.

Barry

> Filename:        draft-leiba-3777upd-eligibility
> Revision:        00
> Title:           Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership
> Creation date:   2012-07-30
> WG ID:           Individual Submission
> Number of pages: 4
> URL:             http://www.ietf.org/internet-drafts/draft-leiba-3777upd-eligibility-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility
> Htmlized:        http://tools.ietf.org/html/draft-leiba-3777upd-eligibility-00
>
>
> 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 d3e3e3@gmail.com  Mon Jul 30 19:18:37 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 324D311E8141 for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 19:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.515
X-Spam-Level: 
X-Spam-Status: No, score=-103.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egTyqMG2Bw6H for <ietf@ietfa.amsl.com>; Mon, 30 Jul 2012 19:18:36 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5597911E8140 for <ietf@ietf.org>; Mon, 30 Jul 2012 19:18:36 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so6002144ggn.31 for <ietf@ietf.org>; Mon, 30 Jul 2012 19:18: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:from:date:message-id:subject:to :cc:content-type; bh=R4FT5Rjc8mMMg4eMZe+TPpwOTHJgwv+aSV+LLPwNu40=; b=RJhrlKIFT2ZVHhZWWMowNQzJzquLOd4BBMmvLmI4ifRSZdH5bppSINPetatFZOvSr6 Zqr3wu0yDWxM+tJxWQDSplrrOs+py8mZOKCl++irF/VfnwJX/jSgl3+i6vThC6NLTSbG XKwVD06FaUTickoTarmJ4Ouyk6kIiDmS14WlmOZISs8j88nUJ7aDqMT8q4ojS+85CKmR 9dm7tUKDmZnsIdCBygHT7evwEkUbi6cFfeogw+AnEvEQGPEf/Z6p1W2kZP7Ms0mQjt91 /Sm13Ehxwgc4BcTe6iTSHGpuAL9O1V+Shj2NufpN6AD+y4W94n/XGS467Jx+KOLu/S/Q h8GQ==
Received: by 10.50.184.226 with SMTP id ex2mr567050igc.58.1343701115451; Mon, 30 Jul 2012 19:18:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.70.227 with HTTP; Mon, 30 Jul 2012 19:18:15 -0700 (PDT)
In-Reply-To: <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com>
References: <20120731005431.21591.33810.idtracker@ietfa.amsl.com> <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 30 Jul 2012 22:18:15 -0400
Message-ID: <CAF4+nEEYKD4TEKrv1sg=1wG+YJ=ZLtEOg_nNHx6k=-0C71-KkA@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-00.txt
To: Barry Leiba <barryleiba@computer.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: Tue, 31 Jul 2012 02:18:37 -0000

Sees reasonable. While you are at it, you might complete the I* with IANA...

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Mon, Jul 30, 2012 at 9:04 PM, Barry Leiba <barryleiba@computer.org> wrote:
> I have just posted the draft cited below, to adjust the NomCom
> eligibility rules to make the following change:
>
> RFC 3777 excludes from eligibility as NomCom volunteers:
>    - members of the ISOC Board of Trustees
>    - "sitting members" of the IAB
>    - "sitting members" of the IESG
>
> The IAOC did not exist when that was written, and there are questions
> about who, exactly, are "sitting members".
>
> This draft excludes from eligibility as NomCom volunteers:
>    - members of the ISOC Board of Trustees
>    - "sitting members" of the IAB
>    - "sitting members" of the IESG
>    - "sitting members" of the IAOC
>
> This draft clarifies that those exclusions:
>    - DO include the ex-officio members
>    - DO NOT include the liaisons (unless, of course, they're excluded
> by another rule)
>
> This draft also excludes from eligibility as NomCom volunteers paid employees:
>    - the Secretariat
>    - the RFC Editor
>
> Comments, please.
>
> Barry
>
>> Filename:        draft-leiba-3777upd-eligibility
>> Revision:        00
>> Title:           Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership
>> Creation date:   2012-07-30
>> WG ID:           Individual Submission
>> Number of pages: 4
>> URL:             http://www.ietf.org/internet-drafts/draft-leiba-3777upd-eligibility-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-leiba-3777upd-eligibility
>> Htmlized:        http://tools.ietf.org/html/draft-leiba-3777upd-eligibility-00
>>
>>
>> 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 hartmans@mit.edu  Tue Jul 31 02:42:03 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 14D9D21F86C6 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 02:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.516
X-Spam-Level: 
X-Spam-Status: No, score=-99.516 tagged_above=-999 required=5 tests=[AWL=-3.804, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M9-FzNKG7CK2 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 02:42:02 -0700 (PDT)
Received: from ec2-23-21-76-251.compute-1.amazonaws.com (ec2-23-21-76-251.compute-1.amazonaws.com [23.21.76.251]) by ietfa.amsl.com (Postfix) with ESMTP id 9ABB021F86BE for <ietf@ietf.org>; Tue, 31 Jul 2012 02:42:02 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (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 99B0420155; Tue, 31 Jul 2012 05:41:26 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 26AF243C6; Tue, 31 Jul 2012 05:41:58 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-00.txt
References: <20120731005431.21591.33810.idtracker@ietfa.amsl.com> <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com> <CAF4+nEEYKD4TEKrv1sg=1wG+YJ=ZLtEOg_nNHx6k=-0C71-KkA@mail.gmail.com>
Date: Tue, 31 Jul 2012 05:41:58 -0400
In-Reply-To: <CAF4+nEEYKD4TEKrv1sg=1wG+YJ=ZLtEOg_nNHx6k=-0C71-KkA@mail.gmail.com> (Donald Eastlake's message of "Mon, 30 Jul 2012 22:18:15 -0400")
Message-ID: <tsllii01d3t.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: Barry Leiba <barryleiba@computer.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, 31 Jul 2012 09:42:03 -0000

I'd probably also recommend excluding paid employees of ISOC. I cannot
really think of rationale that applies to the secretariat staff but not
ISOC.

From sm@resistor.net  Tue Jul 31 03:01: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 9B28B21F8495 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 03:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.077
X-Spam-Level: 
X-Spam-Status: No, score=-102.077 tagged_above=-999 required=5 tests=[AWL=-0.470, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g4SwoSe4sdZW for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 03:01: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 5E61621F86D0 for <ietf@ietf.org>; Tue, 31 Jul 2012 03:01:13 -0700 (PDT)
Received: from sm-THINK.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 q6VA11Li017310; Tue, 31 Jul 2012 03:01:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1343728868; bh=DlQeVWPFjNlB3GDzns9RVYXfeK/8SUQFTBiBCdJ8DNk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=T6HT2RZNbHUJjDWHIv9G9eXXzjDM4BNvASMll4wWDOnSqhF2le9zCJtf845rpcqmO UHHAQ0AJ/0rZqIeSatMFd7RTnxZ7jcfzj/itWKiuQ6c1wpTkhwenhNCvFMDq0kkcQG RLRqzERkkQWXu9aocRzNsCjccRTO3jEeBFklBwKk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1343728868; i=@resistor.net; bh=DlQeVWPFjNlB3GDzns9RVYXfeK/8SUQFTBiBCdJ8DNk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=O9pVChV6d0m/992aidKKf9DrcelFfJDbcXJRev13wnzL8TD0bPP/Y/Rd77y72MBxP JPNMnklItaLulPHpNUJ5BU88qGCJfQOeQnf5G+rzwv21S+Zz4XYLGfanhd+IY8jtgT gdDbkvE5MR7zN8e0fysvafDGMu9Q8kbmCBMokR2I=
Message-Id: <6.2.5.6.2.20120730101231.047f2550@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 30 Jul 2012 10:21:48 -0700
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
From: SM <sm@resistor.net>
Subject: Re: Oauth blog post
In-Reply-To: <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net>
References: <501531F7.5040404@gmail.com> <6.2.5.6.2.20120729073422.06d8fe10@resistor.net> <39B73AD9-4E8F-4E94-A538-69BE5D8C0E18@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 10:01:15 -0000

Hi Hannes,
At 12:19 PM 7/29/2012, Hannes Tschofenig wrote:
>The IETF allows open participation and, as such, everyone, including 
>companies that develop enterprise software, are free to participate 
>in the discussions.
>
>Do you think open participation is wrong?

It depends on what open participation means in the above.  If it is 
open participation by companies, I don't have any problem with it as 
long as the relevant BCPs are updated to reflect that.

At 11:14 AM 7/29/2012, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
>I would find it useful if anyone of you who likes to agree or 
>disagree to have at least read the OAuth specification. I had 
>noticed that many of those who share their valuable thoughts have 
>not even spent the time to look at the document.

I wonder whether I read the OAuth2 specifications. :-)

Regards,
-sm  


From loa@pi.nu  Tue Jul 31 03:40: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 C9E9121F8568 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 03:40:15 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C8wIfvHpmNss for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 03:40:15 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id B34C421F8567 for <ietf@ietf.org>; Tue, 31 Jul 2012 03:40: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 EADCB2A8003; Tue, 31 Jul 2012 12:40:12 +0200 (CEST)
Message-ID: <5017B60D.5050101@pi.nu>
Date: Tue, 31 Jul 2012 12:40:13 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Scott O Bradner <sob@sobco.com>
Subject: Re: I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com> <50164E21.2040904@gmail.com> <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com>
In-Reply-To: <225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2012 10:40:16 -0000

Scott,

would you say that drafts aimed for experimental status are "standards
work".

/Loa

On 2012-07-30 18:33, Scott O Bradner wrote:
> 2804 does not say not to talk about such things - or that such documents should
> not be published as RFCs  - 2804 says that the IETF will not do standards work
> in this area
>
> Scott
>
> On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:
>
>> Under the long-standing IETF policy defined in RFC 2804, I trust
>> we will not be discussing this draft, or
>> draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
>>
>> Regards
>>    Brian Carpenter
>>
>> On 30/07/2012 09:26, internet-drafts@ietf.org wrote:
>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>
>>>
>>> 	Title           : Label-based Provider-Provisioned Lawful Intercept for L3 VPNs
>>> 	Author(s)       : Shankar Raman
>>>                           Balaji Venkat Venkataswami
>>>                           Gaurav Raina
>>>                           Vasan Srini
>>>                           Bhargav Bhikkaji
>>> 	Filename        : draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
>>> 	Pages           : 12
>>> 	Date            : 2012-07-30
>>>
>>> Abstract:
>>>    In models of Single-AS and inter-provider Multi- Protocol Label
>>>    Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
>>>    Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
>>>    models like VPLS and the like do not have any provider provisioned
>>>    methods of lawful intercept that are comprehensive, quick and easy to
>>>    provision from one single point. More particularly the auto-
>>>    provisioning of lawful intercept for all sets of streams travelling
>>>    between VPN sites and consequent re-direction of these streams to the
>>>    appropriate government network has not been covered without multiple
>>>    instances of having to configure the intercept at various points in
>>>    the network both in the Single-AS case and the Inter-Provider VPN
>>>    case.
>>>
>>>    this paper, we propose a technique which uses a set of pre-defined
>>>    labels called Lawful Intercept labels and a method for provisioning
>>>    lawful intercept amongst the various PE devices using these labels
>>>    both in the Single-AS and the inter-provider VPN cases. A single
>>>    point of configuration is the key to this idea. The intercepted
>>>    traffic is mirrored on a PE or a whole set of PEs or on all the PEs
>>>    participating in the VPN. A technique called the Domino-effect
>>>    provisioning of these Label-based Provider Provisioned Lawful
>>>    Intercept mechanism is also outlined.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-label-dis
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-dis-00
>>>
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>
>

-- 


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 brian.e.carpenter@gmail.com  Tue Jul 31 04:14:08 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACCA21F86BD for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 04:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.383
X-Spam-Level: 
X-Spam-Status: No, score=-103.383 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HyLLIOvNpP5h for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 04:14:07 -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 4AD9621F8559 for <ietf@ietf.org>; Tue, 31 Jul 2012 04:14:07 -0700 (PDT)
Received: by eaaa11 with SMTP id a11so1390706eaa.31 for <ietf@ietf.org>; Tue, 31 Jul 2012 04:14:06 -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=QUG35toM/55YkdmB1VgEwo/PSHRaERZqB0KGYoc1Y4M=; b=pn/Hcel1oZXv3M+7jL0iRQtYvvYUNWVBdmIXhe6SujXqGKxwBTkT6hSM/bXQn0hP9Y roY/WnrPWmWWZ/prpj9v/BB9gepfQqrgJibmu9SeqQ2jmSrp49xH/6BVN037tZGLYi/1 /2YfFpdC2LjY5NI9v7Rqb4bBgRlEYOPfqWo5dVAIv/BGdcFw85g3CIxxRMAd27p5tXzc bbR6g9xJ1d13tyi72jmiziLi6DdK4EBo51j5gxTYcOvnsMkAWHLOGpifsL5x2PcMMNRs 6i9Zlg7UzvAiiIx6r61H6nYJQ1QJdpL9ESH2sWDlFDYyUtUmw34680OtTPjYXlQWTHOk UIvQ==
Received: by 10.14.182.134 with SMTP id o6mr2495702eem.26.1343733246431; Tue, 31 Jul 2012 04:14:06 -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 g46sm35882372eep.15.2012.07.31.04.14.04 (version=SSLv3 cipher=OTHER); Tue, 31 Jul 2012 04:14:05 -0700 (PDT)
Message-ID: <5017BDFE.5020100@gmail.com>
Date: Tue, 31 Jul 2012 12:14:06 +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: Loa Andersson <loa@pi.nu>
Subject: Re: I-D Action:	draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com>	<50164E21.2040904@gmail.com>	<225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com> <5017B60D.5050101@pi.nu>
In-Reply-To: <5017B60D.5050101@pi.nu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>, Scott O Bradner <sob@sobco.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, 31 Jul 2012 11:14:08 -0000

Loa,

I can't speak for Scott, but I think the problem arises if any
IANA assignments are needed, regardless of RFC status. That's
because RFC 2804 speaks of "the process for creating and maintaining
IETF standards." IANA assignments are part of standards maintenance
(IMHO, of course).

Don't forget that 2804 *also* says

"  - On the other hand, the IETF believes that mechanisms designed to
     facilitate or enable wiretapping, or methods of using other
     facilities for such purposes, should be openly described, so as to
     ensure the maximum review of the mechanisms and ensure that they
     adhere as closely as possible to their design constraints. The IETF
     believes that the publication of such mechanisms, and the
     publication of known weaknesses in such mechanisms, is a Good
     Thing."

So it's a delicate balance.

    Brian

On 31/07/2012 11:40, Loa Andersson wrote:
> Scott,
> 
> would you say that drafts aimed for experimental status are "standards
> work".
> 
> /Loa
> 
> On 2012-07-30 18:33, Scott O Bradner wrote:
>> 2804 does not say not to talk about such things - or that such
>> documents should
>> not be published as RFCs  - 2804 says that the IETF will not do
>> standards work
>> in this area
>>
>> Scott
>>
>> On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:
>>
>>> Under the long-standing IETF policy defined in RFC 2804, I trust
>>> we will not be discussing this draft, or
>>> draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
>>>
>>> Regards
>>>    Brian Carpenter
>>>
>>> On 30/07/2012 09:26, internet-drafts@ietf.org wrote:
>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>> directories.
>>>>
>>>>
>>>>     Title           : Label-based Provider-Provisioned Lawful
>>>> Intercept for L3 VPNs
>>>>     Author(s)       : Shankar Raman
>>>>                           Balaji Venkat Venkataswami
>>>>                           Gaurav Raina
>>>>                           Vasan Srini
>>>>                           Bhargav Bhikkaji
>>>>     Filename        :
>>>> draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
>>>>     Pages           : 12
>>>>     Date            : 2012-07-30
>>>>
>>>> Abstract:
>>>>    In models of Single-AS and inter-provider Multi- Protocol Label
>>>>    Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
>>>>    Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
>>>>    models like VPLS and the like do not have any provider provisioned
>>>>    methods of lawful intercept that are comprehensive, quick and
>>>> easy to
>>>>    provision from one single point. More particularly the auto-
>>>>    provisioning of lawful intercept for all sets of streams travelling
>>>>    between VPN sites and consequent re-direction of these streams to
>>>> the
>>>>    appropriate government network has not been covered without multiple
>>>>    instances of having to configure the intercept at various points in
>>>>    the network both in the Single-AS case and the Inter-Provider VPN
>>>>    case.
>>>>
>>>>    this paper, we propose a technique which uses a set of pre-defined
>>>>    labels called Lawful Intercept labels and a method for provisioning
>>>>    lawful intercept amongst the various PE devices using these labels
>>>>    both in the Single-AS and the inter-provider VPN cases. A single
>>>>    point of configuration is the key to this idea. The intercepted
>>>>    traffic is mirrored on a PE or a whole set of PEs or on all the PEs
>>>>    participating in the VPN. A technique called the Domino-effect
>>>>    provisioning of these Label-based Provider Provisioned Lawful
>>>>    Intercept mechanism is also outlined.
>>>>
>>>>
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-label-dis
>>>>
>>>>
>>>> There's also a htmlized version available at:
>>>> http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-dis-00
>>>>
>>>>
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> _______________________________________________
>>>> I-D-Announce mailing list
>>>> I-D-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>
>>
> 

From john-ietf@jck.com  Tue Jul 31 05:49:25 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 C2FB421F8620 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 05:49:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yfyycnxLEzxN for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 05:49:25 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 151EA21F85D5 for <ietf@ietf.org>; Tue, 31 Jul 2012 05:49:25 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SwBnM-000CQB-Kp; Tue, 31 Jul 2012 08:43:28 -0400
Date: Tue, 31 Jul 2012 08:48:19 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-00.txt
Message-ID: <C4DFC40DF886B4A5E4B10B2A@7AD4D3FB4841A5E367CCF211>
In-Reply-To: <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com>
References: <20120731005431.21591.33810.idtracker@ietfa.amsl.com> <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 12:49:25 -0000

--On Monday, 30 July, 2012 21:04 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

> I have just posted the draft cited below, to adjust the NomCom
> eligibility rules to make the following change:
>...
> This draft also excludes from eligibility as NomCom volunteers
> paid employees:
>    - the Secretariat
>    - the RFC Editor

Barry,

I'll try to avoid going over the top this time (as I told you in
person, the "exclude WG Chairs" suggestion was entirely to
promote discussion rather than a proposal), but...

If one wants to exclude the Secretariat and RFC Editor staff --
presumably on the basis that they are appointed by, and draw
their salaries from, bodies partially appointed by the Nomcom --
then it seems to me that:

(1) You should explicitly exclude the IAD (for completeness of
the list and to avoid debate about whether he is already
excluded by the "sitting member" and/or "ex-officio" rules for
the IAOC.

(2) You should exclude anyone from the pool who has bid on or
held an IAOC-awarded contract in some period of time (I would
suggest a year) or who has bid on such a contract during that
period.  Anyone who actually serves on the Nomcom should also be
excluded from bidding on any such contract during their Nomcom
terms and perhaps for a year (or more?) thereafter.   

Much of this is about appearances.   For example, I would hope
that sitting ADs would have better sense than to volunteer for
the Nomcom even if the rules technically permitted that.  Nor
would I expect Secretariat staff to volunteer (as far as I know,
none ever has despite the current rules apparently permitting
that).    But relatively short-term contractors are presumably
no different from the Secretariat in either the award or
management processes and the potential for patronage and
cronyism are actually much greater.

   john


From john-ietf@jck.com  Tue Jul 31 06:43:24 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 181AE21F86B6 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 06:43: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gtrQNrTp53yg for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 06:43:23 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 907F421F86B4 for <ietf@ietf.org>; Tue, 31 Jul 2012 06:43:23 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SwCdY-000CWA-VI; Tue, 31 Jul 2012 09:37:25 -0400
Date: Tue, 31 Jul 2012 09:43:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-00.txt
Message-ID: <7DBE67ABAE8620D11EE70AD6@JCK-EEE10>
In-Reply-To: <tsllii01d3t.fsf@mit.edu>
References: <20120731005431.21591.33810.idtracker@ietfa.amsl.com> <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com> <CAF4+nEEYKD4TEKrv1sg=1wG+YJ=ZLtEOg_nNHx6k=-0C71-KkA@mail.gmail.com> <tsllii01d3t.fsf@mit.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: Barry Leiba <barryleiba@computer.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, 31 Jul 2012 13:43:24 -0000

--On Tuesday, 31 July, 2012 05:41 -0400 Sam Hartman
<hartmans-ietf@mit.edu> wrote:

> I'd probably also recommend excluding paid employees of ISOC.
> I cannot really think of rationale that applies to the
> secretariat staff but not ISOC.

There is one, which is that the IETF and its leadership bodies
have just about zero influence over the recruitment and hiring
of those people.  But that same comment applies to IANA staff
(as distinct from the Secretariat).   We don't hire them, we
don't pay them, no money passes (in either direction) between
ICANN/IANA and the IASA/IETF, etc.

In theory, we could "designate" some other entity as the IANA,
which might or might not cost some current IANA staff their
jobs.   But there are questions about how realistic that is (not
part of this discussion).  We certainly cannot fire ISOC and,
given their charter, it isn't clear they could fire us.  If they
could, they'd have to fire the entire IETF, not individuals.  I
suppose one could argue that ISOC staff might have undue
influence on the behavior of the ISOC BoT as a confirming body,
but I find that really dubious.

    john


From smb@cs.columbia.edu  Tue Jul 31 07:30:14 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 5322621F85C7 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 07:30: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=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZM1cuchpQJzl for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 07:30:13 -0700 (PDT)
Received: from rambutan.cc.columbia.edu (rambutan.cc.columbia.edu [128.59.29.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4994421F85C3 for <ietf@ietf.org>; Tue, 31 Jul 2012 07:30:13 -0700 (PDT)
Received: from [10.9.0.66] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by rambutan.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q6VEU8wA023699 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 31 Jul 2012 10:30:09 -0400 (EDT)
Subject: Re: I-D Action:	draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <5017BDFE.5020100@gmail.com>
Date: Tue, 31 Jul 2012 07:30:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D0D2246-86C9-4561-9EE9-3249DA7BAFF5@cs.columbia.edu>
References: <20120730082620.18701.51607.idtracker@ietfa.amsl.com>	<50164E21.2040904@gmail.com>	<225158E4-78BC-42BC-8339-EB9E0DE75AA7@sobco.com> <5017B60D.5050101@pi.nu> <5017BDFE.5020100@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1278)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.5
Cc: IETF discussion list <ietf@ietf.org>, Scott O Bradner <sob@sobco.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, 31 Jul 2012 14:30:14 -0000

Also note that RFC 3924 exists.

On Jul 31, 2012, at 4:14 AM, Brian E Carpenter wrote:

> Loa,
>=20
> I can't speak for Scott, but I think the problem arises if any
> IANA assignments are needed, regardless of RFC status. That's
> because RFC 2804 speaks of "the process for creating and maintaining
> IETF standards." IANA assignments are part of standards maintenance
> (IMHO, of course).
>=20
> Don't forget that 2804 *also* says
>=20
> "  - On the other hand, the IETF believes that mechanisms designed to
>     facilitate or enable wiretapping, or methods of using other
>     facilities for such purposes, should be openly described, so as to
>     ensure the maximum review of the mechanisms and ensure that they
>     adhere as closely as possible to their design constraints. The =
IETF
>     believes that the publication of such mechanisms, and the
>     publication of known weaknesses in such mechanisms, is a Good
>     Thing."
>=20
> So it's a delicate balance.
>=20
>    Brian
>=20
> On 31/07/2012 11:40, Loa Andersson wrote:
>> Scott,
>>=20
>> would you say that drafts aimed for experimental status are =
"standards
>> work".
>>=20
>> /Loa
>>=20
>> On 2012-07-30 18:33, Scott O Bradner wrote:
>>> 2804 does not say not to talk about such things - or that such
>>> documents should
>>> not be published as RFCs  - 2804 says that the IETF will not do
>>> standards work
>>> in this area
>>>=20
>>> Scott
>>>=20
>>> On Jul 30, 2012, at 5:04 AM, Brian E Carpenter wrote:
>>>=20
>>>> Under the long-standing IETF policy defined in RFC 2804, I trust
>>>> we will not be discussing this draft, or
>>>> draft-balaji-l2vpn-lawful-intercept-thru-label-dis, in the IETF.
>>>>=20
>>>> Regards
>>>>   Brian Carpenter
>>>>=20
>>>> On 30/07/2012 09:26, internet-drafts@ietf.org wrote:
>>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>>> directories.
>>>>>=20
>>>>>=20
>>>>>    Title           : Label-based Provider-Provisioned Lawful
>>>>> Intercept for L3 VPNs
>>>>>    Author(s)       : Shankar Raman
>>>>>                          Balaji Venkat Venkataswami
>>>>>                          Gaurav Raina
>>>>>                          Vasan Srini
>>>>>                          Bhargav Bhikkaji
>>>>>    Filename        :
>>>>> draft-balaji-mpls-lawful-intercept-thru-label-dis-00.txt
>>>>>    Pages           : 12
>>>>>    Date            : 2012-07-30
>>>>>=20
>>>>> Abstract:
>>>>>   In models of Single-AS and inter-provider Multi- Protocol Label
>>>>>   Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
>>>>>   Intercept is a key requirement. For example, MPLS-based Layer 3 =
VPN
>>>>>   models like VPLS and the like do not have any provider =
provisioned
>>>>>   methods of lawful intercept that are comprehensive, quick and
>>>>> easy to
>>>>>   provision from one single point. More particularly the auto-
>>>>>   provisioning of lawful intercept for all sets of streams =
travelling
>>>>>   between VPN sites and consequent re-direction of these streams =
to
>>>>> the
>>>>>   appropriate government network has not been covered without =
multiple
>>>>>   instances of having to configure the intercept at various points =
in
>>>>>   the network both in the Single-AS case and the Inter-Provider =
VPN
>>>>>   case.
>>>>>=20
>>>>>   this paper, we propose a technique which uses a set of =
pre-defined
>>>>>   labels called Lawful Intercept labels and a method for =
provisioning
>>>>>   lawful intercept amongst the various PE devices using these =
labels
>>>>>   both in the Single-AS and the inter-provider VPN cases. A single
>>>>>   point of configuration is the key to this idea. The intercepted
>>>>>   traffic is mirrored on a PE or a whole set of PEs or on all the =
PEs
>>>>>   participating in the VPN. A technique called the Domino-effect
>>>>>   provisioning of these Label-based Provider Provisioned Lawful
>>>>>   Intercept mechanism is also outlined.
>>>>>=20
>>>>>=20
>>>>> The IETF datatracker status page for this draft is:
>>>>> =
https://datatracker.ietf.org/doc/draft-balaji-mpls-lawful-intercept-thru-l=
abel-dis
>>>>>=20
>>>>>=20
>>>>> There's also a htmlized version available at:
>>>>> =
http://tools.ietf.org/html/draft-balaji-mpls-lawful-intercept-thru-label-d=
is-00
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>=20
>>>>> _______________________________________________
>>>>> I-D-Announce mailing list
>>>>> I-D-Announce@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>>=20
>>>=20
>>=20
>=20


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






From randy@psg.com  Tue Jul 31 09: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 43FEB21F8567 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 09:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XW+HHPKuMmgG for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 09: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 DC50421F8566 for <ietf@ietf.org>; Tue, 31 Jul 2012 09: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.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1SwF6X-000Pge-Q1; Tue, 31 Jul 2012 16:15:29 +0000
Date: Tue, 31 Jul 2012 09:15:28 -0700
Message-ID: <m2vch3sy8v.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-00.txt
In-Reply-To: <tsllii01d3t.fsf@mit.edu>
References: <20120731005431.21591.33810.idtracker@ietfa.amsl.com> <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com> <CAF4+nEEYKD4TEKrv1sg=1wG+YJ=ZLtEOg_nNHx6k=-0C71-KkA@mail.gmail.com> <tsllii01d3t.fsf@mit.edu>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: Barry Leiba <barryleiba@computer.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, 31 Jul 2012 16:15:35 -0000

> I'd probably also recommend excluding paid employees of ISOC. I cannot
> really think of rationale that applies to the secretariat staff but
> not ISOC.

perhaps we should take the leap of assuming folk are adults here (i
realize it is a stretch), and not start a black-list with no proof of
termination.

randy

From joelja@bogus.com  Tue Jul 31 09:38:54 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 3F7C221F8679 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 09:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zo2Dk-R4CBSo for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 09:38:53 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 4347A21F8671 for <ietf@ietf.org>; Tue, 31 Jul 2012 09:38:53 -0700 (PDT)
Received: from dhcp-6624.meeting.ietf.org (dhcp-6624.meeting.ietf.org [130.129.102.36]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q6VGclxW029255 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 31 Jul 2012 16:38:47 GMT (envelope-from joelja@bogus.com)
Message-ID: <50180A18.2090008@bogus.com>
Date: Tue, 31 Jul 2012 09:38:48 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120717 Thunderbird/15.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: New Version Notification for	draft-leiba-3777upd-eligibility-00.txt
References: <20120731005431.21591.33810.idtracker@ietfa.amsl.com> <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com> <CAF4+nEEYKD4TEKrv1sg=1wG+YJ=ZLtEOg_nNHx6k=-0C71-KkA@mail.gmail.com> <tsllii01d3t.fsf@mit.edu> <m2vch3sy8v.wl%randy@psg.com>
In-Reply-To: <m2vch3sy8v.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.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 31 Jul 2012 16:38:47 +0000 (UTC)
Cc: Barry Leiba <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 16:38:54 -0000

On 7/31/12 9:15 AM, Randy Bush wrote:
>> I'd probably also recommend excluding paid employees of ISOC. I cannot
>> really think of rationale that applies to the secretariat staff but
>> not ISOC.
> perhaps we should take the leap of assuming folk are adults here (i
> realize it is a stretch), and not start a black-list with no proof of
> termination.
One imagines an ISOC employee participating in the IETF activity on the 
same basis as everyone else who participates in the IETF activity, as 
individuals. if their role is covered by an ex officio office exclusion 
that seems sufficient.
> randy
>


From davidb@verisign.com  Mon Jul 30 13:31:13 2012
Return-Path: <davidb@verisign.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B195411E8163; Mon, 30 Jul 2012 13:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gyVP6L9mU55i; Mon, 30 Jul 2012 13:31:13 -0700 (PDT)
Received: from exprod6og102.obsmtp.com (exprod6og102.obsmtp.com [64.18.1.183]) by ietfa.amsl.com (Postfix) with ESMTP id 1701311E8133; Mon, 30 Jul 2012 13:31:01 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob102.postini.com ([64.18.5.12]) with SMTP ID DSNKUBbvBS3GDgnPkJ9RoxJeKOZ64e2FUqVa@postini.com; Mon, 30 Jul 2012 13:31:12 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id q6UKUobn024875 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 30 Jul 2012 16:30:51 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0247.003; Mon, 30 Jul 2012 16:30:51 -0400
From: "Blacka, David" <davidb@verisign.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Subject: Re: [dnsext] Gen-ART review of draft-ietf-dnsext-dnssec-bis-updates-18
Thread-Topic: [dnsext] Gen-ART review of draft-ietf-dnsext-dnssec-bis-updates-18
Thread-Index: AQHNTcEBiArox8QTa0KZinofYFCgT5dCliyAgAA1yYA=
Date: Mon, 30 Jul 2012 20:30:49 +0000
Message-ID: <DA020552-9B8C-45FF-8D89-41894D2C4410@verisign.com>
References: <EBFB2D2E-78FF-46D6-B4FF-1F57FB8D769B@bbn.com> <20120619021211.GI32683@crankycanuck.ca> <9A7F5D7E-C3A8-4118-ADA1-C9CB814CDF72@bbn.com>
In-Reply-To: <9A7F5D7E-C3A8-4118-ADA1-C9CB814CDF72@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <69AE58FA13615E4B8B754C07B1BF039F@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 31 Jul 2012 09:56:17 -0700
Cc: "<draft-ietf-dnsext-dnssec-bis-updates@tools.ietf.org>" <draft-ietf-dnsext-dnssec-bis-updates@tools.ietf.org>, IESG <iesg@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>, "<dnsext@ietf.org>" <dnsext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Jul 2012 20:31:13 -0000

On Jul 30, 2012, at 1:18 PM, Richard L. Barnes wrote:

>>>=20
>>> MAJOR:
>>>=20
>>> 4.1. =20
>>> It's not clear what the threat model is that this section is
>>> designed to address.  If the zone operator is malicious, then it can
>>> simulate the necessary zone cut and still prove the non-existence of
>>> records in the child zone.
>>=20
>> The problem here is not a malicious parent operator, but "an NSEC or
>> NSEC3 RR from an ancestor zone".  In the original specification, an
>> attacker could use such an RR to prove the non-existence of some name
>> in a subordinate zone.  That was the problem.  (Remember, in DNS there
>> is a good chance that you are not talking to an authoritative server.)
>> If you have suggestions on ways to make that clearer, it'd be welcome.
>> The editors tried to come up with compact examples that would be
>> anything other than mystifying, and were unsuccessful. =20
>=20
> I guess I still don't understand this.  Aren't ancestors the only people =
that can generate a valid, signed NSEC or NSEC3 RR?  So if there were a bad=
 NSEC[3], wouldn't it be the ancestor's fault?

This isn't about "bad NSEC[3]" RRs.  It is about an attacker (think "man-in=
-the-middle") using the valid, completely correct NSEC[3] RR from the paren=
t zone in an inappropriate context.

> If the provisioning is *intentional*, then as I noted before, then there'=
s not really anything to be done, since the ancestor can provide whatever i=
nformation he wants for the child zones (as above).  So are you worried abo=
ut *inadvertent* provisioning of these bad records? =20

Again, the record isn't "bad", but being used in the wrong context (either =
via a software bug or on purpose as an attack).  This section isn't about m=
alicious zone operators at all.

I still don't have any great ideas for how to change the text to make this =
more clear, however.

--
David Blacka                          <davidb@verisign.com>=20
Principal               Verisign Infrastructure Engineering





From ned+ietf@mauve.mrochek.com  Tue Jul 31 10:29:37 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 AD37621F87ED for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 10:29:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TZ6yuwFSbrv7 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 10:29:37 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0F69E21F87E9 for <ietf@ietf.org>; Tue, 31 Jul 2012 10:29:37 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OIHVRCILQ8006AZL@mauve.mrochek.com> for ietf@ietf.org; Tue, 31 Jul 2012 10:24:32 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OIGH28IS2O0006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 31 Jul 2012 10:24:27 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OIHVR9FZ6E0006TF@mauve.mrochek.com>
Date: Tue, 31 Jul 2012 10:23:11 -0700 (PDT)
Subject: Re: New Version Notification	for	draft-leiba-3777upd-eligibility-00.txt
In-reply-to: "Your message dated Tue, 31 Jul 2012 09:15:28 -0700" <m2vch3sy8v.wl%randy@psg.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120731005431.21591.33810.idtracker@ietfa.amsl.com> <CALaySJJhKW7Nu46MfoFpavTUM311_yDmeczw=14V-KPXLafbcw@mail.gmail.com> <CAF4+nEEYKD4TEKrv1sg=1wG+YJ=ZLtEOg_nNHx6k=-0C71-KkA@mail.gmail.com> <tsllii01d3t.fsf@mit.edu> <m2vch3sy8v.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Cc: Barry Leiba <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 17:29:37 -0000

> > I'd probably also recommend excluding paid employees of ISOC. I cannot
> > really think of rationale that applies to the secretariat staff but
> > not ISOC.

> perhaps we should take the leap of assuming folk are adults here (i
> realize it is a stretch), and not start a black-list with no proof of
> termination.

+1 on all points, including the stretch part.

				Ned

P.S. I'm not a big fan of "for appearance's sake". All too often it proves to
be a path to madness.

From ole@cisco.com  Tue Jul 31 11:16:31 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C9B321F88DA for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 11:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.471
X-Spam-Level: 
X-Spam-Status: No, score=-110.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uPd8HYHW9hFr for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 11:16:30 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 64DD321F88A2 for <ietf@ietf.org>; Tue, 31 Jul 2012 11:16:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1475; q=dns/txt; s=iport; t=1343758590; x=1344968190; h=date:from:reply-to:to:cc:subject:message-id:mime-version; bh=UBLR7ac0hOrFEbDgwv1uOhIKxALFXJZp6pwMrSPl5MQ=; b=Y6q40ll06o+FEWh1yR2ZP4loI3LzZtjm9g7nvB74/jqdmgJ5uw+JV/kZ wWYBm5JxsZBMgLDX4UE25MdGUON1CU/aNqwvcJto4/0ErV6EyCmL/YT+u iGJPcznNsMdLZzT5ZfNkVl9GVmPXmby3LiIfW7Mpy92IjJfnzMCX3C2HR Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAE4gGFCrRDoG/2dsb2JhbABCA7l6gQeCOQECJT+BPhMih2oMnAKDSBCBTptNi2ODToMhA4hNjg6ER4UygxqBBGKCf4E/
X-IronPort-AV: E=Sophos;i="4.77,688,1336348800"; d="scan'208";a="53587708"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 31 Jul 2012 18:16:30 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q6VIGTHK021774; Tue, 31 Jul 2012 18:16:29 GMT
Date: Tue, 31 Jul 2012 11:16:33 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: The IETF <ietf@ietf.org>
Subject: RFC and I-D Citation Tool
Message-ID: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: RSOC <rsoc@iab.org>, Heather Flanagan <hlflanagan@gmail.com>, rsag@rfc-editor.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 18:16:31 -0000

In The Internet Protocol Journal I have been using the following 
citation format, best illustrated by an example:

 Julien Meuric, Diego Caviglia, Don Fedyk, Attila Takacs, and Lou 
 Berger, "GMPLS Asymmetric Bandwidth Bidirectional Label Switched 
 Paths (LSPs)," RFC 6387, September 2011.

So, that's full author names "and" before the last author name, title, 
document number and date, using the American "quotation outside 
punctuation rule."

I got tired of doing this "by hand" so I asked Henrik if he could 
write me a tool. He did (THANKS!), and the result is here:

http://tools.ietf.org/tools/citation/

This will take either the draft name or the RFC number as input and 
produce a citation similar to the one above. You can of course play 
with the elements and generate a format that suits your own taste, for 
example, for I-Ds, in print it might be good to have the FILE NAME as 
the last entry:

 Adam Langley, "Serializing DNS Records with DNSSEC Authentication," 
 Internet Draft, work in progress, July 2011,
 draft-agl-dane-serializechain-01

...since I like having filenames or URLs on one line (not wrapping)
as much as possible.

Many thanks again to Henrik, and I hope you will find it useful too!

Ole



Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


From marc.blanchet@viagenie.ca  Tue Jul 31 11:17:46 2012
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E25221F88D6 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 11:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1KvRkHPFbwxN for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 11:17:45 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 9F7BA21F869E for <ietf@ietf.org>; Tue, 31 Jul 2012 11:17:45 -0700 (PDT)
Received: from [IPv6:2001:df8::64:7828:6a15:2b28:1571] (unknown [IPv6:2001:df8:0:64:7828:6a15:2b28:1571]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 9163E41364; Tue, 31 Jul 2012 14:17:44 -0400 (EDT)
Subject: Re: RFC and I-D Citation Tool
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Tue, 31 Jul 2012 11:17:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <38D14FAE-F086-49CF-B0D2-9F30E1A2A8E7@viagenie.ca>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1278)
Cc: rsag@rfc-editor.org, RSOC <rsoc@iab.org>, The IETF <ietf@ietf.org>, Heather Flanagan <hlflanagan@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 18:17:46 -0000

cool!!!  I will also be using this! thanks!

Marc.

Le 2012-07-31 =E0 11:16, Ole Jacobsen a =E9crit :

>=20
> In The Internet Protocol Journal I have been using the following=20
> citation format, best illustrated by an example:
>=20
> Julien Meuric, Diego Caviglia, Don Fedyk, Attila Takacs, and Lou=20
> Berger, "GMPLS Asymmetric Bandwidth Bidirectional Label Switched=20
> Paths (LSPs)," RFC 6387, September 2011.
>=20
> So, that's full author names "and" before the last author name, title,=20=

> document number and date, using the American "quotation outside=20
> punctuation rule."
>=20
> I got tired of doing this "by hand" so I asked Henrik if he could=20
> write me a tool. He did (THANKS!), and the result is here:
>=20
> http://tools.ietf.org/tools/citation/
>=20
> This will take either the draft name or the RFC number as input and=20
> produce a citation similar to the one above. You can of course play=20
> with the elements and generate a format that suits your own taste, for=20=

> example, for I-Ds, in print it might be good to have the FILE NAME as=20=

> the last entry:
>=20
> Adam Langley, "Serializing DNS Records with DNSSEC Authentication,"=20
> Internet Draft, work in progress, July 2011,
> draft-agl-dane-serializechain-01
>=20
> ...since I like having filenames or URLs on one line (not wrapping)
> as much as possible.
>=20
> Many thanks again to Henrik, and I hope you will find it useful too!
>=20
> Ole
>=20
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo


From lars@netapp.com  Tue Jul 31 11:28:38 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 4A08711E80A4 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 11:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.436
X-Spam-Level: 
X-Spam-Status: No, score=-10.436 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rDOOyWz-gecB for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 11:28:37 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 7592C21F8926 for <ietf@ietf.org>; Tue, 31 Jul 2012 11:28:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.77,688,1336374000";  d="p7s'?scan'208";a="670548196"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 31 Jul 2012 11:28:22 -0700
Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q6VISLja020589; Tue, 31 Jul 2012 11:28:21 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.13]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0298.004; Tue, 31 Jul 2012 11:28:21 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: RFC and I-D Citation Tool
Thread-Topic: RFC and I-D Citation Tool
Thread-Index: AQHNb0igNg5IgJ3khUOcrqwfWeNK7pdEK0uA
Date: Tue, 31 Jul 2012 18:28:21 +0000
Message-ID: <90AB01B9-F750-4671-A611-7D1651A2C49F@netapp.com>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_787D5717-074C-487D-8E98-2B5A88B6F24A"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<rsag@rfc-editor.org>" <rsag@rfc-editor.org>, RSOC <rsoc@iab.org>, The IETF <ietf@ietf.org>, Heather Flanagan <hlflanagan@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 18:28:38 -0000

--Apple-Mail=_787D5717-074C-487D-8E98-2B5A88B6F24A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

And for those of us who write academic papers, there is of course =
Roland's and Miguel's BibTex collections:

http://tm.uka.de/~bless/bibrfcindex.html
https://sites.google.com/site/ea1dof/bibtex

Lars

On Jul 31, 2012, at 11:16, Ole Jacobsen <ole@cisco.com> wrote:

>=20
> In The Internet Protocol Journal I have been using the following=20
> citation format, best illustrated by an example:
>=20
> Julien Meuric, Diego Caviglia, Don Fedyk, Attila Takacs, and Lou=20
> Berger, "GMPLS Asymmetric Bandwidth Bidirectional Label Switched=20
> Paths (LSPs)," RFC 6387, September 2011.
>=20
> So, that's full author names "and" before the last author name, title,=20=

> document number and date, using the American "quotation outside=20
> punctuation rule."
>=20
> I got tired of doing this "by hand" so I asked Henrik if he could=20
> write me a tool. He did (THANKS!), and the result is here:
>=20
> http://tools.ietf.org/tools/citation/
>=20
> This will take either the draft name or the RFC number as input and=20
> produce a citation similar to the one above. You can of course play=20
> with the elements and generate a format that suits your own taste, for=20=

> example, for I-Ds, in print it might be good to have the FILE NAME as=20=

> the last entry:
>=20
> Adam Langley, "Serializing DNS Records with DNSSEC Authentication,"=20
> Internet Draft, work in progress, July 2011,
> draft-agl-dane-serializechain-01
>=20
> ...since I like having filenames or URLs on one line (not wrapping)
> as much as possible.
>=20
> Many thanks again to Henrik, and I hope you will find it useful too!
>=20
> Ole
>=20
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20


--Apple-Mail=_787D5717-074C-487D-8E98-2B5A88B6F24A
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
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDczMTE4MjgxOVowIwYJKoZIhvcNAQkEMRYEFEhS
Eth5mLr/fZCEoUOCRUXB+lAYMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAJwd0Eld
A3U+kDjIT8EmqtybyPBy58IczhR3Au6FDAqR6I9xL/elbj3D88jiGx9yrz7tmGy1JHXXzBr8jTDf
vxdWOU9VU8O24BWByrbXdjeoZqsiQ4kt/UjMUhFMMMeI4CrfrkcGlJtvvTa9H5AUy2nJhyE+tTK5
hAJKrIFLmsbF80tc3xZKa1UQGuLkp6VzVo7Rl/yg3sfQ7XzHpAl1TIxjhmxbpc0vDE2vNGHn2CTZ
rwNbTCUeyI2/y3460ulnNMXFdtJe4qe1d8lgihpFAoJ6i5EodQWldWpuRVo2OkYIbNjJ3BBQkKVB
AWJwd7gyih8QIqVe0pV7S4wdbalCukEAAAAAAAA=

--Apple-Mail=_787D5717-074C-487D-8E98-2B5A88B6F24A--

From mehmet.ersue@nsn.com  Tue Jul 31 13:27:45 2012
Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D07521F8880; Tue, 31 Jul 2012 13:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.577
X-Spam-Level: 
X-Spam-Status: No, score=-106.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gwibYC1auPDS; Tue, 31 Jul 2012 13:27:44 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 50BEA21F8864; Tue, 31 Jul 2012 13:27:44 -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 q6VKRYXN019361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 31 Jul 2012 22:27:35 +0200
Received: from DEMUEXC047.nsn-intra.net ([10.159.32.93]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q6VKRU4t011188; Tue, 31 Jul 2012 22:27:31 +0200
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 31 Jul 2012 22:27:30 +0200
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: RFC and I-D Citation Tool
Date: Tue, 31 Jul 2012 22:27:27 +0200
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net>
In-Reply-To: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RFC and I-D Citation Tool
Thread-Index: Ac1vSKlaKEftVUhIQ56BFPMxqBB8TQAD8v7A
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "Ole Jacobsen" <ole@cisco.com>, "The IETF" <ietf@ietf.org>
X-OriginalArrivalTime: 31 Jul 2012 20:27:30.0452 (UTC) FILETIME=[E8A59D40:01CD6F5A]
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: 2107
X-purgate-ID: 151667::1343766456-00002E58-ABE6EE33/0-0/0-0
Cc: Henrik Levkowetz <henrik@levkowetz.com>, RSOC <rsoc@iab.org>, Heather Flanagan <hlflanagan@gmail.com>, rsag@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: Tue, 31 Jul 2012 20:27:45 -0000

Nice tool.=20

However, I am wondering why the tool changes the order of the names.
There is actually a reason why documents list names in a specific order.

Some of the citations appear to be incomplete, see RFC3410.

Cheers,=20
Mehmet=20


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of ext Ole
> Jacobsen
> Sent: Tuesday, July 31, 2012 11:17 AM
> To: The IETF
> Cc: RSOC; Heather Flanagan; rsag@rfc-editor.org
> Subject: RFC and I-D Citation Tool
>=20
>=20
> In The Internet Protocol Journal I have been using the following
> citation format, best illustrated by an example:
>=20
>  Julien Meuric, Diego Caviglia, Don Fedyk, Attila Takacs, and Lou
>  Berger, "GMPLS Asymmetric Bandwidth Bidirectional Label Switched
>  Paths (LSPs)," RFC 6387, September 2011.
>=20
> So, that's full author names "and" before the last author name, title,
> document number and date, using the American "quotation outside
> punctuation rule."
>=20
> I got tired of doing this "by hand" so I asked Henrik if he could
> write me a tool. He did (THANKS!), and the result is here:
>=20
> http://tools.ietf.org/tools/citation/
>=20
> This will take either the draft name or the RFC number as input and
> produce a citation similar to the one above. You can of course play
> with the elements and generate a format that suits your own taste, for
> example, for I-Ds, in print it might be good to have the FILE NAME as
> the last entry:
>=20
>  Adam Langley, "Serializing DNS Records with DNSSEC Authentication,"
>  Internet Draft, work in progress, July 2011,
>  draft-agl-dane-serializechain-01
>=20
> ...since I like having filenames or URLs on one line (not wrapping)
> as much as possible.
>=20
> Many thanks again to Henrik, and I hope you will find it useful too!
>=20
> Ole
>=20
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo


From ole@cisco.com  Tue Jul 31 14:23:02 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD4721F8681 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 14:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.488
X-Spam-Level: 
X-Spam-Status: No, score=-110.488 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QvGw8L0gL4Ev for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 14:23:01 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 06A0B21F8644 for <ietf@ietf.org>; Tue, 31 Jul 2012 14:23:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=2644; q=dns/txt; s=iport; t=1343769780; x=1344979380; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=jKlEtUQcZGw/VhL67EN6EWcK6sCEecPCfNcSh5RIcN8=; b=CREoA1JdQ8DKFYPIn17Tl0WyzKpHvTW65rogZyxY/mCXFUuOmAyCufdW BGeWRKWIctoxe1bO0hlGlPkd//b2D5nMwn1kuiD3nau7irW0Un+Kc4Ko2 okK2G4C0p36d4b0v0B1L/+EIbt4OQO7OrEqf9z/StuCS90Obz8VXEUKsQ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAN5LGFCrRDoH/2dsb2JhbABCA7l7gQeCIAEBAQMBEgECJT8FBwQLEQQBASgHRgkIBhMih2UFDJtbg0gQnQ2LSRqDToMhA4hNjg6ER4UygxqBBGKCf4E/
X-IronPort-AV: E=Sophos;i="4.77,689,1336348800"; d="scan'208";a="53682507"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 31 Jul 2012 21:22:58 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q6VLMwfk017675; Tue, 31 Jul 2012 21:22:58 GMT
Date: Tue, 31 Jul 2012 14:23:01 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Subject: RE: RFC and I-D Citation Tool
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net>
Message-ID: <alpine.OSX.2.01.1207311421270.87763@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net> <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: rsag@rfc-editor.org, Henrik Levkowetz <henrik@levkowetz.com>, RSOC <rsoc@iab.org>, The IETF <ietf@ietf.org>, Heather Flanagan <hlflanagan@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 21:23:02 -0000

Mehmet,

The tool is not INTENDED to change the author order. A somewhat 
incomplete database can indeed lead to unexpected results, use with 
caution.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Tue, 31 Jul 2012, Ersue, Mehmet (NSN - DE/Munich) wrote:

> Nice tool. 
> 
> However, I am wondering why the tool changes the order of the names.
> There is actually a reason why documents list names in a specific order.
> 
> Some of the citations appear to be incomplete, see RFC3410.
> 
> Cheers, 
> Mehmet 
> 
> 
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of ext Ole
> > Jacobsen
> > Sent: Tuesday, July 31, 2012 11:17 AM
> > To: The IETF
> > Cc: RSOC; Heather Flanagan; rsag@rfc-editor.org
> > Subject: RFC and I-D Citation Tool
> > 
> > 
> > In The Internet Protocol Journal I have been using the following
> > citation format, best illustrated by an example:
> > 
> >  Julien Meuric, Diego Caviglia, Don Fedyk, Attila Takacs, and Lou
> >  Berger, "GMPLS Asymmetric Bandwidth Bidirectional Label Switched
> >  Paths (LSPs)," RFC 6387, September 2011.
> > 
> > So, that's full author names "and" before the last author name, title,
> > document number and date, using the American "quotation outside
> > punctuation rule."
> > 
> > I got tired of doing this "by hand" so I asked Henrik if he could
> > write me a tool. He did (THANKS!), and the result is here:
> > 
> > http://tools.ietf.org/tools/citation/
> > 
> > This will take either the draft name or the RFC number as input and
> > produce a citation similar to the one above. You can of course play
> > with the elements and generate a format that suits your own taste, for
> > example, for I-Ds, in print it might be good to have the FILE NAME as
> > the last entry:
> > 
> >  Adam Langley, "Serializing DNS Records with DNSSEC Authentication,"
> >  Internet Draft, work in progress, July 2011,
> >  draft-agl-dane-serializechain-01
> > 
> > ...since I like having filenames or URLs on one line (not wrapping)
> > as much as possible.
> > 
> > Many thanks again to Henrik, and I hope you will find it useful too!
> > 
> > Ole
> > 
> > 
> > 
> > Ole J. Jacobsen
> > Editor and Publisher,  The Internet Protocol Journal
> > Cisco Systems
> > Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> > E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> > Skype: organdemo
> 
> 

From smb@cs.columbia.edu  Tue Jul 31 14:35:29 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 2C96521F888D; Tue, 31 Jul 2012 14:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RvrnCS97LT98; Tue, 31 Jul 2012 14:35:28 -0700 (PDT)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id F083221F8857; Tue, 31 Jul 2012 14:35:27 -0700 (PDT)
Received: from [10.9.0.226] (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 q6VLZLqk016938 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 31 Jul 2012 17:35:22 -0400 (EDT)
Subject: Re: RFC and I-D Citation Tool
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <alpine.OSX.2.01.1207311421270.87763@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Tue, 31 Jul 2012 14:35:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C18E588A-541E-43C7-AF41-F301E3A6AE5B@cs.columbia.edu>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net> <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net> <alpine.OSX.2.01.1207311421270.87763@173-11-110-132-sfba.hfc.comcastbusiness.net>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1278)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
Cc: The IETF <ietf@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>, RSOC <rsoc@iab.org>, Heather Flanagan <hlflanagan@gmail.com>, rsag@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: Tue, 31 Jul 2012 21:35:29 -0000

There are a number of very weird entries that require special handling.  =
I (also) wrote a Python script to convert the XML file to bibtex and had =
to deal with a number of these special cases.  For example, RFC 4534 =
lists the authors as "A Colegrove, H Harney" instead of "A. Colegrove, =
H. Harney".  Other names like "The Internet Society" require special =
handling.  And I completely punted on proper capitalization of the =
titles; I just accept what's there.

On Jul 31, 2012, at 2:23 PM, Ole Jacobsen wrote:

>=20
> Mehmet,
>=20
> The tool is not INTENDED to change the author order. A somewhat=20
> incomplete database can indeed lead to unexpected results, use with=20
> caution.
>=20
> Ole
>=20
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
>=20
>=20
> On Tue, 31 Jul 2012, Ersue, Mehmet (NSN - DE/Munich) wrote:
>=20
>> Nice tool.=20
>>=20
>> However, I am wondering why the tool changes the order of the names.
>> There is actually a reason why documents list names in a specific =
order.
>>=20
>> Some of the citations appear to be incomplete, see RFC3410.
>>=20
>> Cheers,=20
>> Mehmet=20
>>=20
>>=20
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>> Of ext Ole
>>> Jacobsen
>>> Sent: Tuesday, July 31, 2012 11:17 AM
>>> To: The IETF
>>> Cc: RSOC; Heather Flanagan; rsag@rfc-editor.org
>>> Subject: RFC and I-D Citation Tool
>>>=20
>>>=20
>>> In The Internet Protocol Journal I have been using the following
>>> citation format, best illustrated by an example:
>>>=20
>>> Julien Meuric, Diego Caviglia, Don Fedyk, Attila Takacs, and Lou
>>> Berger, "GMPLS Asymmetric Bandwidth Bidirectional Label Switched
>>> Paths (LSPs)," RFC 6387, September 2011.
>>>=20
>>> So, that's full author names "and" before the last author name, =
title,
>>> document number and date, using the American "quotation outside
>>> punctuation rule."
>>>=20
>>> I got tired of doing this "by hand" so I asked Henrik if he could
>>> write me a tool. He did (THANKS!), and the result is here:
>>>=20
>>> http://tools.ietf.org/tools/citation/
>>>=20
>>> This will take either the draft name or the RFC number as input and
>>> produce a citation similar to the one above. You can of course play
>>> with the elements and generate a format that suits your own taste, =
for
>>> example, for I-Ds, in print it might be good to have the FILE NAME =
as
>>> the last entry:
>>>=20
>>> Adam Langley, "Serializing DNS Records with DNSSEC Authentication,"
>>> Internet Draft, work in progress, July 2011,
>>> draft-agl-dane-serializechain-01
>>>=20
>>> ...since I like having filenames or URLs on one line (not wrapping)
>>> as much as possible.
>>>=20
>>> Many thanks again to Henrik, and I hope you will find it useful too!
>>>=20
>>> Ole
>>>=20
>>>=20
>>>=20
>>> Ole J. Jacobsen
>>> Editor and Publisher,  The Internet Protocol Journal
>>> Cisco Systems
>>> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
>>> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
>>> Skype: organdemo
>>=20
>>=20
>=20


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






From jnc@mercury.lcs.mit.edu  Tue Jul 31 14:47:57 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDAC721F88F9 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 14:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.321
X-Spam-Level: 
X-Spam-Status: No, score=-5.321 tagged_above=-999 required=5 tests=[AWL=-0.581, BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rrNe9pBXrm1g for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 14:47:56 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6688C21F88EB for <ietf@ietf.org>; Tue, 31 Jul 2012 14:47:56 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 6CF4118C10A; Tue, 31 Jul 2012 17:47:55 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: RFC and I-D Citation Tool
Message-Id: <20120731214755.6CF4118C10A@mercury.lcs.mit.edu>
Date: Tue, 31 Jul 2012 17:47:55 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: rsoc@iab.org, jnc@mercury.lcs.mit.edu, rsag@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: Tue, 31 Jul 2012 21:47:57 -0000

    > From: Ole Jacobsen <ole@cisco.com>

    > using the American "quotation outside punctuation rule."

Ugh. There may be uglier typographic conventions, but off the top of my head,
I can't come up with one.

	Noel

From cabo@tzi.org  Tue Jul 31 14:50:31 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 7745521F8501; Tue, 31 Jul 2012 14:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.684
X-Spam-Level: 
X-Spam-Status: No, score=-106.684 tagged_above=-999 required=5 tests=[AWL=-0.435, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5b+rjIHCTe6H; Tue, 31 Jul 2012 14:50:31 -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 AF6FF21F84F7; Tue, 31 Jul 2012 14:50:30 -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 q6VLoHE1005018; Tue, 31 Jul 2012 23:50:18 +0200 (CEST)
Received: from dhcp-9069.meeting.ietf.org (dhcp-9069.meeting.ietf.org [130.129.8.105]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 9DF4276C; Tue, 31 Jul 2012 23:50:16 +0200 (CEST)
Subject: Re: RFC and I-D Citation Tool
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Tue, 31 Jul 2012 14:50:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A3DE550-E441-469D-9A7D-4844838B8B6B@tzi.org>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1485)
Cc: rsag@rfc-editor.org, RSOC <rsoc@iab.org>, The IETF <ietf@ietf.org>, Heather Flanagan <hlflanagan@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 21:50:31 -0000

Not yet quite optimal for e.g. RFC 3095:

=
http://tools.ietf.org/tools/citation/?doc=3D3095&template=3D%7Bauthors.and=
list%7D%2C+%22%7Bdoctitle%7D%2C%22+%7Bdocname%7D%2C+%7Bdate%3A%25B+%25Y.%7=
D&submit=3DGenerate+citation

Gr=FC=DFe, Carsten


From aservin@lacnic.net  Tue Jul 31 15:33:36 2012
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F26B511E80E2 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 15:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=-0.744, BAYES_05=-1.11, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ih-oqglYGiO3 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 15:33:35 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id E14D421F86DE for <ietf@ietf.org>; Tue, 31 Jul 2012 15:33:34 -0700 (PDT)
Received: from [IPv6:2001:df8::16:d08e:c4dd:6810:5e8c] (unknown [IPv6:2001:df8:0:16:d08e:c4dd:6810:5e8c]) by mail.lacnic.net.uy (Postfix) with ESMTP id E27D830847D for <ietf@ietf.org>; Tue, 31 Jul 2012 19:33:24 -0300 (UYT)
From: Arturo Servin <aservin@lacnic.net>
Content-Type: multipart/signed; boundary="Apple-Mail=_BB5BEB77-3E6D-4582-B58D-3F0C9DD3F73A"; protocol="application/pkcs7-signature"; micalg=sha1
Subject: IETF meeting future dates
Date: Tue, 31 Jul 2012 15:33:19 -0700
Message-Id: <AEE8C452-7C68-4170-A56B-D49E65E65B28@lacnic.net>
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 22:33:36 -0000

--Apple-Mail=_BB5BEB77-3E6D-4582-B58D-3F0C9DD3F73A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


	I was reviewing the dates for future IETF meetings (nothing in =
particular, just curiosity) and I found that IETF 92 is slightly =
different:

March 2015 - 92nd IETF

March 22-27, 2015
Host: TBD
Location: Americas

	IETF 96nd states "North America"

	So I wonder if finally the IETF has decided to go below the Rio =
Grande (Bravo for me). If so, any ideas of where?

	Mexico, Brazil, Puerto Rico, Argentina?

=09
Regards,
as=

--Apple-Mail=_BB5BEB77-3E6D-4582-B58D-3F0C9DD3F73A
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFkTCCBY0w
ggR1oAMCAQICASUwDQYJKoZIhvcNAQEFBQAwgYIxCzAJBgNVBAYTAlVZMQ8wDQYDVQQKDAZMQUNO
SUMxFDASBgNVBAsMC0VuZ2luZWVyaW5nMScwJQYDVQQDDB5MQUNOSUMgQ2VydGlmaWNhdGlvbiBB
dXRob3JpdHkxIzAhBgkqhkiG9w0BCQEWFGNhbWFuYWdlckBsYWNuaWMubmV0MB4XDTEyMDYyMDE5
NDI1N1oXDTE0MDYyMDE5NDI1N1owbjELMAkGA1UEBhMCVVkxJzAlBgNVBAoMHkxBQ05JQyBDZXJ0
aWZpY2F0aW9uIEF1dGhvcml0eTERMA8GA1UECwwISW50ZXJuZXQxFjAUBgNVBAMMDUFydHVybyBT
ZXJ2aW4xCzAJBgNVBAUTAjM3MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA8vWQgfa7
c45wIkd7vr14P8qQ+2rlRilQLi8uZXVJsgYvkwJFAlkCxr5A0f2K3jZLhNcdSj7Onjngt3IH8t5R
jmYiMy9jh+e+wOMLw/Qj+Sf2V0DtKo6PmqTvvurLigkdBSzZRpsNcW4wSFd2qydBEQ49ImlZl0Mh
ytuB9sWvuk/xwSn3bFlPufP13+akyKZAXuH8xjOuE83B/eBBytlJ3kQKVnq16twr5N8LuAixDHW4
++tz/0gnDiNwXA3po4INAdy5zWEuWfSKXihmrC1xRHs4AFu3//tmOiDpPImvYcd0cN2JtIWybc5v
/SozysYvcgBqAf20EZsb5rxaMLHk7wIDAQABo4ICHzCCAhswCQYDVR0TBAIwADARBglghkgBhvhC
AQEEBAMCBaAwCwYDVR0PBAQDAgXgMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDApBglg
hkgBhvhCAQ0EHBYaVXNlciBjZXJ0aWZpY2F0ZSBvZiBMQUNOSUMwHQYDVR0OBBYEFH36gq+iiboP
1S8Yskxtz10MTgXmMIGvBgNVHSMEgacwgaSAFLvgXXmAhISyblB33o/fFPcoVwQloYGIpIGFMIGC
MQswCQYDVQQGEwJVWTEPMA0GA1UECgwGTEFDTklDMRQwEgYDVQQLDAtFbmdpbmVlcmluZzEnMCUG
A1UEAwweTEFDTklDIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYJKoZIhvcNAQkBFhRjYW1h
bmFnZXJAbGFjbmljLm5ldIIBADAdBgNVHREEFjAUgRJhc2VydmluQGxhY25pYy5uZXQwHwYDVR0S
BBgwFoEUY2FtYW5hZ2VyQGxhY25pYy5uZXQwLwYJYIZIAYb4QgEEBCIWIGh0dHBzOi8vcGtpLmxh
Y25pYy5uZXQvY2EvY2EuY3JsMC8GCWCGSAGG+EIBAwQiFiBodHRwczovL3BraS5sYWNuaWMubmV0
L2NhL2NhLmNybDAxBgNVHR8EKjAoMCagJKAihiBodHRwczovL3BraS5sYWNuaWMubmV0L2NhL2Nh
LmNybDANBgkqhkiG9w0BAQUFAAOCAQEAeVjPtkdDXsiSfyYYxSe+n04lRgzhXIpUSvc3r0/Pi9wJ
dwYslC6A/4Q5f58et7r2JHozhl3qvcLoCkGBezEBruSmOw886DugtkZk5FaQriM5cv74fRvabslW
pE5IxBFeM4dbqnyCUM3OWyj/Q2NNjrcGtg0gw9rgOgk7pAH/Uy4BmLe4G9sjtIljiqgeAaY86qjJ
yX55fmr8+Iz07s0Vu/teJCFVAa0MZlabj8VodyP7xkflfakRCxwN5V/XyT7XFGbmZbtJNXJ/p3Gb
vB9arRAmSy+r8ZubytzVUcZ4iMyrXg/D7PKgUfP3b5wqnVOFmRdlrHlW2kyB4QmI/gDmVTGCA0sw
ggNHAgEBMIGIMIGCMQswCQYDVQQGEwJVWTEPMA0GA1UECgwGTEFDTklDMRQwEgYDVQQLDAtFbmdp
bmVlcmluZzEnMCUGA1UEAwweTEFDTklDIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYJKoZI
hvcNAQkBFhRjYW1hbmFnZXJAbGFjbmljLm5ldAIBJTAJBgUrDgMCGgUAoIIBlzAYBgkqhkiG9w0B
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjA3MzEyMjMzMjBaMCMGCSqGSIb3DQEJ
BDEWBBSVNG4hztGVlnGEZak5YU/DF3QbNzCBmQYJKwYBBAGCNxAEMYGLMIGIMIGCMQswCQYDVQQG
EwJVWTEPMA0GA1UECgwGTEFDTklDMRQwEgYDVQQLDAtFbmdpbmVlcmluZzEnMCUGA1UEAwweTEFD
TklDIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYJKoZIhvcNAQkBFhRjYW1hbmFnZXJAbGFj
bmljLm5ldAIBJTCBmwYLKoZIhvcNAQkQAgsxgYuggYgwgYIxCzAJBgNVBAYTAlVZMQ8wDQYDVQQK
DAZMQUNOSUMxFDASBgNVBAsMC0VuZ2luZWVyaW5nMScwJQYDVQQDDB5MQUNOSUMgQ2VydGlmaWNh
dGlvbiBBdXRob3JpdHkxIzAhBgkqhkiG9w0BCQEWFGNhbWFuYWdlckBsYWNuaWMubmV0AgElMA0G
CSqGSIb3DQEBAQUABIIBADqhyoVpox1V+1cv+b15km5wX7XvaZpcENE+Vmmq9VQI4q/CyTWLurfi
I29yk79JhpsKljp41iq2OJqwjBC0kMrEUVxOZEC1oqKlNONQ8m2v2pvT4jP54NQW7SAG/hH13QLs
oJILs3Y5TzLVJIz1OB5REs7ipEEevmQX067R0w4UoNTNe0q5uo/lPnXXbMvU8D1PBnJMI97a3uZV
SWy+0T/nZ3DIpd7pCFx/hql83XtGtlSpzdkE8OH2Z4BsGyvb2Lzf38e6Ydh6jjteVwxyDYsxzKKY
m/ZSFW/fhbxdzGY3Mn/HzX1j/SiTIKHb1n561T0IohzWx93tMeK36MkMGEsAAAAAAAA=

--Apple-Mail=_BB5BEB77-3E6D-4582-B58D-3F0C9DD3F73A--

From sm@resistor.net  Tue Jul 31 15:43: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 05D0F21F88EB for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 15:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aTAJ3lCGSdkh for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 15:43:06 -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 47D5921F87F7 for <ietf@ietf.org>; Tue, 31 Jul 2012 15:43:06 -0700 (PDT)
Received: from sm-THINK.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 q6VMgwOe007313; Tue, 31 Jul 2012 15:43:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1343774585; bh=Qg5hpUInztHM/EC+/q8x8XfKTmzzYXiNs6JI6UrfqnU=; h=Date:To:From:Subject:Cc; b=ENJ5Ml5AS4yvM13iJ1Ah05mY++wXMHF8aINNoon1+DLDlR+6N408z3PM4GJfjMfQW 8cmVh8zxE5A+yLyuVo2FGWPpw8xZwqvBKxeOZLsIfbRDm2ZGPxYelDl7sC4WUCSdD1 mK1ccAIiqfG/DEnbHG6YGw7jHF6xSCIxs/yFDSWE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1343774585; i=@resistor.net; bh=Qg5hpUInztHM/EC+/q8x8XfKTmzzYXiNs6JI6UrfqnU=; h=Date:To:From:Subject:Cc; b=WsuRO/BIAoN8YuK3LBR3IF3CoVTvcji8rCjalVfCCqhOj1NRRXuvNKCPfqc7y6742 lQeqCr0zeQUhxBxV0ABYD1J1BcOKZXC2luN8FDxpTM5rhyKjZ4lxAke1CVqM3TpYNh rseKqUVTdkmv/7HmFhgHYQDh2BWMpGFqTELz0Ydo=
Message-Id: <6.2.5.6.2.20120731152716.088ab5d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 31 Jul 2012 15:42:04 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-00.txt
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 22:43:11 -0000

Hi John,
At 05:48 AM 7/31/2012, John C Klensin wrote:
>Much of this is about appearances.   For example, I would hope
>that sitting ADs would have better sense than to volunteer for
>the Nomcom even if the rules technically permitted that.  Nor

Yes.

>would I expect Secretariat staff to volunteer (as far as I know,
>none ever has despite the current rules apparently permitting

Yes.

The IETF usually says that people participate as individuals.  It is 
up to each individual to see whether it is appropriate to volunteer 
for NomCom if there is possible conflict of interest.  RFC 3777 
discusses about stacking up the selection process (see primary 
affiliation) but it does get into other details which can influence 
the selection process.  If the objective is to avoid self-selection, 
one could question the process for the appointment of the NomCom Chair.

Regards,
-sm 


From henrik@levkowetz.com  Tue Jul 31 15:55:44 2012
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5F421F88E5; Tue, 31 Jul 2012 15:55:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sbDrhPdYr3tk; Tue, 31 Jul 2012 15:55:39 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31::14]) by ietfa.amsl.com (Postfix) with ESMTP id A3C5821F88AD; Tue, 31 Jul 2012 15:55:39 -0700 (PDT)
Received: from dhcp-67cb.meeting.ietf.org ([130.129.103.203]:61583) by merlot.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <henrik@levkowetz.com>) id 1SwLLS-0006HJ-NF; Wed, 01 Aug 2012 00:55:21 +0200
Message-ID: <50186251.7070705@levkowetz.com>
Date: Tue, 31 Jul 2012 15:55:13 -0700
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.6esrpre) Gecko/20120713 Thunderbird/10.0.6
MIME-Version: 1.0
To: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net> <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 130.129.103.203
X-SA-Exim-Rcpt-To: mehmet.ersue@nsn.com, ole@cisco.com, ietf@ietf.org, rsoc@iab.org, hlflanagan@gmail.com, rsag@rfc-editor.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: RFC and I-D Citation Tool
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:57:07 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: RSOC <rsoc@iab.org>, Ole Jacobsen <ole@cisco.com>, The IETF <ietf@ietf.org>, rsag@rfc-editor.org, Heather Flanagan <hlflanagan@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 22:55:44 -0000

Hi Ersue,

On 2012-07-31 13:27 Ersue, Mehmet (NSN - DE/Munich) said the following:
> Nice tool. 
> 
> However, I am wondering why the tool changes the order of the names.
> There is actually a reason why documents list names in a specific order.

There is no intentional name re-ordering.  I'll look into why that happens.

> Some of the citations appear to be incomplete, see RFC3410.

Ok, will check that too.

Thanks for the feedback!


Best regards,

	Henrik

> Cheers, 
> Mehmet 
> 
> 
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of ext Ole
>> Jacobsen
>> Sent: Tuesday, July 31, 2012 11:17 AM
>> To: The IETF
>> Cc: RSOC; Heather Flanagan; rsag@rfc-editor.org
>> Subject: RFC and I-D Citation Tool
>> 
>> 
>> In The Internet Protocol Journal I have been using the following
>> citation format, best illustrated by an example:
>> 
>>  Julien Meuric, Diego Caviglia, Don Fedyk, Attila Takacs, and Lou
>>  Berger, "GMPLS Asymmetric Bandwidth Bidirectional Label Switched
>>  Paths (LSPs)," RFC 6387, September 2011.
>> 
>> So, that's full author names "and" before the last author name, title,
>> document number and date, using the American "quotation outside
>> punctuation rule."
>> 
>> I got tired of doing this "by hand" so I asked Henrik if he could
>> write me a tool. He did (THANKS!), and the result is here:
>> 
>> http://tools.ietf.org/tools/citation/
>> 
>> This will take either the draft name or the RFC number as input and
>> produce a citation similar to the one above. You can of course play
>> with the elements and generate a format that suits your own taste, for
>> example, for I-Ds, in print it might be good to have the FILE NAME as
>> the last entry:
>> 
>>  Adam Langley, "Serializing DNS Records with DNSSEC Authentication,"
>>  Internet Draft, work in progress, July 2011,
>>  draft-agl-dane-serializechain-01
>> 
>> ...since I like having filenames or URLs on one line (not wrapping)
>> as much as possible.
>> 
>> Many thanks again to Henrik, and I hope you will find it useful too!
>> 
>> Ole
>> 
>> 
>> 
>> Ole J. Jacobsen
>> Editor and Publisher,  The Internet Protocol Journal
>> Cisco Systems
>> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
>> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
>> Skype: organdemo
> 
> 

From henrik@levkowetz.com  Tue Jul 31 15:58:44 2012
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0F221F8900; Tue, 31 Jul 2012 15:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YoFQUx8ujVMF; Tue, 31 Jul 2012 15:58:43 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31::14]) by ietfa.amsl.com (Postfix) with ESMTP id 2751521F88F5; Tue, 31 Jul 2012 15:58:43 -0700 (PDT)
Received: from dhcp-67cb.meeting.ietf.org ([130.129.103.203]:61587) by merlot.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <henrik@levkowetz.com>) id 1SwLOL-00031Q-2e; Wed, 01 Aug 2012 00:58:18 +0200
Message-ID: <50186301.9030506@levkowetz.com>
Date: Tue, 31 Jul 2012 15:58:09 -0700
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.6esrpre) Gecko/20120713 Thunderbird/10.0.6
MIME-Version: 1.0
To: Steven Bellovin <smb@cs.columbia.edu>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net> <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net> <alpine.OSX.2.01.1207311421270.87763@173-11-110-132-sfba.hfc.comcastbusiness.net> <C18E588A-541E-43C7-AF41-F301E3A6AE5B@cs.columbia.edu>
In-Reply-To: <C18E588A-541E-43C7-AF41-F301E3A6AE5B@cs.columbia.edu>
X-Enigmail-Version: 1.4
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE32A1D029B96A8DF3A0D7EFA"
X-SA-Exim-Connect-IP: 130.129.103.203
X-SA-Exim-Rcpt-To: smb@cs.columbia.edu, ole@cisco.com, mehmet.ersue@nsn.com, rsag@rfc-editor.org, rsoc@iab.org, ietf@ietf.org, hlflanagan@gmail.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: RFC and I-D Citation Tool
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:57:07 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: Ole Jacobsen <ole@cisco.com>, The IETF <ietf@ietf.org>, RSOC <rsoc@iab.org>, Heather Flanagan <hlflanagan@gmail.com>, rsag@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: Tue, 31 Jul 2012 22:58:44 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE32A1D029B96A8DF3A0D7EFA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


On 2012-07-31 14:35 Steven Bellovin said the following:
> There are a number of very weird entries that require special
> handling. I (also) wrote a Python script to convert the XML file to
> bibtex and had to deal with a number of these special cases. For
> example, RFC 4534 lists the authors as "A Colegrove, H Harney"
> instead of "A. Colegrove, H. Harney". Other names like "The Internet
> Society" require special handling. And I completely punted on proper
> capitalization of the titles; I just accept what's there.

Ah.  I'll have to look at fixing cases like the ones you mention, then.

Thanks!

	Henrik

>=20
> On Jul 31, 2012, at 2:23 PM, Ole Jacobsen wrote:
>=20
>>=20
>> Mehmet,
>>=20
>> The tool is not INTENDED to change the author order. A somewhat=20
>> incomplete database can indeed lead to unexpected results, use with=20
>> caution.
>>=20
>> Ole
>>=20
>> Ole J. Jacobsen
>> Editor and Publisher,  The Internet Protocol Journal
>> Cisco Systems
>> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
>> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
>> Skype: organdemo
>>=20
>>=20
>> On Tue, 31 Jul 2012, Ersue, Mehmet (NSN - DE/Munich) wrote:
>>=20
>>> Nice tool.=20
>>>=20
>>> However, I am wondering why the tool changes the order of the names.
>>> There is actually a reason why documents list names in a specific ord=
er.
>>>=20
>>> Some of the citations appear to be incomplete, see RFC3410.
>>>=20
>>> Cheers,=20
>>> Mehmet=20
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf=

>>> Of ext Ole
>>>> Jacobsen
>>>> Sent: Tuesday, July 31, 2012 11:17 AM
>>>> To: The IETF
>>>> Cc: RSOC; Heather Flanagan; rsag@rfc-editor.org
>>>> Subject: RFC and I-D Citation Tool
>>>>=20
>>>>=20
>>>> In The Internet Protocol Journal I have been using the following
>>>> citation format, best illustrated by an example:
>>>>=20
>>>> Julien Meuric, Diego Caviglia, Don Fedyk, Attila Takacs, and Lou
>>>> Berger, "GMPLS Asymmetric Bandwidth Bidirectional Label Switched
>>>> Paths (LSPs)," RFC 6387, September 2011.
>>>>=20
>>>> So, that's full author names "and" before the last author name, titl=
e,
>>>> document number and date, using the American "quotation outside
>>>> punctuation rule."
>>>>=20
>>>> I got tired of doing this "by hand" so I asked Henrik if he could
>>>> write me a tool. He did (THANKS!), and the result is here:
>>>>=20
>>>> http://tools.ietf.org/tools/citation/
>>>>=20
>>>> This will take either the draft name or the RFC number as input and
>>>> produce a citation similar to the one above. You can of course play
>>>> with the elements and generate a format that suits your own taste, f=
or
>>>> example, for I-Ds, in print it might be good to have the FILE NAME a=
s
>>>> the last entry:
>>>>=20
>>>> Adam Langley, "Serializing DNS Records with DNSSEC Authentication,"
>>>> Internet Draft, work in progress, July 2011,
>>>> draft-agl-dane-serializechain-01
>>>>=20
>>>> ...since I like having filenames or URLs on one line (not wrapping)
>>>> as much as possible.
>>>>=20
>>>> Many thanks again to Henrik, and I hope you will find it useful too!=

>>>>=20
>>>> Ole
>>>>=20
>>>>=20
>>>>=20
>>>> Ole J. Jacobsen
>>>> Editor and Publisher,  The Internet Protocol Journal
>>>> Cisco Systems
>>>> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
>>>> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
>>>> Skype: organdemo
>>>=20
>>>=20
>>=20
>=20
>=20
> 		--Steve Bellovin, https://www.cs.columbia.edu/~smb
>=20
>=20
>=20
>=20
>=20
>=20


--------------enigE32A1D029B96A8DF3A0D7EFA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlAYYwEACgkQeVhrtTJkXCMbeQCeOI0VzKzRCVx+ZizCu3cyd01H
AdMAoIWRjJDyFsyU4FT6wQu0jxtCd8yY
=g/ri
-----END PGP SIGNATURE-----

--------------enigE32A1D029B96A8DF3A0D7EFA--

From ole@cisco.com  Tue Jul 31 16:17:43 2012
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB55E11E808E for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 16:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.493
X-Spam-Level: 
X-Spam-Status: No, score=-110.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F9tt+GJYiatD for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 16:17:43 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 30FBD21F88F5 for <ietf@ietf.org>; Tue, 31 Jul 2012 16:17:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=542; q=dns/txt; s=iport; t=1343776663; x=1344986263; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=+4GPrMu6G8hJBqe+gkMlGdla4ig2CqKy+/nPWwF7mZo=; b=V3v/TLVmNnubmjgS//8f6aZ3sKR+1Fn/mfuqEaa/sjP5s7Geq5KHX3QH tQdeq0o0iY3CH1+7nNdfcFSqntl2KU5+xlCueCJmVew3ViWBWgvfqzeMp SWKzDC2Z3/a1mzeL1fSF9dtDSGEEec4BAjzV2aBb/K/C46vqaM9QFGXCl c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlAFABxnGFCrRDoH/2dsb2JhbABCA4UxtEuBB4IhAQEEEgECJT8QC0ZXBhMih2qbZYNIEJ0Ii2ODToMhA4hNklWFMoMagQRign+BPw
X-IronPort-AV: E=Sophos;i="4.77,689,1336348800"; d="scan'208";a="50580973"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 31 Jul 2012 23:17:42 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q6VNHfiM022134; Tue, 31 Jul 2012 23:17:41 GMT
Date: Tue, 31 Jul 2012 16:17:45 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: RFC and I-D Citation Tool
In-Reply-To: <50186301.9030506@levkowetz.com>
Message-ID: <alpine.OSX.2.01.1207311615310.88195@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net> <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net> <alpine.OSX.2.01.1207311421270.87763@173-11-110-132-sfba.hfc.comcastbusiness.net> <C18E588A-541E-43C7-AF41-F301E3A6AE5B@cs.columbia.edu> <50186301.9030506@levkowetz.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: The IETF <ietf@ietf.org>, RSOC <rsoc@iab.org>, Heather Flanagan <hlflanagan@gmail.com>, rsag@rfc-editor.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 23:17:44 -0000

One feature request that I discussed with Henrik was to either
"auto-detect" I-D file names and handle them slightly differently
from RFC numbers (by putting the file name as the final entry)
OR just having two tools. With the kind of feedback Henrik is
getting I am sure the tool will be improved/enhanced over time.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From barryleiba@gmail.com  Tue Jul 31 16:27:59 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 C8C5711E8137 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 16:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.959
X-Spam-Level: 
X-Spam-Status: No, score=-102.959 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yz94DasTH3O0 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 16:27:59 -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 196C111E80FA for <ietf@ietf.org>; Tue, 31 Jul 2012 16:27:59 -0700 (PDT)
Received: by pbbjt11 with SMTP id jt11so43259pbb.31 for <ietf@ietf.org>; Tue, 31 Jul 2012 16:27:58 -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=Yb6foeIbBJ5K6y24+/5v4twmVKP6KJnLrWOMtU/5sMg=; b=YhT5ghsfsGmE8rcSrGrtbylYxNMCWQQ7wG5UabuSXdE/TNRD6DLmUUYbdwmDtoONgt YENA9EYUY0Cr4aETSfjxUUf42RaNHD589e6b8Hw/Zgnv8yW0Q+ZFnoBVv1EB0/9XNozf UmBjvKBXdSA6shcfdyRGB555HgWWfV2sJD/kokXK7shfihYvDSi684U5aQJII9ow72rK uOmM+cWHy8OodT/PajeumrCPEDEHXyKwNIMiLK9UDSzTN2ndBCQNXxX8Ikmhrgvqsnmg WQeBJ1sTR39xP4yMS0cVQlPhIosQGbLPALUH/b7JV2Ye5Gzm7lPOAPzh1ekhuIM4vTJi F+bg==
MIME-Version: 1.0
Received: by 10.66.89.170 with SMTP id bp10mr35743095pab.12.1343777278903; Tue, 31 Jul 2012 16:27:58 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.68.64.103 with HTTP; Tue, 31 Jul 2012 16:27:58 -0700 (PDT)
Date: Tue, 31 Jul 2012 19:27:58 -0400
X-Google-Sender-Auth: yjCovhzDqvzbeRsVeChexfmIzrM
Message-ID: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com>
Subject: RFC Errata: when to file, and when not to
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d04289c895dc51d04c628870c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jul 2012 23:27:59 -0000

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

We've been seeing a lot of inappropriate errata reports, made by
well-meaning people who, surely, think their reports are useful, even
important.  These aren't free: they take time to process, and they form
clutter in the errata system, obscuring the ones that do fit into what
errata are meant to be.

So I wanted to clarify what's meant to be reported, and what's not.

A valid erratum, one that the IESG will mark as "Verified", mets two
criteria:

1. It is truly an *error* in the original document.  That is, it would have
been considered an error *at the time the document was published*, had it
been noticed at the time.

2. It is important, an error that would cause someone to misread the
document in a significant way, causing implementation or deployment
problems, or other serious issues.

Criterion 1 means that anything that is "wrong" because of situations or
discussions that have come up since publication are not appropriate errata.
 Consider the differences among these:

- (a) Someone realizes that the document forgot to specify the valid range
of a value.

- (b) Someone realizes that the range specified did not correctly reflect
the result of the discussion at the time (the change got missed and no one
noticed).

- (c) Someone realizes that the range specified causes problems in
practice, but we didn't know that would happen when we published the
document.

(a) and (b) are valid errata, and should get marked as "Verified".  (c) is
NOT valid for the errata system, and really ought to be marked as
"Rejected".

Criterion 2 means that minor typos are NOT appropriate errata.  The IESG
will mark these as "Held for Document Update", but, really, there is no
need to say that "an" should be "and", that a comma is missing (unless it
seriously affects the meaning and is likely to be mis-read), or that
"concensus" is misspelled (as here).  Again, consider the differences:

- (a) "The server will now respond with an error code," where "now" should
have been "not".

- (b) "The server will not repond with an error code," where "repond"
should have been "respond".

- (c) "The server will not respond with and error code," where "and" should
have been "an".

(a) is the only valid one here.  There's no real value in recording the
others as errata.

In particular, the errata system is NOT meant to be used as an issue
tracker; please do not submit errata reports with the *intent* that they be
marked as "Held for Document Update", to be used as an issue list later.
 We have mailing lists, issue trackers, and wikis for this purpose.

Barry, Applications AD

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

<span class=3D"Apple-style-span" style>We&#39;ve been seeing a lot of inapp=
ropriate errata reports, made by well-meaning people who, surely, think the=
ir reports are useful, even important. =A0These aren&#39;t free: they take =
time to process, and they form clutter in the errata system, obscuring the =
ones that do fit into what errata are meant to be.<div>
<br></div><div>So I wanted to clarify what&#39;s meant to be reported, and =
what&#39;s not.</div><div><br></div><div>A valid erratum, one that the IESG=
 will mark as &quot;Verified&quot;, mets two criteria:</div><div><br></div>
<div>1. It is truly an *error* in the original document. =A0That is, it wou=
ld have been considered an error *at the time the document was published*, =
had it been noticed at the time.</div><div><br></div><div>2. It is importan=
t, an error that would cause someone to misread the document in a significa=
nt way, causing implementation or deployment problems, or other serious iss=
ues.</div>
<div><br></div><div>Criterion 1 means that anything that is &quot;wrong&quo=
t; because of situations or discussions that have come up since publication=
 are not appropriate errata. =A0Consider the differences among these:</div>
<div><br></div><div>- (a) Someone realizes that the document forgot to spec=
ify the valid range of a value.</div><div><br></div><div>- (b) Someone real=
izes that the range specified did not correctly reflect the result of the d=
iscussion at the time (the change got missed and no one noticed).</div>
<div><br></div><div>- (c) Someone realizes that the range specified causes =
problems in practice, but we didn&#39;t know that would happen when we publ=
ished the document.</div><div><br></div><div>(a) and (b) are valid errata, =
and should get marked as &quot;Verified&quot;. =A0(c) is NOT valid for the =
errata system, and really ought to be marked as &quot;Rejected&quot;.</div>
<div><br></div><div>Criterion 2 means that minor typos are NOT appropriate =
errata. =A0The IESG will mark these as &quot;Held for Document Update&quot;=
, but, really, there is no need to say that &quot;an&quot; should be &quot;=
and&quot;, that a comma is missing (unless it seriously affects the meaning=
 and is likely to be mis-read), or that &quot;concensus&quot; is misspelled=
 (as here). =A0Again, consider the differences:</div>
<div><br></div><div>- (a) &quot;The server will now respond with an error c=
ode,&quot; where &quot;now&quot; should have been &quot;not&quot;.</div><di=
v><br></div><div>- (b) &quot;The server will not repond with an error code,=
&quot; where &quot;repond&quot; should have been &quot;respond&quot;.</div>
<div><br></div><div>- (c) &quot;The server will not respond with and error =
code,&quot; where &quot;and&quot; should have been &quot;an&quot;.</div><di=
v><br></div><div>(a) is the only valid one here. =A0There&#39;s no real val=
ue in recording the others as errata.</div>
<div><br></div><div>In particular, the errata system is NOT meant to be use=
d as an issue tracker; please do not submit errata reports with the *intent=
* that they be marked as &quot;Held for Document Update&quot;, to be used a=
s an issue list later. =A0We have mailing lists, issue trackers, and wikis =
for this purpose.<span></span></div>
<div><br></div></span><font class=3D"Apple-style-span" color=3D"#191919" fa=
ce=3D"Georgia" size=3D"4"><span class=3D"Apple-style-span" style>Barry, App=
lications AD</span></font><div><font class=3D"Apple-style-span" color=3D"#1=
91919" face=3D"Georgia" size=3D"4"></font></div>

--f46d04289c895dc51d04c628870c--

From barryleiba.mailing.lists@gmail.com  Tue Jul 31 16:33:09 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 4209D11E8170 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 16:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.959
X-Spam-Level: 
X-Spam-Status: No, score=-102.959 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUwmdc7g6eKo for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 16:33:08 -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 7D91411E808E for <ietf@ietf.org>; Tue, 31 Jul 2012 16:33:08 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so31098lbb.31 for <ietf@ietf.org>; Tue, 31 Jul 2012 16:33:07 -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=hnUMcXuhkNBm0bVJS/gbszpM/VsVI5Ch6+MYcf9PKqg=; b=twjuJbXF7bBbk5ml41yTOW9W9drPAdbZTMWGGqjcgjoRYopDPnTrHD0JKttkptHSwE R3Ek2SUKOLaSkk/mp1PA5k7rrDvd2qWTCOIDjKmkFp09URSCGBUNZH8oxXYD+MqVw4Bx yml1Wan1r8o9t7eF6ipfX8laTWSCorcNPgcYP8BRSQRm//21yEUmvsCIgxhc9SEZ7niV wSzsTCsRGOOzLqiXgMNbvKWwb2/aBEMorAv/2mXwenoVkOUuAJHa13lyLiyQFcbg8JKf FEJzk53JcZQdTuqZBS+EjMe5dVbAUWffPULRoGpItyQDdL7fDfsbE0YeRdWQW6DtUMMz 9W2A==
MIME-Version: 1.0
Received: by 10.112.42.164 with SMTP id p4mr7340319lbl.54.1343777587425; Tue, 31 Jul 2012 16:33:07 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.17.133 with HTTP; Tue, 31 Jul 2012 16:33:07 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20120731152716.088ab5d0@resistor.net>
References: <6.2.5.6.2.20120731152716.088ab5d0@resistor.net>
Date: Tue, 31 Jul 2012 19:33:07 -0400
X-Google-Sender-Auth: OCLSkHVN8gq8Ynjwwm_sO4pA3_s
Message-ID: <CAC4RtVDEYMWLbNcekVM0YEgMa872C8wgZPj-vY6M7P=BPuJcgQ@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-3777upd-eligibility-00.txt
From: Barry Leiba <barryleiba@computer.org>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=90e6ba181296c1711604c6289939
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, 31 Jul 2012 23:33:09 -0000

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

>
>  does get into other details which can influence the selection process.
>  If the objective is to avoid self-selection, one could question the
> process for the appointment of the NomCom Chair.
>

The NomCom chair does not have a vote on the NomCom, and is just a process
facilitator.  That's for exactly this reason.

Barry

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">=A0does get into other details which can inf=
luence the selection process. =A0If the objective is to avoid self-selectio=
n, one could question the process for the appointment of the NomCom Chair.<=
br>
</blockquote><div style><span class=3D"Apple-style-span" style><br></span><=
/div>The NomCom chair does not have a vote on the NomCom, and is just a pro=
cess facilitator. =A0That&#39;s for exactly this reason.<div><span class=3D=
"Apple-style-span" style><br>
</span></div><div><span class=3D"Apple-style-span" style>Barry=A0<span></sp=
an></span></div>

--90e6ba181296c1711604c6289939--

From peer2peer@gmail.com  Tue Jul 31 17:44:00 2012
Return-Path: <peer2peer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E33421F8912 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 17:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H6DebAih47xD for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 17:44:00 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 70F3A21F890E for <Ietf@ietf.org>; Tue, 31 Jul 2012 17:43:59 -0700 (PDT)
Received: by wibhm11 with SMTP id hm11so2703653wib.13 for <Ietf@ietf.org>; Tue, 31 Jul 2012 17:43: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=sJPK4JGv0Pi4zN20AduiybSHM6ynVulnkJFR9dwweuw=; b=aEgBodui4anWr0TZdmnU+iNfvf+XTk32f6XXnHRUA+t9gpJ+swGr2yQUPvaGLLQ07e ayz7XBwoFFsLdChhkp2RyszfbnnbV4qDYvhZl/7pFvTpICcghxHjEkdQNjRS9ALxCrXN 3XGrEIy7MbzEqu0tXQzHGrwbko94AMhhw715mCGBKyePYn7yijlpC73kWhzsWARBOXIi ncYoK7odGtkoxmndj5HkYXbgW/o4pWaJvOPVDdYUMIQJTrz9Agbj8QMdFvlqvVFgz+L9 shE3bRBE86DP7M9D7n++B7Aj8mO20yqRShl43XPH+2c03GD8xnl3kd+SDjUX+9XVtjt2 lYPA==
MIME-Version: 1.0
Received: by 10.216.136.95 with SMTP id v73mr7383339wei.2.1343781834205; Tue, 31 Jul 2012 17:43:54 -0700 (PDT)
Received: by 10.180.144.107 with HTTP; Tue, 31 Jul 2012 17:43:46 -0700 (PDT)
Received: by 10.180.144.107 with HTTP; Tue, 31 Jul 2012 17:43:46 -0700 (PDT)
In-Reply-To: <CAJYQ-fS6TqrbMDsaK5tb_VkDX1T3q-NGaQ6OuOUSLFPyzaXhAQ@mail.gmail.com>
References: <CAJYQ-fReKkvPXwBtpfnRa-xoY9Crb7EHJn6r+ttRNMJ6AAcO9g@mail.gmail.com> <CAJYQ-fRydy=aGAaBpzSXsfxVsJr94wMCg_6uYg9Nq0t-CytgHw@mail.gmail.com> <CAJYQ-fQ2HZU7wb9k+mhztspt6GexOM8_pDQ8AmtD_MPwGHbrdw@mail.gmail.com> <CAJYQ-fSxeCxcUUSbMTiNhynwVYrvSvp_XisBf9VpLQ_U5-BuSA@mail.gmail.com> <CAJYQ-fS1VBhBC2Rcy+g1a5kbe_zL4iBcwwrMN8C=tYnAD8rVsg@mail.gmail.com> <CAJYQ-fQcPanpSpCaHazXtVxaH7BQLTNJ-JK6T7OWCyga86gJ6g@mail.gmail.com> <CAJYQ-fS6TqrbMDsaK5tb_VkDX1T3q-NGaQ6OuOUSLFPyzaXhAQ@mail.gmail.com>
Date: Wed, 1 Aug 2012 02:43:46 +0200
Message-ID: <CAJYQ-fRxVsEnj0gNK6SihP+UoSVdZAX8QhQiNFgtQT-_sMo=Lw@mail.gmail.com>
Subject: Bar BoF: Media without censorship (Wednesday 20:00, Regency A)
From: Johan Pouwelse <peer2peer@gmail.com>
To: Ietf@ietf.org
Content-Type: multipart/alternative; boundary=0016e6de00efe22b6404c62996e9
Cc: Martin Stiemerling <Martin.Stiemerling@neclab.eu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Aug 2012 00:44:00 -0000

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

Dear All,
At the ongoing 84th IETF meeting we're organizing a bar BoF around
enhancing privacy and reducing censorship. Feel free to drop by. We start
in room regency A and probably will go really informal after 30min, in a
actual bar context: Steamworks Brewing, 375 Water Street, Vancouver,
http://m.google.com/u/m/zr4u7R

Bar BoF name:    Media without censorship (CensorFree)
Location:              IETF 84, Vancouver, Canada
Date:                    1st Aug 2012,  20:00 (Wednesday)
Room:                  Regency A
Promo slides:
http://www.ietf.org/proceedings/84/slides/slides-84-tsvarea-0.pdf(prestented
at TVSArea meeting)
Discussion doc:
https://datatracker.ietf.org/doc/draft-pouwelse-censorfree-scenarios/
Technology status: initial running code
Abstract:
    This document describes some scenarios in which one can imagine that
    the ability of authoritarian regime to censor news dissemination is
    reduced.  It tries to draw some conclusions about what's desirable
    and what's not acceptable for users in those scenarios.
    The CensorFree objective is to standardize the protocols for
    microblogging on smartphones with a focus on security and censorship
    resistance.  Microblog entries are short text messages, possibly
    enriched with pictures or streaming video.  The goal is to devise
    protocols which guard against all known forms of censorship such as:
    cyberspace sabotage, digital eavesdropping, infiltration, fraud,
    Internet kill switches and lawyer-based attacks with the best known
protective methods.

The discussion document lists some scenarios, but is still very much a work
in progress.
Hopefully the knowledge from draft-iab-privacy-considerations-03 and
draft-iab-privacy-terminology-01 can be included in this doc real soon.
   -Johan Pouwelse, Delft University of Technology

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

<p dir=3D"ltr">Dear All,<br>
At the ongoing 84th IETF meeting we&#39;re organizing a bar BoF around enha=
ncing privacy and reducing censorship. Feel free to drop by. We start in ro=
om regency A and probably will go really informal after 30min, in a actual =
bar context: Steamworks Brewing, 375 Water Street, Vancouver, <a href=3D"ht=
tp://m.google.com/u/m/zr4u7R">http://m.google.com/u/m/zr4u7R</a></p>

<p dir=3D"ltr">Bar BoF name: =A0 =A0Media without censorship (CensorFree)<b=
r>
Location: =A0 =A0 =A0 =A0 =A0 =A0 =A0IETF 84, Vancouver, Canada<br>
Date: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0 1st Aug 2012, =A020:00 (Wednes=
day)<br>
Room: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Regency A<br>
Promo slides:=A0=A0=A0=A0 <a href=3D"http://www.ietf.org/proceedings/84/sli=
des/slides-84-tsvarea-0.pdf">http://www.ietf.org/proceedings/84/slides/slid=
es-84-tsvarea-0.pdf</a> (prestented at TVSArea meeting)<br>
Discussion doc:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-pouwelse-censorfree-scena=
rios/">https://datatracker.ietf.org/doc/draft-pouwelse-censorfree-scenarios=
/</a><br>
Technology status: initial running code<br>
Abstract:<br>
=A0 =A0 This document describes some scenarios in which one can imagine tha=
t<br>
=A0 =A0 the ability of authoritarian regime to censor news dissemination is=
<br>
=A0 =A0 reduced. =A0It tries to draw some conclusions about what&#39;s desi=
rable<br>
=A0 =A0 and what&#39;s not acceptable for users in those scenarios.<br>
=A0 =A0 The CensorFree objective is to standardize the protocols for<br>
=A0 =A0 microblogging on smartphones with a focus on security and censorshi=
p<br>
=A0 =A0 resistance. =A0Microblog entries are short text messages, possibly<=
br>
=A0 =A0 enriched with pictures or streaming video. =A0The goal is to devise=
<br>
=A0 =A0 protocols which guard against all known forms of censorship such as=
:<br>
=A0 =A0 cyberspace sabotage, digital eavesdropping, infiltration, fraud,<br=
>
=A0 =A0 Internet kill switches and lawyer-based attacks with the best known=
 protective methods.</p>
<p dir=3D"ltr">The discussion document lists some scenarios, but is still v=
ery much a work in progress.<br>
Hopefully the knowledge from draft-iab-privacy-considerations-03 and<br>
draft-iab-privacy-terminology-01 can be included in this doc real soon.<br>
=A0 =A0-Johan Pouwelse, Delft University of Technology</p>

--0016e6de00efe22b6404c62996e9--

From henrik@levkowetz.com  Tue Jul 31 18:29:44 2012
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55D5611E818A; Tue, 31 Jul 2012 18:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgujudHPgBHK; Tue, 31 Jul 2012 18:29:43 -0700 (PDT)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31::14]) by ietfa.amsl.com (Postfix) with ESMTP id 6434A11E80E7; Tue, 31 Jul 2012 18:29:37 -0700 (PDT)
Received: from dhcp-67cb.meeting.ietf.org ([130.129.103.203]:61935) by merlot.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.77) (envelope-from <henrik@levkowetz.com>) id 1SwNkN-0005cw-A5; Wed, 01 Aug 2012 03:29:12 +0200
Message-ID: <50188662.6000809@levkowetz.com>
Date: Tue, 31 Jul 2012 18:29:06 -0700
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.6esrpre) Gecko/20120713 Thunderbird/10.0.6
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
References: <alpine.OSX.2.01.1207311102470.86865@173-11-110-132-sfba.hfc.comcastbusiness.net> <80A0822C5E9A4440A5117C2F4CD36A6404136619@DEMUEXC006.nsn-intra.net> <alpine.OSX.2.01.1207311421270.87763@173-11-110-132-sfba.hfc.comcastbusiness.net> <C18E588A-541E-43C7-AF41-F301E3A6AE5B@cs.columbia.edu> <50186301.9030506@levkowetz.com> <alpine.OSX.2.01.1207311615310.88195@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1207311615310.88195@173-11-110-132-sfba.hfc.comcastbusiness.net>
X-Enigmail-Version: 1.4
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB2AFB4DEB5DD6908D8A7F40E"
X-SA-Exim-Connect-IP: 130.129.103.203
X-SA-Exim-Rcpt-To: ole@cisco.com, smb@cs.columbia.edu, mehmet.ersue@nsn.com, rsag@rfc-editor.org, rsoc@iab.org, ietf@ietf.org, hlflanagan@gmail.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: RFC and I-D Citation Tool
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:57:07 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: The IETF <ietf@ietf.org>, RSOC <rsoc@iab.org>, Heather Flanagan <hlflanagan@gmail.com>, rsag@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: Wed, 01 Aug 2012 01:29:44 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB2AFB4DEB5DD6908D8A7F40E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Ole,

On 2012-07-31 16:17 Ole Jacobsen said the following:
>=20
> One feature request that I discussed with Henrik was to either
> "auto-detect" I-D file names and handle them slightly differently
> from RFC numbers (by putting the file name as the final entry)
> OR just having two tools. With the kind of feedback Henrik is
> getting I am sure the tool will be improved/enhanced over time.

I'm thinking about how to do this best now.  One option I'm considering
is to provide two template fields in the tool, one to be used for
references to RFCs, the other to references to drafts.


Best regards,

	Henrik


--------------enigB2AFB4DEB5DD6908D8A7F40E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAlAYhmIACgkQeVhrtTJkXCMjDgCg+Kv9IMH4rZTIj344uNr7xNd3
TA0AoP4ZA8/YOHc0Ns2qmhw+Nu/dGIsJ
=z2G9
-----END PGP SIGNATURE-----

--------------enigB2AFB4DEB5DD6908D8A7F40E--

From barryleiba@gmail.com  Tue Jul 31 23:27:17 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 2920E21F8548 for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 23:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.882
X-Spam-Level: 
X-Spam-Status: No, score=-102.882 tagged_above=-999 required=5 tests=[AWL=-0.061, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uTvgXuvo--Ka for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 23:27:16 -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 443B821F86D7 for <ietf@ietf.org>; Tue, 31 Jul 2012 23:27:16 -0700 (PDT)
Received: by pbbjt11 with SMTP id jt11so570060pbb.31 for <ietf@ietf.org>; Tue, 31 Jul 2012 23:27:11 -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=JgDojGrwNyQ9AEuacuMRtze/Td9KYZm4wuEaI3B9BD8=; b=v5YDodlYPEDPS0oiTDCYYBT3snzjnwxKHKMZjVqihOv/WA10dspoQj7L1LGNsnG3Qo 8xqOUndbW4xy3jlsVgWCMTNicY/PNtI+dBqgWkMpFSYtXSGSVxbx+vcPTRatRLKqNsvS JNz1j4dnLz0tgJF5DgGtpWmvWU3+Y5LZ/Sz96wp5s/X5iyo41zPz3Ms+UR2B1uwm3nf5 l7jjFghBZ5ubYp+IFDzQD1DRo0bAoVEQzVIzLVyp3xumibCnfxqWLcWAZ/8AN962PAE4 iA9JiJDPu52NAbEYFNzxjWmjH5GqSSHWb6yXgWDbhrdK7Zem4L8LLr6khczfJ0Rqf4OJ N5Cg==
MIME-Version: 1.0
Received: by 10.68.221.74 with SMTP id qc10mr49325508pbc.31.1343802431011; Tue, 31 Jul 2012 23:27:11 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.68.64.103 with HTTP; Tue, 31 Jul 2012 23:27:10 -0700 (PDT)
In-Reply-To: <20120801062346.31753.92309.idtracker@ietfa.amsl.com>
References: <20120801062346.31753.92309.idtracker@ietfa.amsl.com>
Date: Wed, 1 Aug 2012 02:27:10 -0400
X-Google-Sender-Auth: 7ej72xkn2iCWQRq70CPtPLl87KM
Message-ID: <CALaySJLdEKXPPaUYmxAONv2JLbWeZFhmsqn9nV3S28k7FFi+nA@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-cotton-iana-5226bis-00.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: Wed, 01 Aug 2012 06:27:17 -0000

We're working on a new edition of BCP 26, "Guidelines for Writing an
IANA Considerations Section in RFCs".  Comments, please.  You can see
Section 12.1 for a summary of significant changes.

Barry (with Michelle and Thomas)


On Wed, Aug 1, 2012 at 2:23 AM,  <internet-drafts@ietf.org> wrote:
>
> A new version of I-D, draft-leiba-cotton-iana-5226bis-00.txt
> has been successfully submitted by Barry Leiba and posted to the
> IETF repository.
>
> Filename:        draft-leiba-cotton-iana-5226bis
> Revision:        00
> Title:           Guidelines for Writing an IANA Considerations Section in RFCs
> Creation date:   2012-08-01
> WG ID:           Individual Submission
> Number of pages: 36
> URL:             http://www.ietf.org/internet-drafts/draft-leiba-cotton-iana-5226bis-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis
> Htmlized:        http://tools.ietf.org/html/draft-leiba-cotton-iana-5226bis-00
>
>
> Abstract:
>    Many protocols make use of identifiers consisting of constants and
>    other well-known values.  Even after a protocol has been defined and
>    deployment has begun, new values may need to be assigned (such as for
>    a new option type in DHCP, or a new encryption or authentication
>    transform for IPsec).  To ensure that such quantities have consistent
>    values and interpretations across all implementations, their
>    assignment must be administered by a central authority.  For IETF
>    protocols, that role is provided by the Internet Assigned Numbers
>    Authority (IANA).
>
>    In order for IANA to manage a given namespace prudently, it needs
>    guidelines describing the conditions under which new values can be
>    assigned or when modifications to existing values can be made.  If
>    IANA is expected to play a role in the management of a namespace,
>    IANA must be given clear and concise instructions describing that
>    role.  This document discusses issues that should be considered in
>    formulating a policy for assigning values to a namespace and provides
>    guidelines for authors on the specific text that must be included in
>    documents that place demands on IANA.
>
>    This document obsoletes RFC 5226.

From abdussalambaryun@gmail.com  Tue Jul 31 23:49:01 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 5601E11E809C for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 23:49:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.462
X-Spam-Level: 
X-Spam-Status: No, score=-3.462 tagged_above=-999 required=5 tests=[AWL=0.137,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PXi12+ym-ZxW for <ietf@ietfa.amsl.com>; Tue, 31 Jul 2012 23:49: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 7719211E8097 for <ietf@ietf.org>; Tue, 31 Jul 2012 23:49:00 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so7144483vcb.31 for <ietf@ietf.org>; Tue, 31 Jul 2012 23:49: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=1TjqdxdWaqmVcR1fX1WtLakpnq788xwdOHrOubdnBSE=; b=srCgA5lDkOcUUouylQP0n+djSrHdntOXh/IqYlqD3vQfPk1gO7WZZrurHngi/wtZO0 6h5PpKc1zlnfxiqF5PKs6XjHTWsLqtBKEnQ9iE0wHv8cDzJU2CMUXRiQYhI9aEbpnsXE tuY8RW6WkmgnCseYhQzS7I3w25rKJV1uU3SGCu1w8kCCe9EjMwXc+S0Z499HHfmk4MPr +i0kuwh/I3YJpDzzoAHt7wPhj2sGuGYbsJp7vLP4IUkCqx7b540DOdo4RsykpeltnCM5 W9k9nvdstArhoMEuOy0+doZ51xisEkntYJAdNyWYmFqkudXVeCm8zLMzV1SC1a4NNV1C Sp3w==
MIME-Version: 1.0
Received: by 10.220.152.67 with SMTP id f3mr16283653vcw.19.1343803740015; Tue, 31 Jul 2012 23:49:00 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Tue, 31 Jul 2012 23:48:59 -0700 (PDT)
Date: Wed, 1 Aug 2012 08:48:59 +0200
Message-ID: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com>
Subject: Fwd: New Version Notification for: draft-baryun-rfc2119-update-00.txt
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, 01 Aug 2012 06:49:01 -0000

Dear All,

I written this draft starting a RFC2119 update for the reasons of
discussion threads in [1] and [2]. Please check draft and feedback,
thanking you.

Best Regards
Abdussalam

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

====================================================

From: internet-drafts@ietf.org
Date: Tue, 31 Jul 2012 23:31:10 -0700
Subject: New Version Notification for draft-baryun-rfc2119-update-00.txt

A new version of I-D, draft-baryun-rfc2119-update-00.txt
has been successfully submitted by Abdussalam Nuri Baryun and posted to the
IETF repository.

Filename:	 draft-baryun-rfc2119-update
Revision:	 00
Title:		 Key Words of Conditional Language of Requirements Levels
Creation date:	 2012-07-30
WG ID:		 Individual Submission
Number of pages: 3
URL:
http://www.ietf.org/internet-drafts/draft-baryun-rfc2119-update-00.txt
Status:          http://datatracker.ietf.org/doc/draft-baryun-rfc2119-update
Htmlized:        http://tools.ietf.org/html/draft-baryun-rfc2119-update-00


Abstract:
   In many standards track documents conditional words are used to
   signify the requirements in the specification. These words are
   prefered to be capitalized. This document defines these conditional
   words as they should be interpreted in IETF documents. Authors who
   follow these guidelines should incorporate this phrase near the
   beginning of their document. The additional key words to words
   described in RFC2119 are; "IF, THEN", "ELSE IF", "ELSE".


The IETF Secretariat
